Oracle 1z0-083 Oracle Database Administration II Exam Practice Test

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.

The response file can specify the path of the sudo program.

The response file must contain the root or sudo password.

Silent install always runs operating scripts automatically.

The response file can specify the root or sudo password.

The installer will prompt for the root or sudo password.

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.

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.

RESYNC CATALOG

CROSSCHECK BACKUP OF ARCHIVELOG ALL

LIST ARCHIVELOG ALL

LIST EXPIRED

LIST ARCHIVELOG

REPORT OBSOLETE

It can only be launched from the command line interface.

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

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

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

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

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

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

The sudo password can be specified in a response file.

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

The sudo password must be specified in a response file.

The root password cannot be specified in a response file.

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

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.

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.

PDB-level resource plans can limit uncommitted UNDO per consumer group.

A PDB-level resource plan can limit session PGA memory.

A CDB-level resource plan can limit PDB UNDO use.

A CDB-level resource plan can limit session CPU utilization.

A CDB-level resource plan is mandatory when using PDB-level resource plans.

A CDB-level resource plan can limit PDB CPU utilization

cloning a remote container database in interactive mode

cloning a remote pluggable database in silent mode

relocating a remote pluggable database in interactive mode

relocating a remote container database in silent mode

cloning a remote container database in silent mode

relocating a remote pluggable database in silent mode

relocating a remote container database in interactive mode.

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

It succeed

It fails because no parallel channels are allocated for the auxiliary databa

It fails because connection to the AUXILIARY instance must be as SYSD

Itsucceeds only if the target database is greater than 40

No catalogued backup of the TARGET is used to duplicate the databa

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

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

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.

A Lockdown profile created from a base Lockdown profile is always automatically modified if the profile on which it is based is modified.

A PDB Lockdown profile can be created in an application root.

A Lockdown profile created from a base Lockdown profile is never automatically modified if the profile on which it is based is modified.

A PDB Lockdown profile can be created in a regular PDB.

A PDB Lockdown profile can be created in CDB$ROOT .

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.

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

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

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

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

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

It is integrated with the SQL Access Advisor.

It predicts the impact of system changes on SQL workload response time.

It provides before and after execution statistics for each SQL statement in the analysis task

It offers fine-grained analysis of all the SQL statements in the analysis task as a group.

SQL statements that were originally run concurrently are run concurrently by SPA.

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

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

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

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

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

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.

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

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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

If an RMAN command fails, the output will only identify the command that failed.

Some messages in the error stack are not errors.

If an RMAN command fails, the output will identify the channel ID where the failure occurred. D)Media Management errors appear as a line with "Additional information" and a number.

Media Management errors appear as a line with "sbtio" and a number.

Media Management errors appear as a line with "sbtio".

It can be created from a non-CDB.

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

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

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

It can be created by cloning an existing CDB.

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

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

It requires Oracle ASMLib to manage Automatic Storage Managerment (ASMl) 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 ars groups OSASM and OSDBA be assigned assecondary groups for its installation owner.

It requires the operating system ORACLE_BASDE environment variable to be predefined before installation.

It requires Oracle ASM Filter Drver (ASMFD) to manage Automatic Storage Managemernt (AsM) disks.

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.

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

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

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

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

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

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

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

ROLE1 will be created only in CDB$ROOT.

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

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

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

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

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.

A PDB can be plugged into a CDB only if both are of the same Oracle Database release.

An unplugged PDB can be plugged into multiple CDBs simultaneously by sharing data files.

A PDB unplugged from a container database (CDB) can be plugged into a different CDB without altering any of its schemas.

A non-CDB can be converted into a PDB.

A PDB in a remote CDB can be accessed transparently thereby aggregating results from local and remote PDBs.

A PDB created from PDB$SEED must be set to READ WRITE after loading data.

A PDB created from PDB$SEED must be set to READ ONLY after loading data.

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.

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.

Data file 24 can be recovered while PDB2 is opened.

