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.

Action: Execute DBMS_RA.STARTUP_RECOVERY_APPLIANCE. If any incidents are logged during the subsequent repair, they will need to be corrected. Once they have been corrected, repeat the execution of DBMS_RA.STARTUP_RECOVERY_APPLIANCE.

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.

Action: Add additional storage to the storage location of the database. Increase the DISK_RESERVED_SPACE for the database if it has been set too low.

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.

Action: Contact Oracle Support Services and provide trace and alert files.

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.

Action: Correct the error that terminated the task and request the task to be rerun.

ORA-45113: Recovery Appliance internal error %s

Cause: An internal error was encountered.

Action: Contact Oracle Support Services and provide trace and alert files.

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.

Action: If the file was inadvertently put in the storage location, it should be moved elsewhere. If the file has been separated from its metadata, contact Oracle Support Services and provide trace and alert files.

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.

Action: Increase the storage reservation for the database or shrink 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.

Action: If the anomaly persists, find a copy of the backup piece, if available, and reinsert it into the storage location. If no copy is available, generate a new level 0 backup for all data files in the backup piece.

ORA-45117: There is not enough space for this task.

Cause: Space could not be allocated from the storage location to support this operation.

Action: Review space usage by the different databases and take action:

• Review the RA_INCIDENT_LOG and see what space related incidents might have been recorded. Look for failures that might have impacted normal operations.
• Look for databases without an entry in RA_DISK_RESTORE_RANGE. Such databases are unable to release space properly. These databases are not fully recoverable.
• Consider moving databases to another RA.
• Consider adding more space to your storage location.

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.

Action: This can be a common occurrence if the client cancels the restore request. Reissue the request.

ORA-45119: received a nonexistent operation for privilege change

Cause: An illegal option was specified.

Action: BACKUP, RECONCILE, READ, WRITE, and NULL are only supported values.

ORA-45120: operation failed due to insufficient space

Cause: The storage location was too small to support the new database.

Action: Increase the size of your storage location or reduce DISK_RESERVED_SPACE in the protection policy.

ORA-45121: received an incorrect value for a privilege change

Cause: An internal error was detected while granting or revoking privileges.

Action: Contact Oracle Support Services and provide trace and alert files.

ORA-45122: invalid size or number specified

Cause: An invalid size or number was specified.

Action: Use a non-NULL or number greater than 0.

ORA-45123: The name %s (%s) already exists.

Cause: The object name was not unique.

Action: Specify a unique name for this object.

ORA-45124: Object %s (%s) is referenced and cannot be deleted.

Cause: The object was in use by a storage location or database.

Action: Delete all objects that reference this item.

ORA-45125: Object %s (%s) did not exist.

Cause: The object name did not exist.

Action: Specify an existing object.

ORA-45126: failed to delete database %s

Cause: The database could not be deleted. An unexpected error has occurred.

Action: Examine the associated messages to determine the cause of the exception.

ORA-45127: Required parameter %s must be specified.

Cause: The parameter was not supplied to API routine.

Action: Rerun the command specifying the missing parameter.

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.

Action: Contact Oracle Support Services.

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.

Action: Contact Oracle Support Services.

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.

Action: Reissue the command specifying a different location for the storage.

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.

Action: Query V$RMAN_COMPRESSION_ALGORITHM view to ensure the algorithm name matches one of the algorithm names in that table and that the option has IS_VALID = 'YES' and that the INITIAL_RELEASE column is less than both the Recovery Appliance and the database providing the backup. Reissue the command specifying a valid compression algorithm name.

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.

Action: Perform block media recovery on the corrupt blocks of the database and do a cumulative level 1 backup.

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.

Action: Contact Oracle Support Services.

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.

Action: Check available disk space, as well as for errors on the Recovery Appliance database.

ORA-45136: invalid value for parameter %s

Cause: The value supplied for the specified parameter was invalid.

Action: Check the Recovery Appliance documentation and rerun the command with a correct value.

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.

Action: Backup a small archived log or other backup using SBT or by sending it to the polling location. Then retry this operation.

ORA-45138: Backup not found.

Cause: The specified backup could not be found in the catalog.

Action: Please check and specify the correct backup piece key or backup set key.

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.

Action: If the broken backup is the oldest virtual backup for the data file, sometimes an even older backup will have the data needed to correct the catalog. Find and specify that older backup directly.

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.

Action: Make sure you have provided the correct key value and find a proper incremental backup piece.

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.

Action: The file should be recovered from a replicated Recovery Appliance if it exists. If the file has been separated from its metadata, then contact Oracle Support Services and provide trace and alert files.

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.

Action: To re-create the Recovery Appliance schema in another user schema, uninstall the earlier Recovery Appliance schema setup.

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.

Action: Correct the user name parameter for DBMS_RA_INSTALL and reexecute the procedure.

ORA-45144: Undefined initial replication type for protection policy.

Cause: The initial_replication_type was undefined for the protection policy.

Action: Update the protection policy initial_replication_type with one of LAST FULL, ALL, or NONE.

ORA-45145: Recovery Appliance user %s does not exist.

Cause: The Recovery Appliance user did not exist.

Action: Specify an existing Recovery Appliance user.

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.

Action: Update the storage location with the specified values and try the repair again by executing DBMS_RA.STARTUP_RECOVERY_APPLIANCE.

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.

Action: Determine the storage locations used by each database and repeat any database movements that may have been lost.

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.

Action: Fix the identified errors and execute DBMS_RA.STARTUP_RECOVERY_APPLIANCE to retry the repair.

ORA-45149: unknown task type: %s

Cause: The Recovery Appliance tried to execute a task with an unknown task type.

Action: Contact Oracle Support Services.

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.

Action: Repeat the lost 'add_db' call.

ORA-45151: bad locking protocol for lock %s

Cause: An internal error caused locking to be used incorrectly.

Action: Contact Oracle Support Services.

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.

Action: Remove the corrupted file and reexecute DBMS_RA.STARTUP_RECOVERY_APPLIANCE.

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.

Action: Using RMAN on the specified database, use the 'resync' command to refresh the metadata on the Recovery Appliance and retry the restart of the Recovery Appliance.

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.

Action: Remove the offending file from the storage location of the Recovery Appliance and retry the restart of the Recovery Appliance.

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.

Action: Do not attempt the procedure except on the Recovery Appliance.

ORA-45156: SBT job %s not found

Cause: The specified SBT job was not found.

Action: Check if the SBT job has been deleted by user. If so, then drop the scheduler job.

ORA-45157: Parameter value %s (%s) is invalid.

Cause: The specified value for the parameter was invalid.

Action: Specify a valid value.

ORA-45158: SBT library %s is not ready.

Cause: The specified SBT library was found to not be ready.

Action: Check if the library has been paused by user. If so, then resume the SBT library.

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.

Action: This is a warning and no action is needed. However, you may use DBMS_RA.UPDATE_PROTECTION_POLICY to increase the DISK_RESERVED_SPACE value of the database to ensure additional backups are saved. Select SPACE_USAGE from RA_DATABASE to see how much space is currently in use. You should also check for KEEP backups consuming space on disk and decide if they should be moved to tape or other disk storage. See DBMS_RA.MOVE_BACKUP_PIECE for more details.

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 full LEVEL 0 backup, even if LEVEL 1 was specified.

Action: This is a warning and no action is needed. However, you may use DBMS_RA.UPDATE_DB to increase the RESERVED_SPACE value of the database to ensure additional backups are saved. Select SPACE_USAGE from RA_DATABASE to see how much space is currently in use. You should also check for KEEP backups consuming space on disk and decide if they should be moved to tape or other disk storage. See DBMS_RA.MOVE_BACKUP_PIECE for more details.

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 safe DISK_RESERVED_SPACE value would exceed the size of the database.

Action: Use DBMS_RA.UPDATE_DB to increase the DISK_RESERVED_SPACE value of the database.

ORA-45162: System global area memory is configured incorrectly.

