Oracle Comandos Sql

Modificar Formato de Fecha

2016-11-01T11:28:00.000-07:00

Como modificar el formato de la fecha en la sessión actual.

alter session set nls_date_format ='dd/mm/yyyy hh24:mi:ss';

Alter session set nls_date_format='dd/mm/yy hh:mi:ss';

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

2016-11-01T11:25:00.000-07:00

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.

ORA Error . Listado Errores Oracle. ORA-19851 a ORA-19921

2016-11-01T11:24:00.000-07:00

ORA-19851: OS error while managing auxiliary database string

Cause: An OS error was received while managing the automatic auxiliary instance.

Action: Check the accompanying errors.

ORA-19852: error creating services for auxiliary instance string (error string)

Cause: An error was received while managing the services of the auxiliary instance.

Action: Check the accompanying errors.

ORA-19853: error preparing auxiliary instance string (error string)

Cause: An error was received while managing the automatic auxiliary instance.

Action: Check the accompanying errors.

ORA-19854: error obtaining connect string from target

Cause: Could not obtain the connect string from the target database

Action: Check the accompanying errors.

ORA-19860: piece validation cannot be performed more than once

Cause: The user attempted to validate a list of backup pieces more than once. Validation may only be performed once for a given validation conversation.

Action: Do not attempt to validate the pieces more than once.

ORA-19861: additional backup pieces cannot be validated in this conversation

Cause: The user tried to add new pieces to the list of files being validated after the validation had already been performed. In a validation conversation, the list can only be validated once.

Action: Add all the backup pieces to the list before validating, or start a new validation conversation for the remaining pieces.

ORA-19862: backup pieces must be validated before accessing results

Cause: The user tried to get validation results for backup pieces before the pieces were actually validated.

Action: Validate the pieces before trying to access the results.

ORA-19863: device block size string is larger than max allowed: string

Cause: The user specified a device BLKSIZE that is larger than the device BLKSIZE specified during compressed backup.

Action: Change the device BLKSIZE to be smaller than the maximum allowed.

ORA-19865: Backup piece string has no data

Cause: No data was returned for the specified backup piece.

Action: This normally indicates a problem with the media management software which is linked with Oracle to provide backup and restore services. Contact the media management software vendor.

ORA-19866: error writing file header for datafile string

Cause: During a block recovery, the header of the datafile could not be updated.

Action: Contact Oracle Support Services.

ORA-19870: error while restoring backup piece string

Cause: This error should be followed by other errors indicating the cause of the problem.

Action: See other errors actions.

ORA-19873: cannot apply this backup section to file string

Cause: RMAN cannot restore a multi-section backup to the indicated file, because this section is not a backup of this file, or the file was not prepared correctly for this restore.

Action: If this error occurs while running RMAN, then it is an internal error and you should contact Oracle support.

ORA-19874: cannot finish multi-section restore to file string

Cause: During a multi-section restore, the file being restored is not a file in which a multi-section restore is in progress.

Action: If this error occurs while running RMAN, then it is an internal error and you should contact Oracle support.

ORA-19875: multi-section restore not complete for file string

Cause: While completing a multi-section restore, it was found that all required sections for this file were not correctly applied.

Action: If this error occurs while running RMAN, then it is an internal error and you should contact Oracle support.

ORA-19880: Corrupted space header for datafile string, block string

Cause: When reading the space header block to use Unused Block Optimization for the backup of the datafile, the space header block had corrupted information.

Action: The corrupt space header must be fixed before Unused Block Optimization can be used for this file. Note that you should fix the corruption in any case because it will affect the availability of the data in the file, beyond just taking backups.

ORA-19881: Corrupted space bitmap for datafile string, block string

Cause: When reading a space bitmap block to use Unused Block Optimization for the backup of the datafile, the space bitmap block had corrupted information.

Action: The corrupt space bitmap must be fixed before Unused Block Optimization can be used for this file. Note that you should fix the corruption in any case because it will affect the availability of the data in the file, beyond just taking backups.

ORA-19882: datafile string checkpoint string is ahead of space bitmap datafile string checkpoint string

Cause: When checkpointing the datafile containing the space bitmaps for the datafile being backed up in order to use Unused Block Optimization, the checkpoint of the datafile containing the space bitmaps did not advance.

Action: Examine the trace and alert files for possible causes. Fix underlying problem to use Unused Block Optimization for datafile's backup.

ORA-19883: Unused Block Optimization stopped for datafile string

Cause: Accompanying errors detail the problem that prevented Unused Block Optimization from being used.

Action: See accompanying errors for appropiate action.

ORA-19900: RESETLOGS must be specified after recovery to new incarnation

Cause: Recovery was done to an incarnation after changing the destination incarnation using RMAN's RESET DATABASE command.

Action: Open the database with the RESETLOGS option.

ORA-19901: database needs more recovery to create new incarnation

Cause: Recovery was done to an incarnation after changing the destination incarnation using RMAN's RESET DATABASE command, but one or more of the recovered datafiles still belongs to the parent incarnation. This usually happens when recovery is ended before any logs from the desired incarnation have been applied.

Action: Continue recovery.

ORA-19902: incarnation key string not found

Cause: The specified incarnation was not found in the control file.

Action: Resubmit request with known incarnation key. To see which incarnations are available for this target database, query V$DATABASE_INCARNATION or use RMAN's LIST INCARNATION command.

ORA-19903: test recovery not allowed when recovering to new incarnation

Cause: Either a new incarnation was set using RMAN's RESET DATABASE command for a control file that was CURRENT, or the control file is from a prior incarnation. As recovery to a new incarnation requires changing the control file, test recovery is not allowed.

Action: Perform actual recovery or RESET DATABASE to incarnation that was last opened using the control file to do test recovery.

ORA-19904: test recovery not allowed for datafile string

Cause: The specified datafile has been restored from a backup that was taken before the last RESETLOGS. Recovering this datafile will require a file header update that is incompatible with test recovery.

Action: Perform actual recovery.

ORA-19905: log_archive_format must contain %s, %t and %r

Cause: log_archive_format is missing a mandatory format element. Starting with Oracle 10i, archived log file names must contain each of the elements %s(sequence), %t(thread), and %r(RESETLOGS ID) to ensure that all archived log file names are unique.

Action: Add the missing format elements to log_archive_format.

ORA-19906: recovery target incarnation changed during recovery

Cause: While a media recovery was active, a new incarnation was detected by the server due to inspection or cataloging of archived logs or backup files.

Action: If you want recovery to use the new incarnation, restart recovery. This is the most common action on a standby database when RESETLOGS is done in primary. If you do not want recovery to use the new incarnation, change the recovery destination using RMAN's RESET DATABASE TO INCARNATION <incarnation#> command. To see which incarnations are available for this target database, query V$DATABASE_INCARNATION or use RMAN's LIST INCARNATION command.

ORA-19907: recovery time or SCN does not belong to recovered incarnation

Cause: A point-in-time recovery to an SCN or time stamp prior to the last RESETLOGS was requested.

Action: Either change the specified recovery time/SCN, or change the recovery destination using RMAN's RESET DATABASE command.

ORA-19908: datafile string has invalid checkpoint

Cause: The specified datafile has an invalid checkpoint.

Action: Restore the datafile from a backup.

ORA-19909: datafile string belongs to an orphan incarnation

Cause: Either the specified datafile was restored from a backup that was taken during a period of time that has already been discarded by a RESETLOGS operation, or Oracle cannot identify which database incarnation the file belongs to. The alert log contains more information.

Action: Restore a backup of this file that belongs to either the current or a prior incarnation of the database. If you are using RMAN to restore, RMAN will automatically select a correct backup.

ORA-19910: can not change recovery target incarnation in control file

Cause: The RESET DATABASE TO INCARNATION command was used while the database is open. This is not allowed.

Action: Close the database then re-issue the command.

ORA-19911: datafile string contains future changes at the incarnation boundary

Cause: The file did not hit end backup marker redo during recovery at the incarnation boundary, hence may contain changes discarded by new incarnation.

Action: Use older backup of the file and then re-issue the command.

ORA-19912: cannot recover to target incarnation string

Cause: The control file is not in the recovery path of the target incarnation, and does not contain enough information as to how to recover to the target incarnation.

Action: Restore the latest control file from the target incarnation and retry.

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.

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-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-19916: string

Cause: An error occurred when processing user request.

Action: Do not use message 19917; it is used internally for testing purpose. Do not use message 19918; it is an internal event used by encryption.

ORA-19919: encrypted backups to tertiary storage require Oracle Secure Backup

Cause: RMAN was configured to create encrypted backups, but the channel is neither a DISK channel nor an Oracle Secure Backup channel.

Action: Allocate a DISK channel or an Oracle Secure Backup channel to use backup encryption.

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 Error . Listado Errores Oracle. ORA-19769 a ORA-19831

2016-11-01T11:22:00.003-07:00

ORA-19769: missing FILE keyword

Cause: Syntax error.

Action: Use the correct syntax: ENABLE/DISABLE BLOCK CHANGE TRACKING

ORA-19770: invalid change tracking file name

Cause: The USING clause was specified with ALTER DATABASE ENABLE BLOCK CHANGE TRACKING, but no file name was given.

Action: Specify the change tracking file name, or omit the USING clause to allow Oracle to create a default name for the change tracking file.

ORA-19771: cannot rename change tracking file while database is open

Cause: The ALTER DATABASE RENAME FILE command was used to rename the change tracking file, and the database is open by one or more instances. The database must be mounted, and not open, to rename the change tracking file.

Action: Close the database and reissue the command.

ORA-19772: change tracking file name exceeds limit of string characters

Cause: The name specified for the change tracking file is too long.

Action: Specify a shorter change tracking file name.

ORA-19773: must specify change tracking file name

Cause: No file name was specified with the ALTER DATABASE ENABLE CHANGE TRACKING command, and the DB_CREATE_FILE_DEST parameter was not set.

Action: Either specify a file name, or set the DB_CREATE_FILE_DEST parameter.

ORA-19776: PROXY restore to ASM disk group "string" is not supported.

Cause: An attempt was made to proxy restore a file to ASM disk group using RMAN command. This is not supported.

Action: Use a different file name and reissue RMAN command.

ORA-19777: ASM file string cannot be proxy backed up.

Cause: An attempt was made to proxy backup a ASM file. This is not supported.

Action: Use a different file name and reissue RMAN command.

ORA-19779: could not obtain resilvering status for change tracking file

Cause: An error occurred while obtaining the mirror resilvering status of the change tracking file.

Action: Refer to other error messages shown for additional details of the problem.

ORA-19800: Unable to initialize Oracle Managed Destination

Cause: The name given for an Oracle managed files destination cannot be initialized.

Action: , if possible, and retry the command or use a different name for destination.

ORA-19801: initialization parameter DB_RECOVERY_FILE_DEST is not set

Cause: An attempt was made to create a file in DB_RECOVERY_FILE_DEST when DB_RECOVERY_FILE_DEST was not set. There are number of possible causes of this error, including: 1) A LOG_ARCHIVE_DEST_n parameter was specified using a LOCATION attribute whose value was DB_RECOVERY_FILE_DEST and an archived log file creation was attempted. 2) STANDBY_ARCHIVE_DEST parameter was specified using a LOCATION attribute whose value was DB_RECOVERY_FILE_DEST and an archived log file creation was attempted.

Action: Specify a valid destination for DB_RECOVERY_FILE_DEST in initialization parameter file or with the ALTER SYSTEM SET command.

ORA-19802: cannot use DB_RECOVERY_FILE_DEST without DB_RECOVERY_FILE_DEST_SIZE

Cause: There are two possible cause for this error: 1) The DB_RECOVERY_FILE_DEST parameter was in use when no DB_RECOVERY_FILE_DEST_SIZE parameter was encountered while fetching initialization parameter. 2) An attempt was made to set DB_RECOVERY_FILE_DEST with the ALTER SYSTEM command when no DB_RECOVERY_FILE_DEST_SIZE was in use.

Action: Correct the dependency parameter definitions and retry the command.

ORA-19803: Parameter DB_RECOVERY_FILE_DEST_SIZE is out of range (1 - string)

Cause: Parameter DB_RECOVERY_FILE_DEST_SIZE specified was not valid.

Action: Specify a valid number within the range.

ORA-19804: cannot reclaim string bytes disk space from string limit

Cause: Oracle cannot reclaim disk space of specified bytes from the DB_RECOVERY_FILE_DEST_SIZE limit.

Action: There are five possible solutions: 1) Take frequent backup of recovery area using RMAN. 2) Consider changing RMAN retention policy. 3) Consider changing RMAN archived log deletion policy. 4) Add disk space and increase DB_RECOVERY_FILE_DEST_SIZE. 5) Delete files from recovery area using RMAN.

ORA-19805: RECID string of string was deleted to reclaim disk space

Cause: The file described by the record in control file was deleted in order to reclaim disk space from flash recovery area for other operations.

Action: Wait and try again.

ORA-19806: cannot make duplex backups in recovery area

Cause: Duplex backup to recovery area is not supported.

Action: Remove duplex option and try again.

ORA-19808: recovery destination parameter mismatch

Cause: The value of parameters DB_RECOVERY_FILE_DEST and DB_RECOVERY_FILE_DEST_SIZE must be same in all instances. instance. All databases must have same recovery destination parameters.

Action: Check DB_RECOVERY_FILE_DEST and DB_RECOVERY_FILE_DEST_SIZE values in all instances.

ORA-19809: limit exceeded for recovery files

Cause: The limit for recovery files specified by the DB_RECOVERY_FILE_DEST_SIZE was exceeded.

Action: The error is accompanied by 19804. See message 19804 for further details.

ORA-19810: Cannot create temporary control file string in DB_RECOVERY_FILE_DEST

Cause: An attempt was made to create a control file for a temporary purpose in DB_RECOVERY_FILE_DEST.

Action: Retry the operation with a new file name.

ORA-19811: cannot have files in DB_RECOVERY_FILE_DEST with keep attributes

Cause: An attempt was made to 1) Create a backup piece or image copy in the recovery area with KEEP option. 2) Update the KEEP attributes of an existing backup piece or image copy in the recovery area.

Action: Reissue RMAN command without KEEP options.

ORA-19812: cannot use string without DB_RECOVERY_FILE_DEST

Cause: There are three possible cause for this error: 1) The indicated parameter was in use when no DB_RECOVERY_FILE_DEST parameter was encountered while fetching the initialization parameter. 2) An attempt was made to set indicated the parameter with the ALTER SYSTEM command when no DB_RECOVERY_FILE_DEST was in use. 3) An attempt was made to clear DB_RECOVERY_FILE_DEST with the ALTER SYSTEM command when the indicated parameter was in use.

Action: Eliminate any incompatible parameter definitions.

ORA-19813: cannot have unavailable file string in DB_RECOVERY_FILE_DEST

Cause: An attempt was made to change a backup piece or image copy in recovery area to UNAVAILABLE.

Action: Correct and resubmit the RMAN command. Do not use messages 19814; it is used for simulating crash.

ORA-19815: WARNING: string of string bytes is string% used, and has string remaining bytes available.

Cause: DB_RECOVERY_FILE_DEST is running out of disk space.

Action: One of the following:

1. Add disk space and increase DB_RECOVERY_FILE_DEST_SIZE.

2. Backup files to tertiary device using RMAN.

3. Consider changing RMAN retention policy.

4. Consider changing RMAN archived log deletion policy.

5. Delete files from recovery area using RMAN.

ORA-19816: WARNING: Files may exist in string that are not known to database.

Cause: One of the following events caused this:

1. A database crash happened during file creation.

2. A backup control file was restored.

3. The control file was re-created.

4. DB_RECOVERY_FILE_DEST has previously been enabled and then disabled.

Action: Use RMAN command CATALOG RECOVERY AREA to re-catalog any such files. If the file header is corrupted, then delete those files using an OS utility. Do not use messages 19817; it is used for simulating lock failure Do not use messages 19818; it is used for space reclamation before backup Do not use messages 19819; it is used to disable clearing file name

ORA-19830: error from target database: string

Cause: This error should be followed by other errors indicating the cause of the problem.

Action: No action required.

ORA-19831: incompatible string.string.string.string DBMS_BACKUP_RESTORE package: string.string.string.string required

Cause: This version of database was incompatible with the the indicated DBMS_BACKUP_RESTORE package installed in the database.

Action: If the database has been upgraded from an earlier version, ensure that the catxxxx.sql script has been run successfully. Re-install dbmsbkrs.sql and prvtbkrs.plb if necessary.

shrink space - reducir espacio tabla o index

2015-04-07T10:20:00.000-07:00

Con la clausula shrink del comando alter table o alter index se puede compactar el espacio del objeto para que ocupe
solamente el espacio necesario, segun los datos que tiene dicho objeto.

Recordar que una tabla puede tomar espacio cuando le agregamos filas pero si luego eliminamos estas filas la tabla no reduce la ocupación automaticamente.

lo ejecutamos de la siguiente manera:

Habilitamos para que se puedan mover filas de la tabla.

SQL> alter table (nombre de tabla) enable row movement;

Ejecutamos el shrink para que la tabla ocupe solo el espacio que necesita (según los datos que tiene)

SQL> alter table (nombre de tabla) shrink space;

Este comando ejecutarlo en momentos que no se este accediendo a la tabla, ya que baja considerablemente la performance de la misma.

Ver Objetos Bloqueados

2015-03-04T07:50:00.001-08:00

Con la siguiente consulta vemos los objetos bloqueados y que usuario los tiene.

Ejecutar la consulta con el usuario "system"

select a.session_id,a.oracle_username, a.os_user_name, b.owner "OBJECT OWNER", b.object_name,b.object_type,a.locked_mode from
(select object_id, SESSION_ID, ORACLE_USERNAME, OS_USER_NAME, LOCKED_MODE from v$locked_object) a,
(select object_id, owner, object_name,object_type from dba_objects) b
where a.object_id=b.object_id

y con la siguiente consulta vemos las sessiones que tienen bloqueados objetos:

SELECT l.session_id||','||v.serial# sid_serial,
l.ORACLE_USERNAME ora_user,
o.object_name,
o.object_type,
DECODE(l.locked_mode,
0, 'None',
1, 'Null',
2, 'Row-S (SS)',
3, 'Row-X (SX)',
4, 'Share',
5, 'S/Row-X (SSX)',
6, 'Exclusive',
TO_CHAR(l.locked_mode)
) lock_mode,
o.status,
to_char(o.last_ddl_time,'dd.mm.yy') last_ddl
FROM dba_objects o, gv$locked_object l, v$session v
WHERE o.object_id = l.object_id
and l.SESSION_ID=v.sid
order by 2,3;

con los datos que nos arroja podemos realizar un kill seesion.

ORA Error . Listado Errores Oracle. ORA-19640 a ORA-19768

2013-06-17T13:01:00.000-07:00

ORA-19640: datafile checkpoint is SCN string time string

Cause: This message identifies the datafile checkpoint for a datafile that was too old to take an incremental backup from, or the target of an incremental restore that could not be applied.

Action: See other error message.

ORA-19641: backup datafile checkpoint is SCN string time string

Cause: This message identifies the checkpoint of a datafile in an incremental backup set that could not be applied.

Action: See other error message.

ORA-19642: start SCN of incremental backup is string

Cause: This message identifies the starting SCN of an incremental backup that could not be applied.

Action: See other error message.

ORA-19643: datafile string: incremental-start SCN is too recent

Cause: The incremental-start SCN which was specified when starting an incremental datafile backup is greater than the datafile checkpoint SCN, which could cause some blocks to be missed.

Action: Specify a smaller incremental-start SCN.

ORA-19644: datafile string: incremental-start SCN is prior to RESETLOGS SCN string

Cause: The incremental-start SCN which was specified when starting an incremental datafile backup is less than the RESETLOGS SCN.

Action: Specify a larger incremental-start SCN.

ORA-19645: datafile string: incremental-start SCN is prior to creation SCN string

Cause: The incremental-start SCN which was specified when starting an incremental datafile backup is less than the datafile's creation SCN.

Action: Specify a larger incremental-start SCN.

ORA-19646: cannot change size of datafile string from string to string

Cause: Restore needs to adjust the size of the file as indicated, but the file size adjustment failed.

Action: Examine the other messages which should be present to indicate the cause of the failure.

ORA-19647: non-zero LEVEL cannot be specified when INCREMENTAL is FALSE

Cause: BACKUPSETDATAFILE was called with a non-zero backup_level and a FALSE incremental indication.

Action: Either set incremental to TRUE or change backup_level to zero.

ORA-19648: datafile string: incremental-start SCN equals checkpoint SCN

Cause: The incremental-start SCN which was specified when starting an incremental datafile backup is equal to the datafile's checkpoint SCN. Since an incremental backup can only be applied to a datafile whose checkpoint SCN is between the backup set incremental-start SCN (inclusive) and the backup set checkpoint SCN (exclusive), there is no datafile that this backup set could ever be applied to.

Action: Specify a smaller incremental-start SCN. NOTE that this message will usually only be encountered by the user while taking an incremental backup with Recovery Manager. Recovery Manager should intercept all usual cases of this error and simply ignore the incremental backup for this file. So, if you do encounter this error, please report it to Oracle Support.

ORA-19649: offline-range record RECID string STAMP string not found in file string

Cause: APPLYOFFLINERANGE was called with a RECID/STAMP which was not found in the indicated control file. This probably means that the specified control file is no longer the same control file that Recovery Manager thinks it is.

Action: Specify the RECID/STAMP of a record that exists in the control file copy.

ORA-19650: Offline-range record RECID string STAMP string in file string has SCN string

Cause: This messages identifies the offline-clean SCN from the indicated offline-range record in the indicated file.

Action: See other error message.

ORA-19651: cannot apply offline-range record to datafile string: SCN mismatch

Cause: APPLYOFFLINERANGE cannot apply an offline-range record to a target datafile unless the datafile's checkpoint SCN exactly matches the offline-clean SCN in the specified offline-range record.

Action: Specify an offline-range record whose offline-clean SCN matches the target datafile's checkpoint.

ORA-19652: cannot apply offline-range record to datafile string: file is fuzzy

Cause: The target datafile for an APPLYOFFLINERANGE call is fuzzy.

Action: Specify a target datafile that is closed cleanly.

ORA-19653: cannot switch to older file incarnation

Cause: SWITCHTOCOPY was called with a datafile copy for a datafile that was dropped prior to the time this control file was backed up.

Action: Restore and mount an earlier control file. It is acceptable to use a control file that was backed up prior to the creation of the specified datafile.

ORA-19654: must use backup control file to switch file incarnations

Cause: This SWITCHTOCOPY operation is attempting to switch incarnations of a datafile, but the currently mounted control file is not a backup control file.

Action: Restore and mount a backup control file.

ORA-19655: cannot switch to incarnation with different RESETLOGS data

Cause: This SWITCHTOCOPY operation is attempting to switch to a datafile which comes from a different RESETLOGS version of the database.

Action: Either restore a backup control file that was taken from the same database version as the target datafile copy, or switch to a different datafile copy.

ORA-19656: cannot backup, copy, or delete online log string

Cause: The indicated log file is an active log. You can only backup, copy, or delete archived logs.

Action: The indicated log file cannot be processed - select another file.

ORA-19657: cannot inspect current datafile string

Cause: The file being inspected is already part of the currently mounted database.

Action: None - the file is already part of the database.

ORA-19658: cannot inspect string - file is from different RESETLOGS

Cause: The RESETLOGS data in the log file being inspected does not match that in the currently mounted control file.

Action: The indicated file cannot be processed - inspect another file.

ORA-19659: incremental restore would advance file string past RESETLOGS

Cause: This incremental backup cannot be applied to the specified datafile, because the datafile is from an earlier incarnation of the database, and its checkpoint would be advanced too far to be recoverable in the current incarnation of the database.

Action: This incremental cannot be applied to this datafile. If you wish to recover the file to the RESETLOGS SCN so that the database can be opened with the RESETLOGS option, then you must use redo-log recovery, not incremental restore, to continue recovering this file.

ORA-19660: some files in the backup set could not be verified

Cause: A restore conversation was made to verify all the files in a backup set, and the files which were printed in messages 19661 or 19662 could not be verified because corrupt blocks for those files were found in the backup set.

Action: Unless the damage to the backup set can be repaired, the indicated files cannot be restored from this backup set.

ORA-19661: datafile string could not be verified

Cause: Some data blocks for the indicated datafile were corrupt in the backup set.

Action: Unless the damage to the backup set can be repaired, the indicated datafile cannot be restored from this backup set.

ORA-19662: archived log thread string sequence string could not be verified

Cause: Some data blocks for the indicated archived log were corrupt in the backup set.

Action: Unless the damage to the backup set can be repaired, the indicated archived log cannot be restored from this backup set.

ORA-19663: cannot apply current offline range to datafile string

Cause: An attempt was made to apply the current offline range to the specified datafile, but the datafile is either not current enough or is not at the correct SCN to apply the offline range.

Action: The datafile remains unchanged.

ORA-19664: file type: string, file name: string

Cause: This message is issued to identify the file which is the subject of an error.

Action: None - this is an informational message. There should be other Oracle messages explaining the cause of the error.

ORA-19665: size string in file header does not match actual file size of string

Cause: The size of the file as indicated in the file header does not match the true size of the file. The two differing sizes are shown in units of logical blocks.

Action: This file is not usable - it has most likely been truncated.

ORA-19666: cannot do incremental restore of the control file

Cause: The control file was included in an incremental restore conversation

Action: If you wish to restore the control file, you must do a full restore of the control file

ORA-19667: cannot do incremental restore of datafile string

Cause: The backup of the datafile is a full backup

Action: If you wish to restore the datafile, you must do a full restore of the datafile

ORA-19668: cannot do full restore of datafile string

Cause: The backup of the datafile is an incremental backup

Action: If you wish to restore the datafile, you must do an incremental restore of the datafile

ORA-19669: proxy copy functions cannot be run on DISK channel

Cause: A proxy copy procedure was called, but the device which is allocated to the current session has type DISK.

Action: Allocate a non-DISK channel and retry the operation. Note that proxy copy requires a 3rd-party media management software product that supports the this backup/restore feature.

ORA-19670: file string already being restored

Cause: A proxy restore function has already named this file as a restore destination.

Action: Use a different file name. If this message occurs during a recovery manager job, then this is an internal error in recovery manager, and you should contact Oracle support.

ORA-19671: media management software returned invalid proxy handle

Cause: During a proxy backup or restore, the media management software returned an invalid file handle.

Action: This is an internal error in the media management software which is linked with Oracle to provide backup/restore services. Contact the media management software vendor.

ORA-19672: media management software returned invalid file status

Cause: During a proxy backup or restore, the media management software returned an invalid file status.

Action: This is an internal error in the media management software which is linked with Oracle to provide backup/restore services. Contact the media management software vendor.

ORA-19673: error during proxy copy of file string

Cause: During a proxy backup or restore, an error occurred while copying this file, but other files may have been copied successfully.

Action: There should be other errors on the error stack which explain why the file could not be successfully copied.

ORA-19674: file string is already being backed up with proxy copy

Cause: Recovery manager attempted to back up the specified file with proxy copy, but the file is already being backed up by another recovery manager job.

Action: Wait until the other recovery manager backup of this file is complete, then retry the backup.

ORA-19675: file string was modified during proxy copy

Cause: A proxy backup of the specified file failed because the file was brought on-line or otherwise modified while the proxy backup was in progress. This file was off-line or read-only when the backup began, so the file was not put into hot-backup mode, therefore no modifications are permitted while the backup is in progress.

Action: Take another backup of this file.

ORA-19676: one or more files failed during proxy backup or restore

Cause: During a proxy backup or restore, errors were encountered while processing some files. The files for which no error messages are shown were processed successfully.

Action: Examine the messages regarding the specific files to determine the cause of the problems.

ORA-19677: RMAN configuration name exceeds maximum length of string

Cause: The configuration name string exceeds maximum length.

Action: Supply a correct configuration name and retry the function.

ORA-19678: RMAN configuration value exceeds maximum length of string

Cause: The configuration value string exceeds maximum length.

Action: Supply a correct configuration value and retry the operation.

ORA-19679: RMAN configuration number string is outside valid range of 1 through string

Cause: An invalid RMAN Configuration number was specified.

Action: Specify a correct datafile number and retry the operation.

ORA-19680: some blocks not recovered. See trace file for details

Cause: Some blocks are not recovered during block media recovery.

Action: See trace files for details of the problem.

ORA-19681: block media recovery on control file not possible

Cause: file number 0 specified in block media recovery

Action: check file number

ORA-19682: file string not in block media recovery context

Cause: Internal error

Action: None

ORA-19683: real and backup block size of file string are unequal

Cause: block size changed between backup & real file

Action: use right backup

ORA-19684: block media recovery failed because database is suspended

Cause: Database is suspended, probably by an ALTER SYSTEM SUSPEND statement

Action: Execute ALTER SYSTEM RESUME then retry block media recovery

ORA-19685: SPFILE could not be verified

Cause: Some data blocks for the SPFILE were corrupt in the backup set.

Action: Unless the damage to the backup set can be repaired, the SPFILE cannot be restored from this backup set.

ORA-19686: SPFILE not restored due to string

Cause: The indicated file could not be restored, because some of its data blocks were not found in the backup piece.

Action: Unless the damage to the backup set can be repaired, the SPFILE cannot be restored from this backup set.

ORA-19687: SPFILE not found in backup set

Cause: The SPFILE could not be restored, because it is not in this backup set.

Action: This message is issued when the directory from the first backup piece is read and one or more files named for restoration were not found in the piece. You must supply the first backup piece of a backup set that contains the requested file.

ORA-19688: control file AUTOBACKUP format(string) for string does not have %F

Cause: control file AUTOBACKUP format must contain %F for the device.

Action: Change control file format using RMAN command CONFIGURE CONTROLFILE BACKUP FORMAT FOR DEVICE TYPE <type> TO <format>.

ORA-19689: cannot have more than one %F in control file AUTOBACKUP format(string) for string

Cause: control file AUTOBACKUP format contains more than one %F for the device.

Action: Change control file format using RMAN command CONFIGURE CONTROLFILE BACKUP FORMAT FOR DEVICE TYPE <type> TO <format>.

ORA-19690: backup piece release string incompatible with Oracle release string

Cause: The backup piece was created by incompatible software.

Action: Either restart with a compatible software release or create another backup using the current release.

ORA-19691: string is from different database: id=string, name=string

Cause: The database name or database id in backup piece header does not match the one in control file.

Action: Supply the correct backup piece belonging to this database.

ORA-19692: missing creation stamp on piece string

Cause: The backup piece doesn't have information about creation stamp.

Action: Supply another backup piece which is created by oracle 9i or later version.

ORA-19693: backup piece string already included

Cause: This backup piece was already specified for inclusion in the restore conversation. A restore conversation may process only a single instance of a backup piece.

Action: Remove the specified duplicate backup piece in restore steps and restart the conversation.

ORA-19694: some changed blocks were not found in the change tracking file

Cause: A backup or copy found that some changed blocks had not been recorded in the change tracking file. The details of which files and blocks are affected will be in an Oracle trace file.

Action: This indicates that there is a problem with the change tracking feature. Disable change tracking and re-start the backup.

ORA-19695: fixed table X$KRBMSFT has not been populated

Cause: This is an internal error. The fixed table X$KRBMAFT was not populated using the function DBMS_BACKUP_RESTORE.SEARCHFILES.

Action: Internal error - contact Oracle Customer Support.

ORA-19696: control file not found in backup set

Cause: The control file could not be restored because it is not in this backup set.

ORA-19697: standby control file not found in backup set

Cause: The standby control file could not be restored because it is not in this backup set.

ORA-19698: string is from different database: id=string, db_name=string

Cause: Catalog failed because the database id in file header does not match the one in control file.

Action: Supply the correct file belonging to this database.

ORA-19699: cannot make copies with compression enabled

Cause: Datafile copies with compression are not supported.

Action: If the function DBMS_BACKUP_RESTORE.BACKUPPIECECREATE is called outside RMAN, then the incompatible values are being passed for the parameters DOCOMPRESS and IMAGCP. If this message occurs during an RMAN job, then this is an internal error in RMAN, and you should contact Oracle support.

ORA-19700: device type exceeds maximum length of string

Cause: The device type indicated is invalid.

Action: Supply a correct device type and retry the allocation.

ORA-19701: device name exceeds maximum length of string

Cause: The device name indicated is invalid.

Action: Supply a correct device name and retry the allocation.

ORA-19703: device command string exceeds maximum length of string

Cause: The device command string exceeds maximum length.

Action: Correct the command and retry the operation.

ORA-19704: file name exceeds maximum length of string

Cause: The specified file name, which was a parameter to a copy, backup, or restore operation, exceeds the maximum file name length for this operating system.

Action: Retry the operation with a shorter file name.

ORA-19705: tag value exceeds maximum length of string characters

Cause: During a backup or copy operation, the user supplied a tag value too long to fit in the file header.

Action: Supply a shorter tag and retry the operation.

ORA-19706: invalid SCN

Cause: The input SCN is either not a positive integer or too large.

Action: Check the input SCN and make sure it is a valid SCN.

ORA-19707: invalid record block number - string

Cause: The input number is either negative or too large.

Action: Check the input record block number and make sure it is a valid number clauses in the create database statement.

ORA-19708: log destination exceeds maximum length of string characters

Cause: When starting a restore conversation, the user specified a log restore destination longer than the port-specific maximum.

Action: Supply a shorter destination and retry the operation.

ORA-19709: numeric parameter must be non-negative integer

Cause: A numeric parameter to an DBMS_BACKUP_RESTORE procedure is negative or contains a fractional portion.

Action: Supply a valid numeric parameter.

ORA-19710: unsupported character set string

Cause: When the target database is not mounted, RMAN sets the target database character set to the value specified in the users environment.

Action: Specify a valid character set in the environment. This is usually done via the NLS_LANG environment variable.

ORA-19711: cannot use RENORMALIZEALLFILENAMES while database is open

Cause: An attempt was made to re-normalize all the file names in the control file while the database is open.

Action: Close the database before using the RENORMALIZEALLFILENAMES procedure.

ORA-19712: table name exceeds maximum length of string

Cause: The table name string exceeds maximum length.

Action: Retry the operation with a shorter table name.

ORA-19713: invalid copy number: string

Cause: The copy number is not in a valid range or you have reached maximum limit.

Action: Report the error and other information to support.

ORA-19714: length for generated name longer than string

Cause: The specified format exceeds the maximum length for the piece name.

Action: Change the format to create shorter piece names.

ORA-19715: invalid format string for generated name

Cause: A restricted format or undefined format was used incorrectly.

Action: Change the format specified in the additional information by removing the restricted format.

ORA-19716: error processing format string to generate name for backup

Cause: There were errors while processing the format to generate name for backup.

Action: Change the format.

ORA-19717: for non-OMF search the pattern must be specified

Cause: The procedure DBMS_BACKUP_RESTORE.SEARCHFILES was called with an empty pattern while the parameter OMF was set to FALSE.

