Oracle Utilities - OCP: Oracle Database 12c Administrator Certified Professional - page 615

■ V$LOGMNR_LOGS
■ V$LOGMNR_LOGFILE
■ V$LOGMNR_PARAMETERS
The DBA views DBA_LOGMNR_LOG , DBA_LOGMNR_PURGED_LOG , and DBA_LOGMNR_SESSION
show the information related to sessions in the current container. Analogous CDB views
( CDB_LOGMNR_LOG , for example) include the CON_ID column, and the previous rule regarding
scope in PDBs and the CDB$ROOT apply.
The V$LOGMNR_CONTENTS View in a CDB The V$LOGMNR_CONTENTS view in a CDB and
its associated functions are restricted to the CDB$ROOT . The following columns have been
added to support CDBs:
■ CON_ID —the container ID for the container where the query was executed.
■ SRC_CON_NAME —the PDB name.
■ SRC_CON_ID —the container ID of the PDB that generated the redo record.
■ SRC_CON_DBID —the PDB identifier.
■ SRC_CON_GUID —the GUID associated with the PDB.
■ SRC_CON_UID —the UID associated with the PDB
Enabling Supplemental Logging in a CDB The syntax for enabling and disabling data-
base-wide supplemental logging is the same whether you're in a non-CDB or a CDB.
SQL> ALTER DATABASE ADD SUPPLEMENTAL LOG DATA;
Database altered.
SQL>
Minimal supplemental logging affects the entire CDB. You can connect to a PDB and turn
on and off other levels of supplemental logging for that individual PDB.
Using a Flat File Dictionary in a CDB Connect to a PDB and take a snapshot of that PDB
in a flat file, as in this example:
EXECUTE DBMS_LOGMNR_D.BUILD('dictionary.ora', -
'/oracle/database/', -
DBMS_LOGMNR_D.STORE_IN_FLAT_FILE);
You can mine the redo logs only for the PDB whose data dictionary is contained within
that flat file. This is not an option for a CDB.