1z0-083 Exam Dumps - Oracle Database Administration II

A lost PFILE can be re-created from alert.log using SQL*PLUS.

A lost index tablespace can be re-created without performing any recovery.

A lost password file can be manually re-created with the orapwd utility.

A lost password file can be re-created with SQL*PLUS.

A lost SPFILE can be recovered from memory using SQL*PLUS.

A lost TEMPFILE must always be re-created manually.

All audit data is written to both the traditional locations and to the unified location.

The audit trail is in a single format.

Pre 12c audit data is written to the traditional locations and new 12c audit data is written to the unified location.

The audit trail is read-only.

The audit trail uses less space.

If the password file location changes, then the new location is used automatically by the Oracle Server.

Schema Only accounts can be granted administrator privileges.

All the Oracle-supplied accounts are Schema Only accounts.

Privilege Analysisisincluded in Oracle Enterprise Edition and no longer requires Database Vault. E) Unified Auditing can be configured to audit only events that are issued indirectly by an audited user.

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

RMAN must be connected to the target database instance and the auxiliary instance.

A most recent backup set of the PROD database must exist.

Flashback must be enabled for the PROD database.

The target database must be in MOUNT state.

It can only be launched from the command line interface.

It can be launched from both the command line and the Universal Installer (OUI) interfaces.

It can be used to create container databases and non-container databases.

It can be used to change the character set of an existing database.

It can be used to convert a non-container database to a container database.

Create an application seed, synchronize it with HR_ROOT, and then create the PDB1 application PDB.

Create the PDB1 application PDB and synchronize it with HR_ROOT.

Create the PDB1 application PDB and install HR_APP in it.

Create the PDB1 application PDB and synchronize it with PDB$SEED.

Create an application seed, and install HR_APP in it.

Two or more PDBs can be duplicated with the same RMAN DUPLICATE command.

All tablespaces belonging to a PDB must be duplicated when duplicating the PDB.

The auxiliary instance is automatically created with ENABLE_PLUGGABLE_DATABASE = TRUE.

A user with SYSDBA or SYSBACKUP must be logged in with RMAN to the PDB to duplicate it.

CDB$ROOT and PDB$SEED are automatically duplicated.

by performing emergency monitoring using Real-Time Automatic Database Diagnostic Monitor (ADDM) to fetch data directly from SGA for analysis

by running ADDM to fetch information from the latest Automatic Workload Repository (AWR) snapshots

by using Active Session History (ASH) data and performing hang analysis

by running ADDM in diagnostic mode

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.

The base catalog owner must give the Virtual Private Catalog access to metadata for one or more PDBs.

The target PDB must be registered in both the base catalog and the Virtual Private Catalog.

The base catalog must be used by RMAN when performing point-in-time recovery for the PDB registered in the Virtual Private Catalog.

The base catalog must be enabled for Virtual Private Catalog use.

The target PDB must be registered in a Virtual Private Catalog.

The target PDB must be registered in a base catalog.

The four sections must be image copies.

Each of the file sections must be processed serially.

The four sections must be contained in backup sets.

The four sections can be created in parallel.

The four sections can be created serially.

RMAN can always repair corrupt blocks.

Flashback commands help with repairing physical errors.

The ADR can store metadata in an Oracle Database repository.

The Automatic Diagnostic Repository (ADR) has a separate home directory for each instance of each Oracle product that is installed and uses it.

The ADR command-line utility (ADRCI) can package incident information to send to Oracle Support.

The Data Recovery Advisor uses the ADR.

APP1_USER1can be created in PDB1.

APP1_USER1can be created in CDB1.

APP1_USER1 can have different privileges in each Application PDB contained in APP1_ROOT.

C##_APP_USER1 can be created in CDB1.

P1_USER1can be created in CDB1.

C##_USER1will have the same privileges and roles granted in all PDBs in CDB1.

Plugging the application root into a different CDB plugs in all its application PDBs.

The application root of an application container should be plugged into the other CDB before its application PDBs are plugged in.

Application PDBs in the application container must be unplugged before the application root is unplugged.

Unplugging the application root from a CDB unplugs all its application PDBs.

It requires only local UNDO mode in the database where the application container will be unplugged.

It requires local UNDO mode in both container databases.

They are generated if STATISTICS_LEVEL is set to TYPICAL.

They are always created manually.

They are always created automatically.

They are generated if STATISTICS_LEVEL is set to BASIC.

They are generated if STATISTICS_LEVEL is set to ALL.

They can be retained forever.

A table's constraints must be disabled before issuing the flashback.