Action: Either specify the pattern or set the parameter OMF to TRUE.

ORA-19718: length for command id longer than string

Cause: The specified command id exceeds the maximum length for command id.

Action: Supply a shorter command id and retry the operation.

ORA-19719: length for operation name longer than string

Cause: The specified operation name exceeds the maximum length for operation name.

Action: Supply a shorter operation name and retry the operation.

ORA-19720: Error occurred when converting an OCI number into an SCN

Cause: This is most likely caused by an invalid SCN number that came from an external file, such as an export file.

Action: See other errors on the error stack to look for the source of the problem.

ORA-19721: Cannot find datafile with absolute file number string in tablespace string

Cause: Can not find one of the datafile that should be in the Pluggable Set.

Action: Make sure all datafiles are specified via import command line option or parameter files.

ORA-19722: datafile string is an incorrect version

Cause: The datafile is an incorrect version. It contains either less or more changes then the desired version.

Action: Make sure the right datafiles are transported. Make sure the datafile is copied while its tablespace is read only.

ORA-19723: Cannot recreate plugged in read-only datafile string

Cause: The datafile is plugged in read only. It can not recreated.

Action: Use ALTER DATABASE RENAME FILE command instead.

ORA-19724: snapshot too old: snapshot time is before file string plug-in time

Cause: The snapshot SCN is before the SCN at which the referred datafile is plugged into the database.

Action: retry the query.

ORA-19725: can not acquire plug-in enqueue

Cause: There maybe another "ALTER DATABASE RESET COMPATIBILITY" command issued concurrently, preventing this process from acquiring the plug-in enqueue.

Action: retry the operation.

ORA-19726: cannot plug data [string] at level string into database running at compatibility level string

Cause: Some of the data in the pluggable set requires a compatibility level higher than what is currently allowed by the database. The string in square bracket is the name of the compatibility type associated with the data.

Action: Raise the "compatible" init.ora parameter and retry the operation.

ORA-19727: cannot plug data [string] at level string into database running Oracle string

Cause: Some of the data in the pluggable set requires a compatibility level higher than the release level of the Oracle executable. The string in square bracket is the name of the compatibility type associated with the data.

Action: Upgrade Oracle and retry the operation.

ORA-19728: data object number conflict between table string and partition string in table string

Cause: The non-partitioned table has the same data object number as one of the partitions in the partitioned table. One can not exchange the table with the partition in this case.

Action: Use "alter table move partition" command to move the offending partition, so that the partition will get a new data object number. Retry the operation then.

ORA-19729: File string is not the initial version of the plugged in datafile

Cause: The file is not the initial version of the plugged in datafile.

Action: Use the correct initial version of the plugged in datafile.

ORA-19730: can not convert offline plugged-in datafile string

Cause: As part of making a tablespace read-write, we need to convert datafiles that are plugged in read-only. The file must be online.

Action: Online the datafile and retry the operation.

ORA-19731: cannot apply change to unverified plugged-in datafile string

Cause: Recovery was not able to verify the referred datafile according to information in the control file. Before encountering this change vector for this file, somehow recovery did not encounter the file conversion redo that is supposed to verify the file. This may happen due to corrupted or incorrect control file used for media recovery.

Action: Use the correct control file and continue recovery.

ORA-19732: incorrect number of datafiles for tablespace string

Cause: d by a user editing the export file.

Action: Use the correct export file and retry the operation.

ORA-19733: COMPATIBLE parameter needs to be string or greater

Cause: The COMPATIBLE initialization parameter is not high enough to allow the operation. Allowing the command would make the database incompatible with the release specified by the current COMPATIBLE parameter.

Action: Shutdown and startup with a higher compatibility setting.

ORA-19734: wrong creation SCN - control file expects converted plugged-in datafile

Cause: When a tablespace is plugged into a database, the tablespace is initially read-only. Oracle converts the header of the plugged-in datafiles (assign them a new creation SCN) when the tablespace is first made read-write. This error occurs when the creation SCN in the file header is different from the creation SCN in the control file, possibly because this is the initial version of plugged-in datafile.

Action: Either restore the converted datafile or continue recovering the datafile.

ORA-19735: wrong creation SCN - control file expects initial plugged-in datafile

Action: Either restore the initial version of the plugged-in datafile, or continue database recovery, which will recover the control file.

ORA-19736: can not plug a tablespace into a database using a different national character set

Cause: Oracle does not support plugging a tablespace into a database using a different national character set.

Action: Use import/export or unload/load to move data instead.

ORA-19738: cannot find language information for character set: 'string'

Cause: The compatibility check failed because a character set name that was provided is not valid.

Action: Correct the character set name and retry.

ORA-19740: text is longer than string

Cause: The specified text exceeds the maximum length for text.

Action: Supply a shorter text and retry the operation.

ORA-19750: change tracking file: 'string'

Cause: This message reports the name of a file involved in other messages.

Action: See associated error messages for a description of the problem.

ORA-19751: could not create the change tracking file

Cause: It was not possible to create the change tracking file.

Action: Check that there is sufficient disk space and no conflicts in file names and try to enable block change tracking again.

ORA-19752: block change tracking is already enabled

Cause: The ALTER DATABASE ENABLE BLOCK CHANGE TRACKING command was issued, but block change tracking is already turned on for this database.

Action: None, this is an informative message only.

ORA-19753: error writing to change tracking file

Cause: An I/O error occurred while writing to the change tracking file.

Action: There will be other messages on the error stack that show details of the problem.

ORA-19754: error reading from change tracking file

Cause: An I/O error occurred while reading from the change tracking file.

Action: There will be other messages on the error stack that show details of the problem.

ORA-19755: could not open change tracking file

Cause: The change tracking file could not be opened.

Action: There will be other messages on the error stack that show details of the problem.

ORA-19756: corrupt block number string found in change tracking file

Cause: The specified block number is corrupt in the change tracking file.

Action: There will be other messages on the error stack that show details of the problem. There will also be a trace file that contains a complete dump of the corrupt block.

ORA-19757: could not resize change tracking file to string blocks

Cause: An error occurred while trying to change the size of the change tracking file.

Action: There will be other messages on the error stack that show details of the problem.

ORA-19758: failed to enable/disable block change tracking: out of SGA memory

Cause: out of SGA memory

Action: Increase SGA and restart the instance.

ORA-19759: block change tracking is not enabled

Cause: A command was entered that requires block change tracking to be enabled, but block change tracking is not enabled.

Action: None, this is an informative message only.

ORA-19760: error starting change tracking

Cause: Change tracking is enabled, but a problem was encountered while enabling the change tracking subsystem in this instance. The alert log and the trace file from the CTWR process will contain more information about the error.

Action: Examine the trace and alert files. Correct the error if possible, otherwise disable change tracking.

ORA-19761: block size string is not valid for change tracking file

Cause: While opening the specified change tracking file, it was found that the file header did not contain a valid logical block size. This probably means that the file is corrupt.

Action: If the file can be repaired, do so, otherwise disable and re-enable change tracking to re-initialize the file.

ORA-19762: invalid file type string

Cause: An invalid file type was found in the change tracking file. Some other file was put in place of the change tracking file, or the file is corrupt.

Action: Disable then re-enable change tracking.

ORA-19763: compatibility version string is higher than maximum allowed: string

Cause: The compatibility version in the change tracking file is greater than what can be used by the current release of Oracle. This can happen when you upgrade, use change tracking with a new release, then downgrade.

Action: Disable then re-enable change tracking.

ORA-19764: database id string does not match database id string in control file

Cause: The change tracking file is not the correct one for this database. This can happen when the database ID for this database has been changed.

Action: Disable then re-enable change tracking.

ORA-19765: mount id string does not match mount id string in control file

Cause: d by having a change tracking file that cannot be consistently updated by all instances.

Action: In RAC, ensure that the name specified for the change tracking file truly represents the same disk location for all nodes in the cluster. Disable then re-enable change tracking.

ORA-19766: missing CHANGE keyword

Cause: Syntax error.

Action: Use the correct syntax: ENABLE/DISABLE BLOCK CHANGE TRACKING

ORA-19767: missing TRACKING keyword

Cause: Syntax error.

Action: Use the correct syntax: ENABLE/DISABLE BLOCK CHANGE TRACKING

ORA-19768: USING clause only valid with ENABLE CHANGE TRACKING

Cause: The USING clause was specified with DISABLE CHANGE TRACKING

Action: Correct the statement.

ORA Error . Listado Errores Oracle. ORA-19502 a ORA-19639

2013-06-17T12:56:00.000-07:00

ORA-19502: write error on file "string", block number string (block size=string)

Cause: write error on output file

Action: check the file

ORA-19503: cannot obtain information on device, name="string", type="string", parms="string"

Cause: call to get device information returned an error

Action: check device name, type and parameters

ORA-19504: failed to create file "string"

Cause: call to create file returned an error

Action: check additional messages, check access permissions

ORA-19505: failed to identify file "string"

Cause: call to identify the file returned an error

Action: check additional messages, and check if the file exists

ORA-19506: failed to create sequential file, name="string", parms="string"

Cause: call to create the sequential file returned an error

Action: check additional messages, check access permissions

ORA-19507: failed to retrieve sequential file, handle="string", parms="string"

Cause: call to retrieve the sequential file returned an error

Action: check additional messages, and check if the file exists

ORA-19508: failed to delete file "string"

Cause: call to delete the file returned an error

Action: check additional messages

ORA-19509: failed to delete sequential file, handle="string", parms="string"

Cause: call to delete the sequential file returned an error

Action: check additional messages

ORA-19510: failed to set size of string blocks for file "string" (block size=string)

Cause: call to resize the file returned an error

Action: check additional messages

ORA-19511: Error received from media manager layer, error text: string

Cause: An error occurred in the media management software which is linked with the Oracle server to perform backup and restore in cooperation with Recovery Manager.

Action: If the text of message 19511 does not provide enough information to resolve the problem, then you should contact the vendor of the media management software.

ORA-19512: file search failed

Cause: Recovery manager or Oracle Server attempted to discover files that matched the specified pattern but failed.

Action: Check errors on the error stack for an explanation why the search for files could not be successfully executed.

ORA-19513: failed to identify sequential file

Cause: Unable to identify the sequential file.

Action: Check additional messages, and check if the file exists on media.

ORA-19525: tempfile for the clone database must be renamed

Cause: Opening a clone database failed because Oracle server forces the tempfile to be renamed, in order to avoid overwriting the primary tempfile.

Action: Rename the tempfiles manually or automatically by using the DB_FILE_NAME_CONVERT initialization parameter.

ORA-19526: only one location allowed for parameter string

Cause: A list of default locations was provided in an Oracle-managed files parameter.

Action: Edit the parameter to include a single location.

ORA-19527: physical standby redo log must be renamed

Cause: The CLEAR LOGFILE command was used at a physical standby database. This command cannot be used at a physical standby database unless the LOG_FILE_NAME_CONVERT initialization parameter is set. This is required to avoid overwriting the primary database's log files.

Action: Set the LOG_FILE_NAME_CONVERT initialization parameter.

ORA-19528: redo logs being cleared may need access to files

Cause: The redo logs are being cleared. This procedure may need the files this operation is being applied to.

Action: Wait for the redo logs to be cleared.

ORA-19529: Pattern string in initialization parameter string has an Oracle Managed Files file name.

Cause: An attempt was made to convert a database file name to an Oracle Managed Files file name using DB_FILE_NAME_CONVERT or LOG_FILE_NAME_CONVERT initialization parameter. This was not a valid operation.

Action: Retry the operation with a pattern template instead of a full Oracle Managed Files file name.

ORA-19550: cannot use backup/restore functions while using dispatcher

Cause: Attempted to use backup/restore functions while connected to the dispatcher in a shared server. This is not allowed because the device that is used for backup and restore must remain allocated to a single process.

Action: Connect directly to the instance then re-execute the backup or restore function.

ORA-19551: device is busy, device type: string, device name: string

Cause: The indicated device could not be allocated because it is allocated to another session, or no device was named, or all devices of the requested type are busy.

Action: Either attempt to allocate another device or wait until the required device is no longer busy.

ORA-19552: device type string is invalid

Cause: The device type indicated is invalid.

Action: Supply a correct device type and retry the allocation.

ORA-19553: device name string is invalid

Cause: The device name indicated is invalid.

Action: Supply a correct device name and retry the allocation.

ORA-19554: error allocating device, device type: string, device name: string

Cause: The specified device could not be allocated.

Action: One or more other messages should be displayed to help pinpoint the cause of the error. Correct the error and retry the allocation.

ORA-19555: invalid LOG_ARCHIVE_MIN_SUCCEED_DEST parameter value

Cause: The value of parameter LOG_ARCHIVE_MIN_SUCCEED_DEST was not set within the valid range.

Action: Specify a correct value for parameter LOG_ARCHIVE_MIN_SUCCEED_DEST. If the archive log parameters LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST are in use, set parameter LOG_ARCHIVE_MIN_SUCCEED_DEST to either 1 or 2.

ORA-19556: required destination LOG_ARCHIVE_DUPLEX_DEST currently is deferred

Cause: The destination for parameter LOG_ARCHIVE_DUPLEX_DEST was deferred when it was required to be enabled. The destination was deferred automatically when an ALTER SYSTEM command for parameter LOG_ARCHIVE_DEST defined a destination which duplicated an existing LOG_ARCHIVE_DUPLEX_DEST parameter destination.

Action: Change the destination value for the LOG_ARCHIVE_DUPLEX_DEST parameter.

ORA-19557: device error, device type: string, device name: string

Cause: An error occurred in the platform-specific device code

Action: One or more other messages should be displayed to help pinpoint the cause of the error. Correct the error and retry the allocation.

ORA-19558: error de-allocating device

Cause: The specified device could not be de-allocated.

Action: One or more other messages should be displayed to help pinpoint the cause of the error. Correct the error and retry the allocation.

ORA-19559: error sending device command: string

Cause: An error occurred while sending the indicated command to the session device.

Action: One or more other messages should be displayed to help pinpoint the cause of the error. Correct the error and retry the allocation.

ORA-19560: string is not a valid device limit

Cause: An invalid type of device limit was specified in a call to DBMS_BACKUP_RESTORE.SETLIMIT.

Action: Use one of the documented limits: KBYTES, READRATE, or PARALLEL.

ORA-19561: string requires a DISK channel

Cause: The attempted command requires that a DISK device channel be allocated to the session, but a non-DISK device was found.

Action: Deallocate the current device and allocate a DISK channel, then then retry the command.

ORA-19562: file string is empty

Cause: The indicated file, which is an archived log, control file, or datafile was found to be empty during a copy, backup, or scan] operation.

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

ORA-19563: string header validation failed for file string

Cause: When opening the file to be placed in a copy or backup set, to be inspected, or used as the target for an incremental restore, its header was not recognized as a valid file header for a file of the indicated type (datafile, archived log, or control file) belonging to the current database.

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

ORA-19564: error occurred writing string bytes at block number string

Cause: An error occurred while writing to a file.

Action: One or more other messages should be displayed to help pinpoint the cause of the error. Correct the error if possible, then retry the copy, backup, or restore operation.

ORA-19565: BACKUP_TAPE_IO_SLAVES not enabled when duplexing to sequential devices

Cause: An attempt was made to specify duplexing to sequential devices, but the BACKUP_TAPE_IO_SLAVES initialization parameter was not enabled.

Action: Specify BACKUP_TAPE_IO_SLAVES=TRUE in the INIT.ORA file, or do not specify duplexing to sequential devices.

ORA-19566: exceeded limit of string corrupt blocks for file string

Cause: The user specified limit of allowable corrupt blocks was exceeded while reading the specified datafile for a datafile copy or backup.

Action: None. The copy or backup operation fails. The session trace file contains detailed information about which blocks were corrupt.

ORA-19567: cannot shrink file string because it is being backed up or copied

Cause: An ALTER statement attempted to reduce the size of the indicated file while the same file is being backed up or copied.

Action: Retry the resize after the backup or copy is complete.

ORA-19568: a device is already allocated to this session

Cause: A device cannot be allocated to a session if another device is already allocated.

Action: Deallocate the current device

ORA-19569: no device is allocated to this session

Cause: An operation was attempted which requires a device to be allocated to the current session, and there is no device allocated.

Action: Allocate a device then retry the operation.

ORA-19570: file number string is outside valid range of 1 through string

Cause: A file number used in a copy, backup, or restore operation is not valid for the current database.

Action: Specify a valid file number.

ORA-19571: string RECID string STAMP string not found in control file

Cause: The input file specified for a copy or backup operation could not be opened because the record describing the file is not found in the control file.

Action: Specify a correct RECID/STAMP and retry the copy or backup.

ORA-19572: cannot process file string, file is being being resized

Cause: The input file specified for a copy or backup operation could not be opened because the file is being resized.

Action: Wait for the resize to complete then retry the copy or backup.

ORA-19573: cannot obtain string enqueue for datafile string

Cause: The file access enqueue could not be obtained for a file specified in a backup, copy or restore operation. If the enqueue type shown is 'shared', then the file is the input file for a backup or copy. If the type is 'exclusive', then the file is the output file for a datafile copy or restore which is attempting to overwrite the currently active version of that file - in this case, the file must be offline or the database must be closed. If the type is 'read-only', then you are attempting to back up or copy this file while the database is in NOARCHIVELOG mode.

Action: Wait until the conflicting operation is complete, then retry the copy or backup. If the database is in NOARCHIVELOG mode, then all files being backed up must be closed cleanly.

ORA-19574: output file name must be specified

Cause: This type of copy or restore requires an output file name.

Action: Specify an output file name and retry the copy.

ORA-19575: expected string blocks in file string, found string

Cause: During a backup, restore, copy, or scan operation, the indicated file did not contain as many blocks as were indicated in the file header.

Action: The input copy or backup piece is probably corrupt. If another backup or copy exists of the file that is being restored, then the corrupt file can be deleted from the recovery catalog and the operation can be restarted.

ORA-19576: datafile string not defined in control file

Cause: The specified file number was not found in the control file.

Action: Specify a correct file number and retry the operation.

ORA-19577: file string is MISSING

Cause: A COPYDATAFILECOPY, RESTOREDATAFILETO or PROXYRESTOREDATAFILE function specified a file number but no output file name, indicating that the output file name should be taken from the control file. However, the control file entry for this file indicates that it was created for a file that was present in the data dictionary but not named during the last CREATE CONTROLFILE statement, so the name in the control file cannot be used for restoration.

Action: Either specify an output file name or issue a SQL RENAME command to enter a valid name for this file in the control file.

ORA-19578: end of volume while duplexing to sequential files, backup piece incomplete

Cause: An end of volume (EOV) condition was detected while duplexing to sequential files, and this condition cannot be handled currently.

Action: Before retrying the backup, make sure the backup pieces will fit in the volume, or disable duplexing.

ORA-19579: archived log record for string not found

Cause: No archived log record corresponding to input file could be found in the control file.

Action: Specify a valid archived log file name and retry the operation.

ORA-19580: string conversation not active

Cause: A backup or restore operation was attempted before a conversation was started.

Action: Start a conversation then retry the operation.

ORA-19581: no files have been named

Cause: An attempt was made to proceed from the file naming phase to the piece processing phase of a backup or restore conversation before any files have been specified for backup or restore.

Action: Specify some files then retry the operation.

ORA-19582: archived log file header validation for string failed

Cause: Archived log file header is corrupt and could not be validated.

Action: Provide a valid archived log file and retry the operation.

ORA-19583: conversation terminated due to error

Cause: An error occurred which forced the termination of the current backup or restore conversation.

Action: There should be other error messages to help identify the cause of the problem. Correct the error and begin another conversation.

ORA-19584: file string already in use

Cause: The indicated file, which was specified as the target for a copy, restore, or delete operation is already in use by the database.

Action: Specify a different name and retry the operation.

ORA-19585: premature end of volume on piece string

Cause: While creating the indicated backup piece, an end-of-volume condition was encountered before all of the backup set control data was written to the backup piece. This is most likely a media error, because the amount of backup set control data is very small in relation to the total amount of data in a backup set.

Action: Retry the piece with a larger piece of output media.

ORA-19586: string k-byte limit is too small to hold piece directory

Cause: The user-specified limit of k-bytes per backup piece is not enough to hold the backup set control data.

Action: Use the SETLIMIT procedure to increase the k-byte limit and retry the operation.

ORA-19587: error occurred reading string bytes at block number string

Cause: An error occurred while reading from a file.

Action: One or more other messages should be displayed to help pinpoint the cause of the error. Correct the error then retry the copy, backup, or restore operation.

ORA-19588: string RECID string STAMP string is no longer valid

Cause: The indicated record has been marked as deleted. This indicates that the corresponding file has either been overwritten by another copy or restore, or that the copy was 'consumed' by a SWITCHTOCOPY operation.

Action: If you know the name of the file you wish to copy, then inspect it and then retry the copy specifying the new RECID.

ORA-19589: string is not a snapshot or backup control file

Cause: The control file that is the source for a backup or copy operation is not a snapshot or backup control file.

Action: Specify the name of a snapshot or backup control file.

ORA-19590: conversation already active

Cause: You tried to begin a backup or restore conversation, but another conversation is already active in this session.

Action: Either continue the current conversation, or call BACKUPCANCEL or RESTORECANCEL to end the current conversation before starting a new one.

ORA-19591: backup aborted because job time exceeded duration time

Cause: You tried to backup with duration option and the time provided was not sufficient to complete the backup.

Action: Adjust the duration time and re-run the command. Or run the backup command without duration option.

ORA-19592: wrong string conversation type

Cause: You attempted to specify a type of file to be backed-up or restored, but the current conversation cannot process this type of file. For example, you specified an archived log to be included in a datafile backup set. The specified file will not be included in the backup or restore operation.

Action: No action required - the conversation is still active, and more files can be specified.

ORA-19593: datafile number string already included as string

Cause: This datafile is already specified for inclusion in this backup or restore conversation. A backup or restore conversation may process only a single instance of a datafile.

Action: No action required - the conversation is still active, and more files can be specified.

ORA-19594: control file already included as string

Cause: The control file is already specified for inclusion in this backup or restore conversation. A backup or restore conversation may process only a single instance of the control file.

Action: No action required - the conversation is still active, and more files can be specified.

ORA-19595: archived log string already included in backup conversation

Cause: The indicated archived log has already been specified for inclusion in this backup conversation.

Action: No action required - the conversation is still active, and more files can be specified.

ORA-19596: SPFILE already included

Cause: The SPFILE is already specified for inclusion in this backup or restore conversation. A backup or restore conversation may process only a single instance of the SPFILE.

Action: No action required - the conversation is still active, and more files can be specified.

ORA-19597: file string block size string does not match set block size of string

Cause: A file was specified for inclusion in a backup set but it has a logical block size different from the rest of the files in the backup set. All files in a backup set must have the same logical block size.

Action: Specify a file that has the same block size as the rest of the files in the backup set. The conversation is still active and more files can be specified.

ORA-19598: can not backup SPFILE because the instance was not started with SPFILE

Cause: A backup command requested a backup of the SPFILE, but no SPFILE was used to startup the instance.

Action: Create an SPFILE and re-start the instance using the SPFILE.

ORA-19599: block number string is corrupt in string string

Cause: A corrupt block was found in a control file, archived log, or backup piece that is being read for a backup or copy. Corruption shall not be tolerated in control files, archived logs, or backup pieces.

Action: None. The copy or backup operation fails. Note that in the case of a backup set, the conversation is still active and the piece may be retried.

ORA-19600: input file is string string (string)

Cause: This message identifies the input file for a failed copy operation. Both the file number and name (if the name has been determined) are shown. For a datafile, the file number refers to the datafile's absolute file number as shown in the DBA_DATA_FILES view. For a datafile copy, the file number refers to the copy's control file record number as shown in the RECID column of the V$DATAFILE_COPY view. For an archived log, the file number refers to the log's control file record number as shown in the RECID column of the V$ARCHIVED_LOG view.

Action: See other error message.

ORA-19601: output file is string string (string)

Cause: This message identifies the output file for a failed copy operation. The fields are as described in message 19600. When creating a new datafile copy, its control file record number may not have been determined when the message is printed. In that case, the record number shown is zero.

Action: See other error message.

ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode

Cause: You tried to copy or backup a file that was not closed cleanly, and the database was in NOARCHIVELOG mode. This is not allowed because when restored, the file will require redo application before it is usable, and redo is not currently being saved beyond the contents of the online redo logs.

Action: Take the tablespace offline clean or close the database and retry the copy or backup.

ORA-19603: cannot backup or copy active file with KEEP .. UNRECOVERABLE option

Cause: The user tried to copy or backup a file that was not closed cleanly, with KEEP .. UNRECOVERABLE option. This is not allowed because when restored, the file will require redo application before it is usable, and redo will not be saved because of KEEP .. UNRECOVERABLE option.

Action: Take the tablespace offline cleanly, or close the database and retry the copy or backup.

ORA-19604: conversation file naming phase is over

Cause: A call was made to specify a file to be backed up or restored after the first backup piece has been processed.

Action: You cannot specify more files to be processed during a backup or restore conversation after the first backup piece has been processed. If more files must be specified, you must begin a new conversation.

ORA-19605: input file name must be specified

Cause: The input file name was not specified for a control file copy operation.

Action: Specify an input file name and retry the operation.

ORA-19606: Cannot copy or restore to snapshot control file

Cause: A control file copy or restore operation specified the name of the snapshot control file as the output file. It is not permitted to overwrite the snapshot control file in this manner. Other methods are available to create the snapshot control file.

Action: Specify a different file name and retry the operation. If this is a restore, then the restore conversation remains active and more files may be specified.

ORA-19607: string is an active control file

Cause: A control file copy, restore, or backup specified the name of a control file named in the INIT.ORA file as the input or output file.

Action: Specify a different file name and retry the operation. If this is a backup or restore conversation, then the conversation remains active and more files may be specified.

ORA-19608: string is not a backup piece

Cause: The specified file is not a backup piece produced by the DBMS_BACKUP_RESTORE package. Either the first block of the backup piece is corrupt or this file is not a backup piece.

Action: Specify a different file name and retry the operation.

ORA-19609: string is from different backup set: stamp string count string

Cause: The specified file is not from the backup set which is currently being processed. It is part of a different backup set. The identification of the set containing this piece is shown.

Action: Specify the correct backup piece and retry the operation.

ORA-19610: directory block string is corrupt

Cause: The indicated directory block failed checksum validation. This backup piece is unusable.

Action: Supply another copy of the same backup piece, or terminate the restore conversation.

ORA-19611: backup piece out of order. Expected string but found string

Cause: This backup piece is out of sequence.

Action: Supply the correct backup piece.

ORA-19612: datafile string not restored due to string

Cause: The indicated file could not be restored, because all of its data blocks were not found in the backup piece.

Action: The restore conversation remains active, and the current piece must be re-processed. If the failure cannot be resolved by re-processing the current piece, then the restore conversation must be cancelled.

ORA-19613: datafile string not found in backup set

Cause: The indicated file could not be restored, because it is not in this backup set. If the file number is zero, then this refers to the control file.

Action: This message is issued when the directory from the first backup piece is read and one or more files named for restoration were not found. The restore conversation is still active, but no data has been read and you must supply the first backup piece of a backup set that contains all of the requested files.

ORA-19614: archived log thread string sequence string not found in backup set

Cause: The indicated archived log file was named explicitly for restoration but is not contained in this backup set.

ORA-19615: some files not found in backup set

Cause: Some files that were specified for restoration were not found in the backup set directory. Message 19613 or 19614 is issued for each file that was not found.

Action: See the instructions for message 19613.

ORA-19616: output file name must be specified if database not mounted

Cause: A datafile restore specified no target file name, but the database is not mounted. The database must be mounted when no target file name is specified, so that the target file name can be obtained from the control file.

Action: The restore conversation remains active. If you wish to restore datafiles without their target file names, then mount the database before continuing. Otherwise, a target file name must be specified on all datafile restoration calls.

ORA-19617: file string contains different RESETLOGS data

Cause: The indicated file contains RESETLOGS data which is different from the archived log files which are already included in the backup set. All archived log files in a backup set must have the same RESETLOGS data.

Action: The restore conversation remains active, and you may continue to specify archived log files for inclusion in the backup set.

ORA-19618: cannot name files after RESTOREVALIDATE has been called

Cause: A call was made to specify a file to restore from a backup set, but a previous call to RESTOREVALIDATE has already been made.

Action: You must cancel and restart the conversation if you wish to specify files to restore.

ORA-19619: cannot call RESTOREVALIDATE after files have been named

Cause: RESTOREVALIDATE was called after some files had already been specified for restoration.

Action: You must cancel and restart the conversation if you wish to call RESTOREVALIDATE.

ORA-19620: string is not of string type

Action: The indicated file cannot be processed. Ensure that the correct files are being specified for the copy or backup operation.

ORA-19621: archived log range has already been specified

Cause: A range of logs has already been specified. Only one SCN range may be specified per conversation.

Action: The restore conversation remains active and more logs may be specified by thread and sequence number, if desired.

ORA-19622: archived log thread string sequence string not restored due to string

Cause: The indicated file could not be restored, because all of its data blocks were not found in the backup piece.

ORA-19623: file string is open

Cause: A SWITCHTOCOPY operation specified a datafile copy whose parent datafile is open.

Action: Take the owning tablespace offline or close the database, then retry the operation.

ORA-19624: operation failed, retry possible

Cause: A backup, restore or image copy operation failed with an I/O error. If the source of the I/O error can be corrected, then the operation may be retried.

Action: This message is used by recovery manager to decide whether or not to retry the operation.

ORA-19625: error identifying file string

Cause: A file specified as input to a copy or backup operation, or as the target for an incremental restore, could not be identified as an Oracle file. An OS-specific error accompanies this error to help pinpoint the problem.

Action: Specify an different file and retry the operation.

ORA-19626: backup set type is string - can not be processed by this conversation

Cause: The data in the backup set is not compatible with the current conversation.

Action: Either supply the first piece from a backup set that matches the current conversation or start a new restore conversation which can process this backup set.

ORA-19627: cannot read backup pieces during control file application

Cause: This is a control file restore conversation, which is using the offline range information from one or more control files to update datafile checkpoint data. Backup sets are not used during this type of conversation.

Action: The conversation is still active and more control files may be applied.

ORA-19628: invalid SCN range

Cause: The starting SCN for RESTOREREDOLOGRANGE is greater than the ending SCN.

Action: Specify a starting SCN which is less than or equal to the ending SCN.

ORA-19629: no files in specified archived log SCN range

Cause: This backup set contains no files in the specified range.

Action: Either supply a backup set that contains files in the correct range or start a new conversation and specify a range which will select some files from this backup set.

ORA-19630: end of volume encountered while copying backup piece

Cause: While copying a backup piece from the OS native file system to an output device, the output device encountered end-of-volume.

Action: The copy fails. This could happen if a tape was used which is not large enough to hold the entire backup piece.

ORA-19631: archived log record contains no file name

Cause: This archived log record represents a switch into an active log that took place without archiving its prior contents. The prior contents of the log file are lost.

Action: Specify the RECID of an archived log record that contains a file name. Fixed view v$archived_log can be used to examine the archived logs.

ORA-19632: file name not found in control file

Cause: The name passed to GETFNO was not found in the control file.

Action: Supply a valid file name.

ORA-19633: control file record string is out of sync with recovery catalog

Cause: The control file record describing the file to be deleted in a call to DELETEBACKUPPIECE, DELETEDATAFILECOPY, PROXYDELETE or DELETEARCHIVEDLOG does not match the validation data supplied by recovery manager.

Action: contact Oracle support

ORA-19634: file name required for this function

Cause: The FNAME or HANDLE parameter was not specified for DELETEPIECE, DELETEDATAFILECOPY, DELETEREDOLOG or PROXYDELETE.

Action: Specify the FNAME or HANDLE parameter when calling these functions.

ORA-19635: input and output file names are identical: string

Cause: Identical input and output file names were specified for a datafile copy operation.

Action: Specify an output file name which is different from the input file name.

ORA-19636: archived log thread string sequence string already included

Cause: The indicated archived log has already been specified for inclusion in this restore conversation. A restore conversation may process only one copy of any archived log.

Action: No action required - the conversation is still active, and more files can be specified.

ORA-19637: BACKUPPIECECREATE requires file name when using DISK device

Cause: The session device is currently allocated to disk, and so a file name is required.

Action: Supply a file name and retry the operation.

ORA-19638: file string is not current enough to apply this incremental backup

Cause: The checkpoint of the target for this incremental backup is less than the start of the incremental backup. If this backup were applied, then any changes made between the datafile checkpoint and the start of the incremental backup could be lost.

Action: Supply a backup set that can be applied and retry the operation.

ORA-19639: file string is more current than this incremental backup

Cause: The checkpoint of the target for this incremental backup is greater than or equal to the checkpoint of the file in the incremental backup set. This backup cannot advance the checkpoint of the target file, so there is no point in applying it.

Action: Supply a backup set that can be applied and retry the operation.

ORA Error . Listado Errores Oracle. ORA-19210 a ORA-19501

2013-06-17T12:54:00.002-07:00

ORA-19210: column 'string', specified to be a key or update column for DBMS_XMLSTORE, does not not exist in table 'string'

Cause: The column specified using setKeyColumn()/setUpdateColumn() did not exist in the table.

Action: Change the column specified to be a column in the table

ORA-19211: column 'string', specified as key using DBMS_XMLSTORE.setKeyColumn() , must be of scalar type

Cause: The column specified using setKeyColumn() was a non-scalar type column.

Action: Change the column specified to be a scalar column in the table

ORA-19212: no key columns specified before call to DBMS_XMLSTORE.updateXML()

Cause: No columns were specified as key columns before the call to DBMS_XMLSTORE.updateXML.

Action: Use DBMS_XMLSTORE.setKeyColumn() to specify key columns

ORA-19221: XPST0001 - XQuery static context component string not initialized

Cause: An unitialized static context component was encountered during the static analysis of the expression.

Action: initialize the given static context.

ORA-19222: XPDY0002 - XQuery dynamic context component string not initialized

Cause: An unitialized dynamic context component was encountered during the evaluation of the expression.

Action: Initialize the particular dynamic context component.

ORA-19223: XPST0003 - syntax error in XQuery expression

Cause: The given XQuery expression contains syntax errors.

Action: Fix the syntax error in the XQuery expression.

ORA-19224: XPTY0004 - XQuery static type mismatch: expected - string got - string

Cause: The expression could not be used because it's static type is not appropriate for the context in which it was used.

Action: Fix the expression to be of the required type or add appropriate cast functions around the expression.

ORA-19225: XPST0005 - XQuery static type error: expected non empty type got empty sequence

Cause: The static type assigned to an expression other than the () expression must not be the empty type.

Action: Fix the expression so it does not return empty sequences.

ORA-19226: XPTY0006 - XQuery dynamic type mismatch: expected string got string