Cause: Check initialization parameters LARGE_POOL_SIZE and SHARED_POOL_SIZE. The Recovery Appliance will use all of LARGE_POOL_SIZE or 20% of SHARED_POOL_SIZE to restore virtual or tape backups. The actual space needed is NETWORK_CHUNKSIZE * 2 * (number of concurrent restore channels) where NETWORK_CHUNKSIZE is set using DBMS_RA.CONFIG. Use DBMS_RA.CONFIG to lower NETWORK_CHUNKSIZE or preferably, increase either LARGE_POOL_SIZE or SHARED_POOL_SIZE.

Action: Check initialization parameters LARGE_POOL_SIZE and SHARED_POOL_SIZE and set it correctly.

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.

Action: Only start the Recovery Appliance as the user specified at installation time.

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.

Action: Have the Recovery Appliance administrator execute DBMS_RA.STARTUP_RECOVERY_APPLIANCE and retry the operation.

ORA-45165: Recovery Appliance backup piece with BP_KEY %s is corrupt

Cause: Corruption was found in the backup data.

Action: Ensure that you have a functioning backup of the affected data file. Then delete the corrupt backup piece to clear the condition.

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.

Action: Verify the correctness of the file. If it is corrupt, either delete it or replace it.

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.

Action: Verify the correctness of the backup piece. If it is corrupt, either delete it or replace it.

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.

Action: Contact Oracle Support Services.

ORA-45169: unexpected timer process exit

Cause: The timer process failed with an unexpected error code in the Recovery Appliance.

Action: Contact Oracle Support Services.

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.

Action: Add more storage to the storage location or remove some databases from the storage location or reduce the recovery window goal for some of the databases in the storage location.

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.

Action: Remove some load from the Recovery Appliance by reducing the frequency of backups by protected databases or by offloading some of the databases from the Recovery Appliance.

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.

Action: Remove some load from the Recovery Appliance by reducing the frequency of backups by protected databases or by offloading some of the databases from the Recovery Appliance.

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.

Action: Remove some load from the Recovery Appliance by reducing the frequency of backups by protected databases or by offloading some of the databases from the Recovery Appliance.

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.

Action: Check the following error messages to diagnose the actual error.

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.

Action: Check the following error messages to diagnose the actual error.

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.

Action: Pause the replication server on this Recovery Appliance.

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.

Action: If the file was unavailable due to network errors, the file will be found again once the network is available. If the backup piece was deleted, create a new backup.

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.

Action: Use a storage location with the same minimum allocation size as the source. If necessary create new disk groups with a matching size before creating a new 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.

Action: Remove some load from the Recovery Appliance by reducing the frequency of backups by protected databases or by offloading some of the databases from the Recovery Appliance.

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.

Action: Remove some load from the Recovery Appliance by reducing the frequency of backups by protected databases or by offloading some of the databases from the Recovery Appliance.

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 the DBMS_RA.GRANT_DB_ACCESS and DBMS_RA.REVOKE_DB_ACCESS procedures. This is not allowed.

Action: A different user should be created and granted the necessary access.

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.

Action: Wait for the other API to complete or kill the identified session before repeating the failed API request.

ORA-45184: ORA-%s occurred during wallet operation; WRL %s

Cause: An operation on the wallet failed due to the indicated error.

Action: Refer to the indicated Oracle message for more information.

ORA-45185: alias %s not found in %s wallet

Cause: The specified WALLET alias did not appear in the wallet.

Action: Check the WALLET alias or create an alias in the wallet for the specified attribute and retry the command.

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.

Action: Inspect the alert log for the instance upon which the repair command was issued for the errors detected. If you detect that the errors are caused by missing disk groups, add those disk groups and execute the STARTUP_RECOVERY_APPLIANCE API. If you decide that the missing data cannot be restored, execute the REPAIR_STORAGE_LOCATION API with the REPLACE option prior to executing the STARTUP_RECOVERY_APPLIANCE API.

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.

Action: Inspect the alert log for the instance upon which the repair command was issued for the errors detected. If you detect that the errors are caused by missing disks or disk groups, add those disks or disk groups and execute the STARTUP_RECOVERY_APPLIANCE API. If you decide that the missing data cannot be restored, execute the REPAIR_STORAGE_LOCATION API with the REPLACE option prior to executing the STARTUP_RECOVERY_APPLIANCE API.

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.

Action: Delete the bad storage location and re-create it with the proper name.

ORA-45190: anomaly detected while reading metadata for database with DB_KEY %s

Cause: A transient anomaly was found in the backup data.

Action: If the anomaly persists, generate a new level 0 backup for all data files in the database.

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.

Action: Create an SBT library that can be used for the Recovery Appliance backup.

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.

Action: Remove the existing reservation and then create a new reservation.

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.

Action: Specify a name while reserving the SBT library.

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.

Action: Check the SBT library configuration or RA_INCIDENT_LOG view.

ORA-45195: reservation wait time exceeded

Cause: A timeout occurred while waiting for the system backup to tape (SBT) library reservation.

Action: Increase the wait time for the reservation by modifying the '_drive_wait_minutes' configuration parameter and retry the operation.

ORA-45196: failed to unreserve existing reservation

Cause: The existing System Backup to Tape (SBT) library reservation could not be unreserved.

Action: Check the 'ERROR_LOG' table and trace files for information about the cause of this error.

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.

Action: Check the SBT library name and retry the operation.

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.

Action: The Recovery Appliance services cannot be started on this system.

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.

Action: Check the accompanying errors.

ORA-45200: HTTP status code: %s

Cause: The indicated HTTP status code was received while processing a servlet request,

Action: None

ORA-45201: additional Information: %s

Cause: The indicated additional error was received while processing a servlet request.

Action: None

ORA-45202: operation failed, retry possible

Cause: A backup, restore operation failed while processing a servlet request. The operation may be retried.

Action: This message is used by the SBT client to decide whether to retry the operation.

ORA-45203: failed to %s backup piece file "%s"

Cause: An OS operation on the specified backup piece returned an error.

Action: Check additional messages.

ORA-45204: failure while deleting from sbt library %s

Cause: An attempt to delete a file from the given SBT library failed.

Action: Check additional messages for the actual cause.

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.

Action: Review incidents described in the RA_INCIDENT_LOG for this database. Then use dbms_ra.update_db to adjust disk_reserved_space accordingly.

ORA-45210: resource busy, retry possible

Cause: A backup or restore operation failed while processing a servlet request. The operation may be retried.

Action: This message is used by the SBT client to decide whether to retry the operation.

ORA-45211: error encountered while sending data; error code %s

Cause: An error was encountered while sending data to the client.

Action: Check additional messages.

ORA-45212: error encountered while receiving data; error code %s

Cause: An error was encountered while receiving data from client.

Action: Check additional messages.

ORA-45213: user or role '%s' does not exist

Cause: There was no user or role with the name specified.

Action: Provide a valid user name or role.

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

Action: Change the data, how it is manipulated, or how it is declared so that values do not violate defined constraints.

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.

Action: Cancel the restore or wait for the restore to complete before deleting the replication server.

ORA-45216: backup metadata of %s (%s) for database %s was not found

Cause: The reported backup metadata was not found.

Action: This is an informational message. Ensure that you retain the backups until SBT tasks are executed.

ORA-45217: SBT task %s is not found

Cause: The specified SBT task was not found.

Action: Provide a valid SBT task identifier and retry the command.

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.

Action: Additional information regarding this failure is recorded in the RA_INCIDENT_LOG and is also displayed in the Oracle Enterprise Manager console.

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.

Action: Additional information regarding this failure is recorded in the RA_INCIDENT_LOG and is also displayed in the Oracle Enterprise Manager console.

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.

Action: Additional information regarding this failure is recorded in the RA_INCIDENT_LOG and is also displayed in the Oracle Enterprise Manager console.

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.

Action: Contact Oracle Support Services and provide trace and alert files.

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.

Action: Contact Oracle Support Services and provide trace and alert files.

ORA-45275: container: '%s'

Cause: This message reports the name of the Recovery Appliance container involved in other messages.

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

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.

