Want to know Exambible 1Z0-062 Exam practice test features? Want to lear more about Oracle Oracle Database 12c: Installation and Administration certification experience? Study Verified Oracle 1Z0-062 answers to Latest 1Z0-062 questions at Exambible. Gat a success with an absolute guarantee to pass Oracle 1Z0-062 (Oracle Database 12c: Installation and Administration) test on your first attempt.
2021 Jan 1Z0-062 practice test
Q61. Examine the contents of SQL loader control file:
Which three statements are true regarding the SQL* Loader operation performed using the control file?
A. An EMP table is created if a table does not exist. Otherwise, if the EMP table is appended with the loaded data.
B. The SQL* Loader data file myfile1.dat has the column names for the EMP table.
C. The SQL* Loader operation fails because no record terminators are specified.
D. Field names should be the first line in the both the SQL* Loader data files.
E. The SQL* Loader operation assumes that the file must be a stream record format file with the normal carriage return string as the record terminator.
Explanation: A: The APPEND keyword tells SQL*Loader to preserve any preexisting data in the table. Other options allow you to delete preexisting data, or to fail with an error if the table is not empty to begin with.
B (not D): Note:
* SQL*Loader-00210: first data file is empty, cannot process the FIELD NAMES record
Cause: The data file listed in the next message was empty. Therefore, the FIELD NAMES
FIRST FILE directive could not be processed.
Action: Check the listed data file and fix it. Then retry the operation
* A comma-separated values (CSV) (also sometimes called character-separated values, because the separator character does not have to be a comma) file stores tabular data (numbers and text) in plain-text form. Plain text means that the file is a sequence of characters, with no data that has to be interpreted instead, as binary numbers. A CSV file consists of any number of records, separated by line breaks of some kind; each record consists of fields, separated by some other character or string, most commonly a literal comma or tab. Usually, all records have an identical sequence of fields.
* Fields with embedded commas must be quoted.
1997,Ford,E350,"Super, luxurious truck"
* SQL*Loader is a bulk loader utility used for moving data from external files into the Oracle database.
Q62. A database is stored in an Automatic Storage Management (ASM) disk group, disk group, DGROUP1 with SQL:
There is enough free space in the disk group for mirroring to be done.
What happens if the CONTROLLER1 failure group becomes unavailable due to error of for maintenance?
A. Transactions and queries accessing database objects contained in any tablespace stored in DGROUP1 will fall.
B. Mirroring of allocation units will be done to ASM disks in the CONTROLLER2 failure group until the CONTROLLER1 for failure group is brought back online.
C. The data in the CONTROLLER1 failure group is copied to the controller2 failure group and rebalancing is initiated.
D. ASM does not mirror any data until the controller failure group is brought back online, and newly allocated primary allocation units (AU) are stored in the controller2 failure group, without mirroring.
E. Transactions accessing database objects contained in any tablespace stored in DGROUP1 will fail but queries will succeed.
Explanation: CREATE DISKGROUP NORMAL REDUNDANCY
* For Oracle ASM to mirror files, specify the redundancy level as NORMAL REDUNDANCY (2-way mirroring by default for most file types) or HIGH REDUNDANCY (3-way mirroring for all files).
Q63. Examine the following parameters for a database instance:
MEMORY_MAX_TARGET=0 MEMORY_TARGET=0 SGA_TARGET=0 PGA_AGGREGATE_TARGET=500m
Which three initialization parameters are not controlled by Automatic Shared Memory Management (ASMM)?
Explanation: Manually Sized SGA Components that Use SGA_TARGET Space SGA Component, Initialization Parameter / The log buffer LOG_BUFFER / The keep and recycle buffer caches DB_KEEP_CACHE_SIZE DB_RECYCLE_CACHE_SIZE / Nonstandard block size buffer caches DB_nK_CACHE_SIZE
* In addition to setting SGA_TARGET to a nonzero value, you must set to zero all initialization parameters listed in the table below to enable full automatic tuning of the automatically sized SGA components.
* Table, Automatically Sized SGA Components and Corresponding Parameters
Q64. What happens if a maintenance window closes before a job that collects optimizer statistics completes?
A. The job is terminated and the gathered statistics are not saved.
B. The job is terminated but the gathered statistics are not published.
C. The job continues to run until all statistics are gathered.
D. The job is terminated and statistics for the remaining objects are collected the next time the maintenance window opens.
Q65. You notice a performance change in your production Oracle 12c database. You want to know which change caused this performance difference.
Which method or feature should you use?
A. Compare Period ADDM report
B. AWR Compare Period report
C. Active Session History (ASH) report
D. Taking a new snapshot and comparing it with a preserved snapshot
Explanation: The awrddrpt.sql report is the Automated Workload Repository Compare
Period Report. The awrddrpt.sql script is located in the $ORACLE_HOME/rdbms/admin directory.
Not A: Compare Period ADDM
Use this report to perform a high-level comparison of one workload replay to its capture or to another replay of the same capture. Only workload replays that contain at least 5 minutes of database time can be compared using this report.
Most recent 1Z0-062 test:
Q66. Which statement is true about the Log Writer process?
A. It writes when it receives a signal from the checkpoint process (CKPT).
B. It writes concurrently to all members of multiplexed redo log groups.
C. It writes after the Database Writer process writes dirty buffers to disk.
D. It writes when a user commits a transaction.
Reference: http://docs.oracle.com/cd/B19306_01/server.102/b14220/process.htm (see log writer process (LGWR))
Q67. Your multitenant container database, CDB1, is running in ARCHIVELOG mode and has two pluggable databases, HR_PDB and ACCOUNTS_PDB. An RMAN backup exists for the database.
You issue the command to open ACCOUNTS_PDB and find that the USERDATA.DBF data file for the default permanent tablespace USERDATA belonging to ACCOUNTS_PDB is corrupted.
What should you do before executing the commands to restore and recover the data file in ACCOUNTS_PDB?
A. Place CDB1 in the mount stage and then the USERDATA tablespace offline in ACCOUNTS_PDB.
B. Place CDB1 in the mount stage and issue the ALTER PLUGGABLE DATABASE accounts_pdb CLOSE IMMEDIATE command.
C. Issue the ALTER PLUGGABLE DATABASE accounts_pdb RESTRICTED command.
D. Take the USERDATA tablespace offline in ACCOUNTS_PDB.
Explanation: * You can take an online tablespace offline so that it is temporarily unavailable for general use. The rest of the database remains open and available for users to access data. Conversely, you can bring an offline tablespace online to make the schema objects within the tablespace available to database users. The database must be open to alter the availability of a tablespace.
Q68. Which three are direct benefits of the multiprocess, multithreaded architecture of Oracle Database 12c when it is enabled?
A. Reduced logical I/O
B. Reduced virtual memory utilization
C. Improved parallel Execution performance
D. Improved Serial Execution performance
E. Reduced physical I/O
F. Reduced CPU utilization
Explanation: * Multiprocess and Multithreaded Oracle Database Systems
Multiprocess Oracle Database (also called multiuser Oracle Database) uses several processes to run different parts of the Oracle Database code and additional Oracle processes for the users—either one process for each connected user or one or more processes shared by multiple users. Most databases are multiuser because a primary advantage of a database is managing data needed by multiple users simultaneously.
Each process in a database instance performs a specific job. By dividing the work of the database and applications into several processes, multiple users and applications can connect to an instance simultaneously while the system gives good performance.
* In previous releases, Oracle processes did not run as threads on UNIX and Linux systems. Starting in Oracle Database 12c, the multithreaded Oracle Database model enables Oracle processes to execute as operating system threads in separate address spaces.
Q69. Your multitenant container database (CDB) contains pluggable databases (PDBs), you are connected to the HR_PDB. You execute the following command:
SQL > CREATE UNDO TABLESPACE undotb01
DATAFILE ‘u01/oracle/rddb1/undotbs01.dbf’ SIZE 60M AUTOEXTEND ON;
What is the result?
A. It executes successfully and creates an UNDO tablespace in HR_PDB.
B. It falls and reports an error because there can be only one undo tablespace in a CDB.
C. It fails and reports an error because the CONTAINER=ALL clause is not specified in the command.
D. It fails and reports an error because the CONTAINER=CURRENT clause is not specified in the command.
E. It executes successfully but neither tablespace nor the data file is created.
Explanation: Interesting behavior in 188.8.131.52 DB of creating an undo tablespace in a PDB. With the new Multitenant architecture the undo tablespace resides at the CDB level and PDBs all share the same UNDO tablespace.
When the current container is a PDB, an attempt to create an undo tablespace fails without returning an error.
Q70. Identify three scenarios in which you would recommend the use of SQL Performance Analyzer to analyze impact on the performance of SQL statements.
A. Change in the Oracle Database version
B. Change in your network infrastructure
C. Change in the hardware configuration of the database server
D. Migration of database storage from non-ASM to ASM storage
E. Database and operating system upgrade
Explanation: Oracle 11g/12c makes further use of SQL tuning sets with the SQL Performance Analyzer, which compares the performance of the statements in a tuning set before and after a database change. The database change can be as major or minor as you like, such as:
* (E) Database, operating system, or hardware upgrades.
* (A,C) Database, operating system, or hardware configuration changes.
* Database initialization parameter changes.
* Schema changes, such as adding indexes or materialized views.
* Refreshing optimizer statistics.
* Creating or changing SQL profiles.