Oracle 1Z0-060 Online Practice Questions and Exam Preparation

Oracle 1Z0-060 Online Questions & Answers

• Question 211:

  Which three statements are true about adaptive SQL plan management?

  A. It automatically performs verification or evolves non-accepted plans, in COMPREHENSIVE mode when they perform better than existing accepted plans.
  B. The optimizer always uses the fixed plan, if the fixed plan exists in the plan baseline.
  C. It adds new, bettor plans automatically as fixed plans to the baseline.
  D. The non-accepted plans are automatically accepted and become usable by the optimizer if they perform better than the existing accepted plans.
  E. The non-accepted plans in a SQL plan baseline are automatically evolved, in COMPREHENSIVE mode, during the nightly maintenance window and a persistent verification report is generated.
  A. It automatically performs verification or evolves non-accepted plans, in COMPREHENSIVE mode when they perform better than existing accepted plans.
  D. The non-accepted plans are automatically accepted and become usable by the optimizer if they perform better than the existing accepted plans.
  E. The non-accepted plans in a SQL plan baseline are automatically evolved, in COMPREHENSIVE mode, during the nightly maintenance window and a persistent verification report is generated.

  ---

  With adaptive SQL plan management, DBAs no longer have to manually run the verification or evolve process for non-accepted plans. When automatic SQL tuning is in COMPREHENSIVE mode, it runs a verification or evolve process for all SQL statements that have non-accepted plans during the nightly maintenance window. If the non-accepted plan performs better than the existing accepted plan (or plans) in the SQL plan baseline, then the plan is automatically accepted and becomes usable by the optimizer. After the verification is complete, a persistent report is generated detailing how the non-accepted plan performs compared to the accepted plan performance. Because the evolve process is now an AUTOTASK, DBAs can also schedule their own evolve job at end time.

  Note:

  *

  The optimizer is able to adapt plans on the fly by predetermining multiple subplans for portions of the plan.

  *

  Adaptive plans, introduced in Oracle Database 12c, enable the optimizer to defer the final plan decision for a statement until execution time. The optimizer instruments its chosen plan (the default plan) with statistics collectors so that it can detect at runtime, if its cardinality estimates differ greatly from the actual number of rows seen by the operations in the plan. If there is a significant difference, then the plan or a portion of it will be automatically adapted to avoid suboptimal performance on the first execution of a SQL statement.

• Question 212:

  You are required to migrate your 11.2.0.3 database as a pluggable database (PDB) to a multitenant container database (CDB).

  The following are the possible steps to accomplish this task:

  1.

  Place all the user-defined tablespace in read-only mode on the source database.

  2.

  Upgrade the source database to a 12c version.

  3.

  Create a new PDB in the target container database.

  4.

  Perform a full transportable export on the source database with the VERSION parameter set to 12 using the expdp utility.

  5.

  Copy the associated data files and export the dump file to the desired location in the target database.

  6.

  Invoke the Data Pump import utility on the new PDB database as a user with the DATAPUMP_IMP_FULL_DATABASE role and specify the full transportable import options.

  7.

  Synchronize the PDB on the target container database by using the DBMS_PDS.SYNC_ODB function.

  Identify the correct order of the required steps.

  A. 2, 1, 3, 4, 5, 6
  B. 1, 3, 4, 5, 6, 7
  C. 1, 4, 3, 5, 6, 7
  D. 2, 1, 3, 4, 5, 6, 7
  E. 1, 5, 6, 4, 3, 2
  C. 1, 4, 3, 5, 6, 7

  ---

  1.

  Set user tablespaces in the source database to READ ONLY.

  2.

  From the Oracle Database 11g Release 2 {11.2.0.3) environment, export the metadata and any data residing in administrative tablespaces from the source database using the FULL=Y and TRANSPORTABLE=ALWAYS parameters. Note that the VER$ION=12 parameter is required only when exporting from an Oracle Database llg Release 2 database:

  3.

  Copy the tablespace data files from the source system to the destination system. Note that the log file from the export operation will list the data files required to be moved.

  4.

  Create a COB on the destination system, including a PDB into which you will import the source database.

  5.

  In the Oracle Database 12c environment, connect to the pre-created PDB and import the dump file. The act of importing the dump file will plug the tablespace data files into the destination PDB Oracle White Paper - Upgrading to Oracle Database 12c -August 2013

• Question 213:

  Identify the category of recommendation that can be implemented automatically by the Automatic SQL Tuning Advisor.

  A. creating SQL profiles
  B. restructuring SQL statements
  C. creating invisible indexes
  D. reducing wait events
  E. partitioning a table
  A. creating SQL profiles

  ---

  Reference: https://docs.oracle.com/cd/B28359_01/server.111/b28274/sql_tune.htm#i36217

• Question 214:

  Which statement is true concerning dropping a pluggable database (PDB)?

  A. The PDB must be open in read-only mode.
  B. The PDB must be in mount state.
  C. The PDB must be unplugged.
  D. The PDB data files are always removed from disk.
  E. A dropped PDB can never be plugged back into a multitenant container database (CDB).
  B. The PDB must be in mount state.

  ---

  http://docs.oracle.com/database/121/ADMIN/cdb_plug.htm#ADMIN13658

• Question 215:

  You are connected using SQL* Plus to a multitenant container database (CDB) with SYSDBA privileges and execute the following sequence statements:

  

  What is the result of the last SET CONTAINER statement and why is it so?

  A. It succeeds because the PDB_ADMIN user has the required privileges.
  B. It fails because common users are unable to use the SET CONTAINER statement.
  C. It fails because local users are unable to use the SET CONTAINER statement.
  D. If fails because the SET CONTAINER statement cannot be used with PDB$SEED as the target pluggable database (PDB).
  C. It fails because local users are unable to use the SET CONTAINER statement.

• Question 216:

  Your multitenant container database (CDB) is running in ARCHIVELOG mode.

  Examine this command and its output:

  

  You issue this command in RMAN:

  RMAN>BACKUP PLUGGABLE DATABASE "CDB$ROOT", pdb2_1;

  What is the outcome?

  A. The backup succeeds, but only the SYSTEM and SYSAUX tablespaces in the root container are backed up along with all the data files in PDB2_1.
  B. The backup fails because the root container cannot be backed up with PDB2_1.
  C. The backup succeeds and all the data files belonging to both the root container and PDB2_1 are backed up.
  D. The backup fails because PDB2_1 should be placed in the mount stage.
  C. The backup succeeds and all the data files belonging to both the root container and PDB2_1 are backed up.

• Question 217:

  You are planning the creation of a new multitenant container database (CDB) and want to store the ROOT and SEED container data files in separate directories.

  You plan to create the database using SQL statements.

  Which three techniques can you use to achieve this? (Choose three.)

  A. Use Oracle Managed Files (OMF).
  B. Specify the SEED FILE_NAME_CONVERT clause.
  C. Specify the PDB_FILE_NAME_CONVERT initialization parameter.
  D. Specify the DB_FILE_NAME_CONVERT initialization parameter.
  E. Specify all files names in the CREATE DATABASE statement without using Oracle managed Files (OMF).
  A. Use Oracle Managed Files (OMF).
  B. Specify the SEED FILE_NAME_CONVERT clause.
  C. Specify the PDB_FILE_NAME_CONVERT initialization parameter.

  ---

  You must specify the names and locations of the seed's files in one of the following ways:

  *

  (A) Oracle Managed Files

  *

  (B) The SEED FILE_NAME_CONVERT Clause

  *

  (C) The PDB_FILE_NAME_CONVERT Initialization Parameter