Action: Investigate the entire error stack. If the problem is correctable, do so and retry creating this container.

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.

Action: Specify a container with the same AU size as the other containers in the 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.

Action: Either remove the remaining objects from the group or use the FORCE option. Note that the FORCE option will irretrievably delete all files in the container group.

ORA-45279: Container group %s does not exist.

Cause: The specified container group does not exist.

Action: Specify a container group that exists.

ORA-45280: Container group %s already exists.

Cause: The specified container group already exists.

Action: Specify a container group that does not exist.

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.

Action: Specify a smaller size.

ORA-45282: error identifying container

Cause: An error occurred while identifying a container.

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

ORA-45283: error writing to container

Cause: An I/O error occurred while writing to a container.

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

ORA-45284: error reading from container

Cause: An I/O error occurred while reading from a container.

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

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.

Action: Increase the container group limit.

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.

Action: Increase the container limit.

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.

Action: Correct the name and retry the operation.

ORA-45289: Cannot reserve %s bytes in container group %s.

Cause: The specified container group was out of space.

Action: Add another container to the container group.

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.

Action: Wait until the other process releases the file before attempting to reduce its size.

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.

Action: Examine the logs from the GEN0 process and correct the problem that is making some containers inaccessible.

ORA-45292: error during container group rebuild

Cause: An unrecoverable error occurred during container group rebuild.

Action: Review other messages on the error stack for additional details.

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.

Action: Nothing. File shrink is aborted.

ORA-64700: Recovery Appliance is shutting down

Cause: The Recovery Appliance was in the process of shutting down. This message is recorded in the incident log for the Recovery Appliance. When the shutdown completes, the incident is marked as FIXED.

Action: Wait for the Recovery Appliance to complete its shutdown.

ORA-64701: Storage location %s can no longer honor its reservations.

Cause: The specified storage location did not contain enough space to fulfill the reservations of all of the databases assigned to it. This error will be seen if a storage location lost part of its disk space and was in the process of being repaired.

Action: Either shrink the reservations for the databases contained within the storage location or add additional disk space to the storage location.

ORA-64702: Error repairing container files for storage location %s: %s

Cause: An error was returned while trying to rebuild or repair the container files used to store data from protected databases.

Action: The subsequent error will identify the error that needs to be addressed before the Recovery Appliance can be repaired.

ORA-64703: resource error detected

Cause: A task needed to be interrupted because it detected a resource limitation such as insufficient temporary table space or a snapshot being too old. It will be retried once the contention for the resource decreases. The secondary messages will identify the resource that has been exhausted.

Action: If this error occurs rarely, no user action is required. If the condition becomes persistent, the Recovery Appliance administrator should increase the resource that is exhausted.

ORA-64705: No destination in "%s" at column %s

Cause: The storage destination contained a syntax error.

Action: Correct the syntax error and retry the operation.

ORA-64708: more than one polling_location in "%s" at column %s

Cause: More than one polling_location was specified. Only one polling_location is allowed.

Action: Specify only one polling destination directory and retry the operation.

ORA-64709: ASM polling_location is not supported in "%s" at column %s

Cause: The polling_location specified an ASM-based location. Only non-ASM-based polling_locations are supported.

Action: Specify one non-ASM polling destination and retry the operation.

ORA-64711: Storage destination do not reference an ASM diskgroup.

Cause: The storage destination referenced a non-ASM storage location. Only ASM-based storage destinations are allowed. The operation has been rolled back.

Action: Correct the syntax error and retry the operation.

ORA-64713: Requested size %s for %s was too small; already using %s.

Cause: The size requested for the storage destination was smaller than its current size.

Action: Increase the requested size and retry the operation.

ORA-64714: Requested size %s for %s was larger than total available space %s.

Cause: The size requested for the storage destination was larger than its current used space plus its current free space.

Action: Decrease the requested size and retry the operation.

ORA-64715: Instance %s is not available to Recovery Appliance.

Cause: The Recovery Appliance is not utilizing the specified instance due to its absence from the Oracle RAC.

Action: Restart the specified instance or repair any connectivity issues with the specified instance.

ORA-64716: Storage location %s allocation size %s does not equal diskgroup %s allocation size %s.

Cause: The minimum allocation size of the specified storage location was not the same as the specified diskgroup allocation unit size.

Action: Specify a different diskgroup or a different storage location and retry the operation.

ORA-64717: Network chunk size %s is not a multiple of diskgroup %s allocation size %s.

Cause: The configured network chunk size was not a multiple of the specified diskgroup allocation unit size.

Action: Specify a different diskgroup or reconfigure the network chunk size and retry the operation.

ORA-64718: Diskgroup %s allocation size %s is not a power of two.

Cause: The diskgroup allocation unit size was not a power of two.

Action: Specify a different diskgroup and retry the operation.

ORA-64719: Diskgroup %s allocation size %s is less than two megabytes %s.

Cause: The diskgroup allocation unit size was less than two megabytes.

Action: Specify a different diskgroup and retry the operation.

ORA-64720: No containers were created for storage location %s.

Cause: No storage was allocated and initialized for the specified storage location.

Action: Specify a different diskgroup for the storage location, increase the size of the diskgroup, or reduce the size of the storage location and retry the operation.

ORA-64721: Reserved space %s is less than the minimum reservation %s.

Cause: No storage was allocated and initialized for the specified storage location.

Action: Specify a different diskgroup for the storage location, increase the size of the diskgroup, or reduce the size of the storage location and retry the operation.

ORA-64722: Number of drives must be greater than zero.

Cause: The specified number of tape drives was NULL or was less than or equal to zero.

Action: Specify a number of tape drives greater than 0 and retry the operation.

ORA-64723: Number of drives reserved for restore operations must be greater than or equal to zero.

Cause: The number of tape drives reserved for restore operations was NULL or was less than zero.

Action: Specify a number of tape drives reserved for restore operations greater than or equal to zero and retry the operation.

ORA-64724: Number of restore drives %s too large; must be less than %s.

Cause: The number of tape drives reserved for restore operations was at least as large as the total number of drives available. The number of tape drives reserved for restore operations must be at least one less than the total number of drives available.

Action: Specify a number of tape drives reserved for restore operations less than the total number of drives available and retry the operation.

ORA-64725: Number of streams must be greater than zero.

Cause: The number of streams was less than or equal to zero.

Action: Specify a number of streams greater than zero and retry the operation.

ORA-64726: Number of streams %s too large; must be no larger than %s.

Cause: The number of streams was larger than the total number of drives available. The number of streams must be no larger than the total number of drives available.

Action: Reduce the number of available streams and retry the operation.

ORA-64727: Number of copies %s not in the range 1 through 4.

Cause: The number of copies was either NULL or not in the range 1 through 4 inclusive.

Action: Specify a number of copies in the range 1 through 4 and retry the operation.

ORA-64728: Replication server name length %s is too long.

Cause: The replication server name was longer than 128 characters.

Action: Specify a replication server name shorter than 128 characters and retry the operation.

ORA-64729: Replication server proxy port %s must be greater than zero.

Cause: The replication server proxy port number was less than or equal to zero.

Action: Specify a replication server proxy port number greater than zero and retry the operation.

ORA-64730: Replication server proxy URL provided but proxy port is NULL.

Cause: A replication server proxy URL was provided but a proxy port number was not. If either a proxy URL or a proxy port are specified, both must be specified.

Action: Specify both a replication server URL and a replication server proxy port number and retry the operation.

ORA-64731: Replication server proxy port provided but proxy URL is NULL.

Cause: A replication server proxy port number was provided but a proxy URL was not. If either a proxy URL or a proxy port are specified, both must be specified.

Action: Specify both a replication server URL and a replication server proxy port number and retry the operation.

ORA-64732: HTTP server not configured at replication host.

Cause: The HTTP server at the replication host site has not been configured.

Action: Configure the HTTP server at the replication host site and retry the operation.

ORA-64733: Unable to move individual backup piece with BP_KEY %s; not a KEEP backup.

Cause: An attempt was made to move an individual backup piece, but the backup set of which this backup piece was a member was not a KEEP backup.