Cause: The expression could not be used because it's dynamic type did not match the required type as specified by XQuery sequencetype matching rules.

Action: Fix the expression to return the expected type or use appropriate cast functions.

ORA-19227: XPTY0007 - fn:data function is applied to a node (type (string)) whose type annotation denotes a complex type with non-mixed complex content.

Cause: The input node for atomization contained a type annotation that denoted a complex type with non-mixed complex content.

Action: Fix the input expression to fn:data to be a node that does not contain non-mixed complex content.

ORA-19228: XPST0008 - undeclared identifier: prefix 'string' local-name 'string'

Cause: The given identifier refers to either a type name, function name, namespace prefix, or variable name that is not defined in the static context.

Action: Fix the expression to remove the identifier, or declare the appropriate variable, type, function or namespace.

ORA-19229: XQST0009 - schema import not supported

Cause: A schema import was encountered in the query.

Action: remove the schema import.

ORA-19230: XPST0010 - unsupported axis string

Cause: An unsupported axis was encountered in the given expression.

Action: Remove the unsupported axis from the expression.

ORA-19232: XQST0012 - imported schemas violate validity rules

Cause: The imported schemas did not satisfy the conditions for schema validity specified in the XMLSchema specification.

Action: Fix the imported schemas to satisfy the validity rules.In particular, the definitions must be valid, complete, and unique -- that is, the pool of definitions must not contain two or more schema components with the same name and target namespace.

ORA-19233: XQST0013 - invalid pragma

Cause: A pragma was specified whose contents are invalid.

Action: Specify the pragma with the correct contents.

ORA-19234: XQST0014 - invalid or unsupported must-understand extension

Cause: The must-understand extension specified was either invalid or unsupported.

Action: remove the unsupported must-understand extension or fix the error.

ORA-19235: XQST0015 - unsupported must-understand extension

Cause: The XQuery flagger was enabled and the query contained a must-understand extension.

Action: remove the unsupported must-understand extension.

ORA-19236: XQST0016 - module declaration or import not supported

Cause: The given query had a module declaration or module import.

Action: Remove the import module or module declaration.

ORA-19237: XPST0017 - unable to resolve call to function - string:string

Cause: The name and arity of the function call given could not be matched with any in-scope function in the static context.

Action: Fix the name of the function or the number of parameters to match the list of in-scope functions.

ORA-19238: XPTY0018 - It is a type error if the result of the last step in a path expression contains both nodes and atomic values

Cause: An error occurred during the processing of the XQuery expression.

Action: Check the detailed error message for the possible causes.

ORA-19239: XPTY0019 - It is a type error if the result of an step (other than the last step) in a path expression contains an atomic value

Cause: The step expression returned a sequence containing an atomic value.

Action: Fix the path expression to return only nodes.

ORA-19240: XPTY0020 - context item must be node in an axis expression

Cause: The context item that was used in the axis epression is not a node.

Action: Change the context item to be a node.

ORA-19241: XPDY0021 - cast to type string failed

Cause: The value inside a cast expression could not be cast to the required type.

Action: Fix the input to the cast expression to be of a castable type.

ORA-19242: XQST0022 - namespace declaration attribute must be a literal

Cause: The namespace declaration attribute was not a literal string.

Action: Fix the namespace declaration to be a literal string.

ORA-19243: XQTY0023 - invalid document node content in element constructor

Cause: The content sequence in an element constructor contained a document node.

Action: Change the content of the element constructor so that it does not contain a document node.

ORA-19244: XQTY0024 - invalid attribute node in element constructor

Cause: The content sequence in an element constructor contained an attribute node following a node that was not an attribute node.

Action: Change the content sequence of the element constructor so that it does not contain the attribute node.

ORA-19245: XQDY0025 - duplicate attribute name string

Cause: The content sequence of the element constructor contained more than one attribute that had the same name.

Action: Remove the duplicate attributes.

ORA-19246: validation failed - element string not found in in-scope element declarations

Cause: The validation mode was strict and the element-constructor contained an element name that was not present in the in-scope element declarations.

Action: Fix the validation mode to be lax or import the schema definition that contains the required element declaration.

ORA-19247: XQDY0027 - validation error

Cause: An error was encountered during the validation of the expression.

Action: Fix the validation error.

ORA-19248: XQTY0028 - invalid node in document constructor

Cause: The content sequence in a document constructor contained either a document or an attribute node.

Action: Fix the content so it does not contain any of the above node types.

ORA-19249: XQDY0029 - value does not match facet of the target type

Cause: The input value to a cast expression did not satisfy the facets of the target type.

Action: Fix the value to conform to the facets of the target type.

ORA-19250: XQTY0030 - too many values to validate expression

Cause: The argument of a validate expression returned more than one element or document node.

Action: Fix the argument of the validate expression to return a single element or document node.

ORA-19251: XQST0031 - unsupported query version

Cause: The query version specified in the prolog was not supported.

Action: Supply the version of the query that is supported.

ORA-19252: XQST0032 - too many declarations for base URI

Cause: The query prolog contained multiple declarations for the base URI.

Action: Remove the duplicate definitions for the base URI.

ORA-19253: XQST0033 - too many declarations for namespace prefix string

Cause: The query prolog contained multiple declarations for the same namespace prefix.

Action: Remove the duplicate definitions for the namespace prefix.

ORA-19254: XQST0034 - too many declarations for function string

Cause: The query module contained more than one function, either declared or imported, which have the same expanded QName.

Action: Remove the duplicate function definitions.

ORA-19255: XQST0035 - too many declarations of string in imported schemas

Cause: Two schemas were imported that defined the same name in the same symbol space and in the same scope.

Action: Fix the schema imports to remove the name conflict.

ORA-19256: XQST0036 - missing type definitions in imported module

Cause: A module was imported, which contains references to type names that are not defined in the in-scope type definitions inside the module.

Action: Fix the module definintion to include the in-scope type definition.

ORA-19257: XQST0037 - function or variable string in module already defined

Cause: A module being imported contained the function or variable that is already declared in the static context of the importing module.

Action: Remove the conflicting declarations.

ORA-19258: XQST0038 - unsupported or duplicate default collation specified

Cause: The query prolog prolog either specified more than one default collation or the collation specified was not supported.

Action: Remove the duplicate definition or specify a supported collation.

ORA-19259: XQST0039 - duplicate parameter name string in function declaration

Cause: The function declaration contained more than one parameter with the same name.

Action: Fix the function declaration to remove the duplicate parameters.

ORA-19260: XQST0040 - invalid namespace node in element constructor

Cause: The content sequence in an element constructor contained a namespace node node following a node that was not a namespace node.

Action: Remove the namespace node in the element constructor.

ORA-19261: XQDY0041 - non empty URI in QName

Cause: The name expression in a computed processing instruction or computed namespace constructor returned a QName whose URI part was not empty.

Action: Fix the processing instruction or computed namespace constructor to return the QName with an empty URI part.

ORA-19262: XQST0042 - namespace constructor not inside an element constructor

Cause: The enclosing expression of a computed namespace constructor was not a computed element constructor.

Action: Fix the namespace constructor to be inside an element constructor.

ORA-19263: XQST0043 - duplicate namespace prefix string

Cause: Two or more computed namespace constructors within the same computed element constructor attempted to bind the same namespace prefix.

Action: Remove the duplicate namespace definitions.

ORA-19264: XQDY0044 - invalid namespace in attribute constructors

Cause: A computed attribute constructor returned a QName that is in the pre-defined XML namespace (corresponding to namespace prefix xmlns).

Action: Change the namespace for the computed attribute constructor.

ORA-19265: XQST0045 - invalid or unknown prefix string in function declaration

Cause: The declared function name in a function declaration had no namespace prefix or had one of the predefined namespace prefixes other than local.

Action: Fix the function declaration to have the correct prefix.

ORA-19266: XQST0046 - invalid URI

Cause: The given URI contained a lexical form that was not valid according to the definition of xs:anyURI in XML Schema.

Action: Fix the URI.

ORA-19267: module string not found

Cause: The module with the given target URI could not be found.

Action: Fix the prolog to import only available modules.

ORA-19268: XQST0048 - namespace string does not match target namespace string

Cause: The module contained a function or variable whose namespace did not match the target namespace of the module.

Action: Fix the namespace of the function or variable to match the target namespace of the module.

ORA-19269: XQST0049 - variable string defined multiple times

Cause: The module defined or imported the same variable multiple times.

Action: Fix the import or the module definition to remove duplicate definitions.

ORA-19270: XPDY0050 - treat failed - expected string got string

Cause: The type of the operand to the treat expression did not match the required type.

Action: Fix the input operand to be of the correct type.

ORA-19271: XPST0051 - invalid atomic type definition

Cause: The QName used as an AtomicType in a SequenceType was not defined in the in-scope type definitions as an atomic type.

Action: Use the correct atomic type name.

ORA-19272: XQDY0052 - invalid atomic value in attribute or element constructor

Cause: The content of the element or attribute constructor included an atomic value that could not be cast into a string.

Action: Fix the content to contain atomic values that can be cast to a string.

ORA-19273: XQST0053 - empty string in namespace declaration

Cause: An empty string was used in a namespace declaration.

Action: Fix the namespace declaration to have a non-empty string.

ORA-19274: XQST0054 - variable initialization failed due to circularity

Cause: A circular definition was encountered when the variable was initialized.

Action: Remove the circularity in the initialization.

ORA-19275: XQST0055 - schema path string not found in list of in-scope schema definitions

Cause: The ElementTest specified a schema path that could not be found in the list of in-scope schema definitions.

Action: Include the appropriate schema that can be used to resolve the ElementTest.

ORA-19276: XPST0005 - XPath step specifies an invalid element/attribute name: (string)

Cause: The XPath step specified invalid element or attribute name that did not match any nodes according to the input XML schema or structure.

Action: Correct the element or attribute name as the name may be mis-spelled.

ORA-19277: XPST0005 - XPath step specifies an item type matching no node: (string)

Cause: The XPath step specified an item type that did not match any nodes according to the input XML schema or structure.

Action: Correct the item type defintion as node of such type does not exit in the input XML schema or structure.

ORA-19278: Invalid value: (string) for type: (string)

Cause: The value was invalid for the type.

Action: Correct the value or change the type.

ORA-19279: XPTY0004 - XQuery dynamic type mismatch: expected singleton sequence - got multi-item sequence

Cause: The XQuery sequence passed in had more than one item.

Action: Correct the XQuery expression to return a single item sequence.

ORA-19280: XQuery dynamic type mismatch: expected atomic value - got node

Cause: A node was passed in to the expression where an atomic value was expected.

Action: Correct the XQuery expression to return an atomic value.

ORA-19281: XQST0055 - It is a static error if a Prolog contains more than one copy-namespaces declaration

Cause: The query prolog contained multiple copy-namespaces declarations.

Action: Remove the duplicate copy-namespaces declarations.

ORA-19282: XQST0068 - It is a static error if a Prolog contains more than one xmlspace declaration

Cause: The query prolog contained multiple xmlspace declarations.

Action: Remove the duplicate xmlspace declarations.

ORA-19283: XQST0031 - It is a static error if the version number specified in a version declaration is not supported by the implementation.

Cause: The query contained a version declaration not supported by this implementation.

Action: Change the version declaration to 1.0 which is the version supported by this implementation.

ORA-19284: Encoding specification in version declaration not supported

Cause: The query contained an encoding specification.

Action: Remove the encoding specification.

ORA-19285: FODC0002 - error retrieving resource

Cause: The URI provided could not be resolved to a valid resource.

Action: Provide a valid URI for a resource.

ORA-19286: XPST0017 - unable to resolve call to function - string

Cause: The name and arity of the function call given could not be matched with any in-scope function in the static context.

Action: Fix the name of the function or the number of parameters to match the list of in-scope functions.

ORA-19287: XPST0017 - invalid number of arguments to function - string:string

Cause: The name and arity of the function call given could not be matched with any in-scope function in the static context.

Action: Fix the name of the function or the number of parameters to match the list of in-scope functions.

ORA-19288: XPST0017 - invalid number of arguments to function - string

Cause: The name and arity of the function call given could not be matched with any in-scope function in the static context.

Action: Fix the name of the function or the number of parameters to match the list of in-scope functions.

ORA-19289: XQST0034 - function string:string declared or defined multiple times

Cause: Multiple functions declared or imported by a module had the same expanded QName and the same number of arguments.

Action: Fix the function declaraction or definition to remove duplicates.

ORA-19290: XQST0069 - more than one empty order declaration declared in the prolog

Cause: A prolog had more than one empty order declaration.

Action: Fix the prolog to have just one empty order declaration.

ORA-19291: XPST0081 - specified QName cannot be expanded into a namespace URI

Cause: The namespace prefix of the QName could not be expanded into a namespace URI by using the statically known namespaces.

Action: Use a namespace prefix that can be resolved into a namespace URI from the statically known namespaces.

ORA-19292: XQST0057: It is a static error if a schema import binds a namespace prefix but does not specify a target namespace other than a zero-length string

Cause: An error occurred during the processing of the XQuery expression.

Action: Check the detailed error message for the possible causes.

ORA-19293: XQST0058: It is a static error if multiple schema imports specify the same target namespace

Cause: An error occurred during the processing of the XQuery expression.

Action: Check the detailed error message for the possible causes.

ORA-19294: XQST0059: It is a static error if an implementation is unable to process a schema or module import by finding a schema or module with the specified target namespace

Cause: An error occurred during the processing of the XQuery expression.

Action: Check the detailed error message for the possible causes.

ORA-19295: XQST0060: It is a static error if the name of a function in a function declaration is not in a namespace (expanded QName has a null namespace URI)

Cause: An error occurred during the processing of the XQuery expression.

Action: Check the detailed error message for the possible causes.

ORA-19296: XQDY0061: It is a dynamic error if the operand of a validate expression is a document node whose children do not consist of exactly one element node and zero or more comment and processing instruction nodes, in any order

Cause: An error occurred during the processing of the XQuery expression.

Action: Check the detailed error message for the possible causes.

