Oracle 12c R2 Error Codes and Solution Suggestions from ORA-01300 to ORA-01400
- ORA-01300: writable database required for specified LogMiner options
Cause: Options were specified which required the database to be writable.
Action: Specify different options or open the database for write access.
Cause: Error writing to file during flat file build
Action: n/a
Cause: Missing dictionary build options or incorrectly specified options
Action: Specify either a build to redo log or to flat file. If build to flat file, specify filename and directory.
Cause: A process subordinate to this Logminer process has exited with this error status.
Action: Search for this error in the alert log and trace files for additional information.
Cause: A process subordinate to this Logminer process has exited with an error condition.
Action: Look in the alert log and trace files for additional information.
Cause: The database character set of the mining database was not a superset of the source database character set.
Action: Perform the mining operation on a database having a compatible database character set.
Cause: A select was issued from v$logmnr_contents without first invoking the dbms_logmnr.start_logmnr() procedure.
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.
Cause: The dictionary directory was not valid.
Action: Set the dictionary directory to an appropriate value.
Cause: The specified Logminer session ID or session handle is invalid.
Action: Use a valid Logminer session ID or session handle.
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: 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/view.
Action: Rewrite the SQL statement with a legal invocation of mine_value
Cause: The table/column specified in the lcr_mine call does not exist at the the specified SCN. The table/column definition has to exist at the start SCN specified for lcr_mine to be able to identify the table/column correctly.
Action: Create a LogMiner session at a start SCN at which the table definition is available.
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 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: 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 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 command or procedure was issued which requires an attached Logminer session.
Action: Attach to a Logminer session before issuing the command or procedure.
Cause: The national character set of the mining database was not a superset of the source database national character set.
Action: Perform the mining operation on a database having a compatible national character set.
Cause: A session attribute was supplied which is invalid.
Action: Re-issue with valid session attribute.
Cause: A Logminer dictionary attribute was supplied which is invalid.
Action: Re-issue with valid dictionary attribute.
Cause: The requested session start SCN is less than the SCN of any available Logminer Dictionary build. It is not possible to unwind a Logminer Dictionary to the requested start SCN.
Action: Re-issue the start_logminer request with a start SCN for which a Logminer Dictionary is available.
Cause: An non-existent table was supplied to Logminer include_src_tbl() or exclude_src_table().
Action: Re-issue with valid table name.
Cause: A Logminer routine was called from the wrong state.
Action: n/a
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: 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: 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: Other users are performing DDL operations.
Action: n/a
Cause: Another processes is simultaneously attempting to run build();
Action: Wait until the other processes completes.
Cause: The table may be missing, or locked by another user.
Action: n/a
- ORA-01330: problem loading a required build table
- ORA-01331: general error while running build
- ORA-01332: internal Logminer Dictionary error
Cause: Unexpected error condition
Action: Check trace and/or alert logs
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: Unexpected internal error condition
Action: n/a
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 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: Can not do this when other process is attached to LogMiner session.
Action: n/a
Cause: Unexpected result while accessing system catalog metadata.
Action: Check the alert log.
Cause: Could not load NLS package.
Action: n/a
Cause: The LogMiner session requires more system resources than is currently available.
Action: Allocate more SGA for LogMiner.
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: 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: A coordinator process is already attached to the specified logminer context.
Action: Detach from the active coordinator session and retry the attach.
Cause: A LogMiner client attempted to perform a privileged operation.
Action: Issue the operation from the coordinator process.
Cause: Oracle LogMiner detected a new branch with reset log SCN information prior to redo already mined.
Action: If running inside SQL Apply, retrieve standby reset SCN by executing DBMS_LOGSTDBY.MAP_PRIMARY_SCN (primary reset log SCN). And, execute FLASHBACK STANDBY DATABASE [<database_name>] TO BEFORE SCN standby reset SCN. Note: If the primary reset log SCN is 0, then intermediary log files are missing. Check the primary database for missing log files. In other scenarios, contact Oracle Support Services.
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-01348: LogMiner testing event
- ORA-01349: LogMiner tracing event
- 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: 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 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: 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 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: 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: Logminer sessions are currently active.
Action: End all logminer sessions and retry.
Cause: An attempt was made to mine a LogMiner dictionary from redo logs. The version of the Oracle database that created the logs was higher than the Oracle database version that attempted to mine the logs.
Action: Mine the logs using a newer version of the Oracle database having a version number that is equal to or greater than the dictionary version.
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 specified input value for the parameter was not a valid number.
Action: Specify a valid number and try again.
Cause: NULL was specified for input value of parameter.
Action: Specify a non-NULL value and try again.
Cause: LogMiner reader process has completed mining of physical standby terminal logs up to the stop SCN. LogMiner reader is now waiting for logs from the new branch.
Action: No action necessary. This informational statement is provided to record the event for diagnostic purposes. If there is a problem with log transport, the files can be registered manually using the ALTER DATABASE REGISTER LOGICAL LOGFILE statement.
Cause: LogMiner reader process has completed mining of physical standby terminal logs up to the stop SCN. The builder process is now waiting for logs from the new branch to be registered before continuing.
Action: No action necessary. This informational statement is provided to record the event for diagnostic purposes. If there is a problem with log transport, the files may be registered manually using the ALTER DATABASE REGISTER LOGICAL LOGFILE statement.
Cause: LogMiner failed to find all the expected log files required to complete the terminal apply, requested using the FINISH APPLY clause. During terminal apply, LogMiner does not wait for logs to be registered. It expects all logs between the starting point and the last log on any redo branch that it will or could mine through, to be present at the mining site.
Action: Examine system.logmnr_log$ to see which logs are known to LogMiner. Then, locate or restore any missing logs and use the ALTER DATABASE REGISTER LOGICAL LOGFILE statement to register them. Alternatively, do not use the FINISH APPLY clause, but if activating a logical standby, only do this when you are sure that the missing log files can not be located and registered as this can lead to data loss.
Cause: specified restart scn is too old, logmnr could not find a proper checkpoint.
Action: Specify a bigger restart SCN to try again
Cause: One or more log files containing the LogMiner dictionary was not found.
Action: Add into LogMiner all log files containing the dictionary.
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 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: LogMiner does not mine redo records generated with _log_parallelism_max set to a value greater than 1.
Action: n/a
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: The redo compatibility setting of the log file was unsupported by LogMiner.
Action: Specify a log file produced with a redo compatibility setting supported by LogMiner.
Cause: An invalid value was specified in the BLOCKSIZE clause.
Action: Use correct syntax.
- ORA-01378: The logical block size (string) of file string is not compatible with the disk sector size (media sector size is string and host sector size is string)
Cause: One of the following occurred: (1) An attempt was made to create a file. (2) A file was moved to disks with different sector size.
Action: Create file or move file to the proper disk.
- ORA-01379: LogMiner testing event
- ORA-01380: Instance string (thread string) has less than two string block size log files
Cause: One of the following occurred: (1) An attempt was made to switch to specified block size logs for all threads. (2) An attemp was made to open a thread.
Action: Add log files to the thread that signals error, and try again.
- ORA-01381: Dropping log string would leave less than two log files with block size string for instance string (thread string)
Cause: The database was migrated to use a specified log block size. Dropping all the logs specified would leave fewer than the required two log files with the specified block size per enabled thread.
Action: Either drop fewer logs or disable the thread before deleting the logs. It may be possible to clear the log rather than drop it.
- ORA-01382: Thread string failed to open log file string. The log file’s block size (string) is larger than the disk sector size (string)
Cause: Log file was created on bigger sector disks, and moved to smaller sector disks.
Action: Move the log file back to bigger sector disks.
- ORA-01383: Thread string failed to open string block size log file ‘string‘ on string sector native-mode disks
Cause: Log file was copied from smaller sector disks to larger sector native-mode disks.
Action: Move the log file back to smaller sector disks.
Cause: An attempt was made to automatically convert the control file created with maximum file name size value of 512 to 256. This could result in truncation of file names leading to loss of uniqueness among file names.
Action: One of the following can be done: 1) Change the _kccacb parameter value to ‘reject’ which will ignore the automatic conversion without returning this error. 2) Shorten the file names in the system where the control file was created to conform to the maximum file name length in the current system.
- ORA-01398: LogMiner public event
- ORA-01399: LogMiner public event
- ORA-01400: cannot insert NULL into (string)
Cause: An attempt was made to insert NULL into previously listed objects.
Action: These objects cannot accept NULL values.