Action: Specify a backup piece key that is a member of a KEEP backup set and retry the operation.

ORA-64735: Unknown incarnation detected at Recovery Appliance, need catalog resync.

Cause: A new archived log or backup set belonging to the new incarnation was received at Recovery Appliance.

Action: Using RMAN, connect to the Recovery Appliance as a recovery catalog, primary database as target database and perform the resynchronization operation using the RESYNC CATALOG RMAN command. If this error occurred at downstream of the Recovery Appliance (in a replicated Recovery Appliance setup), the reconcile operation fixes this error automatically when the same error is fixed at the upstream Recovery Appliance.

ORA-64736: Task ID %s of type %s has been interrupted %s times.

Cause: The specified task was restarted an unexpected number of times. Tasks get interrupted when there is competition for resources. This is only a warning. It does not necessarily indicate a problem with the Recovery Appliance.

Action: If these problems persist for long periods, contact Oracle Support Services.

ORA-64737: Unable to copy a full backup for database %s because of missing data files.

Cause: While creating a full database backup to tape or to a replicated Recovery Appliance, level 0 backups of one or more data files were missing.

Action: Query the RA_SBT_TEMPLATE_MDF view to determine the data files for which backups are missing. If using the "incremental forever" backup strategy, perform a level-0 incremental backup for the given database and retry the operation.

ORA-64738: guaranteed copy suspended for database %s

Cause: One of the following operations was performed resulting in the database using more than its allotted disk space:

- UPDATE_DB lowering the DISK_SPACE_RESERVE value.

- UPDATE_PROTECTION_POLICY setting the guaranteed_copy parameter to YES

- DELETE_SBT_LIBRARY where backup data for the given database existed. New backup requests may be stalled until the system can recompute the safety of allowing additional backup data or backup data may be lost.

Action: This event can be avoided by ensuring backups are written to tape in a timely manner. Conversely, one should avoid the activities listed in the Cause statement when backups are not being written to tape in a timely manner.

ORA-64740: Redo and backups from database %s have not been seen for more than UNPROTECTED_WINDOW period

Cause: An UNPROTECTED_WINDOW parameter in protection policy has been specified and the Recovery Appliance has not received sufficient on-line redo, archive log backups, or data file backups from the given target database for at least that period.

Action: Ensure that backups are being performed in a timely manner and that, if set up, redo logs or backups are being sent to the Recovery Appliance.

ORA-64741: Scheduler %s running task %s of type %s did not stop after %s requests.

Cause: The specified Recovery Appliance scheduler process could not be stopped.

Action: If these problems persist for long periods, contact Oracle Support Services.

ORA-64742: database (%s) is in state %s which is unsupported for ( %s).

Cause: An operation was attempted on a database that was in a state precluding the operation being performed.

• The database is being deleted, is suspending, has been suspended or is provisional, and therefore cannot be used to allocate Recovery Appliance storage location.
• Delete database cannot be performed on a database that is already being deleted or suspended.
• The database is unregistered for archival backups.
• The database is in an inactive state that cannot be used for data guard.

Action: The operation should not be tried on databases in an incompatible database state.

ORA-64744: Argument %s is null, invalid, or out of range.

Cause: The argument was expecting a non-null, valid value but the argument value passed in was null, invalid, or out of range.

Action: Check your program and correct the caller of the routine to not pass a null, invalid or out-of-range argument value.

ORA-64745: Name length is %s characters; maximum length is %s characters.

Cause: The length of the name exceeded the limit.

Action: Specify a shorter name and retry the operation.

ORA-64746: Name contains invalid characters.

Cause: The name incorrectly started with "_", "-", ":" or digits or contained non-alphanumeric characters. Verify that all other double quotation marks, if any, in the string are adjacent pairs of double quotation marks. Double quotation marks must not be used in the middle of the name.

Action: Change the name and exclude the invalid characters.

ORA-64747: Name contains invalid character "%s" at the position [%s].

Cause: The name incorrectly started with "_", "-", ":" or digits or contained non-alphanumeric characters. Verify that all other double quotation marks, if any, in the string are adjacent pairs of double quotation marks. Double quotation marks must not be used in the middle of the name.

Action: Change the name and exclude the invalid characters.

ORA-64748: trace file writing initiated using %s

Cause: The configuration of the Recovery Appliance was modified to enable the producing of trace files. Trace files have the capacity to exhaust disk space on the Recovery Appliance.

Action: Turn off the tracing when it is no longer required.

ORA-64750: Instance %s is unable to access %s.

Cause: The Recovery Appliance was unable to find a file that is required for its operation.

Action: Ensure that the file system of the specified file is available on the specified instance.

ORA-64751: Replication setup error during %s. replication server:%s database:%s.

Cause: The Recovery Appliance was unable to complete the configuration and setup of replication for the database specified.

Action: Validate that the downstream replication server is properly configured and all network communication paths are valid.

ORA-64752: storage unavailable for new redo or backups for database %s

Cause: There was a failure while backing up redo or copying backups from a polling location. This condition may be due to one of the following reasons:

* An individual backup piece exceeded the database protection policy DISK_RESERVE_SPACE value. * Guaranteed_copy is enabled but not enough data has been spooled to tape. * Misconfiguration of the storage location size.

Action: Check for the value of DISK_RESERVED_SPACE and storage location uses.

ORA-64753: Incorrect object type specified; specified %s, expected %s

Cause: An incorrect object type was given to an API command.

Action: Use the object-specific API. For example, use 'resume_replication_server' instead of 'resume_sbt_library'.

ORA-64754: Unable to perform operation with associated tape or replication objects.

Cause: An attempt to execute 'update_db' or 'update_protection_policy' and change storage locations with a replication server or tape job associated with the protection policy failed.

Action: Create a temporary protection policy that has the same storage location as the current protection policy with the tape and replication attributes of the target protection policy, Update to the temporary protection policy then finally update to the target protection policy.

ORA-64755: Operation is not allowed when the Recovery Appliance is not running.

Cause: An API request was attempted that requires the Recovery Appliance to be operational.

Action: Have the Recovery Appliance administrator execute DBMS_RA.STARTUP_RECOVERY_APPLIANCE and retry the request.

ORA-64757: unable to restore backup piece with BP_KEY %s

Cause: An attempt was made to restore the specified backup piece which resulted in an error. An explanation of the error appears in the following messages.

Action: Verify the correctness of the backup piece. If it is corrupt, either delete it or replace it.

ORA-64758: unable to grow delta store metadata in tablespace %s

Cause: Additional extents could not be allocated for the tables used to implement the delta store.

Action: Add additional storage to the indicated tablespace.

ORA-64759: Recovery Appliance is leaving restricted resources state

Cause: The Recovery Appliance ended its restrictions on task execution. The restricted resources state was entered when tasks could not run due to insufficient temporary table space or insufficient undo space. At that time, resource intensive tasks were put into RESOURCE_WAIT state.

Action: None. This is only an informational message entered in the alert log.

ORA-64760: Database %s has had tasks in ordering wait state for over %s days.

Cause: The specified database had an INDEX_BACKUP task that could not be run because the task did not tile against the delta store. An incremental backup piece will not tile into the delta store when the necessary control file information is missing or when the backup that it depends upon is not found in the delta store.

Action: Resolve the warnings for the database. A new full backup for the database should also clear this condition.

ORA-64761: disk group %s is not usable by the Recovery Appliance

Cause: A disk group was supplied to either the create_storage_location or update_storage_location APIs that was not previously prepared by the installation software for the Recovery Appliance.

Action: Run the ra_update procedure to process the disk group and retry the API.

ORA-64762: Task %s of type %s has been running for %s.

Cause: The specified task did not complete its execution after a reasonable period. This is only a warning message.

Action: If these errors persist, contact Oracle Support Services.

ORA-64763: Task %s of type %s was terminated after running for %s.

Cause: The specified task did not complete and was presumed hung. Its process was stopped and restarted.

Action: If these errors persist, contact Oracle Support Services.

