Recovery Appliance Error Message Reference (Continued)

This chapter provides details on the Zero Data Loss Recovery Appliance (Recovery Appliance) error messages, which occur between ranges ORA-57800 and 57999.

This chapter provides details on the Zero Data Loss Recovery Appliance (Recovery Appliance) error messages, which occur between ranges ORA-64700 and ORA-64899 and between ranges ORA-61100 and ORA-61699.

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-64739: Tag length %s is too long

Cause: The tag name was longer than 32 characters.

Action: Specify a tag name shorter than 32 characters and retry the operation.

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

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: Recovery Window Goal is too small.

Cause: The protection policy is having the Recovery Window Goal is set to zero (0) which is not allowed for the Recovery Appliance.

Action: Please update the protection policy with a non zero or a NULL Recovery Window Goal.

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-64814: Downstream Recovery Appliance does not support remoteRA messages.

Cause: The Recovery Appliance logged this diagnostic message for a remoteRA operation in which the downstream was an older version.

Action: Consider upgrading the downstream Recovery Appliance software to match the upstream.

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-64843: Database with DBID %s is already registered in the catalog, tenant key %s. Deleting unregistered database %s.

Cause: An attempt was made to add a database with a DBID that is already registered in the catalog. Add two databases with the same DBID, such as primary and standby, to the same tenant is not permitted.

Action: Don't register databases with identical DBIDs to the same Recovery Appliance, same tenant. Because this database is already registered, you can connect to the catalog and perform your activities.

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-64858: Attribute set in use by existing SBT job template.

Cause: Not allowed to delete an attribute set this is currently used by an existing SBT job template.

Action: Delete the SBT job template and then try deleting the attribute set.

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.

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.

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: shutdown_recovery appliance timed out; continuing as abort_recovery_appliance.

Cause: The timeout interval for shutdown_recovery_applicance expired prior to the recovery appliance being quiesced. No more time will be spent waiting for activity to complete. Instead, all remaining activity on the recovery appliance will be aborted.

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

ORA-64889: Downstream Recovery Appliance does not have enough unreserved space for COPYALL replication of database %s.

Cause: The database on the Downstream Recovery Appliance uses autotune_reserved_space to allocate reserved space, but does not have enough unreserved space to receive the COPYALL_BACKUPS

Action: Free up reserved space from other databases, put the downstream data base into a protection policy without autotune_reserved_space, or add additional storage on the downstream Recovery Appliance.

ORA-64890: Recovery Appliance must be upgraded to the latest version

Cause: The Recovery Appliance received a request from a newer version of the Smart Data Protection Agent.

Action: Upgrade the Recovery Appliance to the latest version to ensure optimal support for all versions of the Smart Data Protection Agent.

ORA-64891: Smart Data Protection Agent reported error %s with message %s

Cause: The Smart Data Protection Agent reported an error to the Recovery Appliance during execution of the rcv fetch task command.

Action: Review the error code and message details to diagnose and resolve the issue.

ORA-64892: Missing required configuration parameters: %s

Cause: One or more mandatory Smart Data Protection Agent configurations are not configured in the Recovery Appliance, preventing backup script generation.

Action: Review the error message for listed configurations and provide values for the missing Smart Data Protection Agent settings in the Recovery Appliance.

ORA-64895: Insufficient space to accommodate increased reserved space of %s GB, for database %s under protection policy %s.

Cause: Insufficient allocatable space for protection policy to accommodate increased reserved space for specified database.

Action: Retry after increasing max reserved space setting for the protection policy.

ORA-64896: Insufficient space in storage location %s to accommodate increase d reserved space for all databases under protection policy %s.

Cause: Insufficient allocatable space on storage location to accommodate increased reserved space for all databases under protection policy.

Action: Retry after performing either of the following:

Add more storage to the storage location and then increase storage location autotune space limit settings.
Remove databases from the protection policy.