1z0-083 Practice Exam Questions with Answers Oracle Database Administration II Certification

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.

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.

The password for the encryption must be set up.

Oracle wallet for the encryption must be set up.

All the tablespaces in the database must be encrypted

Oracle Database Vault must be enabled.

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.

OSASM

OSRACDBA

OSKMDBA

OSDBA

E?OSOPER

SPFILE backup duplexing

control file auto backup formats

archive log deletion policy

image copy duplexing

redo log backup duplexing

archive log backup duplexing

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

Virtual Private Database (VPD) policies on objects in an application root are automatically synchronized with all application PDBs contained in the application container.

Application-common TSDP policies are always container specific.

Application-common Transparent Security Data Protection (TSDP) policies can be created only within an application install/patch BEGIN-END block.

Application-common Oracle Label Security (OLS) policies cannot be created in an application root outside an install/patch BEGIN-END block.

Fine-grained auditing (FGA) policies in an application root are automatically synchronized to all application PDBs contained in the application container.

Application-common OLS policies can be created in an application root inside an install/patch BEGIN¬END block.

Unified auditing can be automatically synchronized to all application PDBs in an application container.

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

Online Redo Log backups can be created while connected to CDB$ROOT

Control file backups can be created while connected to CDB$ROOT.

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

Archived Redo Log backups can be created while connected to PDB

Control file backups can not be created while connected to a PDB

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

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

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

CDB1 and CDB2 must be in shared undo mode.

A common user must exist in CDB2 with the CREATE PLUGGABLE DATABASE privilege.

All transactions in HR_PDB1 of CDB1 must commit before the cloning process starts.

Cloning HR_ROOT automatically clones HR_PDB1.

The HR_PDB1clone created in CDB2 will be in mount state when cloning ends.

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 data dictionary in CDB$ROOT

the log writer process (LGWR)

SYSAUX tablespaces

temporary tablespaces

the Process Monitor Process (PMON)

undo tablespaces

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.

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.

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.

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.

Re-create or migrate the password file to the Oracle Database 12c format

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

Copy the password file from a sample file in the DBS dierectory

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

With Automatic Shared Memory Management, the database instance can increase the Large Pool size by reducing the Shared Pool size.

With Automatic Memory Management, the database instance can increase the System Global Area size by reducing the Program Global Area size.

Automatically tuned and resized System Global Area components will always revert to their initial sizes after an instance restart.

Automatic Memory Management must be used together with locking the System Global Area into physical memory.

With Automatic Shared Memory Management, the database instance can increase the Program Global Area size by reducing the System Global Area size.

On Line Transaction Processing systems often use less Program Global Area than Decision Support Systems.

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.

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.

1,2,4,5,7,8

1,2,4,6,7,8

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

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

2,4,5,6,7

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

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

TheC# # B_ADMIN user can perform all back up and recovery operation susing RMAN only.

The C # # C_ADMIN user can perform the data guard operation with Data Guard Broker.

The C # # A_ADMIN user can perform wallet operations.

The C # # D_ADMIN user can perform backup and recovery operations for Automatic Storage Management (ASM).

The C # # B_ADMIN user can perform all backup and recovery operations using RMAN or SQL* Plus.

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)

Duplication can be done by having the auxiliary database instance pull backup sets from the target database instance.

A connection to an auxiliary instance is always required.

A subset of the target database can be duplicated.

A new DBID is always created for the duplicated database.

A connection to the recovery catalog instance is always required.

A backup of the target database is always required.

Duplication can be done by having the target database instance push copies to the auxiliary database instance.

DBMS_PDB.CHECK_PLUG_COMPATIBILITY can be run against a PDB archive.

They contain a PDB manifest file and all the data files in uncompressed form for a PDB.

They contain all the data files only in uncompressed form for a PDB.

They must be created using the DBMS_PDB package.

They contain a PDB manifest file and all the data files in compressed form for a PDB.

They contain all the data files only in compressed form for a PDB.

RESYNC CATALOG

CROSSCHECK BACKUP OF ARCHIVELOG ALL

LIST ARCHIVELOG ALL

LIST EXPIRED

LIST ARCHIVELOG