ORA-64764: Metadata validation task %s was interrupted by COALESCE task while validating df_key %s.

Cause: . The metadata validation task took too long to validate a df_key and blocked a COALESCE task. The df_key validation was terminated before completion and the df_key was skipped.

Action: None

ORA-64766: backup deletion using RMAN prevented by protection policy

Cause: Recovery Manager was prevented from deleting a backup piece, because the allow_backup_deletion parameter of the applicable Recovery Appliance protection policy was NO, or because a prior recovery_window_compliance duration has not passed.

Action: Modify the allow_backup_deletion parameter of the applicable protection policy to YES to allow for deletion of backups and wait for any remaining .recovery_window_compliance windows to espire. Check the ra_recovery_compliance view to find active compliance windows.

ORA-64767: restore timed out

Cause: The Recovery Appliance terminated the restore operation due to unresponsiveness of the client database.

Action: Verify the network between the client database and the Recovery Appliance. Also verify the client database I/O performance. If the error persists, contact Oracle Support Services.

ORA-64768: KEEP file size %s cannot exceed available DISK_RESERVED_SPACE %s

Cause: There was no more space for a KEEP backup piece. The total DISK_RESERVED_SPACE minus the space currently consumed by KEEP backups was less than the size of the current KEEP backup piece. The piece that caused the error was deleted.

Action: Use DBMS_RA.UPDATE_DB to increase the DISK_RESERVED_SPACE value of the database or move KEEP (archival) backups to other storage using the DBMS_RA.MOVE_BACKUP function.

ORA-64771: reconcile error during %s; replication server: %s; database: %s

Cause: The specified database was unable to reconcile with the specified replication server. This is typically due to either a network communication failure, missing or incorrect credentials, incorrect wallet credentials, missing or incorrectly ordered add_db and grant_db_access calls.

Action: Check the incident log for active failures with a component type of REPLICATION_RECONCILE. Resolve the reconcile issues and resume_replication_server or wait until the next reconcile time period. After a successful reconcile all stalled replication tasks will continue and the incident is marked as FIXED.

ORA-64772: downstream replication server: %s is not accessible

Cause: The specified downstream replication server was not running, was not accesible, had incorrect credentials for the replication user in the upstream wallet, or was in the process of starting up or shutting down.

Action: If the credentials are incorrect, correct the credentials. Otherwise, the incident is marked as FIXED once the downstream replication server comes back online or is accessible over the network.

ORA-64773: Note: %s generated during execution of API command: %s

Cause: The specified command was entered correctly but an unexpected event occurred during its processing.

Action: Check the message for further information.

ORA-64774: database %s has replication tasks in reconcile wait state for over %s days

Cause: The specified database had a BACKUP_SBT task that could not be run because the task was waiting for a successful reconcile.

Action: Check the incident log for active failures with a component type of REPLICATION_RECONCILE. Resolve the reconcile issues and execute a manual reconcile, execute a resume_replication_server, or wait until the next reconcile time period. After a successful reconcile, all stalled replication tasks continue and the incident is marked as FIXED.

ORA-64775: unable to authenticate with the downstream recovery appliance for the database %s.

Cause: The specified database could not execute the required code on the downstream replication server. This is typically due to a missing add_db or grant_db_access on the downstream or the commands were issued in the incorrect order.

Action: Ensure that you execute add_db followed by grant_db_access on the downstream replication server. Then reissue the command, execute a manual reconcile, execute a resume_replication_server, or wait until the next reconcile time period. After a successful reconcile, all stalled replication tasks continue and this error is cleared.

ORA-64776: message from downstream replication server during %s: %s

Cause: An unexpected event occurred at the downstream replication server.

Action: The message includes additional information for further examination on the downstream replication server.

ORA-64777: deletion of polled file failed

Cause: The Recovery Appliance could not delete the file that was backed up from the polling location.

Action: Check if the directory specified in the polling location grants the necessary permission to allow for deletion of files.

ORA-64778: privilege not granted to %s for database: %s

Cause: The privilege that was revoked was not granted to the user for this protected database, the revoke was not required.

Action: Do not issue the revoke for this privilege for the protected database, it is not granted to the user.

ORA-64779: The catalog is missing necessary control file information for database %s.

Cause: A backup arrived before the Recovery Appliance could receive all the necessary control file information. INDEX_BACKUP tasks for these data files remain in ORDERING_WAIT state until the catalog receives all the information.

Action: Use the RMAN command RESYNC CATALOG to fix this issue. If the problem persists, contact Oracle Support Services.

ORA-64780: Section 1 of multi-section backup set %s of data file %s has not reached this Recovery Appliance.

Cause: Section 1 of the multi-section backup did not reach the Recovery Appliance. Without the section, INDEX_BACKUP tasks of other sections of the backup set remain in ORDERING_WAIT state.

Action: This could be temporary because sections of a multi-section backup do not reach the Recovery Appliance in order. If the problem persists, check the status of the incoming backup, as well as status of INDEX_BACKUP tasks for this database.

ORA-64781: Section %s of the prior multi-section backup set %s of data file %s is missing.

Cause: A section of the previous multi-section backup prior to the current backup was missing. Without the section, INDEX_BACKUP tasks for processing the current backup set remain in ORDERING_WAIT state.

Action: An INCREMENTAL LEVEL 1 CUMULATIVE or INCREMENTAL LEVEL 0 backup of the data file should clear this condition.

ORA-64782: Missing backups between SCNs %s and %s for data file %s.

Cause: There was a gap in backups provided to the Recovery Appliance. Without the backup, the current backup could not be processed, and the INDEX_BACKUP task remained in ORDERING_WAIT state.

Action: An INCREMENTAL LEVEL 1 CUMULATIVE or INCREMENTAL LEVEL 0 backup of the data file should clear this condition.

ORA-64783: The backup of data file %s is tiling with a backup written to different media.

Cause: The backup on which the current backup piece depends was written to different media and no longer resides on this Recovery Appliance.

Action: The incremental forever mechanism of the Recovery Appliance does not support backups written to disk or other media. Provide an INCREMENTAL LEVEL 0 backup of the data file.

ORA-64784: Corruption found in backup %s of data file %s in Recovery Appliance. New backup cannot be processed.

Cause: A new backup could not be processed because the most recent backup piece of the data file residing in the Recovery Appliance was corrupt.

Action: An INCREMENTAL LEVEL 0 backup of the data file should clear this condition.

ORA-64785: Online redo shipping for DBID %s cannot be performed because the Recovery Appliance is not available.

Cause: The Recovery Appliance was unable to automatically receive archive logs from the indicated database because the Recovery Appliance was not running.

Action: Execute the startup API on the Recovery Appliance before sending archive logs to it.

ORA-64786: Online redo shipping for DBID %s cannot be performed because the delta store is under repair.

Cause: The Recovery Appliance was unable to automatically receive archive logs from the indicated database because the delta store was under repair.

Action: The archive logs are accepted once the repair completes. If the message persists, contact Oracle Support Services.

ORA-64787: Online redo shipping for DBID %s cannot be performed because the database has been suspended or deleted from the Recovery Appliance.

Cause: The Recovery Appliance was unable to automatically receive archive logs from the indicated database because the database was suspended or deleted.

Action: If the database has been deleted, remove the Oracle Data Guard log destination corresponding to the Recovery Appliance from the indicated database; or add or resume the indicated database to the Recovery Appliance.

If the database has been suspended, resume the database in order to restart online redo shipping.

ORA-64788: Online redo shipping for DBID %s cannot be performed because its platform is unknown.

Cause: The Recovery Appliance was unable to automatically receive archive logs from the indicated database because an initial backup from the database was not supplied. The initial backup provides the platform identification to the Recovery Appliance.

Action: An initial backup must be sent from the indicated database to the Recovery Appliance using the recovery manager (RMAN).

ORA-64789: Online redo shipping for DBID %s cannot be performed because its storage location needs repair.

Cause: The database for the Recovery Appliance was opened by specifying resetlogs.

Action: Contact Oracle Support Services.

