1z0-067 Upgrade Oracle9i/10g/11g OCA to Oracle Database 12c OCP Questions and Answers

assigned to a class with rights to browse all directories and catalogs

assigned to a class with rights to back up or restore Oracle database

OSB encryption for data in transport and on tape

RMAN preauthorization on the host

matching the OS user identity of the Oracle instance associated with the database username

scheduling of the RMAN backup to occur automatically at user-defined intervals

CDB$ROOT, PDB$SEED, and the PDBs are opened in read/write mode

CDB$ROOT is opened in read/write mode, PDB$SEED in read-only mode, and the PDBs in MOUNT state

CDB$ROOT and PDB$SEED are opened in read-only mode, but the PDBs are in closed mode

CDB$ROOT, PDB$SEED, and the PDBs are opened in read-only mode

CDB$ROOT is opened in read/write mode, but PDB$SEED and the PDBs are in closed mode

stored scripts in the recovery catalog

available archived redo log files

backup sets and image copies that are obsolete

backups of tablespaces

backups that are marked obsolete according to the current retention policy

Database operations will be monitored only when they consume a significant amount of resource.

Database operations for all sessions will be monitored.

Database operations will be monitored only if the STATISTICS_LEVEL parameter is set to TYPICAL and CONTROL_MANAGEMENT_PACK_ACCESS is set DIAGNISTIC + TUNING.

Only DML and DDL statements will be monitored for the session.

All subsequent statements in the session will be treated as one database operation and will be monitored.

Each pluggable database (PDB) has its own initialization parameter file.

A PDB can have a private undo tablespace.

Log switches occur only at the container database level.

A PDB can have a private temporary tablespace.

Each PDB has a private control file.

All data files belonging to pdb2_1 are backed up and all archive log files are deleted.

All data files belonging to pdb2_1 are backed up along with the archive log files.

Only the data files belonging to pdb2_ are backed up.

This command gives an error because archive log files can be backed up only when RMAN is connected to the root database.

It will fail because DB_8K_CACHE_SIZE cannot be changed dynamically.

It succeeds only if memory is available from the autotuned components of the SGA.

It will fail because an increase in DB_8K_CACHE_SIZE cannot be accommodated within SGA_TARGET.

It will fail because an increase in DB_8K_CACHE_SIZE cannot be accommodated within SGA_MAX_SIZE.

An unplugged PDB can be plugged into the same or another container database (CDB).

PDB data files are automatically removed from disk.

A PDB must have been opened at least once after creation.

A PDB must be in closed state before it can be unplugged.

A PDB must be in MOUNT state before it can be unplugged.

Visibility of the ORA_ARCHIVE_STATE column is controlled by the row archival visibility session parameter.

The ORA_ARCHIVE_STATE column is updated manually or by a program that can reference activity tracking columns, to indicate that a row is no longer considered active.

The row archival visibility session parameter defaults to all rows.

The ORA_ARCHIVE_STATE column is visible if it is referenced in the select list of a query.

The ORA_ARCHIVE_STATE column is updated automatically by the database based on activity tracking columns, to indicate that a row is no longer considered active.

The unified audit trail contains audit records only from unified audit policies and AUDIT settings

Only the CREATE, ALTER, and DROP statements are audited for all users, including SYS

Unified auditing is enabled only if the AUDIT_TRAIL parameter is set to NONE

The unified audit trail, by default, resides in a read-only table in the AUDSYS schema in the SYSAUX tablespace

It can create only local users in all the PDBs.

It has a common schema for all the PDBs.

It can create common users only when it is logged in to the CDB.

It can create only local users in the CDB.

It can be granted only common roles in the PDBs.

because the threaded architecture requires exiting from sql*pIus and reconnecting with sql*PIus / as sysdba before issuing a startup command

because the threaded architecture requires issuing a new connect / as sysdba from within sql*pIus before issuing a startup command

because the threaded architecture requires authentication using a password file before issuing a startup command

because the threaded architecture requires connecting to the instance via a listener before issuing a startup command

because the threaded architecture requires restarting the listener before issuing a startup command

The impdp operation must be performed by the same user that performed the expdp operation.

The path of data files on the target database must be the same as that on the source database.

The export dump file must be created before starting the import on the target database.

All the user defined tablespaces must be in read-only mode on the source database.

The import operation must be performed by a user on the target database with the DATAPUMP_IMP_FULL_DATABASE role, and the database link must connect to a user on the source database with the DATAPUMP_EXP_FULL_DATABASE role.

The source and target databases must be running on the same platform with the same endianness.

The valid time columns employee_time_start and employee_time_end are automatically created.

The same statement may filter on both transaction time and valid temporal time by using the AS OF TIMESTAMP and PERIOD FOR clauses.

The valid time columns are not populated by the Oracle Server automatically.

The valid time columns are visible by default when the table is described.

Setting the session valid time using DBMS_FLASHBACK_ARCHIVE.ENABLE_AT_VALID_TIME sets the visibility for data manipulation language (DML), data definition language (DDL), and queries performed by the session.

An ASM instance mounts an ASM control file

An ASM instance uses the ASMB process for rebalancing of disks within a disk group

Automatic Memory Management is enabled in an ASM instance even when the MEMORY_TARGET parameters not set explicitly

An RDBMS instance gets connected to an ASM instance using ASMB as a foreground process when the database instance is started

It returns an error because there is no level 0 backup available for new data files.

It performs an image copy backup of new data files, and a level 1 incremental backup of all other data files.

It performs a level-0 backup of all data files including those that belong to the new tablespace.

It performs an image copy backup of all data files including those that belong to the new tablespace.

It performs a backup as a backup set of all data files including those that belong to the new tablespace.

Automatic checkpoint tuning is disabled.

The frequency of log switches is increased.

The overhead on database performance is increased because of frequent writes to disk.

The MTTR advisor is disabled.

The recycle bin should be enabled.

No duplicates of the HR.EMPLOYEES table should exist in the recyclebin of the HR schema.

SCOTT should have the SELECT privilege on the HR schema and its recyclebin.

SCOTT should have the FLASHBACK ANY TABLE privilege.

No other table with the same name should exist in the HR schema.

Undo retention guarantee must be enabled.

because pga_aggregate_target is not set

because statistics_level is set to basic

because memory_target and memory_max_target cannot be equal

because sga_target and memory_target are both set

The data is decrypted during SORT and JOIN operations.

The data remains encrypted when it is read into memory.

The data remains encrypted when it is stored in the redo logs

The data remains encrypted in the UNDO tablespace provided that the UNDO tablespace was created with the encryption option enabled.

Create both jobs by using Scheduler raised events.

Create both jobs using application raised events.

Create one job to rebuild indexes using application raised events and another job to perform bulk load using Scheduler raised events.

Create one job to rebuild indexes using Scheduler raised events and another job to perform bulk load by using events raised by the application.

Restart the database instance to create the temp file automatically

Add a new temp file to the TEMP tablespace with a new name, and then drop the temp files that is corrupted

Take the TEMP tablespace offline, drop the missing temp file, and then create a new temp file

Drop the TEMP tablespace, and then re-create it with new temp files

Fast Recovery Area must be enabled for the database

The EXECUTE privilege must be granted to a user on the DBMS_FLASHBACK package

Undo retention guarantee must be configured for the database

A supplemental log must be enabled for the primary key

Row movement must be enabled

Set the backup_tape_io_slaves parameter to true.

Set the dbwr_io_slaves parameter to a nonzero value if synchronous I/O is in use.

Configure large pool if not already done.

Remove the rate parameter, if specified, in the allocate channel command.

Always use RMAN compression for tape backups rather than the compression provided by media manager.

Always use synchronous I/O for the database.

Database Replay

Automatic Database Diagnostic Monitor (ADDM) Compare Period report

Active Session History (ASH) report

SQL Performance Analyzer

4, 8, 11, 5

1, 3, 8, 11, 9

1, 2, 6, 3, 7, 10, 9

1, 3, 7, 10, 9

1, 2, 6, 3, 8, 11, 9

It is set to/u01/app/oracle/product:/12.1.0/db_1/log.

It is set to /u01/app/oracle/admin/en12.1.0/adump.

It is set to /u01/app/oracle.

It is set to /u01/app/oracle/flash_recovery_area.

The backup succeeds only if the USERS tablespace is locally managed.

RMAN uses multiplexing to perform the backup.

The resulting backupset has backup pieces that cannot exceed 300 MB.

RMAN always performs this type of backup in parallel.

The backup set size is limited to 300 MB.

Compressed backups can only be written to media.

Binary compression creates performance overhead during a backup operation.

Unused blocks below the high-water mark are not backed up.

Compressed backups cannot have section size defined during a backup operation

It works only for locally managed tablespaces.

If no PDB plan is enabled for a pluggable database, the PDB uses the CDB plan.

To enable a resource plan for a PDB, a CDB resource plan must be created and enabled.

If no PDB plan is enabled for a pluggable database, all sessions for that PDB are treated to an equal share of resources.

If a PDB plan is enabled for a pluggable database, Resource Manager uses the resource allocation at the PDB level and ignores the limits set at the CDB level.

If a PDB plan is enabled for a pluggable database, resources are allocated to consumer groups based on the shares provided to the PDB in the CDB plan and the shares provided to the consumer groups in the PDB plan.

A DBA can check specific tables with the DMU

The database to be migrated must be opened read-only.

The release of the database to be converted can be any release since 9.2.0.8.

The DMU can report columns that are too long in the converted characterset

The DMU can report columns that are not represented in the converted characterset

It uses multisection backup.

It uses parallelization for the backup set.

It uses asynchronous I/O for the backup.

It creates compressed backup sets.

The database must be running in archivelog mode.

Flashback Database must be enabled.

Fast Recovery Area must be enabled.

The recyclebin must be enabled for the database.

Undo retention guarantee must be enabled.

A database backup must be taken.

1, 2, 4, 3, and 6

2, 4, 3, and 5

2, 4, and 3

1, 5, 2, 4, 3, and 6

1,2,3,4,5,6,8,9, and 10

1,2, 4,5,6,7, and 8

1, 2, 3, 8, 9, and 10

1, 2, 4, 5, 7, 8, 9, and 10

1, 2, 4, 5, 6, and 7

It lists and catalogs all valid data file copies, backup pieces, and archived logs that exist in all directory paths with the prefix /disk1/backups and their subdirectories.

It lists all the data file copies, backup pieces, and archived logs cataloged in the recovery catalog in the /disk1/backups directory and its subdirectories.

Only valid data file copies, existing in the /disk1/backups directory, are cataloged.

Only valid backup pieces and archived logs, existing in the /disk1/backups directory, are cataloged.