Our pass rate is high to 98.9% and the similarity percentage between our 1z0 062 dumps study guide and real exam is 90% based on our seven-year educating experience. Do you want achievements in the Oracle 1z0 062 pdf exam in just one try? I am currently studying for the Oracle 1z0 062 pdf exam. Latest Oracle oracle database 12c installation and administration 1z0 062 pdf Test exam practice questions and answers, Try Oracle 1z0 062 dumps Brain Dumps First.

Q17. To implement Automatic Management (AMM), you set the following parameters: 

When you try to start the database instance with these parameter settings, you receive the following error message: 

SQL > startup 

ORA-00824: cannot set SGA_TARGET or MEMORY_TARGET due to existing internal settings, see alert log for more information. 

Identify the reason the instance failed to start. 

A. The PGA_AGGREGATE_TARGET parameter is set to zero. 

B. The STATISTICS_LEVEL parameter is set to BASIC. 

C. Both the SGA_TARGET and MEMORY_TARGET parameters are set. 

D. The SGA_MAX_SIZE and SGA_TARGET parameter values are not equal. 

Answer:

Explanation: 

Example: SQL> startup force ORA-00824: cannot set SGA_TARGET or MEMORY_TARGET due to existing internal settings ORA-00848: STATISTICS_LEVEL cannot be set to BASIC with SGA_TARGET or MEMORY_TARGET 


Q18. You are about to plug a multi-terabyte non-CDB into an existing multitenant container database (CDB) as a pluggable database (PDB). 

The characteristics of the non-CDB are as follows: 

Version: Oracle Database 12c Releases 1 64-bit Character set: WE8ISO8859P15 National character set: AL16UTF16 O/S: Oracle Linux 6 64-bit 

The characteristics of the CDB are as follows: 

Version: Oracle Database 12c Release 1 64-bit Character set: AL32UTF8 O/S: Oracle Linux 6 64-bit 

Which technique should you use to minimize down time while plugging this non-CDB into the CDB? 

A. Transportable database 

B. Transportable tablespace 

C. Data Pump full export / import 

D. The DBMS_PDB package 

E. RMAN 

Answer: D Explanation: 

Note: 

* Generating a Pluggable Database Manifest File for the Non-CDB 

Execute the dbms_pdb.describe procedure to generate the manifest file. 

exec dbms_pdb.describe(pdb_descr_file=>'/u01/app/oracle/oradata/noncdb/noncdb.xml'); 

Shut down the noncdb instance to prepare to copy the data files in the next section. 

shutdown immediate exit 


Q19. 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. 

Answer:

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. 


Q20. 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. 

Answer: A,B,E 

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 

E: 

* 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. 

Example: 

1997,Ford,E350,"Super, luxurious truck" 

Note: 

* SQL*Loader is a bulk loader utility used for moving data from external files into the Oracle database. 


Q21. A user establishes a connection to a database instance by using an Oracle Net connection. You want to ensure the following: 

1. The user account must be locked after five unsuccessful login attempts. 

2. Data read per session must be limited for the user. 

3- The user cannot have more than three simultaneous sessions. 

4. The user must have a maximum of 10 minutes session idle time before being logged off automatically. 

How would you accomplish this? 

A. by granting a secure application role to the user 

B. by implementing Database Resource Manager 

C. by using Oracle Label Security options 

D. by assigning a profile to the user 

Answer:


Q22. The persistent configuration settings for RMAN have default for all parameters. 

Identify four RMAN commands that produce a multi-section backup. 

A. BACKUP TABLESPACE SYSTEM SECTION SIZE 100M; 

B. BACKUP AS COPY TABLESPACE SYSTEM SECTION SIZE 100M; 

C. BACKUP ARCHIVELOG ALL SECTION SIZE 25M; 

D. BACKUP TABLESPACE "TEMP" SECTION SIZE 10M; 

E. BACKUP TABLESPACE "UNDO" INCLUDE CURRENT CONTROLFILE SECTION SIZE 100M; 

F. BACKUP SPFILE SECTION SIZE 1M; 

G. BACKUP INCREMENTAL LEVEL 0 TABLESPACE SYSAUX SECTION SIZE 100M; 

Answer: A,B,C,G 


Q23. 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 

Answer: B,C,F 

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. 


Q24. Examine the commands executed to monitor database operations: 

$> conn sys oracle/oracle@prod as sysdba 

SQL > VAR eid NUMBER 

SQL > EXEC: eid := DBMS_SQL_MONITOR.BEGIN_OPERATION (‘batch_job’ , FORCED_TRACKING => ‘Y’); 

Which two statements are true? 

A. Database operations will be monitored only when they consume a significant amount of resource. 

B. Database operations for all sessions will be monitored. 

C. Database operations will be monitored only if the STATISTICS_LEVEL parameter is set to TYPICAL and CONTROL_MANAGEMENT_PACK_ACCESS is set DIAGNISTIC + TUNING. 

