1z0-083 Oracle Database Administration II Questions and Answers

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.

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

Compare Period ADDM report

AWR Compare Period report

Active Session History (ASH) report

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

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.

SYSsessions,regardlessoftherolesthataresetinthesession

SYSTEMsessions,regardlessoftherolesthataresetinthesession

SCOTT sessions, only if the MGR role is set in the session

SCOTT sessions, only if the MGR role is granted to SCOTT

SCOTTsessions,becauseheistheownerofthetable

SYSTEM session, only if the MGR role is set in the session

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.

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.

It fails because PDB$SEED is in MIGRATE state.

Only CDB$ROOT, PDB$SEED, and PDB1 are upgraded.

Only CDB$ROOT, PDB$SEED, and PDB2 are upgraded.

It fails because PDB2 is not in UPGRADE state.

CDB$ROOT, PDB$SEED, PDB1, and PDB2 are upgraded.

Only CDB$ROOT and PDB$SEED are upgraded.

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

If no PDB plan is enabled for a pluggable database, then all sessions for that PDB are treated to an equal degree of the resource share of that PDB.

In a PDB plan, subplans may be used with up to eight consumer groups.

If a PDB plan is enabled for a pluggable database, then resources are allocated to consumer groups across all PDBs in the CDB.

If no PDB plan is enabled for a pluggable database, then the PDB share in the CDB plan is dynamically calculated.

If a PDB plan is enabled for a pluggable database, then resources are allocated to consumer groups based on the shares provided to the PDB in the CDB plan and the shares provided to the consumer groups in the PDB plan.

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.

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

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

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

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

PDB1 data files already exist in the correct location.

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

PDB_FILE_NAME_CONVERT must be set before executing the command.

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

PDB1 must be dropped from CDB1.

CDB1, PDB$SEED, PDB1, and PDB2

PDB$SEED, PDB1, and PDB2 only

CDB1 and PDB$SEED only

CDB1, PDB1, and PDB2 only

CDB1, PDB$SEED, and PDB1 only

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

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

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

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

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

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

The target database must be open

The duplication process can use existing backup sets or image copies

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

The target database must be in mount state.

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

The duplication process pushes image copies to the auxiliary instance.

To use it, Flashback Database must be enabled.

A block being recovered is not accessible.

It cannot repair logical corruption.

It can be performed on noncorrupt blocks.

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

The data file containing the block being recovered remains online.

APP1_USER1can be created in PDB1.

APP1_USER1can be created in CDB1.

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

C##_APP_USER1 can be created in CDB1.

P1_USER1can be created in CDB1.

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

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.

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

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

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

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

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

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

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.

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.

It can be created only by using RMAN.

It always includes all data files, the current control file, the server parameter file, and archived redo logs.

It can be consistent.

It is the only possible backup type for a database in NOARCHIVELOG mode.

It can consist of either backup sets or image copies.

It can be inconsistent.

Transparent encryption of backups uses an encryption wallet.

Image copy backups can be created by using password encryption.

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

Encrypted backups can only be written to disk.

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

Reduced logical I/O

Reduced virtual memory utilization

Improved Serial Execution performance

Reduced physical I/O

Reduced CPU utilization

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

RMAN can always repair corrupt blocks.

Flashback commands help with repairing physical errors.

The ADR can store metadata in an Oracle Database repository.

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

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

The Data Recovery Advisor uses the ADR.

If no PDB plan is enabled for a pluggable database, then all sessions for that PDB are treated to an equal degree of the resource share of that PDB.

In a PDB plan, subplans may be used with up to eight consumer groups.

If a PDB plan is enabled for a pluggable database, then resources are allocated to consumer groups across all PDBs in the CDB.

If no PDB plan is enabled for a pluggable database, then the PDB share in the CDB plan is dynamically calculated.

If a PDB plan is enabled for a pluggable database, then resources are allocated to consumer groups based on the shares provided to the PDB in the CDB plan and the shares provided to the consumer groups in the PDB plan.

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.

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.

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.

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.

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

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.

