{"id":2058,"date":"2016-08-09T13:36:07","date_gmt":"2016-08-09T10:36:07","guid":{"rendered":"http:\/\/www.fatihacar.com\/blog\/?p=2058"},"modified":"2016-12-12T09:22:33","modified_gmt":"2016-12-12T06:22:33","slug":"oracle-12c-r2-error-codes-and-solution-suggestions-from-ora-01300-to-ora-01400","status":"publish","type":"post","link":"http:\/\/www.fatihacar.com\/blog\/oracle-12c-r2-error-codes-and-solution-suggestions-from-ora-01300-to-ora-01400\/","title":{"rendered":"Oracle 12c R2 Error Codes and Solution Suggestions from ORA-01300 to ORA-01400"},"content":{"rendered":"

Oracle 12c R2 Error Codes and Solution Suggestions from ORA-01300 to ORA-01400<\/strong><\/p>\n

\n
ORA-01300: writable database required for specified LogMiner options<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Options were specified which required the database to be writable.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Specify different options or open the database for write access.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01301: error writing to file during flat file build<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Error writing to file during flat file build<\/span><\/span><\/p>\n

Action:<\/b>\u00a0n\/a<\/span><\/span><\/p>\n

\n
<\/a> ORA-01302: dictionary build options missing or incorrect<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Missing dictionary build options or incorrectly specified options<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Specify either a build to redo log or to flat file. If build to flat file, specify filename and directory.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01303: subordinate process error:\u00a0string<\/i>. Check alert and trace logs<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0A process subordinate to this Logminer process has exited with this error status.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Search for this error in the alert log and trace files for additional information.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01304: subordinate process error. Check alert and trace logs<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0A process subordinate to this Logminer process has exited with an error condition.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Look in the alert log and trace files for additional information.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01305: incompatible database character set<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The database character set of the mining database was not a superset of the source database character set.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Perform the mining operation on a database having a compatible database character set.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01306: dbms_logmnr.start_logmnr() must be invoked before selecting from v$logmnr_contents<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0A select was issued from v$logmnr_contents without first invoking the dbms_logmnr.start_logmnr() procedure.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Invoke the dbms_logmnr.start_logmnr() procedure before issuing a select from the v$logmnr_contents view.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01307: no LogMiner session is currently active<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0A 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()<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Invoke the dbms_logmnr.start_logmnr() procedure before issuing a select from the v$logmnr_contents view.<\/span><\/span>
\n<\/p>\n

\n
<\/a> ORA-01308: dictionary directory is not set<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The dictionary directory was not valid.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Set the dictionary directory to an appropriate value.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01309: invalid session<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The specified Logminer session ID or session handle is invalid.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Use a valid Logminer session ID or session handle.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01310: requested return type not supported by the lcr_mine function<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The return type requested by the user is not supported by lcr_mine”<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Pick a return type supported by the lcr_mine function”<\/span><\/span><\/p>\n

\n
<\/a> ORA-01311: Illegal invocation of the mine_value function<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An 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.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Rewrite the SQL statement with a legal invocation of mine_value<\/span><\/span><\/p>\n

\n
<\/a> ORA-01312: Specified table\/column does not exist<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The 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.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Create a LogMiner session at a start SCN at which the table definition is available.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01313: LogMiner dictionary column type different from specified type<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The return type specified for the column in lcr_mine call is different from the actual type of the column.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Rewrite the lcr_mine invocation with the right return type.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01314: Name of the column to be mined should be a string literal<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The fully qualified name of the column to be mined by the LogMiner functions should be string literal.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0If 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’.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01315: Log file has been added or removed during select<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0A redo log file has been added or removed while selecting on the v$logmnr_logs fixed view.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Re-issue the SQL select statement on the v$logmnr_logs view.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01316: Already attached to a Logminer session<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0A Logminer attach session was issued while already attached to a Logminer session.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Detach from the current Logminer session and attach to the requested session.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01317: Not attached to a Logminer session<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0A command or procedure was issued which requires an attached Logminer session.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Attach to a Logminer session before issuing the command or procedure.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01318: incompatible national character set<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The national character set of the mining database was not a superset of the source database national character set.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Perform the mining operation on a database having a compatible national character set.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01319: Invalid Logminer session attribute<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0A session attribute was supplied which is invalid.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Re-issue with valid session attribute.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01320: Invalid Logminer dictionar attribute<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0A Logminer dictionary attribute was supplied which is invalid.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Re-issue with valid dictionary attribute.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01321: No Logminer Dictionary for requested start SCN<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The 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.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Re-issue the start_logminer request with a start SCN for which a Logminer Dictionary is available.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01322: No such table<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An non-existent table was supplied to Logminer include_src_tbl() or exclude_src_table().<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Re-issue with valid table name.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01323: Invalid state<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0A Logminer routine was called from the wrong state.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0n\/a<\/span><\/span><\/p>\n

\n
<\/a> ORA-01324: cannot add file\u00a0string<\/i>\u00a0due to DB_ID mismatch<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The logfile is produced by a different database than other logfiles already added to the list.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Specify a logfile produced by the same database.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01325: archive log mode must be enabled to build into the logstream<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Database does not have archivelog mode enabled.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Mount the database, then issue commands to enable archivelog mode. startup pfile=init.ora mount alter database archivelog alter database open<\/span><\/span><\/p>\n

\n
<\/a> ORA-01326: compatability of 9.0 or greater required to build into the logstream<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Compatibility mode set to some value less than 9.0<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Ensure that init.ora parameter establishing a compatability of 9.0 or greater is set. For example: compatible=9.0.0.0.0<\/span><\/span><\/p>\n

\n
<\/a> ORA-01327: failed to exclusively lock system dictionary as required by build<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Other users are performing DDL operations.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0n\/a<\/span><\/span><\/p>\n

\n
<\/a> ORA-01328: only one build operation may occur at one time<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Another processes is simultaneously attempting to run build();<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Wait until the other processes completes.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01329: unable to truncate required build table<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The table may be missing, or locked by another user.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0n\/a<\/span><\/span><\/p>\n

\n
<\/a> ORA-01330: problem loading a required build table<\/b><\/span><\/span><\/span><\/dt>\n
<\/a> ORA-01331: general error while running build<\/b><\/span><\/span><\/span><\/dt>\n
<\/a> ORA-01332: internal Logminer Dictionary error<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Unexpected error condition<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Check trace and\/or alert logs<\/span><\/span><\/p>\n

\n
<\/a> ORA-01333: failed to establish Logminer Dictionary<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0No 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.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0If 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.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01334: invalid or missing logminer dictionary processes context<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Unexpected internal error condition<\/span><\/span><\/p>\n

Action:<\/b>\u00a0n\/a<\/span><\/span><\/p>\n

\n
<\/a> ORA-01335: feature not yet implemented<\/b><\/span><\/span><\/span><\/dt>\n
<\/a> ORA-01336: specified dictionary file cannot be opened<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The dictionary file or directory does not exist or is inaccessible.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Make sure that the dictionary file and directory exist and are accessible.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01337: log file has a different compatibility version<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The logfile has a different compatibility version then the rest of the logfile in the session”<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Make sure that the logfile has the same compatibility version as the rest of the logfiles in the session.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01338: Other process is attached to LogMiner session<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Can not do this when other process is attached to LogMiner session.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0n\/a<\/span><\/span><\/p>\n

\n
<\/a> ORA-01339: LogMiner BUILD: Error copying system catalog metadata to LogMiner dictionary<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Unexpected result while accessing system catalog metadata.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Check the alert log.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01340: NLS error<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Could not load NLS package.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0n\/a<\/span><\/span><\/p>\n

\n
<\/a> ORA-01341: LogMiner out-of-memory<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The LogMiner session requires more system resources than is currently available.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Allocate more SGA for LogMiner.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01342: LogMiner can not resume session due to inability of staging checkpointed data<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Logmnr 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.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Specify a bigger max_sga for the given LogMiner session and try again.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01343: LogMiner encountered corruption in the logstream<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Log file is missing a range of scn values.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Verify the contiguity of the scn range reprented by the log files added to LogMiner.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01344: LogMiner coordinator already attached<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0A coordinator process is already attached to the specified logminer context.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Detach from the active coordinator session and retry the attach.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01345: Must be a LogMiner coordinator process<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0A LogMiner client attempted to perform a privileged operation.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Issue the operation from the coordinator process.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01346: Oracle LogMiner processed redo beyond primary reset log SCN\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Oracle LogMiner detected a new branch with reset log SCN information prior to redo already mined.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0If 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\u00a0standby reset SCN<\/i>. 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.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01347: Supplemental log data no longer found<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The source database instance producing log files for this LogMiner session was altered to no longer log supplemental data.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Destroy this Logminer session. Re-enable supplemental log data on the source system and create a new LogMiner session.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01348: LogMiner testing event<\/b><\/span><\/span><\/span><\/dt>\n
<\/a> ORA-01349: LogMiner tracing event<\/b><\/span><\/span><\/span><\/dt>\n
<\/a> ORA-01350: must specify a tablespace name<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Invocation failed to specify a valid tablespace<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Reformat invocation of DBMS_LOGMNR_D.SET_TABLESPACE to include the name of a valid tablespace.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01351: tablespace given for Logminer dictionary does not exist<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The tablespace name given as a parameter to DBMS_LOGMNR_D.SET_TABLESPACE does not exist.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Check 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.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01352: tablespace given for Logminer spill does not exist<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The tablespace name given as the parameter to DBMS_LOGMNR_D.SET_TABLESPACE does not exist.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Check 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.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01353: existing Logminer session<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An attempt was made to execute DBMS_LOGMNR_D.SET_TABLESPACE while a Logminer session(s) was active.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0First 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.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01354: Supplemental log data must be added to run this command<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An attempt was made to perform an operation that required that supplemental log data be enabled.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Execute a command such as ALTER DATABASE ADD SUPPLEMENTAL LOG DATA; and then reissue the command that failed with this error.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01355: logminer tablespace change in progress<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The tables used by logminer are in the process of being moved to another tablespace.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Wait until the move is complete and try again.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01356: active logminer sessions found<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Logminer sessions are currently active.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0End all logminer sessions and retry.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01358: LogMiner version is less than mined dictionary version<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An 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.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Mine the logs using a newer version of the Oracle database having a version number that is equal to or greater than the dictionary version.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01360: invalid token<\/b><\/span><\/span><\/span><\/dt>\n
<\/a> ORA-01361: global name mismatch<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The database global name where the log file was generated did not match the user-specified global name of the Streams Capture process.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Start a new capture process and ensure that the user-specified global name matches that of the database that generated the log file.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01362: Specified SQL_REDO_UNDO parameter is invalid<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The specified input value for the parameter was not a valid number.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Specify a valid number and try again.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01363: Specified COLUMN_NAME parameter is NULL<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0NULL was specified for input value of parameter.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Specify a non-NULL value and try again.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01364: waiting for branch at SCN\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0LogMiner 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.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0No 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.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01365: waiting for new branch registration<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0LogMiner 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.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0No 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.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01366: failed to find redo logs required for terminal apply<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0LogMiner 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.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Examine 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.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01370: Specified restart SCN is too old<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0specified restart scn is too old, logmnr could not find a proper checkpoint.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Specify a bigger restart SCN to try again<\/span><\/span><\/p>\n

\n
<\/a> ORA-01371: Complete LogMiner dictionary not found<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0One or more log files containing the LogMiner dictionary was not found.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Add into LogMiner all log files containing the dictionary.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01372: Insufficient processes for specified LogMiner operation<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The number of processes requested by the caller can not be allocated<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Increase number of parallel servers allocated to the instance<\/span><\/span><\/p>\n

\n
<\/a> ORA-01373: insufficient memory for staging persistent LogMiner session<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The 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.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Increase LOGMNR_MAX_PERSISTENT_SESSIONS and restart instance.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01374: _log_parallelism_max greater than 1 not supported in this release<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0LogMiner does not mine redo records generated with _log_parallelism_max set to a value greater than 1.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0n\/a<\/span><\/span><\/p>\n

\n
<\/a> ORA-01375: Corrupt logfile\u00a0string<\/i>\u00a0recovered<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0A corrupt logfile has been recovered by RFS<\/span><\/span><\/p>\n

Action:<\/b>\u00a0None. Logical Standby should automatically restart. If logfile is still corrupt, may need to manually copy and reregister the logfile on the standby.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01376: cannot add file\u00a0string<\/i>\u00a0due to unsupported redo compatibility setting<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The redo compatibility setting of the log file was unsupported by LogMiner.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Specify a log file produced with a redo compatibility setting supported by LogMiner.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01377: Invalid log file block size<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An invalid value was specified in the BLOCKSIZE clause.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Use correct syntax.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01378: The logical block size (string<\/i>) of file\u00a0string<\/i>\u00a0is not compatible with the disk sector size (media sector size is\u00a0string<\/i>\u00a0and host sector size is\u00a0string<\/i>)<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0One of the following occurred: (1) An attempt was made to create a file. (2) A file was moved to disks with different sector size.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Create file or move file to the proper disk.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01379: LogMiner testing event<\/b><\/span><\/span><\/span><\/dt>\n
<\/a> ORA-01380: Instance\u00a0string<\/i>\u00a0(thread\u00a0string<\/i>) has less than two\u00a0string<\/i>\u00a0block size log files<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0One 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.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Add log files to the thread that signals error, and try again.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01381: Dropping log\u00a0string<\/i>\u00a0would leave less than two log files with block size\u00a0string<\/i>\u00a0for instance\u00a0string<\/i>\u00a0(thread\u00a0string<\/i>)<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The 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.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Either drop fewer logs or disable the thread before deleting the logs. It may be possible to clear the log rather than drop it.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01382: Thread\u00a0string<\/i>\u00a0failed to open log file\u00a0string<\/i>. The log file’s block size (string<\/i>) is larger than the disk sector size (string<\/i>)<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Log file was created on bigger sector disks, and moved to smaller sector disks.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Move the log file back to bigger sector disks.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01383: Thread\u00a0string<\/i>\u00a0failed to open\u00a0string<\/i>\u00a0block size log file ‘string<\/i>‘ on\u00a0string<\/i>\u00a0sector native-mode disks<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Log file was copied from smaller sector disks to larger sector native-mode disks.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Move the log file back to smaller sector disks.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01397: file name too long to shrink without truncation<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An 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.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0One 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.<\/span><\/span><\/p>\n

\n
<\/a> ORA-01398: LogMiner public event<\/b><\/span><\/span><\/span><\/dt>\n
<\/a> ORA-01399: LogMiner public event<\/b><\/span><\/span><\/span><\/dt>\n
<\/a> ORA-01400: cannot insert NULL into (string<\/i>)<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An attempt was made to insert NULL into previously listed objects.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0These objects cannot accept NULL values.<\/span><\/span><\/p>\n

\n
<\/dd>\n<\/dl>\n","protected":false},"excerpt":{"rendered":"

Oracle 12c R2 Error Codes and Solution Suggestions from ORA-01300 to ORA-01400 ORA-01300: writable database required for specified LogMiner options Cause:\u00a0Options were specified which required the database to be writable. Action:\u00a0Specify different options or open the database for write access. ORA-01301: error writing to file during flat file build Cause:\u00a0Error writing to file during flat…<\/p>\n","protected":false},"author":37,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":true,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[53],"tags":[54],"class_list":["post-2058","post","type-post","status-publish","format-standard","hentry","category-oracle-errors-and-solutions","tag-oracle-error-solutions"],"jetpack_featured_media_url":"","jetpack_shortlink":"https:\/\/wp.me\/p39NFI-xc","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/posts\/2058","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/users\/37"}],"replies":[{"embeddable":true,"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/comments?post=2058"}],"version-history":[{"count":2,"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/posts\/2058\/revisions"}],"predecessor-version":[{"id":2106,"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/posts\/2058\/revisions\/2106"}],"wp:attachment":[{"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/media?parent=2058"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/categories?post=2058"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/tags?post=2058"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}