The FLASHBACK ANY TABLE system privilege or the FLASHBACK object privilege must be granted to the user performing the flashback.

Row Movement must be enabled on the table being flashed back.

A table's indexes must be set to unusable before issuing the flashback.

The FLASHBACK ANY TABLE system privilege or the FLASHBACK object privilege must be granted to the table owner.

RMAN encryption keys are stored in a database keystore.

RMAN can encrypt the Oracle Database password file.

Dual-mode encrypted backups can be restored only if both the password and the keystore used for encryption are available.

The SET ENCRYPTION command overrides encryption settings specified by the CONFIGURE ENCRYPTION command.

Password encryption can be persistently configured using the CONFIGURE ENCRYPTION command.

to switch to a patched Oracle Database home

to upgrade an Oracle Database on the centralized Rapid Home Provisioning server

to move an Oracle Database to the centralized Rapid Home Provisioning server

to switch back to the previous Oracle home as part of a rollback operation

to switch to a read-only Oracle home

Flashback logs are not archived.

Flashback logs are maintained in redo log files.

Flashback logs are maintained in the Flash Recovery Area.

Flashback logs are used to maintain Flashback Database related errors.

Flashback logs need to be cleared manually after you disable Flashback Database.

Any Recovery Manager (RMAN) recovery catalog must be upgraded manually.

After a manual upgrade, TNSNAMES.ORA entries must be updated to reflect the new ORACLE_HOME.

Time zone files must be upgraded manually using the DBMS_DST PL/SQL package.

The new extended data type capability must be enabled by running the utlrp.sql script

The Oracle Application Express configuration should be updated after upgrading Oracle Database.

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

oracle will be an owner of the Oracle Inventory.

oracle must be the owner of every Oracle Database installation.

oracle can own an Oracle Database installation but not an Oracle Grid Infrastructure installation.

oracle will be granted the SYSASM privilege when installing the Oracle Database software.

The user account, oracle, and group, oinstall, can be used for all Oracle software installations.

Re-enableredactionpoliciesthatuseFULLdataredaction.

Re-createredactionpoliciesthatuseFULLdataredaction.

Re-connect the sessions that access objects with redaction policies defined on them.

Flushthesharedpool.

Restart the database instance. Correct

All the triggers associated with the table are flashed back but are disabled.

Materialized views that use the CUSTOMERS table are flashed back.

LOB segments associated with the CUSTOMERS table are flashed back.

All the constraints defined on the table, except the referential integrity constraints, are flashed back.

Only the primary key constraint created for the table is flashed back, whereas all other indexes must be retrieved separately.

They can view data from any data dictionary view or dynamic performance view.

They can drop any tablespace.

They can view data from any user-defined tables.

They can create any table.

They cannot create restore points.

They cannot drop tablespaces.

They can be gathered by the DBMS_STATE package.

They are ignored by Optimizer if they are state.

They are gathered by the SQL Tuning Advisor.

By default, they are automatically gathered by a maintenance job.

They provide real-time data about schema objects.

Run the SQL Access Advisor.

Run the Memory Advisor for the shared pool.

Run the SQL Tunning Advisor.

Run the Memory Advisor for the Program Global Area.

Run the Memory Advisor for the System Global Area.

Execute FLASHBACK PLUGGABLE DATABASE PDB1 TO RESTORE POINT R1by using RMAN while connected to PDB1.

Execute FLASHBACK PLUGGABLE DATABASE PDB1 TO RESTORE POINT R1by using SQL while connected to PDB1.

Execute FLASHBACK PLUGGABLE DATABASE PDB1 TO RESTORE POINT R1by using SQL while connected to CDB$ROOT.

Execute FLASHBACK PLUGGABLE DATABASE PDB1 TO RESTORE POINT R1by using RMAN while connected to CDB$ROOT.

This cannot be done due to the lack of a clean restore point.

DataisredactedfortheEMP.SALcolumnonlyiftheSCOTTsessiondoesnothavetheMGR role set.

DataisredactedforEMP.SALcolumnonlyiftheSCOTTsessionhastheMGRroleset.

Data is never redacted for the EMP_VW.SAL column.

Data is redacted for the EMP_V.SAL column only if the SCOTT session has the MGR role set.

Data is redacted for the EMP_V.SAL column only if the SCOTT session does not have the MGR role set. Correct

A DBA must specify either a redundancy retention policy or a recovery window retention policy. B)A target database's persistent RMAN configuration settings are always synchronized automatically with the RMAN catalog.

Backups older than the recovery window retention policy are always deleted automatically if the backup location has insufficient space.

Backups written to the fast recovery area (FRA) that are obsolete based on the redundancy retention policy can be deleted automatically to free space.

