Oracle 11g Error Codes and Solution Suggestions from ORA-20000 to ORA-22000
- ORA-20000: string
- Cause: The stored procedure ‘raise_application_error’ was called which causes this error to be generated.
- Action: Correct the problem as described in the error message or contact the application administrator or DBA for more information.
- ORA-21300: objects option not installed
- Cause: The objects option is not installed at this site. object types and other object features are, therefore, unavailable.
- Action: Install the objects option. The objects option is not part of the Oracle Server product and must be purchased separately. Contact an Oracle sales representative if the objects option needs to be purchased.
- ORA-21301: not initialized in object mode
- Cause: This function requires the OCI process to be initialized in object mode.
- Action: Specify OCI_OBJECT mode when calling OCIInitialize().
- ORA-21500: internal error code, arguments: [string], [string], [string], [string], [string], [string], [string], [string]
- Cause: This is the generic error number for the OCI environment (client-side) internal errors. This indicates that the OCI environment has encountered an exceptional condition.
- Action: Report as a bug – the first argument is the internal error number.
- ORA-21501: program could not allocate memory
- Cause: The operating system has run out of memory.
- Action: Take action to make more memory available to the program.
- ORA-21503: program terminated by fatal error
- Cause: A program is in an unrecoverable error state.
- Action: Report as a bug.
- ORA-21520: database server driver not installed
- Cause: User attempted to access a database server through an object-mode OCI environment but the necessary driver for supporting such access to the database server is not installed or linked in.
- Action: Check if the driver corresponding to the database server has been installed/linked in and entered in the server driver table.
- ORA-21521: exceeded maximum number of connections in OCI (object mode only)
- Cause: User exceeded the maximum number of connections (255) that can be supported by an OCI environment in object mode.
- Action: Close some of existing and unused connections before opening more connections.
- ORA-21522: attempted to use an invalid connection in OCI (object mode only)
- Cause: User attempted to use an invalid connection or a connection that has been terminated in an OCI environment (object mode), or user attempted to dereference a REF obtained from a connection which has been terminated.
- Action: Ensure that the connection exists and is still valid.
- ORA-21523: functionality not supported by the server (object mode only)
- Cause: User attempted to use a functionality that the server does not support.
- Action: Upgrade the server
- ORA-21524: object type mismatch
- Cause: The object type of the object is different from what is specified.
- Action: Check the type of the object and correct it.
- ORA-21525: attribute number or (collection element at index) string violated its constraints
- Cause: Attribute value or collection element value violated its constraint.
- Action: Change the value of the attribute or collection element such that it meets its constraints. The constraints are specified as part of the attribute or collection element’s schema information.
- ORA-21526: initialization failed
- Cause: The initialization sequence failed. This can happen, for example, if an environment variable such as NLS_DATE_FORMAT is set to an invalid value.
- Action: Check that all NLS environment variables are well-formed.
- ORA-21527: internal OMS driver error
- Cause: A process has encountered an exceptional condition. This is the generic internal error number for Oracle object management services exceptions.
- Action: Report this as a bug to Oracle Support Services.
- ORA-21528: internal error, image could not be understood
- Cause: The format of the image passed to the pickler is incorrect and cannot be understood.
- Action: Contact Oracle Support Services.
- ORA-21560: argument string is null, invalid, or out of range
- Cause: The argument is expecting a non-null, valid value but the argument value passed in is null, invalid, or out of range. Examples include when the LOB/FILE positional or size argument has a value outside the range 1 through (4GB – 1), or when an invalid open mode is used to open a file, etc.
- Action: Check your program and correct the caller of the routine to not pass a null, invalid or out-of-range argument value.
- ORA-21561: OID generation failed
- Cause: The handles passed in may not be valid
- Action: Check the validity of the env, svc handles
- ORA-21600: path expression too long
- Cause: The path expression that is supplied by the user is too long. The path expression is used to specify the position of an attribute in an object. This error occurs when one of the intermediate elements in the path expression refers to an attribute of a built-in type. Thus, the OCI function cannot proceed on to process the rest of the elements in the path expression.
- Action: User should pass in the correct path expression to locate the attribute.
- ORA-21601: attribute is not an object
- Cause: The user attempts to perform an operation (that is valid only for an object) to an attribute of a built-in type. An example of such an illegal operation is to dynamically set a null structure to an attribute of a built-in type.
- Action: User should avoid performing such operation to an attribute of built-in type.
- ORA-21602: operation does not support the specified typecode
- Cause: The user attempts to perform an operation that does not support the specified typecode.
- Action: User should use the range of valid typecodes that are supported by this operation.
- ORA-21603: property id [string] is invalid
- Cause: The specified property id is invalid.
- Action: User should specify a valid property id. Valid property ids are enumerated by OCIObjectPropId.
- ORA-21604: property [string] is not a property of transient or value instances
- Cause: Trying to get a property which applies only to persistent objects.
- Action: User should check the lifetime and only get this property for persistent objects.
- ORA-21605: property [string] is not a property of value instances
- Cause: Trying to get a property which applies only to persistent and transient objects.
- Action: User should check the lifetime and only get this property for persistent and transient objects.
- ORA-21606: can not free this object
- Cause: Trying to free an object that is persistent and dirty and the OCI_OBJECTFREE_FORCE flag is not specified.
- Action: Either flush the persistent object or set the flag to OCI_OBJECTFREE_FORCE
- ORA-21607: memory cartridge service handle not initialized
- Cause: Attempt to use the handle without initializing it.
- Action: Initialize the memory cartridge service handle.
- ORA-21608: duration is invalid for this function
- Cause: Attempt to use a duration not valid for this function.
- Action: Use a valid duration – a previously created user duration or OCI_DURATION_STATEMENT or OCI_DURATION_SESSION. For callout duration or external procedure duration, use OCIExtProcAllocCallMemory.
- ORA-21609: memory being resized without being allocated first
- Cause: Attempt to resize memory without allocating it first.
- Action: Allocate the memory first before resizing it.
- ORA-21610: size [string] is invalid
- Cause: Attempt to resize memory with invalid size.
- Action: Pass in a valid size (must be a positive integer).
- ORA-21611: key length [string] is invalid
- Cause: Attempt to use an invalid key length.
- Action: Key length is invalid and valid range is 0 to 64
- ORA-21612: key is already being used
- Cause: Attempt to use a key that is already used.
- Action: Use a new key that is not yet being used.
- ORA-21613: key does not exist
- Cause: Attempt to use a non-existent key
- Action: Use a key that already exists.
- ORA-21614: constraint violation for attribute number [string]
- Cause: Constraints on the attribute were violated
- Action: Correct the value (of the attribute) so that it satisfies constraints
- ORA-21615: copy of an OTS (named or simple) instance failed
- Cause: see following message
- Action: Check that no attribute value violates constraints.
- ORA-21700: object does not exist or is marked for delete
- Cause: User attempted to perform an inappropriate operation to an object that is non-existent or marked for delete. Operations such as pinning, deleting and updating cannot be applied to an object that is non-existent or marked for delete.
- Action: User needs to re-initialize the reference to reference an existent object or the user needs to unmark the object.
- ORA-21701: attempt to flush objects to different servers
- Cause: User attempted to flush objects to different servers in one function call. These objects are obtained by calling a callback functions provided by the program.
- Action: User should avoid performing such operation.
- ORA-21702: object is not instantiated or has been de-instantiated in cache
- Cause: User attempted to perform an inappropriate operation to a transient object that is not instantiated in the object cache. Operations that cannot be applied to a not-instantiated transient object include deleting or pinning such an object.
- Action: User should check their code to see if they are performing such an operation without instantiating the object first, or performing such an operation after the allocation duration of the object has expired.
- ORA-21703: cannot flush an object that is not modified
- Cause: See the error message.
- Action: The object should not be flushed.
- ORA-21704: cannot terminate cache or connection without flushing first
- Cause: See the error message.
- Action: The transaction should be aborted or committed before terminating the cache or connection.
- ORA-21705: service context is invalid
- Cause: The service context that is supplied by the user is not valid.
- Action: User needs to establish the service context.
- ORA-21706: duration does not exist or is invalid
- Cause: The duration number that is supplied by the user is not valid.
- Action: User needs to establish the duration or use a correct predefined duration.
- ORA-21707: pin duration is longer than allocation duration
- Cause: The pin duration supplied by the user is longer than the allocation duration. This affects operations such as pinning and setting default parameters.
- Action: User should use a shorter pin duration or use the null duration.
- ORA-21708: inappropriate operation on a transient object
- Cause: User attempted to perform an inappropriate operation on a transient object. Operations that cannot be applied to a transient object include flushing and locking.
- Action: User should avoid performing such operation on a transient object.
- ORA-21709: cannot refresh an object that has been modified
- Cause: User attempted to refresh an object that has been marked for delete, update or insert (new).
- Action: User should unmark the object before refreshing it.
- ORA-21710: argument is expecting a valid memory address of an object
- Cause: The object memory address that is supplied by the user is invalid. The user may have passed in a bad memory address to a function that is expecting a valid memory address of an object.
- Action: User should pass in a valid memory address of an object to the function.
- ORA-21779: duration not active
- Cause: User is trying to use a duration that has been terminated.
- Action: User should avoid performing such operation.
- ORA-21780: Maximum number of object durations exceeded.
- Cause: This typically happens if there is infinite recursion in the PL/SQL function that is being executed.
- Action: User should alter the recursion condition in order to prevent infinite recursion.