READ Free Dumps For Oracle- 1z0-060
| Question ID 20774 | Your multitenant container database (CDB) contains three pluggable database (PDBs). You find that the control file is damaged. You plan to use RMAN to recover
the control file. There are no startup triggers associated with the PDBs.
Which three steps should you perform to recover the control file and make the database fully operational?
|
| Option A | Mount the container database (CDB) and restore the control file from the control file auto backup.
|
| Option B | Recover and open the CDB in NORMAL mode.
|
| Option C | Mount the CDB and then recover and open the database, with the RESETLOGS option.
|
| Option D | Open all the pluggable databases.
|
| Option E | Recover each pluggable database
|
| Option F | Start the database instance in the nomount stage and restore the control file from control file auto backup.
|
| Correct Answer | C,D,F |
Explanation Explanation: Step 1: F Step 2: D Step 3: C: If all copies of the current control file are lost or damaged, then you must restore and mount a backup control file. You must then run the RECOVERcommand, even if no data files have been restored, and open the database with the RESETLOGS option. Note: * RMAN and Oracle Enterprise Manager Cloud Control (Cloud Control) provide full support for backup and recovery in a multitenant environment. You can back up and recover a whole multitenant container database (CDB), root only, or one or more pluggable databases (PDBs).
| Question ID 20775 | Real 18
Oracle 1z0-060 Exam
A new report process containing a complex query is written, with high impact on the database. You want to collect basic statistics about query, such as the level of
parallelism, total database time, and the number of I/O requests.
For the database instance STATISTICS_LEVEL, the initialization parameter is set to TYPICAL and the CONTROL_MANAGEMENT_PACK_ACCESS parameter is
set to DIAGNOSTIC+TUNING.
What should you do to accomplish this task?
|
| Option A | Execute the query and view Active Session History (ASH) for information about the query.
|
| Option B | Enable SQL trace for the query.
|
| Option C | Create a database operation, execute the query, and use the DBMS_SQL_MONITOR.REPORT_SQL_MONITOR function to view the report.
|
| Option D | Use the DBMS_APPLICATION_INFO.SET_SESSION_LONGOPS procedure to monitor query execution and view the information from the V$SESSION_LONGOPS view.
|
| Correct Answer | C |
Explanation Explanation: The REPORT_SQL_MONITOR function is used to return a SQL monitoring report for a specific SQL statement. Incorrect: Not A: Not interested in session statistics, only in statistics for the particular SQL query. Not B: We are interested in statistics, not tracing. Not D: SET_SESSION_LONGOPS Procedure This procedure sets a row in the V$SESSION_LONGOPS view. This is a view that is used to indicate the on-going progress of a long running operation. Some Oracle functions, such as parallel execution and Server Managed Recovery, use rows in this view to indicate the status of, for example, a database backup. Applications may use the SET_SESSION_LONGOPS procedure to advertise information on the progress of application specific long running tasks so that the progress can be monitored by way of the V$SESSION_LONGOPS view.