ORA-64790: Online redo shipping for DBID %s cannot be performed because it is not known by the Recovery Appliance.

Cause: The database was not identified in the catalog of the Recovery Appliance.

Action: Execute the ADD_DB API for the specified database.

ORA-64791: DBMS_SCHEDULER jobs have delayed starting on instance %s.

Cause: Problems on the specified instance are preventing DBMS_SCHEDULER jobs from getting into RUNNING state. Until the backlog is cleared, only jobs essential to the health of the Recovery Appliance are created on the instance.

Action: Contact Oracle Support Services.

ORA-64792: incorrect catalog_user_name parameter specified in create_replication_server

Cause: An incorrect catalog_user_name parameter was specified in the create_replication_server or update_replication_server API.

Action: The catalog_user_name parameter must be the owner of the Recovery Appliance schema.

ORA-64793: unexpected scheduler exit

Cause: The task scheduler failed with an unexpected error code in the Recovery Appliance.

Action: Contact Oracle Support Services.

ORA-64794: unable to access the encryption HSM wallet or the encryption wallet is not open on the current instance

Cause: Encryption required a Hardware Security Module (HSM) wallet that was open across all instances.

Action: Ensure the following: - That there is a valid connection to the HSM keystore. - That the HSM credentials are correct. - That the wallet is open across all Oracle RAC instances in GV$ENCRYPTION_WALLET.

ORA-64795: unable to access or create the encryption key

Cause: Encryption could not create or obtain the required access to a valid backup encryption key during the copy to tape operation.

Action: This could be due to a network connection issue, missing or incorrect credentials, or a misconfigured key store. Inspect the ERROR_TEXT in the RA_INCIDENT_LOG for additional information.

ORA-64796: unable to create encrypted backup during copy to tape

Cause: During the copy to tape operation, backup encryption could not create or obtain the required access to a valid encryption key.

Action: Check the ERROR_TEXT in the RA_INCIDENT_LOG for additional information.

ORA-64797: waiting for recall of backup piece %s from cloud storage

Cause: Restore was waiting for a recall of the backup piece from cloud storage.

Action: None. This is only an informational message. The incident status is changed to FIXED once the backup piece is recalled.

ORA-64798: encryption key does not exist in wallet of executing instance

Cause: The protected databases current encryption key did not exist in the wallet of the Oracle RAC instance or the instance that was executing the copy to tape operation.

Action: Rekey the current database and verify that the RA_DATABASE.ENCRYPTION_KEYID for the protected database exists across all instances in GV$ENCRYPTION_KEYS.KEY_ID.

ORA-64799: Job template requires encryption for the specified library.

Cause: Encryption was not specified for a library that requires encryption.

Action: Use the DBMS_RA.UPDATE_SBT_JOB_TEMPLATE procedure and specify an encryption algorithm for all job templates associated with the specified library.

ORA-64800: unable to create encrypted backup for big endian platform

Cause: Copy to tape operation could not create encrypted backup for big endian platform.

Action: Contact Oracle Support Services.

ORA-64801: Altering RASYS password in SQL is not allowed.

Cause: RASYS Password modification attempted via SQL.

Action: Use racli alter rasys_user --password.

ORA-64803: failure to get ingest name for archivelog grouping

Cause: The Oracle backup process was unable to get the ingest name needed to connect to the Oracle restore process.

Action: Set the ingest name for the local node in the configuration variable.

ORA-64804: cannot reinsert deleted backup into delta store

Cause: The specified backup could not be reinserted into the delta store, because it either was previously deleted or contained a corresponding virtual backup in the same backup set that was removed from the catalog.

Action: Take a new backup of the data file.

ORA-64805: cannot reinsert virtual full backup into delta store

Cause: Virtual full backups or copies of virtual full backups could not be reinserted into the delta store because it could corrupt existing backups of the database.

Action: Use a virtual incremental backup of the data file.

ORA-64806: incorrect or all NULL input parameters specified for reset_error API

Cause: Some or all of the input parameters specified for reset_error API were incorrect or they were all NULL input parameters.

Action: Provide at least one valid input parameter.

ORA-64807: Datafile encryption information for database %s, data file %s does not match.

Cause: A data file was encrypted or rekeyed on the protected database and now the encryption key for the current INCREMENTAL LEVEL 1 backup does not match the prior encryption key.

Action: An explicit INCREMENTAL LEVEL 0 backup is needed for the encrypted data files to maintain recoverability.

ORA-64808: Initialization parameter %s has more than one SID value specified

Cause: There were multiple instance settings for one initialization parameter.

Action: Use "racli update parameter -type=db" to update the initialization parameter.

ORA-64809: Initialization parameter %s does not match the recommended value

Cause: Initialization parameter did not match the recommended value.

Action: Use "racli update parameter -type=db" to update the initialization parameter.

ORA-64810: Initialization parameter %s is not set with the proper value

Cause: Initialization parameter was not set with the proper value.

Action: Set the proper initialization parameter value.

ORA-64811: Initialization parameter %s has a non-default value.

Cause: Initialization parameter had a non-default value.

Action: Use "racli update parameter -type=db -restart_db" to update the initialization parameter.

ORA-64812: -force option is required to ignore checking %s initialization parameter

Cause: An attempt was made to ignore checking the initialization parameter value without specifying the -force option.

Action: Add the -force option when attempting to ignore checking the initialization parameter.

ORA-64813: Task %s is being suspended.

Cause: A Recovery Appliance task generated too many errors. Following an unexpected error, a task will be restarted. If it fails to successfully run after 10 tries, the Recovery Appliance normally marks the task as broken and no longer tries to restart it. However, if a task is important for a database's recoverability, it will not be failed. Instead, the task will be suspended. Suspended tasks will be retried every few days until they successfully run or have an irrecoverable failure.

Action: Contact Oracle Support Services if the task remains in SUSPENDED state for more than two weeks.

ORA-64816: Cannot create a replication server to an old version downstream Recovery Appliance.

Cause: The downstream Recovery Appliance was an older version.

Action: Contact Oracle Support Services.

ORA-64817: Error interacting with downstream Recovery Appliance during %s; replication server: %s; database: %s

Cause: An error was encountered during communication or conversationwith a downstream Recovery Appliance for the specified database with the specified replication server. This is typically due toa network communication failure, missing or incorrect wallet,credentials, missing or incorrectly ordered add_db and grant_db_access calls. The error could also indicate an issue during the conversation with the remote Recovery Appliance.

Action: Check the incident log for active failures with a component type of REPLICATION_REMOTERA. Resolve the connection issues and execute the resume_replication_server command or wait until the next reconcile time period. After a successful reconcile, all stalled replication tasks continue and the incident is marked as FIXED.

ORA-64818: Polling feature not supported for multiple tenants

Cause: Polling feature did not work on multiple tenants.

Action: None.

ORA-64819: Database %s with specified %s (%s) does not exist.

Cause: The specified database did not exist in the specified tenant.

Action:Specify an existing database and its associated tenancy.

ORA-64820: db_key %s does not exist.

Cause: No database associated with the db_key specified was found in the Recovery Appliance.

Action: Specify an existing db_key.

ORA-64821: df_key %s does not exist.

Cause: No data file associated with the db_key specified was found in the Recovery Appliance.

Action: Specify an existing db_key.

ORA-64822: Log file cannot be accepted from DBID %s on Tkey %s.

Cause: While performing redo shipping for the specified database, an error was detected that prevented the creation of the log file.

Action: Refer to the other errors in the error stack to determine the cause of the problem.

ORA-64823: Unable to move individual backup piece with BP_KEY %s; backup piece is not ready to move.

Cause: An attempt was made to move an individual backup piece, but the move backup operation encountered the resource busy issue for this backup piece. The backup piece still needed to replicate.

Action: Retry the move command.

ORA-64825: Handle %s already exists for database %s.

Cause: Another backup piece with the same handle already exists on the Recovery Appliance.

Action: For control file autobackup pieces in a Data Guard configuration, use the command RMAN CONFIGURE AUTOBACKUP FORMAT to ensure each database in a Data Guard configuration has a unique autobackup format string.

ORA-64826: filesize mismatch in %s for handle %s: catalog size=%s, but container size=%s

Cause: An internal error caused by an inconsistency in the size of the specified file maintained by two different components of the Recovery Appliance.

Action: Contact Oracle Support Services and provide trace and alert files..

ORA-64827: Database %s is not registered and therefore cannot be suspended.

Cause: A database that was not registered could not be suspended.

Action: Choose a database that has been registered.

ORA-64828: Database %s is not registered and therefore cannot be resumed.

Cause: A database that was not registered could not be resumed.

Action: Choose a database that has been registered.

ORA-64829: Database %s is not suspended and therefore cannot be resumed

Cause: A database that was not suspended could not be resumed.

Action: Use the suspend.db API to suspend the database.

ORA-64830: Incremental backup for database %s is not up-to-date.

Cause: Can be caused by a undersized appliance or indication of problem with backup for particular database.

Action: Run capacity planning report and review sizing of storage location as well as CPU, memory and disk utilization of components to seeif appliance is using more than 80% of resources for extended period of time. Also check for other incidents that may help describe the problem.If the cause is still not clear open a service request for Support.

ORA-64831: No outstanding backups to request for specified group.

Cause: Backup request group is either empty or has requested all backups.

Action: No action is necessary. This is an informational message only.

ORA-64832: Error interacting with remote Recovery Appliance: %s; replication server: %s; database: %s.

Cause: An error was encountered during communication or conversationwith a remote Recovery Appliance for the specified database with the specified replication server. This is typically due toa network communication failure, missing or incorrect wallet,credentials, missing or incorrectly ordered add_db and grant_db_access calls. The error could also indicate an issueduring the conversation with the remote Recovery Appliance.

Action: Check the incident log for active failures with a component type of REMOTERA. Resolve stated issue and rerun the command.

ORA-64833: Insufficient free space at this time is stopping backup acceptance.

Cause: The Recovery Appliance is experiencing an extreme shortage of free space. To prevent failure of redo shipping, new backups are temporarily being rejected.

Action: Retry operation after purging has caught up and free space has grown to a level that can accommodate incoming backups.

If free space does not recover, consider removing databases or reducing recovery windows on the Recovery Appliance.

ORA-64834: Failed to replicate backup piece with bp_key %s and handle %s.

Cause: An error was encountered while backup pieces was being replicated onto configured replication server.

Action: The subsequent error will identify the error that needs to be addressed.

ORA-64835: Recovery Appliance API error %s.

Cause: An error was detected during the execution of an API requirest.

Action: Address the conditions that are identified by the attached message.

ORA-64837: In storage destination %s, tried to create %s GB, but could only create %s GB.

Cause: During a create_storage_location or update_storage_location, an attempt was made to create container files in the specified storage location, but only a portion of the space could be added to the storage location.

Action: Verify that ASM has available space in the storage destination. If the available space is less than expected, use asmcmd to determine whether unwanted files have been created in the storage destination. Unwanted files may appear when a previous operation started to create a storage location and its files were not properly removed.

ORA-64838: Task %s of type %s waiting on event %s for %s seconds.

Cause: The specified task remains stuck waiting for the specified event. This is only a warning message.

Action: If these errors persist, contact Oracle Support Services.

ORA-64839: Task %s of type %s interrupted after waiting on event %s for %s seconds.

Cause: The specified task remained stuck waiting for the specified event. Its process was stopped and restarted.

Action: If these errors persist, contact Oracle Support Services.

ORA-64840: Illegal attempt to change a ZDLRA owned sbt_parms (%s); use procedure parameter (%s) instead.

Cause: An attempt was made to change an internal ZDLRA system parameter through sbt_parms.

Action: Remove the offending sbt_parms and instead use the specified procedure parameter to the update_replaction_server API.

ORA-64841: replication wallet_path cannot be NULL.

Cause: The replication server wallet_path cannot be NULL.

Action: Specify a valid wallet_path.

ORA-64842: Illegal attempt to manage a replication server using generic APIs. Use %s instead.

Cause: An attempt was made to cahnge a replication server using an API that does not support replication.

Action: Use replication specific APIs as given in the error message.

ORA-64844: Only %s GB out of %s GB reserved space is available to provision database %s.

Cause: An attempt was made to assign an initial reserved_space value to an autotuned_reserved_space database which was added with no initial reserved_space value, but there was insufficient unreserved space in the storage location to make the assignment.

Action: Remove unneeded databases from the Recovery Appliance to free up additional space that may be reserved. Manually assigning a lower reserved_space value to the database using the update_db API may also address the situation.

ORA-64845: Database %s must have a defined reserved_space value.

Cause: An attempt was made to assign a database without a reserved_space value to a protection policy with autotune_reserved_space set to NO.

Action: Specify a reserved_space value for the database using the update_db API or assign it a different protection policy with autotune_reserved_space set to YES.

ORA-64846: Database %s is growing too fast.

Cause: The recovery_window_space for an autotuned database has been growing at a rate that is unsupported. Instead of assigning the computed reserved_space setting to the database, a reserved_space is assigned that is constrained by the maximum permitted growth rate and the maximum reserved space permitted by the database's protection policy.

Action: If the reserved_space is constrained by the database's protection policy, assign the database to a protection policy that will support its required size. If the additional growth is valid, manually assign a reserved_space to the database using the update_db API.

ORA-64847: Storage location %s has no available space for autotuning reserved_space.

Cause: While autotuning the reserved_space settings within a storage location, the storage location ran out of unassigned space.

Action: Increase the size of the storage location, remove databases from the storage location, or decrease recovery_window_goal settings for databases within the storage location.

ORA-64848: Database %s has an estimated size of %s GB, but has a disk reservation of %s GB.

Cause: The estimated size of a databse exceeds the amount of space reserved for it within the storage location. The database is in danger of having its recovery window truncated if there is space pressure within its storage location.

Action: Increase the reserved_space assigned to the database.

ORA-64849: Storage location %s requires %s GB, but has only %s GB.

Cause: The sum of the estimaged sizes of the database within a storage location is greater than the total space of the storage location.

Action: Increase the size of the storage location, remove databases from the storage location or decrease recovery_window_goal settings for databases within the storage location.

ORA-64850: Only one of the following parameters must be specified (%s)..

Cause: Multiple parameters provided where only one is legal.

Action: Only specify one parameter from the list per request.

ORA-64851: A full backup of database %s from the past %s days is missing needed for archival backup.

Cause: While creating archival backup, level 0 backups of one or more data files were missing in the past max_redo_to_apply days.

Action: Query the RA_SBT_TEMPLATE_MDF view to determine the data files for which backups are missing. Increase max_redo_to_apply if older backups are present or take new backups of those data files.

ORA-64852: Missing archive log backup of database %s needed for archival backup.

Cause: Missing archive log backups while creating archival backup.

Action: Perform backup of archive log(s) which were not backed up.

ORA-64853: COPYALL replication feature not supported by downstream Recovery Appliance.

Cause: The COPYALL replication feature requires both Recovery Appliances to be running a version that support the feature. The downstream Recovery Appliance version is too old.

Action: Upgrade your downstream Recovery Appliance to a newer release.

ORA-64854: Database %s exceeds the maximum reserved space limit of %s GB.

Cause: A database violated the maximum_reserved_space limit specified by its protection policy.

Action: Assign the database to a protection policy that has a larger maximum_reserved_space limit.

ORA-64855: Unable to copy piece on %s because it is not recognized as a backup piece.

Cause: A database violated the maximum_reserved_space limit specified by its protection policy.

Action: Assign the database to a protection policy that has a larger maximum_reserved_space limit.

ORA-64857: OK4POOL: bpkey %s, rejected encrypted backup.

Cause: TDE Encrypted backups with RMAN compression will not be included into delta pool..

Action: Disable RMAN Database encryption and take INCREMENTAL LEVEL 0 backup for the encrypted data files.

ORA-64859: %s

Cause: .

Action:

ORA-64860: Insufficient space for compliance_hold in database %s.

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

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

