A non-CDB can be cloned into a PDB.

A user with SYSDBA or SYSBKUP must be logged in with RMAN to CDB$ROOT when cloning a PDB.

Only one PDB can be cloned at a time.

Two or more PDBs can be cloned with the same command.

A user with SYSDBA or SYSBKUP must be logged in with RMAN to the non-CDB being cloned when cloning a non-CDB.

The target and auxiliary instance passwords must be the same.

The movement of all segments to a target tablespace with a higher degree of compression, on a different storage tier, when the source tablespace exceeds TBS PERCENT USED

Settingthetargettablespacetoread-only

The movement of some segments to a target tablespace with a higher degree of compression, on a different storage tier, when the source tablespace exceeds TBS PERCENT USED

Setting the target tablespace offline

The movement of some blocks to a target tablespace with a lower degree of compression, on a different storage tier, when the source tablespace exceeds TBS PERCENT USED Correct

If a row lock is held by a nonexistent transaction, the block containing the row is media corrupt.

DB_BLOCK_CHECKING=TRUE causes a check sum to be added to each data block to help detect physical or media corruption.

A media corrupt block is one where the block is not formatted correctly.

The ANALYZE TABLE VALIDATE STRUCTURE CASCADE command verifies that each table row has an index entry pointing to it.

If a row lock is held by a nonexistent transaction, the block containing the row is logically corrupt.

DB_LOST_WRITE_PROTECT=TYPICAL causes extra logging overhead on the standby database.

when free space in a dictionary managed tablespace falls below a specified percentage

when free space in a locally managed tablespace falls below a specified percentage

when the total number of locked user account exceeds a specific value

when the number of logons per second exceeds a specific value

when a resumable statement is suspended

when the total number of logons exceeds a specific value

You can

You can

You can

You can

You can

They can be created only in CDB$ROOT.

They can be only metadata-linked in an application container.

They can exist in user-defined schemas only in application containers.

They can exist in CDB$ROOT and an application root.

They can be extended data-linked in CDB$ROOT. F. They can be created only in an application root.

CDB$ROOT, PDB$SEED, PDB2, PDB1, PDB3, and PDB4

CDB$ROOT, PDB2, PDB1, and PDB3

CDB$ROOT, PDB$SEED, PDB2, PDB1, and PDB3

CDB$ROOT, PDB1, PDB2, PDB3, and PDB4

CDB$ROOT, PDB$SEED, PDB1, PDB3, PDB2, and PDB4

SAL will be added to APP_PDB1.EMP, with 0 in columns of existing rows.

SAL will be added to APP_PDB1.EMP, with NULLs in columns of existing rows.

It will return an error because the SYNC operation is not allowed when constraints are added to common objects.

It will return an error because EMP is not empty in APP_ROOT.

It will return an error because EMP.SAL is empty in APP_ROOT.

The Transparent Data Encryption (TDE) keystore is backed up using RMAN.

Vendor-specific media management software can be used for making encrypted RMAN backups to media.

The BACKUP BACKUPSET command can encrypt and decrypt backup sets.

Image copies can be encrypted.

Keystore-based encryption is the default mode for RMAN backup encryption.

Backup encryption can be enabled selectively for specific tablespaces.

redo logs

control files

all data dictionary metadata

user-defined PL/SQL packages

temporary tablespaces

mandatory Oracle-supplied PL/SQL packages

undo tablespaces

3,4,6

2,3,4,5,6,7

1,3,4,6,8

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

It can be used to patch existing Oracle software installations.

It can be used only on nodes with Oracle Grid Infrastructure installed.

It can be used to create a single-instance Oracle Database in an already-installed Oracle home. D)It can be used to deploy new homes without disrupting active databases.

It can be used to create templates of Oracle homes as gold images of only Oracle databases.

It can be used to upgrade only single-instance databases running on Oracle Restart.

Media Management messages for SBT devices are always written to sbtio.log.

RMAN error stacks should be read from the bottom up as that is the order in which errors are generated.

RMAN error stacks should be read from the top down as that is the order in which errors are generated.

The RMAN LOG command line clause causes output issued during RMAN command compilation to be written to a log file and to standard output.

The RMAN LOG command line clause causes output issued during RMAN command compilation to be written to a log file only.

Media Management messages for SBT devices are written to an Oracle trace file.

Tablespaces always remain in read/write mode during transportable tablespace operations.

Tablespaces never remain in read/write mode during transportable tablespace operations.

A transportable data pump import can leave a plugged-in tablespace in read-only mode.

Simultaneous data pump jobs can be limited at the pluggable database (PDB) level.

A transportable data pump import can leave a plugged-in tablespace in read/write mode.