REPORT OBSOLETE

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.

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.

It includes the Oracle Preinstallation RPM.

From Oracle Database 18c, a single RPM can be used to install only Oracle Database Server for a single instance.

It requires an Unbreakable Linux Network (ULN) subscription.

It performs a software-only Oracle Database installation.

It uses a service configuration script to create a single-instance database as part of the installation.

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

when a character set conversion is required during the upgrade

when multiple pluggable databases in a container database have to be upgraded in a specific sequence

when the target and source database are on the same platform

when the hardware platform needs to be changed as part of the upgrade

when the operating system (OS) needs to be changed as part of the upgrade

A backup set may be duplexed with both copies written to disk.

An image copy on disk can be copied to disk.

A backup set may be duplexed with both copies written to sbt.

A backup set may be duplexed so that one copy is written to sbt and the other to disk.

An image copy on disk can be copied to sbt.

An image copy on sbt can be copied to disk.

Tables or table partitions can be recovered by using an auxiliary instance only.

Tables or table partitions with a foreign key cannot be recovered.

Tables or table partitions can be recovered only when the database is in mount state.

Tables or table partitions from the system and sysaux tablespaces cannot be recovered.

Tables with not null constraints cannot be recovered.

AWR snapshots can be created in CDB$ROOT.

ADDM can run in a nonroot container.

AWR reports can be generated while connected to any container.

All AWR data is stored in the CDB$ROOT SYSAUX tablespace.

AWR snapshots can be created in a PDB.

No AWR data is stored in the CDB$ROOT SYSAUX tablespace.

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.

The REVENUE table must be a list-partitioned table.

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

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

The REVENUE table must be a composite-partitioned table.

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

Data Recovery Advisor can proactively check for failures.

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

ata Recovery Advisor can be used if a database is in the NOMOUNT state.

A failure can be closed only if the database is in MOUNT state.

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

Databases from the RC12C catalog are implicitly unregistered if the RC11 catalog has registered databases with same name.

Recovery catalog is resynchronized with the control files of the registered databases.

Imported databases are unregistered from the RC11 catalog.

Local and global stored scripts that have the same name as existing scripts in the RC12C catalog are automatically renamed.

All databases registered in the RC11 catalog are registered in the RC12C catalog.

They must be written to media.

They can be written only to disk.

They can be created only by using the COPIES option of a BACKUP command.

They can be created by using the RMAN CONFIGURE command to specify duplexing before taking a backup.

They can be written to media.

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.

Add the FILE_NAME_CONVERT clause to the statement and set the PDB_FILE_NAME_CONVERT parameter.

Add only the CREATE_FILE_DEST clause to the statement.

Set only the PDB_FILE_NAME_CONVERT parameter.

Set the PDB_FILE_NAME_CONVERT parameter and enable OMF.

Enable only OMF.

Add the FILE_NAME_CONVERT clause to the statement and enable Oracle Managed Files (OMF)

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.

1,3,5,7

2,5,6

1,5,6

3,4,1.6,8

1,3,5,6,7

Any PDB not specified in the plan will be unable to execute statements in parallel.

PDB3 can use all available parallel execution processes at times.

PDB1 is always limited to 40% of the available system resources regardless of demand.

Any PDB notspecified in the plan will be able to use a maximum of 16.5% of the available system resources.

PDB3 is guaranteed to receive at least 20% of the available system resources if there is enough demand.

PDB2 is guaranteed at least 25% of the available parallel execution processes if there is enough demand.

Compressed backups cannot have a section size defined.

Compressed backups can be written only to media.

Binary compression adds CPU overhead to backup operations.

Unused blocks below the high water mark are backed up.

Compression can be done only for locally managed tablespaces.

seven

five

eight

three

six

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.

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.

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.

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

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

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

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

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

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.

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.

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.

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.

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

All AWR tables belong to the SYSTEM schema.

The AWR data is stored in memory and in t he database.

The snapshots collected by AWR are used by the self-tuning components in the database

AWR computes time model statistics based on time usage for activities, which are displayed in the v$SYS time model and V$SESS_TIME_MODEL views.

AWR contains system wide tracing and logging information.