CDB1_TAB, APP_ROOT_TAB, and APP_PDB1_TAB

CDB1_TAB and APP_PDB1_TAB

CDB1_TAB and APP_ROOT_TAB

CDB1_TAB only

none of the tables, because all three tables will be dropped

The NOREDO clause must be used if the backups of the database being duplicated were taken when the database was in NOARCHIVELOG mode.

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

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

The NOREDO clause can be used if the backups of the database being duplicated were taken when the database was in ARCHIVE LOG mode.

RMAN SBT-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 recovery catalog and the TARGET database is closed.

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

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

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

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.

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

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

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

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

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

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

It can be run only manually.

It is part of the DBMS_ADVISOR package.

It can recommend changes to improve the statistics gathering process.

It always analyzes all schemas in the database.

It runs automatically every night by default.

It is part of the DBMS_STATS package.

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 metrics are instance related.

Cleared stateful alerts are displayed by querying DBA_ALERT_HISTORY.

A space usage management alert is automatically cleared after the underlying problem is resolved

They are generated by SMON when a tablespace is 97% full.

Metrics are statistical counts for a specific unit.

STATISTICS_LEVEL must be set to ALL to generate alerts.

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.

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.

A media manager always writes RMAN requested backups to tape.

A media manager is required to create RMAN image copies.

A media manager is required to create RMAN proxy copies.

The media manager layer (MML) routines provided by Oracle support any vendors' media management products.

By default, a request for a proxy copy may result in a backup set being created.

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

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.

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.

log writer performance

database writer performance

general operating system health

SQL statements

database instance memory management and sizes

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.

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

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

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

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

A CDB can be duplicated using the Database Configuration Assistant (DBCA) in silent mode with no configuration required before starting the duplication.

A CDB can be duplicated using Recovery Manager (RMAN) with no configuration required before starting the duplication.

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

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.

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

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.

Increase the size of tape I/O buffers.

Disable FORCE LOGGING for the database.

Increase the size of the database buffer cache.

Enable asynchronous disk I/O.

Increase the level of RMAN multiplexing.

Run the SQL Access Advisor.

Run the Memory Advisor for the shared pool.

Run the SQL Tunning Advisor.

Run the Memory Advisor for the Program Global Area.

Run the Memory Advisor for the System Global Area.

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 cannot be backed up manually as a binary copy.

It gets backed up automatically by RMAN as a trace file containing SQL statements for control file re¬creation when a database backup occurs.

It can be backed up manually as a binary copy.

It can get backed up automatically as a binary copy.

It gets backed up automatically by RMAN when the BACKUP SPFILE command is used.

It can be backed up manually as a trace file containing SQL statements for control file recreation.

The database must have FLASHBACK DATABASE ON to perform Database Point-in-Time Recovery.

The database must be in MOUNT state when performing Database Point-in-Time Recovery.

Database Point-in-Time Recovery is performed by the Managed Recovery Process (MRP)

The Database must be in ARCHIVE LOG mode.

The target point for the recovery must be specified as a stime or System Change Number (SCN).

The database must be open RESETLOGS after Database Point-in-Time Recovery.

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.

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.

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

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

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

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.

1,3,5,7

2,5,6

1,5,6

3,4,1.6,8

1,3,5,6,7

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

OSASM

OSRACDBA

OSKMDBA

OSDBA

E）OSOPER

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.

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

1,3,6

1,2,5

3,4,5

2,3,5,6

2,4,5,6

1,2,3,4,5,6

1,2,4,5

2,4,5

1,3,4,5

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.

The entire PGA is located in the System Global Area (SGA) when using shared servers.

PGA_AGGREGATE_LIMIT is a hard limit on the PGA size for any one session.

The private SQL area (UGA) is located in the System Global Area (SGA) when using dedicated servers.

The private SQL area (UGA) is located in the System Global Area (SGA) when using shared servers.

Sorts and Hash Joins use PGA memory.

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.

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.

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.

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.

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