1z0-063: Oracle Database 12c Advanced Administration Instance Practice Questions

You notice that the performance of your production 24/7 Oracle 12c database has significantly degraded. Sometimes you are not able to connect to the instance because it hangs. You do not want to restart the database instance. How can you detect the cause of the degraded performance?

• AA. Enable Memory Access Mode, which reads performance data from SGA.
• BB. Use emergency monitoring to fetch data directly from SGA for analysis.
• CC. Run Automatic Database Diagnostic Monitor (ADDM) to fetch information from the latest Automatic Workload Repository (AWR) snapshots.
• DD. Use Active Session History (ASH) data and hang analysis in regular performance monitoring.
• EE. Run ADDM in diagnostic mode.

You issue commands in SQL*Plus as the Oracle owner, to enable multithreading for your UNIX-based Oracle 12c database: CONNECT /AS SYSDBA ALTER SYSTEM SET THREADED_EXECUTION=TRUE SCOPE=SPFILE; SHUTDOWN IMMEDIATE You then restart the instance and get an error: STARTUP ORA-01031: insufficient privileges Why does the startup command return the error shown?

• AA. because the threaded architecture requires exiting from sql*plus and reconnecting with sql*Plus / as sysdba before issuing a startup command
• BB. because the threaded architecture requires issuing a new connect / as sysdba from within sql*plus before issuing a startup command
• CC. because the threaded architecture requires authentication using a password file before issuing a startup command
• DD. because the threaded architecture requires connecting to the instance via a listener before issuing a startup command
• EE. because the threaded architecture requires restarting the listener before issuing a startup command