ORA-21704: cannot terminate cache or connection without flushing first

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-21703: cannot flush an object that is not modified

ORA-21703: cannot flush an object that is not modified

Cause: See the error message.

Action: The object should not be flushed.

ORA-21702: object is not instantiated or has been de-instantiated in cache

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-21701: attempt to flush objects to different servers

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-21700: object does not exist or is marked for delete

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-21615: copy of an OTS (named or simple) instance failed

ORA-21615: copy of an OTS (named or simple) instance failed

Cause: see following message

Action: Check that no attribute value violates constraints.

ORA-21614: constraint violation for attribute number (string(

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-21613: key does not exist

ORA-21613: key does not exist

Cause: Attempt to use a non-existent key

Action: Use a key that already exists.

ORA-21612: key is already being used

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-21611: key length (string( is invalid

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-21610: size (string( is invalid

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-21609: memory being resized without being allocated first

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-21608: duration is invalid for this function

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-21607: memory cartridge service handle not initialized

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-21606: can not free this object

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-21605: property (string( is not a property of value instances

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-21604: property (string( is not a property of transient or value instances

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-21603: property id (string( is invalid

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-21602: operation does not support the specified typecode

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-21601: attribute is not an object

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-21600: path expression too long

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-21561: OID generation failed

ORA-21561: OID generation failed

Cause: The handles passed in may not be valid

Action: Check the validity of the env, svc handles

ORA-21560: argument string is null, invalid, or out of range

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 or 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-21527: internal OMS driver error

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-21526: initialization failed

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-21525: attribute number or (collection element at index) string violated its constraints

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-21524: object type mismatch

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-21523: functionality not supported by the server (object mode only)

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-21522: attempted to use an invalid connection in OCI (object mode only)

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-21521: exceeded maximum number of connections in OCI (object mode only)

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-21520: database server driver not installed

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 or linked in and entered in the server driver table.

ORA-21503: program terminated by fatal error

ORA-21503: program terminated by fatal error

Cause: A program is in an unrecoverable error state.

Action: Report as a bug.

ORA-21501: program could not allocate memory

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-21500: internal error code, arguments: (string(, (string(, (string(, (string(, (string(, (string(, (string(, (string(

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-21301: not initialized in object mode

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-21300: objects option not installed

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-19999: skip_row procedure was called

ORA-19999: skip_row procedure was called

Cause: The skip_row procedure was called which raises this error

Action: Skip_row should only be called within a trigger or a procedure called by a trigger.

ORA-19960: Internal use only

ORA-19960: Internal use only

Cause: NID usage

Action: None

ORA-19958: potential deadlock involving DIAG process

ORA-19958: potential deadlock involving DIAG process

Cause: DIAG requested a control file operation that may lead to a deadlock

Action: Try last operation later when the control file is released

ORA-19957: database should have no datafiles in unknown state

ORA-19957: database should have no datafiles in unknown state

Cause: The operation failed because the database had one or more datafiles that were in an unknown state.

Action: Drop the datafiles or recover them and bring them online.

ORA-19956: database should have no offline immediate datafiles

ORA-19956: database should have no offline immediate datafiles

Cause: The operation failed because the database had one or more datafiles that were in OFFLINE IMMEDIATE mode.

Action: Drop the datafiles or recover them and bring them online.

ORA-19955: only one open thread is allowed to change the DBID

ORA-19955: only one open thread is allowed to change the DBID

Cause: The operation failed because there were active threads in the database. The most likely cause is that the database crashed the last time it was shut down.

Action: Ensure that all threads are closed before retrying the operation. Start and open the database to perform crash recovery, then shut down with the NORMAL or IMMEDIATE options to close it cleanly. Finally, try running the utility again.

ORA-19954: control file is not current

ORA-19954: control file is not current

Cause: The operation failed because a non-current, non-standby control file was mounted.

Action: Make the control file current and retry.

ORA-19953: database should not be open

ORA-19953: database should not be open

Cause: The database was open. To change the DBID, the database must be mounted exclusively.

Action: Shut down the database and mount it in exclusive mode.

ORA-19952: database should be mounted exclusively

ORA-19952: database should be mounted exclusively

Cause: The database was started in parallel mode. To change the DBID, the database must be mounted exclusively.

Action: Shut down the database and start it in exclusive mode.

ORA-19951: cannot modify control file until DBNEWID is completed

ORA-19951: cannot modify control file until DBNEWID is completed

Cause: An operation requiring to modify the control file was attempted, but a NID change is in progress.

Action: Wait until NID completes before attempting the operation. NLS_DO_ NOT_TRANSLATE (19960,19960(

ORA-19932: control file is not clone or standby

ORA-19932: control file is not clone or standby

Cause: The operation failed because the control file was not mounted as standby or clone.

Action: Mount the database as standby or clone and retry.

ORA-19931: file string has invalid creation SCN string

ORA-19931: file string has invalid creation SCN string

Cause: When opening the file to be placed in a copy or backup set, to be inspected, the file header was not recognized as a valid header because it contained a invalid creation SCN. The indicated file cannot be processed.

Action: Ensure that the correct files are being specified for the catalog or backup operation.

ORA-19930: file string has invalid checkpoint SCN string

ORA-19930: file string has invalid checkpoint SCN string

Cause: When opening the file to be placed in a copy or backup set, to be inspected, the file header was not recognized as a valid header because it contained a invalid checkpoint SCN. The indicated file cannot be processed.

Action: Ensure that the correct files are being specified for the catalog or backup operation.

ORA-19927: CONVERT DATABASE operation cannot proceed

ORA-19927: CONVERT DATABASE operation cannot proceed

Cause: An error occurred earlier during CONVERT DATABASE operation.

Action: Retry CONVERT DATABASE command.

ORA-19926: Database cannot be converted at this time

ORA-19926: Database cannot be converted at this time

Cause: Another CONVERT DATABASE operation is already in progress.

Action: Retry CONVERT DATABASE command later.

ORA-19924: there are no row with id string

ORA-19924: there are no row with id string

Cause: RMAN tried to update an V$RMAN_STATUS row, but the row don t exist.

Action: This is an internal error. Contact Oracle Support.

ORA-19923: the session for row with id string is not active

ORA-19923: the session for row with id string is not active

Cause: RMAN tried to update an V$RMAN_STATUS row but the process which owns this row died.

Action: This is an internal error. Contact Oracle Support.

ORA-19922: there is no parent row with id string and level string

ORA-19922: there is no parent row with id string and level string

Cause: RMAN tried to add a new V$RMAN_STATUS row, but the parent row did not exist.

Action: This is an internal error. Contact Oracle Support.

ORA-19921: maximum number of string rows exceeded

ORA-19921: maximum number of string rows exceeded

Cause: The maximum number of rows in the V$RMAN_STATUS or V$RMAN_ OUTPUT table has been exceeded.

Action: Close some of existing and unused RMAN connections and sessions.

ORA-19916: %s

ORA-19916: %s

Cause: An error occured when processing user request.

Action: Do not use message 19917; it is used internally for testing purpose.

ORA-19915: unable to encrypt pre-10.2 files

ORA-19915: unable to encrypt pre-10.2 files

Cause: An RMAN encrypted backup was requested, but this backup includes one or more archived logs that were generated by an older release of Oracle. These archived logs cannot be encrypted.

Action: Back up the older logs without encryption. Logs created with Oracle release 10.2 and greater can be encrypted.

ORA-19914: unable to encrypt backup

ORA-19914: unable to encrypt backup

Cause: RMAN could not create an encrypted backup. This message will be accompanied by other messages that give more details about why the encrypted backup could not be created. The most common reason for this message is that you are trying to create a backup that can be transparently decrypted, and the database external security device is not open.

Action: If the external security device is not open, then open it. If the external security device is not configured, then the only type of encrypted backup that you can create is a password-based backup.

ORA-19913: unable to decrypt backup

ORA-19913: unable to decrypt backup

Cause: A backup piece could not be decrypted. This message is accompanied with another message that indicates the name of the encrypted backup that could not be restored. The reason could be either that an invalid password was entered, or that, when using transparent decryption, the database external security device is not open.

Action: If password-based restore was enabled for this backup, then supply the correct password using the RMAN SET DECRYPTION command. If transparent restore was enabled for this backup, then ensure that the database external security device is open.