1z0-083 Oracle Database Administration II Questions and Answers

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

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

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

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

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

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

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

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.

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.

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

Application-common TSDP policies are always container specific.

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

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

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

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

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

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.

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

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

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

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

Run ADDM in diagnostic mode.

It is automatically synchronized with its application root PDB when an application is upgraded. B)It cannot be added to an application container after the application container has already been created.

A new application PDB created by cloning an application seed PDB can have an old version of the application installed after cloning completes.

It is automatically synchronized with its application root PDB when an application is installed.

It cannot be dropped from its application container.

A new application PDB created by cloning an application seed PDB can have an up-to-date version of the application installed after cloning completes.

It is not required in an application container.

2,4,5,6

1,2,3,4,5,6

1,2,4,5

2,4,5

1,3,4,5

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

the log writer process (LGWR)

SYSAUX tablespaces

temporary tablespaces

the Process Monitor Process (PMON)

undo tablespaces

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.

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

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

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

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

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

by performing emergency monitoring using Real-Time Automatic Database Diagnostic Monitor (ADDM) to fetch data directly from SGA for analysis

by running ADDM to fetch information from the latest Automatic Workload Repository (AWR) snapshots

by using Active Session History (ASH) data and performing hang analysis

by running ADDM in diagnostic mode

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.

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.

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

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.

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.

The General Purpose of Transaction Processing templates are most suitable when concurrency and recoverability are key criteria.

Oracle DBCA templates can store only logical structure and not database files.

New templates can only be created by modifying an existing user-created template.

The Data Warehouse template is most suitable when transaction response time is the key criterion.

Oracle DBCA templates can be used to create new databases and duplicate existing databases.

after losing a SYSAUX tablespace data file

after losing all members of an INACTIVE online redo log group

after losing all members of the CURRENT online redo log group

after losing all copies of the control file

after losing an UNDO tablespace that is in use

A proxy PDB must exist in the application root in the local CDB.

PDB3's application root replica must exist in the local CDB.

The HR_ROOT replica must exist in the remote CDB.

A database link must exist in the remote CDB referring to the local CDB.

A proxy PDB must exist in the application root in the remote CDB.

A database link must exist in the local CDB root referring to the remoteCDB.

You can

You can

You can

You can

You can

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.

It uses multisection backup.

It uses parallelization for the backup set.

It uses asynchronousI/O for the backup.

It creates compressed backup sets.

The restore point is a label for the system change number (SCN) that will be saved two years after the archival backup was taken.

The data file backups in the self-contained archive backup are not considered obsolete for two years regardless of the retention policy.

All archive logs created after this backup are kept for two years.

The SPFILE is included in the self-contaied archival backup.

The control file is included in the self-contained archival backup.

The restore point is a label for the system change number (SCN) before the archival backup was taken.

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.

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.

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.

restore and recover database

flashback transaction

flashback database

flashback table and transaction

flashback table

using Database Replay

using SQL Developer

using Oracle Data Pump

using operating system file copy utilities

using Database Upgrade Assistant

using the CREATE TABLE AS SELECT SQL statement

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.

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.

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.

Re-enableredactionpoliciesthatuseFULLdataredaction.

Re-createredactionpoliciesthatuseFULLdataredaction.

Re-connect the sessions that access objects with redaction policies defined on them.

Flushthesharedpool.

Restart the database instance. Correct

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.

Executing DBMS_STATS.GATHER_DATABASE_STATS while connected to CDB$ROOT gathers object statistics in all open PDBs except PDB$SEED.

Executing DBMS_STATS.GATHER_DATABASE_STATS while connected to a PDB opened in read/ write mode gathers object statistics for that PDB.

Executing DBMS_STATS.GATHER_DATABASE_STATS while connected to CDB$ROOT gathers object statistics only in CDB$ROOT.

System statistics can be gathered only while connected to CDB$ROOT.

Executing DBMS_STATS.GATHER_DATABASE_STATS while connected to CDB$ROOT gathers object statistics in all open pluggable databases (PDBs)

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

AWR snapshots can be created in CDB$ROOT.

ADDM can run in a nonroot container.

AWR reports can be generated while connected to any container.

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

AWR snapshots can be created in a PDB.

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

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.