Overblog Suivre ce blog
Editer la page Administration Créer mon blog
/ / /

Erreurs ORA-00001 à ORA-00200 Cause et Action


ORA-00001 ORA-00001: unique constraint (string.string) violated
Cause An UPDATE or INSERT statement attempted to insert a duplicate key. For Trusted Oracle configured in DBMS MAC mode, you may see this message if a duplicate entry exists at a different level.
Action Either remove the unique restriction or do not insert the key.

ORA-00017 ORA-00017: session requested to set trace event
Cause The current session was requested to set a trace event by another session.
Action This is used internally; no action is required.

ORA-00018 ORA-00018: maximum number of sessions exceeded
Cause All session state objects are in use.
Action Increase the value of the SESSIONS initialization parameter.

ORA-00019 ORA-00019: maximum number of session licenses exceeded
Cause All licenses are in use.
Action Increase the value of the LICENSE MAX SESSIONS initialization parameter.

ORA-00020 ORA-00020: maximum number of processes (string) exceeded
Cause All process state objects are in use.
Action Increase the value of the PROCESSES initialization parameter.

ORA-00021 ORA-00021: session attached to some other process; cannot switch session
Cause The user session is currently used by others.
Action Do not switch to a session attached to some other process.

ORA-00022 ORA-00022: invalid session ID; access denied
Cause Either the session specified does not exist or the caller does not have the privilege to access it.
Action Specify a valid session ID that you have privilege to access, that is either you own it or you have the CHANGE_USER privilege.

ORA-00023 ORA-00023: session references process private memory; cannot detach session
Cause An attempt was made to detach the current session when it contains references to process private memory.
Action A session may contain references to process memory (PGA) if it has an open network connection, a very large context area, or operating system privileges. To allow the detach, it may be necessary to close the session's database links and/or cursors. Detaching a session with operating system privileges is always disallowed.

ORA-00024 ORA-00024: logins from more than one process not allowed in single-process mode
Cause Trying to login more than once from different processes for ORACLE started in single-process mode.
Action Logoff from the other process.

ORA-00025 ORA-00025: failed to allocate string
Cause Out of memory.
Action Restart with larger sga heap.

ORA-00026 ORA-00026: missing or invalid session ID
Cause Missing or invalid session ID string for ALTER SYSTEM KILL SESSION.
Action Retry with a valid session ID.

ORA-00027 ORA-00027: cannot kill current session
Cause Attempted to use ALTER SYSTEM KILL SESSION to kill the current session.
Action None.

ORA-00028 ORA-00028: your session has been killed
Cause A privileged user has killed your session and you are no longer logged on to the database.
Action Login again if you wish to continue working.

ORA-00029 ORA-00029: session is not a user session
Cause The session ID specified in an ALTER SYSTEM KILL SESSION command was not a user session (for example, recursive, etc.).
Action Retry with a user session ID.

ORA-00030 ORA-00030: User session ID does not exist.
Cause The user session ID no longer exists, probably because the session was logged out.
Action Use a valid session ID.

ORA-00031 ORA-00031: session marked for kill
Cause The session specified in an ALTER SYSTEM KILL SESSION command cannot be killed immediately (because it is rolling back or blocked on a network operation), but it has been marked for kill. This means it will be killed as soon as possible after its current uninterruptable operation is done.
Action No action is required for the session to be killed, but further executions of the ALTER SYSTEM KILL SESSION command on this session may cause the session to be killed sooner.

ORA-00032 ORA-00032: invalid session migration password
Cause The session migration password specified in a session creation call was invalid (probably too long).
Action Retry with a valid password (less than 30 chars).

ORA-00033 ORA-00033: current session has empty migration password
Cause An attempt was made to detach or clone the current session and it has an empty migration password. This is not allowed.
Action Create the session with a non-empty migration password.

ORA-00034 ORA-00034: cannot string in current PL/SQL session
Cause An attempt was made to issue a commit or rollback from a PL/SQL object (procedure, function, package) in a session that has this disabled (by 'alter session disable commit in procedure')
Action Enable commits from PL/SQL in this session, or do not attempt to use commit or rollback in PL/SQL when they are disabled in the current session.

ORA-00036 ORA-00036: maximum number of recursive SQL levels (string) exceeded
Cause An attempt was made to go more than the specified number of recursive SQL levels.
Action Remove the recursive SQL, possibly a recursive trigger.

ORA-00037 ORA-00037: cannot switch to a session belonging to a different server group
Cause An attempt was made to switch to a session in a different server group. This is not allowed.
Action Make sure the server switches to a session that belongs to its server group.

ORA-00038 ORA-00038: Cannot create session: server group belongs to another user
Cause An attempt was made to create a non-migratable session in a server group that is owned by a different user.
Action A server group is owned by the first user who logs into a server in the server group in non-migratable mode. All subsequent non-migratable mode logins must be made by the user who owns the server group. To have a different user login in non-migratable mode, the ownership of the server group will have to be changed. This can be done by logging off all current sessions and detaching from all existing servers in the server group and then having the new user login to become the new owner.

ORA-00040 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 database administrator for more information.

ORA-00041 ORA-00041: active time limit exceeded - session terminated
Cause The Resource Manager SWITCH_TIME limit was exceeded.
Action Reduce the complexity of the update or query, or contact your database administrator for more information.

ORA-00050 ORA-00050: operating system error occurred while obtaining an enqueue
Cause Could not obtain the operating system resources necessary to cover an oracle enqueue. This is normally the result of an operating system user quota that is too low.
Action Look up the operating system error in your system documentation and perform the needed action.

ORA-00051 ORA-00051: timeout occurred while waiting for a resource
Cause Usually due to a dead instance.
Action Check for any dead, unrecovered instances and recover them.

ORA-00052 ORA-00052: maximum number of enqueue resources (string) exceeded
Cause Ran out of enqueue resources.
Action Increase the value of the ENQUEUE_RESOURCES initialization parameter.

ORA-00053 ORA-00053: maximum number of enqueues exceeded
Cause Ran out of enqueue state objects.
Action Increase the value of the ENQUEUES initialization parameter.

ORA-00054 ORA-00054: resource busy and acquire with NOWAIT specified
Cause Resource interested is busy.
Action Retry if necessary.

ORA-00055 ORA-00055: maximum number of DML locks exceeded
Cause Ran out of DML lock state objects.
Action Increase the value of the DML_LOCKS initialization parameter and warm start.

ORA-00056 ORA-00056: DDL lock on object 'string.string' is already held in an incompatible mode
Cause An attempt was made to acquire a DDL lock that is already locked.
Action This happens if you attempt to drop a table that has parse locks on it.

ORA-00057 ORA-00057: maximum number of temporary table locks exceeded
Cause The number of temporary tables equals or exceeds the number of temporary table locks. Temporary tables are often created by large sorts.
Action Increase the value of the TEMPORARY_TABLE_LOCKS initialization parameter and warm start.

ORA-00058 ORA-00058: DB_BLOCK_SIZE must be string to mount this database (not string)
Cause DB_BLOCK_SIZE initialization parameter is wrong for the database being mounted. It does not match the value used to create the database.
Action Fix the value of the DB_BLOCK_SIZE parameter or mount a database that matches the value.

ORA-00059 ORA-00059: maximum number of DB_FILES exceeded
Cause The value of the DB_FILES initialization parameter was exceeded.
Action Increase the value of the DB_FILES parameter and warm start.

ORA-00060 ORA-00060: deadlock detected while waiting for resource
Cause Transactions deadlocked one another while waiting for resources.
Action Look at the trace file to see the transactions and resources involved. Retry if necessary.

ORA-00061 ORA-00061: another instance has a different DML_LOCKS setting
Cause The shared instance being started is using DML locks, and the running instances are not, or vice-versa.
Action Ensure that all instances' INIT.ORA files specify the DML_LOCKS parameter as 0 or all as non-zero.

ORA-00062 ORA-00062: DML full-table lock cannot be acquired; DML_LOCKS is 0
Cause The instance was started with DML_LOCKS = 0, and the statement being executed needs a full-table lock (S, X, or SSX).
Action Restart the instance with DML_LOCKS not equal to zero, and reexecute the statement.

ORA-00063 ORA-00063: maximum number of LOG_FILES exceeded
Cause LOG_FILES initialization parameter value exceeded
Action Increase the value of the LOG_FILES initialization parameter and warm start. The parameter needs to be as large as the highest number of log files that currently exist rather than just the count of logs that exist.

ORA-00064 ORA-00064: object is too large to allocate on this O/S (string,string)
Cause An initialization parameter was set to a value that required allocating more contiguous space than can be allocated on this operating system.
Action Reduce the value of the initialization parameter.

ORA-00065 ORA-00065: initialization of FIXED_DATE failed
Cause The FIXED_DATE string was not in date format yyyy-mm-dd:hh24:mi:ss.
Action Make sure the initialization parameter is in the correct date format.

ORA-00066 ORA-00066: LOG_FILES is string but needs to be string to be compatible
Cause The maximum number of log files supported by this instance is not the same as for the other instances. All instances must be able to open all the files any instance can open.
Action Change the value of the LOG_FILES initialization parameter to be compatible.

ORA-00067 ORA-00067: invalid value string for parameter string; must be at least string
Cause The value for the initialization parameter is invalid.
Action Choose a value as indicated by the message.

ORA-00068 ORA-00068: invalid value string for parameter string, must be between string and string
Cause The value for the initialization parameter is invalid.
Action Choose a value as indicated by the message.

ORA-00069 ORA-00069: cannot acquire lock -- table locks disabled for string
Cause A command was issued that tried to lock the table indicated in the message. Examples of commands that can lock tables are: LOCK TABLE, ALTER TABLE ... ADD (...), and so on.
Action Use the ALTER TABLE ... ENABLE TABLE LOCK command, and retry the command.

ORA-00070 ORA-00070: command string is not valid
Cause An invalid debugger command was specified.
Action Type HELP to see the list of available commands.

ORA-00071 ORA-00071: process number must be between 1 and string
Cause An invalid process number was specified.
Action Specify a valid process number.

ORA-00072 ORA-00072: process "string" is not active
Cause An invalid process was specified.
Action Specify a valid process.

ORA-00073 ORA-00073: command string takes between string and string argument(s)
Cause An incorrect number of arguments was specified.
Action Specify the correct number of arguments. Type HELP to see the list of commands and their syntax.

ORA-00074 ORA-00074: no process has been specified
Cause No debug process has been specified.
Action Specify a valid process.

ORA-00075 ORA-00075: process "string" not found in this instance
Cause The specified process was not logged on to the current instance.
Action Specify a valid process.

ORA-00076 ORA-00076: dump string not found
Cause An attempt was made to invoke a dump that does not exist.
Action Type DUMPLIST to see the list of available dumps.

ORA-00077 ORA-00077: dump string is not valid
Cause An attempt was made to invoke an invalid dump.
Action Try another dump.

ORA-00078 ORA-00078: cannot dump variables by name
Cause An attempt was made to dump a variable by name on a system that does not support this feature.
Action Try the PEEK command.

ORA-00079 ORA-00079: variable string not found
Cause An attempt was made to dump a variable that does not exist.
Action Use a valid variable name.

ORA-00080 ORA-00080: invalid global area specified by level string
Cause An attempt was made to dump an invalid global area.
Action Use level 1 for the PGA, 2 for the SGA, and 3 for the UGA. Use to dump global area as well as bytes for every pointer; must be a multiple of 4.

ORA-00081 ORA-00081: address range [string, string) is not readable
Cause An attempt was made to read/write an invalid memory address range.
Action Try another address or length.

ORA-00082 ORA-00082: memory size of string is not in valid set of [1], [2], [4]stringstringstringstringstring
Cause An invalid length was specified for the POKE command.
Action Use a valid length (either 1, 2, 4, or possibly 8).

ORA-00083 ORA-00083: warning: possibly corrupt SGA mapped
Cause Even though there may be SGA corruptions, the SGA was mapped.
Action Use the DUMPSGA command to dump the SGA.

ORA-00084 ORA-00084: global area must be PGA, SGA, or UGA
Cause An attempt was made to dump an invalid global area.
Action Specify either PGA, SGA, or UGA.

ORA-00085 ORA-00085: current call does not exist
Cause An invalid attempt was made to dump the current call heap.
Action Wait until the process starts a call.

ORA-00086 ORA-00086: user call does not exist
Cause An invalid attempt was made to dump the user call heap.
Action Wait until the process starts a call.

ORA-00087 ORA-00087: command cannot be executed on remote instance
Cause Cluster database command issued for non cluster database ORADEBUG command.
Action Issue the command without the cluster database syntax.

ORA-00088 ORA-00088: command cannot be executed by shared server
Cause Debug command issued on shared server.
Action Reissue the command using a dedicated server.

ORA-00089 ORA-00089: invalid instance number in ORADEBUG command
Cause An invalid instance number was specified in a cluster database ORADEBUG command.
Action Reissue the command with valid instance numbers.

ORA-00090 ORA-00090: failed to allocate memory for cluster database ORADEBUG command
Cause Could not allocate memory needed to execute cluster database oradebug.
Action Reissue the command on each instance with single-instance oradebug.

ORA-00091 ORA-00091: LARGE_POOL_SIZE must be at least string
Cause The value of LARGE_POOL_SIZE is below the minimum size.
Action Increase the value of LARGE_POOL_SIZE past the minimum size.

ORA-00092 ORA-00092: LARGE_POOL_SIZE must be greater than LARGE_POOL_MIN_ALLOC
Cause The value of LARGE_POOL_SIZE is less than the value of LARGE_POOL_MIN_ALLOC.
Action Increase the value of LARGE_POOL_SIZE past the value of LARGE_POOL_MIN_ALLOC.

ORA-00093 ORA-00093: %s must be between string and string
Cause The parameter value is not in a valid range.
Action Modify the parameter value to be within the specified range.

ORA-00094 ORA-00094: %s requires an integer value
Cause The parameter value is not an integer.
Action Modify the parameter value to be an integer.

ORA-00096 ORA-00096: invalid value string for parameter string, must be from among string
Cause The value for the initialization parameter is invalid.
Action Choose a value as indicated by the message.

ORA-00097 ORA-00097: use of Oracle SQL feature not in SQL92 string Level
Cause Usage of Oracle's SQL extensions.
Action none

ORA-00099 ORA-00099: timed out while waiting for resource, potential PDML deadlock
Cause The resource needed by the transaction was busy. The PDML transaction could not acquire the resource within the specified amount of time. This indicates potential deadlock involving this PDML transaction and other transactions currently running in the system.
Action Increase the the value of the PARALLEL_TRANSACTION_RESOURCE_TIMEOUT parameter; then retry the operation.

ORA-00100 ORA-00100: no data found
Cause An application made reference to unknown or inaccessible data.
Action Handle this condition within the application or make appropriate modifications to the application code. NOTE: If the application uses Oracle-mode SQL instead of ANSI-mode SQL, ORA-01403 will be generated instead of ORA-00100.

ORA-00101 ORA-00101: invalid specification for system parameter DISPATCHERS
Cause The syntax for the DISPATCHERS parameter is incorrect.
Action Refer to the manual for correct syntax.

ORA-00102 ORA-00102: network protocol string cannot be used by dispatchers
Cause The network specified in DISPATCHERS does not have the functionality required by the dispatchers.
Action Refer to the manual on network protocols supported by the dispatchers.

ORA-00103 ORA-00103: invalid network protocol; reserved for use by dispatchers
Cause The network specified in the SQL*Net connect string is reserved for use by the dispatchers.
Action Specify other network protocols in the connection string.

ORA-00104 ORA-00104: deadlock detected; all public servers blocked waiting for resources
Cause All available public servers are servicing requests that require resources locked by a client which is unable to get a public server to release the resources.
Action Increase the limit for the system parameter MAX_SHARED_SERVERS as the system will automaticaly start up new servers to break the deadlock until the number of servers reaches the value specified in MAX_SHARED_SERVERS.

ORA-00105 ORA-00105: too many dispatcher configurations
Cause Too many dispatcher configurations have been specified. No more can be added.
Action Consolidate the dispatcher configurations if possible.

ORA-00106 ORA-00106: cannot startup/shutdown database when connected to a dispatcher
Cause An attempt was made to startup/shutdown database when connected to a shared server via a dispatcher.
Action Re-connect as user INTERNAL without going through the dispatcher. For most cases, this can be done by connect to INTERNAL without specifying a network connect string.

ORA-00107 ORA-00107: failed to connect to ORACLE listener process
Cause Most likely due to the fact that ORACLE listener has not been started.
Action Start ORACLE listener if it has not been started. Or else contact your ORACLE representative.

ORA-00108 ORA-00108: failed to set up dispatcher to accept connection asynchronously
Cause Most likely due to the fact that the network protocol used by the the dispatcher does not support aynchronous operations.
Action Contact your ORACLE representative.

ORA-00109 ORA-00109: invalid value for attribute string: string
Cause The value specified for the attribute was incorrect.
Action Refer to the manual for the proper values.

ORA-00110 ORA-00110: invalid value string for attribute string, must be between string and string
Cause The value specified for the attribute was incorrect.
Action Specify a value within the range allowed.

ORA-00111 ORA-00111: invalid attribute string
Cause The specified attribute was not recognized.
Action Refer to the manual for the proper keyword to use to specify a dispatcher attribute.

ORA-00112 ORA-00112: value of string is null
Cause The attribute was specified with no value.
Action Specify a non-null value.

ORA-00113 ORA-00113: protocol name string is too long
Cause A protocol name specified in the DISPATCHERS system parameter is too long.
Action Use a valid protocol name for the DISPATCHERS value.

ORA-00114 ORA-00114: missing value for system parameter SERVICE_NAMES
Cause No value was specified for the SERVICE_NAMES system parameter, nor for the DB_NAME parameter.
Action Add an SERVICE_NAMES or DB_NAME definition to the INIT.ORA file. By default, SERVICE_NAMES is the value of DB_NAME unless SERVICE_NAMES is explicitly specified.

ORA-00115 ORA-00115: connection refused; dispatcher connection table is full
Cause A connection request was refused by a dispatcher because the dispatcher cannot support any more connections.
Action Connect to a different dispatcher, or use a dedicated server.

ORA-00116 ORA-00116: SERVICE_NAMES name is too long
Cause A service name specified in the SERVICE_NAMES system parameter is too long.
Action Use a shorter name in the SERVICE_NAMES value (<= 255 chars).

ORA-00117 ORA-00117: PROTOCOL, ADDRESS or DESCRIPTION must be specified
Cause PROTOCOL, ADDRESS or DESCRIPTION was not specified.
Action Use one of the attributes: PROTOCOL, ADDRESS or DESCRIPTION to specify the listening address for dispatchers.

ORA-00118 ORA-00118: Only one of PROTOCOL, ADDRESS or DESCRIPTION may be specified
Cause More than one of PROTOCOL, ADDRESS or DESCRIPTION was specified.
Action Use only one of the attributes: PROTOCOL, ADDRESS or DESCRIPTION to specify the listening address for dispatchers.

ORA-00119 ORA-00119: invalid specification for system parameter string
Cause The syntax for the specified parameter is incorrect.
Action Refer to the Oracle Reference Manual for the correct syntax.

ORA-00122 ORA-00122: cannot initialize network configuration
Cause ORACLE could not initialize SQL*Net version 2.
Action Check the error stack for detailed information.

ORA-00123 ORA-00123: idle public server terminating
Cause Too many idle servers were waiting on the common queue.
Action This error is used internally, no action is required.

ORA-00125 ORA-00125: connection refused; invalid presentation
Cause The PRESENTATION in the CONNECT_DATA of the TNS address DESCRIPTION is not correct or is not supported.
Action Correct the PRESENTATION specified in the TNS address.

ORA-00126 ORA-00126: connection refused; invalid duplicity
Cause The DUPLICITY in the CONNECT_DATA of the TNS address DESCRIPTION is not correct or is not supported.
Action Correct the DUPLICITY specified in the TNS address.

ORA-00127 ORA-00127: dispatcher string does not exist
Cause There is currently no dispatcher running with the specified name.
Action Retry with a name of the form "D###" denoting an existing dispatcher process.

ORA-00128 ORA-00128: this command requires a dispatcher name
Cause Wrong syntax for ALTER SYSTEM SHUTDOWN
Action Use correct syntax: ALTER SYSTEM SHUTDOWN [ IMMEDIATE ] 'dispatcher name'

ORA-00129 ORA-00129: listener address validation failed 'string'
Cause An error was encountered while validating the listener address.
Action Resolve error or contact your ORACLE representative.

ORA-00130 ORA-00130: invalid listener address 'string'
Cause The listener address specification is not valid.
Action Make sure that all fields in the listener address (protocol, port, host, key, ...) are correct.

ORA-00131 ORA-00131: network protocol does not support registration 'string'
Cause The specified protocol does not support async notification.
Action Refer to the manual for information on supported network protocols.

ORA-00132 ORA-00132: syntax error or unresolved network name 'string'
Cause Listener address has syntax error or cannot be resolved.
Action If a network name is specified, check that it corresponds to an entry in TNSNAMES.ORA or other address repository as configured for your system. Make sure that the entry is syntactically correct.

ORA-00133 ORA-00133: value of string is too long
Cause The value specified for the attribute was too long.
Action Use shorter names and keywords or remove unneeded blanks.

ORA-00134 ORA-00134: invalid DISPATCHERS specification #string
Cause The syntax for the n-th DISPATCHERS specification was incorrect.
Action Refer to the Oracle Reference Manual for the correct syntax.

ORA-00150 ORA-00150: duplicate transaction ID
Cause Attempted to start a new transaction with an ID already in use by an existing transaction.
Action Check your application.

ORA-00151 ORA-00151: invalid transaction ID
Cause The specified transaction ID does not correspond to an existing valid transaction.
Action Check your application.

ORA-00152 ORA-00152: current session does not match requested session
Cause The current session is not the same as the session that was passed into a upixado() call.
Action Check your application.

ORA-00153 ORA-00153: internal error in XA library
Cause The XA library could not access thread-specific pointers.
Action Contact customer support.

ORA-00154
ORA-00154: protocol error in transaction monitor
Cause The transaction monitor returned TMJOIN on an AX_REG call but the transaction was locally suspended.
Action Contact the transaction monitor customer support.

ORA-00155 ORA-00155: cannot perform work outside of global transaction
Cause The application tried to perform some work on either an Oracle 7.3 server or an Oracle8 server with local transactions disabled while outside of a global transaction.
Action Check if the application is connected to an Oracle 7.3 server. The Transaction monitor must not return a NULL XID on an AX_REG call when the resource manager is Oracle 7.3. If the application is connected to an Oracle8 server, either set nolocal=f in the xa_open string or start a global transaction prior to attempting the work.

ORA-00160 ORA-00160: global transaction length string is greater than maximum (string)
Cause An external global transaction ID with a too large length field was passed in.
Action Report the problem to your external transaction coordinator vendor.

ORA-00161 ORA-00161: transaction branch length string is illegal (maximum allowed string)
Cause An external transaction branch ID with a length either too large or 0 was passed in.
Action Report the problem to your external transaction coordinator vendor.

ORA-00162 ORA-00162: external dbid length string is greater than maximum (string)
Cause An external database name with too large a length field was passed in.
Action Report the problem to your external transaction coordinator vendor.

ORA-00163 ORA-00163: internal database name length string is greater than maximum (string)
Cause An internal database name with a too large length field was passed in.
Action Report the problem to your external transaction coordinator vendor.

ORA-00164 ORA-00164: distributed autonomous transaction disallowed within migratable distributed transaction
Cause A request was made by the application to start a distributed autonomous transaction when the application was in a migratable distributed transaction.
Action Roll back or commit the current distributed transaction first.

ORA-00165 ORA-00165: migratable distributed autonomous transaction with remote operation is not allowed
Cause A request was made by the application to start a migratable distributed autonomous transaction with remote operation.
Action none

ORA-00166 ORA-00166: remote/local nesting level is too deep
Cause Too many remote table operations required a reverse trip back to the local site, for example to execute a local function on a remote table.
Action Rearrange the query or co-locate the functions with the tables.

ORA-00200 ORA-00200: controlfile could not be created
Cause It was not possible to create the controlfile.
Action Check that there is sufficient disk space and no conflicts in filenames and try to create the controlfile again.

Partager cette page

Repost 0
Published by