25 Recovery Appliance Error Message Reference
This chapter provides details on the Zero Data Loss Recovery Appliance (Recovery Appliance) error messages, which occur between ranges ORA-45100
and ORA-45299
, between ranges ORA-64700
and ORA-64899
, and between ranges ORA-61100
and ORA-61699
.
-
ORA-45100: Database incarnation went from
%s
to%s
. Recovery Appliance repair is required. -
Cause: A '
startup resetlogs
' command was executed on the Recovery Appliance. This caused old metadata to be used to refer to the storage locations. Before the Recovery Appliance can be started, a repair operation must be run to synchronize its metadata with its storage. -
ORA-45102: unable to allocate
%s
bytes of storage -
Cause: The Recovery Appliance was unable to allocate additional disk space in the storage location of the database for the current allocation. This condition may be due to one of the following reasons:
-
Guaranteed copy has been specified for a database and there are too many backups waiting to be copied to tape.
-
Nothing can be purged within the storage location of the database.
-
There are no purgable backup pieces for the database and the sum of the sizes of the pieces being received by the database exceeds its
DISK_RESERVED_SPACE
. -
The metadata of the Recovery Appliance is being repaired.
-
-
ORA-45109: metadata for database
%s
; file%s
has inconsistencies -
Cause: Internal self checks found inconsistencies in the metadata used to manage the Recovery Appliance block pool.
-
ORA-45111: Task
%s
is being terminated after%s
restarts. -
Cause: A Recovery Appliance task generated too many errors. Following an error, a task is normally restarted. If it fails to restart after 10 tries, the Recovery Appliance marks the task as broken and no longer tries to restart it.
-
ORA-45113: Recovery Appliance internal error
%s
-
Cause: An internal error was encountered.
-
ORA-45114: file "
%s
" not referenced by metadata for storage location%s
-
Cause: A consistency check performed by the check files task of the Recovery Appliance identified that the file was not being referenced by the metadata of the Recovery Appliance. Without these references, the Recovery Appliance cannot manage the file.
-
ORA-45115: database with DB_KEY
%s
is too big to move. -
Cause: An attempt was made to move the specified database to a new storage location, but the database could not be shrunk to within its storage reservation and still preserve its retention window.
-
ORA-45116: anomaly detected while reading metadata for backup piece with BP_KEY
%s
-
Cause: A transient anomaly was found in the backup data.
- ORA-45117: There is not enough space for this task.
-
Cause: Space could not be allocated from the storage location to support this operation.
- ORA-45118: servlet timeout error
-
Cause: A restore task was waiting on a servlet process to pass data to a client. The time allotted for responding was exceeded and the restore task was aborted.
- ORA-45119: received a nonexistent operation for privilege change
-
Cause: An illegal option was specified.
- ORA-45120: operation failed due to insufficient space
-
Cause: The storage location was too small to support the new database.
- ORA-45121: received an incorrect value for a privilege change
-
Cause: An internal error was detected while granting or revoking privileges.
- ORA-45122: invalid size or number specified
-
Cause: An invalid size or number was specified.
-
ORA-45123: The name
%s
(%s
) already exists. -
Cause: The object name was not unique.
-
ORA-45124: Object
%s
(%s
) is referenced and cannot be deleted. -
Cause: The object was in use by a storage location or database.
-
ORA-45125: Object
%s
(%s
) did not exist. -
Cause: The object name did not exist.
-
ORA-45126: failed to delete database
%s
-
Cause: The database could not be deleted. An unexpected error has occurred.
-
ORA-45127: Required parameter
%s
must be specified. -
Cause: The parameter was not supplied to API routine.
-
ORA-45128: backup piece
%s
in database%s
is not referenced by the catalog -
Cause: A consistency check performed by the check files task of the Recovery Appliance identified that the specified backup piece was unreferenced by the RMAN catalog. Without this reference, the Recovery Appliance cannot reclaim space used by this piece.
-
ORA-45129: expected
%s
bytes used by database%s
in storage location%s
, but found%s
bytes used -
Cause: A consistency check performed by the check files task of the Recovery Appliance identified that the storage usage of the database in a storage location did not match the sum of the size of storage pieces assigned to the Recovery Appliance.
-
ORA-45130: Storage parameter overlaps with storage in
%s
. -
Cause: A parameter for a storage location was specified that overlapped storage previously assigned to another storage location.
- ORA-45131: illegal or unknown restore compression option specified
-
Cause: The specified compression option was not supported on either the Recovery Appliance database or the database providing the backup.
- ORA-45132: corrupt block detected in backup piece
-
Cause: A corrupt block was detected in a backup piece when populating the Recovery Appliance block pool.
-
ORA-45133: expected
%s
byte allocation by database%s
, but found%s
bytes allocated -
Cause: A consistency check performed by the check files task of the Recovery Appliance found that the storage allocations of the database did not match the sum of the size of allocations for that database in all storage locations.
- ORA-45135: request terminated by the Recovery Appliance
-
Cause: A request was holding resources needed by the Recovery Appliance and was terminated to free those resources. This can be the result of a lack of disk space or some other resource.
-
ORA-45136: invalid value for parameter
%s
-
Cause: The value supplied for the specified parameter was invalid.
- ORA-45137: unknown platform
-
Cause: The Recovery Appliance has not received any backups from System Backup to Tape (SBT) or through polling. This is necessary for the Recovery Appliance to learn about the protected platform of the database and for the current operation to succeed.
- ORA-45138: Backup not found.
-
Cause: The specified backup could not be found in the catalog.
- ORA-45139: A useful backup could not be found to correct this corruption.
-
Cause: A virtual backup piece key was provided, but there was no known backup on tape or disk to correct this backup.
- ORA-45140: cannot insert backup into catalog
-
Cause: The specified backup was either not an incremental or not in the proper SCN range to correct problems in the catalog.
-
ORA-45141: File "
%s
" was missing from storage location%s
. -
Cause: During recovery of the Recovery Appliance, the specified file was referenced by the metadata of the Recovery Appliance, but was not found in its storage location.
- ORA-45142: The Recovery Appliance prerequisite is already set up.
-
Cause: The
DBMS_RA_INSTALL
procedure was executed to set up prerequisite objects for creation of a catalog schema for the Recovery Appliance. This error is reported because there can be only one user schema that manages the Recovery Appliance for the database. - ORA-45143: The Recovery Appliance prerequisite setup administors user name is mismatched.
-
Cause: The
DBMS_RA_INSTALL
procedure was executed to uninstall the Recovery Appliance prerequisite object for the wrong user name. - ORA-45144: Undefined initial replication type for protection policy.
-
Cause: The initial_replication_type was undefined for the protection policy.
-
ORA-45145: Recovery Appliance user
%s
does not exist. -
Cause: The Recovery Appliance user did not exist.
-
ORA-45146: Storage location
%s
needs%s
additional bytes of storage. -
Cause: The metadata of the Recovery Appliance was being repaired following a database open with the '
resetlogs
' command and the storage allocated in the specified storage location was insufficient. This may be caused by either an 'update_storage_location
' call being lost due to the 'resetlogs' command or the storage location becoming very low on free storage when the resetlogs command was executed. -
ORA-45147: Database
%s
and database%s
are both moving. -
Cause: The metadata of the Recovery Appliance was being repaired following a database open with 'resetlogs' and two databases were found to be moving between storage locations. The Recovery Appliance will only function correctly when one database is being moved. This may be caused by an 'update_protection_policy' or 'update_db' call being lost due to the 'resetlogs' command.
-
ORA-45148: must fix
%s
errors before restarting the Recovery Appliance -
Cause: During a repair of the metadata of the Recovery Appliance, errors were found that precluded the restart of the Recovery Appliance.
-
ORA-45149: unknown task type:
%s
-
Cause: The Recovery Appliance tried to execute a task with an unknown task type.
-
ORA-45150: File
%s
references unknown DBID%s
. -
Cause: During a repair of the metadata of the Recovery Appliance, the specified file was found that referenced the specified database which was unknown to the Recovery Appliance. This may be caused by an '
add_db
' call being lost due to a 'resetlogs
' command. -
ORA-45151: bad locking protocol for lock
%s
-
Cause: An internal error caused locking to be used incorrectly.
-
ORA-45152: bad backup piece format for
%s
-
Cause: During a repair of the metadata of the Recovery Appliance, the specified file was found whose type could not be determined.
-
ORA-45153: unknown data file
%s
for DBID%s
-
Cause: During repair of the metadata of the Recovery Appliance, data for the specified database was found whose data file could not be found.
-
ORA-45154: bad Recovery Appliance format found in file
%s
-
Cause: During a repair of the metadata of the Recovery Appliance, a file was found in a storage location that was neither a chunk file nor a backup piece.
- ORA-45155: The Recovery Appliance has not been installed.
-
Cause: The Recovery Appliance was never installed on this database. The requested procedure is only supported on the Recovery Appliance.
-
ORA-45156: SBT job
%s
not found -
Cause: The specified SBT job was not found.
-
ORA-45157: Parameter value
%s
(%s
) is invalid. -
Cause: The specified value for the parameter was invalid.
-
ORA-45158: SBT library
%s
is not ready. -
Cause: The specified SBT library was found to not be ready.
-
ORA-45159: RECOVERY_WINDOW_GOAL is lost for database
%s
. -
Cause: A low space condition forced the deletion of backups needed to support the recovery window goal for the named database.
-
ORA-45160: Incremental forever strategy is lost for database
%s
. -
Cause: A low space condition has forced the deletion of backup data needed to generate the last remaining virtual
LEVEL 0
of one or more data files. The next client backup will be a fullLEVEL 0
backup, even ifLEVEL 1
was specified. - ORA-45161: The backup piece size cannot exceed database DISK_RESERVED_SPACE.
-
Cause: An individual backup piece exceeded the database protection policy
DISK_RESERVE_SPACE
value. A safeDISK_RESERVED_SPACE
value would exceed the size of the database. - ORA-45162: System global area memory is configured incorrectly.
-
Cause: Check initialization parameters
LARGE_POOL_SIZE
andSHARED_POOL_SIZE
. The Recovery Appliance will use all ofLARGE_POOL_SIZE
or 20% ofSHARED_POOL_SIZE
to restore virtual or tape backups. The actual space needed isNETWORK_CHUNKSIZE * 2 * (number of concurrent restore channels)
whereNETWORK_CHUNKSIZE
is set usingDBMS_RA.CONFIG
. Use DBMS_RA.CONFIG
to lowerNETWORK_CHUNKSIZE
or preferably, increase eitherLARGE_POOL_SIZE
orSHARED_POOL_SIZE
. -
ORA-45163: operation is only supported for user
%s
-
Cause: An attempt was made to start the Recovery Appliance by a user other than the Recovery Appliance administrator.
- ORA-45164: The Recovery Appliance is not running.
-
Cause: An attempt was made to use the Recovery Appliance, but the Recovery Appliance has been deactivated by the administrator.
-
ORA-45165: Recovery Appliance backup piece with BP_KEY
%s
is corrupt -
Cause: Corruption was found in the backup data.
-
ORA-45166: unable to access file
%s
-
Cause: An attempt was made to access the specified file which resulted in an error. An explanation of the error appears in the following messages.
-
ORA-45167: unable to validate backup piece with BP_KEY
%s
-
Cause: An attempt was made to validate the specified backup piece which resulted in an error. An explanation of the error appears in the following messages.
-
ORA-45168: unexpected executer exit while processing task ID
%s
of type%s
-
Cause: A task failed with an unexpected error code in the Recovery Appliance.
- ORA-45169: unexpected timer process exit
-
Cause: The timer process failed with an unexpected error code in the Recovery Appliance.
-
ORA-45170: Storage location
%s
is too full. -
Cause: Purging the specified storage location would result in the loss of the recovery window goal for one of its databases.
- ORA-45171: The chunk optimization task has not run recently for one or more databases.
-
Cause: The background chunk optimization task had not been performed recently for at least one database. This may happen if the Recovery Appliance is too overloaded with foreground activities to have time to do background tasks.
- ORA-45172: The validation task has not run recently for one or more databases.
-
Cause: The background validation task had not been performed recently for at least one database. This may happen if the Recovery Appliance is too overloaded with foreground activities to have time to do background tasks.
- ORA-45173: The checkfiles task has not run recently for one or more storage locations.
-
Cause: The background checkfiles task had not been performed recently for one or more storage locations. This may happen if the Recovery Appliance is too overloaded with foreground activities to have time to do background tasks.
-
ORA-45174: unable to use replication server
%s
-
Cause: While using the Recovery Appliance, either a backup failed to be transmitted to the target replicated Recovery Appliance or a restore request failed to complete on the replicated Recovery Appliance.
-
ORA-45175: unable to use SBT library
%s
-
Cause: While using the Recovery Appliance, a request failed to complete while using the specified System Backup to Tape library.
-
ORA-45176: Replication server
%s
is not in the paused state. -
Cause: An attempt was made to update information for a replication server that was not in a paused state.
-
ORA-45177: unable to find file
%s
previously found while polling -
Cause: A backup piece file previously found in a polling location was later not accessible to the Recovery Appliance.
- ORA-45178: The allocation unit size cannot be changed.
-
Cause: An attempt was made to move one or more databases into a storage location with a different allocation unit size. This value comes from the ASM disk group allocation unit size specified when creating the disk groups referenced by the storage location.
-
ORA-45179: The reconcile task has not run recently for database
%s
. -
Cause: The background reconcile task had not been performed recently for the specified database. This may happen if the Recovery Appliance is too overloaded with foreground activities to have time to do background tasks.
- ORA-45180: The crosscheck task has not run recently for database one or more databases.
-
Cause: The background reconcile task had not been performed recently for at least one database. This may happen if the Recovery Appliance is too overloaded with foreground activities to have time to do background tasks.
- ORA-45182: database access cannot be granted or revoked using catalog owner or sys
-
Cause: The catalog owner or
SYS
was specified as the user in theDBMS_
RA.GRANT_DB_ACCESS
andDBMS_RA.REVOKE_DB_ACCESS
procedures. This is not allowed. -
ORA-45183: request is blocked by session
%s
on instance%s
-
Cause: An API request was made to the Recovery Appliance while another API was in progress. Only one API may be performed at a time.
-
ORA-45184: ORA-
%s
occurred during wallet operation; WRL%s
-
Cause: An operation on the wallet failed due to the indicated error.
-
ORA-45185: alias
%s
not found in%s
wallet -
Cause: The specified WALLET alias did not appear in the wallet.
-
ORA-45187: storage location
%s
is unusable; container repair key is%s
-
Cause: During a repair of the Recovery Appliance, fatal errors were detected while rebuilding the specified storage location.
-
ORA-45188: storage location
%s
requires repair; container repair key is%s
-
Cause: During a repair of the Recovery Appliance, consistency errors were detected while rebuilding the specified storage location.
-
ORA-45189: repair failed because storage location was renamed from
%s
to%s
-
Cause: During a repair of the Recovery Appliance, a storage location was found whose name was different from the name originally used to define the storage location.
-
ORA-45190: anomaly detected while reading metadata for database with DB_KEY
%s
-
Cause: A transient anomaly was found in the backup data.
- ORA-45191: no suitable SBT library was found for the Recovery Appliance backups
-
Cause: Recovery Appliance could not find a suitable System Backup to Tape (SBT) library for performing the Recovery Appliance metadata backups.
- ORA-45192: reservation already exists for the Recovery Appliance backup
-
Cause: An attempt was made to create a new reservation to perform a Recovery Appliance metadata backup when an unexpired reservation exists.
- ORA-45193: multiple SBT libraries are present
-
Cause: More than one System Backup to Tape (SBT) library was found that can be used to back up the Recovery Appliance metadata.
- ORA-45194: Recovery Appliance metadata backup to SBT library failed
-
Cause: An error occurred while backing up the Recovery Appliance metadata to the System Backup to Tape (SBT) library. The error could be caused by the SBT library configuration or an internal Recovery Appliance error.
- ORA-45195: reservation wait time exceeded
-
Cause: A timeout occurred while waiting for the system backup to tape (SBT) library reservation.
- ORA-45196: failed to unreserve existing reservation
-
Cause: The existing System Backup to Tape (SBT) library reservation could not be unreserved.
-
ORA-45197: SBT library
%s
could not be found for reservation -
Cause: The Recovery Appliance could not find a System Backup to Tape (SBT) library for the given name.
- ORA-45198: machine is not a physical Recovery Appliance
-
Cause: Recovery Appliance services were attempted to start on a machine that was not a physical Recovery Appliance.
-
ORA-45199: Error
%s
encountered when executing%s
. -
Cause: An error was encountered when executing PL/SQL code. This message should be accompanied by other error message(s) indicating the cause of the error.
-
ORA-45200: HTTP status code:
%s
-
Cause: The indicated HTTP status code was received while processing a servlet request,
-
ORA-45201: additional Information:
%s
-
Cause: The indicated additional error was received while processing a servlet request.
- ORA-45202: operation failed, retry possible
-
Cause: A backup, restore operation failed while processing a servlet request. The operation may be retried.
-
ORA-45203: failed to
%s
backup piece file "%s
" -
Cause: An OS operation on the specified backup piece returned an error.
-
ORA-45204: failure while deleting from sbt library
%s
-
Cause: An attempt to delete a file from the given SBT library failed.
- ORA-45205: Not enough reserved space for this task.
-
Cause: The task did not have enough reserved space to proceed. Not enough storage space was allocated for backup related operations.
- ORA-45210: resource busy, retry possible
-
Cause: A backup or restore operation failed while processing a servlet request. The operation may be retried.
-
ORA-45211: error encountered while sending data; error code
%s
-
Cause: An error was encountered while sending data to the client.
-
ORA-45212: error encountered while receiving data; error code
%s
-
Cause: An error was encountered while receiving data from client.
-
ORA-45213: user or role '
%s
' does not exist -
Cause: There was no user or role with the name specified.
-
ORA-45214: cannot convert '
%s
' to number -
Cause: An arithmetic, numeric, string, conversion, or constraint error occurred. For example, a NULL value was assigned to a variable that was declared as NOT NULL or an integer larger than 99 was assigned to a variable declared as
NUMBER(2)
. - ORA-45215: cannot delete a replication server that is in use
-
Cause: An attempt was made to delete a replication server that was actively restoring a backup.
-
ORA-45216: backup metadata of
%s
(%s
) for database%s
was not found -
Cause: The reported backup metadata was not found.
-
ORA-45217: SBT task
%s
is not found -
Cause: The specified SBT task was not found.
-
ORA-45264: error encountered during Recovery Appliance test recovery
%s
-
Cause: As part of Recovery Appliance protection, test recovery was performed by the Recovery Appliance metadata protection script. The test recovery uses the image copies, without additional disk space requirement to restore datafiles, to test the database.
-
ORA-45265: error encountered during Recovery Appliance backup health check
%s
-
Cause: As part of Recovery Appliance protection, backup health check was performed by the Recovery Appliance metadata protection script. The backup health check uses the database 'validate' and 'preview' command to test the backups.
-
ORA-45266: error encountered during Recovery Appliance database health check
%s
-
Cause: As part of Recovery Appliance protection, database health check was performed by the Recovery Appliance metadata protection script. The database health check uses the 'backup validate' command to perform database health check.
-
ORA-45267: Inconsistency found while validating
db_key %s df_key %s
-
Cause: Internal self checks found inconsistencies in the metadata used to manage the Recovery Appliance block pool.
-
ORA-45268: Inconsistency found while purging
db_key %s, df_key %s, vb_key %s
-
Cause: Internal self checks found inconsistencies in the metadata used to manage the Recovery Appliance block pool while purging. No blocks have been deleted and backups are valid.
-
ORA-45275: container: '
%s
' -
Cause: This message reports the name of the Recovery Appliance container involved in other messages.
- ORA-45276: could not create container
-
Cause: A container creation failed. There will be other messages printed in the error stack that show more details about the problem.
-
ORA-45277: New AU size
%s
differs from existing AU size%s
in group%s
. -
Cause: An attempt was made to create a new container that has a different AU size than the other containers that already exist in this container group.
-
ORA-45278: Container group
%s
is not empty. -
Cause: An attempt was made to drop the specified container group but it is not empty.
-
ORA-45279: Container group
%s
does not exist. -
Cause: The specified container group does not exist.
-
ORA-45280: Container group
%s
already exists. -
Cause: The specified container group already exists.
-
ORA-45281: Size of
%s
bytes exceeds maximum container size of%s
bytes. -
Cause: You tried to create a container greater than the maximum size.
- ORA-45282: error identifying container
-
Cause: An error occurred while identifying a container.
- ORA-45283: error writing to container
-
Cause: An I/O error occurred while writing to a container.
- ORA-45284: error reading from container
-
Cause: An I/O error occurred while reading from a container.
-
ORA-45285: Cannot create more than
%s
container groups. -
Cause: An attempt to add a new container group would cause the number of container groups to exceed the system maximum.
-
ORA-45286: Cannot create more than
%s
containers. -
Cause: An attempt to add a new container would cause the number of containers to exceed the system maximum.
-
ORA-45287: File name
%s
is not valid for creation. -
Cause: An attempt was made to create a contained file name in an invalid format.
-
ORA-45289: Cannot reserve
%s
bytes in container group%s
. -
Cause: The specified container group was out of space.
-
ORA-45290: Cannot shrink file
%s
because file is busy. -
Cause: The specified file cannot be reduced in size because some other process was holding the file open.
-
ORA-45291: Container
%s
is not globally identified. -
Cause: An attempt to create or identify a file failed because a required container is not globally identified in this instance. The logs from the GEN0 process will usually indicate the reason why the file could not be identified.
- ORA-45292: error during container group rebuild
-
Cause: An unrecoverable error occurred during container group rebuild.
- ORA-45293: Cannot shrink file
-
Cause: An attempt to shrink file was requested but this has been prevented because the file has been marked as not shrinkable.
Next grouping of error messages.
- ORA-57800: Blocks metadata storage internal I/O error %s.
-
Cause: The Recovery Appliance encountered an internal error while performing a read or write operation on backup blocks metadata stored in the delta store.
- ORA-57801: Excess fragmentation detected while reading blocks metadata for datafile %s.
-
Cause: Backup blocks metadata stored in the delta store was found to be excessively fragmented for the datafile.
- ORA-57802:
-
Cause: