Free Oracle 1Z0-062 Exam Questions (page: 3)

Examine the following query output:

You issue the following command to import tables into the hr schema:
$ > impdp hr/hr directory = dumpdir dumpfile = hr_new.dmp schemas=hr TRANSFORM=DISABLE_ARCHIVE_LOGGING: Y
Which statement is true?

  1. All database operations performed by the impdp command are logged.
  2. Only CREATE INDEX and CREATE TABLE statements generated by the import are logged.
  3. Only CREATE TABLE and ALTER TABLE statements generated by the import are logged.
  4. None of the operations against the master table used by Oracle Data Pump to coordinate its activities are logged.

Answer(s): C

Explanation:

Oracle Data Pump disable redo logging when loading data into tables and when creating indexes.
The new TRANSFORM option introduced in data pumps import provides the flexibility to turn off the redo generation for the objects during the course of import. The Master Table is used to track the detailed progress information of a Data Pump job. The Master Table is created in the schema of the current user running the Pump Dump export or import, and it keeps tracks of lots of detailed information.



You plan to create a database by using the Database Configuration Assistant (DBCA), with the following specifications:
­ Applications will connect to the database via a middle tier.
­ The number of concurrent user connections will be high.
­ The database will have mixed workload, with the execution of complex BI queries scheduled at night.
Which DBCA option must you choose to create the database?

  1. a General Purpose database template with default memory allocation
  2. a Data Warehouse database template, with the dedicated server mode option and AMM enabled
  3. a General Purpose database template, with the shared server mode option and Automatic Memory Management (AMM) enabled
  4. a default database configuration

Answer(s): C


Reference:

http://www.oracledistilled.com/oracle-database/administration/creating-a- database-using-database-configuration-assistant/



What is the effect of specifying the "ENABLE PLUGGABLE DATABASE" clause in a "CREATE DATABASE" statement?

  1. It will create a multitenant container database (CDB) with only the root opened.
  2. It will create a CDB with root opened and seed read only.
  3. It will create a CDB with root and seed opened and one PDB mounted.
  4. It will create a CDB that must be plugged into an existing CDB.
  5. It will create a CDB with root opened and seed mounted.

Answer(s): B

Explanation:

* The CREATE DATABASE ... ENABLE PLUGGABLE DATABASE SQL statement creates a new CDB. If you do not specify the ENABLE PLUGGABLE DATABASE clause, then the newly created database is a non-CDB and can never contain PDBs. Along with the root (CDB$ROOT), Oracle Database automatically creates a seed PDB (PDB$SEED). The following graphic shows a newly created CDB:

* Creating a PDB
Rather than constructing the data dictionary tables that define an empty PDB from scratch, and then populating its Obj$ and Dependency$ tables, the empty PDB is created when the CDB is created. (Here, we use empty to mean containing no customer-created artifacts.) It is referred to as the seed PDB and has the name PDB$Seed. Every CDB non-negotiably contains a seed PDB; it is non-negotiably always open in read-only mode. This has no conceptual significance; rather, it is just an optimization device. The create PDB operation is implemented as a special case of the clone PDB operation.



Which three statements are true about adaptive SQL plan management? (Choose three.)

  1. It automatically performs verification or evolves non-accepted plans, in COMPREHENSIVE mode when they perform better than existing accepted plans.
  2. The optimizer always uses the fixed plan, if the fixed plan exists in the plan baseline.
  3. It adds new, bettor plans automatically as fixed plans to the baseline.
  4. The non-accepted plans are automatically accepted and become usable by the optimizer if they perform better than the existing accepted plans.
  5. 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.

Answer(s): A,D,E

Explanation:

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.






Post your Comments and Discuss Oracle 1Z0-062 exam prep with other Community members:

1Z0-062 Exam Discussions & Posts