ORA-19297: XQDY0064: It is a dynamic error if the value of the name expression in a computed processing instruction constructor is equal to "XML" (in any combination of upper and lower case

Cause: An error occurred during the processing of the XQuery expression.

Action: Check the detailed error message for the possible causes.

ORA-19298: XQST0065: A static error is raised if a Prolog contains more than one ordering mode declaration

Cause: An error occurred during the processing of the XQuery expression.

Action: Check the detailed error message for the possible causes.

ORA-19299: XQST0066: A static error is raised if a Prolog contains more than one default element/type namespace declaration, or more than one default function namespace declaration

Cause: An error occurred during the processing of the XQuery expression.

Action: Check the detailed error message for the possible causes.

ORA-19300: Error occurred in uri processingstring

Cause: An error occurred when processing the URL

Action: Check the given error message and fix the appropriate problem

ORA-19320: Host name not specified in HTTP URL

Cause: A host name was not specified in the HTTP url

Action: Specify a host name in the HTTP url when creating the URL string

ORA-19321: Could not open HTTP connection to host (string): port (string)

Cause: A HTTP connection could not be opened to the host

Action: Specify a valid host name and port to connect to

ORA-19322: An error occurred while reading from host (string): port (string)

Cause: An error occurred while reading from the HTTP host

Action: Specify a valid host name and port to read from

ORA-19323: Invalid url string

Cause: The URL must be a valid URL string

Action: Specify a valid url string

ORA-19330: Type 'string'.'string' not installed. Please install the type before using the CREATE_DBURI operator

Cause: The type required for the CREATE_DBURI operator has not been installed correctly.

Action: Read the installation notes to install the type correctly.

ORA-19331: Last argument to CREATE_DBURI operator must be a column

Cause: The final argument to the CREATE_DBURI operator must be a column to which the reference is being created.

Action: Specify a valid column name in the query.

ORA-19332: Invalid column in the CREATE_DBURI operator

Cause: The argument to the CREATE_DBURI operator can only be a column.

Action: Specify a valid column name for the operator

ORA-19333: Invalid flags for the CREATE_DBURI operator

Cause: The flags argument given to the DBURI operator is invalid

Action: Specify a valid flag value (TEXT) for the DBURI operator

ORA-19334: Invalid column specification for CREATE_DBURI operator

Cause: All columns must be valid and pointing to the same table or view

Action: Specify valid list of columns that are from the same table or view.

ORA-19335: Invalid format type object

Cause: An invalid format type object was specified for the XML function

Action: Specify a valid format type object

ORA-19336: Missing XML root element

Cause: The XML being generated does not have an enclosing root element.

Action: The XML generated must have a root element

ORA-19361: ONLINE option not allowed with this type of index

Cause: The ONLINE option was specified to validate the structure of a system-generated metadata index

Action: The ONLINE option can not be used with system-generated metadata indexes such as an LOB index, an IOT Top index, an Index on Clusters etc., Run query without using the ONLINE option.

ORA-19371: invalid update option

Cause: The user attempted to call load_sqlset with an update option that is different than REPLACE and ACCUMULATE.

Action: Adjust the update option and retry the operation.

ORA-19372: invalid update condition

Cause: The user attempted to call load_sqlset with an invalid update condition.

Action: Check the update condition (e.g., NEW.COL1_NAME >= OLD.COL2_NAME) and retry the operation.

ORA-19373: invalid staging table or tablespace

Cause: The user attempted to create a staging table and specified an invalid staging table (or one that already exists) or tablespace

Action: Check the arguments and try again.

ORA-19374: invalid staging table

Cause: The user specified an invalid staging table to one of the pack, unpack, or remap stgtab routines, or the user does not have the correct privileges on the staging table

Action: Provide a correct staging table or grant the appropriate privileges

ORA-19375: no CREATE TABLE privilege on schema "string"

Cause: The user tried to create a staging table when he is missing the CREATE TABLE privilege on the specified schema.

Action: Grant the privilege to the user and retry

ORA-19376: no privileges on tablespace provided or tablespace is offline

Cause: The user tried to create a staging table on a tablespace on which he does not have any space allocated, or it is offline

Action: Allocate space on the tablespace, bring it online, and retry

ORA-19377: no "SQL Tuning Set" with name like "string" exists for owner like "string"

Cause: The user specified a filter to a pack/unpack function for the SQL Tuning Set that targets no STS in the SYS schema or the staging table, respectively

Action: Provide a different filter after checking the state of the system

ORA-19378: invalid mode

Cause: The user specified an invalid mode argument to the capture function.

Action: Provide a mode argument that was defined in the dbmssqlt file

ORA-19379: invalid time_limit or repeat_interval

Cause: The user specified a NULL value for either the time_limit or the repeat_interval, or a repeat_interval that is greater than the time_limit

Action: Provide a non-null value and make sure time_limit >= repeat_interval

ORA-19380: invalid plan filter

Cause: The user specified an invalid filter for the plan when calling the select_sqlset table function.

Action: Adjust the the filter to be one of the following values and retry the operation: MAX_ELAPSED_TIME, MAX_CPU_TIME, MAX_DISK_READS, MAX_OPTIMIZER_COST, MAX_BUFFER_GETS, FIRST_LOADED LAST_LOADED, FIRST_GENERATED, or LAST_GENERATED.

ORA-19381: cannot create staging table in SYS schema

Cause: The user attempted to create a staging table in the sys schema

Action: Create the table in another schema.

ORA-19384: cannot pack into staging table from previous version

Cause: An attempt was made to perform a pack operation on a staging table from a previous version.

Action: Create a staging table in the current version and retry the operation.

ORA-19385: staging table is empty

Cause: An attempt was made to perform an operation on an empty staging table.

Action: Check the staging table to make sure that it has rows.

ORA-19386: target object already exists for tuning task "string"

Cause: An attempt was made to set a target object for a tuning task when one had already been set.

Action: Create a new task if another target object is needed.

ORA-19387: "SQL Tuning Set" "string" belongs to another tuning task

Cause: The user attempted to tune a task-managed SQL Tuning Set belonging to one task within the scope of another task.

Action: Check the SQL Tuning Set and retry the operation.

ORA-19388: operation not supported for "SQL Tuning Set" type

Cause: The attempted operation was unsupported for the type of the given SQL Tuning Set.

Action: Check the SQL Tuning Set and retry the operation.

ORA-19400: System type conflict with object SYS.string

Cause: The user had an object with the same name as one of the system types. The system types were not initialized properly.

Action: Remove the conflicting object and rerun migration.

ORA-19500: device block size string is invalid

Cause: the device block size returned by sequential I/O OSD is invalid

Action: If the block size was set by using the PARMS option of the Recovery Manager ALLOCATE CHANNEL command, then the specified block size must be changed. If no PARMS option was specified on the ALLOCATE CHANNEL command, then this is an internal error that should be reported to Oracle.

ORA-19501: read error on file "string", block number string (block size=string)

Cause: read error on input file

Action: check the file

ORA Error . Listado Errores Oracle. ORA-19024 a ORA-19209

2013-06-17T12:52:00.000-07:00

ORA-19024: Cursor expression must be named

Cause: The value of context passed to GETXML was invalid.

Action: Rewrite the query so that the value of context passed to GETXML is valid.

ORA-19025: EXTRACTVALUE returns value of only one node

Cause: Given XPath points to more than one node.

Action: Rewrite the query so that exactly one node is returned.

ORA-19026: EXTRACTVALUE can only retrieve value of leaf node

Cause: Given XPath does not point to a leaf node.

Action: Rewrite the query so that a leaf node is returned.

ORA-19028: Invalid ADT parameter passed to toObject() function

Cause: The object passed as ADT parameter to sys.XMLType.toObject() is not the same type, or a super-type, of the mapped type.

Action: Pass an object of the correct type to toObject().

ORA-19029: Cannot convert the given XMLType to the required type

Cause: The passed in XMLType could not be convert to the required type

Action: Binary XMLtype instances or other objects cannot be converted to the required object or collection types.

ORA-19030: Method invalid for non-schema based XML Documents.

Cause: The method can be invoked on only schema based xmltype objects.

Action: Don't invoke the method for non schema based xmltype objects.

ORA-19031: XML element or attribute string does not match any in type string.string

Cause: The passed in XML tag does not match any in the object type

Action: Pass a valid canonical XML that can map to the given object type

ORA-19032: Expected XML tag string got string

Cause: When converting XML to object, a wrong tag name was present

Action: Pass a valid canonical XML that can map to the given object type

ORA-19033: schema specified in the XML document does not match the schema parameter

Cause: When creating schema-based XML, the schema specified in the XML document is different from the schema passed in as the 'schema' parameter.

Action: Change the schema parameter to match the schema specified in the XML document.

ORA-19034: Type not supported during schema generation

Cause: The object type contained a type that is not supported for schema generation.

Action: Use a different type or do not generate a schema.

ORA-19035: Invalid select item of the query in newContextFromHierarchy()

Cause: The query does not have a number select item followed by an XMLType select item only.

Action: Make sure the result set of the query used in the newContextFromHierarchy() must have only two selected items: the first item must be number type and the second item must be XMLType.

ORA-19036: Invalid query result set in newContextFromHierarchy()

Cause: The result set of the query used in the newContextFromHierarchy() does not have the same property as the result set generated by a CONNECT BY query.

Action: Make sure the query used in newContextFromHierarchy() is a CONNECT BY query or the query returns the result set have the same property as the result set generated by a CONNECT BY query.

ORA-19037: XMLType result can not be a fragment

Cause: The select item of the query in newContextFromHierarchy() is an XML fragment.

Action: Make sure the select item of the query in newContextFromHierarchy() is NOT an XML fragment

ORA-19038: Invalid opertions on query context

Cause: SetMaxRows, SetSkipRows, SetRowTagName opertions are applied to a query context created from newContextFromHierarchy().

Action: SetMaxRows, SetSkipRows, SetRowTagName opertions can not be applied to a query context created from newContextFromHierarchy().

ORA-19039: Keyword string reserved for future use

Cause: The keyword is reserved for future use as a builtin function.

Action: Change the name mentioned above to a different one.

ORA-19040: Element string does not match expected string.

Cause: The given XML document had a different root element than expected.

Action: Insert/Update only the XML documents that conform to that particular schema and element.

ORA-19041: Comment data cannot contain two consecutive '-'s

Cause: The given comment string expression has two consecutive '-'s.

Action: Modify comment string to eliminate one or both of the consevutive '-'s.

ORA-19042: Enclosing tag string cannot be xml in any case combination

Cause: The given enclosing tag matched 'xml' in some case combination

Action: Modify the enclosing tag so that it is not xml in any case combination.

ORA-19043: Multiply nested XMLROOT function disallowed

Cause: An XMLROOT function has an operand that is also an XMLROOT function.

Action: Modify the query so that there are no multiply nested XMLROOT functions.

ORA-19044: character length specified for XMLSerialize is too small.

Cause: An XMLSerialize function was called with a type of character type (e.g. VARCHAR2(27)), and the length specified (27 in the example) was too small.

Action: Modify the query so that the character length specified is larger.

ORA-19045: character set id specified for XMLSerialize not valid

Cause: An XMLSerialize function was called with an invalid value for the caracter set id.

Action: Modify the query so that the character set id is valid.

ORA-19100: PASSING or RETURNING keyword expected

Cause: The keyword PASSING or RETURNING was missing.

Action: Specify the PASSING or RETURNING keyword.

ORA-19101: CONTENT keyword expected

Cause: The keyword CONTENT was missing.

Action: Specify the CONTENT keyword.

ORA-19102: XQuery string literal expected

Cause: The string literal containing the XQuery expression was missing.

Action: Specify the XQuery expression as a string literal.

ORA-19103: VALUE keyword keyword

Cause: The keyword VALUE was missing.

Action: Specify the VALUE keyword.

ORA-19104: invalid XQueryX: missing attribute string

Cause: The XQueryX expression was not assigned the expected attribute.

Action: Specify a valid XQueryX.

ORA-19105: invalid XQueryX: expected text node - got string

Cause: The XQueryX expression did not contain a text node as expected.

Action: Specify a valid XQueryX.

ORA-19106: invalid XQueryX: expected string - got string

Cause: The XQueryX expression did not contain the node as expected.

Action: Specify a valid XQueryX.

ORA-19107: invalid XQueryX - unsupported construct - string

Cause: The given XQuery expression contains an unsupported construct.

Action: Specify a valid XQueryX.

ORA-19108: WHITESPACE keyword expected

Cause: The keyword WHITESPACE was missing.

Action: Specify the WHITESPACE keyword.

ORA-19109: RETURNING keyword expected

Cause: The keyword RETURNING was missing.

Action: Specify the RETURNING keyword.

ORA-19110: unsupported XQuery expression

Cause: The program specified an XQuery expression that is not supported.

Action: Rewrite the XQuery with a expression that is supported.

ORA-19111: error during evaluation of the XQuery expression

Cause: An error occurred during the processing of the XQuery expression.

Action: Check the detailed error message for the possible causes.

ORA-19112: error raised during evaluation: string

Cause: The error function was called during evaluation of the XQuery expression.

Action: Check the detailed error message for the possible causes.

ORA-19113: trace function called during evaluation: string

Cause: The trace function was called during evaluation of the XQuery expression.

Action: Check the log file for the trace message.

ORA-19114: XPST0003 - error during parsing the XQuery expression: string

Cause: An error occurred during the parsing of the XQuery expression.

Action: Check the detailed error message for the possible causes.

ORA-19115: too many context items specified

Cause: More than one context item was specified as input to the XMLQuery function.

Action: Specify a single context item for the XMLQuery function.

ORA-19116: too many xmlspace declarations

Cause: The query prolog contained multiple xmlspace declarations.

Action: Remove the duplicate xmlspace declarations.

ORA-19117: XQST0070 - invalid redefinition of predefined namespace prefix 'string'

Cause: The given predefined namespace was being redefined in a namespace declaration.

Action: Remove the namespace declaration that redefines the predefined namespace prefix.

ORA-19118: XQST0066 - duplicate default namespace definition - string

Cause: More than one default namespace declaration used the given namespace URI.

Action: Remove the duplicate default namespace definition.

ORA-19121: duplicate attribute definition - string

Cause: More than one attribute with the same name.

Action: Remove the duplicate attribute definition.

ORA-19122: unsupported XQuery declaration

Cause: The program specified an XQuery declaration that is not supported.

Action: Rewrite the XQuery with a declaration that is supported.

ORA-19123: FORG0003: fn:zero-or-one() called with a sequence containing more than one item

Cause: sequence with more than one item was passed into fn:zero-or-one() function

Action: correct input argument to fn:zero-or-one() function

ORA-19124: FORG0004: fn:one-or-more() called with a sequence containing no items

Cause: sequence containing no items was passed into fn:one-or-more() function

Action: correct input argument to fn:one-or-more() function

ORA-19125: FORG0005: fn:exactly-one() called with a sequence containing zero or more than one item

Cause: sequence containing zero or more than one item was passed into fn:exactly-one() function

Action: correct input argument to fn:exactly-one() function

ORA-19126: XQuery extension expression contains neither a pragma that is recognized by the implementation nor an expression enclosed in curly braces

Cause: No expression was enclosed in curly braces for the extension expression or the pragma content was not recognized.

Action: Correct inputs to extension expression.

ORA-19127: XQST0067: XQST0067: A static error is raised if a Prolog contains more than one construction declaration

Cause: An error occurred during the processing of the XQuery expression.

Action: Check the detailed error message for the possible causes.

ORA-19128: XQST0068: A static error is raised if a Prolog contains more than one boundary-space declaration

Cause: An error occurred during the processing of the XQuery expression.

Action: Check the detailed error message for the possible causes.

ORA-19129: XQST0069: A static error is raised if a Prolog contains more than one empty order declaration

Cause: An error occurred during the processing of the XQuery expression.

Action: Check the detailed error message for the possible causes.

ORA-19130: XQST0070: A static error is raised if the predefined namespace prefix xml or xmlns is redeclared by a namespace declaration or namespace declaration attribute

Cause: An error occurred during the processing of the XQuery expression.

Action: Check the detailed error message for the possible causes.

ORA-19131: XQST0071: A static error is raised if the namespace declaration attributes of a direct element constructor do not have distinct names

Cause: An error occurred during the processing of the XQuery expression.

Action: Check the detailed error message for the possible causes.

ORA-19132: XQDY0072: It is a dynamic error if the result of the content expression of a computed comment constructor contains two adjacent hyphens or ends with a hyphen

Cause: An error occurred during the processing of the XQuery expression.

Action: Check the detailed error message for the possible causes.

ORA-19133: XQST0073: It is a static error if the graph of module imports contains a cycle (that is, if there exists a sequence of modules M1 ... Mn such that each Mi imports Mi+1 and Mn imports M1), unless all the modules in the cycle share a common namespace

Cause: An error occurred during the processing of the XQuery expression.

Action: Check the detailed error message for the possible causes.

ORA-19134: XQDY0074: It is a dynamic error if the value of the name expression in a computed element constructor cannot be converted to an expanded QName (for example, because it contains a namespace prefix not found in statically known namespaces.)

Cause: An error occurred during the processing of the XQuery expression.

Action: Check the detailed error message for the possible causes.

ORA-19135: XQST0075: An implementation that does not support the Validation Feature must raise a static error if it encounters a validate expression

Cause: An error occurred during the processing of the XQuery expression.

Action: Check the detailed error message for the possible causes.

ORA-19136: XQST0076: It is a static error if a collation subclause in an order by clause of a FLWOR expression does not identify a collation that is present in statically known collations

Cause: An error occurred during the processing of the XQuery expression.

Action: Check the detailed error message for the possible causes.

ORA-19137: XQST0079: It is a static error if an extension expression contains neither a pragma that is recognized by the implementation nor an expression enclosed in curly braces

Cause: An error occurred during the processing of the XQuery expression.

Action: Check the detailed error message for the possible causes.

ORA-19138: The target type of a cast or castable expression must be an atomic type that is in the in-scope schema types and is not xs:NOTATION or xs:anyAtomicType, optionally followed by the occurrence indicator "?"; otherwise a static error is raised

Cause: An error occurred during the processing of the XQuery expression.

Action: Check the detailed error message for the possible causes.

ORA-19139: XPST0081: It is a static error if a QName used in a query contains a namespace prefix that cannot be expanded into a namespace URI by using the statically known namespaces

Cause: An error occurred during the processing of the XQuery expression.

Action: Check the detailed error message for the possible causes.

ORA-19140: XPST0083: It is a static error if the target type of a cast expression or constructor function is xs:QName or a type derived from xs:QName or xs:NOTATION, and the argument of the cast expression or constructor function is not a string literal

Cause: An error occurred during the processing of the XQuery expression.

Action: Check the detailed error message for the possible causes.

ORA-19141: XQDY0084: It is a dynamic error if the element validated by a validate statement does not have a top-level element declaration in the in-scope element declarations, if validation mode is strict

Cause: An error occurred during the processing of the XQuery expression.

Action: Check the detailed error message for the possible causes.

ORA-19142: FONC0001 = FONC0001: undefined context item

Cause: An error occurred during the processing of the XQuery expression.

Action: Check the detailed error message for the possible causes.

ORA-19143: XQTY0086: It is a type error if the typed value of a copied element or attribute node is namespace-sensitive when construction mode is preserve and copy-namespaces mode is no-preserve

Cause: An error occurred during the processing of the XQuery expression.

Action: Check the detailed error message for the possible causes.

ORA-19145: XQST0087: It is a static error if the encoding specified in a Version Declaration does not conform to the definition of EncName specified in [XML 1.0]

Cause: An error occurred during the processing of the XQuery expression.

Action: Check the detailed error message for the possible causes.

ORA-19146: XQST0088: It is a static error if the literal that specifies the target namespace in a module import or a module declaration is of zero length

Cause: An error occurred during the processing of the XQuery expression.

Action: Check the detailed error message for the possible causes.

ORA-19147: XQST0089: It is a static error if a variable bound in a for clause of a FLWOR expression, and its associated positional variable, do not have distinct names (expanded QNames)

Cause: An error occurred during the processing of the XQuery expression.

Action: Check the detailed error message for the possible causes.

ORA-19148: XQST0090: It is a static error if a character reference does not identify a valid character in the version of XML that is in use

Cause: An error occurred during the processing of the XQuery expression.

Action: Check the detailed error message for the possible causes.

ORA-19149: XQDY0091: An implementation may raise a dynamic error if an xml:id error, as defined in [XML ID], is encountered during construction of an attribute named xml:id

Cause: An error occurred during the processing of the XQuery expression.

Action: Check the detailed error message for the possible causes.

ORA-19150: XQDY0092: An implementation may raise a dynamic error if a constructed attribute named xml:space has a value other than preserve or default

Cause: An error occurred during the processing of the XQuery expression.

Action: Check the detailed error message for the possible causes.

ORA-19151: XQST0093: It is a static error to import a module M1 if there exists a sequence of modules M1 ... Mi ... M1 such that each module directly depends on the next module in the sequence (informally, if M1 depends on itself through some chain of module dependencies.)

Cause: An error occurred during the processing of the XQuery expression.

Action: Check the detailed error message for the possible causes.

ORA-19152: FOCH0001 = FOCH0001: codepoint not valid

Cause: An error occurred during the processing of the XQuery expression.

Action: Check the detailed error message for the possible causes.

ORA-19153: FOCH0002: unsupported collation

Cause: An error occurred during the processing of the XQuery expression.

Action: Check the detailed error message for the possible causes.

ORA-19154: FOCH0003: unsupported normalization form

Cause: An error occurred during the processing of the XQuery expression.

Action: Check the detailed error message for the possible causes.

ORA-19155: FOCH0004: collation does not support collation units

Cause: An error occurred during the processing of the XQuery expression.

Action: Check the detailed error message for the possible causes.

ORA-19156: FODC0001: no context document

Cause: An error occurred during the processing of the XQuery expression.

Action: Check the detailed error message for the possible causes.

ORA-19157: FODC0002: error retrieving resource

Cause: An error occurred during the processing of the XQuery expression.

Action: Check the detailed error message for the possible causes.

ORA-19158: FODC0004: invalid argument to fn:collection()

Cause: An error occurred during the processing of the XQuery expression.

Action: Check the detailed error message for the possible causes.

ORA-19159: FODC0005: invalid argument to fn:doc

Cause: An error occurred during the processing of the XQuery expression.

Action: Check the detailed error message for the possible causes.

ORA-19160: XPST0003 - syntax error: invalid variable name string

Cause: The given XQuery variable does not begin with the '$' sign

Action: Fix the variable name to start with the "$" sign.

ORA-19161: XPTY0004 - XQuery type mismatch: invalid argument type 'string' for function 'string'

Cause: The type of the argument that was passed to the given function was not valid.

Action: Fix the argument to be of a type supported by the given function.

ORA-19162: XPTY0004 - XQuery type mismatch: invalid argument types 'string', 'string' for function 'string'

Cause: The type of the arguments that were passed to the given function was not valid.

Action: Fix the arguments to be of a type appropriate for the given function.

ORA-19163: XPTY0004 - XQuery type mismatch: argument type mismatch: expected - 'string' got - 'string' for function 'string'

Cause: The type of the arguments that were passed to the given function was not valid.

Action: Fix the arguments to be of a type appropriate for the given function.

ORA-19164: XQST0085 - It is a static error if the namespace URI in a namespace declaration attribute is a zero-length string, and the implementation does not support [XML Names 1.1].

Cause: There was a zero-length URI in namespace declaration.

Action: Fix the namespace declaration.

ORA-19165: FONS0003: no prefix defined for namespace

Cause: There was a zero-length URI in namespace declaration.

Action: Fix the namespace declaration.

ORA-19166: FONS0003: FONS0004: no namespace found for prefix

Cause: There was a zero-length URI in namespace declaration.

Action: Fix the namespace declaration.

ORA-19167: FONS0005: base uri not defined in the static context

Cause: There was a zero-length URI in namespace declaration.

Action: Fix the namespace declaration.

ORA-19168: FORG0002: invalid argument to fn:resolve-uri()

Cause: There was a zero-length URI in namespace declaration.

Action: Fix the namespace declaration.

ORA-19169: FORG0006: invalid argument type in 'string'

Cause: There was a zero-length URI in namespace declaration.

Action: Fix the namespace declaration.

ORA-19171: FORG0007: invalid argument to aggregate function

Cause: An error occurred during the processing of the XQuery expression.

Action: Check the detailed error message for the possible causes.

ORA-19172: FORG0008: both arguments to fn:dateTime have a specified timezone

Cause: An error occurred during the processing of the XQuery expression.

Action: Check the detailed error message for the possible causes.

ORA-19173: FORG0009: error in resolving a relative URI against a base URI in fn:resolve-uri

Cause: An error occurred during the processing of the XQuery expression.

Action: Check the detailed error message for the possible causes.

ORA-19174: FORX0001: invalid regular expression flags

Cause: An error occurred during the processing of the XQuery expression.

Action: Check the detailed error message for the possible causes.

ORA-19175: FORX0002: invalid regular expression

Cause: An error occurred during the processing of the XQuery expression.

Action: Check the detailed error message for the possible causes.

ORA-19176: FORX0003: regular expression matches zero-length string

Cause: An error occurred during the processing of the XQuery expression.

Action: Check the detailed error message for the possible causes.

ORA-19177: FORX0004: invalid replacement string

Cause: An error occurred during the processing of the XQuery expression.

Action: Check the detailed error message for the possible causes.

ORA-19178: FOTY0001: type error

Cause: An error occurred during the processing of the XQuery expression.

Action: Check the detailed error message for the possible causes.

ORA-19179: FOTY0011: Type error. Context item is not a node

Cause: An error occurred during the processing of the XQuery expression.

Action: Check the detailed error message for the possible causes.

ORA-19180: FOTY0012: argument node does not have a typed value

Cause: An error occurred during the processing of the XQuery expression.

Action: Check the detailed error message for the possible causes.

ORA-19181: FOTY0014: type exception

Cause: An error occurred during the processing of the XQuery expression.

Action: Check the detailed error message for the possible causes.

ORA-19182: FORT0001: invalid number of parameters

Cause: An error occurred during the processing of the XQuery expression.

Action: Check the detailed error message for the possible causes.

ORA-19183: FOTY0002: type definition not found

Cause: An error occurred during the processing of the XQuery expression.

Action: Check the detailed error message for the possible causes.

ORA-19184: FOTY0021: invalid node type

Cause: An error occurred during the processing of the XQuery expression.

Action: Check the detailed error message for the possible causes.

ORA-19185: FOAR0002: numeric operation overflow/unflow

Cause: An error occurred during the processing of the XQuery expression.

Action: Check the detailed error message for the possible causes.

ORA-19186: FOCA0001: input value too large for decimal

Cause: An error occurred during the processing of the XQuery expression.

Action: Check the detailed error message for the possible causes.

ORA-19187: FOCA0002: invalid lexical value

Cause: An error occurred during the processing of the XQuery expression.

Action: Check the detailed error message for the possible causes.

ORA-19188: FOCA0003: input value too large for integer

Cause: An error occurred during the processing of the XQuery expression.

Action: Check the detailed error message for the possible causes.

ORA-19189: FOCA0005: NaN supplied as float/double value

Cause: An error occurred during the processing of the XQuery expression.

Action: Check the detailed error message for the possible causes.

ORA-19190: FOER0000: Unidentified error

Cause: An error occurred during the processing of the XQuery expression.

Action: Check the detailed error message for the possible causes.

ORA-19191: FOAR0001: division by zero

Cause: An error occurred during the processing of the XQuery expression.

Action: Check the detailed error message for the possible causes.

ORA-19192: XQST0047: It is a static error if multiple module imports in the same Prolog specify the same target namespace

Cause: An error occurred during the processing of the XQuery expression.

Action: Check the detailed error message for the possible causes.

ORA-19193: XQST0045: It is a static error if the function name in a function declaration is in one of the following namespaces: http://www.w3.org/XML/1998/namespace, http://www.w3.org/2001/XMLSchema, http://www.w3.org/2001/XMLSchema-instance, http://www.w3.org/2005/04/xpath-functions, http://www.w3.org/2005/04/xpath-datatypes

Cause: An error occurred during the processing of the XQuery expression.

Action: Check the detailed error message for the possible causes.

ORA-19194: XQDY0026: It is a dynamic error if the result of the content expression of a computed processing instruction constructor contains the string "?>"

Cause: An error occurred during the processing of the XQuery expression.

Action: Check the detailed error message for the possible causes.

ORA-19200: Invalid column specification

Cause: All input arguments must be valid columns

Action: Specify a valid list of columns

ORA-19201: Datatype not supported

Cause: The particular datatype is not supported in the XMLGEN operator

Action: Specify only supported datatypes as arguments to the XMLGEN operator

ORA-19202: Error occurred in XML processingstring

Cause: An error occurred when processing the XML function

Action: Check the given error message and fix the appropriate problem

ORA-19203: Error occurred in DBMS_XMLGEN processingstring

Cause: An error occurred when processing the DBMS_XMLGEN functions

Action: Check the given error message and fix the appropriate problem

ORA-19204: Non-scalar value 'string' is marked as XML attribute

Cause: Only scalar values (i.e. values which are not of object or collection type) can be marked as XML attribute,i.e. is prefixed by '@'. In this case, a non-scalar value was prefixed with '@'

Action: Remove the '@' sign, or make the value a scalar.

ORA-19205: Attribute 'string' qualifies a non-scalar value in the select list

Cause: The attribute immediately follows a value of object or collection type in the select list or type definition.

Action: Remove the '@' sign, or make the previous value a scalar.

ORA-19206: Invalid value for query or REF CURSOR parameter

Cause: The queryString argument passed to DBMS_XMLGEN.newContext was not a valid query, or REF CURSOR.

Action: Rewrite the query so that the queryString argument is a valid query or REF CURSOR.

ORA-19207: scalar parameter string of XMLELEMENT cannot have an alias.

Cause: The scalar parameter to XMLELEMENT has been qualified with an alias.

Action: Remove the AS clause of the scalar element.

ORA-19208: parameter string of function string must be aliased

Cause: The indicated parameter of the XML generation function has not been aliased, although it is an expression.

Action: Specify an alias for the expression using the AS clause.

ORA-19209: invalid or unsupported formatting argument

Cause: An invalid or unsupported formatting argument was supplied

Action: Change the formatting argument to legal supported values

ORA Error . Listado Errores Oracle. ORA-16808 a ORA-19023

2013-06-17T12:50:00.002-07:00

ORA-16808: primary database is not open

Cause: A prior attempt to open the primary database was disallowed because the fast-start failover status could not be evaluated. The fast-start failover status has since been evaluated and the database can now be opened.

Action: Open the database by issuing the SQL*Plus ALTER DATABASE OPEN command.

ORA-16809: multiple warnings detected for the database

Cause: The broker detected multiple warnings for the database.

Action: Check the StatusReport monitorable property of the specifed database to get a detailed status report.

ORA-16810: multiple errors or warnings detected for the database

Cause: The broker detected multiple errors or warnings for the database.

Action: Check the StatusReport monitorable property of the specified database to get a detailed status report.

ORA-16811: apply instance not recorded by the Data Guard broker

Cause: The broker did not register an apply instance for a standby database.

Action: Reenable the standby database to clear the error.

ORA-16812: log apply service not running on apply instance recorded by the broker

Cause: Log apply services were not running on the instance the Data Guard broker expected them to be running upon.

Action: Reenable the standby database to clear the error.

ORA-16813: log apply service not running on apply instance string recorded by the broker

Cause: Log apply services were not running on the instance the Data Guard broker expected them to be running upon.

Action: Reenable the standby database to clear the error.

ORA-16814: incorrect redo transport setting for AlternateLocation for standby database

Cause: The Data Guard broker detected an incorrect redo transport setting for a standby database AlternateLocation property. The incorrect setting could be one of the following:

- The AlternateLocation property was empty, but the redo transport to the standby database had an ALTERNATE setting.

- The AlternateLocation property was not empty and the redo transport to the standby database had no ALTERNATE setting.

- The AlternateLocation property did not match the ALTERNATE setting in the redo transport. The mismatch may include service string, directory specification of the alternate location, or the DB_UNIQUE_NAME attribute.

- The LOG_ARCHIVE_DEST_STATE_n parameter corresponding to the alternate location was not set to ALTERNATE.

- The flash recovery area was being used by the standby database for archived logs, but the redo transport to the standby database still had an ALTERNATE setting for the AlternateLocation property. Data Guard broker logs provide more details on which of the above cases caused the error.

Action: Reenable the primary database to clear the error.

ORA-16815: incorrect redo transport setting for AlternateLocation for standby database "string"

Cause: The Data Guard broker detected an incorrect redo transport setting for a standby database AlternateLocation property. The incorrect setting could be one of the following:

- The AlternateLocation property was empty, but the redo transport to the standby database had an ALTERNATE setting.

- The AlternateLocation property was not empty and the redo transport to the standby database had no ALTERNATE setting.

- The LOG_ARCHIVE_DEST_STATE_n parameter corresponding to the alternate location was not set to ALTERNATE.

Action: Reenable the primary database to clear the error.

ORA-16816: incorrect database role

Cause: The Data Guard broker detected that the specified database had a database role that was different from the database role recorded in the Data Guard configuration. This could be the result of a failed switchover or failover operation, or an out-of-band switchover or failover operation done to the database.

Action: Manually fix the database to convert it to the appropriate database role, then issue an ENABLE DATABASE command to reenable the database.

ORA-16817: unsynchronized fast-start failover configuration

Cause: The fast-start failover target standby database was not synchronized with the primary database. As a result, a fast-start failover could not happen automatically in case of a primary database failure.

Action: Ensure that the fast-start failover target standby database is running and that the primary database can ship redo data to it. When the standby database has received all of the redo data from the primary database, the primary and standby databases will then be synchronized. The Data Guard configuration may then fail over automatically to the standby database in the event of loss of the primary database.

ORA-16818: fast-start failover suspended

Cause: The primary database was intentionally shutdown. As a result, a fast-start failover could not happen automatically.

Action: Start the primary database. This effectively restores the ability to automatically perform a fast-start failover in the event of a failure of the primary database.

ORA-16819: fast-start failover observer not started

Cause: The observer for fast-start failover was not started. As a result, fast-start failover could not happen in the case of a primary database failure.

Action: Start the fast-start failover observer by using, for example, the DGMGRL START OBSERVER command.

ORA-16820: fast-start failover observer is no longer observing this database

Cause: A previously started observer was no longer actively observing this database. A significant amount of time elapsed since this database last heard from the observer. Possible reasons were:

- The host where the observer was running was not available.

- The network connection between the observer and this database was not available.

- The observer process was terminated unexpectedly.

Action: Check the reason why the observer cannot contact this database. If the problem cannot be corrected, stop the current observer by connecting to the Data Guard configuration and issue the DGMGRL STOP OBSERVER command. Then, restart the observer on another host. Finally, use the DGMGRL START OBSERVER command to start the observer on the other host.

ORA-16821: logical standby database dictionary not yet loaded

Cause: The logical standby database had not loaded the dictionary. This status was detected by the broker health check mechanism. Alternatively, this status may be returned when attempting to switch or fail over to a logical standby database that had not yet loaded its dictionary.

Action: Start SQL Apply on the logical standby database, if it is not already running, and wait for it to reach the APPLYING state.

ORA-16822: new primary database not yet ready for standby database reinstatement

Cause: The new primary database, as a result of a logical standby database failover operation, had not fully completed the failover operation. An attempt to reinstate a disabled standby database could not be completed until failover completed on the new primary database.

Action: Wait until the failover operation has completed on the new primary database. Then retry the reinstate operation.

ORA-16823: redo transport mode is incompatible for current operation

Cause: The redo transport mode of this database was incompatible for this broker operation.

Action: Reset the LogXptMode database property for this database and retry the broker operation.

ORA-16824: multiple warnings, including fast-start failover-related warnings, detected for the database

Cause: The broker detected multiple warnings for the database. At least one of these warnings may have prevented fast-start failover from occurring.

Action: Check the StatusReport monitorable property of the database specified.

ORA-16825: multiple errors or warnings, including fast-start failover-related errors or warnings, detected for the database

Cause: The broker detected multiple errors or warnings for the database. At least one of these errors or warnings may have prevented a fast-start failover from occurring.

Action: Check the StatusReport monitorable property of the database specified.

ORA-16826: apply service state is inconsistent with the DelayMins property

Cause: This warning was caused by one of the following reasons:

- The apply service was started without specifying the real-time apply option or without the NODELAY option when the DelayMins property was set to zero.

- The apply service was started with the real-time apply option or with the NODELAY option when the DelayMins property was set to a value greater than zero.

Action: Reenable the standby database to allow the broker to restart the apply service with the apply options that are consistent with the specified value of the DelayMins property.

ORA-16827: Flashback Database is disabled

Cause: The broker detected that the Flashback Database feature was disabled. With Flashback Database disabled, the broker would not be able to:

- reinstate a database that required reinstatement.

- convert a physical standby database to a snapshot standby database.

- convert a snapshot standby database to a physical standby database. Flashback Database may been disabled manually with the ALTER DATABASE FLASHBACK DATABASE OFF command or automatically by the database in the event of an error.

Action: Check the database alert log to determine whether Flashback Database was disabled due to errors and then correct the problem. If Flashback Database had been manually disabled, reenable Flashback Database with the ALTER DATABASE FLASHBACK DATABASE ON command. If, after enabling Flashback Database, the database still cannot be reinstated or converted, you must re-create the database from a copy of the primary database.

ORA-16828: invalid value specified for REDO_TRANSPORT_USER initialization parameter

Cause: An invalid value was specified for the REDO_TRANSPORT_USER initialization parameter. The length of the user name exceeded 30 characters.

Action: Check the documentation and specify a new value for the REDO_TRANSPORT_USER initialization parameter.

ORA-16829: fast-start failover configuration is lagging

Cause: The fast-start failover target standby database was not within the lag limit specified by the FastStartFailoverLagLimit configuration property. As a result, a fast-start failover could not happen in the event of a primary database failure.

Action: Ensure that the fast-start failover target standby database is running and applying redo data and that the primary database is successfully trasmitting redo data. If this condition persists consider raising the value of the FastStartFailoverLagLimit configuration property.

ORA-16830: primary isolated from fast-start failover partners longer than FastStartFailoverThreshold seconds: shutting down

Cause: The primary database was isolated from both the observer and target standby database for longer than the seconds specified by the FastStartFailoverThreshold property. A fast-start failover probably occurred. If the FastStartFailoverPmyShutdown configuration property was set to TRUE, the broker will shut down the primary database in this situation.

Action: Ensure one instance of this database is running and the database is mounted on that instance so that the broker may reinstate the old primary database.

ORA-16831: operation disallowed on this standby database type

Cause: The Data Guard broker operation was disallowed on the standby database type.

Action: Check the documentation for the correct standby database type and reissue the Data Guard broker command to another standby database that is of the correct standby database type.

ORA-16950: Remote mapped cursors are not supported by this feature.

Cause: This cursor is a remote mapped cursor which could not be processed locally.

Action: Try to process this statement directly on the remote site.

ORA-16951: Too many bind variables supplied for this SQL statement.

Cause: Binding this SQL statement failed because too many bind variables were supplied.

Action: Pass the correct number of bind variables.

ORA-16952: Failed to bind this SQL statement.

Cause: Binding this SQL statement failed.

Action: Check if bind variables for that statement are properly specified.

ORA-16953: Type of SQL statement not supported.

Cause: This type of SQL statement could not be processed.

Action: None

ORA-16954: SQL parse error.

Cause: The specified SQL statement failed to be parsed.

Action: Check if syntax is correct and ensure that this statement can be parsed by the specified user name.

ORA-16955: Unknown error during SQL analyze.

Cause: The specified SQL statement failed to be analyzed.

Action: This is an internal error, please contact Oracle support.

ORA-16956: Only SELECT or DML statements are supported for test execute.

Cause: The specified SQL statement cannot be tested for execute.

Action: None

ORA-16957: SQL Analyze time limit interrupt

Cause: This is an internal error code used indicate that SQL analyze has reached its time limit.

Action: None

ORA-16958: DML statements running parallel are not supported for test execute.

Cause: The specified DML statement cannot be tested for execute because part of it is running parallel.

Action: None

ORA-16959: Statement type has been disabled for SQL Analyze

Cause: The system attempted to analyze a type of statement that was disabled by the current feature.

Action: Try a different feature capable of analyzing this statement type.

ORA-16960: SQL Analyze could not reproduce the desired plan.

Cause: SQL Analyze failed to reproduce a particular plan using an outline.

Action: Check the outline data.

ORA-16961: SQL statement with SQL patch is ignored

Cause: SQL statements with SQL patches are not supported by SQL tuning advisor.

Action: Check the SQL patch information. Rerun SQL repair advisor on that SQL statement for a potential better SQL patch.

ORA-17500: ODM err:string

Cause: An error returned by ODM library

Action: Look at error message and take appropriate action or contact Oracle Support Services for further assistance

ORA-17501: logical block size string is invalid

Cause: logical block size for oracle files must be a multiple of the physical block size, and less than the maximum

Action: check INIT.ORA file parameters

ORA-17502: ksfdcre:string Failed to create file string

Cause: file creation failed due to either insufficient OS permission or the file already exists

Action: check additional error messages

ORA-17503: ksfdopn:string Failed to open file string

Cause: file open failed due to either insufficient OS permission or the name of file exceeds maximum file name length.

Action: check additional error messages

ORA-17504: ksfddel:Failed to delete file string

Cause: The file that was being deleted is still in use or the process has insufficient permission to delete file.

Action: check additional error messages

ORA-17505: ksfdrsz:string Failed to resize file to size string blocks

Cause: There is insufficient space left on the device or the process has insufficient permission to resize file.

Action: check additional error messages

ORA-17506: I/O Error Simulation

Cause: The i/o request is marked with error because the i/o error simulation event is turned on.

Action: None

ORA-17507: I/O request size string is not a multiple of logical block size

Cause: i/o's are done in multiple of logical block size

Action: Check additional error messages

ORA-17508: I/O request buffer ptr is not alligned

Cause: i/o request buffer should be alligned, check additional information for buffer ptr value

Action: Call Oracle Support Services

ORA-17509: Attempt to do i/o beyond block1 offset

Cause: When a file is identified with logical block size of 0, only i/o's to block1 is allowed.

Action: check additional error messages and call Oracle Support Services

ORA-17510: Attempt to do i/o beyond file size

Cause: The i/o request points to a block beyond End Of File

Action: check additional error messages and call Oracle Support Services

ORA-17512: Block Verification Failed

Cause: Block Verification after a read operation on a database file failed since the block is media corrupt.

Action: check additional error messages in the trace file and call Oracle Support Services

ORA-17610: file 'string' does not exist and no size specified

Cause: An attempt to create a file found neither an existing file nor a size for creating the file.

Action: Specify a size for the file.

ORA-17611: ksfd: file 'string' cannot be accessed, global open closed

Cause: An attempt to write to a file which has gone offline/unidentified

Action: Check for other errno in the stack

ORA-17612: Failed to discover Oracle Disk Manager library, return value string

Cause: Discovery of the odm library by calling odm_discover() failed

Action: Contact your storage vendor who has provided the ODM library or call Oracle Support

ORA-17613: Failed to initialize Oracle Disk Manager library: string

Cause: ODM initialization for the thread failed due to insufficient previlige or memory.

Action: Make sure there is enough system resources available for the oracle process and it has access to the ODM library

ORA-17618: Unable to update block 0 to version 10 format

Cause: An attempt was made to update block 0 to version 10 format.

Action: Check additional error messages and call Oracle Support Services

ORA-17619: max number of processes using I/O slaves in a instance reached

Cause: An attempt was made to start large number of processes requiring I/O slaves.

Action: There can be a maximum of 35 processes that can have I/O slaves at any given time in a instance.

ORA-17620: failed to register the network adapter with Oracle Disk Manager library: string

Cause: The ODM library returned an error while trying to register the network adapter.

Action: Make sure the network adapter name given in the fileio_network_adapters is a valid name, and that the Oracle user has the correct access privileges.

ORA-17621: failed to register the memory with Oracle Disk Manager library

Cause: The ODM library returned an error while trying to register the memory.

Action: Contact the Oracle Disk Manager Library provider.

ORA-17622: failed to deregister the memory with Oracle Disk Manager library

Cause: The ODM library returned an error while trying to deregister the memory.

Action: Contact the Oracle Disk Manager Library provider

ORA-17624: Failed to delete directory string

Cause: The directory that was being deleted is still in use or the process had insufficient permission to delete the directory.

Action: check additional error messages.

ORA-17626: ksfdcre: string file exists

Cause: trying to create a database file, but file by that name already exists

Action: verify that name is correct, specify REUSE if necessary

ORA-17627: string

Cause: An error returned by OCI while sending/receiving message from remote instance

Action: Look at error message and take appropriate action or contact Oracle Support Services for further assistance

ORA-17628: Oracle error string returned by remote Oracle server

Cause: Oracle server on the remote instance has returned an error.

Action: Look at remote instance alert log/trace file for more information and take appropriate action or contact Oracle Support Services for further assistance

ORA-17629: Cannot connect to the remote database server

Cause: Connecting to the remote server specified by database connect string for netowrk file transfer failed.

Action: Check additional error messages

ORA-17630: Mismatch in the remote file protocol version client string server string

Cause: Cannot communicate with the remote database server as there is a mismatch in the Oracle file protocol version.

Action: Check additional error messages

ORA-17631: dbname 'string' specified by remote server does not match the instance name 'string'

Cause: The dbname specified by the remote server is not intended for this instance.

Action: Check the dbname specified in the command of the remote instance and look for further error messages.

ORA-17632: file 'string' is a formatted ASM disk

Cause: An attempt to create a datafile on a device that was formatted for ASM disk failed.

Action: Check that the device specified is not an ASM disk. If you would like to use the disk for datafiles, please clear the disk before you retry the operation.

ORA-18000: invalid outline name

Cause: The parser detected a missing or invalid outline name

Action: None

ORA-18001: no options specified for ALTER OUTLINE

Cause: The parser detected that no clause was specified on the command Our performance tests, which are not typical as they exercise all branches of the code, have shown approximately a 30% performance increase line for ALTER OUTLINE.

Action: Re-issue the command, specifying a valid ALTER OUTLINE clause.

ORA-18002: the specified outline does not exist

Cause: Either the outline did not exist to begin with, or a timing window allowed for another thread to drop or alter the outline midstream.

Action: None

ORA-18003: an outline already exists with this signature

Cause: The signature generation algorithm generates signatures that are are 16 bytes in length so it is highly unlikely that any 2 signatures will be identical. This message is raised in such a rare case.

Action: Either re-issue the statement that led to the outline being created with some whitespace added or force the outline to be created in a different category.

ORA-18004: outline already exists

Cause: An outline already exists, either with the specified name, or for the specified SQL text.

Action: None

ORA-18008: cannot find OUTLN schema

Cause: The database creation script that creates this schema must not have been executed.

Action: Review the log files to see what happened when the database was created.

ORA-18009: one or more outline system tables do not exist

Cause: Either the database creation script that creates these tables was not executed or a user accidently deleted the table

Action: Review the log files to see what happened when the database was created.

ORA-18010: command missing mandatory CATEGORY keyword

Cause: User failed to specify the CATEGORY keyword

Action: Re-issue the command with the CATEGORY keyword included

ORA-18015: invalid source outline signature

Cause: User imported an 8i outline into a 9i database without updating signatures

Action: execute dbms_outln.update_signatures

ORA-19000: missing RELATIONAL keyword

Cause: The keyword RELATIONAL in the work OBJECT RELATIONAL is missing in the XMLTYPE storage clause specification.

Action: Supply the RELATIONAL keyword in the storage clause

ORA-19001: Invalid storage option specified

Cause: An invalid storage option was specified for the XMLType.

Action: Supply a valid storage option.

ORA-19002: Missing XMLSchema URL

Cause: A XML schema URL must be specified in the storage option.

Action: Specify a URL for the XMLSchema.

ORA-19003: Missing XML root element name

Cause: A root element in the XMLSchema must be specified if the XML schema is given.

Action: Specify a root element in the XML schema.

ORA-19004: Duplicate XMLType OBJECT RELATIONAL storage option

Cause: A duplicate storage option for the XMLType column was specified

Action: Specify a single storage option for an XMLType column

ORA-19005: Duplicate XMLType LOB storage option

Cause: A duplicate storage option for the XMLType column was specified

Action: Specify a single storage option for an XMLType column

ORA-19006: XMLType TYPE storage option not appropriate for storage type

Cause: The TYPE option can only be used in case of OBJECT RELATIONAL storage option

Action: Remove the TYPE option or specify an OBJECT RELATIONAL storage for the XMLType column

ORA-19007: Schema string does not match expected string.

Cause: The given XML document conformed to a different schema than expected.

Action: Insert/Update only the XML documents that conform to that particular schema.

ORA-19008: Invalid version of the XMLType

Cause: An invalid version of the XMLType was found.

Action: This is possible due to data corruption or an internal error or running an older client against a newer version of the database. Make sure that the version of the client can understand the XMLType in the database.

ORA-19009: Missing XMLSchema keyword

Cause: The XMLSchema keyword is missing

Action: Specify the XMLSchema URL and element name.

ORA-19010: Cannot insert XML fragments

Cause: XML fragments got from extractNode cannot be inserted into the database.

Action: Convert the fragment into a proper XML document before insertion.

ORA-19011: Character string buffer too small

Cause: The string result asked for is too big to return back

Action: Get the result as a lob instead

ORA-19012: Cannot convert XML fragment to the required datatype

Cause: A conversion to a datatype was requested which cannot be performed

Action: The XMLType may contain fragments and other elements which cannot be converted to the appropriate datatype.

ORA-19013: Cannot create VARRAY columns containing XMLType

Cause: An attempt was made to create a VARRAY column which contains a XMLType

Action: You cannot store VARRAYs containing XMLTypes in tables. Use nested tables instead

ORA-19015: Invalid XML tag identifier (string)

Cause: An invalid XML identifer was detected during XML generation

Action: Fix the offending tag to not contain characters or symbols that are not allowed by the XML specification

ORA-19016: attributes cannot occur after element specifications

Cause: Attributes specified using the "@" identifier can only occur before any other element definition when creating XML

Action: Change the order of the types so that the attributes occur in the begining

ORA-19017: Attributes can only be simple scalars

Cause: Attribute values can only be simple scalar values

Action: Use only simple datatypes for attribute values

ORA-19018: Invalid character in XML tag 'string'

Cause: A tag name was found to have an invalid XML character during XML generation.

Action: Rewrite the query so that the generated XML tag, corresponding to a column name or alias, contains only valid characters.

ORA-19019: Invalid context passed to DBMS_XMLGEN.GETXML

Cause: The value of context passed to GETXML was invalid.

Action: Rewrite the query so that the value of context passed to GETXML is valid.

ORA-19020: invalid dereference of XMLType columns

Cause: An attempt was made to dereference the attributes of an XMLType column which is not part of a base table

Action: You can only dereference the attributes of a base table XMLType column

ORA-19023: The first argument to UPDATEXML operator has to be an XMLTYPE

Cause: The first argument passed to the update value operator was not an XMLTYPE.

Action: Rewrite the query so that the first argument to the UPDATEXML operator is XMLTYPE.

ORA Error . Listado Errores Oracle. ORA-16706 a ORA-16807

2013-06-17T12:47:00.000-07:00

ORA-16706: no resource guard is available

Cause: Resource guard was not available to service the request.

Action: Contact Oracle Support Services.

ORA-16707: the value of the property string is invalid, valid values are string

Cause: An invalid property value was entered while broker management of the database was disabled.

Action: Reset the property to a valid value.

ORA-16708: the state supplied to broker is invalid

Cause: The state name specified was invalid for the database.

Action: Check the state name and reissue the request.

ORA-16709: standby archived log location settings conflict with database recovery area

Cause: The StandbyArchiveLocation or AlternateLocation property was set to USE_DB_RECOVERY_FILE_DEST, but the initialization parameter DB_RECOVERY_FILE_DEST did not specify a valid destination.

Action: Use a value other than USE_DB_RECOVERY_FILE_DEST for StandbyArchiveLocation or AlternateLocation, or set up a valid database recovery area by setting DB_RECOVERY_FILE_DEST to a valid destination.

ORA-16713: the Data Guard broker command timed out

Cause: The Data Guard broker timed out the command.

Action: Verify that the command is valid for the database and then retry the command.

ORA-16714: the value of property string is inconsistent with the database setting

Cause: The value of the specified configuration property was inconsistent with database in-memory settings or server parameter file settings. This may be caused by changing an initialization parameter that corresponds to a configuration property.

Action: Query the InconsistentProperties property on the database to determine the which properties are set inconsistently. Reset the properties to make them with the database settings.

ORA-16715: redo transport-related property string of standby database "string" is inconsistent

Cause: The value of the specified redo transport-related configuration property of the given standby database was inconsistent with the primary database redo transport service setting. This may be caused by changing an initialization parameter that corresponds to a configuration property.

Action: Query the InconsistentLogXptProps property on the primary database to determine which redo transport properties are set inconsistently Reset the properties on the standby database to make them consistent with the primary database redo transport settings.

ORA-16716: clearing parameter LOG_ARCHIVE_DEST failed

Cause: An attempt to clear the LOG_ARCHIVE_DEST parameter failed.

Action: Contact Oracle Support Services.

ORA-16717: clearing parameter LOG_ARCHIVE_DUPLEX_DEST failed

Cause: An attempt to clear the LOG_ARCHIVE_DUPLEX_DEST parameter failed.

Action: Contact Oracle Support Services.

ORA-16718: failed to locate database

Cause: The Data Guard broker was unable to locate the database in the broker configuration.

Action: Add the database to the broker configuration and then reissue the command.

ORA-16719: unable to query V$ARCHIVE_DEST fixed view

Cause: The broker failed to query the V$ARCHIVE_DEST fixed view."

Action: Test and clear the problem using SQL*Plus.

ORA-16720: no LOG_ARCHIVE_DEST_n initialization parameters available

Cause: All LOG_ARCHIVE_DEST_n initialization parameters were in use.

Action: Clear one or more LOG_ARCHIVE_DEST_n initialization parameters so that broker can use them to setup the primary database redo transport.

ORA-16721: unable to set LOG_ARCHIVE_DEST_n initialization parameters

Cause: The broker was unable to set one or more LOG_ARCHIVE_DEST_n initialization parameters.

Action: Check the Data Guard broker log and Oracle alert logs for more details.

ORA-16722: unable to set LOG_ARCHIVE_DEST_STATE_n initialization parameters

Cause: The broker was unable to set one or more LOG_ARCHIVE_DEST_STATE_n initialization parameters.

Action: Check the Data Guard broker log and Oracle alert logs for more details.

ORA-16723: setting AlternateLocation property conflicts with the redo transport setting

Cause: The standby database was not using standby redo logs, and the redo transport service to the standby database is set to a nonzero value for the ReopenSecs property and a value of zero for the MaxFailure property. In this case, the redo transport service will attempt to send redo data to the standby database indefinitely and never switch to the alternate destination.

Action: Any one of the following actions will solve the problem:

- add standby redo logs to the standby database.

- set ReopenSecs property to zero.

- set MaxFailure property to a nonzero value. After performing one of the above actions, reset the standby database AlternateLocation property.

ORA-16727: cannot close database

Cause: The Data Guard broker could not close the database.

Action: Terminate any active sessions connected to the database and then reissue the request.

ORA-16728: consistency check for property string found string error

Cause: The consistency check for the specified property failed due to the error shown.

Action: Check the error message and clear the error.

ORA-16729: validation of value for property string found string error

Cause: The property value validation failed due to the error shown.

Action: Check the error message and clear the error.

ORA-16730: error executing DBMS_LOGSTDBY.SKIP_TXN procedure

Cause: Logical standby database package may not be installed.

Action: Install logical standby database packages and reissue the request.

ORA-16731: error executing DBMS_LOGSTDBY.UNSKIP_TXN procedure

Cause: Logical standby database package may not be installed.

Action: Install logical standby database packages and reissue the request.

ORA-16732: error executing DBMS_LOGSTDBY.SKIP procedure

Cause: Logical standby database package may not be installed.

Action: Install logical standby database packages and reissue the request.

ORA-16733: error executing DBMS_LOGSTDBY.UNSKIP procedure

Cause: Logical standby database package may not be installed.

Action: Install logical standby database packages and reissue the request.

ORA-16734: error executing DBMS_LOGSTDBY.SKIP_ERROR procedure

Cause: Logical standby database package may not be installed.

Action: Install logical standby database packages and reissue the request.

ORA-16735: error executing DBMS_LOGSTDBY.UNSKIP_ERROR procedure

Cause: Logical standby database package may not be installed.

Action: Install logical standby database packages and reissue the request.

ORA-16736: unable to find the destination entry of standby database "string" in V$ARCHIVE_DEST

Cause: Either the standby destination was manually changed or deleted outside of Data Guard broker, or no entry was available for the Data Guard broker to use.

Action: Clean up the destination setting, remove the unused settings, and reset the redo transport service.

ORA-16737: the redo transport service for standby database "string" has an error

Cause: A communication problem with the standby database caused the redo transport to fail.

Action: Query the LogXptStatus property to see the error message. Check the Data Guard broker log and Oracle alert log for more details.

ORA-16738: redo transport service for database "string" is not running

Cause: The redo transport service for the specified standby database was not running.

Action: Check the Data Guard broker log and/or the alert log for more details. If necessary, start the redo transport service for the standby database.

ORA-16739: redo transport service for standby database "string" is running

Cause: The redo transport service for the standby database was running.

Action: Check the Data Guard broker log for more details. If necessary, stop the redo transport service for the standby database.

ORA-16740: redo transport service for standby database "string" incorrectly set to ALTERNATE

Cause: The redo transport service to the standby database was set to ALTERNATE when no other destination was set to alternate to this destination.

Action: Reenable the standby database or the entire configuration to allow the configuration property settings to be propagated to the initialization parameters.

ORA-16741: the destination parameter of standby database "string" has incorrect syntax

Cause: The destination defined in the server parameter file of the primary database had incorrect syntax and Data Guard broker failed to update the destination when redo transport services were enabled.

Action: Fix the syntax error in the primary database server parameter file or remove the entry from the server parameter file. Also, check the values of the redo transport-related properties for the specified standby database.

ORA-16742: the standby database "string" has exhausted its quota

Cause: The standby database exhausted its quota for storing archived redo logs.

Action: Remove some archived redo logs from the standby database or increase its quota.

ORA-16743: cannot determine status of redo transport service for standby database "string"

Cause: The status of redo transport to the specified standby database could not be determined.

Action: Check the Data Guard broker log and Oracle alert log for more details.

ORA-16744: the DG_CONFIG list of LOG_ARCHIVE_CONFIG parameter is full

Cause: The DG_CONFIG list of the LOG_ARCHIVE_CONFIG attribute was full and the Data Guard broker was not able to add a new DB_UNIQUE_NAME to the list.

Action: Remove some unused entries in the DG_CONFIG list, then reenable the database.

ORA-16745: unable to add DB_UNIQUE_NAME "string" into the DG_CONFIG list because it is full

Cause: The DG_CONFIG list of the LOG_ARCHIVE_CONFIG attribute was full and the Data Guard broker was not able to add the specified DB_UNIQUE_NAME to the list.

Action: Remove some unused entries in the DG_CONFIG list, then reenable the database.

ORA-16746: Data Guard broker cannot mount the database

Cause: The Data Guard broker failed to mount the database."

Action: Check the Data Guard broker log and Oracle alert log for more details.

ORA-16747: logical standby database guard could not be turned on

Cause: The Data Guard broker could not turn on the logical standby database guard.

Action: Check the Data Guard broker log and Oracle alert log for more details.

ORA-16748: Data Guard broker cannot open the primary database

Cause: The Data Guard broker failed to open the primary database" the database.

Action: Check the Data Guard broker log and Oracle alert log for more details.

ORA-16749: switchover to logical standby database failed

Cause: The Data Guard broker failed to switch a logical standby database over to a primary database.

Action: Check the Data Guard broker log and Oracle alert log for more details.

ORA-16750: failed to activate logical standby database

Cause: The Data Guard broker failed to activate a logical standby database.

Action: Check the Data Guard broker log and Oracle alert log for more details.

ORA-16751: failed to switchover to physical standby database

Cause: The Data Guard broker failed to switch a physical standby database over to a primary database.

Action: Check the Data Guard broker log and Oracle alert log for more details.

ORA-16753: Data Guard broker cannot open standby database

Cause: The Data Guard broker failed to open the standby database.

Action: Check the Data Guard broker log and Oracle alert log for more details.

ORA-16754: failed to activate physical standby database

Cause: The Data Guard broker failed to activate the physical standby database.

Action: Check the Data Guard broker log and Oracle alert log for more details.

ORA-16755: failed to set initialization parameter

Cause: The Data Guard broker failed to set an initialization parameter using either the ALTER SYSTEM SET or ALTER SYSTEM RESET command.

Action: Check the Data Guard broker log and Oracle alert log for more details.

ORA-16757: unable to get this property's value

Cause: The Data Guard broker failed to get the value for the specified property, possibly because the specified property's value is not available for the current database role.

Action: If the specified property's value is not available for the database's current role, please specify this property for a database for which it is available. Otherwise, check the Data Guard broker log for more details.

ORA-16758: the specified apply instance is not running

Cause: The Data Guard broker could not start apply services on the specified instance because that instance was not running.

Action: Start the instance and then retry the command.

ORA-16759: cannot start SQL Apply with initial SCN

Cause: The Data Guard broker failed to start SQL Apply with an initial SCN.

Action: Check the Data Guard broker log and Oracle alert log for more details.

ORA-16760: cannot start SQL Apply

Cause: The Data Guard broker failed to start SQL Apply.

Action: Check the Data Guard broker log and Oracle alert log for more details.

ORA-16761: cannot stop SQL Apply

Cause: The Data Guard broker failed to stop SQL Apply.

Action: Check the Data Guard broker log and Oracle alert log for more details.

ORA-16762: invalid database state

Cause: Database was not in the intended state.

Action: Determine the reason why the database is not running in the intended state and reissue the command.

ORA-16763: redo transport service for a standby database is running

Cause: The redo transport service for a standby database was running.

Action: Query the StatusReport property of the primary database for more details. If necessary, stop the redo transport service for the database.

ORA-16764: redo transport service to a standby database is not running

Cause: The redo transport service to a standby database was not running.

Action: Query the StatusReport property of the primary database for more details. If necessary, start the redo transport service.

ORA-16765: Redo Apply is running

Cause: Redo Apply was running when it should have been stopped.

Action: If necessary, stop Redo Apply.

ORA-16766: Redo Apply is stopped

Cause: Redo Apply was stopped when it should have been running.

Action: If necessary, start Redo Apply.

ORA-16767: SQL Apply is running

Cause: SQL Apply was running when it should have been stopped."

Action: If necessary, stop SQL Apply.

ORA-16768: SQL Apply is stopped

Cause: SQL Apply was stopped when it should have been running."

Action: If necessary, start SQL Apply.

ORA-16769: the physical standby database is open read-only

Cause: All instances in the physical standby database were put into a read-only state instead of APPLY-OFF.

Action: Issue the EDIT DATABASE SET STATE command to set the database to the APPLY-OFF state.

ORA-16770: Redo Apply not started since physical standby database is opening

Cause: Redo Apply services could not be started on the physical standby database because it was being opened. The Data Guard broker will start Redo Apply services once the physical standby database has been opened.

Action: No action required.

ORA-16771: failover to a physical standby database failed

Cause: The Data Guard broker encountered errors when converting a physical standby database to a primary database.

Action: Check the Data Guard broker log and the Oracle alert log for more details about the error.

ORA-16772: switchover to a standby database failed

Cause: The Data Guard broker encountered errors when switching over to the specified standby database.

Action: Check the Data Guard broker log and Oracle alert log for more details.

ORA-16773: cannot start Redo Apply

Cause: The Data Guard broker failed to start Redo Apply.

Action: Check the Data Guard broker log and Oracle alert log for more details. If the database is already open, the broker will not be able to start Redo Apply if the COMPATIBLE initialization parameter is set to a value less than 11.0.

ORA-16774: cannot stop Redo Apply

Cause: The Data Guard broker failed to stop Redo Apply.

Action: Check the Data Guard broker log and Oracle alert log for more details.

ORA-16775: target standby database in broker operation has potential data loss

Cause: The target standby database specified for the broker operation did not have all the redo data from the primary database.

Action: Confirm that the redo transport service on the primary database is functioning correctly by checking its status using the StatusReport monitorable property. Reissue the broker command once all redo data is available on the target standby database.

ORA-16776: health check of the redo transport service failed

Cause: The Data Guard broker could not complete the health check for the redo transport service.

Action: Check the Data Guard broker log and Oracle alert log for more details.

ORA-16777: unable to find the destination entry of a standby database in V$ARCHIVE_DEST

Cause: Either a destination was manually deleted or no entry was available for Data Guard.

Action: Check the Data Guard broker log and the Oracle alert log for more details. The redo transport service may need to be reset.

ORA-16778: redo transport error for one or more databases

Cause: The redo transport service was unable to send redo data to one or more standby databases.

Action: Check the Data Guard broker log and Oracle alert log for more details. Query the LogXptStatus property to see the errors.

ORA-16779: the destination parameter of a database is set incorrectly

Cause: The destination was defined in the LOG_ARCHIVE_DEST_n server parameter file with incorrect syntax. The Data Guard broker failed to update the destination when the redo transport was turned on.

Action: Check the Data Guard broker log to see which database has the problem. Fix the syntax error in the server parameter file or remove the entry from the server parameter file. Check if the syntax of the redo transport-related properties are correct.

ORA-16780: a database has exhausted its archived redo log storage quota

Cause: A database has exhausted its quota for storing archived redo logs.

Action: Check the Data Guard broker log to see which database has the problem. Remove some archived logs at the standby database or increase its quota.

ORA-16781: cannot determine status of redo transport service for standby database

Cause: The status of redo transport to the specified standby database could not be determined.

Action: Check the Data Guard broker log and Oracle alert log for more details.

ORA-16782: instance not open for read and write access

Cause: The database was mounted on an instance but not opened for read and write access.

Action: Check the StatusReport property for more details and, if possible, open the instance manually.

ORA-16783: instance string not open for read and write access

Cause: The database was mounted on an instance but not opened for read and write access.

Action: Check the StatusReport property for more details and, if possible open the instance manually.

ORA-16784: database name specified by Dependency property is incorrect

Cause: The database name, that should be the value of the DB_UNIQUE_NAME initialization parameter, specified in the Dependency property was incorrect.

Action: Reset the Dependency property to the correct name of the database.

ORA-16785: the database is in NOARCHIVELOG mode

Cause: The database was in NOARCHIVELOG mode when it was either a primary database or when it was a standby database that was being switched over to be a primary database.

Action: Set the database to ARCHIVELOG mode by issuing the ALTER DATABASE ARCHIVELOG command.

ORA-16786: unable to access Data Guard broker metadata

Cause: The Data Guard broker configuration files did not exist or for some other reason the Data Guard broker configuration metadata could not be accessed.

Action: Check the Data Guard broker log for more details.

ORA-16788: unable to set one or more database configuration property values

Cause: This situation occurred when the broker attempted to set database configurable property values into the database by issuing ALTER SYSTEM or ALTER DATABASE commands. Typical causes of this error are:

- The values of redo transport-related properties contain syntax syntax errors.

- The value of the LogArchiveTrace property was out of range.

Action: Check the Data Guard broker log to see which property has the problem and set the property to the correct value.

ORA-16789: standby redo logs not configured

Cause: Standby redo logs were not configured for the database.

Action: Standby redo logs are required when the redo transport mode is set to SYNC or ASYNC. Check the Data Guard documentation to see how to create standby redo logs.

ORA-16790: the value of the configurable property is invalid

Cause: An invalid property value was entered.

Action: Reset the property to a correct value.

ORA-16791: unable to check the existence of the standby redo logs

Cause: The database may not be mounted, or the query of the V$STANDBY_LOG fixed view failed.

Action: Ensure the database is mounted and query the V$STANDBY_LOG fixed view to see if the problem has been corrected, and retry the operation.

ORA-16792: configurable property value is inconsistent with database setting

Cause: The values of one or more configurable properties were inconsistent with database in-memory settings or server parameter file settings. This may happen by directly altering initialization parameters instead of editing configurable property values using Data Guard broker.

Action: Query the InconsistentProperties property on the database or check the Data Guard broker log to find which properties are set inconsistently. Reset these properties to make them consistent with the database settings. Alternatively, enable the database or the entire configuration to allow the configurable property settings to be propagated to the initialization parameters.

ORA-16793: logical standby database guard is off

Cause: The logical standby database guard was turned off.

Action: Issue the ALTER DATABASE GUARD ALL command to turn the guard on and verify that Data Guard health check error or warning is cleared.

ORA-16794: database guard is on for primary database

Cause: The database guard was turned on for the primary database.

Action: Issue the ALTER DATABASE GUARD NONE command to turn off the guard and verify that Data Guard health check error or warning is cleared.

ORA-16795: the standby database needs to be re-created

Cause: A switchover or failover operation caused this database to require re-creation. The database was marked for re-creation because it was not a viable standby database for the new primary database. Until this error status is resolved for this database, information about this database and the broker configuration to which it belongs is unavailable to a broker client that is connected to this database. Therefore, all commands directed by that client to this database cannot be completed.

Action: Re-create (or flash back) the standby database. Connect to the primary database in the broker configuration and reenable broker management of that database. Once enabled, it is possible to connect to that standby database and manage it with the broker. Alternatively, many client commands that cannot be completed at the standby database when in this error state can be completed successfully when issued to the primary database. In this case, simply reconnect to the primary database and retry the command.

ORA-16796: one or more properties could not be imported from the database

Cause: The broker was unable to import property values for the database being added to the broker configuration. This error indicates:

- The Oracle Net service name specified in DGMGRL CREATE CONFIGURATION or ADD DATABASE command was not one that provides access to the database being added.

- There were no instances running for the database being added.

Action: Remove the database from the configuration using the REMOVE CONFIGURATION or REMOVE DATABASE command. Make sure that the database to be added has at least one instance running and that the Oracle Net service name provides access to the running instance. Also check the broker log file for additional information. Then, reissue the CREATE CONFIGURATION or ADD DATABASE command.

ORA-16797: database is not using a server parameter file

Cause: The database was not using a server parameter file or the broker was unable to access the server parameter file.

Action: Issue the CREATE SPFILE='..' FROM PFILE='...'" command to create a server parameter file and then restart the database to use it.

ORA-16798: unable to complete terminal recovery on the standby database

Cause: Terminal recovery on the standby database failed during the failover operation.

Action: Check the Data Guard broker log and the Oracle alert logs to see more details on the reason for the failure.

ORA-16799: Redo Apply is not running

Cause: Either the Data Guard broker metadata indicates that Redo Apply was turned off, or the recovery process, MRP0, was not running. As a result, Redo Apply-related properties could not be set.

Action: Turn on Redo Apply through Data Guard broker and reissue the command to set a Redo Apply-related property.

ORA-16800: redo transport service for a standby database incorrectly set to ALTERNATE

Cause: The redo transport service for a standby database was set to ALTERNATE when no other destination is set to alternate to this destination.

Action: Reenable the standby database or the entire configuration to allow the configuration property settings to be propagated to the initialization parameters.

ORA-16801: redo transport-related property is inconsistent with database setting

Cause: The values of one or more redo transport-related configuration properties were inconsistent with database in-memory settings or server parameter file settings. This may happen by directly altering initialization parameters instead of editing configurable property values using Data Guard broker.

Action: Query the InconsistentLogXptProps property on the primary database or check the Data Guard broker log to find which properties are set inconsistently. Reset these properties to make them consistent with the database settings. Alternatively, enable the database or the entire configuration to allow the configurable property settings to be propagated to the initialization parameters.

ORA-16802: downgrading redo transport mode from SYNC disallowed

Cause: An attempt was made to downgrade the redo transport mode of a standby database from SYNC to ASYNC when the configuration was in Maximum Protection or Maximum Availability mode and the primary database was a RAC database. This was not disallowed even though there may have been other standby databases with redo transport modes set to SYNC to support the protection mode.

Action: Do one of the following if the redo transport mode of the standby must be downgraded:

- Shut down all instances of the primary database and restart one instance with the initialization parameter CLUSTER_DATABASE set to FALSE. Downgrade the redo transport mode of the standby database of interest. Then, shutdown the instance, set the the CLUSTER_DATABASE initialization parameter to TRUE, and restart all primary database instances.

- Downgrade the protection mode to Maximum Performance mode and then, downgrade the redo transport mode of the standby database of interest. Finally, upgrade the protection mode. This will require a restart of all primary database instances if upgrading to Maximum Protection mode. Note that the above only works when there is at least one standby database in the configuration that has its redo transport mode set to SYNC.

ORA-16803: unable to query a database table or fixed view

Cause: Failed to query a database table or fixed view. The database may not be opened or mounted.

Action: Check the Data Guard broker log for more details.

ORA-16804: one or more configuration properties in metadata have invalid values

Cause: Data Guard broker health check detected that one or more configuration properties in the broker configuration had invalid values. The property values were changed while broker management of the database was disabled.

Action: Check Data Guard broker log for more details on which properties have invalid values and reset them through the Data Guard broker.

ORA-16805: change of LogXptMode property violates overall protection mode

Cause: The broker disallowed the attempt to change the LogXptMode configurable property for the standby database because, if allowed, the overall protection mode for the configuration would have been violated.

Action: If the LogXptMode configuration property must be changed for the specified standby database, first downgrade the overall protection mode for the broker configuration. After that operation has completed, the LogXptMode configuration property for the standby database can be changed.

ORA-16806: supplemental logging is not turned on

Cause: Supplemental logging was not turned on while there was a logical standby database in the configuration. This could happen either on the primary database or on the logical standby database that was being switched over to be the primary database.

Action: Check the Data Guard broker log for more details. Issue the ALTER DATABASE ADD SUPPLEMENTAL LOG DATA (PRIMARY KEY, UNIQUE INDEX) COLUMNS to add supplemental logging.

ORA-16807: unable to change database protection mode

Cause: An attempt to issue the ALTER DATABASE SET STANDBY TO MAXIMIZE {PROTECTION | AVAILABILITY | PERFORMANCE} failed.

Action: Check the Data Guard broker log and the Oracle log for more information.

ORA Error . Listado Errores Oracle. ORA-16589 a ORA-16704

2013-06-02T12:53:00.001-07:00

ORA-16589: Data Guard broker detected network transfer error

Cause: The Data Guard broker detected an error while transferring data from one database to another. This may happen when:

- the broker detects an inconsistency in the block count of configuration file when the file is transmitted between databases.

- the broker encountered an error when writing the configuration file.

Action: Contact Oracle Support Services.

ORA-16594: DMON background process is not running

Cause: The Data Guard broker background process, DMON, was not running.

Action: Check the Data Guard broker log and DMON process trace file to determine why the DMON process is not running.

ORA-16595: process string failed to terminate

Cause: The specified process did not terminate at the request of the Data Guard broker.

Action: Contact Oracle Support Services.

ORA-16596: database not part of the Data Guard broker configuration

Cause: The specified database is not in the Data Guard broker configuration.

Action: Retry the command with a database that is in the broker configuration.

ORA-16597: Data Guard broker detects two or more primary databases

Cause: The Data Guard broker detected two or more primary databases in the broker configuration and could not continue.

Action: Contact Oracle Support Services.

ORA-16598: Data Guard broker detected a mismatch in configuration

Cause: The Data Guard broker detected a significant mismatch while performing configuration membership validation between two or more databases in the broker configuration. This can occur when the primary database has stale broker configuration files.

Action: Contact Oracle Support Services.

ORA-16599: Data Guard broker detected a stale configuration

Cause: The Data Guard broker detected a stale configuration during initialization for this database.

Action: The broker will automatically resolve this situation once the primary database completes its initialization.

ORA-16600: not connected to target standby database for failover

Cause: The failover command failed because the client was not connected to the target standby database.

Action: Explicitly connect to the standby database to be failed over to and retry the failover command.

ORA-16602: database must be disabled to perform this operation

Cause: An attempt was made to edit a database property while the database was enabled.

Action: Disable the database and retry the command.

ORA-16603: Data Guard broker detected a mismatch in configuration ID

Cause: There was a mismatch in configuration unique ID. This could occur if the original configuration was re-created while this database was disconnected from the network or the same database was added to two different Data Guard broker configurations.

Action: Make sure the database belongs to only one broker configuration. Shut down the broker by setting the DG_BROKER_START initialization parameter to false. Then remove the Data Guard broker configuration files. Finally restart the broker by setting the DG_BROKER_START initialization parameter to true.

ORA-16606: unable to find property "string"

Cause: The specified property did not exist.

Action: Specify a valid property name and reissue the request.

ORA-16607: one or more databases have failed

Cause: A failure was detected for one or more databases in the Data Guard broker configuration.

Action: Locate the database(s) with a failure status and correct it.

ORA-16608: one or more databases have warnings

Cause: A warning was detected for one or more databases in the Data Guard broker configuration.

Action: Locate the database(s) with a warning status and correct it.

ORA-16609: database is being disabled

Cause: A command was attempted on a database that was being disabled. For example, attempting to reinstate the old primary database, the database that was the primary database prior to the most recent failover, before it was ready to be reinstated.

Action: Wait for the Data Guard broker to disable the database and then retry the command.

ORA-16610: command "string" in progress

Cause: The specified broker command was already running and the command issued could not be completed.

Action: Wait for the specified command to finish and then retry the command.

ORA-16611: command aborted at user request

Cause: The command was aborted at the user's request.

Action: No action required.

ORA-16612: string value too long for attribute "string"

Cause: The string value for the named attribute was too long.

Action: Specify a shorter string value.

ORA-16613: initialization in progress for database

Cause: A request was made to modify the Data Guard broker configuration before the Data Guard broker had completed initialization.

Action: Wait until the Data Guard broker has completed initialization before attempting to modify the broker configuration.

ORA-16614: Data Guard broker configuration is disabled

Cause: An attempt to enable a database failed because the Data Guard broker configuration was disabled.

Action: Enable the Data Guard broker configuration and issue the DGMGRL CLI SHOW CONFIGURATION command to see if there are any databases that are still disabled. If the database you tried to enable is still disabled, issue the DGMGRL CLI SHOW DATABASE command to check the status of the database. If the database status indicates that the database needs to be reinstated then issue the DGMGRL CLI REINSTATE DATABASE command to reinstate and enable the database. If the database does not require reinstatement then issue the DGMGRL CLI ENABLE DATABASE command to enable the database.

ORA-16617: unknown object identifier specified in request

Cause: Object identifier specified in the request was invalid or unknown.

Action: Verify that a valid object identifier is specified and reissue reissue the request.

ORA-16619: health check timed out

Cause: The standby database could not be reached during a routine health check.

Action: This typically indicates a network problem where the standby database is unable to respond to the primary database within a predefined time frame. Check the network connections between the primary and standby databases.

ORA-16620: one or more databases could not be reached for a delete operation

Cause: One or more standby databases could not be reached for either a DGMGRL CLI REMOVE DATABASE or a REMOVE CONFIGURATION command.

Action: This typically indicates a network problem where the standby database is unable to respond to the primary database. In the event of this situation, examine the primary database Data Guard broker log to determine which standby databases could not be reached. For each standby database not reached, connect to that database and shut down the broker by setting the initialization parameter, DG_BROKER_START, to false. After the broker has been shut down for the standby database, locate the Data Guard broker configuration files from the standby database DG_BROKER_CONFIG_FILE[1|2] initialization parameter values and delete them. Then restart the broker by setting DG_BROKER_START to true.

ORA-16621: database name for ADD DATABASE must be unique

Cause: An attempt was made to add a database to the broker configuration that already included a database with the specified name. The database names must be unique.

Action: Verify that a unique name is specified for the new database to be added. Also, the database name must match the DB_UNIQUE_NAME initialization parameter of the database.

ORA-16622: two or more broker database objects resolve to the same database

Cause: Multiple database objects referred to the same database.

Action: Examine the details of all databases in the broker configuration and verify that there are not two or more databases referring to the same database. If two or more database profiles in the broker configuration have the same value for the DGConnectIdentifier database property, either:

- Remove and re-add the erroneously defined database(s) to resolve the ambiguity.

- Ensure that the DGConnectIdentifier database property for each database allows the broker to properly connect to that database.

ORA-16623: database detected role change

Cause: A successful switchover or failover operation had been completed and was detected during database startup or broker health check. If this database was unavailable during a switchover or failover operation, it may not be a viable standby database for the new primary database and was disabled by the Data Guard broker.

Action: Connect to the new primary database and examine the broker configuration for databases that were disabled and that may require reinstatement or re-creation.

ORA-16624: broker protocol version mismatch detected

Cause: A network protocol version number mismatch was detected. This could happen if the databases in the broker configuration were not running the same version of Oracle. The broker would disable standby databases that were not running the same version of Oracle as the primary database if this situation was detected.

Action: Examine the version of Oracle installed on all databases in the broker configuration to ensure they are identical. Once all of the datbases in the broker configuration are running the same version of Oracle, reenable the standby databases that were disabled.

ORA-16625: cannot reach the database

Cause: The command could not be executed because the database required to complete the command was not reachable from the database where the command was issued. If the command modifies the configuration, the command must be processed by the copy of the broker running on an instance of the primary database.

Action: Check the network connections between all of the databases in the configuration. Alternatively, connect to a different database in the Data Guard broker configuration and retry the command. If an attempt was made to determine the status of a particular database in the configuration, connect to that database and get the current value of the StatusReport property for that database.

ORA-16626: failed to enable specified database

Cause: This status was returned when attempting to enable a standby database that:

- Could not locate itself in the broker configuration file.

- Failed to distinguish itself from two or more databases in the configuration file.

- Determined it missed a role change within the configuration.

Action: To correct the problem, try one of these actions:

- Confirm that the host and SID names for the database exactly match the values in the HOST_NAME and INSTANCE_NAME columns of V$INSTANCE.

- Confirm that there are not two or more databases with the same connect identifier. That is, multiple databases in the broker configuration should not reach the same database.

- If a failover had been performed and the old primary database has been re-created (or a standby database has been re-created), make sure the Data Guard broker configuration files have been removed for that database. Do NOT remove the configuration files that are in use by the new primary database.

ORA-16627: operation disallowed since no standby databases would remain to support protection mode

Cause: This status was returned because of one of the following:

- The broker rejected an attempt to change the overall configuration protection mode since it could not find any enabled standby databases that supported the proposed protection mode.

- The broker rejected an attempt to enable the configuration if it determined that there were no enabled standby databases that supported the overall protection mode.

- The broker rejected an attempt to disable or remove a database that, if disabled or deleted, would result in no remaining standby databases that could support the overall configuration protection mode.

- The broker rejected an attempt to switchover if doing so would violate the overall configuration protection mode.

- Performing automatic health check if the broker determined that no standby datbases supported the overall protection mode.

Action: - If changing the overall protection mode, confirm that at least one standby database satisfies the new protection mode.

- For enable failures, confirm that at least one standby database has a LogXptMode configurable property setting that supports the current overall protection mode.

- For delete and disable failures, confirm that at least one other standby database has a LogXptMode configurable property setting that supports the overall protection mode.

- For switchover failures that occur when the configuration is operating in maximum protection or maximum availability mode, confirm that at least one other standby database has its LogXptMode configurable property set to the value "SYNC". If the configuration contains a primary database and a single standby database and is operating in either maximum protection or maximum availability mode, ensure that the LogXptMode configurable property of the primary database is set to the value "SYNC". Since the old primary database will become the standby database after switchover completes, its LogXptMode configurable property setting must support the configuration protection mode.

- For health check error, confirm that at least one standby database has a LogXptMode configurable property setting that supports the current overall protection mode.

ORA-16628: broker protection mode inconsistent with the database setting

Cause: The Data Guard broker protection mode saved in the broker configuration file was inconsistent with the actual database setting.

Action: Reset the protection mode through the Data Guard broker.

ORA-16629: database reports a different protection level from the protection mode

Cause: The actual or current database protection level was different from the configured protection mode. This typically is caused by redo transport problems.

Action: Check the database alert logs and Data Guard broker logs for more details. Also, check the redo transport status. Ensure that one standby database supports the configured protection mode and that the network to that standby database is working properly.

ORA-16630: database property has been deprecated

Cause: The property that was specified in the command was deprecated.

Action: Check the broker documentation to identify a replacement property or SQL command for the deprecated property.

ORA-16631: operation requires shutdown of database or instance "string"

Cause: The Data Guard broker operation required a shutdown of the database or instance.

Action: If database or instance has not been shutdown by the DGMGRL CLI or Enterprise Manager, shutdown the database or instance manually.

ORA-16632: instance being added to database profile

Cause: The Data Guard broker determined that an instance successfully found its database profile within the broker configuration file, but lacked an instance-specific profile. The broker automatically created an instance-specific profile and associated the instance with its database profile.

Action: No user action is required. The broker will automatically associate the instance with its database profile and incorporate the instance into broker activity.

ORA-16633: the only instance of the database cannot be removed

Cause: The instance to be removed was the only instance of the corresponding database that was known to the broker.

Action: Remove the corresponding database object from the broker configuration instead of the individual instance object of the database.

ORA-16635: network connection failed during transmission

Cause: The Data Guard broker detected a connection failure to a remote database in the broker configuration. This failure happened in the middle of a transmission session. A transmission session usually requires more than one send operation for sending a large amount of data (for example, the broker configuration file) to the remote database.

Action: In most cases, no user action is required. The Data Guard broker always tries to resend the data. This error will be reported if the problem persists. This error indicates there are some problems with the network connection between broker managed databases. Further network troubleshooting should be done to identify and correct the actual problem.

ORA-16636: fast-start failover target standby in error state, cannot stop observer

Cause: A STOP OBSERVER operation could not be completed when fast-start failover was enabled because the target standby database could not participate in the STOP OBSERVER operation.

Action: Additional information about this failure is recorded in the Data Guard broker log file for the primary database. This information helps to identify the reason why the target standby database was unable to participate in the STOP OBSERVER operation. If the problem can be corrected by the information in the broker log file, retry the operation. Alternatively, fast-start failover may be forcibly disabled by connecting to the primary database and issuing the DISABLE FAST_START FAILOVER FORCE command from the DGMGRL CLI. Once fast-start failover has been forcibly disabled, the observer can be stopped regardless of the current state of the target standby database.

ORA-16637: an instance failed to access the Data Guard broker configuration

Cause: The broker could not access the broker configuration files on one or more database instances. This can happen when the DG_BROKER_CONFIG_FILE[1|2] initialization parameter values are not to the same set of file locations for a RAC database.

Action: Shut off the broker by setting the DG_BROKER_START initialization parameter to false. Then set the DG_BROKER_CONFIG_FILE1 and DG_BROKER_CONFIG_FILE2 initialization parameters to file locations that are shared by all instances of a RAC database. Finally, restart the broker by setting the DG_BROKER_START initialization parameter to true.

ORA-16638: could not get the instance status

Cause: The broker could not determine whether the specified instance was running.

Action: See the next error message in the error stack for more detailed information. If the situation described in the next error in the stack can be corrected, do so; otherwise, contact Oracle Support Services.

ORA-16639: specified instance inactive or currently unavailable

Cause: An attempt was made to perform an operation on an instance that was not running or was unavailable.

Action: Ensure that the instance specified in the operation is running and then retry the operation.

ORA-16640: CRS warns that multiple instances may still be running

Cause: The broker failed to have CRS stop instance monitoring and shut down all but one instance. CRS instance monitoring did stop, but CRS may not have been able to shut down all but one instance. The broker operation was canceled.

Action: Suspend CRS management of this database using SRVCTL STOP DATABASE -D <name> -O NONE. Reissue the broker request.

ORA-16642: DB_UNIQUE_NAME mismatch

Cause: The expected DB_UNIQUE_NAME value did not match the actual DB_UNIQUE_NAME value for the database that the broker contacted using the connect identifier that was associated with that database.

Action: Verify that the connect identifier correctly connects to the intended database. Verify that the name of the database the broker expects to find by that connect identifier matches the actual DB_UNIQUE_NAME for that database.

ORA-16643: unable to determine location of broker configuration files

Cause: The Data Guard broker was unable to determine the location of its configuration files from the DG_BROKER_CONFIG_FILE[1|2] initialization parameters.

Action: Retry the operation and, if the error persists, contact Oracle Support Services.

ORA-16644: apply instance not available

Cause: The broker operation could not finish, because it requires a running apply instance for the standby database, and either there was no such instance designated for the standby database or the designated apply instance was not currently available.

Action: Start the designated apply instance or wait until the broker specifies an instance to be the apply instance and reissue the command.

ORA-16645: unexpected new instance interrupted current operation

Cause: A new instance unexpectedly joined the Data Guard configuration at a point when the current operation may proceed only if the set of known instances is not changing dynamically.

Action: Reissue the operation after the new instance has joined the Data Guard configuration.

ORA-16646: fast-start failover is disabled

Cause: The operation was not allowed because fast-start failover was disabled.

Action: Enable fast-start failover and retry the operation.

ORA-16647: could not start more than one observer

Cause: The observer could not start because there was another observer already observing the Data Guard configuration for which fast-start failover may have been enabled.

Action: Stop the running observer. Retry the operation.

ORA-16648: a new observer registered with identifier string

Cause: The observer was registered with the Data Guard broker and will begin observing the Data Guard configuration for conditions that warrant doing a fast-start failover.

Action: None

ORA-16649: possible failover to another database prevents this database being opened

Cause: An attempt to open the database was made either when a failover occurred or while fast-start failover was enabled and the fast-start failover status could not be evaluated.

Action: Check if a failover did occur. If fast-start failover is enabled, and a failover did not occur, ensure that connectivity exists between this database and either the observer or the target standby database. Then, try opening the database again.

ORA-16650: command incompatible when fast-start failover is enabled

Cause: An attempt was made to issue a command that is not permitted when fast-start failover is enabled. The command was not issued using the Data Guard broker.

Action: The command must be issued using the Data Guard broker.

ORA-16651: requirements not met for enabling fast-start failover

Cause: The attempt to enable fast-start failover could not be completed because one or more requirements were not met:

- The Data Guard configuration must be in either MaxAvailability or MaxPerformance protection mode.

- The LogXptMode property for both the primary database and the fast-start failover target standby database must be set to SYNC if the configuration protection mode is set to MaxAvailability mode.

- The LogXptMode property for both the primary database and the fast-start failover target standby database must be set to ASYNC if the configuration protection mode is set to MaxPerformance mode.

- The primary database and the fast-start failover target standby database must both have flashback enabled.

- No valid target standby database was specified in the primary database FastStartFailoverTarget property prior to the attempt to enable fast-start failover, and more than one standby database exists in the Data Guard configuration.

Action: Retry the command after correcting the issue:

- Set the Data Guard configuration to either MaxAvailability or MaxPerformance protection mode.

- Ensure that the LogXptMode property for both the primary database and the fast-start failover target standby database are set to SYNC if the configuration protection mode is set to MaxAvailability.

- Ensure that the LogXptMode property for both the primary database and the fast-start failover target standby database are set to ASYNC if the configuration protection mode is set to MaxPerformance.

- Ensure that both the primary database and the fast-start failover target standby database have flashback enabled.

- Set the primary database FastStartFailoverTarget property to the DB_UNIQUE_NAME value of the desired target standby database and the desired target standby database FastStartFailoverTarget property to the DB_UNIQUE_NAME value of the primary database.

ORA-16652: fast-start failover target standby database is disabled

Cause: The command to enable or disable fast-start failover could not be completed because Data Guard broker management of the fast-start failover target standby database is currently disabled.

Action: Enable broker management of the target standby database and reissue the command. If an attempt was made to disable fast-start failover when this error was reported, disable fast-start failover forcibly using the DGMGRL DISABLE FAST_START FAILOVER FORCE command. Consult the documentation for more information.

ORA-16653: failed to reinstate database

Cause: The Data Guard broker failed to reinstate the specified database because the REINSTATE command failed or because the database is already enabled.

Action: Additional information about this failure is recorded in the primary database or the specified database Data Guard broker log files. This information is helpful in determining how to proceed.

ORA-16654: fast-start failover is enabled

Cause: The attempted command was not allowed while fast-start failover was enabled:

- The FastStartFailoverTarget property may not be modified.

- The LogXptMode property for either the primary database or the fast-start failover target standby database may not be modified.

- The configuration's protection mode may not be modified.

- Neither the broker configuration nor the fast-start failover target standby database may be disabled using the DGMGRL CLI DISABLE command.

- Neither the broker configuration nor the fast-start failover target standby database may be removed using the DGMGRL CLI REMOVE command.

- The FAILOVER IMMEDIATE command is not allowed.

- The DG_BROKER_START initialization parameter may not be set to FALSE.

Action: Disable fast-start failover, using the FORCE option if required. Then retry the attempted command.

ORA-16655: specified target standby database invalid

Cause: The attempted command was not allowed because fast-start failover was enabled for this Data Guard configuration and the target standby database specified in the command differs from the standby database that was indicated by the FastStartFailoverTarget property associated with the current primary database.

Action: Retry the attempted command by specifying the standby database that is indicated by the FastStartFailoverTarget property that is associated with the current primary database. Alternatively, fast-start failover may be disabled. Then retry the command using the originally specified target standby database.

ORA-16656: Data Guard broker detected role change

Cause: The Data Guard broker detected a role during database startup or health check.

Action: Additional information about this failure is recorded in the Data Guard broker log files, one for the primary database and one for each standby database in the Data Guard configuration. This information is helpful in determining how best to proceed from this failure.

ORA-16657: reinstatement of database in progress

Cause: Reinstatement of this database was in progress.

Action: None

ORA-16658: unobserved fast-start failover configuration

Cause: The fast-start failover configuration was currently unobserved so failover was disallowed.

Action: Make sure the observer is running and has connectivity to both the primary and the target standby databases. Otherwise, disable fast-start failover to perform a failover in the absence of the observer process.

ORA-16659: failover operation in progress

Cause: A primary database that restarted contacted a standby database that is being failed over to.

Action: Shut down the primary database and wait for failover to complete on the standby database. Once failover is complete, restart the old primary database. If the failover occurred due to fast-start failover, restarting the primary database after failover is complete allows it to be automatically reinstated as a standby database to the new primary database.

ORA-16660: fast-start failover operation attempted in absence of a broker configuration

Cause: An attempt was made to enable or disable fast-start failover when connected to a standby database for which broker configuration details are currently unavailable. For instance, the standby database may currently require re-creation (or flashback reinstantiation) before it may respond to broker client commands.

Action: 1) An attempt to enable or disable (non-FORCE) fast-start failover at this standby database will be rejected until such time that the broker configuration details have been made available to that standby database from the primary database. This normally occurs when the standby database is successfully re-created or flashed back, and then reenabled at the primary database. 2) Use the FORCE option to override fast-start failover that has been enabled at the standby database even when the broker configuration details are currently unavailable to the standby database. In this case, this status message is only a warning. Note that fast-start failover is not formally disabled in the broker configuration. The effect of this command issued under these circumstances may or may not be permanent, depending upon when the primary and standby databases regain full communication between each other and if the state of fast-start failover has been altered at the primary database in the meantime.

