Oracle错误代码整理

Error Code Oracle11g Oracle10g Oracle9iORA-00000ORA-00000: normal, successful completion Cause: Normal exit.Action: None ORA-00000: normal, successful completionCause: Normal exit.Action: None.ORA-00000 normal, successful completionCause: An operation has completed normally, havingmet no exceptions.Action: No action required.ORA-00001ORA-00001: unique constraint (string.string) violated Cause: An UPDATE or INSERT statement attempted toinsert a duplicate key. ForTrusted Oracle configured in DBMS MAC mode, youmay see this message if aduplicate entry exists at a different level.Action: Either remove the unique restriction or do notinsert the key.ORA-00001: unique constraint (string.string) violatedCause: An UPDATE or INSERT statement attempted toinsert a duplicate key. ForTrusted Oracle configured in DBMS MAC mode, youmay see this message if aduplicate entry exists at a different level.Action: Either remove the unique restriction or do notinsert the key.ORA-00001 unique constraint (string.string) violatedCause: An UPDATE or INSERT statement attemptedto insert a duplicate key.Action: Either remove the unique restriction or donot insert the key.ORA-00017ORA-00017: session requested to set trace eventCause: The current session was requested to set a traceevent by another session.Action: This is used internally; no action is required.ORA-00017: session requested to set trace eventCause: The current session was requested to set a traceevent by another session.Action: This is used internally; no action is required.ORA-00017 session requested to set trace eventCause: The current session was requested to set atrace event by anothersession.Action: This is used internally; no action is required.ORA-00018ORA-00018: maximum number of sessions exceeded Cause: All session state objects are in use.Action: Increase the value of the SESSIONS initializationparameter.ORA-00018: maximum number of sessions exceededCause: All session state objects are in use.Action: Increase the value of the SESSIONSinitialization parameter.ORA-00018 maximum number of sessions exceededCause: All session state objects are in use.Action: Increase the value of the SESSIONSinitialization parameter.ORA-00019ORA-00019: maximum number of session licenses exceededCause: All licenses are in use.Action: Increase the value of the LICENSE MAXSESSIONS initializationparameter.ORA-00019: maximum number of session licensesexceededCause: All licenses are in use.Action: Increase the value of the LICENSE MAXSESSIONS initializationparameter.ORA-00019 maximum number of session licensesexceededCause: All licenses are in use.Action: Increase the value of the LICENSE MAXSESSIONS initializationparameter.ORA-00020ORA-00020: maximum number of processes (string) exceededCause: All process state objects are in use.Action: Increase the value of the PROCESSESinitialization parameter.ORA-00020: maximum number of processes (string)exceededCause: All process state objects are in use.Action: Increase the value of the PROCESSESinitialization parameter.ORA-00020 maximum number of processes (string)exceededCause: All process state objects are in use.Action: Increase the value of the PROCESSESinitialization parameter.Error Code Oracle11g Oracle10g Oracle9iORA-00021ORA-00021: session attached to some other process;cannot switch sessionCause: The user session is currently used by others.Action: Do not switch to a session attached to someother process.ORA-00021: session attached to some other process;cannot switch sessionCause: The user session is currently used by others.Action: Do not switch to a session attached to someother process.ORA-00021 session attached to some other process;cannot switch sessionCause: The user session is currently used by others.Action: Do not switch to a session attached to someother process.ORA-00022ORA-00022: invalid session ID; access deniedCause: Either the session specified does not exist or thecaller does not have theprivilege to access it.Action: Specify a valid session ID that you have privilegeto access, that is eitheryou own it or you have the CHANGE_USER privilege.ORA-00022: invalid session ID; access deniedCause: Either the session specified does not exist orthe caller does not have theprivilege to access it.Action: Specify a valid session ID that you haveprivilege to access, that is eitheryou own it or you have the CHANGE_USER privilege.ORA-00022 invalid session ID; access deniedCause: Either the session specified does not exist orthe caller does not have theprivilege to access it.Action: Specify a valid session ID that you haveprivilege to access, that iseither you own it or you have the CHANGE_USERprivilege.ORA-00023ORA-00023: session references process private memory;cannot detach sessionCause: An attempt was made to detach the currentsession when it containsreferences to process private memory.Action: A session may contain references to processmemory (PGA) if it has anopen network connection, a very large context area, oroperating systemprivileges. To allow the detach, it may be necessary toclose the session's databaselinks and/or cursors. Detaching a session with operatingsystem privileges isalways disallowed.ORA-00023: session references process privatememory; cannot detach sessionCause: An attempt was made to detach the currentsession when it containsreferences to process private memory.Action: A session may contain references to processmemory (PGA) if it has anopen network connection, a very large context area, oroperating systemprivileges. To allow the detach, it may be necessary toclose the session"s databaselinks and/or cursors. Detaching a session withoperating system privileges isalways disallowed.ORA-00023 session references process privatememory; cannot detach sessionCause: An attempt was made to detach the currentsession when it containsreferences to process private memory.Action: A session may contain references to processmemory (PGA) if it has anopen network connection, a very large context area,or operating systemprivileges. To allow the detach, it may be necessaryto close the session'sdatabase links and/or cursors. Detaching a sessionwith operating systemprivileges is always disallowed.Error Code Oracle11g Oracle10g Oracle9iORA-00024ORA-00024: logins from more than one process not allowed in single-process modeCause: Trying to login more than once from differentprocesses for ORACLEstarted in single-process mode.Action: Logoff from the other process.ORA-00024: logins from more than one process notallowed in single-process modeCause: Trying to login more than once from differentprocesses for ORACLEstarted in single-process mode.Action: Logoff from the other process.ORA-00024 logins from more than one process notallowed in single-processmodeCause: An attempt was made to log in more thanonce from different processesfor Oracle started in single-process mode.Action: Log off from the other process.ORA-00025ORA-00025: failed to allocate stringCause: Out of memory.Action: Restart with larger sga heap.ORA-00025: failed to allocate stringCause: Out of memory.Action: Restart with larger sga heap.ORA-00025 failed to allocate stringCause: An application failed because Oracle ran outof memory.Action: Restart Oracle with a larger SGA heap.ORA-00026ORA-00026: missing or invalid session IDCause: Missing or invalid session ID string for ALTERSYSTEM KILL SESSION.Action: Retry with a valid session ID.ORA-00026: missing or invalid session IDCause: Missing or invalid session ID string for ALTERSYSTEM KILL SESSION.Action: Retry with a valid session ID.ORA-00026 missing or invalid session IDCause: The session ID string specified in the ALTERSYSTEM KILL SESSIONcommand was invalid, or no string was specified.Action: Retry the command with a valid session ID.ORA-00027ORA-00027: cannot kill current sessionCause: Attempted to use ALTER SYSTEM KILL SESSIONto kill the currentsession.Action: None ORA-00027: cannot kill current sessionCause: Attempted to use ALTER SYSTEM KILL SESSIONto kill the currentsession.Action: None.ORA-00027 cannot kill current sessionCause: An attempt was made to use ALTER SYSTEMKILL SESSION to kill thecurrent session.Action: If it is necessary to kill the current session, doso from another session.ORA-00028ORA-00028: your session has been killedCause: A privileged user has killed your session and youare no longer logged onto the database.Action: Login again if you wish to continue working.ORA-00028: your session has been killedCause: A privileged user has killed your session andyou are no longer logged onto the database.Action: Login again if you wish to continue working.ORA-00028 your session has been killedCause: A privileged user killed the session and it is nolonger logged in to thedatabase.Action: Contact the database administrator. Theadministrator may beattempting to perform an operation that requiresusers to be logged out. Whenthe database administrator announces that thedatabase is available, log in andresume work.Error Code Oracle11g Oracle10g Oracle9iORA-00029ORA-00029: session is not a user sessionCause: The session ID specified in an ALTER SYSTEM KILLSESSION commandwas not a user session (for example, recursive, etc.).Action: Retry with a user session ID.ORA-00029: session is not a user sessionCause: The session ID specified in an ALTER SYSTEMKILL SESSION commandwas not a user session (for example, recursive, etc.).Action: Retry with a user session ID.ORA-00029 session is not a user sessionCause: The session ID specified in an ALTER SYSTEMKILL SESSIONcommand was not a user session. For example, thesession may be recursivelystarted.Action: Retry the command with a valid session ID.ORA-00030ORA-00030: User session ID does not exist.Cause: The user session ID no longer exists, probablybecause the session waslogged out.Action: Use a valid session ID.ORA-00030: User session ID does not exist.Cause: The user session ID no longer exists, probablybecause the session waslogged out.Action: Use a valid session ID.ORA-00030 User session ID does not exist.Cause: The user session ID no longer exists, probablybecause the session waslogged out.Action: Use a valid session ID.ORA-00031ORA-00031: session marked for killCause: The session specified in an ALTER SYSTEM KILLSESSION commandcannot be killed immediately (because it is rolling backor blocked on a networkoperation), but it has been marked for kill. This means itwill be killed as soon aspossible after its current uninterruptable operation isdone.Action: No action is required for the session to be killed,but further executions ofthe ALTER SYSTEM KILL SESSION command on thissession may cause thesession to be killed sooner.ORA-00031: session marked for killCause: The session specified in an ALTER SYSTEM KILLSESSION commandcannot be killed immediately (because it is rolling backor blocked on a networkoperation), but it has been marked for kill. This meansit will be killed as soon aspossible after its current uninterruptable operation isdone.Action: No action is required for the session to bekilled, but further executions ofthe ALTER SYSTEM KILL SESSION command on thissession may cause thesession to be killed sooner.ORA-00031 session marked for killCause: The session specified in an ALTER SYSTEMKILL SESSION commandcannot be killed immediately because the session isinvolved in anon-interruptible operation (for example, rollingback a transaction or beingblocked by a network operation). The session hasbeen marked to be killed assoon as possible after the current operation is done.Action: No action is required for the session to bekilled, but further executionsof the ALTER SYSTEM KILL SESSION command onthis session may cause thesession to be killed sooner.ORA-00032ORA-00032: invalid session migration passwordCause: The session migration password specified in asession creation call wasinvalid (probably too long).Action: Retry with a valid password (less than 30 chars).ORA-00032: invalid session migration passwordCause: The session migration password specified in asession creation call wasinvalid (probably too long).Action: Retry with a valid password (less than 30 chars).ORA-00032 invalid session migration passwordCause: The session migration password specified in asession creation call wasinvalid (probably too long).Action: Retry with a valid password (less than 30characters).Error Code Oracle11g Oracle10g Oracle9iORA-00033ORA-00033: current session has empty migrationpasswordCause: An attempt was made to detach or clone thecurrent session and it has anempty migration password. This is not allowed.Action: Create the session with a non-empty migrationpassword.ORA-00033: current session has empty migrationpasswordCause: An attempt was made to detach or clone thecurrent session and it has anempty migration password. This is not allowed.Action: Create the session with a non-empty migrationpassword.ORA-00033 current session has empty migrationpasswordCause: An attempt was made to detach or clone thecurrent session and it hasan empty migration password. This is not allowed.Action: Create the session with a non-emptymigration password.ORA-00034ORA-00034: cannot string in current PL/SQL session Cause: An attempt was made to issue a commit orrollback from a PL/SQL object(procedure, function, package) in a session that has thisdisabled (by 'alter sessiondisable commit in procedure')Action: Enable commits from PL/SQL in this session, ordo not attempt to usecommit or rollback in PL/SQL when they are disabled inthe current session.ORA-00034: cannot string in current PL/SQL sessionCause: An attempt was made to issue a commit orrollback from a PL/SQL object(procedure, function, package) in a session that hasthis disabled (by "alter sessiondisable commit in procedure")Action: Enable commits from PL/SQL in this session, ordo not attempt to usecommit or rollback in PL/SQL when they are disabledin the current session.ORA-00034 cannot string in current PL/SQL sessionCause: An attempt was made to issue a commit orrollback from a PL/SQLobject (procedure, function, package) in a sessionthat has this disabled by aALTER SESSION DISABLE COMMIT IN PROCEDUREstatement.Action: Enable commits from PL/SQL in this session,or do not attempt to usecommit or rollback in PL/SQL when they are disabledin the current session.ORA-00035ORA-00035 LICENSE_MAX_USERS cannot be lessthan current number of usersCause: Specified values for LICENSE_MAX_USERS isless than the currentnumber of users.Action: Check the license limit and drop extra usersor purchase more licenses.ORA-00036ORA-00036: maximum number of recursive SQL levels (string) exceededCause: An attempt was made to go more than thespecified number of recursiveSQL levels.Action: Remove the recursive SQL, possibly a recursivetrigger.ORA-00036: maximum number of recursive SQL levels(string) exceededCause: An attempt was made to go more than thespecified number of recursiveSQL levels.Action: Remove the recursive SQL, possibly a recursivetrigger.ORA-00036 maximum number of recursive SQL levels(string) exceededCause: An attempt was made to go more than thespecified number ofrecursive SQL levels.Action: Remove the recursive SQL, possibly arecursive trigger.Error Code Oracle11g Oracle10g Oracle9iORA-00037ORA-00037: cannot switch to a session belonging to a different server groupCause: An attempt was made to switch to a session in adifferent server group.This is not allowed.Action: Make sure the server switches to a session thatbelongs to its servergroup.ORA-00037: cannot switch to a session belonging to adifferent server groupCause: An attempt was made to switch to a session ina different server group.This is not allowed.Action: Make sure the server switches to a session thatbelongs to its servergroup.ORA-00037 cannot switch to a session belonging toa different server groupCause: An attempt was made to switch to a sessionin a different server group.This is not allowed.Action: Make sure the server switches to a sessionthat belongs to its servergroup.ORA-00038ORA-00038: Cannot create session: server groupbelongs to another userCause: An attempt was made to create a non-migratable session in a server groupthat is owned by a different user.Action: A server group is owned by the first user whologs into a server in theserver group in non-migratable mode. All subsequentnon-migratable mode loginsmust be made by the user who owns the server group.To have a different userlogin in non-migratable mode, the ownership of theserver group will have to bechanged. This can be done by logging off all currentsessions and detaching fromall existing servers in the server group and then havingthe new user login tobecome the new owner.ORA-00038: Cannot create session: server groupbelongs to another userCause: An attempt was made to create a non-migratable session in a server groupthat is owned by a different user.Action: A server group is owned by the first user whologs into a server in theserver group in non-migratable mode. All subsequentnon-migratable mode loginsmust be made by the user who owns the server group.To have a different userlogin in non-migratable mode, the ownership of theserver group will have to bechanged. This can be done by logging off all currentsessions and detaching fromall existing servers in the server group and then havingthe new user login tobecome the new owner.ORA-00038 Cannot create session: server groupbelongs to another userCause: An attempt was made to create a non-migratable session in a servergroup that is owned by a different user.Action: A server group is owned by the first user whologs into a server in theserver group in non-migratable mode. Allsubsequent non-migratable modelogins must be made by the user who owns theserver group. To have adifferent user log in non-migratable mode, theownership of the server groupwill have to be changed. This can be done by loggingoff all current sessionsand detaching from all existing servers in the servergroup and then having thenew user login to become the new owner.ORA-00039ORA-00039: error during periodic actionCause: An unexpected error occurred while executing aperiodically invokedAction: Check the error stack for detailed errorinformation.Error Code Oracle11g Oracle10g Oracle9iORA-00040ORA-00040: active time limit exceeded - call aborted Cause: The Resource Manager SWITCH_TIME limit wasexceeded.Action: Reduce the complexity of the update or query,or contact your databaseadministrator for more information.ORA-00040: active time limit exceeded - call aborted Cause: The Resource Manager SWITCH_TIME limit was exceeded.Action: Reduce the complexity of the update or query, or contact your databaseadministrator for more information.ORA-00041ORA-00041: active time limit exceeded - sessionterminatedCause: The Resource Manager SWITCH_TIME limit wasexceeded.Action: Reduce the complexity of the update or query,or contact your databaseadministrator for more information.ORA-00041: active time limit exceeded - session terminatedCause: The Resource Manager SWITCH_TIME limit was exceeded.Action: Reduce the complexity of the update or query, or contact your databaseadministrator for more information.ORA-00042ORA-00042: Unknown Service name stringCause: An attempt was made to use an invalidapplication service.Action: Use a valid service name from SERVICE$ or add anew service using theDBMS_SERVICE package.ORA-00042: Unknown Service name stringCause: An attempt was made to use an invalid application service.Action: Use a valid service name from SERVICE$ or add a new service using theDBMS_SERVICE package.ORA-00043ORA-00043: remote operation failedCause: Execution of the inter-instance operation failed.Action: Check the status of the target instance. Theoperation may have partiallyexecuted. Verify the result of the intended operation.ORA-00044ORA-00044: timed_statistics must be TRUE whenstatistics_level is not BASICCause: The user attempted to set timed_statistics toFALSE when statistics_levelwas not BASIC. timed_statistics is required to be TRUE tocollect meaningfulstatistics when statistics_level is set to TYPICAL or ALL.Action: Either set timed_statistics to TRUE or setstatistics_level to BASIC.Error Code Oracle11g Oracle10g Oracle9iORA-00050ORA-00050: operating system error occurred whileobtaining an enqueueCause: Could not obtain the operating system resourcesnecessary to cover anoracle enqueue. This is normally the result of anoperating system user quota thatis too low.Action: Look up the operating system error in yoursystem documentation andperform the needed action.ORA-00050: operating system error occurred whileobtaining an enqueueCause: Could not obtain the operating systemresources necessary to cover anoracle enqueue. This is normally the result of anoperating system user quota thatis too low.Action: Look up the operating system error in yoursystem documentation andperform the needed action.ORA-00050 operating system error occurred whileobtaining an enqueueCause: Could not obtain the operating systemresources necessary to cover anOracle enqueue. This is normally the result of anoperating system user quotathat is too low.Action: Look up the operating system error in yoursystem documentation andperform the needed action.ORA-00051ORA-00051: timeout occurred while waiting for aresourceCause: Usually due to a dead instance.Action: Check for any dead, unrecovered instances andrecover them.ORA-00051: timeout occurred while waiting for aresourceCause: Usually due to a dead instance.Action: Check for any dead, unrecovered instances andrecover them.ORA-00051 timeout occurred while waiting for aresourceCause: This message is usually caused by an instancethat has terminatedabnormally.Action: Restart any non-recovered instances.ORA-00052ORA-00052: maximum number of enqueue resources (string) exceededCause: Ran out of enqueue resources.Action: Increase the value of the ENQUEUE_RESOURCESinitializationparameter.ORA-00052: maximum number of enqueue resources(string) exceededCause: Ran out of enqueue resources.Action: Increase the value of theENQUEUE_RESOURCES initializationparameter.ORA-00052 maximum number of enqueue resources(string) exceededCause: Ran out of enqueue resources.Action: Increase the value of theENQUEUE_RESOURCES initializationparameter.ORA-00053ORA-00053: maximum number of enqueues exceeded Cause: Ran out of enqueue state objects.Action: Increase the value of the ENQUEUESinitialization parameter.ORA-00053: maximum number of enqueues exceededCause: Ran out of enqueue state objects.Action: Increase the value of the ENQUEUESinitialization parameter.ORA-00053 maximum number of enqueuesexceededCause: Ran out of enqueue state objects.Action: Increase the value of the ENQUEUESinitialization parameter.Error Code Oracle11g Oracle10g Oracle9iORA-00054ORA-00054: resource busy and acquire with NOWAIT specified or timeout expiredCause: Interested resource is busy.Action: Retry if necessary or increase timeout.ORA-00054: resource busy and acquire with NOWAITspecifiedCause: Resource interested is busy.Action: Retry if necessary.ORA-00054 resource busy and acquire with NOWAITspecifiedCause: The NOWAIT keyword forced a return to thecommand promptbecause a resource was unavailable for a LOCKTABLE or SELECT FORUPDATE command.Action: Try the command after a few minutes orenter the command withoutthe NOWAIT keyword.ORA-00055ORA-00055: maximum number of DML locks exceeded Cause: Ran out of DML lock state objects.Action: Increase the value of the DML_LOCKSinitialization parameter and warmstart.ORA-00055: maximum number of DML locks exceededCause: Ran out of DML lock state objects.Action: Increase the value of the DML_LOCKSinitialization parameter and warmstart.ORA-00055 maximum number of DML locksexceededCause: Ran out of DML lock state objects.Action: Increase the value of the DML_LOCKSinitialization parameter andrestart Oracle.ORA-00056ORA-00056: DDL lock on object 'string.string' is already held in an incompatiblemodeCause: An attempt was made to acquire a DDL lock thatis already locked.Action: This happens if you attempt to drop a table thathas parse locks on it.ORA-00056: DDL lock on object "string.string" isalready held in an incompatiblemodeCause: An attempt was made to acquire a DDL lockthat is already locked.Action: This happens if you attempt to drop a tablethat has parse locks on it.ORA-00056 DDL lock on object 'string.string' isalready held in an incompatiblemodeCause: The attempted lock is incompatible with theDDL lock already held onthe object. This happens if you attempt to drop atable that has parse locks.Action: Before attempting to drop a table, check thatit has no parse locks. Waita few minutes before retrying the operation.Error Code Oracle11g Oracle10g Oracle9iORA-00057ORA-00057: maximum number of temporary table locks exceededCause: The number of temporary tables equals orexceeds the number oftemporary table locks. Temporary tables are oftencreated by large sorts.Action: Increase the value of theTEMPORARY_TABLE_LOCKS initializationparameter and warm start.ORA-00057: maximum number of temporary tablelocks exceededCause: The number of temporary tables equals orexceeds the number oftemporary table locks. Temporary tables are oftencreated by large sorts.Action: Increase the value of theTEMPORARY_TABLE_LOCKS initializationparameter and warm start.ORA-00057 maximum number of temporary tablelocks exceededCause: The number of temporary tables equals orexceeds the number oftemporary table locks. Temporary tables are oftencreated by large sorts.Action: Increase the value of theTEMPORARY_TABLE_LOCKS initializationparameter and restart Oracle.ORA-00058ORA-00058: DB_BLOCK_SIZE must be string to mount this database (not string)Cause: DB_BLOCK_SIZE initialization parameter is wrongfor the database beingmounted. It does not match the value used to create thedatabase.Action: Fix the value of the DB_BLOCK_SIZE parameteror mount a database thatmatches the value.ORA-00058: DB_BLOCK_SIZE must be string to mountthis database (not string)Cause: DB_BLOCK_SIZE initialization parameter iswrong for the database beingmounted. It does not match the value used to createthe database.Action: Fix the value of the DB_BLOCK_SIZE parameteror mount a database thatmatches the value.ORA-00058 DB_BLOCK_SIZE must be string to mountthis database (not string)Cause: The value of the DB_BLOCK_SIZE initializationparameter used to startthis database does not match the value used whenthat database was created.Potential reasons for this mismatch are:■mounting the wrong database■using the wrong initialization parameter filen the value of the DB_BLOCK_SIZE parameter waschangedAction: For one of the above causes, either:■mount the correct database■use the correct initialization parameter file■correct the value of the DB_BLOCK_SIZE parameter。