Listeners use only the TCP/IP protocol.

Multiple listener processes can run simultaneously on a host.

Multiple database instances can be registered with a single listener,

Listener-related errors can be traced only at the administrative level.

Only one database instance can be registered with a single listener at any time.

shared UNDO and default database temporary tablespace

Oracle-supplied metadata

shared Oracle-supplied data

CDB views providing information across PDBs

application tablespaces

local temporary tablespaces

local users and local roles

Process Monitor Process (PMON)

Flashback Data Archive process (FBDA)

Space Management Coordinator process (SMCO)

Recoverer process (RECO)

Listener Registration process (LREG)

Checkpoint Process

The database advances a checkpoint.

A client process commits a transaction.

The redo log buffer becomes full.

A server process cannot find non-dirty blocks after scanning a threshold number of buffers.

A tablespace is changed to read-only status.

The database is shut down in immediate mode.

The database is open and registered with a global service manager.

The service has been disabled on that database.

The database role is different from the role attribute of the service.

The replication lag on the database does not exceed the maximum value specified for the service.

The service has reached its cardinality defined by the number of preferred databases.

No other database in the pool is a better candidate for starting the service.

a solution that provides zero-data-loss protection at any distance without impacting database performance

a solution for disaster protection and database rolling upgrades for a mission-critical OLTP database, where you also want to extract data from a data guard primary database for ETL update o' an enterprise data warehouse

a solution requiring minimal planned downtime and risk, using standby first patching, database rolling upgrades, and select platform migrations

a solution that helps with integrated automatic database and client failover between source and target, where you also need to establish advanced replication (such as multi master and bidirectional replication and data transformations)

undo data

isolation level

lock mechanism

serializability

create local role l_hr;

create role c##_hr container=current;

create role l_hr container=current;

create role l_hr container=all;

less instance overhead

increased storage cost

minor application changes

fast and easy provisioning

same time needed for patching and upgrade as in the previous release

isolation

A snapshot standby can be the target of a switchover or fast-start failover operation.

Neither a switchover nor a failover is possible to a far sync instance.

For fast-start failover, you must preselect the target standby database that will be used.

You can activate a standby database to test whether it is being updated correctly.

STARTUP

SHUTDOWN

CREATE DATABASE

DROP DATABASE

ALTER DATABASE RECOVER

PMON performs process recovery when a client process fails.

During instance startup, PMON takes care of instance recovery.

PMON performs listener registration.

PMON restarts background and dispatcher processes when they fail.

PMON resolves failures of distributed transactions.

There is only one SYSTEM tablespace per CDB.

There is only one instance per PDB.

There is a set of redo log files per PDB.

There is only one UNDO tablespace per CDB.

There is one SYSAUXtablespace per PDB.

You can perform complete recovery by using the command:

RESTORE DATABASE

FROM TAG“consistent_whole_backup”;

RECOVER DATABASE;

You can perform incomplete recovery by using the command:

RESTORE DATABASE;

FROM TAG "consistent_whole_backup";

RECOVER DATABASE NOREDO;

Only consistent backups can be used for restoring a database in NOARCHIVELOG mode.

Media recovery is possible in most cases.

It enables you to use third-party technologies to take a storage snapshot of your database without putting the database in BACKUP mode. You can then use the snapshot to recover all or part of the database.

It enables you to use RMAN to take a storage snapshot of your database. The database must be in BACKUP mode. You can then use the snapshot to recover all or part of the database.

It enables you to use RMAN to take a storage snapshot of your database. The database doesn't have to be in BACKUP mode. You can then use the snapshot to recover all or part of the database.

It enables you to use third-party technologies to take a storage snapshot of your database. The database must be in BACKUP mode. You can then use the snapshot to recover all or part of the database.

Tablespace< Segment < Extent < Oracle Datablock

B) Segment < Extent < Oracle Datablock

Tablespace< Extent < Segment < Oracle Datablock

Data File

615 MB

2.5 GB

4 GB

12 GB

22 GB

The database stops (shutdown abort).

B) The database Stops (shutdown immediate).

You activate Automatic Shared Memory Management.

You get an error message.

It is ignored by the query optimizer.

It is not used while the index is being rebuilt.

The index cannot be rebuilt, and has to be re-created.

The index is automatically rebuilt when used the next time.