ORA-01426: numeric overflow
Cause: Evaluation of an value expression causes an overflow or underflow.
Action: Reduce the operands.
Cause: Evaluation of an value expression causes an overflow or underflow.
Action: Reduce the operands.
Saturday 14 January 2012
ORA-01425: escape character must be character string of length 1
ORA-01425: escape character must be character string of length 1
Cause: Given escape character for LIKE is not a character string of length 1.
Action: Change it to a character string of length 1.
Cause: Given escape character for LIKE is not a character string of length 1.
Action: Change it to a character string of length 1.
ORA-01424: missing or illegal character following the escape character
ORA-01424: missing or illegal character following the escape character
Cause: The character following the escape character in LIKE pattern is missing or not one of the escape character, % , or _ .
Action: Remove the escape character or specify the missing character.
Cause: The character following the escape character in LIKE pattern is missing or not one of the escape character, % , or _ .
Action: Remove the escape character or specify the missing character.
ORA-01422: exact fetch returns more than requested number of rows
ORA-01422: exact fetch returns more than requested number of rows
Cause: The number specified in exact fetch is less than the rows returned.
Action: Rewrite the query or change number of rows requested
Cause: The number specified in exact fetch is less than the rows returned.
Action: Rewrite the query or change number of rows requested
ORA-01417: a table may be outer joined to at most one other table
ORA-01417: a table may be outer joined to at most one other table
Cause: a.b (+) = b.b and a.c (+) = c.c is not allowed
Action: Check that this is really what you want, then join b and c first in a view.
Cause: a.b (+) = b.b and a.c (+) = c.c is not allowed
Action: Check that this is really what you want, then join b and c first in a view.
ORA-01415: too many distinct aggregate functions
ORA-01415: too many distinct aggregate functions
Cause: The query contains more distinct aggregates than can be processed. The current limit is 255.
Action: Reduce the number of distinct aggregate functions in the query.
Cause: The query contains more distinct aggregates than can be processed. The current limit is 255.
Action: Reduce the number of distinct aggregate functions in the query.
ORA-01414: invalid array length when trying to bind array
ORA-01414: invalid array length when trying to bind array
Cause: An attempt was made to bind an array without either a current array length pointer or a zero maximum array length.
Action: Sepcify a valid length.
Cause: An attempt was made to bind an array without either a current array length pointer or a zero maximum array length.
Action: Sepcify a valid length.
ORA-01413: illegal value in packed decimal number buffer
ORA-01413: illegal value in packed decimal number buffer
Cause: The user buffer bound by the user as packed decimal number contained an illegal value.
Action: Use a legal value.
Cause: The user buffer bound by the user as packed decimal number contained an illegal value.
Action: Use a legal value.
ORA-01412: zero length not allowed for this datatype
ORA-01412: zero length not allowed for this datatype
Cause: The length for type 97 is 0
Action: Specify the correct length.
Cause: The length for type 97 is 0
Action: Specify the correct length.
ORA-01411: cannot store the length of column in the indicator
ORA-01411: cannot store the length of column in the indicator
Cause: Tried to fetch a column of size more than 64K and couldn t store the length of the column in the given indicator of size 2 bytes.
Action: Use the new bind type with call backs to fetch the long column.
Cause: Tried to fetch a column of size more than 64K and couldn t store the length of the column in the given indicator of size 2 bytes.
Action: Use the new bind type with call backs to fetch the long column.
ORA-01409: NOSORT option may not be used; rows are not in ascending order
ORA-01409: NOSORT option may not be used; rows are not in ascending order
Cause: Creation of index with NOSORT option when rows were not ascending. For non-unique indexes the rowid is considered part of the index key. Therefore, if you create an index nosort and two of the rows in the table have the same key and are stored in ascending order, but get split accross two extents where the dba of the first block in the second extent is less than the dba of the last block in the first extent, then the create index nosort may fail.
Action: Create the index without the NOSORT option, or ensure table is stored in one extent.
Cause: Creation of index with NOSORT option when rows were not ascending. For non-unique indexes the rowid is considered part of the index key. Therefore, if you create an index nosort and two of the rows in the table have the same key and are stored in ascending order, but get split accross two extents where the dba of the first block in the second extent is less than the dba of the last block in the first extent, then the create index nosort may fail.
Action: Create the index without the NOSORT option, or ensure table is stored in one extent.
ORA-01375: Corrupt logfile string recovered
ORA-01375: Corrupt logfile string recovered
Cause: A corrupt logfile has been recovered by RFS
Action: None. Logical Standby should automatically restart. If logfile is still corrupt, may need to manually copy and reregister the logfile on the standby.
Cause: A corrupt logfile has been recovered by RFS
Action: None. Logical Standby should automatically restart. If logfile is still corrupt, may need to manually copy and reregister the logfile on the standby.
ORA-01374: _log_parallelism_max greater than 1 not supported in this release
ORA-01374: _log_parallelism_max greater than 1 not supported in this release
Cause: LogMiner does not mine redo records generated with _log_parallelism_ max set to a value greater than 1.
Action: none
Cause: LogMiner does not mine redo records generated with _log_parallelism_ max set to a value greater than 1.
Action: none
ORA-01373: insufficient memory for staging persistent LogMiner session
ORA-01373: insufficient memory for staging persistent LogMiner session
Cause: The maximum number of concurrent persistent LogMiner sessions allowed is limited by LOGMNR_MAX_PERSISTENT_SESSIONS parameter. Not enough memory has been set aside at instance startup to allocate the new LogMiner session.
Action: Increase LOGMNR_MAX_PERSISTENT_SESSIONS and restart instance.
Cause: The maximum number of concurrent persistent LogMiner sessions allowed is limited by LOGMNR_MAX_PERSISTENT_SESSIONS parameter. Not enough memory has been set aside at instance startup to allocate the new LogMiner session.
Action: Increase LOGMNR_MAX_PERSISTENT_SESSIONS and restart instance.
ORA-01372: Insufficient processes for specified LogMiner operation
ORA-01372: Insufficient processes for specified LogMiner operation
Cause: The number of processes requested by the caller can not be allocated
Action: Increase number of parallel servers allocated to the instance
Cause: The number of processes requested by the caller can not be allocated
Action: Increase number of parallel servers allocated to the instance
ORA-01371: Complete LogMiner dictionary not found
ORA-01371: Complete LogMiner dictionary not found
Cause: One or more log files containing the LogMiner dictionary was not found.
Action: Add into LogMiner all log files containing the dictionary.
Cause: One or more log files containing the LogMiner dictionary was not found.
Action: Add into LogMiner all log files containing the dictionary.
ORA-01370: Specified restart SCN is too old
ORA-01370: Specified restart SCN is too old
Cause: specified restart scn is too old, logmnr could not find a proper checkpoint.
Action: Specify a bigger restart SCN to try again
Cause: specified restart scn is too old, logmnr could not find a proper checkpoint.
Action: Specify a bigger restart SCN to try again
ORA-01361: global name mismatch
ORA-01361: global name mismatch
Cause: The database global name where the log file was generated did not match the user-specified global name of the Streams Capture process.
Action: Start a new capture process and ensure that the user-specified global name matches that of the database that generated the log file.
Cause: The database global name where the log file was generated did not match the user-specified global name of the Streams Capture process.
Action: Start a new capture process and ensure that the user-specified global name matches that of the database that generated the log file.
ORA-01356: active logminer sessions found
ORA-01356: active logminer sessions found
Cause: Logminer sessions are currently active.
Action: End all logminer sessions and retry.
Cause: Logminer sessions are currently active.
Action: End all logminer sessions and retry.
ORA-01355: logminer tablespace change in progress
ORA-01355: logminer tablespace change in progress
Cause: The tables used by logminer are in the process of being moved to another tablespace.
Action: Wait until the move is complete and try again.
Cause: The tables used by logminer are in the process of being moved to another tablespace.
Action: Wait until the move is complete and try again.
ORA-01354: Supplemental log data must be added to run this command
ORA-01354: Supplemental log data must be added to run this command
Cause: An attempt was made to perform an operation that required that supplemental log data be enabled.
Action: Execute a command such as ALTER DATABASE ADD SUPPLEMENTAL LOG DATA; and then reissue the command that failed with this error.
Cause: An attempt was made to perform an operation that required that supplemental log data be enabled.
Action: Execute a command such as ALTER DATABASE ADD SUPPLEMENTAL LOG DATA; and then reissue the command that failed with this error.
ORA-01353: existing Logminer session
ORA-01353: existing Logminer session
Cause: An attempt was made to execute DBMS_LOGMNR_D.SET_TABLESPACE while a Logminer session(s) was active.
Action: First cause all Logminer sessions to be closed. A Logminer session can exist as a result of executing DBMS_LOGMNR.START_LOGMNR or as the result of using Oracle features such as Data Guard SQL Apply or Streams which use Logminer. Next, execute DBMS_LOGMNR_D.SET_TABLESPACE.
Cause: An attempt was made to execute DBMS_LOGMNR_D.SET_TABLESPACE while a Logminer session(s) was active.
Action: First cause all Logminer sessions to be closed. A Logminer session can exist as a result of executing DBMS_LOGMNR.START_LOGMNR or as the result of using Oracle features such as Data Guard SQL Apply or Streams which use Logminer. Next, execute DBMS_LOGMNR_D.SET_TABLESPACE.
ORA-01352: tablespace given for Logminer spill does not exist
ORA-01352: tablespace given for Logminer spill does not exist
Cause: The tablespace name given as the parameter to DBMS_LOGMNR_D.SET_ TABLESPACE does not exist.
Action: Check spelling of the tablespace name. If spelling is correct verify that the named tablespace has already been created. DBMS_LOGMNR_D.SET_ TABLESPACE does not create a tablespace.
Cause: The tablespace name given as the parameter to DBMS_LOGMNR_D.SET_ TABLESPACE does not exist.
Action: Check spelling of the tablespace name. If spelling is correct verify that the named tablespace has already been created. DBMS_LOGMNR_D.SET_ TABLESPACE does not create a tablespace.
ORA-01351: tablespace given for Logminer dictionary does not exist
ORA-01351: tablespace given for Logminer dictionary does not exist
Cause: The tablespace name given as a parameter to DBMS_LOGMNR_D.SET_ TABLESPACE does not exist.
Action: Check spelling of the tablespace name. If spelling is correct verify that the named tablespace has already been created. DBMS_LOGMNR_D.SET_ TABLESPACE does not create a tablespace.
Cause: The tablespace name given as a parameter to DBMS_LOGMNR_D.SET_ TABLESPACE does not exist.
Action: Check spelling of the tablespace name. If spelling is correct verify that the named tablespace has already been created. DBMS_LOGMNR_D.SET_ TABLESPACE does not create a tablespace.
ORA-01350: must specify a tablespace name
ORA-01350: must specify a tablespace name
Cause: Invocation failed to specify a valid tablespace
Action: Reformat invocation of DBMS_LOGMNR_D.SET_TABLESPACE to include the name of a valid tablespace.
Cause: Invocation failed to specify a valid tablespace
Action: Reformat invocation of DBMS_LOGMNR_D.SET_TABLESPACE to include the name of a valid tablespace.
ORA-01347: Supplemental log data no longer found
ORA-01347: Supplemental log data no longer found
Cause: The source database instance producing log files for this LogMiner session was altered to no longer log supplemental data.
Action: Destroy this Logminer session. Re-enable supplemental log data on the source system and create a new LogMiner session.
Cause: The source database instance producing log files for this LogMiner session was altered to no longer log supplemental data.
Action: Destroy this Logminer session. Re-enable supplemental log data on the source system and create a new LogMiner session.
ORA-01346: LogMiner processed redo beyond specified reset log scn
ORA-01346: LogMiner processed redo beyond specified reset log scn
Cause: LogMiner has detected a new branch with resetlogs scn information prior to redo already mined.
Action: Contact your customer support representative.
Cause: LogMiner has detected a new branch with resetlogs scn information prior to redo already mined.
Action: Contact your customer support representative.
ORA-01345: must be a LogMiner coordinator process
ORA-01345: must be a LogMiner coordinator process
Cause: A LogMiner client attempted to perform a privileged operation.
Action: Issue the operation from the coordinator process.
Cause: A LogMiner client attempted to perform a privileged operation.
Action: Issue the operation from the coordinator process.
ORA-01344: LogMiner coordinator already attached
ORA-01344: LogMiner coordinator already attached
Cause: A coordinator process is already attached to the specified logminer context.
Action: Detach from the active coordinator session and retry the attach.
Cause: A coordinator process is already attached to the specified logminer context.
Action: Detach from the active coordinator session and retry the attach.
ORA-01343: LogMiner encountered corruption in the logstream
ORA-01343: LogMiner encountered corruption in the logstream
Cause: Log file is missing a range of scn values.
Action: Verify the contiguity of the scn range reprented by the log files added to LogMiner.
Cause: Log file is missing a range of scn values.
Action: Verify the contiguity of the scn range reprented by the log files added to LogMiner.
ORA-01342: LogMiner can not resume session due to inability of staging checkpointed data
ORA-01342: LogMiner can not resume session due to inability of staging checkpointed data
Cause: Logmnr can not resume session because there is not enough SGA memory available to read in checkpointed data. Logminer periodically checkpoints data to enable faster crash recovery.
Action: Specify a bigger max_sga for the given LogMiner session and try again.
Cause: Logmnr can not resume session because there is not enough SGA memory available to read in checkpointed data. Logminer periodically checkpoints data to enable faster crash recovery.
Action: Specify a bigger max_sga for the given LogMiner session and try again.
ORA-01341: LogMiner out-of-memory
ORA-01341: LogMiner out-of-memory
Cause: The LogMiner session requires more system resources than is currently available.
Action: Allocate more SGA for LogMiner.
Cause: The LogMiner session requires more system resources than is currently available.
Action: Allocate more SGA for LogMiner.
ORA-01338: Other process is attached to LogMiner session
ORA-01338: Other process is attached to LogMiner session
Cause: Can not do this when other process is attached to LogMiner session.
Action: none
Cause: Can not do this when other process is attached to LogMiner session.
Action: none
ORA-01337: log file has a different compatibility version
ORA-01337: log file has a different compatibility version
Cause: The logfile has a different compatibility version then the rest of the logfile in the session
Action: Make sure that the logfile has the same compatibility version as the rest of the logfiles in the session.
Cause: The logfile has a different compatibility version then the rest of the logfile in the session
Action: Make sure that the logfile has the same compatibility version as the rest of the logfiles in the session.
ORA-01336: specified dictionary file cannot be opened
ORA-01336: specified dictionary file cannot be opened
Cause: The dictionary file or directory does not exist or is inaccessible.
Action: Make sure that the dictionary file and directory exist and are accessible.
Cause: The dictionary file or directory does not exist or is inaccessible.
Action: Make sure that the dictionary file and directory exist and are accessible.
ORA-01334: invalid or missing logminer dictionary processes context
ORA-01334: invalid or missing logminer dictionary processes context
Cause: Unexpected internal error condition
Action: none
Cause: Unexpected internal error condition
Action: none
ORA-01333: failed to establish Logminer Dictionary
ORA-01333: failed to establish Logminer Dictionary
Cause: No previously established Logminer Dictionary is available and a complete gather of a source system data dictionary was not found in the logstream. build() may not have been run to force the gathering of a source system data dictiony. Or add_log_file() may not have been called to add all log files which contain the complete gathered system data dictionary.
Action: If build() was not employed prior to this mining session the Logminer Ad Hoc user may elect to employ an alternate dictionary such as the current system catalog or a previously built flat file dictionary. Other Logminer clients must run build() prior to mining. If build() has been run, ensure that all logfiles which comprise the gathered system dictionary have beed added. The following query, run on the system which build() was run, can be helpful in identifying the requried files. select DICTIONARY_BEGIN, DICTIONARY_END, name from v$archived_log; Minimally a set of files beginning with one which has DICTIONARY_BEGIN = YES and all following log files through one marked DICTIONARY_END = YES must be added.
Cause: No previously established Logminer Dictionary is available and a complete gather of a source system data dictionary was not found in the logstream. build() may not have been run to force the gathering of a source system data dictiony. Or add_log_file() may not have been called to add all log files which contain the complete gathered system data dictionary.
Action: If build() was not employed prior to this mining session the Logminer Ad Hoc user may elect to employ an alternate dictionary such as the current system catalog or a previously built flat file dictionary. Other Logminer clients must run build() prior to mining. If build() has been run, ensure that all logfiles which comprise the gathered system dictionary have beed added. The following query, run on the system which build() was run, can be helpful in identifying the requried files. select DICTIONARY_BEGIN, DICTIONARY_END, name from v$archived_log; Minimally a set of files beginning with one which has DICTIONARY_BEGIN = YES and all following log files through one marked DICTIONARY_END = YES must be added.
ORA-01332: internal Logminer Dictionary error
ORA-01332: internal Logminer Dictionary error
Cause: Unexpected error condition
Action: Check trace and or or alert logs
Cause: Unexpected error condition
Action: Check trace and or or alert logs
ORA-01329: unable to truncate required build table
ORA-01329: unable to truncate required build table
Cause: The table may be missing, or locked by another user.
Action: none
Cause: The table may be missing, or locked by another user.
Action: none
ORA-01328: only one build operation may occur at one time
ORA-01328: only one build operation may occur at one time
Cause: Another processes is simultaneously attempting to run build();
Action: Wait until the other processes completes.
Cause: Another processes is simultaneously attempting to run build();
Action: Wait until the other processes completes.
ORA-01327: failed to exclusively lock system dictionary as required by build
ORA-01327: failed to exclusively lock system dictionary as required by build
Cause: Other users are performing DDL operations.
Action: none
Cause: Other users are performing DDL operations.
Action: none
ORA-01326: compatability of 9.0 or greater required to build into the logstream
ORA-01326: compatability of 9.0 or greater required to build into the logstream
Cause: Compatibility mode set to some value less than 9.0
Action: Ensure that init.ora parameter establishing a compatability of 9.0 or greater is set. For example: compatible=9.0.0.0.0
Cause: Compatibility mode set to some value less than 9.0
Action: Ensure that init.ora parameter establishing a compatability of 9.0 or greater is set. For example: compatible=9.0.0.0.0
ORA-01325: archive log mode must be enabled to build into the logstream
ORA-01325: archive log mode must be enabled to build into the logstream
Cause: Database does not have archivelog mode enabled.
Action: Mount the database, then issue commands to enable archivelog mode. startup pfile=init.ora mount alter database archivelog alter database open
Cause: Database does not have archivelog mode enabled.
Action: Mount the database, then issue commands to enable archivelog mode. startup pfile=init.ora mount alter database archivelog alter database open
ORA-01324: cannot add file string due to DB_ID mismatch
ORA-01324: cannot add file string due to DB_ID mismatch
Cause: The logfile is produced by a different database than other logfiles already added to the list.
Action: Specify a logfile produced by the same database.
Cause: The logfile is produced by a different database than other logfiles already added to the list.
Action: Specify a logfile produced by the same database.
ORA-01323: Invalid state
ORA-01323: Invalid state
Cause: A Logminer routine was called from the wrong state.
Action: none
Cause: A Logminer routine was called from the wrong state.
Action: none
ORA-01322: No such table
ORA-01322: No such table
Cause: An non-existent table was supplied to Logminer include_src_tbl() or exclude_src_table().
Action: Re-issue with valid table name.
Cause: An non-existent table was supplied to Logminer include_src_tbl() or exclude_src_table().
Action: Re-issue with valid table name.
ORA-01320: Invalid Logminer dictionar attribute
ORA-01320: Invalid Logminer dictionar attribute
Cause: A Logminer dictionary attribute was supplied which is invalid.
Action: Re-issue with valid dictionary attribute.
Cause: A Logminer dictionary attribute was supplied which is invalid.
Action: Re-issue with valid dictionary attribute.
ORA-01319: Invalid Logminer session attribute
ORA-01319: Invalid Logminer session attribute
Cause: A session attribute was supplied which is invalid.
Action: Re-issue with valid session attribute.
Cause: A session attribute was supplied which is invalid.
Action: Re-issue with valid session attribute.
ORA-01317: Not attached to a Logminer session
ORA-01317: Not attached to a Logminer session
Cause: A command or procedure was issued which requires an attached Logminer session.
Action: Attach to a Logminer session before issuing the command or procedure.
Cause: A command or procedure was issued which requires an attached Logminer session.
Action: Attach to a Logminer session before issuing the command or procedure.
ORA-01316: Already attached to a Logminer session
ORA-01316: Already attached to a Logminer session
Cause: A Logminer attach session was issued while already attached to a Logminer session.
Action: Detach from the current Logminer session and attach to the requested session.
Cause: A Logminer attach session was issued while already attached to a Logminer session.
Action: Detach from the current Logminer session and attach to the requested session.
ORA-01315: Log file has been added or removed during select
ORA-01315: Log file has been added or removed during select
Cause: A redo log file has been added or removed while selecting on the v$logmnr_logs fixed view.
Action: Re-issue the SQL select statement on the v$logmnr_logs view.
Cause: A redo log file has been added or removed while selecting on the v$logmnr_logs fixed view.
Action: Re-issue the SQL select statement on the v$logmnr_logs view.
ORA-01314: Name of the column to be mined should be a string literal
ORA-01314: Name of the column to be mined should be a string literal
Cause: The fully qualified name of the column to be mined by the LogMiner functions should be string literal.
Action: If the fully qualified name of the column to be mined is a.b.c.d, enclose the column name in quotes as in a.b.c.d .
Cause: The fully qualified name of the column to be mined by the LogMiner functions should be string literal.
Action: If the fully qualified name of the column to be mined is a.b.c.d, enclose the column name in quotes as in a.b.c.d .
ORA-01313: LogMiner dictionary column type different from specified type
ORA-01313: LogMiner dictionary column type different from specified type
Cause: The return type specified for the column in lcr_mine call is different from the actual type of the column.
Action: Rewrite the lcr_mine invocation with the right return type.
Cause: The return type specified for the column in lcr_mine call is different from the actual type of the column.
Action: Rewrite the lcr_mine invocation with the right return type.
ORA-01312: Specified table or column does not exist
ORA-01312: Specified table or column does not exist
Cause: The table or column specified in the lcr_mine call does not exist at the the specified SCN. The table or column definition has to exist at the start SCN specified for lcr_mine to be able to identify the table or column correctly.
Action: Create a LogMiner session at a start SCN at which the table definition is available.
Cause: The table or column specified in the lcr_mine call does not exist at the the specified SCN. The table or column definition has to exist at the start SCN specified for lcr_mine to be able to identify the table or column correctly.
Action: Create a LogMiner session at a start SCN at which the table definition is available.
ORA-01311: Illegal invocation of the mine_value function
ORA-01311: Illegal invocation of the mine_value function
Cause: An attempt was made to use mine_value function on a column other than redo_value or undo_value columns of SYS.X$LOGMNR_CONTENTS or SYS.V$LOGMNR_CONTENTS fixed table or view.
Action: Rewrite the SQL statement with a legal invocation of mine_value
Cause: An attempt was made to use mine_value function on a column other than redo_value or undo_value columns of SYS.X$LOGMNR_CONTENTS or SYS.V$LOGMNR_CONTENTS fixed table or view.
Action: Rewrite the SQL statement with a legal invocation of mine_value
ORA-01310: requested return type not supported by the lcr_mine function
ORA-01310: requested return type not supported by the lcr_mine function
Cause: The return type requested by the user is not supported by lcr_mine
Action: Pick a return type supported by the lcr_mine function
Cause: The return type requested by the user is not supported by lcr_mine
Action: Pick a return type supported by the lcr_mine function
ORA-01309: invalid session
ORA-01309: invalid session
Cause: The specified Logminer session ID or session handle is invalid.
Action: Use a valid Logminer session ID or session handle.
Cause: The specified Logminer session ID or session handle is invalid.
Action: Use a valid Logminer session ID or session handle.
ORA-01308: initialization parameter utl_file_dir is not set
ORA-01308: initialization parameter utl_file_dir is not set
Cause: utl_file_dir is not set in the initialization file.
Action: Set utl_file_dir to the appropriate directory.
Cause: utl_file_dir is not set in the initialization file.
Action: Set utl_file_dir to the appropriate directory.
ORA-01307: no LogMiner session is currently active
ORA-01307: no LogMiner session is currently active
Cause: A select was issued from v$logmnr_contents without first invoking the dbms_logmnr.start_logmnr() procedure. Otherwise, dbms_logmnr.end_logmnr() was called without a prior call to dbms_logmnr.start_logmnr() or dbms_ logmnr.add_logfile()
Action: Invoke the dbms_logmnr.start_logmnr() procedure before issuing a select from the v$logmnr_contents view.
Cause: A select was issued from v$logmnr_contents without first invoking the dbms_logmnr.start_logmnr() procedure. Otherwise, dbms_logmnr.end_logmnr() was called without a prior call to dbms_logmnr.start_logmnr() or dbms_ logmnr.add_logfile()
Action: Invoke the dbms_logmnr.start_logmnr() procedure before issuing a select from the v$logmnr_contents view.
Subscribe to:
Posts (Atom)