The Automatic Database Diagnostic Monitor (ADDM) Compare Period report can compare two consecutive periods.

SQL Performance Analyzer can suggest schema changes.

SQL Performance Analyzer can identify regressed SQL statements.

Database Replay always uses one replay client for all the original database sessions.

Database Replay always uses one replay client for each original database session.

The Automatic Database Diagnostic Monitor (ADDM) Compare Period report can compare two non¬consecutive periods.

The Active Session History (ASH) report is based on wait event samples.

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

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.

Space might be reclaimed proactively before space pressure occurs.

Space is always reclaimed proactively before space pressure occurs.

Space might be reclaimed automatically when the retention period for Flashback logs is lowered.

Space is always reclaimed automatically when the retention period for Flashback logs is lowered.

Space is only reclaimed when there is space pressure in the Fast Recovery Area (FRA).

A PDB snapshot is always a full copy of the source PDB.

A PDB snapshot is always a sparse copy of the source PDB.

A snapshot copy PDB depends on a storage snapshot which can only be stored on specific file systems.

A PDB snapshot depends on a storage snapshot which can be stored on any file system.

A PDB snapshot depends on a storage snapshot which can only be stored on specific file systems.

A snapshot copy PDB depends on a storage snapshot which can be stored on any file system.

A snapshot copy PDB can be created from a stand-alone clone PDB.

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.

By default, members of the OSASM group can access Automatic Storage Management and RDBMS instances.

The primary group for the Oracle Grid Infrastructure and Oracle Database owners must be the Oracle Inventory group.

The Oracle Grid Infrastructure installation must be owned by the grid user.

The Oracle Grid Infrastructure owner owns Oracle Restart and Oracle Automatic Storage Management binaries.

The Oracle Grid Infrastructure owner must have OSOPER, OSBACKUPDBA, and OSKMDBA as secondary groups.

The same OSDBA group must be used for Automatic Storage Management and the Oracle Database.

the Optimal Flexible Architecture (OFA) compliant path to store Oracle software and configuration files.

the location of Oracle Net Services configuration files

the list of a disk group names to be mounted by an Oracle Automatic Storage Management (ASM) instance at startup

default directories for temporary files used by temporary tablespaces

the temporary disk space used by Oracle Installer during installation

the maximum number of database files that can be opened by a database 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.

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.

It performs a shutdown and then a restart of all processes in both Oracle Grid Infrastructure and Oracle Database home during the patching process.

It must be invoked by a user with root user privileges.

Patches are applied via opatchauto.

Users must always input patch plans to opatchauto.

It requires the Oracle Grid Infrastructure and Oracle Database instances to be shut down before being invoked.

It applies patches in nonrolling mode by default.

It is used to apply interim patches to Oracle Grid Infrastructure and Oracle Database home combinations.

ADDM can recommend shrinking the buffer cache.

ADDM can recommend extending the buffer cache.

By default, MMON creates an AWR snapshot every 30 minutes.

ADDM performs its analysis only when a DBA requests it.

By default, AWR snapshots are automatically purged after eight days.

AWR snapshots must be deleted when no longer required by ADDM.

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.

Compare Period ADDM report

AWR Compare Period report

Active Session History (ASH) report

Taking a new snapshot and comparing it with a preserved snapshot.

The valid time columns employee_time_start and employee_time_end are automatically created.

Thesamestatementmayfilteronbothtransactiontimeandvalidtemporaltimebyusingthe 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.

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 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.

Flashback logs are automatically purged when DB_FLASHBACK_RETENTION_TARGET is set lower than the time they have already been retained.

Flashback logs are monitored and proactively deleted when beyond the retention period defined in DB_FLASHBACK_RETENTION_TARGET only after there is space pressure.

Flashback logs are monitored and proactively deleted when beyond the retention period defined in DB_FLASHBACK_RETENTION_TARGET before there is space pressure.

Flashback logs are monitored for being older than the retention period defined in DB_FLASHBACK_RETENTION_TARGET and can be deleted by an administrator written event trigger.

Flashback logs are automatically purged whenever the value of DB_FLASHBACK_RETENTION_TARGET is changed.