{"id":1692,"date":"2016-02-19T11:05:53","date_gmt":"2016-02-19T08:05:53","guid":{"rendered":"http:\/\/www.fatihacar.com\/blog\/?p=1692"},"modified":"2016-10-19T11:09:26","modified_gmt":"2016-10-19T08:09:26","slug":"oracle-11g-error-codes-and-solution-suggestions-from-ora-01301-to-ora-01400","status":"publish","type":"post","link":"http:\/\/www.fatihacar.com\/blog\/oracle-11g-error-codes-and-solution-suggestions-from-ora-01301-to-ora-01400\/","title":{"rendered":"Oracle 11g Error Codes and Solution Suggestions from ORA-01301 to ORA-01400"},"content":{"rendered":"

Oracle 11g Error Codes and Solution Suggestions from ORA-01301 to ORA-01400<\/strong><\/p>\n

ORA-01301: error writing to file during flat file build<\/strong><\/p>\n

Cause:<\/strong> Error writing to file during flat file build<\/p>\n

Action:<\/strong> None<\/p>\n

ORA-01302: dictionary build options missing or incorrect<\/strong><\/p>\n

Cause:<\/strong> Missing dictionary build options or incorrectly specified options<\/p>\n

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

ORA-01303: subordinate process error: number. Check alert and trace logs<\/strong><\/p>\n

Cause:<\/strong> A process subordinate to this Logminer process has exited with this error status.<\/p>\n

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

ORA-01304: subordinate process error. Check alert and trace logs<\/strong><\/p>\n

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

Action:<\/strong> Look in the alert log and trace files for additional information.<\/p>\n

ORA-01306: dbms_logmnr.start_logmnr() must be invoked before selecting from v$logmnr_contents<\/strong><\/p>\n

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

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

ORA-01307: no LogMiner session is currently active<\/strong><\/p>\n

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

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

ORA-01308: initialization parameter utl_file_dir is not set<\/strong><\/p>\n

Cause:<\/strong> utl_file_dir is not set in the initialization file.<\/p>\n

Action:<\/strong> Set utl_file_dir to the appropriate directory.<\/p>\n

ORA-01309: invalid session<\/strong><\/p>\n

Cause:<\/strong> The specified Logminer session ID or session handle is invalid.<\/p>\n

Action:<\/strong> Use a valid Logminer session ID or session handle.
\n<\/p>\n

ORA-01310: requested return type not supported by the lcr_mine function<\/strong><\/p>\n

Cause:<\/strong> The return type requested by the user is not supported by lcr_mine”<\/p>\n

Action:<\/strong> Pick a return type supported by the lcr_mine function”<\/p>\n

ORA-01311: Illegal invocation of the mine_value function<\/strong><\/p>\n

Cause:<\/strong> 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.<\/p>\n

Action:<\/strong> Rewrite the SQL statement with a legal invocation of mine_value<\/p>\n

ORA-01312: Specified table\/column does not exist<\/strong><\/p>\n

Cause:<\/strong> 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.<\/p>\n

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

ORA-01313: LogMiner dictionary column type different from specified type<\/strong><\/p>\n

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

Action:<\/strong> Rewrite the lcr_mine invocation with the right return type.<\/p>\n

ORA-01314: Name of the column to be mined should be a string literal<\/strong><\/p>\n

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

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

ORA-01315: Log file has been added or removed during select<\/strong><\/p>\n

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

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

ORA-01316: Already attached to a Logminer session<\/strong><\/p>\n

Cause:<\/strong> A Logminer attach session was issued while already attached to a Logminer session.<\/p>\n

Action:<\/strong> Detach from the current Logminer session and attach to the requested session.<\/p>\n

ORA-01317: Not attached to a Logminer session<\/strong><\/p>\n

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

Action:<\/strong> Attach to a Logminer session before issuing the command or procedure.<\/p>\n

ORA-01319: Invalid Logminer session attribute<\/strong><\/p>\n

Cause:<\/strong> A session attribute was supplied which is invalid.<\/p>\n

Action:<\/strong> Re-issue with valid session attribute.<\/p>\n

ORA-01320: Invalid Logminer dictionar attribute<\/strong><\/p>\n

Cause:<\/strong> A Logminer dictionary attribute was supplied which is invalid.<\/p>\n

Action:<\/strong> Re-issue with valid dictionary attribute.<\/p>\n

ORA-01321: No Logminer Dictionary for requested start SCN<\/strong><\/p>\n

Cause:<\/strong> 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.<\/p>\n

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

ORA-01322: No such table<\/strong><\/p>\n

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

Action:<\/strong> Re-issue with valid table name.<\/p>\n

ORA-01323: Invalid state<\/strong><\/p>\n

Cause:<\/strong> A Logminer routine was called from the wrong state.<\/p>\n

Action:<\/strong> None<\/p>\n

ORA-01324: cannot add file string due to DB_ID mismatch<\/strong><\/p>\n

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

Action:<\/strong> Specify a logfile produced by the same database.<\/p>\n

ORA-01325: archive log mode must be enabled to build into the logstream<\/strong><\/p>\n

Cause:<\/strong> Database does not have archivelog mode enabled.<\/p>\n

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

ORA-01326: compatability of 9.0 or greater required to build into the logstream<\/strong><\/p>\n

Cause:<\/strong> Compatibility mode set to some value less than 9.0<\/p>\n

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

ORA-01327: failed to exclusively lock system dictionary as required by build<\/strong><\/p>\n

Cause:<\/strong> Other users are performing DDL operations.<\/p>\n

Action:<\/strong> None<\/p>\n

ORA-01328: only one build operation may occur at one time<\/strong><\/p>\n

Cause:<\/strong> Another processes is simultaneously attempting to run build();<\/p>\n

Action:<\/strong> Wait until the other processes completes.<\/p>\n

ORA-01329: unable to truncate required build table<\/strong><\/p>\n

Cause:<\/strong> The table may be missing, or locked by another user.<\/p>\n

Action:<\/strong> None<\/p>\n

ORA-01332: internal Logminer Dictionary error<\/strong><\/p>\n

Cause:<\/strong> Unexpected error condition<\/p>\n

Action:<\/strong> Check trace and\/or alert logs<\/p>\n

ORA-01333: failed to establish Logminer Dictionary<\/strong><\/p>\n

Cause:<\/strong> 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.<\/p>\n

Action:<\/strong> 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.<\/p>\n

ORA-01334: invalid or missing logminer dictionary processes context<\/strong><\/p>\n

Cause:<\/strong> Unexpected internal error condition<\/p>\n

Action:<\/strong> None<\/p>\n

ORA-01336: specified dictionary file cannot be opened<\/strong><\/p>\n

Cause:<\/strong> The dictionary file or directory does not exist or is inaccessible.<\/p>\n

Action:<\/strong> Make sure that the dictionary file and directory exist and are accessible.<\/p>\n

ORA-01337: log file has a different compatibility version<\/strong><\/p>\n

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

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

ORA-01338: Other process is attached to LogMiner session<\/strong><\/p>\n

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

Action:<\/strong> None<\/p>\n

ORA-01339: LogMiner BUILD: Error copying system catalog metadata to LogMiner dictionary<\/strong><\/p>\n

Cause:<\/strong> Unexpected result while accessing system catalog metadata.<\/p>\n

Action:<\/strong> Check the alert log.<\/p>\n

ORA-01340: NLS error<\/strong><\/p>\n

Cause:<\/strong> Could not load NLS package.<\/p>\n

Action:<\/strong> None<\/p>\n

ORA-01341: LogMiner out-of-memory<\/strong><\/p>\n

Cause:<\/strong> The LogMiner session requires more system resources than is currently available.<\/p>\n

Action:<\/strong> Allocate more SGA for LogMiner.<\/p>\n

ORA-01342: LogMiner can not resume session due to inability of staging checkpointed data<\/strong><\/p>\n

Cause:<\/strong> 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.<\/p>\n

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

ORA-01343: LogMiner encountered corruption in the logstream<\/strong><\/p>\n

Cause:<\/strong> Log file is missing a range of scn values.<\/p>\n

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

ORA-01344: LogMiner coordinator already attached<\/strong><\/p>\n

Cause:<\/strong> A coordinator process is already attached to the specified logminer context.<\/p>\n

Action:<\/strong> Detach from the active coordinator session and retry the attach.<\/p>\n

ORA-01345: Must be a LogMiner coordinator process<\/strong><\/p>\n

Cause:<\/strong> A LogMiner client attempted to perform a privileged operation.<\/p>\n

Action:<\/strong> Issue the operation from the coordinator process.<\/p>\n

ORA-01346: LogMiner processed redo beyond specified reset log scn<\/strong><\/p>\n

Cause:<\/strong> LogMiner has detected a new branch with resetlogs scn information prior to redo already mined.<\/p>\n

Action:<\/strong> Contact your customer support representative.<\/p>\n

ORA-01347: Supplemental log data no longer found<\/strong><\/p>\n

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

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

ORA-01350: must specify a tablespace name<\/strong><\/p>\n

Cause:<\/strong> Invocation failed to specify a valid tablespace<\/p>\n

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

ORA-01351: tablespace given for Logminer dictionary does not exist<\/strong><\/p>\n

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

Action:<\/strong> 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.<\/p>\n

ORA-01352: tablespace given for Logminer spill does not exist<\/strong><\/p>\n

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

Action:<\/strong> 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.<\/p>\n

ORA-01353: existing Logminer session<\/strong><\/p>\n

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

Action:<\/strong> 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.<\/p>\n

ORA-01354: Supplemental log data must be added to run this command<\/strong><\/p>\n

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

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

ORA-01355: logminer tablespace change in progress<\/strong><\/p>\n

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

Action:<\/strong> Wait until the move is complete and try again.<\/p>\n

ORA-01356: active logminer sessions found<\/strong><\/p>\n

Cause:<\/strong> Logminer sessions are currently active.<\/p>\n

Action:<\/strong> End all logminer sessions and retry.<\/p>\n

ORA-01358: LogMiner version is less than mined dictionary version<\/strong><\/p>\n

Cause:<\/strong> 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.<\/p>\n

Action:<\/strong> 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.<\/p>\n

ORA-01361: global name mismatch<\/strong><\/p>\n

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

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

ORA-01370: Specified restart SCN is too old<\/strong><\/p>\n

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

Action:<\/strong> Specify a bigger restart SCN to try again<\/p>\n

ORA-01371: Complete LogMiner dictionary not found<\/strong><\/p>\n

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

Action:<\/strong> Add into LogMiner all log files containing the dictionary.<\/p>\n

ORA-01372: Insufficient processes for specified LogMiner operation<\/strong><\/p>\n

Cause:<\/strong> The number of processes requested by the caller can not be allocated<\/p>\n

Action:<\/strong> Increase number of parallel servers allocated to the instance<\/p>\n

ORA-01373: insufficient memory for staging persistent LogMiner session<\/strong><\/p>\n

Cause:<\/strong> 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.<\/p>\n

Action:<\/strong> Increase LOGMNR_MAX_PERSISTENT_SESSIONS and restart instance.<\/p>\n

ORA-01374: _log_parallelism_max greater than 1 not supported in this release<\/strong><\/p>\n

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

Action:<\/strong> None<\/p>\n

ORA-01375: Corrupt logfile string recovered<\/strong><\/p>\n

Cause:<\/strong> A corrupt logfile has been recovered by RFS<\/p>\n

Action:<\/strong> None. Logical Standby should automatically restart. If logfile is still corrupt, may need to manually copy and reregister the logfile on the standby.<\/p>\n","protected":false},"excerpt":{"rendered":"

Oracle 11g Error Codes and Solution Suggestions from ORA-01301 to ORA-01400 ORA-01301: error writing to file during flat file build Cause: Error writing to file during flat file build Action: None ORA-01302: dictionary build options missing or incorrect Cause: Missing dictionary build options or incorrectly specified options Action: Specify either a build to redo log…<\/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":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[53],"tags":[14,32,54],"class_list":["post-1692","post","type-post","status-publish","format-standard","hentry","category-oracle-errors-and-solutions","tag-database-administration","tag-oracle-administration","tag-oracle-error-solutions"],"jetpack_featured_media_url":"","jetpack_shortlink":"https:\/\/wp.me\/p39NFI-ri","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/posts\/1692","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=1692"}],"version-history":[{"count":1,"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/posts\/1692\/revisions"}],"predecessor-version":[{"id":1693,"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/posts\/1692\/revisions\/1693"}],"wp:attachment":[{"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/media?parent=1692"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/categories?post=1692"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/tags?post=1692"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}