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

YES or IMPLICIT indicates that supplemental logging is enabled: YES if the SQL ALTER
DATABASE ADD SUPPLEMENTAL LOG DATA statement was issued, or IMPLICIT if database-level
identification key logging options are enabled.
exeRCiSe 13.3
Steps for Using logMiner
To use LogMiner, you execute procedures in the DBMS_LOGMNR and DBMS_LOGMNR_D PL/SQL
supplied packages and query data from the V$LOGMNR_CONTENTS view. The EXECUTE_
CATALOG_ROLE role and the LOGMINING privilege are required to query the V$LOGMNR_
CONTENTS view and to execute the LogMiner PL/SQL packages.
1. Use the DBMS_LOGMNR_D.BUILD procedure or specify the LogMiner dictionary when
you start LogMiner.
2. Use the DBMS_LOGMNR.ADD_LOGFILE procedure, or direct LogMiner to create a list of
log files for analysis automatically when you start LogMiner.
3. Start LogMiner by executing the DBMS_LOGMNR.START_LOGMNR procedure.
4. Query the V$LOGMNR_CONTENTS view.
5. End LogMiner by executing the DBMS_LOGMNR.END_LOGMNR procedure.
Using LogMiner in a CDB
You can use LogMiner a multitenant CDB. There are some differences when using LogMiner
in a CDB compared to a non-CDB, and we'll explain them here:
LogMiner V$ Views and DBA Views in a CDB The views used to show LogMiner infor-
mation in a CDB contain the additional column CON_ID , which identifies the container ID
associated with the session ID. When you query the same view from a PDB, you'll see only
information associated with the current PDB. When you query from the CDB$ROOT you'll
see all rows in the CDB. Here's the list of LogMiner V$ views:
■ V$LOGMNR_DICTIONARY_LOAD
■ V$LOGMNR_LATCH
■ V$LOGMNR_PROCESS
■ V$LOGMNR_SESSION
■ V$LOGMNR_STATS
■ V$LOGMNR_TRANSACTION
These views do not contain a session ID column but do contain the CON_ID column:
■ V$LOGMNR_CONTENTS
■ V$LOGMNR_DICTIONARY