D. Only DML and DDL statements will be monitored for the session. 

E. All subsequent statements in the session will be treated as one database operation and will be monitored. 

Answer: C,E 

Explanation: C: Setting the CONTROL_MANAGEMENT_PACK_ACCESS initialization parameter to DIAGNOSTIC+TUNING (default) enables monitoring of database operations. Real-Time SQL Monitoring is a feature of the Oracle Database Tuning Pack. 

Note: 

* The DBMS_SQL_MONITOR package provides information about Real-time SQL 

Monitoring and Real-time Database Operation Monitoring. 

*(not B) BEGIN_OPERATION Function 

starts a composite database operation in the current session. 

/ (E) FORCE_TRACKING - forces the composite database operation to be tracked when the operation starts. You can also use the string variable 'Y'. 

/ (not A) NO_FORCE_TRACKING - the operation will be tracked only when it has consumed at least 5 seconds of CPU or I/O time. You can also use the string variable 'N'. 


Q25. Which three statements are true when the listener handles connection requests to an Oracle 12c database instance with multithreaded architecture enabled In UNIX? 

A. Thread creation must be routed through a dispatcher process 

B. The local listener may spawn a now process and have that new process create a thread 

C. Each Oracle process runs an SCMN thread. 

D. Each multithreaded Oracle process has an SCMN thread. 

E. The local listener may pass the request to an existing process which in turn will create a thread. 

Answer: A,D,E 


Q26. Your multitenant container (CDB) containing three pluggable databases (PDBs) is running in ARCHIVELOG mode. You find that the SYSAUX tablespace is corrupted in the root container. 

The steps to recover the tablespace are as follows: 

1. Mount the CDB. 

2. Close all the PDBs. 

3. Open the database. 

4. Apply the archive redo logs. 

5. Restore the data file. 

6. Take the SYSAUX tablespace offline. 

7. Place the SYSAUX tablespace online. 

8. Open all the PDBs with RESETLOGS. 

9. Open the database with RESETLOGS. 

10. Execute the command SHUTDOWN ABORT. 

Which option identifies the correct sequence to recover the SYSAUX tablespace? 

A. 6, 5, 4, 7 

B. 10, 1, 2, 5, 8 

C. 10, 1, 2, 5, 4, 9, 8 

D. 10, 1, 5, 8, 10 

Answer:

Explanation: RMAN> ALTER TABLESPACE sysaux OFFLINE IMMEDIATE; RMAN> RESTORE TABLESPACE sysaux; RMAN> RECOVER TABLESPACE sysaux; RMAN> ALTER TABLESPACE sysaux ONLINE; 

* Example: 

While evaluating the 12c beta3 I was not able to do the recover while testing “all pdb files lost”. 

Cannot close the pdb as the system datafile was missing… 

So only option to recover was: 

Shutdown cdb (10) 

startup mount; (1) 

restore pluggable database 

recover pluggable database 

alter database open; 

alter pluggable database name open; 

Oracle support says: You should be able to close the pdb and restore/recover the system tablespace of PDB. 

* Inconsistent backups are usually created by taking online database backups. You can also make an inconsistent backup by backing up data files while a database is closed, either: 

/ Immediately after the crash of an Oracle instance (or, in an Oracle RAC configuration, all instances) / After shutting down the database using SHUTDOWN ABORT 

Inconsistent backups are only useful if the database is in ARCHIVELOG mode and all archived redo logs created since the backup are available. 

* Open the database with the RESETLOGS option after finishing recovery: SQL> ALTER DATABASE OPEN RESETLOGS; 


Q27. You are about to plug a multi-terabyte non-CDB into an existing multitenant container database (CDB). 

The characteristics of the non-CDB are as follows: 

Version: Oracle Database 11g Release 2 (11.2.0.2.0) 64-bit Character set: AL32UTF8 National character set: AL16UTF16 O/S: Oracle Linux 6 64-bit 

The characteristics of the CDB are as follows: 

Version: Oracle Database 12c Release 1 64-bit Character Set: AL32UTF8 National character set: AL16UTF16 O/S: Oracle Linux 6 64-bit 

Which technique should you use to minimize down time while plugging this non-CDB into the CDB? 

A. Transportable database 

B. Transportable tablespace 

C. Data Pump full export/import 

D. The DBMS_PDB package 

E. RMAN 

Answer:

Explanation: * Overview, example: 

-Log into ncdb12c as sys 

-Get the database in a consistent state by shutting it down cleanly. 

-Open the database in read only mode 

-Run DBMS_PDB.DESCRIBE to create an XML file describing the database. 

-Shut down ncdb12c 

-Connect to target CDB (CDB2) 

-Check whether non-cdb (NCDB12c) can be plugged into CDB(CDB2) 

-Plug-in Non-CDB (NCDB12c) as PDB(NCDB12c) into target CDB(CDB2). 

-Access the PDB and run the noncdb_to_pdb.sql script. 

-Open the new PDB in read/write mode. 

