Free Practice Questions for Oracle 1z0-083 Exam

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.

All archive redo log files are automatically copied to the duplicate database.

The duplicate database has the same directory structure as the source database.

The duplicate database is created by using the backups created during the execution of

he duplicate command.

The password file and SPFILE for the duplicate database dup1 are created in their respective default locations.

The duplicate database is created without using RMAN backups and prod1 is allowed to remain open during duplication.

If Automatic Memory Management is enabled, no memory advisors are available.

If Automatic Memory Management is enabled, the Shared Pool Advisor and Buffer Cache Advisor are available to set the maximum size for these individual System Global Area components.

All memory advisors use data from Automatic Workload Repository.

If Automatic Shared Memory Management is enabled, both the SGA Advisor and PGA Advisor are always available.

If Manual Shared Memory Management is enabled, only the Shared Pool Advisor and Buffer Cache Advisor are available.

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

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.

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.

to generate an XML metadata file that describes a non-CDB Oracle 12c database so that it can be plugged in as a PDB

to generate an XML metadata file from any unplugged PDB

to determine whether an XML file describes a PDB that can be plugged into the CDB in which you run the procedure

to generate a . pdb archive file for any PDB in the current CDB

to generate an XML metadata file that describes the current plugged-in PDB

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

It is used to change failure priority only for HIGH or LOW priorities.

It is used to execute the advised repair script.

It is used to change failure priority only for the CRITICAL priority.

It is used to explicitly close the open failures.

It is used to inform the database about the repair after the repair script executes.