D

Overall explanation
RMAN must be connected as AUXILIARY to the instance of the duplicate
database. The instance of the duplicate database is called the auxiliary
instance. The auxiliary instance must be started with the NOMOUNT option.

RMAN uses an auxiliary instance to create the duplicate database. You must
prepare the auxiliary instance before you begin the duplication.

Duplicating Databases
A subset of the target database can be duplicated.

Duplicating a Subset of the Source Database Tablespaces

A backup can be used to duplicate the database but it's not mandatory.

A connection to the target database instance is not always required as a

duplicate can be run using backups as well.

Backup-Based Duplication Without a Target Database and Recovery Catalog

Connection

A duplicate can be run via push or pull methods.

Active Database Duplication Using Image Copies

In this method, RMAN connects as TARGET to the source database and as

AUXILIARY to the auxiliary instance. The source database then transfers the
required database files over the network to the auxiliary instance. This
method is referred to as the push-based method of active database
duplication.

Active Database Duplication Using Image Copies

Active Database Duplication Using Backup Sets

Using backup sets to perform active database duplication is also known as

the pull-based method of active database duplication.

In this method, RMAN connects as TARGET to the source database and as

AUXILIARY to the auxiliary instance. The auxiliary instance then connects to
the source database through Oracle Net Services and retrieves the required
database files, over the network, from the source database.

Active Database Duplication Using Backup Sets

Question 2Skipped
Which two are true about creating pluggable databases (PDBs) using
snapshots in Oracle 19c and later releases? (Choose two.)

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 is always a full copy of the source PDB. - FALSE

A PDB snapshot is always a sparse copy of the source PDB. - FALSE

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

A snapshot copy PDB depends on a storage snapshot which can only be

stored on specific file systems. - TRUE

See the doc User Interface for PDB Cloning.

A PDB snapshot is not created from a storage snapshot. So, it is not related
to storage snapshots anyway.

A PDB snapshot depends on a storage snapshot which can be stored on any

file system. - FALSE

A PDB snapshot depends on a storage snapshot which can only be stored on

specific file systems. - FALSE
A snapshot copy PDB depends on a storage snapshot which can be stored on
any file system. - FALSE

A snapshot copy PDB can be created from a stand-alone clone PDB. - TRUE

Question 3Skipped
Which four are true about a Recovery Manager (RMAN) duplication without a
TARGET connection? (Choose four.)
Overall explanation
The question is about Recovery Manager (RMAN) duplication without a
TARGET connection.
For backup-based duplication of databases without a connection to the
target database, RMAN cannot determine whether the source database was
in NOARCHIVELOG mode. Therefore, you must use the NOREDO option when
the source database was in NOARCHIVELOG mode when the backups were
taken. You can also use the NOREDO option when you do not want to apply
archived redo log files to a consistent backup.

Read Backup-Based Duplication

The UNDO TABLESPACE clause is mandatory in the below 2 cases:

If No Target and No Recovery Connection

OR

Target Connection but target is closed

Then, if you duplicate a subset of tablespaces, and if the source database is

not open, then any duplicated tablespaces with undo segments must be
listed in the UNDO TABLESPACE clause.

Read Prerequisites for Three Modes of Backup-Based Duplication

As there is no target connection, RMAN will not push across the network. It
will be restored from backups via RMAN.

Question 4Skipped
Which two are true about changing the LOCAL_UNDO_ENABLED property to
false in a CDB? (Choose two.)
Overall explanation
Only a proper common user can create an undo tablespace in CDB$ROOT.
That is correct all the time.

Once LOCAL_UNDO_ENABLED is set to false, PDBs will not automatically

begin to use CDB's undo tablespaces. Rather, PDBs have to be restarted.

CDB$ROOT can have any number of undo tablespaces but only one can be
used by a given database instance. That is correct all the time.

After switching to shared undo mode, PDB-level undo tablespaces can still
stay there and it's not mandatory to drop them.

When in shared undo mode, the CDB ignores any local undo tablespaces that
were created when it was in local undo mode. Oracle recommends that you
delete the unused local undo tablespaces.

Configuring a CDB to Use Shared Undo Mode

If LOCAL_UNDO_ENABLED is set to false, then if the current container is not
the CDB root, an attempt to create an undo tablespace will fail and return an
error.

