1z0-083 Oracle Database Administration II Questions and Answers

Application-common Transparent Security Data Protection (TSDP) policies can be created only if all the PDBs in the application container are closed.

Application-common TSDP policies are always container specific.

Application-common OLS policies can be created only if all the PDBs in the application container are closed.

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

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

A base recovery catalog should exist.

The owner of VPC cannot own recovery catalog.

At least one target database should be registered in the recovery catalog.

The register database privilege should be granted to the virtual catalog owner.

The recovery_catalog_owner role should be granted to the virtual catalog owner.

seven

five

eight

three

six

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

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.

It fails because Data Pump cannot be container.

It creates a full export of the root

It creates a full export of the root

It creates a full export of only the used while connected to the root container and PDB1. container and all PDBs. container and all open PDBs. root container.

It will create ‘$ORACLE_HOME/dbs/cdb1/CDB1/controlfile02.ctl’

It will create ‘/u01/app/oralce/oradata/CDB1/controlfile/controlfile02.ctl’.

It will re-create ‘/u02/app/oracle/fast_recover_area/cdb1/CDB1/controlfile02.ctl’

It will create ‘/u01/app/oracle/product/12.2.0.1/db_1/dbs/snapcf_cdb1control02.ctl’.

It will fail because there is no autobackup of the controlfiles.

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 local database to the PDB in the remote system that is to be cloned

backing up the cloned PDB

opening the cloned PDB

leaving the cloned PDB in mount state

Stateless alerts can be cleared manually.

Stateless alerts are automatically cleared after one day.

Stateful alerts are purged automatically from the alert history after one day.

Stateless alerts can be purged manually from the alert history.

Stateful alerts must be cleared by a DBA to resolve the problem identified in the alert.

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.

using RMAN stored scripts

creating encrypted backups

creating customized reports about a single database's backups

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

using the KEEP FOREVER clause with the BACKUP command

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

To use Flashback Data Archive, users must have unlimited quota on the Flashback Data Archive tablespace.

To enable Flashback Data Archive for a table, it is mandatory to have a default Flashback Data Archive for a database

While enabling Flashback Data Archive for a table, if no name is provided for Flashback Data Archive, it is enabled using the default Flashback Data Archive.

A table enabled for Flashback Data Archive cannot be dropped unless Flashback Data Archive is disabled or disassociated first.

Flashback Data Archive prevents flashback queries from getting a snapshot-too-old error.

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.

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.

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

OSASM

OSRACDBA

OSKMDBA

OSDBA

E）OSOPER

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.

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.

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.

It uses a single master key for a database.

It replaces secure application roles.

It encrypts only data on the client.

It stores the current and all past master keys in the keystore.

Master encryption keys are managed by Oracle Database Vault.

It can encrypt data at the column level.

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

Single-byte character sets provide better performance than multibyte character sets.

Unicode enables information from any language to be stored using a single character set.

Unicode is the only supported character set for Oracle databases created using Database Configuration Assistant (DBCA).

Single-byte character sets always use 7-bit encoding schemes.

Multibyte character sets allow more efficient space utilization than single byte character sets.

Single-byte character sets always use 8-bit encoding schemes.

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.

a General Purpose database template with default memory allocation

a Data Warehouse database template, with t he dedicated server mode option and AMM enabled

a General Purpose database template, with t he shared server mode option and Automatic Memory Management (AMM) enabled

a default database configuration

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.

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.

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.

It always analyzes all schemas in the database.

It can recommend changes to improve the statistics gathering process.

It can be run only manually.

It runs automatically every night by default. E) It can be run only automatically.

defining primary keys for all tables to speed up all queries

using check constraints to speed up updates

defining foreign keys for all tables to speed up joins

the physical data model

the configuration of storage arrays

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

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

The BACKUP BACKUPSET command can encrypt and decrypt backup sets.

Image copies can be encrypted.

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

Backup encryption can be enabled selectively for specific tablespaces.

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.

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.

All audit records are written to the audit trail in CDB$ROOT .

Application-common unified audit policies defined in an application root must be manually synchronized by each application PDB contained in the application root.

Fine-grained auditing policies defined in an application root must be manually synchronized by each application PDB contained in the application root.

A common unified audit policy can be created at the CDB level.

A common unified audit policy can be created at the application root level.

An application PDB cannot have a local audit policy.

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.

The ORA_ARCHIVE_STATE column visibility is controlled by the ROW ARCHIVAL VISIBILITY session parameter.

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

The ROW ARCHIVAL VISIBILITY session parameter defaults to active rows only.

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

The ORA_ARCHIVE_STATE column is updated automatically by the Oracle Server based on activity tracking columns, to Indicate that a row is no longer considered active. Correct

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.

Tune individual SQL statements using the SQL Tuning Advisor.

Identify poorly tuned SQL statements using Automatic Database Diagnostic Monitor.

Test the application as a whole using tuned SQL statements.

Test tuned SQL statements one at a time for all statements in the application.

Identify poorly tuned SQL statements using the SQL Tuning Advisor.

Tune SQL statements as a group using the SQL Tuning and SQL Access Advisors.

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

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.

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