ORA-16661: the standby database needs to be reinstated

Cause: A switchover or failover operation has caused this database to require reinstatement.

Action: Use the DGMGRL REINSTATE DATABASE command or Enterprise Manager to reinstate the database. If the target database has flashback enabled and it has sufficient flashback logs, the database will be reinstated as a standby database for the current primary database.

ORA-16662: network timeout when contacting a database

Cause: In response to the issued command, the Data Guard broker attempted to contact a database in the Data Guard configuration. That attempt failed because there was no response from that database after the period of time specified by the NetTimeout property for that database.

Action: Check the Data Guard broker log for the details of the failure. Fix the problem and try the command again.

ORA-16664: unable to receive the result from a database

Cause: During execution of a command, a database in the Data Guard broker configuration failed to return a result.

Action: Check Data Guard broker logs for the details of the failure. Fix any possible network problems and try the command again.

ORA-16665: timeout waiting for the result from a database

Cause: The Data Guard broker was forced to time out a network connection

Action: Check Data Guard broker logs for the details of the failure. Fix any possible network problems and reissue the command.

ORA-16666: unable to initiate fast-start failover on a standby database

Cause: The request to initiate a fast-start failover using DBMS_DG.INITIATE_FS_FAILOVER was made to a standby database. An application may only request that fast-start failover be initiated by calling DBMS_DG.INITIATE_FS_FAILOVER on a primary database.

Action: Call DBMS_DG.INITIATE_FS_FAILOVER on the primary database.

ORA-16667: request Data Guard broker client to reissue command

Cause: The Data Guard broker operation required the same command be issued again from the client.

Action: If DGMGRL or Enterprise Manager has not already done so, reissue the same command to the Data Guard broker manually.

ORA-16668: operation invalid on fast-start failover target database

Cause: The attempted command was not allowed on the fast-start failover target standby database when fast-start failover is currently enabled.

Action: Retry the attempted command on a database other than the fast-start failover target standby database. Alternatively, disable fast-start failover and reissue the same command to the fast-start failover target standby database.

ORA-16700: the standby database has diverged from the primary database

Cause: The primary database may have been flashed back or restored from a backup set and then reopened with the RESETLOGS option.

Action: Re-create the standby database from the primary database or flash back the standby database to the same point the primary database had been flashed back to.

ORA-16701: Data Guard broker command failed

Cause: Command to modify or query the database failed.

Action: Check the Data Guard broker log for the reason for the failure, and reissue the command.

ORA-16702: Data Guard broker command warning

Cause: A command to modify or query the database resulted in a warning.

Action: Check the Data Guard broker log for the warning and, if necessary, reissue the command.

ORA-16703: cannot set property while the database is enabled

Cause: An attempt was made to change a database property while the database was enabled.

Action: Disable the database first, update the property and then, reenable the database.

ORA-16704: cannot modify a read-only property

Cause: An attempt was made to change a read-only property.

Action: The property is controlled internally by the Data Guard broker and cannot be modified.

span><� ]s a �Or 0s N style='font-size:10.0pt;font-family:"Arial","sans-serif";mso-fareast-font-family: "Times New Roman";color:#222222;mso-ansi-language:EN;mso-fareast-language:ES-AR'> Verify space, permissions and file name as indicated by the DG_BROKER_CONFIG_FILE[1|2] initialization parameters and retry the operation.

ORA Error . Listado Errores Oracle. ORA-16262 a ORA-16587

2013-06-02T12:48:00.002-07:00

ORA-16262: Invalid value specified for Logical Standby parameter

Cause: The value specified in APPLY_SET is invalid for the parameter.

Action: Specify correct parameter value. Please refer to documentation on DBMS_LOGSTDBY PL/SQL package for details.

ORA-16263: Dynamic parameters can only be set on SQL apply instance

Cause: Attempt to set a Logical standby dynamic parameter on an instacne other than where SQL apply coordinator is running.

Action: Connect to the instance where SQL apply coordinator is running and re-issue the statement.

ORA-16264: invalid value for PREPARE_SERVERS parameter

Cause: attempt to set PREPARE_SERVERS parameter to zero or to a value which would require MAX_SERVERS to be increased.

Action: set PREPARE_SERVERS parameter to a non zero value and or increase MAX_SERVERS parameter accordingly.

ORA-16265: Unsupported PL/SQL procedure encountered

Cause: Apply encountered an unsupported procedure from an Oracle supplied PL/SQL package that is otherwise supported

Action: Either add a skip rule for this procedure or manually apply the procedure and restart apply skipping the failed transaction Please refer to documentation on the PL/SQL package for details.

ORA-16266: Cannot instantiate a Logical Standby from another Logical Standby

Cause: An instantiation of a Logical Standby has been attempted for another database with the Logical Standby role, which is not supported.

Action: Instantiate a Logical Standby database only from a Primary Database.

ORA-16267: Cannot instantiate a Logical Standby during a switchover

Cause: An instantiation of a Logical Standby has been attempted for a primary database that is in the middle of a switchover.

Action: Execute ALTER DATABASE PREPARE TO SWITCHOVER CANCEL to cancel the switchover, and attempt the instantiation again.

ORA-16268: user procedure processing of logical standby apply PL/SQL

Cause: A user-provided stored procedure was called to inspect a PL/SQL statement prior to the statement being processed.

Action: No action necessary, this informational statement is provided to record user involvement in the processing of a statement. Additional information can be found in the DBA_LOGSTDBY_EVENTS and the DBA_LOGSTDBY_SKIP views.

ORA-16269: PL/SQL procedure skipped due to failure on primary database

Cause: Because the PL/SQL procedure failed when executed on the primary database, it could not be executed on the standby database.

Action: This informational statement is provided to record the event for diagnostic purposes. The failed PL/SQL procedure needs to be investigated to ensure it did not commit interesting data before it failed.

ORA-16270: PL/SQL procedure skipped due to unmaintained standby objects

Cause: Because the PL/SQL procedure manipulated objects not being maintained by the standby database, it was skipped.

Action: No action necessary. This informational statement is provided to record the event for diagnostic purposes.

ORA-16271: PL/SQL successfully applied

Cause: A PL/SQL procedure was successfully applied on the logical standby database.

Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.

ORA-16272: PL/SQL procedure skipped due to skip setting

Cause: A setting in the logical standby skip table indicated that this PL/SQL procedure should always be skipped.

Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.

ORA-16273: invalid value for APPLY_SERVERS parameter

Cause: attempt to set APPLY_SERVERS parameter to zero or to a value which would require MAX_SERVERS to be increased.

Action: set APPLY_SERVERS parameter to a non zero value or increase MAX_SERVERS parameter accordingly.

ORA-16274: failure to perform DDL on all RAC instances

Cause: One or more instances encountered an error while performing an operation.

Action: Ensure every instance in the RAC meets the requirements for the operation, and retry the operation.

ORA-16275: prior failed CTAS detected and pre-existing table dropped

Cause: During the processing of a CTAS operation, an existing empty table with the same name and attributes as the CTAS source table was found, and the table was dropped.

Action: No action is necessary. This informational statement is provided to record the event for diagnostic purposes.

ORA-16276: specified database link does not correspond to primary database

Cause: The database link specified to DBMS_LOGSTDBY.INSTANTIATE_TABLE did not link to the primary database for this logical standby database.

Action: Specify a database link that corresponds to the primary database for this logical standby database. The link should have privileges to read and lock the table being instantiated, as well as the SELECT_CATALOG_ROLE.

ORA-16277: specified table is not supported by logical standby database

Cause: A call was made to DBMS_LOGSTDBY.INSTANTIATE_TABLE to instantiate an unsupported table on the logical standby database. Tables with unsupported data types cannot be replicated to a logical standby database.

Action: Specify a table which is not listed in the DBA_LOGSTDBY_UNSUPPORTED_TABLE view.

ORA-16278: specified table has a multi-object skip rule defined

Cause: A table that is instantiated via DBMS_LOGSTDBY.INSTANTIATE_TABLE must not have any skip rules defined with wildcard characters.

Action: Remove or rewrite any skip rules defined for the specified table so that they no longer contain wildcard characters, or no longer affect the specified table.

ORA-16279: Supplied dblink must have CONNECT, RESOURCE, and SELECT_CATALOG_ROLE roles

Cause: A dblink was specified to DBMS_LOGSTDBY.INSTANTIATE_TABLE that lacked one or more of the CONNECT, RESOURCE, or SELECT_CATALOG_ROLE roles.

Action: Grant the CONNECT, RESOURCE, and SELECT_CATALOG_ROLE roles to the specified dblink, and retry the operation.

ORA-16280: cannot change master key on a logical standby database

Cause: An attempt was made to change the master key for transparent data encryption on a logical standby database.

Action: Set GUARD to NONE and reissue the command. This prevents you from replicating tables with encrypted columns from the primary database.

ORA-16281: missing identification key for table "string"."string".

Cause: No identification key was created for specified table.

Action: Create a primakey key or unique index for specified table.

ORA-16282: operation not permitted during rolling upgrade

Cause: An operation was attempted that is not supported during a rolling upgrade.

Action: Retry the operation upon completion of the upgrade.

ORA-16400: quota attributes are not allowed with DB_RECOVERY_FILE_DEST

Cause: Quota attributes for the destination parameters are not allowed when the parameter DB_RECOVERY_FILE_DEST is defined.

Action: No action is required.

ORA-16401: archivelog rejected by RFS

Cause: An attempt was made to re-archive an existing archivelog. This usually happens because either a multiple primary database or standby database(s) or both are trying to archive to this standby database.

Action: See alert log and trace file for more details. No action is necessary; this is an informational statement provided to record the event for diagnostic purposes.

ORA-16402: ONDEMAND archival requires FAL_CLIENT and FAL_SERVER support

Cause: The archivelog destination TRANSPORT=ONDEMAND attribute was specified on the primary database. Use of the TRANSPORT=ONDEMAND attributes requires that the corresponding standby database explicitly specify the FAL_CLIENT and FAL_SERVER initialization parameters.

Action: Make sure the FAL_CLIENT and FAL_SERVER initialization parameters are explicitly specified on the standby database that received this error.

ORA-16403: shutdown in progress - remote connection is not permitted

Cause: The SHUTDOWN command was used to shut down a running remote primary or standby ORACLE instance, so the LGWR or ARCH processes cannot connect to ORACLE.

Action: Wait for the remote instance to be restarted, or contact your DBA.

ORA-16406: Primary and standby database software version mismatch

Cause: The primary database and standby database Oracle software is not compatible.

Action: Install the correct Oracle software and try again.

ORA-16407: Standby database is in the future of the archive log

Cause: An archive log, from a different Redo Branch, was received by a standby database that has applied Redo in the future of Redo contained within the archive log. The standby database has rejected the REDO Branch archive logs.

Action: No action is required.

ORA-16408: Incompatible archival Redo Branch lineage

Cause: An archive log, from an incompatible different Redo Branch, was received by a standby database. The standby database has rejected the Redo Branch archive logs.

Action: No action is required.

ORA-16409: Archive log switchover reference number mismatch

Cause: The archive log switchover reference numbers of the Primary and Standby database do not match. Remote archival of redo log files is not allowed to incompatible STANDBY database instances.

Action: No action is required.

ORA-16411: ONDEMAND archival requires active managed recovery operation

Cause: The use of the ONDEMAND attribute for a physical standby database destination requires that the managed recovery operation be active prior to establishing the network connection.

Action: Start the managed recovery operation on the standby database.

ORA-16412: ONDEMAND archival requires active SQL apply operation

Cause: The use of the ONDEMAND attribute for a logical standby database destination requires that the SQL apply operation be active prior to establishing the network connection.

Action: Start the SQL apply operation on the standby database.

ORA-16413: Unsupported database type for ONDEMAND archivelog destinations

Cause: The use of the ONDEMAND attribute for a standby database destination is supported for only physical and logical standby database types. Cross-Instance-Archival and repository database types are not valid for the ONDEMAND attribute.

Action: Verify the database corresponding to the archivelog destination is either a physical standby database or a logical standby database.

ORA-16416: Switchover target is not synchronized with the primary

Cause: The switchover target incurred an error or has a gap at the time the switchover operation was attempted.

Action: Allow the switchover target to become synchronized and then re-attempt the switchover.

ORA-16417: Activation occurred after recovery from standby redo log files; a full database backup is required

Cause: Activation occurred after recovery from standby redo log files.

Action: Take a full database backup.

ORA-16419: Snapshot standby must be converted from physical standby

Cause: The database is not physical standby.

Action: Convert to physical standby and retry the operation.

ORA-16420: fast-start failover target cannot be converted to snapshot standby

Cause: The database chosen for conversion to a snapshot standby was the fast-start failover target standby database.

Action: Choose another physical standby database and retry the operation.

ORA-16424: Terminal recovery cannot start due to GAP on Physical Standby

Cause: Terminal Recovery failed because of gap behind the start point of standby recovery.

Action: Issue ALTER DATABASE ACTIVATE STANDBY DATABASE

ORA-16425: Terminal recovery branch string older than target branch string

Cause: Terminal Recovery failed because of new branch on Physical Standby.

Action: Issue real time apply recovery and see if recovery can proceed on the new branch by checking if logs on the new branch are applied by recovery. If so, issue another terminal recovery. Otherwise, issue ALTER DATABASE ACTIVATE STANDBY DATABASE

ORA-16426: log requested by recovery is not the correct log

Cause: Media recovery has selected an incorrect log

Action: Verify that the proper log has been properly registered and restart media recovery.

ORA-16427: Potential archive log gap too large to service

Cause: Standby destination is too far behind the primary database for automatic archive log gap detection/resolution to take place.

Action: Standby database should be recreated with a recent backup copy of the primary database.

ORA-16431: Cannot expand control file

Cause: More threads were added on the primary database after this standby control file was created.

Action: Shut down the standby database, either replace the control file with a new standby control file from primary database or change the COMPATIBLE parameter to 10.2.0 or above, and restart the standby database.

ORA-16432: inconsistent set of terminal logs detected

Cause: Media Recovery stopped because it detected an inconsistency between the first log in the new incarnation and the state of the previous incarnation. If this database is a bystander standby database, this is most likely because there was a failover operation, and this database applied terminal logs generated from that failover operation for some redo threads but applied corresponding logs from the old primary database of that failover operation for some other redo threads.

Action: Flashback or restore this database to before the standby_became_primary_scn of that failover operation and restart media recovery. The standby_became_primary_scn of the failover operation can be obtained from V$DATABASE on the new primary.

ORA-16433: The database has not been opened in read-write mode

Cause: When a physical standby database is converted to a read-write database or there was a failed open resetlogs attempt, the database should be opened in read-write mode to have correct file access information in the controlfile.

Action: Open the database in read-write mode and reissue the command.

ORA-16438: Switchover to primary cannot be executed at this time

Cause: ALTER DATABASE COMMIT TO SWITCHOVER TO PRIMARY could not be executed because an incompatible operation such as RMAN restore or flashback was in progress. See the database alert log for details.

Action: Wait for the incompatible operation to complete. The files that have been flashed back or restored need recovery before you can reissue ALTER DATABASE COMMIT TO SWITCHOVER TO PRIMARY statement. Start redo apply and verify that the SWITCHOVER_STATUS column of the V$DATABASE view reports TO_PRIMARY or SESSIONS_ACTIVE before retrying ALTER DATABASE COMMIT TO SWITCHOVER TO PRIMARY.

ORA-16501: the Data Guard broker operation failed

Cause: The Data Guard broker operation failed.

Action: See accompanying messages for details.

ORA-16502: the Data Guard broker operation succeeded with warnings

Cause: The Data Guard broker operation succeeded with warnings.

Action: See accompanying messages for details.

ORA-16504: the Data Guard configuration already exists

Cause: A request to create a Data Guard configuration was made while connected to a database that is part of an existing configuration.

Action: To create a new configuration, the existing configuration must be deleted.

ORA-16505: site ID is invalid

Cause: The request contained an invalid site ID.

Action: Make the request again with a valid site ID.

ORA-16506: out of memory

Cause: Process exceeded private or shared memory limits.

Action: Check for memory leaks, increase system parameters and restart.

ORA-16507: unrecognized request identifier

Cause: The specified request identifier was not recognized by the Data Guard broker.

Action: Reissue the request using a valid request identifier.

ORA-16509: request timed out

Cause: The Data Guard broker timed out out the request.

Action: Check the Data Guard broker log file for more information. Ensure that the network connections between the databases are functioning properly and retry the request.

ORA-16513: maximum requests exceeded

Cause: The maximum number of requests that the broker can service

Action: Wait for the broker to complete processing the requests before issuing more requests.

ORA-16514: request was not found

Cause: An attempt was made to read a response but a matching request was not found.

Action: Verify request identifier is valid and that it references a previously issued request.

ORA-16516: current state is invalid for the attempted operation

Cause: The broker may have returned this error for either switchover operations or for database state change operations. If this error was returned for a switchover operation, the broker determined that either:

- The databases changing roles are shut down.

- The primary database is not shipping redo data.

- The standby database that will become the primary database is not applying redo data. If this error was returned for database state change operations, the database state specified was invalid.

Action: If this error is returned when attempting a switchover operation, make sure that:

- The databases changing roles are started.

- The primary database is shipping redo data.

- The standby database is applying redo data. If this error is returned when attempting a database state change operation, make sure a valid database state is specified.

ORA-16523: operation requires the client to connect to instance "string"

Cause: The switchover or failover operation required the client to connect to the apply instance of the target database.

Action: Connect to the indicated instance and reissue the SWITCHOVER or FAILOVER command.

ORA-16524: unsupported operation

Cause: A command or option was not supported in this release.

Action: Contact Oracle Support Services.

ORA-16525: the Data Guard broker is not yet available

Cause: The Data Guard broker process was either not yet started, was initializing, or failed to start.

Action: If the broker has not been started, set the DG_BROKER_START initialization parameter to true and allow the broker to finish initializing before making the request. If the broker failed to start, check the Data Guard log for possible errors. Otherwise, retry the operation.

ORA-16526: unable to allocate task element

Cause: The Data Guard broker was unable to allocate memory for a request.

Action: Increase the size of the SGA.

ORA-16527: unable to allocate broker SGA memory

Cause: The Data Guard broker was unable to allocate memory within the SGA.

Action: Increase the size of the SGA memory.

ORA-16528: unable to allocate PGA memory

Cause: There was insufficient space in PGA to allocate memory.

Action: Increase process virtual memory.

ORA-16530: invalid buffer or length

Cause: A NULL buffer or a length of zero was specified.

Action: Correct the command parameters and retry the command.

ORA-16532: Data Guard broker configuration does not exist

Cause: A broker operation was requested that required a broker configuration to already be created.

Action: Create a Data Guard broker configuration prior to performing other broker operations.

ORA-16534: no more requests accepted

Cause: The Data Guard broker returned this status because either:

- A failover operation was submitted or was in progress.

- A switchover operation was submitted or was in progress.

- An instance restart was pending for one or more databases.

Action: Wait until the operation is complete and reissue the request.

ORA-16535: CRS is preventing execution of a broker operation

Cause: The broker was unable to have CRS stop management of all of the instances of this database.

Action: Suspend CRS management of this database using the SRVCTL STOP DATABASE -D <name> -O NONE command. Then reissue the broker request.

ORA-16541: database is not enabled

Cause: The database specified in the request was not enabled.

Action: Select an enabled database and reissue the request.

ORA-16544: modifying DG_BROKER_START requires SID='*' qualifier

Cause: The setting for the DG_BROKER_START parameter must be exactly the same on all RAC database instances. The SID='*' qualifier was required in the command.

Action: Reenter the command using the SID='*' qualifier.

ORA-16545: unable to get response

Cause: The Data Guard broker was unable to return the result of a previous request.

Action: Contact Oracle Support Services.

ORA-16546: missing or invalid value

Cause: The value of the request to return was not specified or was invalid.

Action: Specify the value of the response starting from one.

ORA-16547: cannot disable or delete the primary database

Cause: An attempt was made to disable broker management of the primary database or delete the primary database from the broker configuration while the configuration was enabled.

Action: If you wish to disable broker management of the primary database when the configuration is enabled, you must instead disable broker management of the entire broker configuration. If you wish to delete the primary database from the broker configuration while the configuration is enabled, you must instead delete the entire broker configuration.

ORA-16548: database not enabled

Cause: An attempt was made to modify or query a disabled database. This error is also returned on an attempt to enable, modify, or query a database that the broker has disabled because of a switchover or failover operation. The broker disables its management of a database when it detects that the database needs to be re-created because of a failover or switchover operation.

Action: If broker management of the database is disabled, enable it and reissue the request.

ORA-16549: invalid string

Cause: An invalid or NULL string value was specified.

Action: Correct command parameters and retry.

ORA-16550: truncated result

Cause: A string property value was truncated due to insufficient buffer size.

Action: Specify a larger receive buffer.

ORA-16551: short string copied

Cause: A string property value that did not fill the receive buffer was placed in the receive buffer.

Action: This is an informational message only.

ORA-16552: an error occurred when generating the CLIENT OPERATION table

Cause: An error occurred while Data Guard broker was generating the CLIENT OPERATION table.

Action: See the next error message for more detailed information. Execute the action described in the next error or contact Oracle Support Services.

ORA-16555: database is not active

Cause: An operation was attempted on a database that was not active. not active.

Action: Verify that the database is active and retry the operation.

ORA-16556: observer version mismatch

Cause: This version of the observer was incompatible with the version of the specified Oracle database server to which the observer had been connected. This observer client cannot be used to observe the specified Oracle server.

Action: Use a version of the observer that is compatible with the Oracle database server to be observed.

ORA-16557: database is already in use

Cause: An attempt was made to create a duplicate database in the broker configuration.

Action: Check the database to be added to ensure there are no duplicates.

ORA-16558: database specified for switchover is not a standby database

Cause: An attempt was made to switchover to a database that was not a standby database.

Action: Locate an enabled standby database and select that database as the target of the switchover.

ORA-16561: cannot remove an active instance

Cause: The instance to be removed was running.

Action: Shut down the instance and reissue the REMOVE command.

ORA-16568: cannot set property string

Cause: The specified property could not be modified because it was either a monitorable property or a property that did not exist.

Action: Retry the command with a valid configurable property.

ORA-16569: Data Guard configuration is not enabled

Cause: The requested operation required that broker management of the Data Guard configuration must be enabled.

Action: Enable the Data Guard configuration and reissue the request.

ORA-16570: database needs restart

Cause: The Data Guard broker operation required this database instance to be shut down and restarted.

Action: If DGMGRL or Enterprise Manager has not already done so, shutdown the Oracle instance and then restart it.

ORA-16571: Data Guard configuration file creation failure

Cause: The Data Guard broker was unable to create the configuration file on permanent storage.

Action: Verify space, permissions and file name as indicated by the DG_BROKER_CONFIG_FILE[1|2] initialization parameters and retry the operation.

ORA-16572: Data Guard configuration file not found

Cause: The Data Guard broker configuration file was either unavailable or did not exist.

Action: Verify that the configuration file was successfully created. If the DG_BROKER_CONFIG_FILE[1|2] initialization parameters were changed, ensure the file name on disk and the parameter value match, there is space on the device, and the proper permissions are granted.

ORA-16573: attempt to change or access configuration file for an enabled broker configuration

Cause: The operation was rejected because the Data Guard broker configuration file was in use. The attempted operation was unsafe while broker management of the configuration was enabled. For example:

- An attempt was made to alter the DG_BROKER_CONFIG_FILE[1|2] initialization parameters while the broker was running.

- Non-broker access (such as DBMS_FILE_TRANSFER) to the configuration files was attempted. See the alert log for additional information.

Action: Disable the broker configuration and shut down the Data Guard broker, then retry the operation. If the operation includes altering the DG_BROKER_CONFIG_FILE[1|2] initialization parameters, be sure that the new parameter values correctly specify the files at their expected location before reenabling broker management of the configuration.

ORA-16574: switchover disallowed when required databases are shut down

Cause: Switchover failed because either the primary database or the designated standby database were shut down.

Action: Ensure that the primary and standby databases are running and that primary database is shipping redo data to the designated standby database. Also ensure that that the designated standby database is applying the redo data received from the primary database.

ORA-16575: request terminated at broker discretion

Cause: This error was returned when the broker terminated a command because it was processing a failover command.

Action: Wait for failover to complete and then retry the command.

ORA-16576: failed to update Data Guard configuration file

Cause: A failure was encountered while the broker was updating the Data Guard broker configuration file on permanent storage.

Action: Verify space, permissions and file name as indicated by the DG_BROKER_CONFIG_FILE[1|2] initialization parameters.

ORA-16577: corruption detected in Data Guard configuration file

Cause: The Data Guard broker detected errors while loading the configuration file.

Action: Verify space, permissions and file name as indicated by the DG_BROKER_CONFIG_FILE[1|2] initialization parameters. Contact Oracle Support Services.

ORA-16578: failed to read Data Guard configuration file

Cause: A failure was encountered while the broker was reading the configuration file on permanent storage.

Action: Verify space, permissions and file name as indicated by the DG_BROKER_CONFIG_FILE[1|2] initialization parameters.

ORA-16582: cannot change instance-specific property

Cause: An attempt was made to change an instance-specific property for a database that had more than one instance.

Action: Retry the command and identify a specific instance whose property value is to be changed.

ORA-16586: cannot change database property with EDIT INSTANCE command

Cause: An attempt was made to change a database property using an EDIT INSTANCE command instead of an EDIT DATABASE command.

Action: Use an EDIT DATABASE command to change database properties.

ORA-16587: ambiguous object specified to Data Guard broker

Cause: An object was specified that the broker could not uniquely distinguish from other objects in the configuration.

ORA Error . Listado Errores Oracle. ORA-16159 a ORA-16261

2013-06-02T12:47:00.001-07:00

ORA-16159: Cannot change protected standby destination attributes

Cause: An attempt was made to change the LGWR/ARCH or SYNC/ASYNC attributes for a destination that is participating in the standby protection mode of the database.

Action: No action is required.

ORA-16160: Cannot change protected standby database configuration

Cause: An attempt was made to change the standby database configuration when the primary database is in standby protected mode.

Action: The standby database must be added to the configuration before the primary database is opened.

ORA-16161: Cannot mix standby and online redo log file members for group string

Cause: An attempt was made to add a log file member that does not match the other member types. This problem typically occurs when adding a standby log file member to an online redo logfile group, or adding an online redo log file member to a standby redo log file group.

Action: Verify the log file group type using the TYPE column of the V$LOG fixed view.

ORA-16162: Cannot add new standby databases to protected configuration

Cause: An attempt was made to enable a new standby database destination when the primary database is in standby protected mode.

Action: The standby database must be added to the configuration before the primary database is opened.

ORA-16163: LGWR network server host attach error

Cause: The LGWR network server could not attach to remote host

Action: The alert log contains more problem-specific information

ORA-16164: LGWR network server host detach error

Cause: The LGWR network server could not detach from remote host

Action: The alert log contains more problem-specific information

ORA-16165: LGWR failed to hear from network server

Cause: The LGWR lost its connection to the network server

Action: The alert log contains more problem-specific information

ORA-16166: LGWR network server failed to send remote message

Cause: The LGWR network server could not communicate with the remote host

Action: The alert log contains more problem-specific information

ORA-16167: LGWR network server could not switch to non-blocking mode

Cause: The LGWR network server could not switch to non-blocking mode

Action: The alert log contains more problem-specific information

ORA-16168: LGWR network server could not switch to blocking mode

Cause: The LGWR network server could not switch to blocking mode

Action: The alert log contains more problem-specific information

ORA-16169: LGWR network server invalid parameters

Cause: The LGWR network server could not switch to blocking mode

Action: The alert log contains more problem-specific information

ORA-16170: Terminal recovery may have left the database in an inconsistent state

Cause: When terminal recovery is invoked in a standby database without synchronous log shipping, in the rare case of the recovery session being in an unrecoverable state, terminal recovery cannot bring the standby database to a consistent SCN boundary if the primary database continues to have redo thread(s) open.

Action: Continue standby recovery with additional log shipping from primary.

ORA-16171: RECOVER...FINISH not allowed due to gap for thr string, seq string-string

Cause: See alert log for more details

Action: Copy missing archived logs from primary or another standby. Register the logs and re-issue the RECOVER...FINISH command. If the logs are not available, issue the ALTER DATABASE RECOVER MANAGED STANDBY SKIP command to ignore the standby redo log files.

ORA-16172: archive logs detected beyond Terminal End-Of-Redo

Cause: An attempt to archive a Terminal End-Of-Redo archive log to a remote destination failed due the existence, at the remote site, of archive logs containing REDO in the future of the Terminal EOR.

Action: None

ORA-16173: incompatible archival network connections active

Cause: One of two situations can cause this error: 1) An attempt to start a Terminal Incomplete Recovery operation failed due to an active Remote File Server process detected. 2) An attempt to archive a Terminal End-Of-Redo archive log to a remote destination failed due to an active Remote File Server process at the remote site. An active Remote File Server (RFS) process implies connectivity with the primary database which may indicate that a Terminal Incomplete Recovery operation is not warrented.

Action: Verify the Managed Standby environment and re-evaluate the necessity of a Terminal Incomplete Recovery operation.

ORA-16174: user requested thread/sequence termination of managed recovery

Cause: The managed standby database recovery operation has been terminated per user specified THROUGH THREAD/SEQUENCE option of the RECOVER MANAGED STANDBY DATABASE statement.

Action: No action is required.

ORA-16175: cannot shut down database when media recovery is active

Cause: An attempt was made to shut down a standby database while media recovery was active.

Action: Cancel media recovery to proceed with the shutdown.

ORA-16176: background dictionary build cannot be running

Cause: The background process dedicated to dictionary build is active.

Action: wait and try it later.

ORA-16177: media recovery is not required

Cause: The THROUGH LAST SWITCHOVER clause of the ALTER DATABASE RECOVER MANAGED STANDBY DATABASE was specified and the database has been recovered to the most recent End-Of-Redo marker. All known archived logs have been applied. Managed recovery is not required.

Action: No action is necessary. The standby database may be activated as a new primary or may continue as a standby.