ORA-64861: unable to restore for compliance_hold time.

Cause: The time stamp specified for a compliance_hold is not within a valid disk restore range.

Action: Choose a time for which the database is restorable.

ORA-64862: Database %s requires an additional %s GB space for recovery_window_compliance.

Cause: The reserved_space assigned to the database is not large enough to guarantee that the space specified by recovery_window_compliance will not be purged.

Action: Increase the reserved_space setting for the targeted database or specify a smaller recovery_window_compliance.

ORA-64863: cannot perform %s request with backups under %s restrictions.

Cause: The API that was attempted would violate compliance_hold, keep_compliance, recovery_window_compliance restrictions, or SBT immutability.

Action: Allow the restrictions to lapse before performing the API request.

ORA-64864: SBT libraries are needed to support guaranteed_copy in policy %s.

Cause: At least one SBT library with the guaranteed attribute are needed to support the guaranteed_copy attribute in a protection policy..

Action: Create an SBT library that has the guaranteed attribute before retrying the current operation.

ORA-64865: Library %s is needed to maintain immutable backups for database %s.

Cause: The library is currently referencing immutable backups which precludes the library from being modified by the current operation.

Action: Wait until backups stored in the library are no longer referenced by the designated database.

ORA-64866: The setting for %s conflicts with the setting for %s.

Cause: One or more of the specified settings conflicts with another setting provided in this request or a prior request.

Action: Resolve the conflict and try again.

ORA-64867: Backup set %s is not permitted to have its KEEP UNTIL TIME reduced or eliminated.

Cause: An attempt was made to change the KEEP UNTIL TIME of a backup set, but the Recovery Appliance KEEP_COMPLIANCE protection policy prevents this action.

Action: None. The KEEP UNTIL TIME for this bacup set cannot be reduced.

ORA-64868: Only RMAN encrypted backups are supported on this Recovery Appliance.

Cause: The Recovery Appliance has the SECURE_MODE protection policy set to YES for this database. This policy requires all backup data be encrypted with RMAN.

Action: Use RMAN with Transparent Data Encryption while creating your next backup.

ORA-64869: Unencrypted redo is not allowed for database %s.

Cause: The Recovery Appliance has the SECURE_MODE protection policy set to YES for this database. This policy requires all redo sent from the database to be encrypted.

Action: First alter the LOG_ARCHIVE_DEST settings to turn on Transparent Data Encryption. Then use RMAN to encrypt and backup the existing archived logs.

ORA-64870: Online redo shipping for DBID %s cannot be performed because the Recovery Appliance is preparing for planned maintenance.

Cause: The Recovery Appliance was unable to automatically receive archive logs from the indicated database because the Recovery Appliance will be undergoing maintenance operations in the near future.

Action: Retry the operation after the Recovery Appliance has been restarted.

ORA-64871: Database %s is already a COPYALL_BACKUPS replication destination from Recovery Appliance %s.

Cause: For the specified database, the downstream Recovery Appliance was already a COPYALL_BACKUPS destination from a different Recovery Appliance. COPYALL_BACKUPS can be specified from only one upstream Recovery Appliance.

Action: Move the database to a replication policy that does not have COPYALL_BACKUPS defined.

ORA-64872: Exceeded throttle_db_channel_limit %s.

Cause: Multiple RMAN jobs are running simultaneously and have exceeded the allotted channel count.

Action: Check the setting of config parameter throttle_db_channel_limit then check the number of channels used by your RMAN jobs.

Also check for errant jobs performing backup. It is also possible a nightly data file backup job is running at the same time an hourly archived log backup job is running. The solution is to either increase throttle_db_channel_limit or stagger the RMAN jobs so they do not run at the same time. Or you might simply use fewer channels in one or both jobs.

ORA-64873: Encryption information with id %s not found for backup piece %s.

Cause: The required encryption information was not fetched by the Recovery Appliance which prevented the backup piece from being validated or re stored.

Action: Contact Oracle Support Services and provide the necessary trace files.

ORA-64874: Database %s is already registered.

Cause: The specified database is already registered on the downstream Recovery Appliance.

COPYALL_BACKUPS replication requires the database to be unregistered .

Action: Either run DELETE_DB on the downstream followed by the ADD_DB and GRANT_DB_ACCESS or move the database to a replication policy that does not have COPYALL_BACKUPS defined.

ORA-64875: Unable to run API command at this due to %s.

Cause: The Recovery Appliance is in a state in which the current API command is not permitted to run.

Action: Retry the API command when the specified operation completes.

ORA-64876: Found unknown DBID for polling policy %s.

Cause: Found some polling files that are not associated with an active database in a protection policy that uses the polling policy.

Action: Ensure that all databases are in the active state and that polling tasks run after databases are added to the polling policy. Ensure that the unknown databases are in a protection policy that uses the polling policy. To find the list of files that have failed, look for files with status DBID NOT IN POLICY in the view ra_polling_files.

ORA-64877: Some polling files have timed out for polling policy %s.

Cause: One or more polling files are incomplete and have exceeded the timeout period for further processing.

Action: Recreate the polling files in the polling directory. To find the list of files that have timed out, look for files with status INCOMPLETE FILE in the view ra_polling_files.

ORA-64878: Illegal attempt to add/update %s to tenant %s.

Cause: (a) The user is in a tenant other than DEFAULT_TENANT.

(b) An incorrect add/update was attempted of the user or the database to the DEFAULT_TENANT.

(c) An add/update of the database has been made to REP_TENANT.

Action: Retry the register_tenant_user/add_db with the desired tenancy or update_db/add_db to a tenancy other than REP_TENANT.

ORA-64879: Backups cannot exist on both upstream and downstream Recovery Appliances for database %s.

Cause: The specified database has backups on both the upstream and the downstream Recovery Applicance. COPYALL_BACKUPS replication requires backups to exist on one Recovery Appliance only..

Action: Either run on the downstream Recovery Appliance DELETE_DB followed by ADD_DB and GRANT_DB_ACCESS. Or, on the upstream Recovery Appliance move the database to a replication policy that does not have COPYALL_BACKUPS defined.

ORA-64880: Restore point already exists.

Cause: The restore point name already exists. A restore point name must be unique.

Action: Either use a different name or delete the existing restore point on the Recovery Appliance with the same name.

Action: Either use a different name or delete the existing restore point on the Recovery Appliance with the same name.

ORA-64881: The provided restore_until_scn/restore_until_time is not in the restore range for database %s.

Cause: The restore_until_scn/restore_until_time should be in the restore range for the database.

Action: Retry the API using a restore_until_scn/restore_until_time that lies in the restore range for the database.

ORA-64882: Update %s is not allowed because one or more databases are associated with the user %s."

Cause: One or more databases is still associated with the user.

Action: Revoke_db_access for the specified user and retry the command.

ORA-64883: Update %s is not allowed because the replication server is not in a paused state."

Cause: The database is associated with a replication server that is not in a paused state.

Action: Pause the replication server then retry updating the database on the upstream and downstream.

ORA-64884: TLS certificate needs update.

Cause: TLS certificate is expiring or is expired.

Action: Replace expiring or expired TLS certificate with a new valid one.

ORA-64885: Online redo shipping for DBID %s cannot be performed because recovery from an instance failure is in progress.

Cause: The Recovery Appliance was unable to automatically receive archive logs from the indicated database because the Recovery Appliance is still recovering logs that were active when an instance went down.

Action: Retry the operation after waiting for all INSTANCE_CHANGE tasks to complete.

ORA-64886: Failed to create a container file with free space of %s GB which is less than the minimum file size of %s GB.

Cause: The creation of a container file failed due to free space being less than the minimum required file size as specified in the error message. ".

Action: Ensure there is enough free space available to create the container file, or contact support.

ORA-64887: Backup piece cannot be used because it is in RA format

Cause: POPULATE_BACKP_PIECE was called on a backup piece in RA format which is unsupported by this API.

Action: Ensure that POPULATE_BACKP_PIECE is only called on backup pieces that are not in RA format.