RMAN? (Choose two.)
Two or more PDBs can be duplicated with the same RMAN DUPLICATE
Command.
All tablespaces belonging to a PDB must be duplicated when duplicating the
PDB.
The auxiliary instance is automatically created with
ENABLE_PLUGGABLE_DATABASE = TRUE.
A user with SYSDBA or SYSBACKUP must be logged in with RMAN to the PDB
To duplicate it.
Point-In-Time Recovery (TSPITR) using Recovery Manager (RMAN)?
It can be performed using an auxiliary instance managed by RMAN.
It can be performed using an auxiliary instance managed by a DBA.
It can be used to recover a truncated table.
It can be performed repeatedly until the correct time is found without using an
RMAN catalog.
RMAN always includes tablespaces containing UNDO segments
In the recovery set.
RMAN automatically adds any required tablespaces to the recovery set to
Make it selfcontained.
Without a TARGET connection? (Choose four.)
Assistant (DBCA)?
Large data file is divided into four sections? (Choose two.)
Three.)
Snapshots in Oracle 19c and later releases? (Choose two.)
A PDB snapshot is always a full copy of the source PDB.
A PDB snapshot is always a sparse copy of the source PDB.
A snapshot copy PDB depends on a storage snapshot which can only be
Stored on specific file systems.
A PDB snapshot depends on a storage snapshot which can be stored on any
File system.
A PDB snapshot depends on a storage snapshot which can only be stored on
Specific file systems.
Message output? (Choose two.)
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.
(Choose three.)
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.
(Choose three.)
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.
Later releases? (Choose two.)
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.
It is performed automatically while the database remains in MOUNT state.
Then the database is opened.
Individual pluggable databases (PDB plans) in a multitenant container
Database (CDB)?
Compression? (Choose two.)
Compressed backups can be written only to media.
Binary compression adds CPU overhead to backup operations.
Unused blocks below the high water mark are backed up.
Compressed backups cannot have a section size defined.
我来回答: