The Library is currently in the process of being upgraded from Oracle Database Version 220.127.116.11 to
18.104.22.168. Demos are being upgraded to reflect the new Container paradigm as well as EBR (Edition Based Redefinition) and may contain
references to CDBs, PDBs, and other objects you may not be familiar with such as CDB_OBJECTS_AE: Welcome to 12c.
Interested in Oracle GoldenGate? Check out the IGGOUG,
Enables online query online of archived redo log files through a SQL interface and provides most of the tools requiredd to start and stop log mining.
Add archive log option flags
Status column option flags
Start LOGMNR option flags
If set, DML statements corresponding to committed transactions are returned.
DML statements corresponding to a committed transaction are grouped together. Transactions are returned in their commit order.
Transactions that are rolled back or in-progress are filtered out, as are internal redo records (those related to index operations, management, and so on).
If this option is not set, all rows for all transactions (committed, rolled back, and in-progress) are returned in the order in which they are found in the redo logs (in order of SCN values).
Directs LogMiner to automatically add redo log files, as needed, to find the data of interest.
You only need to specify the first log to start mining, or just the starting SCN or date to indicate to LogMiner where to begin mining logs. You are not required to specify any redo log files explicitly.
LogMiner automatically adds and mines the (archived and online) redo log files for the data of interest. This option requires that LogMiner is connected to the same database instance that is generating the redo log files.
It also requires that the database be mounted and that archiving be enabled.
Beginning with Oracle Database release 10.1, the CONTINUOUS_MINE options is supported for use in an Oracle Real Application Clusters environment.
If the LogMiner dictionary in use is a flat file or in the redo log files, LogMiner updates its internal dictionary if a DDL event occurs.
This ensures that correct SQL_REDO and SQL_UNDO information is maintained for objects that are modified after the LogMiner internal dictionary is built. The database to which LogMiner is connected must be open.
This option cannot be used in conjunction with the DICT_FROM_ONLINE_CATALOG option.
Directs LogMiner to use the current online database dictionary rather than a LogMiner dictionary contained in a flat file or in the redo log files being analyzed.
This option cannot be used in conjunction with the DDL_DICT_TRACKING option. The database to which LogMiner is connected must be the same one that generated the redo log files.
Expect to see a value of 2 in the STATUS column of the GV$LOGMNR_CONTENTS view if the table definition in the database does not match the table definition in the redo log file.
If set, LogMiner expects to find a LogMiner dictionary in the redo log files that were specified.
The redo log files are specified with the DBMS_LOGMNR.ADD_LOGFILE procedure or with the DBMS_LOGMNR.START_LOGMNR procedure with the CONTINUOUS_MINE option.
Will be deprecated soon
If set, the ROWID clause is not included in the reconstructed SQL statements.
The redo log file may already contain logically unique identifiers for modified rows if supplemental logging is enabled.
When using this option, you must be sure that supplemental logging was enabled in the source database at the appropriate level and that no duplicate rows exist in the tables of interest.
LogMiner does not make any guarantee regarding the uniqueness of logical row identifiers.
If set, the SQL delimiter (a semicolon) is not placed at the end of reconstructed SQL statements.
This is helpful for applications that open a cursor and then execute the reconstructed statements.
If set, LogMiner formats the reconstructed SQL statements for ease of reading. These reconstructed SQL statements are not executable.
Directs a select operation on the GV$LOGMNR_CONTENTS view to skip any corruptions in the redo log file being analyzed and continue processing.
This option works only when a block in the redo log file (and not the header of the redo log file) is corrupt.
You should check the INFO column in the GV$LOGMNR_CONTENTS view to determine the corrupt blocks skipped by LogMiner.
When a corruption in the redo log file is skipped, the OPERATION column contains the value CORRUPTED_BLOCKS, and the STATUS column contains the value 1343.
SUBTYPE Length IS BINARY_INTEGER;
SUBTYPE ThreadId IS BINARY_INTEGER;
-- workarounds for the lack of constrained subtypes
SUBTYPE LogFileName IS LogFileNameTemplate%TYPE;
SUBTYPE LogFileDescription IS LogFileDescTemplate%TYPE;
Value specified for the column_name parameter is not a fully qualified column name.
startScn or endSCN parameter specified is not a valid SCN or endScn is greater then startScn
startTime parameter not between years 1988 and 2110 or endTime parameter is greater than year 2110
The value specified in the Options parameter is not a NUMBER or is not a known LogMiner Adhoc option
Specified dictionary file in DictFileName parameter has a length greater then 256 or cannot be opened
DictFileName parameter is not a valid VARCHAR2
Options specified require start time or start SCN
Specified file is from a different database incarnation
Specified file has already been added to the list. Duplicate redo log files cannot be added.
Specified file is not in the current list and therefore cannot be removed from the list.
Redo files needed to satisfy the user's requested SCN/time range are missing. The user can specify ALLOW_MISSING_LOGS option. Missing logs are not allowed when DDL tracking is in use
No log file has been registered with LogMiner
Mounted database required for options specified (CONTINUOUS_MINE)
Error while processing the data dictionary extract
DB_ID of the data dictionary does not match that of the redo logs
Character set specified in the data dictionary does not match (is incompatible with) that of the database
Redo version mismatch between the dictionary and the registered redo logs
More than one dictionary source was specified or DDL_DICT_TRACKING was requested with DICT_FROM_ONLINE_CATALOG
Dictionary is from a different database incarnation
Writable database required for options specified (DDL_DICT_TRACKING, DICT_FROM_REDO_LOGS,
A LogMiner dictionary is not associated with the LogMiner session
Specified file cannot be added to the list because there is a DB_ID mismatch.
A logfile containing the dictionary dump to redo logs is missing
Owned by SYS with EXECUTE granted to the EXECUTE_CATALOG_ROLE role
SELECT v.scn, v.commit_timestamp, v.table_name, o.object_name, v.operation
FROM sys.v_$logmnr_contents v, dba_objects_ae o
WHERE SUBSTR(v.table_name,6) = o.object_id;
conn / as sysdba
STARTUP MOUNT EXCLUSIVE;
ALTER DATABASE NOARCHIVELOG;
ALTER DATABASE OPEN;
SELECT sql_redo, sql_undo
WHERE username = 'UWCLASS';
SELECT utl_raw.cast_to_varchar2(HEXTORAW('53414c')) FROM dual;
WHERE seg_name = 'AIRPLANES'
AND seg_owner = 'UWCLASS'
AND operation = 'UPDATE'
AND sys.dbms_logmnr.mine_value(REDO_VALUE, 'CUSTOMER_ID') <> sys.dbms_logmnr.mine_value(UNDO_VALUE, 'CUSTOMER_ID');
startscn IN NUMBER DEFAULT 0,
endscn IN NUMBER DEFAULT 0,
starttime IN DATE DEFAULT '',
endtime IN DATE DEFAULT '',
dictfilename IN VARCHAR2 DEFAULT '',
options IN BINARY_INTEGER DEFAULT 0);