A.Recovery reads redo until the end of the redo thread, and then opens the database. SMON then rolls back any dead transactions.

B.Recovery begins from the last checkpoint position that wascalculated by the Database Writer before instance failure.

C.Recovery begins from the start of any ACTIVE redo log group or the start of the CURRENT log group if no other group is ACTIVE.

D.Recovery begins from the last checkpoint position that was recorded in the control file by the checkpoint process (CKPT).

E.Recovery begins from the beginning of the CURRENT redo log group.

F.Recovery reads redo until the end of the redo thread. SMON rollsback any dead transactions, and then the datanase is opened.

A.If an RMAN command fails, the output will only identify the command that failed.

B.If an RMAN command fails, the output will identify the channel ID where the failure occurred. D)Media Management errors appear as a line with "Additional information" and a number.

C.Media Management errors appear as a line with "sbtio".

D.Media Management errors appear as a line with "sbtio" and a number.

E.Some messages in the error stack are not errors.

A.It contains predefined common roles in both the root and the seed.

B.It can contain only one PDB$SEED, which is created when the CDB is created.

C.It can have any number of pluggable databases (PDBs) limited only by space availability.

D.It can have local users with the same name in different PDBs.

E.It can be created by cloning an existing CDB.

F.It can contain only one Application Container seed, which is created when the Application Container is created.

G.It can be created from a non-CDB.

A.Recovery begins from the beginning of the CURRENT redo log group.

B.Recovery reads redo until the end of the redo thread, and then opens the database. SMON then rolls back any dead transactions.

C.Recovery begins from the start of any ACTIVE redo log group or the start of the CURRENT log group if no other group is ACTIVE.

D.Recovery reads redo until the end of the redo thread. SMON rolls back any dead transactions, and then the datanase is opened.

E.Recovery begins from the last checkpoint position that was calculated by the Database Writer before instance failure.

F.Recovery begins from the last checkpoint position that was recorded in the control file by the checkpoint process (CKPT).

A.flashback drop requires undo to retrieve all versions of a row that existed between two points in time.

B.flashback drop requires that the recyclebin parameter be set to on.

C.flashback data archive requires undo to store all versions of all rows of a table being tracked.

D.flashback transaction query requires undo to retrieve all versions of a row that existed between two points in time.

E.flashback version query requires undo to retrieve all versions of a row that existed between two points in time.

F.flashback version query requires that the recyclebin parameter be set to on.