* You can easily plug an Oracle Database 12c non-CDB into a CDB. Just create a PDB manifest file for the non-CDB, and then use the manifest file to create a cloned PDB in the CDB. 

* Note that to plugin a non-CDB database into a CDB, the non-CDB database needs to be of version 12c as well. So existing 11g databases will need to be upgraded to 12c before they can be part of a 12c CDB. 


Q28. You performed an incremental level 0 backup of a database: 

RMAN > BACKUP INCREMENTAL LEVEL 0 DATABASE; 

To enable block change tracking after the incremental level 0 backup, you issued this 

command: 

SQL > ALTER DATABASE ENABLE BLOCK CHANGE TRACKING USING FILE 

‘ /mydir/rman_change_track.f’; 

To perform an incremental level 1 cumulative backup, you issued this command: 

RMAN> BACKUP INCREMENTAL LEVEL 1 CUMULATIVE DATABASE; 

Which three statements are true? 

A. Backup change tracking will sometimes reduce I/O performed during cumulative incremental backups. 

B. The change tracking file must always be backed up when you perform a full database backup. 

C. Block change tracking will always reduce I/O performed during cumulative incremental backups. 

D. More than one database block may be read by an incremental backup for a change made to a single block. 

E. The incremental level 1 backup that immediately follows the enabling of block change tracking will not read the change tracking file to discover changed blocks. 

Answer: A,D,E 

Explanation: A: In a cumulative level 1 backup, RMAN backs up all the blocks used since the most recent level 0 incremental backup. 

E:.Oracle Block Change Tracking Once enabled; this new 10g feature records the modified since last backup and stores the log of it in a block change tracking file using the CTW (Change Tracking Writer) process. During backups RMAN uses the log file to identify the specific blocks that must be backed up. This improves RMAN's performance as it does not have to scan whole datafiles to detect changed blocks. Logging of changed blocks is performed by the CTRW process which is also responsible for writing data to the block change tracking file. 

Note: 

* An incremental level 0 backup backs up all blocks that have ever been in use in this database. 


Q29. Which two statements are true about the use of the procedures listed in the v$sysaux_occupants.move_procedure column? 

A. The procedure may be used for some components to relocate component data to the SYSAUX tablespace from its current tablespace. 

B. The procedure may be used for some components to relocate component data from the SYSAUX tablespace to another tablespace. 

C. All the components may be moved into SYSAUX tablespace. 

D. All the components may be moved from the SYSAUX tablespace. 

Answer: A,B 


Q30. Examine the details of the Top 5 Timed Events in the following Automatic Workloads Repository (AWR) report: 

What are three possible causes for the latch-related wait events? 

A. The size of the shared pool is too small. 

B. Cursors are not being shared. 

C. A large number COMMITS are being performed. 

D. There are frequent logons and logoffs. 

E. The buffers are being read into the buffer cache, but some other session is changing the buffers. 

Answer: A,B,E 


Q31. Which three statements are true about a job chain? 

A. It can contain a nested chain of jobs. 

B. It can be used to implement dependency-based scheduling. 

C. It cannot invoke the same program or nested chain in multiple steps in the chain. 

D. It cannot have more than one dependency. 

E. It can be executed using event-based or time-based schedules. 

Answer: A,B,E 

Reference: http://docs.oracle.com/cd/B28359_01/server.111/b28310/scheduse009.htm#ADMIN12459 


Q32. You executed this command to create a password file: 

$ orapwd file = orapworcl entries = 10 ignorecase = N 

Which two statements are true about the password file? 

A. It will permit the use of uppercase passwords for database users who have been granted the SYSOPER role. 

B. It contains username and passwords of database users who are members of the OSOPER operating system group. 

C. It contains usernames and passwords of database users who are members of the OSDBA operating system group. 

D. It will permit the use of lowercase passwords for database users who have granted the SYSDBA role. 

E. It will not permit the use of mixed case passwords for the database users who have been granted the SYSDBA role. 

Answer: A,D 

Explanation: * You can create a password file using the password file creation utility, ORAPWD. 

* Adding Users to a Password File 

When you grant SYSDBA or SYSOPER privileges to a user, that user's name and privilege information are added to the password file. If the server does not have an EXCLUSIVE 

password file (that is, if the initialization parameter REMOTE_LOGIN_PASSWORDFILE is NONE or SHARED, or the password file is missing), Oracle Database issues an error if you attempt to grant these privileges. 

A user's name remains in the password file only as long as that user has at least one of these two privileges. If you revoke both of these privileges, Oracle Database removes the user from the password file. 

* The syntax of the ORAPWD command is as follows: 

ORAPWD FILE=filename [ENTRIES=numusers] [FORCE={Y|N}] [IGNORECASE={Y|N}] [NOSYSDBA={Y|N}] 

* IGNORECASE If this argument is set to y, passwords are case-insensitive. That is, case is ignored when comparing the password that the user supplies during login with the password in the password file.