1z0-083 Exam Dumps - Oracle Database 19c Questions and Answers

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.

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.

Decreasing PCTUSED

Decreasing PCTFREE

Increasing the number of DBWN process

Using Automatic Segment Space Management (ASSM)

Increasing db_buffer_cache based on t he V$DB_CACHE_ADVICE recommendation

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.

All the triggers associated with the table are flashed back but are disabled.

Materialized views that use the CUSTOMERS table are flashed back.

LOB segments associated with the CUSTOMERS table are flashed back.

All the constraints defined on the table, except the referential integrity constraints, are flashed back.

Only the primary key constraint created for the table is flashed back, whereas all other indexes must be retrieved separately.

Tablespaces are automatically created as need while importing full exports in either a non-CDB or a PDB.

Oracle attempts to convert conventional database users to local users when moving schemas from a non-CDB to a PDB.

A new PDB is automatically created when importing a non-CDB into a CDB.

Oracle attempts to convert common users to conventional users when moving schemas from a PDB to a non-CDB.

Moving data from a PDB to a non-CDB is only possible by using transportable tablespace export and import.

Moving data from a non-CDB to a PDB is only possible by using conventional export and import.

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 checks each query being analyzed for stale statistics.

It checks each query being analyzed for missing statistics.

It only recommends syntactic changes to SQL statements.

It can recommend semantic changes to SQL statements.

It considers all SQL statements being analyzed by the advisor task as a group.

It builds SQL profiles for each poorly performing SQL statement to prevent regressions.

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

Media Management messages for SBT devices are always written to sbtio.log.

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

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

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

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

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