1z0-083 Questions and Answers

log writer performance

database writer performance

general operating system health

SQL statements

database instance memory management and sizes

The root password cannot be specified in a response file.

The sudo password must be specified in a response file.

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.

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

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

Decreased use ofstorage to store audit trail rowsin the database.

It improves overall auditing performance.

It guarantees zero-loss auditing.

The audit trail cannot be easily modified because it is read-only.

It automatically audits Recovery Manager (RMAN) events.

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.

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.

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.

Control file backups can be created while connected to the root container.

Archived Redo Log backups can be created while connected to an application root CDB.

Control file backups can be created while connected to a nonroot container.

Online Redo Log backups can be created while connected to the root container.

The BACKUP TABLESPACE command can back up a PDB tablespace even if RMAN is connected to CDB$ROOT.

It is not possible if an archived log is missing.

It is performed automatically after the database is opened; however, blocks requiring recovery are not available until they are recovered.

Setting FAST_START_MTTR_TARGET to a lower value reduces instance recovery time by causing dirty buffers to be written to disk more frequently, thereby reducing the number of I/Os needed during instance recovery.

It is performed by the Recovery Writer (RVWR) background process.

Setting FAST_START_MTTR_TARGET to a higher value reduces instance recovery time by causing The log writer to write more frquently, thereby reducing the number of I/Os needed during instance recovery.

It is performed automatically while the database remains in MOUNT state. Then the database is opened.

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.

when the duplicate ... from active database command contains the section size clause

when you perform active database duplication on a database with flashback disabled

when you specify set encryption before the duplicate ... from active database command

when the number of auxiliary channels allocated is equal to or greater than the number of target channels

when you perform active database duplication on a database that has readonly tablespaces

Open the CDB instance in restricted mode. In CDB$ROOT, drop the UNDO tablespace. Execute ALTER DATABASE LOCAL UNDO ON in each PDB, and then restart the CDB instance.

Open the CDB instance in upgrade mode. In CDB$ROOT, execute ALTER DATABASE LOCAL UNDO ON, and then restart the CDB instance.

Open the CDB instance in upgrade mode. In each PDB, execute ALTER DATABASE LOCAL UNDO ON, create an UNDO tablespace, and then restart the CDB instance.

Open the CDB instance in restricted mode. In CDB$ROOT, execute ALTER DATABASE LOCAL UNDO ON. create an UNDO tablespace in each PDB, and then restart the CDB instance.

Open the CDB in read-only mode. In CDB$ROOT, execute ALTER DATABASE LOCAL UNDO ON, and then change the CDB to read/write mode.

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.

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.

By default, AWR snapshots are taken every 60 minutes.

Its collection level is determined by the value of the STATISTICS_LEVEL database parameter.

By default, AWR snapshots are retained for 7 days.

The taking of AWR snapshots can be disabled.

AWR data is stored in the SYSTEM tablespace.

By default it analyzes a period of time corresponding to the last 4 hours of activity.

When ADDM reports multiple findings, summing all their impacts can yield to more than 100% of DB time

By default it analyzes a period of time corresponding to the last 24 hours of activity.

It runs automatically after each AWR snapshot.

Results are written to the alert log.

the data dictionary in CDB$ROOT

the log writer process (LGWR)

SYSAUX tablespaces

temporary tablespaces

the Process Monitor Process (PMON)

undo tablespaces

It can be created from a non-CDB.

It can contain only one PDB$SEED, which is created when the CDB is created.

It can have local users with the same name in different PDBs.

It can contain only one Application Container seed, which is created when the Application Container is created.

It can be created by cloning an existing CDB.

It can have any number of pluggable databases (PDBs) limited only by space availability.

It contains predefined common roles in both the root and the seed.

It can be used for applications and middleware.

It can be used only for Oracle Grid Infrastructure, including Oracle Restart.

It can be used for both Oracle Database and Oracle Grid Infrastructure, including Oracle Restart.

It can be used for both Oracle Database and Oracle Grid Infrastructure, excluding Oracle Restart.

It can be used only for Oracle Grid Infrastructure, excluding Oracle Restart.

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.

backup retention policy

default backup device type

default section size for backups

default destinations for backups

multiple backup device types for a single backup

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.

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.

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

when any archived log from, before, or after the most recent backup is corrupt.

after losing all copies of the control file

after losing an archived log from after the most recent backup

after losing an archived log from before the most recent backup

after losing the SYSTEM tablespace

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.

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.

After the change, only a common user with the required privilege can create an undo tablespace in CDB&ROOT.

Any new PDB and existing PDBs are automatically configured to use the default undo tablespace in CDB$ROOT.

After the change, only one undo tablespace can exist in CDB$ROOT.

After the change, any user with the required privilege can create an undo tablespace in the PDBs.

Undo tablespaces existing in PDBs must be dropped before the change.

After the change, each existing PDB has to be reopened for the new undo mode to take effect.

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.

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.

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.

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.

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.

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

