START_LOGMNR Procedure

This procedure starts a LogMiner session.

Note: This procedure fails if you did not specify a list of redo log files to be analyzed previously through the ADD_LOGFILE procedure.

Syntax

DBMS_LOGMNR.START_LOGMNR( 
   startScn           IN NUMBER default 0,
   endScn             IN NUMBER default 0,
   startTime          IN DATE default '01-jan-1988',
   endTime            IN DATE default '01-jan-2988',
   DictFileName       IN VARCHAR2 default '',
   Options            IN BINARY_INTEGER default 0 );

Parameters

The parameters for the DBMS_LOGMNR.START_LOGMNR procedure are listed in Table 24-3.

Table 24-3 START_LOGMNR Procedure Parameters

Parameter	Description
startScn	Only consider redo records with SCN greater than or equal to the startSCN specified. This fails if there is no redo log file with an SCN range (i.e, the LOW_SCN and NEXT_SCN associated with the log file as shown in V$LOGMNR_LOGS view) containing the startScn.
endScn	Only consider redo records with SCN less than or equal to the endSCN specified. This fails if there is no redo log file with an SCN range (i.e, the LOW_SCN and NEXT_SCN associated with the log file as shown in V$LOGMNR_LOGS view) containing the endScn.
startTime	Only consider redo records with timestamp greater than or equal to the startTime specified. This fails if there is no redo log file with a time range (i.e, the LOW_TIME and HIGH_TIME associated with the log file as shown in V$LOGMNR_LOGS view) containing the startTime. This parameter is ignored if startScn is specified.
endTime	Only consider redo records with timestamp less than or equal to the endTime specified. This fails if there is no redo log file with a time range (i.e, the LOW_TIME and HIGH_TIME associated with the log file as shown in V$LOGMNR_LOGS view) containing the endTime. This parameter is ignored if endScn is specified.
DictFileName	This flat file contains a snapshot of the database catalog. It is used to reconstruct SQL_REDO and SQL_UNDO columns in V$LOGMNR_CONTENTS, as well as to fully translate SEG_NAME, SEG_OWNER, SEG_TYPE_NAME and TABLE_SPACE columns. The fully qualified pathname for the dictionary file must be specified (This file must have been created previously through the DBMS_LOGMNR_D.BUILD procedure). You only need to specify this parameter if neither DICT_FROM_REDO_LOGS nor DICT_FROM_ONLINE_CATALOG is specified.
Options	See "Constants for START_LOGMNR Options Flag".

After executing the START_LOGMNR procedure, you can make use of the following views:

• V$LOGMNR_DICTIONARY - contains current information about the dictionary file

• V$LOGMNR_PARAMETERS - contains information about the LogMiner session

• V$LOGMNR_LOGS - contains information about the redo log files being analyzed

Exceptions

• ORA-1280: The procedure fails with this exception if LogMiner encounters an internal error

• ORA-1281: endScn is less than startScn

• ORA-1282: endDate is earlier than startDate

• ORA-1283: Invalid options is specified

• ORA-1293: The procedure fails with this exception for the following reasons:
  1. No logfile has (LOW_SCN, NEXT_SCN) range containing the startScn specified.

  2. No logfile has (LOW_SCN, NEXT_SCN) range containing the endScn specified.

  3. No logfile has (LOW_TIME, HIGH_TIME) range containing the startTime specified.

  4. No logfile has (LOW_TIME, HIGH_TIME) range containing the endTime specified.

• ORA-1294: Dictionary file specified is corrupt.

• ORA-1295: Dictionary specified does not correspond to the same database that produced the logfiles being analyzed.