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).
CONTINUOUS_MINE
BINARY_INTEGER
1024
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.
DDL_DICT_TRACKING
BINARY_INTEGER
8
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 and cannot be used when the LogMiner dictionary being used is one that was extracted to a flat file prior to Oracle9i.
DICT_FROM_ONLINE_CATALOG
BINARY_INTEGER
16
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 V$LOGMNR_CONTENTS view if the table definition in the database does not match the table definition in the redo log file.
DICT_FROM_REDO_LOGS
BINARY_INTEGER
32
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.
NO_DICT_RESET_ONSELECT
BINARY_INTEGER
1
Will be deprecated soon
NO_ROWID_IN_STMT
BINARY_INTEGER
2048
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.
NO_SQL_DELIMITER
BINARY_INTEGER
64
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.
PRINT_PRETTY_SQL
BINARY_INTEGER
512
If set, LogMiner formats the reconstructed SQL statements for ease of reading. These reconstructed SQL statements are not executable.
SKIP_CORRUPTION
BINARY_INTEGER
4
Directs a select operation on the V$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 V$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.
Status column option flags
Name
Data Type
Value
CORRUPTED_BLK_IN_REDO
BINARY_INTEGER
32
HOLE_IN_LOGSTREAM
BINARY_INTEGER
13
INVALID_SQL
BINARY_INTEGER
2
UNGUARANTEED_SQL
BINARY_INTEGER
3
VALID_SQL
BINARY_INTEGER
0
Workarounds for the lack of constrained subtypes
LogFileNameTemplate VARCHAR2(256);
SUBTYPE LogFileName IS LogFileNameTemplate%TYPE;
LogFileDescTemplate VARCHAR2(256);
SUBTYPE LogFileDescription IS LogFileDescTemplate%TYPE;
Data Types
SUBTYPE Length IS BINARY_INTEGER;
SUBTYPE ThreadId IS BINARY_INTEGER;
Dependencies
DBA_LOGMNR_LOG
GV_$LOGMNR_STATS
DBA_LOGMNR_PURGED_LOG
GV_$LOGMNR_TRANSACTION
DBA_LOGMNR_SESSION
V_$LOGMNR_CALLBACK
DBMS_LOGMNR_INTERNAL
V_$LOGMNR_CONTENTS
DBMS_STREAMS_ADM_UTL
V_$LOGMNR_DICTIONARY
GV_$LOGMNR_CALLBACK
V_$LOGMNR_DICTIONARY_LOAD
GV_$LOGMNR_CONTENTS
V_$LOGMNR_LATCH
GV_$LOGMNR_DICTIONARY
V_$LOGMNR_LOGFILE
GV_$LOGMNR_DICTIONARY_LOAD
V_$LOGMNR_LOGS
GV_$LOGMNR_LATCH
V_$LOGMNR_PARAMETERS
GV_$LOGMNR_LOGFILE
V_$LOGMNR_PROCESS
GV_$LOGMNR_LOGS
V_$LOGMNR_REGION
GV_$LOGMNR_PARAMETERS
V_$LOGMNR_SESSION
GV_$LOGMNR_PROCESS
V_$LOGMNR_STATS
GV_$LOGMNR_REGION
V_$LOGMNR_TRANSACTION
GV_$LOGMNR_SESSION
Exceptions
Number
Description
ORA-00904
Value specified for the column_name parameter is not a fully qualified column name.
ORA-01281
startScn or endSCN parameter specified is not a valid SCN or endScn is greater then startScn
ORA-01282
startTime parameter not between years 1988 and 2110 or endTime parameter is greater than year 2110
ORA-01283
The value specified in the Options parameter is not a NUMBER or is not a known LogMiner Adhoc option
ORA-01284
The dictionary file specified in DictFileName parameter has a length greater then 256 or cannot be opened
ORA-01285
DictFileName parameter is not a valid VARCHAR2
ORA-01286
Options specified require start time or start SCN
ORA-01287
Specified file is from a different database incarnation
ORA-01289
Specified file has already been added to the list. Duplicate redo log files cannot be added.
ORA-01290
Specified file is not in the current list and therefore cannot be removed from the list.
ORA-01291
Redo files are missing which are needed to satisfy the user's requested SCN/time range. The user can specify ALLOW_MISSING_LOGS option. Missing logs are not allowed when DDL tracking is in use
ORA-01292
No log file has been registered with LogMiner
ORA-01293
Mounted database required for options specified (CONTINIOUS_MINE)
ORA-01294
Error while processing the data dictionary extract
ORA-01295
DB_ID of the data dictionary does not match that of the redo logs
ORA-01296
Character set specified in the data dictionary does not match (is incompatible with) that of the database
ORA-01297
Redo version mismatch between the dictionary and the registered redo logs
ORA-01298
More than one dictionary source was specified or DDL_DICT_TRACKING was requested with DICT_FROM_ONLINE_CATALOG
ORA-01299
Dictionary is from a different database incarnation
ORA-01300
Writable database required for options specified (DDL_DICT_TRACKING, DICT_FROM_REDO_LOGS, DICT_FROM_ONLINE_CATALOG)
ORA-01323
A LogMiner dictionary is not associated with the LogMiner session
ORA-01324
Specified file cannot be added to the list because there is a DB_ID mismatch.
ORA-01371
A logfile containing the dictionary dump to redo logs is missing
Pragma
pragma TIMESTAMP('1998-05-05:11:25:00');
Security Model
Execute granted to execute_catalog_role
-- either GRANT execute catalog role TO uwclass; - or GRANT select ON v_$logmnr_contents TO uwclass;
Designed to be used in conjunction with the MINE_VALUE function. If the MINE_VALUE function returns a NULL value, it can mean either the specified column is not present in the redo or undo portion of the data or the specified column is present and is NULL.
SELECT v.scn, v.commit_timestamp, v.table_name, o.object_name, v.operation FROM sys.v_$logmnr_contents v, dba_objects o WHERE SUBSTR(v.table_name,6) = o.object_id;
SELECT info FROM gv$logmnr_contents;
SELECT sql_redo, sql_undo FROM gv$logmnr_contents WHERE username = 'UWCLASS';
SELECT utl_raw.cast_to_varchar2(HEXTORAW('53414c')) FROM dual; NWO HEXTORAW('4e574f') USAF HEXTORAW('55534146') DAL HEXTORAW('44414c') SAL 53414c
SELECT sql_redo FROM gv$logmnr_contents WHERE seg_name = 'AIRPLANES' AND seg_owner = 'UWCLASS' AND operation = 'UPDATE' AND dbms_logmnr.mine_value(REDO_VALUE) <> dbms_logmnr.mine_value(UNDO_VALUE);
-- need query with COLUMN_PRESENT (finds it and doesn't find it)
exec sys.dbms_logmnr.end_logmnr;
REMOVE_LOGFILE
Removes a redo log file from an existing list of redo log files for LogMiner to process
dbms_logmnr.remove_logfile(LogFileName VARCHAR2);
TBD
START_LOGMNR
Begin a log miner session
dbms_logmnr.start_logmnr( startscn NUMBER DEFAULT 0, endscn NUMBER DEFAULT 0, starttime DATE DEFAULT '01-JAN-1988', endtime DATE DEFAULT '31-DEC-2110', dictfilename VARCHAR2 DEFAULT '', options BINARY_INTEGER DEFAULT 0);
3161
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