Question 5Skipped
Which three actions are performed by Database Upgrade Assistant (DBUA)?
(Choose three.

Overall explanation
The following is a list of examples of DBUA checks, and of actions that DBUA
performs on the database:
  Empty database recycle bin.
 Identify invalid objects.
 Identify deprecated and desupported initialization parameters.
 Identify time zone data file version.

Read Using DBUA to Upgrade the Database on Linux, Unix, and Windows
Systems

DBUA uses the following logic to modify or create new required tablespaces:

 If the data files are auto-extensible and have enough disk space to
grow, then DBUA continues with the upgrade.
 If the data files are not auto-extensible, then DBUA prompts you and
makes the files auto-extensible.
 If the tablespaces are auto-extensible and the MAXSIZE initialization
parameter needs adjustment, then DBUA prompts you to for this
adjustment, and adjusts the MAXSIZE parameter.
 If there is not enough disk space to grow, then DBUA prompts you to
create space by adding more data files. DBUA does not automatically
add new data files, because DBUA cannot determine where to create
the files.

Read Upgrade Scripts Started by DBUA

Question 6
Your container database, CDB1, has an application container, HR_ROOT, with
an application PDB, HR_PDB1. You have the required privilege to clone
HR_PDB1 to container database CDB2, which does not contain HR_ROOT.
Which two are always true? (Choose two.)
Overall explanation
PDB Cloning can be done via dbca or
CREATE PLUGGABLE DATABASE command.

The following prerequisites must be met:

 A database link must enable a connection from the destination CDB

(the CDB to which the PDB is being cloned) to the PDB in the source
CDB.
 The database link can connect as a common user to the root of
the source CDB, or as a common or local user to the source PDB. The
source PDB can be either a standard PDB or application PDB.
 The user account specified in the database link must have either of the
following privileges:
 The CREATE PLUGGABLE DATABASE privilege, granted either
commonly or locally, on the source PDB
 The SYSOPER privilege

After you create the PDB, it is in mounted mode, and its status is NEW.

Read Cloning a Remote PDB: Basic Steps

Question 7
Which two are true about flashback features in Oracle Database 19c and
later releases? (Choose two.)

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

Question 8Skipped
You are managing this configuration: CDB1 is a container database. PDB1
and PDB2 are two pluggable databases in CDB1. USER1.EMP is a table in
PDB1 and USER2.DEPT is a table in PDB2. CDB1 user SYS executes these
commands after connecting successfully to PDB2:
Overall explanation
Changing the session from one PDB to another doesn't commit the DMLs in
the previous PDB session.

A DML on a new PDB session is not allowed if you didn't rollback/commit the
DML on the previous PDB. It will give error.

Question 9Skipped
Which two are true about data movement between a non-CDB and a PDB
using Data Pump? (Choose two.)

Overall explanation
Tablespaces are never created automatically in the export/import process.

PDB is not created automatically. It must be pre-created.

Moving data from a PDB to a non-CDB - there are many ways like TTS,
conventional export and import, DataPump export and import, SQL* Loader,
cloning, etc.

As non-CDBs have only conventional users and PDBs have local users,
moving schemas from non-CDB to PDB will try to convert conventional users
to local users and vice versa.

Read Cloning a PDB or Non-CDB

Question 10
Which three are true about RMAN persistent configuration settings,
administration, and their effects? (Choose three.)
Overall explanation
Maintaining the Control File Repository

RMAN is designed to work without a recovery catalog. If you choose not to

use a recovery catalog, however, then the control file of each target
database is the exclusive repository for RMAN metadata.

The CONFIGURE command always stores a configuration for a target

database in the target database control file. If you use RMAN with a recovery
catalog, then RMAN also stores persistent configuration settings for each
registered database in the catalog.

Read Maintaining the Control File Repository and CONFIGURE

The RMAN SHOW ALL command shows all parameters.

For example, run SHOW ALL as shown in the following example (sample
output included). The output includes both parameters that you have
changed and those that are set to the default. The configuration is displayed
as the series of RMAN commands required to re-create the configuration. You
can save the output in a text file and use this command file to re-create the
configuration on the same or a different database.

Read Showing and Clearing Persistent RMAN Configurations

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

Overall explanation
By default, an AWR snapshot is created every hour and retained for 8 days,
and its collection level is controlled by STATISTICS_LEVEL (ALL | TYPICAL).

Read Managing Snapshots

Read Enabling the Automatic Workload Repository

Oracle Database uses the SYSAUX tablespace to store AWR data by default.
Starting with Oracle Database 19c, you can specify any other tablespace to
store the AWR data, so as to avoid overloading the SYSAUX tablespace.

Read Space Consumption

Question 12Skipped
Examine this configuration: CDB1 is a container database. PDB1 and
PDB2 are pluggable databases in CDB1. You execute these
commands successfully:

Which two are true? (Choose two.)

Overall explanation
As the root database itself is in the mounted state, all pluggable databases
will be in the MOUNTED state only.
Redo logs open when the container database is in READ WRITE or
READ ONLY WITH APPLY mode.

Domain
Multitenant Architecture

Question 13Skipped
A database is configured in ARCHIVELOG mode. A full RMAN backup exists
but no control file backup to trace has been taken. A media failure has
occurred. In which two scenarios is incomplete recovery required? (Choose
two.)
Overall explanation
You can not do complete recovery if:
 You have lost all copies of the control file.
 You have lost archive logs after the last good backup.

Read Overview of Complete Database Recovery

If you restore the control file from backup, then you must perform media
recovery of the whole database and then open it with the OPEN RESETLOGS
option, even if no data files must be restored.

Read Identifying a Lost Control File

If the lost group is Current then it is the log that Oracle is currently writing
to. Attempt to clear the log; if impossible, then you must restore a backup
and perform incomplete recovery up to the most recent available log.

Read Recovering After the Loss of All Members of an Online Redo Log Group

Domain
RMAN Backup and Recovery

Question 14Skipped
Which three are true about the SQL Tuning Advisor? (Choose three.)
Overall explanation
Use SQL Tuning Advisor to obtain recommendations for improving
performance of high-load SQL statements, and prevent regressions by only
executing optimal plans.

Tuning recommendations include:

 Collection of object statistics

 Creation of indexes
 Rewriting SQL statements
 Creation of SQL profiles
 Creation of SQL plan baselines

Read Purpose of SQL Tuning Advisor

During structural analysis, Automatic Tuning Optimizer tries to identify

syntactic, semantic, or design problems that can lead to suboptimal
performance. The goal is to identify poorly written SQL statements and to
advise you how to restructure them.

Read SQL Structural Analysis

Domain
Database Performance Tuning and Dynamic Performance Views

Question 15Skipped
Which three are located by using environment variables? (Choose three.)

Overall explanation
The Optimal Flexible Architecture (OFA) compliant path is dictated by
the environment variable ORACLE_BASE.

The location of Oracle Net Services configuration files is dictated by

the environment variable TNS_ADMIN.

The list of ASM disk group names is dictated by the ASM instance parameter
ASM_DISKGROUPS.

Default directories for temporary files used by temporary tablespaces are

dictated by the database parameter DB_CREATE_FILE_DEST.

The temporary disk space is dictated by the environment variable

TMPDIR.

The maximum number of database files is dictated by the database

parameter DB_FILES.

Optimal Flexible Architecture

Enabling the Creation and Use of Oracle Managed Files

Domain
Optimal Flexible Architecture and Oracle Managed Files
Overall explanation
By definition, the common objects can be present in CDB$ROOT or
application root. But, you can not create your own common objects in
CDB$ROOT while you can do so in the application root.

Application common objects can be linked in 3 ways, not just metadata-

linked.

Creation of Application Common Objects

To create common objects, connect to an application root, and then execute
a CREATE statement that specifies a sharing attribute.

 Metadata-Linked Application Common Objects

A metadata link is a dictionary object that supports referring to, and
granting privileges on, common metadata shared by all PDBs in the
application container.
  Data-Linked Application Common Objects
A data-linked object is an object whose metadata and data reside in
an application root, and are accessible from all application PDBs in this
application container.
 Extended Data-Linked Application Objects
An extended data-linked object is a hybrid of a data-linked object
and metadata-linked object.

Read Application Common Objects

Domain
Multitenant Architecture

Overall explanation
You can improve backup performance by adjusting the level of
multiplexing, which is number of input files simultaneously read and then
written into the same RMAN backup piece.
Read Tuning the Read Phase

When reading from an ASM disk group, use asynchronous disk I/O if
possible. Also, if a channel reads from a raw device managed with a
volume manager, then asynchronous disk I/O also works well.

Read Synchronous and Asynchronous Disk I/O

For RMAN, tuning LARGE_POOL_AREA is useful, not buffer cache.

Domain
RMAN Backup and Recovery

Question 18Skipped
Which two are true about SQL Performance Analyzer (SPA)? (Choose two.)
Overall explanation
Comparing Performance Measurements

SQL Performance Analyzer compares the performance of SQL statements

before and after the change and produces a report identifying any changes
in execution plans or performance of the SQL statements.

SQL Performance Analyzer measures the impact of system changes both on

the overall execution time of the SQL workload and on the response time of
every individual SQL statement in the workload. By default, SQL Performance
Analyzer uses elapsed time as a metric for comparison. Alternatively, you
can choose the metric for comparison from a variety of available SQL run-
time statistics, including:

 CPU time
 User I/O time
 Buffer gets
 Physical I/O
  Optimizer cost
 I/O interconnect bytes
 Any combination of these metrics in the form of an expression

Comparing Performance Measurements

Each SQL statement in the SQL tuning set is executed separately from other
SQL statements, without preserving their initial order of execution or
concurrency.

Measuring the Pre-Change SQL Performance

Overall explanation
Depending on if this is the first time Oracle software is being installed on
your system and on the products that you are installing, you may have to
create several operating system groups and users.

However, if you use Oracle Preinstallation RPM to provision your Linux

operating system for an Oracle Grid Infrastructure or Oracle Database
installation, then it configures an Oracle database installation owner
(oracle), an Oracle Inventory group (oinstall), and an Oracle administrative
privileges group (dba).

Read Creating Required Operating System Groups and Users

Domain
Oracle Software Installation
Overall explanation
RMAN encryption keys are stored in a database keystore. - TRUE

Transparent encryption

 This is the default mode and uses the Oracle software keystore. A
keystore is a password-protected container used to store a
Transparent Data Encryption (TDE) key. In previous releases, this
container was referred to as a wallet.

Read About Backup Encryption

The SET ENCRYPTION command overrides encryption settings specified by

the CONFIGURE ENCRYPTION command. - TRUE

Override the encryption settings specified by the CONFIGURE ENCRYPTION

command. For example, you can use SET ENCRYPTION OFF to create an
unencrypted backup, even though a database is configured for encrypted
backups.

Read Configuring RMAN Backup Encryption Modes

Password encryption can be persistently configured using the CONFIGURE

ENCRYPTION command. - FALSE

Password encryption is useful for backups that are restored at remote

locations, but which must remain secure in transit. Password encryption
cannot be persistently configured. You do not need to configure an
Oracle keystore if password encryption is used exclusively.

Read Password Encryption of Backups

Domain
RMAN Backup and Recovery
Overall explanation
The Oracle Preinstallation RPM can be used to configure the Oracle database
installation owner, the Oracle Inventory group, and an Oracle administrative
privileges group. - TRUE

Depending on if this is the first time Oracle software is being installed on

your system and on the products that you are installing, you may have to
create several operating system groups and users.
However, if you use Oracle Preinstallation RPM to provision your Linux
operating system for an Oracle Grid Infrastructure or Oracle Database
installation, then it configures an Oracle database installation owner
(oracle), an Oracle Inventory group (oinstall), and an Oracle administrative
privileges group (dba).

Read Creating Required Operating System Groups and Users

Oracle Database installation on Linux can be done before or after the Grid
Infrastructure installation.

If you plan to use Oracle Restart or Oracle ASM, then you must install
Oracle Grid Infrastructure for a standalone server before you install and
create the database. Otherwise, you must manually register the database
with Oracle Restart.

Read Installing the Oracle Database Software

Domain
Oracle Software Installation
Overall explanation
Basic concepts:

Automatic Shared Memory Management -> Only components within SGA are
auto-managed by Oracle. PGA remains a separate component.

Automatic Memory Management -> SGA as well as PGA, both are auto-
managed by Oracle. So, memory can be allocated/deallocated between
SGA and PGA.

Automatically tuned and resized System Global Area components

will NOT always revert to their initial sizes after an instance restart. Rather,
in the case of spfile being in use, the dynamically changed values are written
to the spfile with *. prefix which will be starting value of the memory
components after an instance restart.

The total memory that the instance uses remains relatively constant, based
on the value of MEMORY_TARGET, and the instance automatically distributes
memory between the system global area (SGA) and the instance program
global area (instance PGA). As memory requirements change, the instance
dynamically redistributes memory between the SGA and instance PGA.

Read About Automatic Memory Management

Domain
Managing Memory
Overall explanation
FLASHBACK DATABASE uses flashback logs and archived logs, not undo, and
brings back the whole database.

Read FLASHBACK DATABASE

FLASHBACK QUERY uses undo, not redo or archived logs.

Read Using Oracle Flashback Query (SELECT AS OF)

FLASHBACK TABLE ... to SCN/TIMESTAMP uses undo and brings back the
whole table.
Read FLASHBACK TABLE

FLASHBACK TABLE ... TO BEFORE DROP uses recycle bin and brings back
the indexes too but it does not recover referential constraints.

Oracle Flashback Drop enables you to reverse the effects of dropping

(deleting) a table, returning the dropped table to the database along with
dependent objects such as indexes and triggers. This feature stores dropped
objects in a recycle bin, from which they can be retrieved until the recycle
bin is purged, either explicitly or because space is needed.

Read Recover a Dropped Table Using Oracle Flashback Drop

Domain
Flashback Technologies

Overall explanation
For metric alert event types, an event (metric alert) is raised based on the
metric threshold values. These metric alert events are called stateful alerts.
For example, tablespace usage > 85%.

For those metric alert events that are not tied to the state of a monitored
system (for example, snapshot too old, or resumable session suspended ),
these alerts are called stateless alerts. Because stateless alerts are not
cleared automatically, they need to be cleared manually. You can perform a
bulk purge of stateless alerts using the clear_stateless_alerts EM CLI verb.

Clearing Stateless Alerts for Metric Alert Event Types

Domain
Database Monitoring

Overall explanation
As PDB is being plugged into the same CDB, PDB's data files are present in
their original location.

Unplugging a PDB from a CDB

ALTER PLUGGABLE DATABASE salespdb UNPLUG INTO

'/oracle/data/salespdb.xml';
To completely remove the PDB from the CDB, drop the PDB. The only
operation supported on an unplugged PDB is dropping the PDB. The PDB
must be dropped from the CDB before it can be plugged back into
the same CDB.

Unplugging a PDB from a CDB

Run the CREATE PLUGGABLE DATABASE ... USING statement, specifying the
XML file or the .pdb archive file in the USING clause. Specify other clauses
when they are required.

Plugging In an Unplugged PDB

DBMS_PDB.CHECK_PLUG_COMPATIBILITY is optional, not mandatory.

SOURCE_FILE_NAME_CONVERT is being given here, so

PDB_FILE_NAME_CONVERT is not mandatory to set.

Plugging in an Unplugged PDB: Examples

Domain
Creating and Removing PDBs and Application Containers
Overall explanation
All metrics are instance related. - FALSE

There are different types of metrics.

 Performance Metrics
Performance metrics give an overview of where time is spent in the
system and enable comparisons of wait times across the system.
 Resource Metrics
Resource metrics give an overview of where time is spent in the
system for each resource requested.
 Performance Satisfaction Metrics
A useful metric for analyzing workload performance is a common and
 consistent numeric measure of how work requests in a Performance
Class are doing against the current Performance Objective for that
Performance Class.

Read Overview of Metrics

DBA_ALERT_HISTORY - Lists a history of alerts that have been cleared

Read Server-Generated Alerts Data Dictionary Views

A space usage management alert is a stateful alert, so it will auto clear once
issue is resolved.

For metric alert event types, an event (metric alert) is raised based on the
metric threshold values. These metric alert events are
called stateful alerts. For example, tablespace usage > 85%.

For those metric alert events that are not tied to the state of a monitored
system (for example, snapshot too old, or resumable session suspended ),
these alerts are called stateless alerts. Because stateless alerts are not
cleared automatically, they need to be cleared manually. You can perform a
bulk purge of stateless alerts using the clear_stateless_alerts EM CLI verb.

Clearing Stateless Alerts for Metric Alert Event Types

The alerts are generated by MMON, not SMON.

The manageability monitor process (MMON) performs many tasks

related to the Automatic Workload Repository (AWR).

For example, MMON writes when a metric violates its threshold value,
taking snapshots, and capturing statistics value for recently modified SQL
objects.

Read Manageability Monitor Processes (MMON and MMNL)

Domain
Database Monitoring
Overall explanation
The opatchauto utility can take care of the stop and start of all components
as needed. It requires the Oracle Grid Infrastructure and Oracle Database
instances to be shut down before being invoked.

So, it doesn't require the Oracle Grid Infrastructure and Oracle Database
instances to be shut down before being invoked.
The high-level phases follow. They can be specified as (a) book-keeping, (b),
life-cycle operations, of (c) configuration change operations

 Init: Bookeeping operation to initialize internal state needed for

correction patching.
 Shutdown: Life-cycle operation that brings down run-time entities to
permit patching.
 Offline: Configuration change operation to apply the patch content with
the system down. Bits application happens here, for instance. So the
opatch patch will be recorded to the homes OUI inventory in this
phase.
 Start-up: Life-cycle operation that brings the shutdown entities back up
again.
 Online: Configuration change operation apply patch content that
requires that the systems be up. If these configuration changes have a
system inventory, they will also be recorded to that system's inventory
at this point.
 Finalize: Book-keeping operation to record that patch operation is
complete.

Phases and Sessions

If opatchauto is executed as Oracle home owner, then sudo must be

configured for the oracle home owner to become root and owners of
the other homes, if the other homes have different owner.

Running OPatchAuto on a Single Node

Patches can be applied via opatch too, not necessarily opatachauto.

Patch Plans - They are optional and advanced inputs. However, internally,
OPatchAuto always selects a patch plan to guide its execution.

Patch Plans

It applies patches in rolling mode by default, not non-rolling.

Patch Application Modes

It is used to apply many types of patches, not just interim patches.

Supported Patch Format

Domain
OPatch and Patching

Overall explanation
OLTP database needs very good transaction response time as multiple
small DMLs are done all the time.

Template - General Purpose or Transaction processing

Many concurrent users perform numerous transactions that require rapid

access to data. Availability, speed, concurrency, and recoverability are
key issues.
Transactions consist of reading (SELECT statements), writing (INSERT and
UPDATE statements), and deleting (DELETE statements) data in database
tables.

The data warehouse needs good response time but not good transaction
response time as database warehouse doesn't perform transactions as such.

Template - Data warehouse

Users perform numerous, complex queries that process large volumes of

data. Response time, accuracy, and availability are key issues.

These queries (SELECT statements) range from a fetch of a few records to

queries that sort thousands of records from many different tables.

Read DBCA Templates Provided by Oracle

The seed type template contains both the structure and the physical
data files of an existing database, referred to as the seed database. Your
new database starts as a copy of the seed database, and requires only the
following changes:

 Name of the database

 Destination of the data files
 Number of control files
 Number of online redo log groups
 Initialization parameters

Read Types of DBCA Templates

Database Configuration Assistant (DBCA) templates are XML files that

contain information required to create a database. Templates are used in
DBCA to create new databases and duplicate existing databases. The
information in templates includes database options, initialization
parameters, and storage attributes (for data files, tablespaces, control files,
and online redo log files).

Read Managing Templates with DBCA

You can create template from existing databases too.

The createTemplateFromDB command creates a database template from an

existing database.

Read createTemplateFromDB

Domain
Oracle Software Installation
Overall explanation
Single-byte encoding schemes are efficient. They take up the least amount
of space to represent characters and are easy to process and program with
because one character can be represented in one byte.

How are Characters Encoded?

The Unicode Standard is a character encoding system that defines every

character in most of the spoken languages in the world.

What is the Unicode Standard?

Oracle Database supports many character sets, not just Unicode.

Recommended Database Character Sets

Single-byte character sets can use 7-bit or 8-bit encoding schemes.

Single-Byte Encoding Schemes

Multibyte character sets cause less efficient space utilization than single byte
character sets.

Domain
Database Globalization Support
Overall explanation
If the database is in NOARCHIVELOG mode, you have to shutdown the
database and copy the files using cp or similar commands.

The files copied in such a way can be later added to the RMAN catalog as
image copies because the copied files are full data files image.

If the database is in ARCHIVELOG mode, then the backup can be taken even
database is running using ALTER DATABASE BEGIN BACKUP followed by
copying of data files and archive log files.

You can make a consistent whole database backup of all files in a database
after the database has been shut down with the NORMAL, IMMEDIATE, or
TRANSACTIONAL options. A whole database backup taken while the
database is open or after an instance failure or SHUTDOWN ABORT
command is inconsistent. In such cases, the files are inconsistent with the
database checkpoint SCN.

Read Making User-Managed Backups of the Whole Database

Domain
User-Managed Backups and Recovery
Overall explanation
Time model statistics use time to identify quantitative effects about specific
actions performed on the database, such as logon operations and parsing.

Read Time Model Statistics

The database should be continuously monitored for performance issues. The

efforts for tuning should never stop.

Proactive monitoring usually occurs on a regularly scheduled interval, where

several performance statistics are examined to identify whether the system
behavior and resource usage has changed. Proactive monitoring can also be
considered as proactive tuning.

Read Proactive Monitoring

The alert log file will not have any tuning information.

Domain
Database Performance Tuning and Dynamic Performance Views

Overall explanation
 Oracle Grid Infrastructure upgrades are always out-of-place upgrades.
You cannot perform an in-place upgrade of Oracle Grid Infrastructure to
existing homes.
 The same user that owned the earlier release Oracle Grid
Infrastructure software must perform the Oracle Grid Infrastructure
19c upgrade.
 Oracle ASM and Oracle Clusterware both run in the Oracle Grid Infrastructure
home.
 When you upgrade Oracle Grid Infrastructure, you upgrade to an Oracle Flex
Cluster configuration.

Restrictions for Oracle Grid Infrastructure Upgrades

After you have upgraded Oracle Grid Infrastructure 19c, you can install
individual software patches by downloading them from My Oracle Support.

Read Applying Patches to Oracle Grid Infrastructure

Domain
Oracle Software Installation
Overall explanation
During instance recovery, the database must apply the changes that occur
between the checkpoint position and the end of the redo thread.

Read Importance of Checkpoints for Instance Recovery

Instead of waiting for the SMON process to roll back terminated transactions,
new transactions can roll back individual blocks themselves to obtain the
required data.
Read Instance Recovery Phases

Question 34Skipped
Examine this output:

Which two are true? (Choose two.)

Overall explanation
When you do not explicitly define directives for a PDB, the PDB uses the
default directive for PDBs.

In other words, any PDB not having a resource plan directive under the
current CDB plan will get the resources according to
ORA$DEFAULT_PDB_DIRECTIVE.

In this case, ORA$DEFAULT_PDB_DIRECTIVE - PARALLEL_SERVER_LIMIT is 0,

so any PDB not specified in the plan will be unable to execute statements in
parallel.

The Default Directive for PDBs

If PARALLEL_SERVER_LIMIT is not specified, then it defaults to
100%. In this case, PDB3 doesn't have PARALLEL_SERVER_LIMIT specified,
so PDB3 can use all available parallel execution processes at times.

Managing Parallel Statement Queuing Using Parallel Server Limit

PDB1 is not limited to 40% as it can use more resources if available.

Similarly, any PDB is not limited to any minimum % and can use more than
dictated by its resource plan directive.

PDB3 is NOT guaranteed to receive at least 20% of the available system

resources because there might be other PDBs in the database not listed in
the above listing.

PDB2 is NOT guaranteed at least 25% of the available parallel execution

processes because PARALLEL_SERVER_LIMIT is an upper limit.

Parallel Server Limit

Domain
Database Resource Manager
Overall explanation
You can perform tablespace conversion with the RMAN CONVERT
TABLESPACE command on the source host, but not on the destination host.
The CONVERT TABLESPACE command does not perform in-place conversion
of data files. Rather, the command produces output files in the correct
format for use on the destination platform. The command does not alter the
contents of data files in the source database.

Overview of Tablespace and Data File Conversion Using Image Copies

Domain
Transportable Tablespace Sets
Overall explanation
For a tablespace to be backed up in read/write mode, the database must be
in ARCHIVELOG mode. You can take Level 0/1 backups.
Domain
RMAN Backup and Recovery
Overall explanation
The CDB property LOCAL_UNDO_ENABLED is false so undo is in shared mode.
So, recovery can be done only by connecting to CDB as the target, not by
connecting to PDB as the target.

Point-in-Time Recovery of a PDB

When a PDB is closed in an open or closed CDB, you can recover the PDB to
a past point in time. The technique depends on the undo mode of the CDB.
The following table describes the differences.
Read here

You can perform point-in-time recovery (PITR) of one or more PDBs. Backups
created before the PITR operation remain valid and they can be used if a
media failure occurs.

During a PDB PITR operation, all the data files for the PDBs are recovered in
place. If the CDB uses shared undo, the UNDO tablespace cannot be
recovered in place because it is shared by all PDBs in the CDB. Therefore,
RMAN restores the UNDO, SYSTEM, and SYSAUX tablespaces to an auxiliary
destination and then uses the undo information to recover the PDB to the
target time.

Read here

Question 38Skipped
Your SALES_ROOT application container has two application PDBs.
The SALES_APP application has a common table, FIN.REVENUE, in
the two PDBs. Examine this query and its output:
Which two are true? (Choose two.)
Overall explanation
The CONTAINERS clause cannot be used in queries on the REVENUE table.
- FALSE

The REVENUE table is a common table, so the CONTAINERS clause can be

used.

The REVENUE table must be a list-partitioned table. - FALSE

It can be range-partitioned too.

Read Range-Partitioned Container Map: Example

The MAPTABLE tables defines a logical partition key on a commonly used

column for the REVENUE table. - TRUE

A container map can define a logical partition key on a column for a common
object.

Read About Container Maps

The MAPTABLE table is a metadata-linked table. - FALSE

As CONTAINER_MAP_OBJECT is YES for MAPTABLE, it means it is a normal

container map table. Rather, in this case, REVENUE is a metadata-linked
table.

Read Map Objects

A container map exists for the REVENUE table, but is not enabled. - FALSE

The container map is enabled as the value of CONTAINER_MAP is YES.

The REVENUE table partitions are not pruned across the PDBs automatically.
- FALSE
The CONTAINER_DEFAULT is NO, so no automatic pruning.

You can set the CONTAINERS_DEFAULT attribute on any metadata-linked

object so that DML issued in the application root is wrapped in the
CONTAINERS clause by default.

Read Setting the Default Container or DML

Domain
Multitenant Architecture

Overall explanation
The number of table rows is considered when evaluating the cost of
accessing a table using an index. - FALSE

When a query uses an index, the blocks of the index are hit first then actual
table blocks are hit.
Index balanced B*Tree height is considered when evaluating the cost of
using an index. - TRUE

In an index scan, the database retrieves a row by traversing the index,

using the indexed column values specified by the statement. If the database
scans the index for a value, then it will find this value in n I/Os where n is the
height of the B-tree index. This is the basic principle behind Oracle Database
indexes.

Read Index Scans

Statistics collected using DBMS_STATS always yield the best optimizer result.
- FALSE

Depending on options chosen for gathering the statistics and run-time

changes like number of rows in the table, and skewedness in the data, the
statistics collected using DBMS_STATS MAY NOT always yield the best
optimizer result.

The Statistics Advisor can help recommend the best way to gather statistics.
- TRUE

Based on each finding, Optimizer Statistics Advisor makes recommendations

on how to achieve better statistics.

For example, the advisor might discover a violation to the rule of not using
sampling when gathering statistics, and recommend specifying
AUTO_SAMPLE_SIZE instead. The advisor stores the recommendations in
DBA_ADVISOR_RECOMMENDATIONS.

Read Recommendations for Optimizer Statistics Advisor

The Statistics Advisor generates actions for all recommendations. - FALSE

An Optimizer Statistics Advisor action is a SQL or PL/SQL script that

implements recommendations. When feasible, recommendations have
corresponding actions. The advisor stores actions in
DBA_ADVISOR_ACTIONS.
Read Actions for Optimizer Statistics Advisor

Domain
Gathering Optimizer Statistics

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
Rapid Hope Provisioning
Overall explanation
The RMAN BACKUP VALIDATE command will do only reads, no writes. So, if
this takes almost the same time as an actual backup, it means that read is
the problem, else write is the problem.
The parameter DBWR_IO_SLAVES is relevant for synchronous I/O systems
only.

If you set DBWR_IO_SLAVES to a nonzero value, the number of I/O server

processes used by the ARCH and LGWR processes is set to 4. However, the
number of I/O server processes used by Recovery Manager is set to 4 only if
asynchronous I/O is disabled (either your platform does not support
asynchronous I/O or disk_asynch_io is set to false).

Read DBWR_IO_SLAVES

Data files with a high value in

V$BACKUP_SYNC_IO.DISCRETE_BYTES_PER_SECOND are a potential
performance bottleneck when synchronous I/O is used. - FALSE

A higher rate is not the problem, a lower rate would be a problem.

If the rate is lower than the rate that the device specifies, then consider
tuning this aspect of the backup and restore process.

Read Identifying Bottlenecks with Synchronous I/O

Data files with a high value in V$BACKUP_ASYNC_IO.SHORT_WAITS are a

potential performance bottleneck when asynchronous I/O is used. - FALSE

A high number of short waits is not a problem.

Short waits are the number of times the backup or restore process made
an operating system call to poll for I/O completion in a nonblocking mode.

Read Identifying Bottlenecks with Asynchronous I/O

Domain
RMAN Backup and Recovery
Overall explanation
You can not do complete recovery if:
 You have lost all copies of the control file.
 You have lost archive logs after the last good backup.

Read Overview of Complete Database Recovery

If you restore the control file from backup, then you must perform media
recovery of the whole database and then open it with the OPEN RESETLOGS
option, even if no data files must be restored.

Read Identifying a Lost Control File

Domain
RMAN Backup and Recovery
Overall explanation
V$SESSION_EVENT displays information on all waits for all events by a
session.

V$SESSION_EVENT

V$SESSION_WAIT - displays only the current or last wait for each session, not
all waits.

V$SESSION_WAIT

Oracle Wait Events

V$SESSION_WAIT_CLASS displays the time spent in various wait classes on a

per-session basis.

V$SESSION_WAIT_CLASS

Domain
Database Performance Tuning and Dynamic Performance Views
Overall explanation
Virtual Private Database (VPD) policies on objects in an application root are
automatically synchronized with all application PDBs contained in the
application container. - FALSE
Only common VPD policies for common objects will be applied to all PDBs in
the application container.

With regard to application containers, you can create Virtual Private

Database policies to protect application common objects by applying the
common policy to all PDBs that belong to the application root. In other
words, when you install an application in the application root, all the
common Virtual Private Database policies that protect the common objects
will be applied to and immediately enforced for all PDBs in the application
container.

Read Oracle Virtual Private Database in a Multitenant Environment

Application-common TSDP policies are always container specific. - TRUE

In an application PDB:

 The security policies that protect an application PDB apply to TSDP

operations that are performed on local application objects.
 The security policies that protect an application PDB apply to TSDP
operations that are performed on application common objects that are
accessed from the PDB. However, access to the application common
object outside the application PDB is not governed by the security
policy that protects the application PDB.

Read How a Multitenant Environment Affects Transparent Sensitive Data

Protection

Application-common Transparent Security Data Protection (TSDP) policies

can be created only within an application install/patch BEGIN-END block.
- FALSE

In an application root, you cannot use TSDP statements in BEGIN/END block.

Rather TSDP statements can be created using anonymous blocks.

When you create scripts for application install, upgrade, patch, or uninstall
operations, you can include SQL statements within the ALTER PLUGGABLE
DATABASE app_name BEGIN INSTALL and ALTER PLUGGABLE DATABASE
app_name END INSTALL blocks to perform various operations. If you include
TSDP statements within these blocks, then the TSDP statements will fail. You
can, however, include TSDP statements outside these blocks in the script.
Read How a Multitenant Environment Affects Transparent Sensitive Data
Protection

Application-common Oracle Label Security (OLS) policies cannot be created

in an application root outside an install/patch BEGIN-END block. - TRUE

Application-common OLS policies can be created in an application root inside

an install/patch BEGIN-END block. - FALSE

You cannot create Oracle Label Security policies in the CDB root or the
application root.

Read Oracle Label Security Integration in a Multitenant Environment

Fine-grained auditing (FGA) policies in an application root are automatically

synchronized to all application PDBs contained in the application container.
- FALSE

When you create a fine-grained audit policy as a common audit policy in an

application root, it will be effective in each PDB that belongs to this
application root. Therefore, any access to the application common object
and CDB common object (on which the application common fine-grained
audit policy is defined) from the application PDB is audited in the fine-
grained audit trail in that application PDB.

Read Fine-Grained Auditing in a Multitenant Environment

Unified auditing can be automatically synchronized to all application PDBs in

an application container. - TRUE

FGA policies will propagate to PDBs set in the CONTAINER = clause.

Read Example: Application Common Unified Audit Policy

Domain
Oracle Database Security
Overall explanation
It is possible to duplicate multiple PDBs at once.

Use one of the following techniques:

 Duplicate the specified PDBs to a new CDB by using the following

syntax:

DUPLICATE DATABASE TO cdb_name PLUGGABLE DATABASE pdb_name;

Use a comma-delimited list to duplicate multiple PDBs.

 Duplicate all the PDBs, except the PDBs specified by pdb_name, to a

new CDB by using the following syntax:

DUPLICATE DATABASE TO cdb_name SKIP PLUGGABLE DATABASE pdb_name

Use a comma-delimited list to specify multiple PDBs that must be

excluded.
 Read About Duplicating PDBs

It is possible to duplicate selected tablespaces.

You can duplicate one or more tablespaces within a PDB to a new CDB by
using the DUPLICATE command.

1. DUPLICATE DATABASE TO dup_cdb

2. TABLESPACE pdb1:users;

Read Duplicating Tablespaces Within a PDB to a New CDB

Domain
RMAN Backup and Recovery
Overall explanation
Basic concepts:

For PITR, the database must be in ARCHIVELOG mode.

For PITR, the flashback mode is not relevant.

For PITR of the whole database, the database must be in MOUNTED mode.

PITR is incomplete recovery, so database must be open RESETLOGS.

The target point for the recovery can be log sequence number or scn or time.

Read Performing Database Point-in-Time Recovery

Domain
RMAN Backup and Recovery
Overall explanation
Here, the question is asking about how to migrate a table 'after upgrading a
database'. It is not asking how to upgrade.

Once you have got a newer version database created, then you can move
the data from the older version database to the newer version database
using the below methods:

1. DataPump export from source to target.

2. Using the CREATE TABLE AS SELECT SQL statement - over a DB link or

using an external table
3. SQL Developer - You can export data from the source database using
SQL Developer, and then import it into the target database using
SQL Developer.

Read Upgrade and Data Migration Methods and Processes

Domain
Database Upgrade
Overall explanation
Duplexing Backup Sets

RMAN can make up to four copies of a backup set simultaneously, each an

exact duplicate of the others.

A copy of a duplexed backup set is a copy of each backup piece in the

backup set, with each copy getting a unique copy number (for example,
0tcm8u2s_1_1 and 0tcm8u2s_1_2). It is not possible to duplex backup sets to
the fast recovery area.

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
RMAN Backup and Recovery

Question 49Skipped
Examine these queries and their output:
After a system crash, an instance restart and an attempted opening
of the PDBs result in:
Which two are true? (Choose two.)

Overall explanation
The CDB property LOCAL_UNDO_ENABLED is false so undo is in shared mode.
But that has no bearing in the current scenario. But, recovery can be done
only by connecting to CDB as the target, not by connecting to PDB as the
target.

Datafile 24 belongs to PDB1, so only PDB1 must be closed for recovery. CDB
and other PDBs may be closed or open; that will not impact the recovery of
PDB1.

When a PDB is closed in an open or closed CDB, you can recover the PDB to
a past point in time. The technique depends on the undo mode of the CDB.
The following table describes the differences.
Read Point-in-Time Recovery in a Multitenant Environment

You can perform point-in-time recovery (PITR) of one or more PDBs. Backups
created before the PITR operation remain valid and they can be used if a
media failure occurs.

During a PDB PITR operation, all the data files for the PDBs are recovered in
place. If the CDB uses shared undo, the UNDO tablespace cannot be
recovered in place because it is shared by all PDBs in the CDB. Therefore,
RMAN restores the UNDO, SYSTEM, and SYSAUX tablespaces to an auxiliary
destination and then uses the undo information to recover the PDB to the
target time.

Read Basic Concepts of Point-in-Time Recovery for PDBs

Domain
RMAN Backup and Recovery
Overall explanation
To back up all recovery-related files to tape, use the RMAN BACKUP
RECOVERY FILES command once a week.

This ensures that all current incremental, image copy, and archived log
backups on disk are backed up to tape.

Read Performing Backups Directly to Tape

Domain
RMAN Backup and Recovery
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
Overall explanation
FLASHBACK DATABASE uses flashback logs and archived logs, not undo, and
brings back the whole database.

Read here

FLASHBACK QUERY uses undo, not redo, or archived logs.

Read here
FLASHBACK TABLE ... to SCN/TIMESTAMP uses undo and brings back the
whole table.

Read here

FLASHBACK TABLE ... TO BEFORE DROP uses recycle bin and brings back
the indexes too but it does not recover referential constraints.

Oracle Flashback Drop enables you to reverse the effects of dropping

(deleting) a table, returning the dropped table to the database along with
dependent objects such as indexes and triggers. This feature stores dropped
objects in a recycle bin, from which they can be retrieved until the recycle
bin is purged, either explicitly or because space is needed.

Read here

FLASHBACK DATA ARCHIVE requires undo to store all versions of all rows of a
table being tracked. - FALSE

Use the CREATE FLASHBACK ARCHIVE statement to create a flashback

archive, which provides the ability to automatically track and archive
transactional data changes to specified database objects. A flashback
archive consists of multiple tablespaces and stores historic data from all
transactions against tracked tables. The data is stored in internal history
tables.

Read CREATE FLASHBACK ARCHIVE

Domain
Flashback Technologies
Overall explanation
To convert a whole database to a different platform, both platforms must use
the same endian format. The RMAN CONVERT DATABASE command
automates the movement of an entire database from a source platform to a
destination platform.

You can convert the format of the data files either on the source platform or
on the destination platform if you are transporting the whole database
because full database transport requires the endian format to be the same
on source and target platforms anyway.

Overview of Database Conversion Using Image Copies

A new DBID is not automatically created for the transported database. You
must run the nid command to create a new DBID.

nid TARGET=SYS

Changing Only the Database ID

Domain
Transporting Data Across Platforms
Overall explanation
The USER_TABLESPACES clause of the CREATE PLUGGABLE DATABASE
statement specifies which tablespaces are available in the new PDB.

You can use this clause to specify one of the following options:

 List one or more tablespaces to include.

 Specify ALL, the default, to include all tablespaces.
 Specify ALL EXCEPT to include all tablespaces, except for the
tablespaces listed.
 Specify NONE to make only the SYSTEM, SYSAUX, and TEMP
tablespaces available in the new PDB.

Read User Tablespaces

Domain
Multitenant Architecture
Overall explanation
The real-time query is a must for automatic block repair.

Block recovery behavior depends on whether the data block corruption was
discovered on the primary database or the physical standby database.

If the database on which the corruption occurs is associated with a real-time

query physical standby database, then the database automatically attempts
to perform block media recovery. The primary database searches for good
copies of blocks on the standby database and, if they are found, repairs the
blocks with no impact to the query that encountered the corrupt block. The
Oracle Database physical block corruption message ORA-1578 is displayed
only if the database cannot repair the corruption.

For block media recovery to work automatically, the physical standby

database must be in real-time query mode. An Oracle Active Data Guard
license is required.

Read About Block Recovery and Standby Databases

The parameter DB_BLOCK_CHECKING only enables the logical block
corruption detection, not repair.

Read DB_BLOCK_CHECKING

Domain
Block Media Recovery

Question 56Skipped
Examine the command for creating pluggable database PDB2 in
container database CDB2.

Select three options, any one of which is required for it to execute

successfully. (Choose three.)
Overall explanation
You need one of the below, at minimum.

1. Enable OMF at the CDB level which means setting init parameters -
DB_CREATE_FILE_DEST, DB_CREATE_ONLINE_LOG_DEST_n and
DB_RECOVERY_FILE_DEST

Read Initialization Parameters That Enable Oracle Managed Files

OR

2. Use the clause FILE_NAME_CONVERT in the PDB create command.

Read FILE_NAME_CONVERT Clause

OR

3. Use the clause CREATE_FILE_DEST in the PDB create command. This

enables the OMF for the current PDB to be created.

Read PDB File Locations

Domain
Multitenant Architecture

Overall explanation
Moves one or more databases from a source working copy or any Oracle
Database home to a patched working copy.

rhpctl move database

The independent automaton for Oracle Database patching performs all of the
steps necessary to switch from one home to another. Because the
automaton is not aware of gold images, moving the database requires two
home paths, as follows:

$ rhpctl move database -sourcehome Oracle_home_path -desthome

destination_oracle_home_path

Patching Oracle Database with the Independent Automaton

The Fleet Patching and Provisioning Server acts as a central server for
provisioning Oracle Database homes, Oracle Grid Infrastructure homes, and
other application software homes, making them available to the cluster
hosting the Fleet Patching and Provisioning Server and to the Fleet Patching
and Provisioning Client clusters, their targets, and non-client targets.

Oracle Fleet Patching and Provisioning Server

Use the rhpctl add workingcopy command to provision a working copy of a

database home on a Fleet Patching and Provisioning Server, Client, or target.

Run the rhpctl add workingcopy command on a Fleet Patching and

Provisioning Server, similar to the following example:

$ rhpctl add workingcopy -image db12c -path

/u01/app/dbusr/product/12.2.0/db12201

-client client_007 -oraclebase /u01/app/dbusr/ -workingcopy wc_db122_1

Provisioning Oracle Database Homes

You can not switch to a read-only Oracle home. Rather, read-only Oracle
home images are used as a source to create working software homes.

The Fleet Patching and Provisioning Server stores and serves gold images of
software homes. These images must be instantiated on the Fleet Patching
and Provisioning Server.
Images are read-only, and you cannot run programs from them. To create a
usable software home from an image, you must create a working copy of a
gold image. You cannot directly use images as software homes. You can,
however, use images to create working copies (software homes).

Adding Gold Images to the Fleet Patching and Provisioning Server

Domain
Rapid Hope Provisioning

Question 58Skipped
Examine this configuration: CDB1 is a container database.
COMMON_USER_PREFIX is C##. PDB1 is a pluggable database
contained in CDB1. APP1_ROOT is an application container contained
in CDB1. APP1_PDB1 is an application PDB contained in APP1_ROOT.
You execute these commands successfully:

Which two are true? (Choose two.)

Overall explanation
Basic concepts:

A common user is a database user that has the same identity in the root and
in every existing and future pluggable database (PDB). Every common user
can connect to and perform operations within the root, and within any PDB in
which the common user has privileges.

Every common user is either Oracle-supplied or user-created. Examples of

Oracle-supplied common users are SYS and SYSTEM.

Any user created at the CDB level will always be a common user.

As COMMON_USER_PREFIX is C##, the common user name must start with

C##.

A common user reflects in all PDBs, hence a user with the same name cannot
be created again in any of the PDBs.
You can grant more privileges to a common user inside the PDB than it was
given at the CDB level. You can revoke CDB-level privileges from a common
user inside the PDB. So, a common user can have different privileges
between CDB and PDB.

In addition to common users propagating from the CDB, you can create local
users in the PDBs as needed. The same local username can exist in multiple
PDBs as the scope of local users is limited to the PDB level only.

Read Common Users in a CDB

Domain
Multitenant Architecture

Question 59Skipped
You have configured RMAN SBT channels to write backups to media.
You then take an RMAN backup by using this command:

Which three are true? (Choose three.)

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

Including or exempting backups from the retention policy

 Archival backups can be created by using the KEEP clause to

exempt backups from the configured retention policy. You can
also change the status of an archival backup and subsequently include
it in the configured retention policy.

Read Changing the Repository Status of Backups and Copies

When KEEP is specified, RMAN creates multiple backup sets. RMAN backs up
data files, archived redo log files, the control file, and the server
parameter file with the options specified in the first backupOperand. Since
a backup of the control file is created, an autobackup of the control file is not
created.

Read keepOption

If the KEEP UNTIL TIME period has not expired for an archival backup, RMAN
does not consider the backup as obsolete. As soon as the KEEP UNTIL period
expires, however, the backup is immediately considered to be obsolete,
regardless of any configured backup retention policy.

Read DELETE OBSOLETE Behavior When KEEP UNTIL TIME Expires

Domain
RMAN Backup and Recovery
Overall explanation
In the Oracle Restart environment, starting a component will automatically
start its dependency components first.

When starting a component with SRVCTL, Oracle Restart can first start any
components on which this component depends. When stopping a component
with SRVCTL, Oracle Restart can stop any dependent components first.

Read Starting and Stopping Components Managed by Oracle Restart

Domain
Oracle Restart
Question 61Skipped
Oracle Managed Files (OMF) is enabled in a CDB and this command is
successfully executed:

Which three are true? (Choose three.)

Overall explanation
The clause APPLICATION CONTAINER creates an application container (to
start with, it will have an application root container only).

A default service with the name same as the container is always created
whether you create CDB root, CDB PDB, application root, or application PDB.
If there is no seed PDB in the application container, then CDB's PDB$SEED is
used to create new PDBs.

Read Creating an Application Container

Domain
Multitenant Architecture

Overall explanation
The package DBMS_STATS will gather the stats only for the connected
container which can be root or any of the pluggable databases.

SYSTEM or any kind of stats gathering can be done at a pluggable level too,
similar to CDB$ROOT level.
Read DBMS_STATS Overview

Domain
Gathering Optimizer Statistics

Overall explanation
V$SESSION_EVENT shows these details for existing sessions, not past
sessions.

V$SESSION_EVENT

V$SERVICE_EVENT displays aggregated wait counts and wait times for each
wait statistic.

V$SERVICE_EVENT

V$SESSION_WAIT_CLASS displays the time spent in various wait event

operations on a per-session basis.

V$SESSION_WAIT_CLASS

V$SESSION_WAIT and V$SESSION both contain details of the event on which

a session is currently waiting. That's true.

V$SESSION_WAIT

Domain
Database Performance Tuning and Dynamic Performance Views
Overall explanation
Primary keys will not speed up all queries as not all queries will use the
primary keys columns.

Check constraints don't speed up updates, rather they slow them down as
constraints have to be maintained on each update.

Foreign keys don't speed up the joins. Rather, indexes on foreign keys can
speed up the joins.

The physical data model manifests the logical data model into database
tables and relationships (or foreign key constraints). Partitions, indexes, and
Materialized Views have been added to aid performance.

The Physical data model includes the following:

 Reference Tables
  Lookup Tables
 Base Tables
 Derived Tables
 Aggregate Tables
 Sequences

Read Physical Data Model

The configuration of storage arrays will impact I/O performance of the

database.

You can gather the necessary statistics by using Automatic Workload

Repository (AWR) reports or by querying the GV$SYSSTAT view. Along with
understanding the database performance requirements, you must evaluate
the performance capabilities of a storage array.

Read Evaluate Database Performance and Storage Capacity Requirements

Domain
Database Performance Tuning and Dynamic Performance Views
Overall explanation
In Oracle documentation, a user created to own only Oracle Grid
Infrastructure software installations is called the Grid user (grid). This user
owns both the Oracle Clusterware and Oracle Automatic Storage
Management binaries. A user created to own either all Oracle installations, or
one or more Oracle database installations, is called the Oracle user (oracle).
You can have only one Oracle Grid Infrastructure installation owner, but you
can have different Oracle users to own different installations.

Oracle software owners must have the Oracle Inventory group as their
primary group, so that each Oracle software installation owner can write to
the central inventory (oraInventory), and so that OCR and Oracle Clusterware
resource permissions are set correctly. The database software owner must
also have the OSDBA group and (if you create them) the OSOPER,
OSBACKUPDBA, OSDGDBA, OSRACDBA, and OSKMDBA groups as secondary
groups.

About Oracle Installation Owner Accounts

Overall explanation
Instance recovery uses only online redo log files and current online data files
to synchronize the data files and ensure that they are consistent.
Read Overview of Instance Recovery

The higher value of FAST_START_MTTR_TARGET means that you are giving

more time for instance recovery. So, it will write dirty buffers to disks less
frequently.

Read Configuring the Duration of Cache Recovery:

FAST_START_MTTR_TARGET

Domain
Instance Recovery

Question 67Skipped
Examine this configuration: CDB1 is a container database. PDB1 and
PDB2 are pluggable databases in CDB1. PDB1 and PDB2 are OPEN in
READ WRITE mode. You execute these commands successfully:

Which two are true? (Choose two.)

Overall explanation
Any uncommitted transactions will be rollbacked on a shutdown of the PDB.
This behavior is same as for a normal non-PDB database.
Domain
Multitenant Architecture

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

Question 69Skipped
Examine this configuration: CDB1 is an Oracle Database 12c Release
2 database containing pluggable databases PDB$SEED, PDB1, and
PDB2. PDB$SEED is open READ ONLY PDB1 is open READ WRITE
PDB2 is MOUNTED. ORACLE_HOME is
/u01/app/oracle/product/18.1.0/dbhome_1. You execute these
commands before upgrading the database to the current release:

For which databases will fixup scripts be created?

Overall explanation
You must set up the user environment variables for the Pre-Upgrade
Information Tool. This example shows how to use shell commands to set up
user environment variables to point to an earlier release Oracle home. For
multitenant architecture upgrades, you must also open up all the PDBs that
you want the tool to analyze.

Read Setting Up Environment Variables for the Pre-Upgrade Information Tool

Domain
Database Upgrade
Overall explanation
The amount of memory available for the library cache can drastically affect
the parse rate of Oracle Database. To help you correctly size the library
cache, Oracle Database provides the following shared pool advisory views:

V$SHARED_POOL_ADVICE

V$LIBRARY_CACHE_MEMORY

V$JAVA_POOL_ADVICE

V$JAVA_LIBRARY_CACHE_MEMORY

Read Using Shared Pool Advisory Statistics

Domain
Memory Advisors
Overall explanation
The advisor task runs automatically in the maintenance window, but you can
also run it on demand.

It is part of the package DBMS_STATS.

Read Analyzing Statistics Using Optimizer Statistics Advisor

The advisor analyzes how you are currently gathering statistics (using
manual scripts, explicitly setting parameters, and so on), the effectiveness
of existing statistics gathering jobs, and the quality of the gathered
statistics. Optimizer Statistics Advisor does not gather a new or alternative
set of optimizer statistics, and so does not affect the workload. Rather,
Optimizer Statistics Advisor analyzes information stored in the data
dictionary, and then stores the findings and recommendations in the
database.

Read Advantages of Optimizer Statistics Advisor

You can filter which schemas to include.

A filter is the use of DBMS_STATS to restrict an Optimizer Statistics Advisor

task to a user-specified set of rules, schemas, or operations.

Read About Filters for Optimizer Statistics Advisor

Domain
Gathering Optimizer Statistics
Overall explanation
Few thumb rules to remember when using application containers:

An application container has exactly one application root, which is the

parent of the application PDBs in the container.

Read Application Root

An application seed is an optional, user-created PDB within an application
container. An application container has either zero or one application seed.

Only the application root PDB is mandatory.

Read Application Seed

The application seed PDB can be added and dropped at any time and doing
so will not impact any already created application PDBs.

Read Creating and Removing Application Seeds

When creating a new application PDB, it will clone from the application seed
PDB if present, else it will clone from the CDB PDB seed PDB$SEED.

Read About Creating a PDB from Scratch

Creating an Application Seed

If the application seed was created from the PDB seed, then switch container
to the application seed, and use an ALTER PLUGGABLE DATABASE statement
with the SYNC clause to synchronize the application seed. Synchronizing with
the application root instantiates one or more of the application root’s
applications in the application seed.

If the application seed was created from an application root, then switch
container to the application seed, and run the pdb_to_apppdb.sql script to
convert the application root to an application PDB.

Read Creating an Application Seed

Domain
Multitenant Architecture
Overall explanation
ADDM is run automatically after each AWR but can be run manually by a
DBA.

ADDM analyzes the period covered by the last AWR which is one hour by
default.

Results are written to the ADDM report file, not the alert log.

Overview of the Automatic Database Diagnostic Monitor

Domain
Automatic Performance Diagnostics
Overall explanation
Privilege Analysis is included in Oracle Enterprise Edition and no longer
requires Database Vault. - TRUE

Database Vault does not have to be configured or enabled to use Privilege

Analysis in any version.

Read Privilege Analysis – Included with Oracle Database Enterprise Edition

Unified Auditing can be configured to audit only events that are issued
indirectly by an audited user. - FALSE
You cannot audit just indirect statements. You can audit either direct-only
(TOP-LEVEL) or all (default).

The ONLY TOPLEVEL clause in the CREATE AUDIT POLICY statement enables
you to audit only the SQL statements that are directly issued by an end user
by honoring the audit configuration in the audit policy.

Read Auditing Only Top-LevelConfiguring a Unified Audit Policy to Capture

Only Top-Level Statements

Domain
Oracle Database Security

Overall explanation
By default, an AWR snapshot is created every hour and retained for 8 days.

Read Managing Snapshots

ADDM can recommend resizing memory components.

Read Overview of the Automatic Database Diagnostic Monitor

Domain
Automatic Workload Repository

Question 76Skipped
You plan to install Oracle Grid Infrastructure for a Standalone
Server and Oracle Database for the first time on a server. Examine
this command and its outcome:

Which two are true? (Choose two.)

Overall explanation
The account 'oracle' is the default owner for an Oracle Grid Infrastructure
installation and 'grid' is the default owner for an Oracle Database installation.
But, you can 'oracle' for the grid as well as the database.

Or, you can create and use any user other than 'oracle' and 'grid' for Oracle
software installations.

Here, 'oracle' is part of 'oinstall' group so 'oracle' will be the inventory owner.

Read About Oracle Installation Owner Accounts

If the Oracle software owner user (oracle or grid) does not exist, or if you
require a new Oracle software owner user, then create it as described in this
section.

The following example shows how to create the user oracle with the user ID
54321; with the primary group oinstall; and with secondary groups dba,
asmdba, backupdba, dgdba, kmdba, and racdba:

# /usr/sbin/useradd -u 54321 -g oinstall -G

dba,asmdba,backupdba,dgdba,kmdba,racdba oracle
Read Creating an Oracle Software Owner User

Domain
Oracle Software Installation

Overall explanation
SBT tape compression (provided by a media management vendor) and RMAN
compression (provided by Oracle) are different things. They can be used
independently. Moreover, Oracle doesn't recommend using them together.

If you are backing up to tape and your tape device performs its own
compression, then do not use both RMAN backup set compression and the
media manager vendor's compression.

Read About Oracle Advanced Compression Option

You can configure channels to create parallel database backups. You have
two tape drives and want each drive to use tapes from a different tape
media family. The backup data is divided between the two tape devices.
Each configured channel backs up approximately half the total data.

Read Configuring Specific Channels: Examples

The number of backup pieces and backup sets are not dependent on the
number of tape drives.

Domain
RMAN Backup and Recovery
Overall explanation
As a thumb rule, any password cannot be put into any file.

So, orainstRoot.sh can be run either as root login or as sudo.

Read Install Oracle Database 19c with Automatic root Scripts

Execution and Running Oracle Universal Installer Using a Response File

root.sh can be executed automatically by the Database Installer not only if it

is provided with root credentials but also with root scripts automation.

Read Root Scripts Automation Support for Oracle Database Installation

Question 79Skipped
Examine this configuration:

While CDB1 is open,

‘/u02/app/oracle/fast_recover_area/cdb1/CDB1/controlfile02.ctl’ is
accidentally deleted. To recover from this critical failure, you
execute these commands:

What will be the outcome?

Overall explanation
When restoring the control file, the default destination is all of the locations
defined in the CONTROL_FILES initialization parameter.

Read About Control File Locations During RMAN Restore

If you know the backup piece name that contains the control file (for
example, from the media manager or because the piece is on disk), then you
can specify the piece name using the RESTORE CONTROLFILE FROM
'filename' command. The database records the location of every autobackup
in the alert log.

Read Performing Recovery with a Backup Control File and No Recovery

Catalog
Read RMAN Behavior When Restoring Control Files
Domain
RMAN Backup and Recovery
Overall explanation
A RMAN catalog can be created in any existing database, so there is no need
to create a new database. Rather, a separate user is needed.

The catalog database doesn't need to be ARCHIVELOG mode itself for the
catalog to work but is recommended.

A separate tablespace is recommended.

The recovery catalog owner for the base recovery catalog must be granted
the RECOVERY_CATALOG_OWNER role. The recovery catalog is created in
the default tablespace of the recovery catalog owner.

SYSBACKUP privilege is not needed.

Read CREATE CATALOG

When you use a recovery catalog, RMAN requires that you maintain a
recovery catalog schema. The recovery catalog is stored in the default
tablespace of the schema. Privileged users such as SYS cannot be the owner
of the recovery catalog.

Decide which database you will use to install the recovery catalog schema,
and also how you will back up this database. Also, decide whether to operate
the catalog database in ARCHIVELOG mode, which is recommended.

Configuring the Recovery Catalog Database

Domain
RMAN Backup and Recovery