Overall explanation

Remember that the different forms of contention are symptoms that can
be fixed by making changes in the following places:
 Changes in the application, or the way the application is used
 Changes in Oracle
 Changes in the host hardware configuration

Often, the most effective way of resolving a bottleneck is to change

the application.

Read Bottleneck Elimination

Domain
Database Performance Tuning and Dynamic Performance Views

Question 2Skipped
Which three are true about block media recovery? (Choose three.)
Overall explanation
Purpose of Block Media Recovery

Enables affected data files to remain online during recovery

Without block media recovery, if even a single block is corrupt, then you
must take the data file offline and restore a backup of the data file. You
must apply all redo generated for the data file after the backup was
created. The entire file is unavailable until media recovery completes.
With block media recovery, only the blocks actually being recovered are
unavailable during the recovery.

Block media recovery is most useful for physical corruption problems

that involve a small, well-known number of blocks.

Block media recovery may not be able to repair all logical block
corruptions. In these cases, alternate recovery methods, such as
tablespace point-in-time recovery, or dropping and re-creating the
affected objects, may repair the corruption.

Although the documentation says below, block media recovery

can be run on noncorrupt blocks too and recovery will be
complete successfully without doing anything.

You can perform block recovery only on blocks that are marked corrupt or
that fail a corruption check.

Read Performing Block Media Recovery

Domain
Block media recovery
Overall explanation
Each pluggable, seed, root, and container can have its own default
temporary tablespace. So, the total can be 8 in this case.
Domain
Multitenant Architecture
Overall explanation
During a proxy copy, RMAN turns over control of the data transfer to
a media manager that supports this feature. The PROXY option of the
BACKUP command specifies that a backup is a proxy copy.

Proxy copy can only be used with media managers that support it
and cannot be used with channels of type DISK.

For each file that you attempt to back up with the BACKUP PROXY
command, RMAN queries the media manager to determine whether it can
perform a proxy copy. If the media manager cannot proxy copy the
file, then RMAN backs up the file as if the PROXY option had not
been used. (Use the PROXY ONLY option to force RMAN to fail if a proxy
copy cannot be performed.)
Control files are never backed up with proxy copy. If the PROXY option is
specified on an operation backing up a control file, then it is silently
ignored for the purposes of backing up the control file.

Read About RMAN Proxy Copies

Domain
RMAN Backup and Recovery

Question 5Skipped
Which three can be done using Oracle Database Configuration Assistant
(DBCA) starting from Oracle Database 19c? (Choose three.)
Overall explanation
In silent mode, you can clone a remote CDB or PDB.

Read createPluggableDatabase

Also, the relocatePDB command relocates a PDB from a remote CDB to a

local CDB.

Read relocatePDB

Domain
Database Creation

Question 6Skipped
Which three are true about creating container databases (CDBs) and
pluggable databases (PDBs) in Oracle 19c and later releases? (Choose
three.)
Overall explanation
Basic concepts:

PDB snapshot vs snapshot copy PDB - both are different things.

PDB snapshot is a sparse or full point-in-time copy of a normal source

PDB. You can maintain multiple PDB snapshots of a PDB in a carousel
(circular library). When needed, you can create a new PDB by cloning from
the PDB snapshot.
Snapshot copy PDB is a storage snapshot based copy of a PDB and it
occupies only a fraction of the space of the source PDB.

A PDB snapshot can be a sparse copy of a source PDB. - TRUE

A PDB snapshot can be a full copy of a source PDB. - TRUE

A PDB snapshot is a point-in-time copy of a PDB. The source PDB can be

open read-only or read/write while the snapshot is created. You can
create snapshots manually using the SNAPSHOT clause of CREATE
PLUGGABLE DATABASE (or ALTER PLUGGABLE DATABASE), or
automatically using the EVERY interval clause. If the storage system
supports sparse clones, then the preceding command creates a sparse
copy. Otherwise, the command creates a full copy.

Read About PDB Snapshot Carousel

Snapshot copy PDB

Creates a snapshot copy PDB from a storage-managed snapshot (not

ALTER PLUGGABLE DATABASE SNAPSHOT). Storage-managed snapshots
are only supported on specific file systems.

A snapshot copy PDB does not include a complete copy of the source data
files. Rather, Oracle Database creates a storage-level snapshot of the
underlying file system, and then creates the clone PDB from the snapshot.

Read User Interface for PDB Cloning

A snapshot copy PDB can be a full copy of a source PDB. - FALSE

A PDB snapshot is not created from a storage snapshot. So, it is not

related to storage snapshots anyway.

A PDB snapshot depends on an existing storage snapshot of the source

PDB. - FALSE
A snapshot copy PDB does not depend on an existing storage snapshot of
the source PDB. - FALSE - It does depend on an existing storage snapshot
of the source PDB. Read User Interface for PDB Cloning.

A CDB can be duplicated using the Database Configuration Assistant

(DBCA) in silent mode with no configuration required before starting the
duplication. - TRUE

Read Duplicate CDBs using DBCA in Silent Mode

Domain
Multitenant Architecture
Overall explanation
Upgrading Oracle Multitenant In Sequence

With the In Sequence technique, you install the new release multitenant
architecture CDB. Next, in the earlier release multitenant architecture
CDB, you issue SQL commands to run preupgrade scripts to prepare one
or more PDBs to upgrade, and shut them down. You then unplug PDBs,
plug them into the new release multenant architecture CDB, and
complete the upgrade sequentially for each PDB.

Read About Oracle Multitenant Oracle Database Upgrades

When using DBUA or when performing a manual upgrade for Oracle

Database, you cannot directly migrate or transport data in a database on
one operating system to a database on another operating system. For
example, you cannot migrate data in an Oracle database on Solaris to an
Oracle 12c database on Windows using DBUA. You must follow procedures
specific to your operating system platforms.

Read Options for Transporting Data to a Different Operating System

Domain
Upgrades
Overall explanation
Poorly written SQLs and infrequent commits can cause bad database
performance as the number of users, and hence concurrency or the
amount of data to be read/written increases.

Read Understanding Scalability and Factors Preventing Scalability

Domain
Performance Tuning
Overall explanation
In a CDB with multiple PDBs, some PDBs typically are more important than
others. The Resource Manager enables you to prioritize and limit the
resource usage of specific PDBs. With the Resource Manager, you can:
 Specify that different PDBs should receive different shares of the
system resources so that more resources are allocated to the more
important PDBs
 Limit the CPU usage of a particular PDB
 Limit the number of parallel execution servers that a particular PDB
can use
 Limit the memory usage of a particular PDB
 Specify the amount of memory guaranteed for a particular PDB
 Specify the maximum amount of memory a particular PDB can use
 Use PDB performance profiles for different sets of PDB

A performance profile for a set of PDBs can specify shares of system

resources, CPU usage, and number of parallel execution servers.
PDB performance profiles enable you to manage resources for large
numbers of PDBs by specifying Resource Manager directives for
profiles instead of individual PDBs.

 Limit the resource usage of different sessions connected to a single

PDB
 Limit the I/O generated by specific PDBs
 Monitor the resource usage of PDBs

Undo Pool

You can specify an undo pool for each consumer group. An undo pool
controls the total amount of undo for uncommitted transactions that can
be generated by a consumer group.

When the total undo generated by a consumer group exceeds its undo
limit, the current DML statement generating the undo is terminated. No
other members of the consumer group can perform further data
manipulation until undo space is freed from the pool.

Read Purpose of Resource Management in a Multitenant Environment

and The Types of Resources Managed by the Resource Manager

Domain
Database Resource Manager
Question 12Skipped
Your database is in ARCHIVELOG mode and you plan to use Flashback
Database. Which two features or parameters manage space availability in
the fast recovery area? (Choose two.)
Overall explanation
The fast recovery area stores only backup files and archive log files.
Domain
Flashback Technologies

Question 13Skipped
Which three resources are always shared among CDB$ROOT and
pluggable databases (PDBs)? (Choose three.)
Overall explanation
When connected to root CDB, you can take a backup of just CDB$ROOT or
selective/all PDBs or the whole database (CDB$ROOT and PDBs).

Connected to PDB, you cannot backup archive logs.

Read Backing Up and Recovering CDBs and PDBs and Backing Up a Whole
CDB and Backing Up PDBs with RMAN

Domain
Database Creation
Overall explanation
You can use BACKUP...COPIES or CONFIGURE...BACKUP COPIES to duplex
backup sets. RMAN can duplex backups to either disk or tape, but cannot
duplex backups to tape and disk simultaneously. For DISK channels,
specify multiple values in the FORMAT option to direct the multiple copies
to different physical disks. For SBT channels, if you use a media manager
that supports Version 2 of the SBT API, then the media manager
automatically writes each copy to a separate medium (for example, a
separate tape). When backing up to tape, ensure that the number of
copies does not exceed the number of available tape devices.

Duplexing applies only to backup sets, not image copies. It is an error to

specify the BACKUP... COPIES when creating image copy backups, and the
CONFIGURE... BACKUP COPIES setting is ignored for image copy backups.

Read Duplexing Backup Sets

Domain
Database Creation
Question 18Skipped
Examine this configuration:
Overall explanation
As only the app_root pluggable database is being flashbacked, only its
changes will be rollbacked. The tables created in other pluggable
databases will still be there.
Domain
Multitenant Architecture
Overall explanation
Any password cannot be put in any kind of file.

The installer will ask for the password if installation is not being done via
sudo program.

Read Read the Response File

Domain
Oracle Software Installation
Overall explanation
Starting with Oracle Database Release 19c, the management of space in
the fast recovery area is simplified. Oracle Database monitors flashback
logs in the fast recovery area and automatically deletes flashback logs
that are beyond the retention period. When the retention target is
reduced, flashback logs that are beyond the retention period are deleted
immediately.

The COMPATIBLE initialization parameter must be set to 19.0.0 or higher

for flashback logs to be automatically deleted.

In scenarios where a sudden workload spike causes a large number of

flashback logs to be created, the workload is monitored for several days
before deleting flashback logs that are beyond the retention period. This
avoids the overhead of recreating the flashback logs, if another peak
workload occurs soon after.

Read Managing Space for Flashback Logs in the Fast Recovery Area
Domain
Flashback Technologies

Question 21Skipped
Which three are true about RMAN archival backups with the RESTORE
POINT clause? (Choose three.)
Overall explanation
The ADRCI utility assists you with diagnosing the cause of problems in
your database (incidents). It can assist you with collecting data in an
incident package that Oracle Support may need to help you to address the
root cause of issues.

Read About the ADR Command Interpreter (ADRCI) Utility

Each instance of each product stores diagnostic data underneath its own
ADR home directory. For example, in an Oracle Real Application Clusters
(Oracle RAC) environment with shared storage and Oracle ASM, each
database instance and each Oracle ASM instance has a home directory
within the ADR.

Read Definitions for Oracle Database ADRC

If failures are diagnosed, then they are recorded in the Automatic

Diagnostic Repository (ADR), which is a directory structure stored
outside of the database. You can use Data Recovery Advisor to generate
repair advice and repair failures only after failures have been detected by
the database and stored in ADR.

Read About Data Integrity Checks

Domain
Automatic Diagnostic Repository
Overall explanation
The KEEP FOREVER clause requires the use of a recovery catalog, because
the control file cannot contain an infinitely large set of RMAN repository
data.

Read Changing the Status of an Archival Backup

Stored scripts are an alternative to command files that allow scripts to be

available to any RMAN client that can connect to the target database and
its recovery catalog.

Use the CREATE SCRIPT command to create a stored script in the recovery
catalog. A stored script is a sequence of RMAN commands that is given a
name and stored in the recovery catalog for later execution.
Read Scripting RMAN Operationsand CREATE SCRIPT

Domain
RMAN Backup and Recovery

Question 24Skipped
Which three are true about the Oracle Optimizer? (Choose three.)
Overall explanation
Selectivity

The percentage of rows in the row set that the query selects, with 0
meaning no rows and 1 meaning all rows. Selectivity is tied to a query
predicate, such as WHERE last_name LIKE 'A%', or a combination of
predicates. A predicate becomes more selective as the selectivity value
approaches 0 and less selective (or more unselective) as the value
approaches 1.

Read Estimator

The optimizer choose the plan with the lowest cost among all considered
candidate plans. The optimizer uses available statistics to calculate cost.
For a specific query in a given environment, the cost computation
accounts for factors of query execution such as I/O, CPU, and
communication.

Read Query Optimizer Concepts

In Oracle Database, adaptive query optimization enables the

optimizer to make run-time adjustments to execution plans and discover
additional information that can lead to better statistics.

Read About Adaptive Query Optimization

Domain
Performance Tuning
Question 25Skipped
Which three are true about a whole database backup? (Choose three.)

Overall explanation
Use the RMAN BACKUP command to create
both consistent and inconsistent backups.

The RMAN BACKUP command supports backing up the following types of

files:

 Data files and control files

 Server parameter file
 Archived redo logs
 RMAN backups

Read About Consistent and Inconsistent RMAN Backups

When you execute the BACKUP command in RMAN, you create one or
more backup sets or image copies. By default, RMAN creates backup sets
regardless of whether the destination is disk or a media manager.

Note:

Data file backup sets are typically smaller than data file image copies and
take less time to write.

Read About Backup Sets

Domain
RMAN Backup and Recovery

Overall explanation
Pluggable database (PDBs) can be transported and plugged in to a
destination multitenant container database (CDB) which is on a different
platform than the source CDB. In addition to an RMAN backup of the PDB,
you need the metadata required to plug the PDB into the destination CDB.

The COMPATIBLE parameter on the source CDB and destination CDB must
be set to 12.2. The source CDB and the destination CDB must use
the same endian format.

To perform cross-platform transport of a closed PDB into a destination

CDB:

1. Perform the following steps on the source CDB:

a. Connect to the root as a common user with
the SYSDBA or SYSBACKUP privilege.
b. Close the PDB that needs to be transported.

The following statement closes the PDB hr_pdb .

1. CopyRMAN> ALTER PLUGGABLE DATABASE hr_pdb CLOSE IMMEDIATE;

.....

.....

Read Performing Cross-Platform Transport of a Closed PDB

Domain
Multitenant Architecture

Question 27Skipped
Which three are true about Audit policies in container databases (CDBs)?
Question 29Skipped
Application PDBs, SALES_APP1 and SALES_APP2, must be created and they
must access common tables of the SALES_APP application.

Examine these steps:

1. Install the SALES_APP application, including the common tables, in the

application root.

2. Install the SALES_APP application in the application root and the

common tables in both the CDB root and the application root.

3. Create an application seed.

4. Install the SALES_APP application in the application seed.

5. Create the SALES_APP1 and SALES_APP2 application PDBs.

6. Sync the SALES_APP1 and SALES_APP2 application PDBs with the
application root.

7. Sync the SALES_APP1 and SALES_APP2 application PDBs with the

application seed.

8. Sync the application seed with the application root.

Which are the minimum required steps in the correct sequence?

Overall explanation
If there is no application seed, still you can create the application PDBs
but it will create the PDBs using the main CDB's seed PDB PDB$SEED.

After that, you can sync up the application PDBs from the application root.

Domain
Multitenant Architecture

Question 30Skipped
How do you configure a CDB for local undo mode?

Overall explanation
You can change a CDB to local undo mode by issuing an ALTER DATABASE
LOCAL UNDO ON statement and restarting the database.

When a CDB is in local undo mode, each container has its own undo
tablespace for every instance in which it is open. Oracle Database
automatically creates an undo tablespace in any container in the CDB that
does not have one. If a PDB without an undo tablespace is cloned,
relocated, or plugged into a CDB that is configured to use local undo
mode, then Oracle Database automatically creates an undo tablespace for
the PDB the first time it is opened.

Read Configuring a CDB to Use Local Undo Mode

Domain
Multitenant Architecture
Question 31Skipped
Which three are true about interpreting Recovery Manager (RMAN) error
stacks returned to standard output? (Choose three.)
Overall explanation
In certain cases, Media Management messages may not be written to
sbtio.log file.

The sbtio.log contains information written by the media management

software, not Oracle Database. Thus, you must consult your media vendor
documentation to interpret the error codes and messages. If no
information is written to the sbtio.log, then contact your media manager
support to ask whether they are writing error messages in some other
location, or whether there are steps you must take to have the media
manager errors appear in sbtio.log.

Read Interpreting SBT 1.1 Media Management Errors

RMAN error stack should be read from the bottom up.

Read the messages from the bottom up, because this is the order in which
RMAN issues the messages. The last one or two errors displayed in the
stack are often the most informative.

Read Interpreting RMAN Error Stacks

If you LOG option on the RMAN command, the output will not show on
standard output and will go to the log file only.

Completed job information is in V$RMAN_STATUS and RC_RMAN_STATUS.

The current job information is in V$RMAN_OUTPUT.

When running RMAN from the command line, you can direct output to the
following places:

 Standard output
 A log file specified by LOG on the command line or the SPOOL LOG
command
 A file created by redirecting RMAN output (for example, in UNIX,
using the '>' operator)

Read Identifying Types of RMAN Message Output

Domain
RMAN Backup and Recovery

Question 32Skipped
Which three are true about patchsets? (Choose three.)
Overall explanation
RECOVERY AREA

Backs up recovery files created in the current and all previous fast
recovery area destinations. Backups can go to SBT and disk. To backup to
disk, you must use the TO DESTINATION syntax outlined in toDestSpec.

Recovery files are full and incremental backup sets, control file
autobackups, data file copies, and archived redo log files. If an archived
redo log file is missing or corrupted, then RMAN looks outside of the
recovery area for a good copy of the log that it can use for the backup.
Flashback logs, the current control file, and online redo log files are not
backed up.

By default, backup optimization is enabled for this command even

if the CONFIGURE BACKUP OPTIMIZATION setting is OFF. You can
disable backup optimization for BACKUP RECOVERY AREA by
specifying FORCE.

Note: If the fast recovery area is not enabled but was enabled previously,
then files created in the previous fast recovery area location are backed
up.

Read BACKUP

You can use the BACKUP BACKUPSET command to back up backup sets
produced by other backup jobs. You can also use BACKUP RECOVERY
AREA to back up recovery files created in the current and all
previous fast recovery area destinations.

Recovery files are full and incremental backup sets, control file
autobackups, data file copies, and archived redo logs. SBT and disk
backups are supported for BACKUP RECOVERY AREA. For disk backups of
the recovery files, you must use the TO DESTINATION option.

Read Backing Up RMAN Backups

Domain
RMAN Backup and Recovery

Overall explanation
If there is no application seed, still you can create the application PDBs
but it will create the PDBs using the main CDB's seed PDB PDB$SEED.

After that, you can sync up the application PDBs from the application root.

Read Creating an Application PDB

Domain
Multitenant Architecture

Question 35Skipped
Which three are true about Automatic Workload Repository (AWR)
snapshots? (Choose three.)

Overall explanation
To enable statistics gathering by AWR, set the STATISTICS_LEVEL
parameter to TYPICAL or ALL.

AWR snapshots are created automatically but you can create them
manually too.

The default retention is 8 days but you can alter it.

read Automatic Workload Repository

Domain
Automatic Workload Repository (AWR)
Overall explanation
Using an initialization parameter to increase the shared pool size fixes the
problem at the database level and improves performance for all sessions.
However, if a single SQL statement is not using a helpful index, then
changing the optimizer initialization parameters for the entire database
could harm overall performance.

Read SQL Tuning Tasks

You can enable automatic indexing by executing the following procedure

in the DBMS_AUTO_INDEX package:

EXEC DBMS_AUTO_INDEX.CONFIGURE('AUTO_INDEX_MODE','IMPLEMENT')

Read Automatic Indexing

Domain
Performance Tuning
Question 40Skipped
Examine this configuration: CDB1 is a container database running in
ARCHIVELOG mode. Multiple uncommitted transactions are running in
CDB1. Redo log groups 1 and 2 are INACTIVE. Redo log group 3 is the
CURRENT group. All members of redo log group 3 are lost before it is
archived. Examine these possible steps: 1. SHUTDOWN ABORT 2.
STARTUP NOMOUNT 3. STARTUP MOUNT 4. ALTER DATABASE MOUNT 5.
RESTORE DATABSE 6. RECOVER DATABASE NOREDO 7. RECOVER
DATABASE UNTIL AVAILABLE 8. RESTORE ARCHIVELOG ALL 9. ALTER
DATABSE OPEN 10.ALTER DATABASE OPEB RESETLOGS Choose the
minimum required steps in the correct order to recover the database.
Overall explanation
The Program Global Area (PGA) is a private memory region that contains
the data and control information for a server process. Only a server
process can access the PGA. Oracle Database reads and writes
information in the PGA on behalf of the server process. An example of
such information is the run-time area of a cursor. Each time a cursor is
executed, a new run-time area is created for that cursor in the PGA
memory region of the server process executing that cursor.

Note: Part of the run-time area can be located in the Shared Global Area
(SGA) when using shared servers.

For complex queries (such as decision support queries), a big portion of

the run-time area is dedicated to work areas allocated by memory
intensive operators, including:

 Sort-based operators, such as ORDER BY, GROUP BY, ROLLUP, and

window functions
 Hash-join
 Bitmap merge
  Bitmap create
 Write buffers used by bulk load operations

Read About the Program Global Area

Sizing the Program Global Area by Specifying an Absolute Limit

In automatic PGA memory management mode, Oracle Database attempts

to adhere to the PGA_AGGREGATE_TARGET value by dynamically
controlling the amount of PGA memory allotted to work areas. However,
PGA memory usage may exceed the PGA_AGGREGATE_TARGET setting at
times due to the following reasons:

 The PGA_AGGREGATE_TARGET setting acts as a target, and not a

limit.
 PGA_AGGREGATE_TARGET only controls allocations of tunable
memory.

Read Sizing the Program Global Area by Specifying an Absolute Limit

Domain
Database Memory and Process Architecture
Question 42Skipped
Which three are true about RMAN duplexed backup sets or image copies?
(Choose three.)
Question 44Skipped
The HR_ROOT application container must support the execution of a query
on a table shared by application local PDBs PDB1 and PDB2, and remote
PDB PDB3. Which three are true? (Choose three.)
Overall explanation
You can create a proxy PDB in an application container. To do so, the
referenced PDB must be an application root or an application PDB in an
application container in a different CDB. The database link must be
created in the root of the application container that will contain the proxy
PDB, and the database link connects either to the root of remote
application container or to the remote referenced application PDB.

Read About Creating a Proxy PDB

Overall explanation
Only PDBs open in MIGRATE open will be upgraded.

For all PDBs, ensure that the status is set to MIGRATE.

Read Upgrading Multitenant Container Databases In Parallel

Domain
Upgrades

Question 46Skipped
Which three actions will add a resource to an Oracle Restart
configuration? (Choose three.)

Overall explanation
Any resource you create via SQL or within a database will not get added to
Clusterware automatically.

If you install Oracle Restart and then create your database with Database
Configuration Assistant (DBCA), DBCA automatically adds the database to
the Oracle Restart configuration. When DBCA then starts the database,
the required dependencies between the database and other components
(for example disk groups in which the database stores data) are
established, and Oracle Restart begins to manage the database.

You can manually add and remove components from the Oracle Restart
configuration with SRVCTL commands. For example, if you install Oracle
Restart onto a host on which a database is already running, you can use
SRVCTL to add that database to the Oracle Restart configuration. When
you manually add a component to the Oracle Restart configuration and
then start it with SRVCTL, Oracle Restart begins to manage the
component, restarting it when required.

Read Oracle Restart Configuration

Domain
Oracle Software Installation
Question 48Skipped
Which three are true about Automatic Workload Repository (AWR) and
Automatic Database Diagnostic Monitor (ADDM) in an Oracle multitenant
environment? (Choose three.)
Overall explanation
Limitations of Recovering Tables and Table Partitions from RMAN
Backups

Recovering tables and table partitions from RMAN backups by using the
RECOVER command is subject to certain limitations.

The limitations include the following:

 Tables and table partitions belonging to SYS schema cannot be

recovered.
  Tables and table partitions from SYSTEM and SYSAUX
tablespaces cannot be recovered.
 Tables and table partitions on standby databases cannot be
recovered.
 Tables with named NOT NULL constraints cannot be recovered with
the REMAP option.

Read Limitations of Recovering Tables and Table Partitions from RMAN

Backups

As part of the recovery process, RMAN creates an auxiliary database that

is used to recover tables or table partitions to the specified point in time.

Read Basic Concepts of Recovering Tables and Table Partitions from

RMAN Backups

Recovering tables and table partitions from RMAN backups is useful in the
following scenarios:

 You need to recover a very small number of tables to a particular

point in time. In this situation, TSPITR is not the most effective
solution because it moves all the objects in the tablespace to a
specified point in time.
 You need to recover tables that have been logically corrupted or
have been dropped and purged.
 Flashback Table is not possible because the desired point-in-time is
older than available undo.
 You want to recover data that is lost after a DDL operation
modified the structure of tables. Using Flashback Table is not
possible because a DDL was run on the tables between the desired
point in time and the current time. Flashback Table cannot rewind
tables through structural changes such as a truncate table
operation.

Read Purpose of Recovering Tables and Table Partitions from RMAN

Backups

Domain
RMAN Backup and Recovery
Overall explanation
Oracle ASM instances mount disk groups to make Oracle ASM files
available to database instances.

The Oracle ASM instance manages the metadata and provides space
allocation for the Oracle ASM files.

Every Oracle ASM disk is divided into allocation units (AU).

An allocation unit is the fundamental unit of allocation within a disk group.
A file extent consists of one or more allocation units. An Oracle ASM file
consists of one or more file extents.

Read About Oracle ASM Instances

Domain
Oracle Automatic Storage Management (Oracle ASM)
Overall explanation
Oracle Fleet Patching and Provisioning enables mass deployment and
maintenance of standard operating environments for databases, clusters,
and user-defined software types.

Oracle FPP enables you to install clusters, and provision, patch, scale, and
upgrade Oracle Grid Infrastructure, Oracle Restart, and Oracle Database
homes. The supported releases are 11.2.0.4, 12.1, 12.2, 18c, and later
releases. You can also provision applications and middleware using Oracle
Fleet Patching and Provisioning.

Read About Deploying Oracle Grid Infrastructure Using Oracle Fleet

Patching and Provisioning

Domain
Oracle Fleet Patching and Provisioning
Overall explanation
An RPM-based installation performs preinstallation checks, extracts the
database software, reassigns ownership of the extracted software to the
preconfigured user and groups, maintains the Oracle inventory, and
executes all root operations required to configure the Oracle Database
software for a single-instance Oracle Database creation and configuration.

The RPM-based installation process provides you with the option to create
a database with the default settings using the
/etc/init.d/oracledb_ORCLCDB-19c service configuration script.

read About RPM-Based Oracle Database Installation

Domain
Oracle Software Installation
Overall explanation
Creating an Application Seed From an Application PDB

the following statement creates the application seed from the application
root, opens the application seed, closes the application seed, and opens
the application seed in open read-only mode:

CREATE PLUGGABLE DATABASE AS SEED FROM salesapppdb;

ALTER PLUGGABLE DATABASE salesact$SEED OPEN;

ALTER PLUGGABLE DATABASE CLOSE IMMEDIATE;

ALTER PLUGGABLE DATABASE OPEN READ ONLY;

Because the application container name is salesact, the application seed

name is salesact$SEED.

Read Creating an Application Seed

Creating an Application PDB

You create an application PDB by running the CREATE PLUGGABLE

DATABASE statement with an application root as the current container.

You can create application PDBs using the same SQL statements that you
use to create PDBs in the CDB root. The newly created PDB is an
application PDB when the CREATE PLUGGABLE DATABASE statement is
run in an application root. The statement must be run in an application
root and has an explicit dependency on the application database defined
in that application root.

Read Creating an Application PDB

Domain
Multitenant Architecture
Overall explanation
Starting with Oracle Grid Infrastructure 19c, the feature formerly known
as Rapid Home Provisioning (RHP) is now Oracle Fleet Patching and
Provisioning (Oracle FPP).

Oracle Fleet Patching and Provisioning (Oracle FPP) enables mass

deployment and maintenance of standard operating environments for
databases, clusters, and user-defined software types. With Oracle Fleet
Patching and Provisioning, you can also install clusters and provision,
patch, scale, and upgrade Oracle Grid Infrastructure and Oracle Database
11g release 2 (11.2), and later. Additionally, you can provision
applications and middleware.

Read Oracle Fleet Patching and Provisioning Overview

Domain
Oracle Fleet Patching and Provisioning

Overall explanation
If the target control file is mounted and the catalog database is available
at command execution, then RMAN automatically resynchronizes the
recovery catalog as needed when you use RMAN commands. RMAN
performs a full resynchronization after structural changes to database
(adding or dropping database files, creating new incarnation, and so on)
or after changes to the RMAN persistent configuration.

Read RESYNC CATALOG

Domain
RMAN Backup and Recovery

Overall explanation
If an index-only tablespace is lost, you can rebuild the indexes after
creating a new tablespace with the same name.

Domain
Oracle Database Concepts
Overall explanation
MAX_DATAPUMP_JOBS_PER_PDB determines the maximum number of
concurrent Oracle Data Pump jobs per PDB.

Read MAX_DATAPUMP_JOBS_PER_PDB

KEEP_READ_ONLY: Indicates that you want the transportable data files to

remain in read-only mode. If you use KEEP_READ_ONLY, then you enable
data files to be plugged into one or more additional compatible databases
for read-only access.TRANSPORTABLE=KEEP_READ_ONLY: If specified,
then data files remain in read-only mode. As a result of this setting, the
tables containing TSTZ column data cannot be updated, and are dropped
from the import. In addition, data file bitmaps cannot be rebuilt.

TRANSPORTABLE=NO_BITMAP_REBUILD: If specified, then if it becomes

necessary during the import to update tables containing TSTZ column
data, then the data files are placed into read/write mode.

Read TRANSPORTABLE

Domain
Transportable Tablespace

Question 61Skipped
Examine this configuration: CDB1 and CDB2 are two container databases.
PDB1 is a pluggable database in CDB1. PDB1_C1_SRV is a service for
PDB1. CDB1_LINK is a database link in CDB2 referring to PDB1. CDB2 is
also an entry in tnsnames.ora pointing to the CDB2 database default
service. You execute these commands successfully: $ sqlplus
sys/oracle_4U@cdb2 as sysdba SQL> CREATE PLUGGABLE DATABASE
PDB1 FROM PDB1@CDB1_LINK
SERVICE_NAME_CONVERT=('PDB1_C1_SRV','PDB1_C2_SRV'); Which two
are true? (Choose two.)
 Overall explanation