An ordinary data pump export of a table with encrypted columns will always encrypt the same columns when imported.

The UNDO TABLESPACE clause is always required when no connection exists to the recovery catalog and the TARGET database is closed.

RMAN disk-based backups of the database to be duplicated can be used by the auxiliary instance.

The UNDO TABLESPACE clause is always required when no connection exists to the TARGET instance.

The UNDO TABLESPACE clause is never required.

RMAN "pushes" the backups of the database to be duplicated over the network to the auxiliary instance.

Automatic block repair can repair blocks with no standby database if DB_BLOCK_CHECKING = TRUE.

Real-Time Query must be enabled on a physical standby database for automatic block repair to be done on that physical standby database.

Real-Time Query must be enabled on a primary database for automatic block repair to be done on any of its physical standby databases.

It is not possible for media corrupt blocks.

Real-Time Query must be enabled on a physical standby database for automatic block repair to be done on its primary database.

It is used in both clustered and non-clustered environments.

You can add and remove components from an Oracle Restart configuration with Server Control (SRVCTL) commands.

It runs from the Oracle Grid Infrastructure home.

If you shut down a database instance with SQL*Plus, Oracle Restart interprets this as a database failure and attempts to restart the instance.

The Server Control (SRVCTL) utility can be used to start and stop Oracle Restart.

It can manage Oracle Database instances, Oracle Net Listeners, and Oracle Automatic Storage Management instances.

It succeeds and creates multisection backup sets that are used for active database duplication.

It fails because there is no connection to a recovery catalog.

It succeeds only if the target database is in MOUNT state.

It fails because no parallel channels are allocated for the auxiliary database.

The restore point is a label for the system change number (SCN) that will be saved two years after the archival backup was taken.

The data file backups in the self-contained archive backup are not considered obsolete for two years regardless of the retention policy.

All archive logs created after this backup are kept for two years.

The SPFILE is included in the self-contaied archival backup.

The control file is included in the self-contained archival backup.

The restore point is a label for the system change number (SCN) before the archival backup was taken.

Schema Only accounts can be granted administrator privileges.

If the password file location changes, then the instance must be restarted.

Unified Auditing can be configured to audit only events that are issued directly by an audited user.

All the Oracle-supplied accounts are Schema Only accounts.

Unified Auditing can be configured to audit only events that are issued indirectly by all users

It requires Oracle ASMLib to manage Automatic Storage Management (ASM) disks.

It creates one disk group during installation.

It includes both Oracle Restart and Oracle Automatic Storage Management (ASM) software.

Automatic Storage Management (ASM) requires that O/S groups OSASM and OSDBA be assigned as secondary groups for its installation owner.

It requires Oracle ASM Fitter Driver (ASMFD) to manage Automatic Storage Management (ASM) disks.

It requires the operating system ORACLE_BASE environment variable to be predefined before installation.

to generate an XML metadata file that describes a non-CDB Oracle 12c database so that it can be plugged in as a PDB

to generate an XML metadata file from any unplugged PDB

to determine whether an XML file describes a PDB that can be plugged into the CDB in which you run the procedure

to generate a . pdb archive file for any PDB in the current CDB

to generate an XML metadata file that describes the current plugged-in PDB

The unified audit trail is written to a read-only table.

The unified audit trail is written to a read-only external file.

Audit records are created for COMMIT, ROLLBACK, and SAVEPOINT statements.

Audit records are created for SYS.

Audit records are created for non-sys users.

Data files with a high value in V$BACKUP_ASYNC_IO.SHORT_WAITS are a potential performance bottleneck when asynchronous I/O is used.

If an RMAN BACKUP VALIDATE command takesroughly the same time as an actual backup, then read I/O is a likely bottleneck.F

If an RMAN BACKUP VALIDATE command takes noticeably less time than an actual backup, then write I/O is a likely bottleneck.

If an RMAN BACKUP VALIDATE command takesroughly the same time as an actual backup, then both read and write I/O are likely bottlenecks.

Data files with a high value in V$BACKUP_SYNC_IO.DISCRETE_BYTES_PER_SECOND are a potential performance bottleneck when synchronous I/O is used.

defining primary keys for all tables to speed up all queries

using check constraints to speed up updates

defining foreign keys for all tables to speed up joins

the physical data model

the configuration of storage arrays

A PDB can be plugged into a CDB only if both are of the same Oracle Database release.

An unplugged PDB can be plugged into multiple CDBs simultaneously by sharing data files.

A PDB unplugged from a container database (CDB) can be plugged into a different CDB without altering any of its schemas.

A non-CDB can be converted into a PDB.