mounting disk groups

acting as an I/O server to read data file blocks from ASM disks on behalf of database server processes

managing extent allocation for Oracle database segments

managing Allocation Units (AUs) for disk group content

managing space allocation for Oracle ASM files

acting as an I/O server to write data file blocks to ASM disks on behalf of Database Writer processes (DBWn)

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

Create the PDB1 application PDB and synchronize it with HR_ROOT.

Create the PDB1 application PDB and install HR_APP in it.

Create an application seed, and install HR_APP in it.

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

FLASHBACK transaction query requires undo to retrieve all versions of a row that existed between two points in time.

FLASHBACK drop requires that the RECYCLEBIN parameter be set to ON.

FLASHBACK version query requires that the RECYCLEBIN parameter be set to ON.

FLASHBACK DATA ARCHIVE requires undo to store all versions of all rows of a table being tracked.

FLASHBACK drop requires undo to retrieve all versions of a row that existed two points in time.

FLASHBACK version query requires undo to retrieve all versions of a row that existed between two points in time.

It is enabled for all users having SELECT privilege on SH.SALES.

Only successful queries of SH.SALES are written to the audit trail.

It is only enabled for user SH.

Audit records are always stored in an external audit file.

all backups prior to 10th of August

all backups prior to 22nd of August

all backups prior to 20th of August

all backups prior to 24th of August

all backups prior to 17th of August

Using the Data Recovery Advisor LIST FAILURE command always requires that the database for which failures are to be listed is in MOUNT state.

A failure can be closed only when it has been repaired.

Data Recovery Advisor can be used if a database is closed.

The Data Recovery Advisor CHANGE FAILURE command can be used only to change failure priorities.

Data Recovery Advisor can proactively check for failures.

connecting to the target database and a recovery catalog to execute the duplicate command

creating a password file for an auxiliary instance

connecting to an auxiliary instance

matching the database identifier (DBID) of the source database and the duplicate database

creating an SPFILE for the target database

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.

V$SERVICE_EVENT displays wait counts for every wait event for each service even including counts of zero for waits that never occurred.

V$SESSION_WAIT and V$SESSION both contain details of the event on which a non-waiting session last waited.

V$SESSION_WAIT and V$SESSION both contain details of the event on which a waiting session is currently waiting.

V$SESSION_EVENT displays all waits events for those events that have occurred at least once for sessions that have now terminated.

V$SESSION_WAIT_CLASS displays waits broken down by wait class only for terminated sessions.

restore and recover database

flashback transaction

flashback database

flashback table and transaction

flashback table

It is a set of recommendations by the optimizer to change the access methods used.

It is auxiliary information collected by the optimizer for a SQL statement to eliminate estimation error.

It is a set of recommendations by the optimizer to restructure a SQL statement to avoid suboptimal execution plans.

It is auxiliary information collected by the optimizer for a SQL statement to help use better joins orders.

It is a set of recommendations by the optimizer to create new indexes.

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.

The CONTAINERS clause cannot be used in queries on the REVENUE table.

The REVENUE table must be a list-partitioned table.

The MAPTABLE tables defines a logical partition key on a commonly used column for the REVENUE table.

The MAPTABLE table is a metadata-linked table.

A container map exists for the REVENUE table, but is not enabled.

The REVENUE table partitions are not pruned across the PDBs automatically.

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.

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.

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.

The target database control file is synchronized from the recovery catalog with a partial resync at the next backup.

The recovery catalog is synchronized from the target database control file with a full resync at the next backup.

The target database control file is synchronized from the recovery catalog with a full resync at the next backup.

The recovery catalog is synchronized from the target database control file with a partial resync at the next backup.

Use DBCA to create a template from the existing database to contain the database structure with data files and then use the same template to create the database in the new location.

Use Database Configuration Assistant (DBCA) to create a template from the existing database to contain the database structure.

Use DBCA to create a template from the existing database to contain the database structure and then manually copy the data by using Oracle Data Pump.

Create the database by using the CREATE DATABASE . . . command and manually import data by using Data Pump.

V$SESSION_EVENT displays all waits for all past and existing sessions if the wait has occurred at least once for a session.

V$SERVICE_EVENT displays all waits for all services if the wait has occurred at least once for a service.

V$SESSION_WAIT _CLASS displays waits broken down by wait class only for waiting sessions.

V$SESSION_WAIT and V$SESSION both contain details of the event on which a non-waiting session last waited.

V$SESSION_EVENT displays all waits for all past sessions if the wait has occurred at least once for a session.

V$SESSION_WAIT and V$SESSION both contain details of the event on which a session is currently waiting.

The number of table rows is considered when evaluating the cost of accessing a table using an index.

Index balanced B*Tree height is considered when evaluating the cost of using an index.

The Statistics Advisor can help recommend the best way to gather statistics.

Statistics collected using DBMS_STATS always yield the best optimizer result.

The Statistics Advisor generates actions for all recommendations.