Data file 24 must be recovered while the CDB is opened.

Data file 24 can be recovered while CDB$ROOT and PDB$SEED are opened.

Data file 24 cannot be recovered while the CDB is opened.

Data file 24 must be recovered while PDB2 is closed.

They are never considered obsolete by RMAN.

They can optionally be written to a fast recovery area (FRA).

All archive logs are retained after an archival backup is taken, until the next archival backup is taken of the same database.

Archive logs are retained if they are necessary to allow the database to be recovered to a consistent state when an archival backup is restored.

The SPFILE is included in the archival backup.

Use of a recovery catalog is always required to support the creation and use of archival backups. G)The ARCHIVAL attribute for a backup overrides the RMAN retention policy.

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

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.

It uses multisection backup.

It uses parallelization for the backup set.

It uses asynchronousI/O for the backup.

It creates compressed backup sets.

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.

The ORA_ARCHIVE_STATE column may only be queried by users with the DBA role set.

The ORA_ARCHIVE_STATE column is only displayed if it is referenced in the column select list of a query

The ROW ARCHIVAL VISIBILITY session parameter defaults to active rows.

The ORA_ARCHIVE_STATE column may only be updated by users with the DBA role set.

The ORA_ARCHIVE_STATE column is updated in an overnight maintenance job based on activity tracking.

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.

If a row lock is held by a nonexistent transaction, the block containing the row is media corrupt.

DB_BLOCK_CHECKING=TRUE causes a check sum to be added to each data block to help detect physical or media corruption.

A media corrupt block is one where the block is not formatted correctly.

The ANALYZE TABLE VALIDATE STRUCTURE CASCADE command verifies that each table row has an index entry pointing to it.

If a row lock is held by a nonexistent transaction, the block containing the row is logically corrupt.

DB_LOST_WRITE_PROTECT=TYPICAL causes extra logging overhead on the standby database.

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

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 Oracle Database time model should be used to find the database and instance areas most in need of tuning.

Tuning activities should stop once the user is satisfied with performance.

Tuning activities should stop once agreed service levels for performance have been met.

The database instance memory should always be tuned before tuning any file systems.

SQL statements should always be tuned before tuning any file systems.

The alert log should be used to find the database and instance areas most in need of tuning.

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.

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.

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.

It can configure Automatic Storage Management (ASM) diskgroups.

It can be used to copy an existing Oracle database to a new host and apply any patches necessary in the new host.

It can be used to add a new tablespace.

It can be used to create a database template from an existing database.

It can generate SQL database creation scripts.

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

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.

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 UNDO TABLESPACE clause is always required when no connection exists to the recovery catalog and the TARGET database is closed.

RMAN disk-based backups of the database to be duplicated can be used by the auxiliary instance.

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

The UNDO TABLESPACE clause is never required.

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

Reduced logical I/O

Reduced virtual memory utilization

Improved Serial Execution performance

Reduced physical I/O

Reduced CPU utilization

It is an Oracle Database service

It cannot be used to upgrade Oracle Database homes.

It can be used to provision applications.

It can be used to patch Grid Infrastructure homes containing Oracle Restart.

It can be used to provision middleware.

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.

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

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

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

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

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

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

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

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

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

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

A lost TEMPFILE must always be re-created manually.

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

Schema Only accounts can be granted administrator privileges.

All the Oracle-supplied accounts are Schema Only accounts.

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

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

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

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

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

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

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

They are installed via OPatch or OPatchAuto.

A base release is not needed to install patchsets.

They can be applied in a rolling fashion for Clusterware and the databases.

Installing a patchset is considered an "upgrade."

They can introduce new features.

They are only released quarterly.

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.

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.

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

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

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

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

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

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

redo logs

control files

all data dictionary metadata

user-defined PL/SQL packages

temporary tablespaces

mandatory Oracle-supplied PL/SQL packages

undo tablespaces

seven

five

eight

three

six

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.