A target database's persistent RMAN configuration settings are always stored in the target's control file.

It can be used to deploy Grid Infrastructure homes, including Oracle Restart.

It can be used to deploy Oracle Database homes.

It is an Oracle Database service.

It cannot be used to provision applications.

It cannot be used to provision middleware.

It is an Oracle Grid Infrastructure service.

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.

orainstRoot.sh can be executed automatically by the Database installer by using sudo or root credentials.

root.sh can be executed automatically by the Database Installer only if it is provided with root credentials.

The sudo password can be specified in a response file.

root.sh can be executed automatically by the Database installer only by using sudo credentials.

The sudo password must be specified in a response file.

The root password cannot be specified in a response file.

Assign the appropriate operating system groups to SYSBACKUP, SYSDG, SYSKM.

Grant SYSBACKUP, SYSDG, and SYSKM privileges to the intended users.

Re-create the password file with SYSBACKUP, SYSDG, and SYSKM privilege and the FORCE argument set to No.

Re-create the password file with SYSBACKUP, SYSDG, and SYSKM privilege, and FORCE arguments set to Yes.

Re-createthepasswordfileintheOracleDatabase12cformat. Correct

Data Pump full database export and import

cloning the non-CDB as a PDB

replication using GoldenGate

Data Pump transportable tablespaces

Data Pump full transportable database

the DBMS_PDB package

A backup piece can belong to only one backup set.

A data file can be split into multiple sections stored in different backup sets.

A data file can be split into multiple sections stored in different backup pieces in the same backup set.

Blocks from multiple data files can be contained in one backup piece,

A backup set can contain only one backup piece.

A backup set must be written to media.

A backup set must be written to disk.

An application root clone gets created automatically.

The upgrade can be performed when connected either to CDB$ROOT or to PDB$SEED.

After an application upgrade, the application container's PDBs remain synchronized with the existing application root.

The upgrade must be performed when connected to CDB$ROOT.

An application name and version number must be specified to upgrade the application.

After an application upgrade, the application container's PDBs are automatically synchronized with the application root clone.

The runfixup.sh script can install missing RPMs.

The Oracle Preinstallation RPM must be used to configure the Oracle database installation owner, the Oracle Inventory group, and an Oracle administrative privileges group

It allows you to select the languages supported by the Oracle database server.

It can be done before installing Grid Infrastructure for a Standalone Server

The Oracle Preinstallation RPM can be used to configure the Oracle database installation owner, the Oracle Inventory group, and an Oracle administrative privileges group

It can be done after installing Grid Infrastructure for a Standalone Server.

The Oracle database administrator must be granted access to the root operating system account to run root privileged scripts.

poorly trained users who do not commit transactions

the number of tablespaces containing tables updated by a transaction

issuing multiple savepoints during a transaction

the number of data files containing extents belonging to tables updated by a transaction

poorly written SQL

SBT tape compression can be used even if no RMAN compression is configured.

Any backup set written to the SBT device in this configuration can contain a maximum of two backup pieces.

Any backup written to the SBT device in this configuration can contain a maximum of two backup sets.

SBT tape compression and RMAN backup compression should be used in parallel.

The SBT device should be configured to use PARALLELISM 2 to allow both tape drive to be used simultaneously.

It has the same common users defined as does CDB1.

It has only local roles.

It has the same number of roles as CDB1.

Service PDB1 is created for remote logins to PDB1.

It is in mount state after creation.

It has no local users.

to allow database duplication without a connection to the target instance.

to store backup metadata that would cause the controlfile to become too large.

to store backups that would cause the controlfile to become too large.

to report on the database schema at an earlier point in time.

to allow database duplication without a connection to the auxiliary instance.

It succeeds and needs to be enabled to capture all SQL statements that require either the specified privileges or any privilege granted to the HR_ADMIN or OE_ADMIN role.

It fails because the command does notspecify when the unified audit policy should be enforced.

It succeeds and starts capturing only successful SQL statements for all users who have either the specified privileges or roles granted to them.

It fails because system privileges cannot be granted with roles in the same audit policy.

It recompiles all stored PL/SQL code by using utlrp.sql.

It empties the RECYCLE BIN.

It performs prerequisite checks to verify if the Oracle database is ready for upgrade.

It sets all user tablespaces to “read-only” before starting the upgrade.

It removes the AUDSYS schema and the AUDIT_ADMIN and AUDIT_VIEWER roles

It increases tablespace size, if required, to meet upgrade requirements.

To use it, Flashback Database must be enabled.

A block being recovered is not accessible.

