1z0-062 Exam Dumps - Oracle Database 12c: Installation and Administration

Only one window can be open at any given time

Consumer groups are associated with windows

Windows work with job classes to control resource allocation

The database service name must be provided during windows creation

Windows can automatically start job or change resource allocation among jobs for various time periods

Oracle Data Pump export and import operations can be performed to move data across different database releases.

DBMS_DATAPUMP PL/SQL packages can be used independent of Data Pump clients.

A directory object must exist and a user performing an EXPDP or IMPDP operation must have read and write permission on that directory object.

Oracle Data Pump export and import operations can be performed only by users with the SYSDBA privilege.

Oracle Data Pump export operations invoked from the clients that are connected remotely by using a connection string, create Data Pump files on the client file system.

creating a separate central inventory group for the Oracle Database 12c installation

assigning oinstall as the primary group for the oracle user

assigning asmadmin and asmoper as primary groups for the oracle user

creating OS groups associated with the OSBACKUPDBA, OSDGDBA, and OSKMDBA system privileges

assigning asmdba as the secondary group for the oracle user

They are tied to a specific statement or SQL ID.

They instruct the maintenance job to collect missing statistics or perform dynamic sampling to generate a more optimal plan.

They are used to gather only missing statistics.

They are created for a query expression where statistics are missing or the cardinality estimates by the optimizer are incorrect.

They instruct the optimizer to create only column group statistics.

Improve plan accuracy by persisting both compilation and execution statistics in the SYSAUX tablespace.

The partitions can be moved online to new tablespaces.

Global indexes must be rebuilt manually after moving the partitions.

The partitions can be compressed in the same tablespaces.

The partitions can be compressed in the new tablespaces.

Local indexes must be rebuilt manually after moving the partitions.

BACKUP TABLESPACE SYSTEM SECTION SIZE 100M;

BACKUP AS COPY TABLESPACE SYSTEM SECTION SIZE 100M;

BACKUP ARCHIVELOG ALL SECTION SIZE 25M;

BACKUP TABLESPACE "TEMP" SECTION SIZE 10M;

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

BACKUP SPFILE SECTION SIZE 1M;

BACKUP INCREMENTAL LEVEL 0 TABLESPACE SYSAUX SECTION SIZE 100M;

It generates a script to recompile invalid objects post-upgrade.

The preupgrade_fixups.sql script is created to list and describe issues in the source database.

A log file, preupgrade.log, is created that contains the output of the Pre-Upgrade Information tool.

It checks for required tablespaces and if they are not available, creates them automatically.

The preupgrade_fixups.sql script is executed automatically to fix issues in the source database.

The postupgrade_fixups.sql script is created to address issues that can be fixed after a database has been upgraded.

The ADDM requires at least four AWR snapshots for analysis

The ADDM runs after each AWR snapshot is collected automatically by MMON

The results of the ADDM analysis are stored in the Automatic Workload Repository (AWR)

The ADDM analysis provides only diagnostics information but does not provide recommendations

The ADDM calls other advisors if required, but does not provide recommendations about the advisors