ORA-16178: Cannot specify remote destinations in archivelog manual mode

Cause: The database is operating in ARCHIVELOG MANUAL mode. Remote archivelog destinations are not allowed in this mode.

Action: Use the ALTER DATABASE ARCHIVELOG command to place the database in automatic archivelog mode, or defer the archivelog destinations that specify the SERVICE= attribute.

ORA-16179: incremental changes to "string" not allowed with SPFILE

Cause: Incremental changes to a log_archive_dest_n parameter cannot be made when using an SPFILE.

Action: Specify either LOCATION or SERVICE plus all other attributes to be set in one ALTER SYSTEM/SESSION SET command.

ORA-16180: number of processes specified is too large

Cause: The number of server processes available for Logical Standby is currently limited to 1024 LogMiner processes and 1024 apply processes or a total of 2048.

Action: Retry with a lower value.

ORA-16181: SGA specified for Logical Standby is too large

Cause: MAX_SGA is larger than the larger of initialization parameters SHARED_POOL_SIZE and SGA_TARGET.

Action: Specify the value of MAX_SGA to be less than the maximum of SHARED_POOL_SIZE and SGA_TARGET. Likely only 75% or lower.

ORA-16182: Internal error on internal channel during remote archival

Cause: An internal error was encountered on the internal channel between LGWR and Network Server.

Action: No action is required, as an attempt will be made to re-archive the file that had this failure during archival.

ORA-16184: DB_UNIQUE_NAME string hashes to the same value as DB_UNIQUE_NAME string

Cause: The internal hash value generated for one DB_UNIQUE_NAME collided with the hash value of another DB_UNIQUE_NAME.

Action: Slightly modify one of the DB_UNIQUE_NAMEs so it hashes to a different value.

ORA-16185: REMOTE_ARCHIVE_ENABLE and LOG_ARCHIVE_CONFIG mutually exclusive

Cause: Both the REMOTE_ARCHIVE_ENABLE and LOG_ARCHIVE_CONFIG parameters are defined in the initialization file and they are mutually exclusive.

Action: The REMOTE_ARCHIVE_ENABLE parameter has been made obsolete. Use only the LOG_ARCHIVE_CONFIG parameter.

ORA-16186: Modifying LOG_ARCHIVE_CONFIG requires SID='*' qualifier

Cause: The setting for the LOG_ARCHIVE_CONFIG parameter must be exactly the same on all RAC instances so the SID='*' qualifier is required.

Action: Re-enter the command using the SID='*' qualifier.

ORA-16187: LOG_ARCHIVE_CONFIG contains duplicate, conflicting or invalid attributes

Cause: The LOG_ARCHIVE_CONFIG parameter was specified with duplicate, conflicting or invalid attributes.

Action: Check the documentation regarding the correct specification of the LOG_ARCHIVE_CONFIG parameter.

ORA-16188: LOG_ARCHIVE_CONFIG settings inconsistent with previously started instance

Cause: The settings for the LOG_ARCHIVE_CONFIG parameter are inconsistent with the settings of a previously started instance. The settings for this parameter must be exactly the same for all instances.

Action: Make sure all instances use the exact same LOG_ARCHIVE_CONFIG settings.

ORA-16191: Primary log shipping client not logged on standby

Cause: An attempt to ship redo to standby without logging on to standby or with invalid user credentials.

Action: Check that primary and standby are using password files and that both primary and standby have the same SYS password. Restart primary and/or standby after ensuring that password file is accessible and REMOTE_LOGIN_PASSWORDFILE initialization parameter is set to SHARED or EXCLUSIVE.

ORA-16192: Primary and standby network integrity mismatch

Cause: Standby wants sqlnet network integrity for redo shipment which is not configured properly at the primary.

Action: Check sqlnet.ora documentation regarding how to setup network integrity and set it up identically on both primary and standby. Restart primary and/or standby.

ORA-16193: Primary and standby network encryption mismatch

Cause: Standby wants sqlnet network encryption for redo shipment which is not configured properly at the primary.

Action: Check sqlnet.ora documentation regarding how to setup network encryption and set it up identically on both primary and standby. Restart primary and/or standby.

ORA-16194: Modifying DB_UNIQUE_NAME requires SID='*' qualifier

Cause: The setting for the DB_UNIQUE_NAME parameter must be exactly the same on all RAC instances so the SID='*' qualifier is required.

Action: Re-enter the command using the SID='*' qualifier.

ORA-16195: DG_CONFIG requires DB_UNIQUE_NAME be explicitly defined

Cause: The DG_CONFIG attribute of the LOG_ARCHIVE_CONFIG parameter can only be used if the DB_UNIQUE_NAME parameter has been explicitly defined.

Action: Explicitly define a valid DB_UNIQUE_NAME.

ORA-16196: database has been previously opened and closed

Cause: The instance has already opened and closed the database, which is allowed only once in its lifetime.

Action: Shut down the instance.

ORA-16197: Invalid DB_UNIQUE_NAME parameter specification

Cause: The DB_UNIQUE_NAME parameter has an invalid specification. The DB_UNIQUE_NAME parameter has a maximum length of 30 characters and the only characters allowed are alpha-numeric characters and "_", "$" and "#".

Action: Check the documentation and re-enter the parameter.

ORA-16198: Timeout incurred on internal channel during remote archival

Cause: A timeout was incurred during remote archival.

Action: No action is required, as an attempt will be made to re-archive the file that had this failure during archival.

ORA-16199: Terminal recovery failed to recover to a consistent point

Cause: See alert log for more details

Action: Try to resolve the problem. Retry terminal recovery. If the problem occurs repeatedly and cannot be resolved, call Oracle support.

ORA-16200: Skip procedure requested to skip statement

Cause: Logical standby called a skip procedure that requested for a particular statement not to be applied.

Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.

ORA-16201: Skip procedure requested to apply statement

Cause: Logical standby called a skip procedure that requested for a particular statement to be applied.

Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.

ORA-16202: Skip procedure requested to replace statement

Cause: Logical standby called a skip procedure that requested for a particular statement to be replaced with a new statement.

Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.

ORA-16203: Unable to interpret skip procedure return values

Cause: The skip procedure returned conflicting or invalid values.

Action: Ensure that the new_statement output parameter is non-NULL when returning DBMS_LOGSTDBY.SKIP_ACTION_REPLACE and NULL otherwise. Also ensure SKIP_ACTION is specified correctly.

ORA-16204: DDL successfully applied

Cause: A DDL statement has successfully commited on the logical standby database.

Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.

ORA-16205: DDL skipped due to skip setting

Cause: A setting in the logical standby skip table indicates that this type of DDL should always be skipped.

Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.

ORA-16206: database already configured as Logical Standby database

Cause: This database has been previously configured as a Logical Standby database. A Logical Standby database is not capable of processing the requested operation.

Action: Ensure that you entered the command on the correct database as this database is a Logical Standby and is not capable of servicing the request.

ORA-16207: Logical standby dictionary build not permitted.

Cause: A dictionary build is currently in progress. Only one build can be active at a time.

Action: Wait for the active build to complete before invoking a new build.

ORA-16208: Logical standby dictionary build failed to start.

Cause: Failure to start the logical standby dictionary build process (LSP1)

Action: Check the accompanying messages, and the background process trace file. Correct the problem mentioned in the messages. Then shut down and restart the instance. If the trace file mentions any other background process messages, check the trace file for the mentioned process until the root message is found.

ORA-16209: Logical standby dictionary build failed to complete.

Cause: The logical standby dictionary build process terminated abnormally.

ORA-16210: Logical standby coordinator process terminated with error

Cause: The logical standby coordinator process terminated abnormally.

ORA-16211: unsupported record found in the archived redo log

Cause: Log apply services encountered a record in the archived redo log that could not be interpreted.

Action: 1. Use DBMS_LOGSTDBY.INSTANTIATE_TABLE to re-create the table on the standby database or simply drop the table if it's unimportant.

2. ALTER DATABASE START LOGICAL STANDBY APPLY;

3. Examine the current_scn column in the DBA_LOGSTDBY_EVENTS view to determine which log file contains the unsupported record.

4. Provide the log file to Oracle Support Services.

ORA-16212: number of processes specified for SQL Apply is too great

Cause: Logical standby apply engine was started with more processes requested than are available.

Action: Adjust the values of the initialization parameters PROCESSES or the MAX_SERVERS parameter seen in the DBA_LOGSTDBY_PARAMETERS view. If you did not specify MAX_SERVERS, but instead specified PREPARE_SERVERS and APPLY_SERVERS through the dbms_logstdby.apply_set procedure, you will need to decrease either one or both of them.

ORA-16213: ddl encountered, stopping apply engine

Cause: stop_on_ddl callout specified and DDL was encountered.

Action: Either disable stop_on_ddl callout or remove DDL.

ORA-16214: apply stalled for apply delay

Cause: A delay has been specified on the primary database for this destination.

Action: Either turn off the delay on the primary or use DBMS_LOGSTDBY.APPLY_UNSET('APPLY_DELAY'); to override.

ORA-16215: history metadata inconsistency

Cause: internal error.

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

ORA-16216: Log stream sequence error

Cause: The log stream being processed did not follow the last processed stream.

Action: If the database is in an active configuration, issue an ALTER DATABASE START LOGICAL STANDBY APPLY NEW PRIMARY command to synchronize log stream data with the current primary database. If the database is not in an active configuration, manually add the next dictionary-begin logfile that followed the previous log stream.

ORA-16217: prepare to switchover has not completed

Cause: An ALTER DATABASE PREPARE TO SWITCHOVER command was issued, but the prepare activity did not complete.

Action: Verify that the standby was prepared properly. You may cancel the prepare and perform an unprepared switchover which requires a database link to complete. Or reissue the prepare operation on the standby.

ORA-16218: This database is already preparing to switch over.

Cause: The database was already preparing to switch over and was not able to accomodate another prepare attempt.

Action: Cancel the current prepare attempt with the ALTER DATABASE PREPARE TO SWITCHOVER CANCEL command, then reissue the prepare request.

ORA-16219: This database is not preparing to switch over.

Cause: The database was not preparing to switch over. Therefore, it was not possible to cancel the SWITCHOVER command.

Action: Preparing for the SWITCHOVER command can be accomplished with the ALTER DATABASE PREPARE TO SWITCHOVER command.

ORA-16220: no failed transaction found

Cause: No failed transaction was found.

Action: Retry the ALTER DATABASE START LOGICAL STANDBY APPLY command without the SKIP FAILED TRANSACTION option.

ORA-16221: history table synchronization error

Cause: internal error.

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

ORA-16222: automatic Logical Standby retry of last action

Cause: A failure occurred while running Logical Standby apply. A new attempt is automatically being made by Logical Standby apply.

Action: No action is necessary. This informational statement is provided to record the event for diagnostic purposes.

ORA-16223: DDL skipped, unsupported in current version

Cause: The given DDL statement was not supported in the current version of Logical Standby and was skipped.

Action: No action is necessary. This informational statement is provided to record the event for diagnostic purposes.

ORA-16224: Database Guard is enabled

Cause: Operation could not be performed because database guard is enabled

Action: Verify operation is correct and disable database guard

ORA-16225: Missing LogMiner session name for Streams

Cause: An attempt was made to register the log file for Streams without a specified LogMiner session name.

Action: Specify a valid LogMiner session name to which the log file will be registered.

ORA-16226: DDL skipped due to lack of support

Cause: Logical Standby does not support this type of DDL in this version, so the DDL is skipped.

Action: The DBA may apply the DDL explicitly at a later time or a procedure to handle this type of DDL can be created. see DBMS_LOGSTDBY.SKIP procedure for details.

ORA-16227: DDL skipped due to missing object

Cause: A table or other database object upon which this DDL depends is not defined on the Logical Standby database.

Action: No action is necessary, this infomational statement is provided to record the event for diagnostic purposes.

ORA-16228: Insufficient recovery for logical standby

Cause: Insufficient amount of recovery was run for logical standby instantiation.

Action: Continue to recover the database using ALTER DATABASE RECOVER MANAGED STANDBY DATABASE.

ORA-16229: PDML child string string string for parent string string string cannot be skipped.

Cause: A request was made to skip a parallel DML child transaction id. This is not supported.

Action: Using the DBMS_LOGSTDBY.UNSKIP_TRANSACTION procedure, remove the child transaction id, then specify the parent transaction id using DBMS_LOGSTDBY.SKIP_TRANSACTION if appropriate.

ORA-16230: committing transaction string string string

Cause: Logical Standby apply was committing changes for the given transaction.

Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.

ORA-16232: adding Logical Standby skip entry for table string.string

Cause: Table was previously unsupported due to datatype or storage attribute definitions. Table is now capable of being supported.

Action: To have Logical Standby maintain the table, import that table directly from the primary.

ORA-16233: The table string.string is unsupported now

Cause: Table was previously supported but now is unsupported due to altered datatype or storage attribute definitions.

Action: None

ORA-16234: restarting to reset Logical Standby apply

Cause: Logical Standby encountered a work load that required a restart to properly reschedule.

Action: No action necessary. This informational statement is provided to record the event for diagnostic purposes.

ORA-16235: DDL skipped because import has occurred

Cause: An object was exported from the primary database and imported into the Logical Standby database. This DDL occurred before the export.

Action: No action necessary. This informational statement is provided to record the event for diagnostic purposes.

ORA-16236: Logical Standby metadata operation in progress

Cause: The requested operation failed because a Logical Standby metadata operation, such as DBMS_LOGSTDBY.SET_TABLESPACE or DBMS_LOGSTDBY.INSTANTIATE_TABLE, has not finished.

Action: Wait for the Logical Standby metadata operation to finish, then re-enter or respecify the operation.

ORA-16237: SGA specified for Logical Standby is too small

Cause: MAX_SGA must be at least 10 Megabytes for proper functioning of Logical Standby.

Action: Specify the value of MAX_SGA to be greater than or equal to 10Mb. Alternatively, increase the shared_pool_size/sga_target so that 1/4 of it will amount to 10 Megabytes.

ORA-16238: attempt to use version 9 log

Cause: Version 9 log files are not supported.

Action: Use log files of a supported version.

ORA-16239: IMMEDIATE option not available without standby redo logs

Cause: The IMMEDIATE option cannot be used without standby redo logs.

Action: Do not specify the IMMEDIATE option unless standby redo logs are being used.

ORA-16240: Waiting for logfile (thread# string, sequence# string)

Cause: Reader process is idle waiting for additional logfile to be available.

Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.

ORA-16241: Waiting for gap logfile (thread# string, sequence# string)

Cause: Reader process is idle waiting for the logfile to fill the log sequence gap.

Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.

ORA-16242: Processing logfile (thread# string, sequence# string)

Cause: Reader process is processing the logfile.

Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.

ORA-16243: paging out string bytes of memory to disk

Cause: Builder process is paging out momery to free up space in lcr cache.

Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.

ORA-16246: User initiated abort apply successfully completed

Cause: SQL Apply was stopped using the abort option.

Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.

ORA-16247: DDL skipped on internal schema

Cause: Logical Standby ignores DDLs on internal schemas such as SYS and SYSTEM. For a complete list of internal schemas ignored by Logical Standby perform the following query: SELECT owner FROM dba_logstdby_skip WHERE statement_opt = 'INTERNAL SCHEMA'.

Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.

ORA-16248: RFS connections not permitted during Terminal Apply

Cause: Writes by RFS are not permitted while Logical Standby is performing Terminal Apply.

Action: Permit any outstanding Logical Standby operations to complete.

ORA-16249: Terminal apply failed to complete during failover

Cause: The logical standby coordinator process terminated abnormally."

Action: Examine the DBA_LOGSTDBY_EVENTS view for the reason behind the abnormal shutdown, and resolve accordingly. Once the problem has been rectified, reissue the ALTER DATABASE ACTIVATE LOGICAL STANDBY DATABASE command to complete the failover.

ORA-16250: Failed to acquire starting scn of new log stream

Cause: The starting SCN for the new log stream could not be determined.

Action: Please reissue the ACTIVATE LOGICAL STANDBY DATABASE command.

ORA-16251: LSP1 Background Build not permitted

Cause: The LSP1 background process is not permitted to start because it had previously been attempted.

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

ORA-16252: Rebuild operation not permitted

Cause: The REBUILD operation is not permitted.

Action: Only on a primary database that has failed to complete the LogMiner dictionary build may the REBUILD operation take place. Reissue the ACTIVATE LOGICAL STANDBY DATABASE command if it previously failed to complete.

ORA-16253: Logical Standby cannot start due to incomplete terminal apply

Cause: A previous ACTIVATE of the logical standby failed to complete.

Action: Reissue the ALTER DATABASE ACTIVATE LOGICAL STANDBY DATABASE FINISH APPLY command.

ORA-16254: change db_name to string in the client-side parameter file (pfile)

Cause: An ALTER DATABASE RECOVER TO LOGICAL STANDBY new-dbname command was successfully executed without a server parameter file (spfile).

Action: The client-side parameter file must be edited so that db_name is set to the given name before mounting the database again.

ORA-16255: Log Auto Delete conflicts with another LogMiner session

Cause: Log Auto Delete cannot be on while another LogMiner session is running on the same database.

Action: Start Logical Standby without Log Auto Delete or destroy other LogMiner sessions first.

ORA-16256: Failure to complete standby redo logfile archival after failover

Cause: The standby redo logfiles processed during the failover of a logical standby were not archived.

Action: Execute DBMS_LOGSTDBY.REBUILD to reattempt the archival.

ORA-16257: Switchover initiated stop apply successfully completed

Cause: SQL Apply was stopped because of a switchover.

Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.

ORA-16258: marking index unusable due to a constraint violation

Cause: A constraint violation occurred during the apply of a direct path load. The index will be marked unusable and the apply will be restarted.

Action: No action necessary. See alert log for index schema and name.

ORA-16259: Switchover to logical standby requires a log archive destination

Cause: A valid log archive destination was not found to which the local system could archive the EOR logfile. A minimum of one destination is required.

Action: Ensure all log archive destinations are properly configured and, if applicable, have network connectivity before re-issuing the ALTER DATABASE COMMIT TO SWITCHOVER TO LOGICAL STANDBY DDL operation.

ORA-16260: Waiting to replace partial or corrupt logfile (thread# string, sequence# string)

Cause: LogMiner Reader process reached end of a partial logfile or encountered a corrupted block. It is now waiting for the logfile to be recovered and re-registered.

Action: No action necessary. Once the FAL archiver replaces the logfile, standby will automatically restart to process the replaced file.

ORA-16261: Identification key mismatch for table "string"."string".

Cause: Internal error in SQL Apply.

Action: Contact Oracle Support Services.

ORA Error . Listado Errores Oracle. ORA-16037 a ORA-16157

2013-06-02T12:45:00.000-07:00

ORA-16037: user requested cancel of managed recovery operation

Cause: The managed standby database recovery operation has been canceled per user request.

Action: No action is required.

ORA-16038: log string sequence# string cannot be archived

Cause: An attempt was made to archive the named file, but the file could not be archived. Examine the secondary error messages to determine the cause of the error.

Action: No action is required.

ORA-16039: RFS request version mismatch

Cause: A request to archive a redo log to a standby site failed because the request was incompatible with the Remote File Server (RFS) at the standby site.

Action: Verify that compatible versions of Oracle are running on the primary and all standby sites.

ORA-16040: standby destination archive log file is locked

Cause: The target standby destination archive log file is currently locked. This indicates that the file is being archived to by another Remote File Server (RFS) process.

Action: Check for and eliminate duplicate standby destination archive log service names defined for the primary database.

ORA-16041: Remote File Server fatal error

Cause: The Remote File Server (RFS) process at the standby destination archive log site has encountered a disabling error and is no longer available. Further archiving to the standby site may not be possible.

Action: Refer to the appropriate RFS trace file located at the standby site for details regarding the error encountered and if possible take corrective action.

ORA-16042: user requested cancel immediate of managed recovery operation

Cause: The managed standby database recovery operation has been canceled immediately per user request. Processing of the current archive log file has been interrupted and therefore the database is in an inconsistent state.

Action: No action is required.

ORA-16043: managed recovery session canceled

Cause: The standby database managed recovery operation has been canceled per user request or operation timeout.

Action: More specific messages will accompany this message.

ORA-16044: destination string attribute cannot be specified at session level

Cause: An archive log destination attribute was attempted to be modified at the session level.

Action: Use the ALTER SYSTEM command to modify the destination attribute.

ORA-16045: circular archive log destination dependency chain

Cause: An archive log destination contains a dependency to another archive log destination that also contains a dependency.

Action: The parent archive log destination cannot be dependent on another archive log destination. Use the ALTER SYSTEM command to remove one of the dependency attributes.

ORA-16046: Archive log destination failed due to failed dependent destination

Cause: The archive log destination is dependent upon another destination, which has failed. Therefore, this destination also fails.

Action: No action required.

ORA-16047: DGID mismatch between destination setting and standby

Cause: The DB_UNIQUE_NAME specified for the destination does not match the DB_UNIQUE_NAME at the destination.

Action: Make sure the DB_UNIQUE_NAME specified in the LOG_ARCHIVE_DEST_n parameter defined for the destination matches the DB_UNIQUE_NAME parameter defined at the destination.

ORA-16050: destination exceeded specified quota size

Cause: An archive log was attempted to be created in a destination with a specified maximum quota size. The creation of the archive log exceeded the specified quota size. Therefore, the destination has been made inaccessible to future archival operations.

Action: No action is required.

ORA-16051: parameter string contains an invalid delay time

Cause: The value for the specified LOG_ARCHIVE_DEST_n (n = 1...10) parameter contained a DELAY attribute with an invalid numeric value. The valid range is 0-5760 (in minutes).

Action: Correct the value for the indicated LOG_ARCHIVE_DEST_n parameter.

ORA-16052: DB_UNIQUE_NAME attribute is required

Cause: The DB_UNIQUE_NAME attribute is required when DG_CONFIG is enabled.

Action: Use the DB_UNIQUE_NAME attribute to specify a valid Data Guard Name for the destination. The list of valid DB_UNIQUE_NAMEs can be seen with the V$DATAGUARD_CONFIG view.

ORA-16053: DB_UNIQUE_NAME string is not in the Data Guard Configuration

Cause: The specified DB_UNIQUE_NAME is not in the Data Guard Configuration.

Action: If the DG_CONFIG attribute of the LOG_ARCHIVE_CONFIG parameter is enabled, you must specify a valid DB_UNIQUE_NAME. The list of valid DB_UNIQUE_NAMEs can be seen with the V$DATAGUARD_CONFIG view. This problem can also occur when specifying a non-standby destination with an DB_UNIQUE_NAME attribute that does not match the DB_UNIQUE_NAME initialization parameter for the current instance.

ORA-16055: FAL request rejected

Cause: FAL server rejects the FAL request from the FAL client. This may be caused by different reasons.

Action: to solve the problem.

ORA-16056: backup control file archival requires proper syntax

Cause: An attempt was made to perform an online log file archival using a backup control file. However, the USING BACKUP CONTROLFILE syntax was not specified.

Action: If the archival operation is correct when using a backup control file, then the USING BACKUP CONTROLFILE syntax is required.

ORA-16057: DGID from server not in Data Guard configuration

Cause: The Data Guard name of the primary database or the FAL server is not in the Data Guard configuration of the standby.

Action: In order for the primary database or the FAL server to archive logs to the standby database, the Data Guard name of the primary or FAL server must be in the Data Guard configuration of the standby.

ORA-16058: standby database instance is not mounted

Cause: The RFS process on the standby database received an internal error.

Action: Check the standby alert log and RFS trace files for more information.

ORA-16059: Log file is empty or invalid next available block

Cause: Archiving not allowed of an empty or invalid log file.

Action: No action is required.

ORA-16060: Log file is current

Cause: The current log file cannot be archived using its file name.

Action: No action is required.

ORA-16061: Log file status has changed

Cause: It is possible the online log file was reclaimed as a new log file either before archival started, or during the archival operation.

Action: No action is required.

ORA-16062: DGID from standby not in Data Guard configuration

Cause: The Data Guard name from the standby is not in the Data Guard configuration of the server.

Action: In order for the server to be allowed to archive logs to the standby, the Data Guard name of the standby must be in the Data Guard configuration of the server.

ORA-16063: remote archival is enabled by another instance

Cause: Remote archival of database REDO log files has been enabled by another instance, and cannot be disabled for this instance.

Action: Set the REMOTE_ARCHIVE_ENABLE parameter to TRUE and restart this instance.

ORA-16064: remote archival is disabled by another instance

Cause: Remote archival of database REDO log files has been disabled by another instance, and cannot be enabled for this instance.

Action: Set the REMOTE_ARCHIVE_ENABLE parameter to FALSE and restart this instance.

ORA-16065: remote archival disabled at standby destination

Cause: Receipt of remote archived REDO log files has been disabled at the associated standby destination host database.

Action: If appropriate change the associated archive log parameter to specify a local destination with the LOCATION keyword or defer the associated archive log destination. Or, if possible, set the standby REMOTE_ARCHIVE_ENABLE parameter to TRUE, or enable the RECEIVE attribute of the LOG_ARCHIVE_CONFIG parameterand restart the standby database instance before further REDO log file archivals occur.

ORA-16066: remote archival disabled

Cause: An archive log destination parameter has specified a remote destination with the SERVICE keyword. Remote archival of REDO log files has been disabled for this database. The associated archive log destination has been disabled.

Action: If appropriate change the archive log parameter to specify a local destination with the LOCATION keyword or (if appropriate) set the REMOTE_ARCHIVE_ENABLE parameter to TRUE, or enable the SEND attribute of the LOG_ARCHIVE_CONFIG parameter and restart the database instance before further REDO log file archivals occur.

ORA-16067: activation identifier mismatch in archive log string

Cause: The activation identifier contained in the archive log file header does not match the activation identifier of the database being recovered. The indicated archive log cannot be applied to the database.

Action: Locate the appropriate archive log for the database.

ORA-16068: redo log file activation identifier mismatch

Cause: The activation identifier of the indicated redo log file does not match the activation identifier of the database.

Action: None

ORA-16069: Archive Log standby database activation identifier mismatch

Cause: The activation identifiers of the Primary and Standby database do not match. Remote archival of redo log files is not allowed to incompatible STANDBY database instances. This can occur when trying to apply an incorrect archive log to a standby database, or when trying to archive to a standby database that does not match the primary database.

Action: Take the necessary steps to create the required compatible STANDBY database before retrying the ARCHIVE LOG processing.

ORA-16070: parameter string contains an invalid REGISTER attribute value

Cause: The value for the specified LOG_ARCHIVE_DEST_n (n = 1...10) parameter contained a REGISTER attribute that specified an invalid file name template string. If specified, the REGISTER file name template string must indicate an O/S-specific file path name including thread and log sequence number substitution directives (%t, %T, %s, %S).

Action: Correct the value for the LOG_ARCHIVE_DEST_n parameter.

ORA-16071: dependency archived log file not found string

Cause: The specified archived log file was not found at the indicated standby destination.

Action: Verify the correctness of the dependency archived log file name template specified for the indicated standby destination against the actual dependency archived log file.

ORA-16072: a minimum of one standby database destination is required

Cause: No standby database archive log destinations were specified.

Action: Specify a standby archive log destination in the initialization parameter file.

ORA-16073: archiving must be enabled

Cause: Online log file archiving is disabled.

Action: Enable log file archiving.

ORA-16074: ARCH processes must be active

Cause: There are no active ARCH processes.

Action: It is required that at least one ARCH process be active.

ORA-16075: standby database destination mismatch

Cause: A standby database destination was specified that is not accessed by another instance.

Action: All database instances must access the same standby databases.

ORA-16076: unknown standby database destination

Cause: A standby database destination was specified that is not accessed by another instance.

Action: All database instances must access the same standby databases.

ORA-16078: media recovery disabled

Cause: The database is not in ARCHIVELOG mode.

Action: Place the database in ARCHIVELOG mode.

ORA-16079: standby archival not enabled

Cause: The standby database does not have archival enabled.

Action: In order to allow the standby database to access the standby log files, the ARCH process must be enabled and active.

ORA-16080: invalid LogMiner session string for APPLY

Cause: Logical standby apply engine was started with an invalid LogMiner session identifier.

Action: Fix the problem with the LogMiner session or create a new session.

ORA-16081: insufficient number of processes for APPLY

Cause: Logical standby apply engine was started with fewer processes available than needed.

Action: Increase the values of the initialization parameters PROCESSES and or the MAX_SERVERS parameter seen in the DBA_LOGSTDBY_PARAMETERS view.

ORA-16082: logical standby is not initialized correctly

Cause: Logical standby apply engine was started but it found inconsistencies in its metadata.

Action: Look in the trace file for more information.

ORA-16083: LogMiner session has not been created

Cause: Logical standby apply engine was started without creating a LogMiner session.

Action: Create a LogMiner session and restart the apply engine.

ORA-16084: an apply engine is already running

Cause: A logical standby apply engine was running when another was created.

Action: Shut down the previous apply engine before starting a new one.

ORA-16086: standby database does not contain available standby log files

Cause: The primary database is in "no data loss" mode, but the standby database does not contain any "standby log files".

Action: Add one or more standby log files to the standby database. This can be done while the standby database is mounted.

ORA-16087: graceful switchover requires standby or current control file

Cause: An attempt was made to perform a graceful switchover operation using a backup or clone control file.

Action: Convert the backup control file into a current control file prior to attempting a graceful switchover operation. A clone control file cannot be used for a graceful switchover operation.

ORA-16088: archive log has not been completely archived

Cause: An attempt was made to register an archive log that has not been completely archived. The specified archive log may be a "current" log file.

Action: Specify a completed archive log.

ORA-16089: archive log has already been registered

Cause: An attempt was made to register an archive log that already has a corresponding thread# and sequence# entry in the standby database control file. Duplicate information is not permitted.

Action: Use the V$ARCHIVED_LOG fixed view to verify the archive log information.

ORA-16090: archive log to be replaced not created by managed standby process

Cause: An attempt was made to replace an archive log entry that was not originally created by the managed standby operation.

Action: No user action required.

ORA-16091: dependent archive log destination already archived

Cause: An archive log destination contains a dependency to another archive log destination that has previously been archived.

Action: The parent archive log destination cannot be dependent on another archive log destination. Use the ALTER SYSTEM command to remove one of the dependency attributes.

ORA-16092: dependent archive log destination is not active

Cause: An archive log destination contains a dependency to another archive log destination that is not active"

Action: The child archive log destination cannot be dependent on another invalid archive log destination. Use the ALTER SYSTEM command to remove one of the dependency attributes.

ORA-16093: dependent archive log destination is not LGWR-enabled

Cause: An archive log destination contains a dependency to another archive log destination that is not enabled for the LGWR process"

Action: The child archive log destination cannot be dependent on another archive log destination not archived by the LGWR. Use the ALTER SYSTEM command to change the parent archive log to specify the LGWR process.

ORA-16094: database shutdown during archival operation

Cause: The database was shut down while an online log file archival was active.

Action: None required. The ARCH process is terminated.

ORA-16095: Dependent destination removal for inactivation

Cause: A dependent archive log destination was inactivated due to the parent archive log destination becoming inelligible for archival. This may be due to the parent destination being manually deferred by an application user.

Action: None required.

ORA-16098: inaccessible standby database forced shutdown to protect primary

Cause: No standby database archive log destinations remain accessible and the primary database is in "protected" no-data-loss mode.

Action: Specify an alternate standby archive log destination in the initialization parameter file.

ORA-16099: internal error

ORA-00600 occurred at standby database

Cause: The RFS process on the standby database received an internal error.

Action: Check the standby alert log and RFS trace files for more information.

ORA-16100: not a valid Logical Standby database

Cause: This database has not been completely configured as a Logical Standby database.

Action: Verify that the database is the intended Logical Standby database. Ensure that you already started logical standby apply with the ALTER DATABASE START LOGICAL APPLY INITIAL statement. See the Oracle8i SQL Reference manual for the statement syntax.

ORA-16101: a valid start SCN could not be found

Cause: An SCN from which to start could not be found.

Action: Register the first log file following the backup from which this database was generated. Using the ALTER DATABASE REGISTER LOGILE statement to register the database is recommended. Alternatively, you can provide a starting SCN value with this startement.

ORA-16102: remote information is not available on the specified primary

Cause: The new primary has not completed generating the necessary information for the standby to begin consuming its log stream.

Action: Verify that the database link provided references a system that is about to become a new primary. Wait a short time before retrying the command to allow the primary some time to generate the necessary information.

ORA-16103: Logical Standby apply must be stopped to allow this operation

Cause: Logical Standby is currently applying changes. The apply must complete or be stopped to allow the requested operation.

Action: Execute the ALTER DATABASE STOP LOGICAL STANDBY APPLY statement, then re-enter or respecify the operation.

ORA-16104: Invalid Logical Standby parameter

Cause: The specified parameter is not valid.

Action: Check spelling or refer to the DBMS_LOGSTDBY PL/SQL package documentation for the correct statement syntax.

ORA-16105: Logical Standby is already running in background

Cause: A Logical Standby apply operation is already running.

Action: None

ORA-16107: all log data from primary has been processed

Cause: On the primary system, the log stream has been ended by the ALTER DATABASE COMMIT TO SWITCHOVER TO LOGICAL STANDBY command.

Action: Issue one of the following commands to make this standby a primary or resume applying changes from a new primary. ALTER DATABASE COMMIT TO SWITCHOVER TO LOGICAL PRIMARY; ALTER DATABASE START LOGICAL STANDBY APPLY NEW PRIMARY dblink;

ORA-16108: database is no longer a standby database

Cause: The current database has already been made a primary database.

Action: Issue the following commands to make this primary a standby. ALTER DATABASE COMMIT TO SWITCHOVER TO LOGICAL STANDBY; ALTER DATABASE START LOGICAL STANDBY APPLY NEW PRIMARY dblink;

ORA-16109: failed to apply log data from previous primary

Cause: Log data from previous primary could not be completely applied.

Action: . Then, re-issue command.

ORA-16110: user procedure processing of logical standby apply DDL

Cause: A user provided stored procedure has been called to inspect a DDL statement prior to it being processed.

ORA-16111: log mining and apply setting up

Cause: This logical standby process is setting up to begin processing changes.

Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.

ORA-16112: log mining and apply stopping

Cause: This logical standby process is cleaning up and stopping Logical Standby apply.

Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.

ORA-16113: applying change to table or sequence string

Cause: The process is applying changes to a specific schema object.

Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.

ORA-16114: applying DDL transaction with commit SCN string

Cause: The process is applying a DDL change that's committed at the given SCN.

Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.

ORA-16115: string\% of LogMiner dictionary loading is done

Cause: The process is loading dictionary information from the redo stream. This activity may take a few minutes.

Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.

ORA-16116: no work available

Cause: The process is idle waiting for additional changes to be made available.

Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.

ORA-16117: processing

Cause: The process is performing its primary function and is not waiting on any significant event.

Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.

ORA-16119: building transaction at SCN string

Cause: The transaction being committed at the given SCN is being prepared for apply.

Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.

ORA-16120: dependencies being computed for transaction at SCN string

Cause: The transaction committed at the given SCN is being analyzed for dependencies.

Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.

ORA-16121: applying transaction with commit SCN string

Cause: The transaction committed at the given SCN is being applied.

Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.

ORA-16122: applying large dml transaction at SCN string

Cause: A large transaction is being applied before the commit has been seen. The current redo being applied ends as the given SCN.

Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.

ORA-16123: transaction string string string is waiting for commit approval

Cause: The apply process is waiting for approval to commit a transaction. This transaction may depend on another or other synchronization activity may delay the committing of a transaction.

Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.

ORA-16124: transaction string string string is waiting on another transaction

Cause: The apply process is waiting to apply additional changes. This transaction likely depends on another.

Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.

ORA-16125: large transaction string string string is waiting for more data

Cause: The apply process is waiting until additional changes for a large transaction are retrieved from the log stream.

Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.

ORA-16126: loading table or sequence string

Cause: Information on the given table or sequence is being loaded into an in memory cache for future use.

Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.

ORA-16127: stalled waiting for additional transactions to be applied

Cause: This process is waiting for additional memory before continuing. Additional log information cannot be read into memory until more transactions have been applied to the database, thus freeing up additional memory.

Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes. If this message occurs often and changes are not being applied quickly, increase available SGA or the number of apply processes.

ORA-16128: User initiated stop apply successfully completed

Cause: Logical standby was shutdown in an orderly fashion.

Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.

ORA-16129: unsupported dml encountered

Cause: DML to tables in the SYS schema have been updated and are not part of a DDL operation. This may be due to some DBA activity or DML associated with a kernel PL/SQL request that Logical Standby does not yet support.

Action: Check the DBA_LOGSTDBY_EVENTS table for the name of the table being processed. Possibly use Log Miner to understand the transaction, and provide a compensating transaction on the standby system. Once complete, call DBMS_LOGSTDBY.SKIP_TRANSACTION with the associated transaction id, and resume apply.

ORA-16130: supplemental log information is missing from log stream

Cause: Supplemental logging is not enabled at the primary database.

Action: Issue the following command to enable supplemental logging. ALTER DATABASE ADD SUPPLEMENTAL LOG DATA (PRIMARY KEY, UNIQUE INDEX) COLUMNS;

ORA-16131: An error occurred during a Terminal Recovery of the standby.

Cause: An error occurred during a Terminal Recovery of the standby.

Action: Check the standby alert log additional information.

ORA-16132: An error occurred during activation of the standby.

Cause: An error occurred during activation of the standby database following a Terminal Recovery.

Action: Check the standby alert log additional information.

ORA-16133: Datafile string has incorrect terminal recovery stamp.

Cause: After activation of a standby database following a terminal recovery (recovery of standby using current logs), recovery of a datafile from before the activation must have completed the same terminal recovery to avoid corruption.

Action: A backup of the datafile taken after the terminal recovery and before activating the standby must be used for recovery.

ORA-16134: invalid MANAGED recovery FINISH option

Cause: A mode other than NOWAIT follows the FINISH keyword in RECOVER MANAGED STANDBY DATABASE statement.

Action: Specify either nothing or NOWAIT following FINISH.

ORA-16135: Invalid LOG_ARCHIVE_CONFIG modification while in protected mode

Cause: The LOG_ARCHIVE_CONFIG parameter can not be modified while any RAC instance is open in either maximum protection or maximum availability mode. Also, the parameter can not be modified in such way that would cause all destinations to fail while in maximum protection mode.

Action: Make the modification before the database is opened by any instance.

ORA-16136: Managed Standby Recovery not active

Cause: An attempt was made to cancel a managed recovery session but no managed recovery session was active.

Action: No action is necessary.

ORA-16138: end of log stream not received from primary

Cause: The standby system has not received notification that the primary system log stream has been terminated. A graceful switchover is not possible.

Action: Verify that the primary log stream has been terminated. Ensure that the standby has applied all necessary redo from the primary system and, if appropriate, reissue the graceful switchover command.

ORA-16139: media recovery required

Cause: An error has occurred while performing a switchover.

Action: If you were switching a primary database to the standby role, the conversion was successful, but one or more errors occurred after the conversion completed. See the alert log for more information. You can proceed with switching the target standby database to the primary role, but you must address the errors reported at the old primary database before it can protect the new primary database. If you encountered this error while switching a physical standby database to the primary role, the switchover did not succeed because additional redo must be applied. Verify that redo apply is active and wait until the SWITCHOVER_STATUS column of the V$DATABASE dynamic performance view reports TO_PRIMARY or SESSIONS_ACTIVE before retrying the switchover.

ORA-16140: standby online logs have not been recovered

Cause: The standby database has online logs containing redo that has not been recovered. Activating the standby would lose redo contained in the online logs.

Action: To recover the standby online logs issue the following command: ALTER DATABASE RECOVER MANAGED STANDBY DATABASE FINISH. Then re-issue the ALTER DATABASE ACTIVATE STANDBY DATABASE command. To activate the standby without recovering the online logs, issue the following command: ALTER DATABASE ACTIVATE STANDBY DATABASE SKIP STANDBY LOGFILE.

ORA-16143: RFS connections not allowed during or after terminal recovery

Cause: An attempt was made, by an RFS process, to access a standby online log file during or after a terminal recovery.

Action: The primary must not attempt to archive to the standby after a terminal recovery.

ORA-16145: archival for thread# string sequence# string in progress

Cause: The indicated archived log file is not available for recovery due to the fact that it is still being archived.

Action: Verify that archival of the indicated log file has completed and reissue the RECOVER STANDBY DATABASE command.

ORA-16146: standby destination control file enqueue unavailable

Cause: The target standby destination control file is currently unavailable to the Remote File Server (RFS) process. This indicates that the target destination is the primary database itself.

Action: Check for and eliminate the standby destination archive log parameter in question.

ORA-16147: standby database referenced by multiple archive log destinations

Cause: Multiple archive log destinations reference the same standby database, using different service names. This is not allowed.

Action: Remove one of the duplicate archive log destinations.

ORA-16148: user requested expiration of managed recovery operation

Cause: The managed standby database recovery operation has been canceled per user specified EXPIRE option of the RECOVER MANAGED STANDBY DATABASE statement.

Action: No action is required.

ORA-16150: FINISH recovery performed on another, older standby database

Cause: An archive log containing a FINISH recovery indicator was received by a standby database that has received archive logs in the future of the received archive log. Because of the possibility that these future archive logs have been applied to this standby database, the received archive log must be rejected.

Action: No action is required.

ORA-16151: Managed Standby Recovery not available

Cause: The attempted operation failed because of a pending CANCEL of the managed standby recovery operation.

Action: Wait for the managed standby recovery session to end. Then retry the operation.

ORA-16152: standby database is in 'no-data-loss' protected mode

Cause: The attempted database operation is not allowed while the standby database is in 'no-data-loss' protected mode.

Action: Verify that the attempted database operation is warranted, ALTER DATABASE SET STANDBY DATABASE UNPROTECTED and reissue the statement.

ORA-16154: suspect attribute: string

Cause: Use of the indicated attribute is illegal in the given context.

Action: Make the appropriate changes and reissue the statement.

ORA-16156: LGWR archive log dependency not allowed if database is standby protected

Cause: The use of a LGWR archive log dependency is not allowed when the primary is protected by a standby database, as this requires use of the standby redo log files.

Action: Remove the LGWR archive log dependency and use normal LGWR archival instead.

ORA-16157: media recovery not allowed following successful FINISH recovery

Cause: A RECOVER MANAGED STANDBY DATABASE FINISH command has previously completed successfully. Another media recovery is not allowed.

Action: Issue one of these operations following a FINISH recocvery: ALTER DATABASE OPEN READ ONLY or ALTER DATABASE COMMIT TO SWITCHOVER TO PRIMARY.

ORA Error . Listado Errores Oracle. ORA-15451 a ORA-16036

2013-06-02T12:43:00.000-07:00

ORA-15451: missing or invalid volume size specifier

Cause: The volume size specified was invalid.

Action: Specify a valid volume size.

ORA-15452: missing or invalid stripe width specifier

Cause: The volume stripe width specified was invalid.

Action: Specify a valid volume stripe width.

ORA-15453: invalid STRIPE_COLUMNS specifier

Cause: An ADD VOLUME command did not specify a valid number of stripe columns.

Action: Specify a valid number of stripe columns.

ORA-15454: ALTER DISKGROUP ALL cannot use single volume names

Cause: An ALTER DISKGROUP ALL command specified a single volume or a list of volumes

Action: Use the ALL keyword when specifying volumes on multiple diskgroups.

ORA-15455: FORCE option cannot be used when specifying ALL volumes

Cause: The FORCE option was used to disable ALL volumes.

Action: Use FORCE option to disable one volume at a time.

ORA-15456: missing or invalid volume usage specifier

Cause: The command did not specify a valid volume usage string.

Action: Specify a valid volume usage string with alphanumeric characters.

ORA-15457: first letter of the volume name is not alphabetic

Cause: A volume name was specified with a nonalphabetic first character.

Action: Set the first character of the volume name to be alphabetic.

ORA-15458: invalid character in volume name

Cause: A volume name was specified with an invalid character.

Action: Use a volume name with only alphanumeric characters.

ORA-15459: STRIPE_WIDTH of string is not a power of two

Cause: An ADD VOLUME command specified a STRIPE_WIDTH that was not a power of two.

Action: Select a STRIPE_WIDTH that is a power of two; for example, 4K, 8K, etc.

ORA-15460: volume name 'string' is already in use

Cause: An ADD VOLUME command specified a volume name that was already used by another volume.

Action: Select a different name for the volume.

ORA-15461: STRIPE_WIDTH of string bytes is less than the minimum of string bytes

Cause: An ADD VOLUME command specified a STRIPE_WIDTH that was too small.

Action: Select a larger STRIPE_WIDTH.

ORA-15462: STRIPE_WIDTH of string bytes is greater than the maximum of string bytes

Cause: An ADD VOLUME command specified a STRIPE_WIDTH that was too large.

Action: Select a smaller STRIPE_WIDTH.

ORA-15463: volume size of stringK is less then the minimum of stringM

Cause: The volume size specified was too small.

Action: Select a larger volume size.

ORA-15464: STRIPE_COLUMNS of string is greater than the maximum of string

Cause: An ADD VOLUME command specified a STRIPE_COLUMNS that was that was too large.

Action: Select a smaller STRIPE_COLUMNS value.

ORA-15465: STRIPE_COLUMNS of string is less than the minimum of string

Cause: An ADD VOLUME command specified a STRIPE_COLUMNS that was too small.

Action: Select a larger STRIPE_COLUMNS value.

ORA-15466: volume name 'string' does not exist

Cause: The command specified a volume name that does not exist.

Action: Ensure a valid volume name is used.

ORA-15467: volume operation is already in progress

Cause: Another command is currently operating on the specified volume.

Action: Wait a short time before retrying the command.

ORA-15468: operation not permitted; volume 'string' currently being accessed

Cause: An attempt was made to communicate with the volume driver. The volume was being accessed by another application and, therefore, could not be changed.

Action: Shut down all applications that might be accessing this volume and then retry the command.

ORA-15469: VBG process terminated with error

Cause: A volume background process terminated with error.

Action: Wait for process to restart.

ORA-15470: VDBG process terminated with error

Cause: The volume driver background process terminated with error.

Action: Warm start instance.

ORA-15471: volume redundancy incompatible with diskgroup redundancy

Cause: An ADD VOLUME command specified a volume redundancy that was incompatible with the diskgroups redundancy.

Action: Specify a valid volume redundancy. A volume cannot have external redundancy with a high redundancy diskgroup. Also, a volume cannot have high redundancy with an external redundancy diskgroup.

ORA-15472: volume library cannot be loaded. Platform may not support volume creation.

Cause: The volume library could not be loaded. Either the platform does not support volume operations, or there is a problem with the library.

Action: Ensure that the platform supports volumes. If the platform does support volumes, check the alert log for library loading failure information.

ORA-15473: access to a volume's storage through an unsupported interface

Cause: An attempt was made to access or modify a volume's storage through an unsupported interface.

Action: Use supported interfaces for access to volume devices.

ORA-15474: volume name is greater than string characters

Cause: An ADD VOLUME command specified a volume name that was too long.

Action: Select a smaller volume name.

ORA-15475: usage string is greater than string characters

Cause: The usage string specified was too long.

Action: Select a smaller usage string.

ORA-15476: resize of OFS volume must use OFS resize command

Cause: An attempt was made to resize an OFS volume through SQL.

Action: Use the supported OFS commands to resize the volume.

ORA-15477: cannot communicate with the volume driver

Cause: An attempt was made to communicate with the volume driver.

Action: Check that the ASM volume driver is loaded. If so, check the alert log to identify the reason for failure and take necessary action to prevent such failures in the future.

ORA-15478: OFSC process terminated with error

Cause: The ofs background process terminated with error

Action: Wait for process restart

ORA-15479: diskgroup version incompatible with ASM volumes

Cause: The diskgroup's version was incompatible with creating volumes.

Action: Upgrade the diskgroup version in order to use volume functionality.

ORA-15480: error reported in the ASM volume driver

Cause: An error was reported in the ASM volume driver.

Action: Check the operating system log files to identify the reason for the failure and take necessary action to prevent such failures in the future.

ORA-15481: missing or invalid volume mountpath specifier

Cause: A invalid volume mountpath string was specified.

Action: Specify a valid volume mountpath string with alphanumeric characters.

ORA-15482: failed to create/remove path to volume device file

Cause: Improper driver installation.

Action: Check the alert log for device file creation failure information. Reload the driver using the supported installation method.

ORA-15501: cannot start workload capture on instance string

Cause: Given instance encountered unexpected errors while trying to start the workload capture.

Action: Check the alert log and other diagnostics in the given instance to diagnose the problem.

ORA-15502: cannot stop workload capture on instance string

Cause: Given instance encountered unexpected errors while trying to stop the workload capture.

Action: Check the alert log and other diagnostics in the given instance to diagnose the problem.

ORA-15503: cannot startup instance when procedures in "DBMS_WORKLOAD_CAPTURE" or "DBMS_WORKLOAD_REPLAY" are in the middle of their execution

Cause: The new instance could not be started because the database was executing a procedure in either the DBMS_WORKLOAD_CAPTURE or DBMS_WORKLOAD_REPLAY package.

Action: Start the new instance after such procedures in the given packages have finished execution.

ORA-15504: cannot start workload capture because instance string not present in RESTRICTED SESSION mode

Cause: The NO_RESTART_MODE option in DBMS_WORKLOAD_CAPTURE.START_CAPTURE was FALSE, therefore all the active instances were expected to be in the RESTRICTED SESSION mode.

Action: Start all instances using STARTUP RESTRICT or execute ALTER SYSTEM ENABLE RESTRICTED SESSION on all active instances before issuing DBMS_WORKLOAD_CAPTURE.START_CAPTURE.

ORA-15505: cannot start workload capture because instance string encountered errors while accessing directory "string"

Cause: Given instance could not access the specified CAPTURE directory or the specified CAPTURE directory already had a workload capture in it.

Action: Provide a directory object that is valid, empty and accessible from all the instances in the database cluster.

ORA-15506: cannot prepare instance string for replay

Cause: Given instance encountered unexpected errors while trying to prepare for a workload replay.

Action: Check the alert log and other diagnostics in the given instance to diagnose the problem.

ORA-15507: cannot start workload replay on instance string

Cause: Given instance encountered unexpected errors while trying to start a workload replay.

Action: Check the alert log and other diagnostics in the given instance to diagnose the problem.

ORA-15508: cannot cancel workload replay on instance string

Cause: Given instance encountered unexpected errors while trying to cancel a workload replay.

Action: Check the alert log and other diagnostics in the given instance to diagnose the problem.

ORA-15509: workload replay has been cancelled

Cause: Workload replay was cancelled.

Action: Restart the workload replay.

ORA-15510: cannot perform operation when "STATISTICS_LEVEL" is "BASIC"

Cause: The STATISTICS_LEVEL initialization parameter was set to BASIC.

Action: Change the STATISTICS_LEVEL initialization parameter setting to either TYPICAL or ALL.

ORA-15511: cannot process workload capture because no user sessions were recorded

Cause: No user sessions were recorded in the given workload capture. Processing this capture failed because no user workload was captured.

Action: Capture a workload in which at least one user session connects and performs some operations.

ORA-15512: directory "string" does not contain a valid processed workload capture

Cause: One or more files created by DBMS_WORKLOAD_REPLAY.PROCESS_CAPTURE were missing.

Action: Process the workload capture using DBMS_WORKLOAD_REPLAY.PROCESS_CAPTURE and then retry the command.

ORA-15513: cannot access the input directory

Cause: Given input directory is either invalid or inaccessible.

Action: Verify that the input directory is valid and accessible and then retry the command.

ORA-15514: cannot find a match for the remote procedure call during replay

Cause: The corresponding PL/SQL program was either dropped or modified.

Action: Verify that the corresponding PL/SQL program is defined the same way during replay as it was defined during workload capture.

ORA-15515: error while replaying remote procedure call: "string.string.string"

Cause: Error encountered during the replay of a remote procedure call.

Action: Correct the cause of the preceding error and restart workload replay.

ORA-15516: parallel preprocessing worker hit error

ORA-string

Cause: One of the parallel preprocessing workers died unexpectedly while processing the workload.

Action: Find the root cause or simply preprocess the workload using only one process.

ORA-15517: cannot start parallel preprocessing worker

Cause: One of the parallel preprocessing workers could not be started.

Action: Find the root cause or simply preprocess the workload using only one process.

ORA-15518: parallel preprocessing encountered an unexpected error

Cause: An unexpected error occured during parallel preprocessing.

Action: Find the root cause or simply preprocess the workload using only one process.

ORA-15551: workload replay client cannot connect to database server

Cause: The server connection identifier was invalid.

Action: Restart the client with correct server connection identifier.

ORA-15552: workload replay client cannot login to database server

Cause: 1) the replay client used an invalid username or password; 2) the replay user does not have the privilege to switch user; 3) the recorded username does not exist in the replay database.

Action: 1) restart replay client with correct username and password 2) grant user switching prvilege to the replay user 3) verify whether the replay database was restored properly

ORA-15553: workload replay client cannot execute the DBMS_WORKLOAD_REPLAY package

Cause: Workload Replay Client's replay user did not have EXECUTE permission on the DBMS_WORKLOAD_REPLAY package.

Action: Grant execute permission on the DBMS_WORKLOAD_REPLAY package to replay user and restart the Workload Replay Client.

ORA-15554: cannot start workload replay client because the database server is not in PREPARE mode

Cause: The Workload Replay Client could not connect to the database server because the database server was not in the PREPARE mode.

Action: Put the database in PREPARE mode by using DBMS_WORKLOAD_REPLAY.PREPARE_REPLAY, and restart the Workload Replay Client.

ORA-15555: workload replay client encountered unexpected error: "string"

Cause: Workload Replay Client encountered an unexpected error.

Action: Check the Workload Replay Client's log files and the database server alert log to diagnose the problem.

ORA-15556: invalid input specified to the workload replay client

Cause: Invalid input was specified.

Action: Use the Workload Replay Client's HELP=Y option to know more about valid input options.

ORA-15557: workload replay client cannot access the replay directory or the database version do not match the preprocessing one

Cause: The Workload Replay Client could not access the directory that contained the workload to be replayed, or the workload was preprocessed by a different version of the database.

Action: Restart the workload replay after specifying the correct replay directory, or preprocess it with the correct database.

ORA-15558: replay thread encountered unexpected error

Cause: A single replay thread got disconnected from the server due to an unexpected error.

Action: Check the Workload Replay Client's log files and the database server alert log to diagnose the problem.

ORA-15559: workload replay client cannot open workload capture file

Cause: The Workload Replay Client could not access one or more workload capture files from the replay directory.

Action: Restart the workload replay after copying all the workload capture files to the replay directory.

ORA-15560: workload replay client cannot access the work directory

Cause: The Workload Replay Client could not access the work directory to write log files for debug information.

Action: Restart the Workload Replay Client after specifying the correct work directory.

ORA-15561: workload replay client cannot connect to the remapped connection with conn_id : string

Cause: The specified connection is invalid or the specified host is inaccessible.

Action: Test the specified connection using other methods and redefine the connection remapping, if necessary. Consult the view DBA_WORKLOAD_CONNECTION_MAP to inspect connection remappings.

ORA-15562: workload replay client cannot read the DBA_WORKLOAD_CONNECTION_MAP view

Cause: The DBA_WORKLOAD_CONNECTION_MAP view did not exist or was not accessible.

Action: Re-create the workload capture and replay views. For additional information, see the documentation.

ORA-15563: workload replay client cannot spawn new threads

Cause: The Workload Replay Client does not have enough resource (CPU or memory) to spawn new threads.

Action: Restart the workload replay after allocating more resource (CPU and memory) to the Workload Replay Client or use more hosts as replay clients to drive the workload.

ORA-15564: contents of the replay directory provided to the workload replay client do not match with the replay directory provided to the database server

Cause: The processed workload capture files given to the workload replay client directory did not match the contents of the replay directory given as input to DBMS_WORKLOAD_REPLAY.INITIALIZE_REPLAY.

Action: Provide the same processed workload capture files to both the database server and all the workload replay clients and restart the replay. If the same workload capture files were processed more than once, provide a copy of the latest processed workload capture files to all the workload replay clients and the database server.

ORA-15566: workload replay client cannot replay user call in the current version

Cause: The workload replay client encountered a user call in the captured workload that was not supported for replay in the current version.

Action: Look in the DBA_WORKLOAD_REPLAY_DIVERGENCE view for details about the call that encountered this error. Refer to the documentation for more details on the types of workload that are not supported in the current version.

ORA-15590: encountered an incomplete workload capture file

Cause: The captured workload contained one or more incomplete recording files. This can happen when the original workload capture's FINISH_CAPTURE command timed out while waiting for all the active sessions to close their workload capture files.

Action: Incomplete capture files will not interfere with the processing and replaying of the captured workload. This is simply a warning message to point out that some database calls might not have been recorded due to FINISH_CAPTURE command timing out.

ORA-15601: Invalid value specified for parameter "string"

Cause: An invalid value was specified for the given parameter.

Action: Correct the value being specified for the parameter.

ORA-15602: Parameter "string" cannot be NULL.

Cause: An attempt was made to call a procedure without a required parameter.

Action: Specify a valid value for this parameter.

ORA-15603: Action cannot be performed when database is in read-only mode.

Cause: A procedure in DBMS_AUTO_TASK_ADMIN package was invoked when database was open in read-only mode.

Action: Retry when database is open in read/write mode.

ORA-15604: Initialization parameters prevent client from being enabled.

Cause: An attempt was made to enable a client that was disabled for automatic execution by an initialization parameter.

Action: Check the related client parameters and try again.

ORA-15605: "string" is not a Maintenance Window

Cause: Window name passed to DBMS_AUTO_TASK_ADMIN.ENABLE procedure must be a member of the MAINTENANCE_WINDOW_GROUP.

Action: Make the window a member of the MAINTENANCE_WINDOW_GROUP and retry the call.

ORA-16000: database open for read-only access

Cause: The database has been opened for read-only access. Attempts to modify the database using inappropriate DML or DDL statements generate this error.

Action: In order to modify the database, it must first be shut down and re-opened for read-write access.

ORA-16001: database already open for read-only access by another instance

Cause: The database has been opened for read-only access by another instance, and cannot be opened for read-write access by this instance.

Action: This instance must be opened for read-write access, or all other instances must first be shut down and re-opened for read-only access.

ORA-16002: database already open for read-write access by another instance

Cause: The database has been opened for read-write access by another instance, and cannot be opened for read-only access by this instance.

Action: This instance must be opened for read-only access, or all other instances must first be shut down and re-opened for read-write access.

ORA-16003: standby database is restricted to read-only access

Cause: To ensure its integrity, a standby database can only be opened for read-only access.

Action: Re-issue the ALTER DATABASE OPEN specifying READ ONLY.

ORA-16004: backup database requires recovery

Cause: The control file is for a backup database which requires recovery, and cannot be opened for read-only access by this instance.

Action: Perform the necessary recovery and re-open for read-only access.

ORA-16005: database requires recovery

Cause: The database requires recovery, and therefore cannot be opened for read-only access by this instance.

Action: Perform the necessary recovery and re-open for read-only access.

ORA-16006: audit_trail destination incompatible with database open mode

Cause: The audit_trail initialization parameter was set to "DB" (or TRUE), which is incompatible with a database opened for read-only access.

Action: When the database is opened for read-only access, the audit_trail initialization parameter can only be set to "OS" or "NONE" (FALSE).

ORA-16007: invalid backup control file checkpoint

Cause: The backup control file being opened for read-only access does not contain a valid control file checkpoint. Therefore the database cannot be opened for read-only access.

Action: First open the database for read-write access which will result in valid control file checkpoint. Then re-open the database for read-only access.

ORA-16008: indeterminate control file checkpoint

Cause: The control file for the database being opened for read-only access was created via CREATE CONTROLFILE. Therefore a control file checkpoint could not be calculated and the database cannot be opened for read-only access.

Action: First open the database for read-write access which will result in valid control file checkpoint. Then re-open the database for read-only access.

ORA-16009: remote archive log destination must be a STANDBY database

Cause: The database associated with the archive log destination service name is other than the required STANDBY type database. Remote archival of redo log files is not allowed to non-STANDBY database instances.

Action: Take the necessary steps to create the required compatible STANDBY database before retrying the ARCHIVE LOG processing.

ORA-16011: Archivelog Remote File Server process in Error state

Cause: The archivelog remote file server (RFS) process at the specified standby database site has experienced an unrecoverable error and is unable to receive further archive log data.

Action: Correct the problem at the standby database site.

ORA-16012: Archive log standby database identifier mismatch

Cause: The database identifiers of the Primary and Standby database do not match. Remote archival of redo log files is not allowed to incompatible STANDBY database instances.

Action: Take the necessary steps to create the required compatible STANDBY database before retrying the ARCHIVE LOG processing.

ORA-16013: log string sequence# string does not need archiving

Cause: An attempt was made to archive the named file manually, but the file did not require archiving. The file had previously been successfully archived.

Action: No action is required.

ORA-16014: log string sequence# string not archived, no available destinations

Cause: An attempt was made to archive the named log, but the archive was unsuccessful. The archive failed because there were no archive log destinations specified or all destinations experienced debilitating errors.

Action: Verify that archive log destinations are being specified and/or take the necessary step to correct any errors that may have occurred.

ORA-16015: log string sequence# string not archived, media recovery disabled

Cause: An attempt was made to archive the named log, but the archive was unsuccessful. A standby archive log destination was specified and the database was not media recovery enabled. This is not allowed.

Action: Disable the standby destination or enable media recovery and retry.

ORA-16016: archived log for thread string sequence# string unavailable

Cause: The managed standby database recovery operation has timed out waiting for the requested archived log file.

Action: Verify that the primary database is still archiving redo logs to the standby recovery database site and reissue the RECOVER STANDBY DATABASE WAIT command.

ORA-16017: cannot use LOG_ARCHIVE_DUPLEX_DEST without a primary archive destination

Cause: The parameter LOG_ARCHIVE_DUPLEX_DEST was set to a non-NULL value when the primary archive destination was set to NULL explicitly.

Action: Set the primary archive destination to a valid non-NULL value.

ORA-16018: cannot use string with LOG_ARCHIVE_DEST_n or DB_RECOVERY_FILE_DEST

Cause: One of the following events caused an incompatibility: 1) Parameter LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST was in use when a LOG_ARCHIVE_DEST_n (n = 1...10) parameter was encountered while fetching initialization parameters. 2) An ALTER SYSTEM ARCHIVE LOG START TO command was in effect when a LOG_ARCHIVE_DEST_n parameter was encountered while fetching initialization parameters. 3) A LOG_ARCHIVE_DEST_n parameter was in use when an ALTER SYSTEM command was used to define a value for either the LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST parameter. 4) Parameter DB_RECOVERY_FILE_DEST was in use when an attempt was made to use an ALTER SYSTEM or ALTER SESSION command to define a value for LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST.

Action: Eliminate any incompatible parameter definitions.

ORA-16019: cannot use string with LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST

Cause: One of the following events caused an incompatibility: 1) Parameter LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST was in use when the specified LOG_ARCHIVE_DEST_n (n = 1...10) or DB_RECOVERY_FILE_DEST parameter was encountered while fetching initialization parameters. 2) Parameter LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST was in use when an attempt was made to use an ALTER SYSTEM or ALTER SESSION command to define a value for the specified LOG_ARCHIVE_DEST_n or DB_RECOVERY_FILE_DEST parameter. 3) An ALTER SYSTEM ARCHIVE LOG START TO command was in effect when the specified LOG_ARCHIVE_DEST_n parameter was encountered while fetching initialization parameters. 4) An ALTER SYSTEM ARCHIVE LOG START TO command was in effect when an attempt was made to use an ALTER SYSTEM or ALTER SESSION command to define a value for the specified LOG_ARCHIVE_DEST_n parameter.

Action: Eliminate any incompatible parameter definitions.

ORA-16020: less destinations available than specified by LOG_ARCHIVE_MIN_SUCCEED_DEST

Cause: With automatic archiving enabled, the number of archive log destinations that could be used for the database was less than the LOG_ARCHIVE_MIN_SUCCEED_DEST parameter value.

Action: Either adjust the settings of the log archive destination parameters, or lower the value of LOG_ARCHIVE_MIN_SUCCEED_DEST.

ORA-16021: session string destination cannot be the same as session string destination

Cause: An attempt was made to change the first specified archive log parameter using ALTER SESSION to have a destination value that duplicates the session-level destination value of the second specified archive log parameter.

Action: Specify a different session destination value for one of the LOG_ARCHIVE_DEST_n parameters.

ORA-16022: LOG_ARCHIVE_DEST cannot be NULL because LOG_ARCHIVE_DUPLEX_DEST is non-NULL

Cause: An attempt was made to change parameter LOG_ARCHIVE_DEST to NULL when parameter LOG_ARCHIVE_DUPLEX_DEST is non-NULL.

Action: Either set parameter LOG_ARCHIVE_DEST to a non-NULL value, or set parameter LOG_ARCHIVE_DUPLEX_DEST to a NULL value.

ORA-16023: system string destination cannot be the same as session string destination

Cause: An attempt to change the first specified LOG_ARCHIVE_DEST_n (n = 1...10) parameter produced a destination that duplicates the session destination value of the second specified LOG_ARCHIVE_DEST_n parameter. This error can occur when setting a non-NULL value with the ALTER SYSTEM command. Or, this error can occur when setting a NULL value with ALTER SESSION command, because then the associated system destination value may appear as a duplicate.

Action: Specify a different destination value for the first specified LOG_ARCHIVE_DEST_n parameter.

ORA-16024: parameter string cannot be parsed

Cause: The value for the indicated LOG_ARCHIVE_DEST_n (n = 1...10) parameter could not be parsed. Common causes for this error are a misplaced equal sign, an unrecognized attribute, or an attribute that is missing a required value.

Action: Correct the value for the indicated LOG_ARCHIVE_DEST_n parameter.

ORA-16025: parameter string contains repeated or conflicting attributes

Cause: The value for the specified LOG_ARCHIVE_DEST_n (n = 1...10) parameter contained either repeated attributes or attributes that conflicted with each other.

Action: Correct the value for the indicated LOG_ARCHIVE_DEST_n parameter.

ORA-16026: parameter string contains an invalid attribute value

Cause: The value for the specified LOG_ARCHIVE_DEST_n (n = 1...10) parameter contained an attribute with an invalid value.

Action: Correct the value for the indicated LOG_ARCHIVE_DEST_n parameter.

ORA-16027: parameter string is missing a destination option

Cause: The value for the indicated LOG_ARCHIVE_DEST_n (n = 1...10) parameter failed to include a destination option. A destination option is specified using either the LOCATION or SERVICE attrbute.

Action: Correct the value for the indicated LOG_ARCHIVE_DEST_n parameter.

ORA-16028: new string causes less destinations than LOG_ARCHIVE_MIN_SUCCEED_DEST requires

Cause: With automatic archiving enabled, an attempt was made to change the indicated LOG_ARCHIVE_DEST_n or a LOG_ARCHIVE_DEST_STATE_n parameter (n = 1...10) to a value that reduces the number of archive log destinations to less than the specified LOG_ARCHIVE_MIN_SUCCEED_DEST value.

Action: Either select different options for the LOG_ARCHIVE_DEST_n or LOG_ARCHIVE_DEST_STATE_n parameters, or reduce the value for parameter LOG_ARCHIVE_MIN_SUCCEED_DEST.

ORA-16029: cannot change LOG_ARCHIVE_MIN_SUCCEED_DEST, no archive log destinations

Cause: An attempt was made to change the LOG_ARCHIVE_MIN_SUCCEED_DEST parameter when there are no archive log destinations.

Action: Define one or more log archive destinations using parameters LOG_ARCHIVE_DEST, LOG_ARCHIVE_DUPLEX_DEST, or LOG_ARCHIVE_DEST_n (n = 1...10). Then, change the value of parameter LOG_ARCHIVE_MIN_SUCCEED_DEST.

ORA-16030: session specific change requires a LOG_ARCHIVE_DEST_n destination

Cause: The following event caused an incompatibility: Parameter LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST was in use when an attempt was made to change the LOG_ARCHIVE_MIN_SUCCEED_DEST parameter with an ALTER SESSION command.

Action: Replace any LOG_ARCHIVE_DEST and LOG_ARCHIVE_DUPLEX_DEST parameters with LOG_ARCHIVE_DEST_n (n = 1...10) parameters.

ORA-16031: parameter string destination string exceeds string character limit

Cause: The value for the specified parameter contained a destination string that is too long.

Action: Replace the destination value for the specified parameter with a character string that has a length below the limit specified in the error message.

ORA-16032: parameter string destination string cannot be translated

Cause: The value for the specified parameter contained a destination string that could not be translated.

Action: Use a valid destination string in the specified parameter.

ORA-16033: parameter string destination cannot be the same as parameter string destination

Cause: An attempt was made to change the first specified archive log parameter to have a destination value that duplicates the system-level destination value of the second specified archive log parameter.

Action: Specify a different value for one of the archive log parameters.

ORA-16034: FROM parameter is incompatible with MANAGED recovery

Cause: Use of the FROM 'location' parameter is not allowed when MANAGED recovery has been specified.

Action: Correct the syntax and retry the command.

ORA-16035: missing required keyword string

Cause: The indicated keyword is required but was not specified.

Action: Correct the syntax and retry the command.

ORA-16036: invalid MANAGED recovery CANCEL option

Cause: A mode other than IMMEDIATE follows the CANCEL keyword in RECOVER MANAGED STANDBY DATABASE statement.

Action: Specify either nothing or IMMEDIATE following CANCEL.