A PDB in a remote CDB can be accessed transparently thereby aggregating results from local and remote PDBs.

A PDB created from PDB$SEED must be set to READ WRITE after loading data.

A PDB created from PDB$SEED must be set to READ ONLY after loading data.

using RMAN stored scripts

creating encrypted backups

creating customized reports about a single database's backups

using the REPORT SCHEMA command to list a database's data files and tablespaces at times in the past

using the KEEP FOREVER clause with the BACKUP command

using the REPORT SCHEMA command to list a database's current data files and tablespaces

Data file 24 can be recovered only while connected to PDB2.

Data file 24 can be restored and recovered while connected to CDB$ROOT.

Data file 24 can be restored only while connected to CDB$ROOT.

Data file 24 can be restored only while connected to PDB2.

Data file 24 can be recovered while connected to PDB2.

Data file 24 can be recovered while connected to CDB$ROOT.

PDB1 data files already exist in the correct location.

DBMS_PDB.CHECK_PLUG_COMPATIBILITY must be run in CDB1 before executing the command.

PDB_FILE_NAME_CONVERT must be set before executing the command.

/u01/app/oracle/oradata/pdb1.xml does not contain the current locations of data files for PDB1.

PDB1 must be dropped from CDB1.

when control file metadata for archive log backups or image copies has been overwritten in the target database's control file due to being older than CONTROL_FILE_RECORD_KEEP_TIME

when a new tablespace is added to a registered target database

when a backup of the current control file is created

when control file metadata for data file backups or image copies has been overwritten in the target database's control file due to being older than CONTROL_FILE_RECORD_KEEP_TIME

when the target is first registered

SGA_MIN_SIZE cannot be set for a PDB.

Setting SHARED_POOL_SIZE for a PDB guarantees a minimum amount of Shared Pool memory for that PDB.

Setting SGA_TARGET for a PDB guarantees a minimum amount of SGA memory for that PDB.

The SHARED_POOL_SIZE setting for a PDB can be up to 80% of the SHARED_POOL_SIZE setting of the root container.

Setting DB_CACHE_SIZE for a PDB guarantees a minimum amount of Database Buffer Cache memory for that PDB.

The SGA_TARGET setting for a PDB cannot exceed 50% of the SGA_TARGET value of the root container.

USER1 can connect to CDB1.

USER1 can connect to APP1_ROOT and APP1_PDB1.

USER1 can connect to APP1_ROOT, APP1_ROOT$SEED, and APP1_PDB1.

USER1 is defined in APP1_PDB2. E) USER1 can connect only to APP1_PDB1.

USER1 can connect only to APP1_ROOT.

RMAN can recover tables owned by the SYSTEM user.

RMAN can recover tables owned by the SYS user.

RMAN can recover tables in the SYSTEM tablespace.

RMAN always uses an auxiliary instance.

RMAN can recover a table after a DDL operation has altered the table structure.

RMAN can recover tables in the SYSAUX tablespace.

RMAN can recover tables in a standby database.

the backup retention policy

the backup optimization policy

the DB_CREATE_ONLINE_LOG_DEST_n parameter setting

the archived log deletion policy

the DB_RECOVERY_FILE_DEST parameter setting

using guaranteed UNDO retention

The control file is backed up whenever a new tablespace is created.

The server parameter file (SPFILE) is automatically backed up each time the control file is backed up.

The control file is backed up whenever a new table is created.

The control file is backed up whenever an RMAN backup is successfully recorded in the catalog.

It requires the use of fast recovery area (FRA).

The control file is backed up automatically each time the SPFILE is backed up manually.

an operating system user to own this installation

the Oracle Inventory group oinstall

an operating system account called grid

a group called dba

the installation of Oracle ASMLIB

A proxy PDB must exist in the application root in the local CDB.

PDB3's application root replica must exist in the local CDB.

The HR_ROOT replica must exist in the remote CDB.

A database link must exist in the remote CDB referring to the local CDB.

A proxy PDB must exist in the application root in the remote CDB.

A database link must exist in the local CDB root referring to the remoteCDB.

Updating client scripts with the new Oracle home.

Resetting passwords to enforce case-sensitivity.

Run OPatch commands from the new Oracle home.

Setting threshold values for tablespace alerts.

Migration to unified auditing.

Upgrading user tables that depend on Oracle-maintained abstract data types.

It is integrated with the SQL Access Advisor.

It predicts the impact of system changes on SQL workload response time.

It provides before and after execution statistics for each SQL statement in the analysis task

It offers fine-grained analysis of all the SQL statements in the analysis task as a group.

SQL statements that were originally run concurrently are run concurrently by SPA.