It cannot repair logical corruption.

It can be performed on noncorrupt blocks.

The target database for which one or more blocks are to be recovered must be in the OPEN state.

The data file containing the block being recovered remains online.

V$SESSION_EVENT

V$SESSTAT

V$SESSION_WAIT

V$SESSION_WAIT_CLASS

V$SESSION

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.

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.

All files in any previous FRA that have not yet been backed up, are backed up.

All files in the current fast recovery area (FRA) that have not yet been backed up, are backed up. C)All files in the current FRA that have been backed up already, are backed up.

All Oracle recovery files normally written to the FRA and which have been backed up already to the current FRA, are backed up.

All files in any previous FRA that have been backed up already, are backed up.

All Oracle recovery files normally written to the FRA and which have not yet been backed, are backed up.

All Oracle recovery files normally written to the FRA and which have been backed up already to in any previous FRA, are backed up.

It will return an error because creation of a local role is not allowed in CDB$ROOT.

ROLE1 will be created only in CDB$ROOT.

It will return an error because common roles must start with C##.

ROLE1 will be created only in CDB$ROOT and APP1_ROOT.

ROLE1 will be created in CDB$ROOT, PDB1, APP1_ROOT, and APP1_PDB1.

It will create a multitenant container database (CDB) with only the root opened.

ItwillcreateaCDBwithrootopenedandseedreadonly.

It will create a CDB with root and seed opened and one PDB mounted.

It will create a CDB that must be plugged into an existing CDB.

ItwillcreateaCDBwithrootopenedandseedmounted.

A PDB snapshot depends on an existing storage snapshot of the source PDB.

APDB snapshot can be a full copy of a source PDB.

A PDB snapshot can be a sparse copy of a source PDB

A snapshot copy PDB does not depend on an existing storage snapshot of the source PDB.

A snapshot copy PDB can be a full copy of a source PDB

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.

using Database Replay

using SQL Developer

using Oracle Data Pump

using operating system file copy utilities

using Database Upgrade Assistant

using the CREATE TABLE AS SELECT SQL statement

FULL redaction is active on the SAL column

RANDOM redaction is active on the MGR column

RANDOM redaction is active on the HIREDATE column

PARTIAL redaction is active on the MGR column.

PARTIAL redaction is active of the HIREDATE column.

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.

Transparent encryption of backups uses an encryption wallet.

Image copy backups can be created by using password encryption.

A password encryption of backups uses the password while creating and restoring backups.

Encrypted backups can only be written to disk.

A database uses the same encryption key for every encrypted backup.

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

It facilitates and helps to enforce keystore backup requirements.

It handles encrypted data without modifying applications.

It enables a keystore to be stored only in a file on a file system.

It enables separation of duties between the database administrator and the security administrator.

It transparently decrypts data for the database users and applications that access this data.

It helps to track encryption keys and implement requirements such as keystore password rotation and master encryption key reset or re-key operations.

They can only be written to disk.

They can be encrypted using Transparent Data Encryption (TDE).

They can be used as a level 0 incremental backup.

They can be used as a level 1 incremental backup.

They are the only backup option available for databases in NOARCHIVELOG mode.

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

FLASHBACK QUERY can retrieve REDO records from ONLINE and ARCHIVE D REDO LOG files.

FLASHBACK VERSION QUERY can retrieve REDO records from ONLINE and ARCHIVE D REDO LOG files.

FLASHBACK TABLE can undrop a column.

FLASHBACK DROP can undrop an index when undropping a table.

After a database is restored from flashback logs using the FLASHBACK DATABASE command, it is sometimes rolled forward using redo logs.

The ORCL database, the Oracle ASM instances, the +DATA and +FRA disk groups, and the LISTENER are started.

Only the ORCL database instance is started.

Only the ORCL database and the ASM instances are started.

Only the ORCL database instance, the Oracle ASM instance, and the +DATA and +FRA disk groups are started.

Only the ORCL database instance and the +DATA and +FRA disk groups are started.

SQL statements performing many physical I/Os can always have their performance improved by creating indexes.

The solution that best optimizes one SQL statement can degrade the performance of others.

SQL statements doing joins always do more physical I/O than single table queries.

Poorly performing SQL statements can be tuned automatically by the Oracle server.

SQL statements doing only logical reads never require tuning because they do no physical I/O.

automatically dropping the database link to the remote database if it already exists

opening the cloned PDB

creating a new empty PDB in the local database from PDB$SEED

creating a database link from CDB$ROOT in the local database to CDB$ROOT in the remote system that is to be cloned

creating a database link from CDB$ROOT in the remote database to be cloned to CDB$ROOT in the local database

creating a database link from CDB$ROOT in the local database to the PDB in the remote system that is to be cloned

creating a database link from CDB$ROOT in the remote database to the PDB in the local database

The root and the seed database in the container database (CDB) are also duplicated.

A backup of PDB1 and PDB5 must exist before executing the command.

The SPFILE is copied along with the data files of the pluggable databases (PDBs).

An auxiliary instance must be started with the initialization parameter ENABLE_PLUGGABLE_DATABASE set to TRUE. E) The DUPLICATE command first creates a backup, and then duplicates the

PDBs by using the backup.

Tablespaces are automatically created as need while importing full exports in either a non-CDB or a PDB.

Oracle attempts to convert conventional database users to local users when moving schemas from a non-CDB to a PDB.

A new PDB is automatically created when importing a non-CDB into a CDB.

Oracle attempts to convert common users to conventional users when moving schemas from a PDB to a non-CDB.

Moving data from a PDB to a non-CDB is only possible by using transportable tablespace export and import.

Moving data from a non-CDB to a PDB is only possible by using conventional export and import.

All historical data older than two years, if any, is purged from the flashback archive FDA1.

An error is returned because the retention period cannot be reduced.

All the flashback data archives are purged and the subsequently created flashback archives are maintained for two years

All historical data older than two years, if any, is archived to flashback logs and the flashback archive is set to new retention time.

It succeeds.

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

It fails because connection to the AUXILIARY instance must be as SYSDBA.

Itsucceeds only if the target database is greater than 400M.

No catalogued backup of the TARGET is used to duplicate the database.

It requires installation of Oracle Universal Installer.

It supports Rolling Patching.

It must be invoked as the user that owns the software being patched.

It is a Java-based utility for applying patchsets.

It is platform independent.

It can be used to apply interim patches to the Grid Infrastructure and Database Home combination.

It creates a binary backup of the control file.

It updates the alert log with the location and contents of the control file

It creates a file that contains SQL statements to re-create the control file.

It creates a file that contains RMAN scripts to create a duplicate database.

It creates a copy of the control file in the fast recovery area (FRA).

DBUA must be launched from the target Oracle Home.

Multiple databases with the same ORACLE_HOME can be upgraded simultaneously.

A whole database backup must exist before upgrade.

The Pre-Upgrade Information Tool script is executed by DBUA.

All pluggable databases are automatically upgraded as part of a container database upgrade.

The database must be opened in read-only mode.

Stateful alerts must be created by a DBA after resolving the problem.

Stateless alerts can be purged manually from the alert history.

Stateless alerts can be cleared manually.

Stateless alerts are automatically cleared.

Stateful alerts are purged automatically from the alert history

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.

Reduced logical I/O

Reduced virtual memory utilization

Improved Serial Execution performance

Reduced physical I/O

Reduced CPU utilization

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;

after losing a SYSAUX tablespace data file

after losing all members of an INACTIVE online redo log group

after losing all members of the CURRENT online redo log group

after losing all copies of the control file

after losing an UNDO tablespace that is in use

The target database must be open

The duplication process can use existing backup sets or image copies

The duplication process can use existing backup sets or image copies.

The target database must be in mount state.

The duplication -process pushes backup sets to the auxiliary instance.

The duplication process pushes image copies to the auxiliary instance.

to specify a default tablespace in a PDB cloned from another PDB in the same CDB

to exclude all tablespaces except SYSTEM, SYSAUX, and TEMP when plugging in a PDB

to include specific user tablespaces only when relocating a PDB

to specify the list of user tablespaces to include when moving a non-CDB to a PDB

to exclude a temp tablespace when plugging in a PDB

to specify the list of tablespaces to include when creating a PDB from the CDB seed

to switch an existing Oracle Database home to a newer release of Oracle software on the same server

to switch to a read-only Oracle home

to switch back to the previous Oracle home as part of a rollback operation

to switch the Oracle Database home when using a centralized Rapid Home Provisioning server

to switch to a patched Oracle Database home Answer: CE

Create SQL plan directives for each of the regressed statements.

Use The SQL Tuning Advisor for each of the regressed statements.

Create an adaptive execution plan for each of the regressed statements

Use the SQL Access Advisor for each of the regressed statements.

It checks each query being analyzed for stale statistics.

It checks each query being analyzed for missing statistics.

It only recommends syntactic changes to SQL statements.

It can recommend semantic changes to SQL statements.

It considers all SQL statements being analyzed by the advisor task as a group.

It builds SQL profiles for each poorly performing SQL statement to prevent regressions.