DBCA has option to create container database or not.

1. dbca -createDatabase
2. -responseFile | (-gdbName,-templateName)
3. -responseFile response_file_directory
4. -gdbName global_database_name
5. -templateName database_template_name
6. [-sid database_system_identifier]
7. [-createAsContainerDatabase {true | false}

Read createDatabase

DBCA can be launched by the Oracle Universal Installer (OUI), depending

upon the type of install that you select. You can also launch DBCA as a
standalone tool at any time after Oracle Database installation.
You can run DBCA in interactive mode or noninteractive/silent mode.
Interactive mode provides a graphical interface and guided workflow for
creating and configuring a database. Noninteractive/silent mode enables
you to script database creation. You can run DBCA in noninteractive/silent
mode by specifying command-line arguments, a response file, or both.

Read About Creating a Database with DBCA

Domain
Database Creation
Overall explanation
Gold Images can be used to install databases as well as grid and single-
instance as well as cluster configurations.

Read About Oracle Fleet Patching and Provisioning

Domain
Oracle Software Installation

Question 64Skipped
You want to transport the UNIVERSITY tablespace from one database to
another. The UNIVERSITY tablespace is currently open read/write.

The source and destination platforms have the same endian format.
Examine this list of steps: 1. Make the UNIVERSITY tablespace read-only
on the source system. 2. Export the UNIVERSITY tablespace metadata
using EXPDP. 3. Create a cross-platform backup set from the UNIVERSITY
tablespace on the source system, using an RMAN command that includes
the DATAPUMP clause. 4. Copy the cross-platform backup sets to the
destination system. 5. Copy the Data Pump dump set from the source to
the destination system. 6. Restore the cross-platform backup set on the
destination system using an RMAN command that includes the DATAPUMP
clause. 7. Import the UNIVERSITY tablespace metadata using IMPDP. 8.
Make the UNIVERSITY tablespace read/write on the destination system.

Which are the minimum number of steps required, in the correct order, to
transport the UNIVERSITY tablespace?
Overall explanation
Using RMAN BACKUP with DATAPUMP feature, there is no need to export
metadata and covert files separately.

On the source database, use the DATAPUMP clause in the BACKUP

command to create the metadata required to plug tablespaces in to the
target database. The metadata is stored in a Data Pump export dump file
as a separate backup set. Use this backup set to plug the transported
tablespaces in to the target database.

Read About the Data Pump Export Dump File Used for Cross-Platform
Tablespace Transport

BACKUP

FOR TRANSPORT

FORMAT '/tmp/xplat_backups/db_trans.bck'

DATABASE;
Read Steps to Transport a Database to a Different Platform Using Backup
Sets

Domain
RMAN Backup and Recovery

Overall explanation
When connected to root CDB, you can take a backup of just CDB$ROOT or
selective/all PDBs or the whole database (CDB$ROOT and PDBs).

Connected to PDB, you cannot backup archive logs.

Read Backing Up and Recovering CDBs and PDBs and Backing Up a Whole
CDB and Backing Up PDBs with RMAN and Backing Up Tablespaces and
Data Files in a PDB

Domain
RMAN Backup and Recovery
Question 66Skipped
Which three are true about using Database Upgrade Assistant (DBUA) to
upgrade a database? (Choose three.)
Overall explanation
The purpose of multisection backups is to enable RMAN channels to back
up a single large file in parallel. RMAN divides the work among multiple
channels, with each channel backing up one file section in a file. Backing
up a file in separate sections can improve the performance of backups of
large data files.

To make a multisection backup:

1. Start RMAN and connect to a target database and recovery catalog

(if used).
2. If necessary, configure channel parallelism so that RMAN can make
the backup parallel.
3. Execute BACKUP with the SECTION SIZE parameter.

Read Dividing the Backup of a Large Data File into Sections

Domain
RMAN Backup and Recovery

Overall explanation
To flash back a table to an earlier SCN or timestamp, you must have
either the FLASHBACK object privilege on the table or the FLASHBACK
ANY TABLE system privilege. In addition, you must have the READ or
SELECT object privilege on the table, and you must have the INSERT,
DELETE, and ALTER object privileges on the table.

Row movement must be enabled for all tables in the Flashback list
unless you are flashing back the table TO BEFORE DROP. That operation is
called a flashback drop operation, and it uses dropped data in the recycle
bin rather than undo data. Refer to row_movement_clause for information
on enabling row movement.

Read FLASHBACK TABLE Prerequisites

Domain
Flashback Technologies

Overall explanation
Because failure information is not stored in the database itself, the
database does not need to be open or mounted for you to access it. You
can view failures when the database is started in NOMOUNT mode.

Read About Failures

You can use CHANGE FAILURE to change the status of an open failure to
CLOSED if you have fixed it manually. However, it makes sense to use
CHANGE FAILURE ... CLOSED only if for some reason the failure was not
closed automatically. If a failure still exists when you use CHANGE to close
it manually, then Data Recover Advisor re-creates it with a different failure
ID when the appropriate data integrity check is executed.

Read About the Failure Status

CHANGE FAILURE is used to change the status too, not just priority.

You can also invoke a data integrity check proactively. You can execute
the check through the Health Monitor, which detects and stores failures in
the same way as when the checks are invoked reactively. You can also
check for block corruption with the VALIDATE and BACKUP VALIDATE
commands.

Read About Data Integrity Checks

Domain
Data Recovery Advisor
Overall explanation
A backup set contains the data from one or more data files, archived redo
logs, control files, or server parameter file. Backup sets, which are only
created and accessed through RMAN, are the only form in which RMAN
can write backups to media managers such as tape drives and tape
libraries.
A backup set contains one or more binary files in an RMAN-specific
format. Each of these files is known as a backup piece. A backup set can
contain multiple data files. For example, you can back up 10 data files
into a single backup set consisting of a single backup piece. In this case,
RMAN creates one backup piece as output. The backup set contains only
this backup piece.

If you specify the SECTION SIZE parameter on the BACKUP command,

then RMAN produces a multisection backup. This is a backup of a single
large file, produced by multiple channels in parallel, each of which
produces one backup piece. Each backup piece contains one file section
of the file being backed up.

For non-multisection backups, RMAN only records backup sets in the

repository that complete successfully. There is no such thing as a partial
backup set. This differs from an unsuccessful multisection backup, where
it is possible for RMAN metadata to contain a record for a partial backup
set. In the latter case, you must use the DELETE command to delete the
partial backup set.

Read About Backup Sets

Domain
Database Creation
Overall explanation
DB_CACHE_SIZE - This parameter is optional for pluggable databases
(PDBs). When this parameter is set for a PDB, it indicates a possible
minimum value for the PDB usage of the memory pool.

Read DB_CACHE_SIZE

SHARED_POOL_SIZE - This parameter is optional for pluggable databases

(PDBs). When this parameter is set for a PDB, it indicates a possible
minimum value for the PDB usage of the memory pool.
Read SHARED_POOL_SIZE

SGA_TARGET - This parameter is optional for pluggable databases (PDBs).

When this parameter is set for a PDB, it specifies the maximum SGA that
the PDB can use at any time. When this parameter is not set at the PDB
level, the PDB has no limit for the amount of SGA it can use, other than
the CDB's SGA size.

Read SGA_TARGET

Domain
Database Memory and Process Architecture

Question 75Skipped
Your container database, CDB1, is in local undo mode. You successfully
execute this command while connected to CDB1: CREATE PLUGGABLE
DATABASE pdb1 ADMIN USER pdb1_admin IDENTIFIED BY pdb123
ROLES=(CONNECT)
CREATE_FILE_DEST='/u01/app/oracle/oradata/cdb1/pdb1'; Which three are
true about PDB1? (Choose three.)
Question 76Skipped
Which three are true about using an RMAN Recovery Catalog with a
pluggable database (PDB) target connection in Oracle Database 19c and
later releases? (Choose three.)
Overall explanation
A Virtual Private Catalog is an optional feature to allow the separation of
duties for different databases.

A virtual private catalog is a set of security policies that restrict user

access to a subset of a base recovery catalog.

The virtual private catalog is created automatically when catalog

privileges are granted to the virtual private catalog owner.

A Virtual Private Catalog can be a container database or a container

database.

Read Separating the Recovery Catalog from the Target Database

Read CREATE CATALOG

Domain
RMAN Backup and Recovery
Overall explanation
Starting 19c, you can flashback a PDB from a restore point even if it is not
clean.

When using restore points, you can perform a flashback database

operation either to a CDB restore point, PDB restore point, PDB clean
restore point, or PDB guaranteed restore point.

Read Performing a Flashback Database Operation for PDBs

Domain
Flashback Technologies
Overall explanation
OSASM OS group is used for Oracle ASM instance and it is not needed for
database installation.

Read Operating System Groups Created During Oracle Database

Installation

Domain
Oracle Software Installation
Overall explanation
Oracle Grid Infrastructure for a standalone server is a version of Oracle
Grid Infrastructure that supports single instance databases. This support
includes volume management, file system, and automatic restart
capabilities. Oracle Grid Infrastructure for a standalone server includes
Oracle Restart and Oracle Automatic Storage Management. Oracle
combined the two infrastructure products into a single set of binaries that
is installed into an Oracle Restart home.

Read About Oracle Grid Infrastructure for a Standalone Server

CSS is part of Clusterware so it runs from Grid Infrastructure home.

Cluster Synchronization Services (CSS): Manages the cluster configuration

by controlling which nodes are members of the cluster and by notifying
members when a node joins or leaves the cluster. If you are using
certified third-party clusterware, then CSS processes interface with your
clusterware to manage node membership information.

The cssdagent process monitors the cluster and provides I/O fencing. This
service formerly was provided by Oracle Process Monitor Daemon
(oprocd), also known as OraFenceService on Windows. A cssdagent failure
may result in Oracle Clusterware restarting the node.

Read The Cluster Ready Services Technology Stack

Domain
Oracle Grid Infrastructure / Clusterware