ORA Error . Listado Errores Oracle. ORA-19922 a ORA-21604

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-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-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-19926: Database cannot be converted at this time

Cause: Another CONVERT DATABASE operation is already in progress.

Action: Retry CONVERT DATABASE command later.

ORA-19927: CONVERT DATABASE operation cannot proceed

Cause: An error occurred earlier during CONVERT DATABASE operation.

Action: Retry CONVERT DATABASE command.

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-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-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-19941: invalid blocksize in cross platform datafile string

Cause: Blocksize in header of datafile copy being converted at target was invalid. Either datafile has not been made read/write with compatibility 10.0 or greater at source database or datafile copy is corrupted.

Action: Make a new datafile copy taken after tablespace has been made read/write with compatibility 10.0 at source database and retry conversion.

ORA-19942: datafile copy string not created with compatibility 10.0 or greater

Cause: The specified datafile copy to be converted at the target was not produced after making the tablespace in read/write mode with compatibility 10.0 or greater at the source database.

Action: Make a new datafile copy taken after tablespace has been made read/write with compatibility 10.0 at source database and retry conversion.

ORA-19943: The current database incarnation changed during backup

Cause: The backup failed because the current database incarnation was changed during the backup. One of the following events caused this incarnation change:

- The database was opened using ALTER DATABASE OPEN RESETLOGS statement.

- RMAN command RESET DATABASE TO INCARNATION was issued.

- If this happened on physical standby database, then redo apply has applied redo data from a new database incarnation.

Action: Re-try the backup.

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.

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-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-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-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-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-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-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-19960: Internal use only

Cause: NID usage

Action: None

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-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-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.