All Oracle recovery files not in the current FRA that have not been backed up already, are backed up.

All non-Oracle files in the current FRA that have not been backed up already, are backed up.

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

These backups can be written to disk or SBT.

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.

Tracking the most recent read time for a table segment in a user tablespace

Tracking the most recent write time for a table segment in a user tablespace

Tracking insert time by row for table rows

Tracking the most recent write time for a table block

Tracking the most recent read time for a table segment in the SYSTEM tablespace

Tracking the most recent write time for a table segment in the SYSAUX tablespace Correct

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.

By default, the transported database will use Oracle Managed Files (OMF)

Data files can be converted on the destination system.

Data files can be converted on the source system.

A new DBID is automatically created for the transported database.

Databases can be transported between systems with different endian formats.

The password file is automatically converted by RMAN.

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

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.

It can be performed using an auxiliary instance managed by RMAN.

It can be performed using an auxiliary instance managed by a DBA.

It can be used to recover a truncated table.

It can be performed repeatedly until the correct time is found without using an RMAN catalog. E)RMAN always includes tablespaces containing UNDO segments in the recovery set.

RMAN automatically adds any required tablespaces to the recovery set to make it selfcontained. G) FLASHBACK DATABASE must be enabled for it to work. H) It can be used to recover a dropped

tablespace.

It considers the filters in WHERE clauses when generating execution plans for SQL statements.

It obeys all hints.

It considers object statistics when generating execution plans for SQL statements.

It updates stale object statistics in the Data Dictionary.

It can only use SQL Plan Directives tied to the SQL statement for which a plan is being generated.

It can re-optimize execution plans after previous executions detect suboptimal plans.

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.

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.

2,4,5,6

1,2,3,4,5,6

1,2,4,5

2,4,5

1,3,4,5

RMAN uses the pull method to restore files using image copies

RMAN uses the push method to transfer image copies

RMAN uses the push method to transfer backup sets

RMAN uses the pull method to restore files using backup sets

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

You can

You can

You can

You can

You can

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

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.

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.

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.

he SPFILE is copied along with the datafiles of the pluggable databases (PDBs). 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 duplicate command first creates a backup, and then duplicates the PDBs by using the backup.

A backup of CDB and pdb1 and pdb5 must exist before executing the command.

An auxiliary instance must be started with the initialization parameter ENABLE_PLUGGABLE_DATABASE set to TRUE.

creating a disk group using the CREATE DISKGROUP SQL statement

creating a database service using DBMS_SERVICE.CREATE_SERVICE

creating a database service using Oracle Database Configuration Assistant (DBCA)

creating a database using the CREATE DATABASE SQL statement

creating an Oracle Database service by modifying the SERVICE_NAMES parameter

creating an Oracle Automatic Storage Management (ASM) instance with ASM Configuration Assistant (ASMCA)

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

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

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.

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

PDB1 and PDB2 are in MOUNT state.

Redo logs are opened.

PDB1 and PDB2 are in READ ONLY state.

CDB$ROOT is in MOUNT state.

PDB$SEED is in READ ONLY state.

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.

Recovery begins from the beginning of the CURRENT redo log group.

Recovery begins from the last checkpoint position that was calculated by the Database Writer before instance failure.

Recovery begins from the start of any ACTIVE redo log group or the start of the CURRENT log group if no other group is ACTIVE.

Recovery reads redo until the end of the redo thread. SMON rolls back any dead transactions, and then the datanase is opened.

Recovery begins from the last checkpoint position that was recorded in the control file by the checkpoint process (CKPT).

Recovery reads redo until the end of the redo thread, and then opens the database. SMON then rolls back any dead transactions.

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.

FLASHBACK DATABASE only uses FLASHBACK LOGS to get the database to the desired flashback time.

It requires that the target database be in ARCHIVELOG mode.

FLASHBACK LOGS are archived after a log switch.

A database can be flashed back using SQL*PLUS.

It always generates REDO and UNDO.

Queries and DML have the same FLASHBACK LOG overhead when flashback is enabled for a database.

It can manage database resources on the server where it is installed or on a different server.

The CSS daemon runs from the Grid Infrastructure home.

It supports volume management, file system, and automatic restart capabilities.

It requires Oracle Automatic Storage Management (ASM) components to be installed separately.

It must be installed before the Oracle database software is installed.

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.

Backups can be taken only if a fast recovery area is configured.

Backups can be written only to disk.

Backups can be taken only for data files.

Binary compression cannot be applied to the backup.

Backups can be written only if checksums are stored for each block.

Backups can be written only to media.

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.

It can contain a single application

Two application containers can share an application seed PDB.

It must have an application root PDB.

An application PDB can belong to multiple application containers.

It must have an application seed PDB.

It can contain multiple applications.

Pre-existing backups of the database to be duplicated are required for the "push" method of duplication.

Pre-existing backups of the database to be duplicated are required for the "pull" method of duplication.

Pre-existing backups of the database to be duplicated are always used if they exist.

Image copies can be used to duplicate the active database.

The active database must be duplicated while in OPEN state.

No connection to the recovery catalog is required for active database duplication.

Backup sets can be used to duplicate the active database.

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