Tablespaces from different PDBs with identical names must be backed up by connecting RMAN separately to each PDB to back up the tablespaces.

The BACKUP DATABASE command will create a pluggable database (PDB) backup when RMAN is connected to a PDB.

SPFILE backups can be created while connected to an application root PDB.

The BACKUP DATABASE PLUS ARCHIVE LOG command will back up archive logs when RMAN is connected to a PDB.

The BACKUP PLUGGABLE DATABASE command can be used to back up CDB$ROOT.

Enable Memory Access Mode, which reads performance data from SGA.

Use emergency monitoring to fetch data directly from SGA for analysis.

Run Automatic Database Diagnostic Monitor (ADDM) to fetch information from the latest Automatic Workload Repository (AWR) snapshots.

Use Active Session History (ASH) data and hang analysis in regular performance monitoring,

Run ADDM in diagnostic mode.

It can recommend semantic changes to SQL statements.

It prevents performance regressions for SQL statements when changes are made.

It checks each query being analyzed for missing or stale statistics.

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

It only recommends syntactic changes to SQL statements.

PDB1_C2_SRV will be created but not started.

PDB1 will be created in CDB2 and automatically opened.

PDB1_C1_SRV in CDB1 will be renamed PDB1_C2_SRV.

PDB1 will be created in CDB2 and left in MOUNT state.

PDB1_C2_SRV will be created and started automatically.

Backups must be done incrementally.

Backups must be contained in backup sets.

Backups can be taken only if the database is in ARCHIVE LOG mode.

Backups can be done incrementally.

The database must be registered in an RMAN catalog.

Only consistent backups can be created.

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

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.

It is not supported for image copies.

It is only supported for backups to tape via the media management interface.

Duplex backups can be performed on either disk or media, but cannot be performed on media and disk simultaneously.

Duplex backups can contain only data files and control files.

For performing duplexed backups, the parallelism for the device must be set equal to the number of copies.

Backing up a database in NOARCHIVELOG mode using O/S utilities requires that the database instance be started and the databased be in the MOUNT state.

Backing up a database in ARCHIVE LOG mode using O/S utilities requires that the database instance be started and the database be in MOUNT state.

An Oracle database can be restored from backup files copied using O/S utilities.

Oracle data file backups, copied using an O/S utility, can be added to the RMAN catalog as IMAGE COPIES.

Backing up a database in NOARCHIVELOG mode using O/S utilities requires that the database instance be shut down.

Oracle archive log backups, copied using an O/S utility, can be added to the RMAN catalog as a backup set.

Backing up a database in ARCHIVE LOG mode using O/S utilities requires that the database instance be started and the database be in OPEN state.

2,4,5,6

1,2,3,4,5,6

1,2,4,5

2,4,5

1,3,4,5

A direct upgrade can be performed only from the immediately preceding Oracle Grid Infrastructure version.

The newer version is installed in a separate Oracle Grid Infrastructure home on the same server as the existing version.

An existing Oracle base can be used.

The upgrade process will automatically install all mandatory patches for the current version of Oracle Grid Infrastructure.

Existing Oracle Database instances must be shut down before starting the upgrade.

Only the grid user can perform the upgrade.

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.

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.

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.

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

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

after losing all members of an INACTIVE online redo log group

after losing a SYSAUX tablespace data file

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

If Automatic Memory Management is enabled, no memory advisors are available.

If Automatic Memory Management is enabled, the Shared Pool Advisor and Buffer Cache Advisor are available to set the maximum size for these individual System Global Area components.

All memory advisors use data from Automatic Workload Repository.

If Automatic Shared Memory Management is enabled, both the SGA Advisor and PGA Advisor are always available.

If Manual Shared Memory Management is enabled, only the Shared Pool Advisor and Buffer Cache Advisor are available.

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

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.

The statistics_level parameter is set to all when any of the PDBs is reopened.

The statistics_level parameter is set to all only for PDB2 when it is reopened.

The statistics_level parameter is set to all when the root database is restarted.

The statement is ignored because there is no SPFILE for a PDB.

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.

The inserts on USER1.EMP remain uncommitted when the session connected to PDB2.

The inserts on USER1.EMP were committed when the session inserted a row into USER2. DEPT.

The insert on USER2.DEPT fails because of the active transaction in the parent container.

The insert on USER2.DEPT is a recursive autonomous transaction by the child session and is committed.

The inserts on USER1.EMP were rolled back when the session connected to PDB2

The insert on USER2.DEPT is uncommitted.

The inserts on USER1.EMP were committed when the session connected to PDB2.

user-managed backups of data files and control files

flashback logs

RMAN backups that are obsolete

archived redo log files that have multiple copies in a different archive location

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 analyzes a period of time corresponding to the 12 hours of activity.

It runs automatically after each AWR snapshot.

A DBA can run it manually.

Results are written to the alert log.

It analyzes a period of time corresponding to the last day of activity.