Skip to main content

How can we help you?

Druva Documentation

Oracle Direct to Cloud Errors

Phoenix Editions: File:/tick.png Business File:/cross.png Enterprise File:/tick.png Elite

 

This topic lists the errors that you may encounter during Oracle configuration.  

ORACLE_DTC1

Error message: Cannot perform archive log backup. Archive log chain is broken.

Error description: The archive log chain might break because of the following reasons:

  • The archived log sequences are accidentally deleted.
  • The archive logs are not found after the last archive log backup.

Error solution: Perform a full backup to initiate a new archive log chain.

ORACLE_DTC2

Error message: Cannot perform archive log backup. Incarnation is changed.

Error description: The incarnation of the database might change because of the following reasons:

  • A database might be opened with the RESETLOGS option.
  • An attempt is made to undo the effects of the RESETLOGS by restoring backups taken before RESETLOGS.

Error solution: Perform a full backup to initiate a new archive log chain with the latest incarnation.

ORACLE_DTC3

Error message: Cannot perform archive log backup. Resync flag is set.

Error description: This error might occur if the data corruption occurs during the last backup of a database.

Error solution: Perform a full backup to create a baseline for the next incremental and archive log backups.

ORACLE_DTC4

Error message: Oracle instance is not available.

Error description: This error might occur when the Oracle instance does not startup. This might occur if:

  • The SGA requires more space than was allocated for it.
  • The operating system variable pointing to the Oracle instance is improperly defined.

Error solution: Identify the issue on the server and bring up the Oracle instance. Refer to Oracle documentation for more details.

ORACLE_DTC5

Error message: RMAN error occurred on the Oracle server. Check RMAN logs for details.

Error description: This error might occur if an ongoing backup or restore operation fails due to RMAN errors.

Error solution: To resolve this error:

  1. Inspect the Progress logs or Detailed logs on the Jobs page for RMAN errors.
  2. If the expected archived log not found, loss of archived log compromises recoverability error occurs in the RMAN logs, check whether archive logs are unavailable or expired for the database by connecting to RMAN and running the crosscheck archivelog all command. 
    The list of all archive logs along with their statuses are displayed. 
    Run the delete expired archivelog all command to clean up all archive logs with the expired status. Trigger backup. 
  3. Refer to Oracle documentation for more details. 
  4. Contact Support to resolve the errors.

ORACLE_DTC6

Error message: Cancelling Log Backup job, as Schedule/BackupNow event has occurred.

Error description: This error can occur if a scheduled or manual backup is triggered when an archive log backup job is already in progress.

Error solution: The archive log backup job gets triggered automatically as per the configuration after the full/incremental backup completes.

ORACLE_DTC7

Error Message: Oracle server discovery on the client failed

Error Description: This error can occur if Druva Phoenix fails to discover Oracle resources, such as individual Oracle instances and Oracle RAC configurations.

Error Solution: To resolve this error, check the Phoenix agent log file for errors. Contact Support.

ORACLE_DTC8

Error Message: Cannot perform backup. Resetlog change number in one or more data files is greater than incarnation resetlog change number.

Error Description: This error occurs when the RESETLOGS change number in one or more data files is greater than the incarnation RESETLOGS change number.

Error Solution: To resolve this error, review the Druva Phoenix log (Phoenix.log) file for issue details. Contact Support.

ORACLE_DTC9

Error Message: Invalid Log Backup job as the DB is in the NOARCHIVELOG mode.

Error Description: This error occurs when the archive log backup is scheduled for a database, which is in the NOARCHIVELOG Mode.

Error Solution: To resolve this error, disable the archive log backup from the backup policy.

ORACLE_DTC10

Error Message: Cannot perform online backup as the DB is in the NOARCHIVE log mode.

Error Description: This error occurs when an online backup for a database cannot be performed, which is in the NOARCHIVELOG mode.

Error Solution: To resolve this error, enable the Perform offline backup if database is in NOARCHIVELOG mode option of the RMAN settings in the backup policy.

ORACLE_DTC11    

Error Message: Cannot perform archive log backup. ResetLogsChange has changed for this incarnation.

Error Description: This error occurs when the database is opened with the RESETLOGS option and Oracle creates a new incarnation, however, the incarnation number is the same as in the last backup.

Error Solution: To resolve this error, perform a full backup of the database.

ORACLE_DTC12

Error Message: Restore cancelled as another restore started for same DB.

Error Description:  This error occurs for a database that has an ongoing restore operation and another restore operation is initiated on the same database for a backup set different than the one for which restore is in progress.

ORACLE_DTC14

Error message: No logs found.

Description: This error occurs when the requested logs for a particular job are not available on the Oracle server host.

Resolution: To resolve this error, contact Support.

ORACLE_DTC15

Error message: Zip upload failed.

Description: This error occurs when the agent fails to upload logs to the S3 bucket due to unavailability of the deviceStore service or network issues.

Resolution: To resolve this error, trigger the Log Request job or contact Support.

ORACLE_DTC16

Error message: Metadata Error.

Description: This error occurs when there is an issue while creating, updating, validating, downloading, or loading the metadata file.

Resolution: Trigger a full backup or contact Druva Support.

ORACLE_DTC17

Error message: IOServer Process Error.

Description: This error occurs when there is any issue while connecting or disconnecting with partner IOserver Process.

Resolution: Contact Support.

ORACLE_DTC18

Error message: SQLPLUS Error.

Description: This error occurs when the SQL query execution fails.

Resolution: Check if the database is in the Open state or contact Support.

ORACLE_DTC19

Error message: Configuration or Validation Error.

Description: This error occurs when validation of a job fails or fetching the job configuration details fails.

Resolution: Contact Support.

ORACLE_DTC20

Error message: Authentication Error.

Description: Failed to authenticate database credentials.

Resolution: Check the credentials assigned to the database or contact Support.

ORACLE_DTC21

Error message: Archive Log Validation Error.

Description: Failed to get archive log information for the database.

Resolution: Check if the database is up or contact Support.

ORACLE_DTC22

Error message: Wallet Backup Error.

Description: This error occurs when wallet files listing, uploading, or deletion fails.

Resolution: Contact Support.

ORACLE_DTC512

Error message: The specified backup request type is invalid. The supported backup request types are FULL, INCR, and LOG

Description: This error occurs when you have entered an invalid backup type in the backupNow or bulkBackupNow request.

Resolution: Use the following BackupType values for the respective BackupNow requests:
 

Value Description
FULL Specify this value for a full BackupNow request.
INCR Specify this value for an incremental BackupNow request.
LOG Specify this value for an archive log BackupNow request.

ORACLE_DTC513

Error Message: Failed to get the backupset because the backupset doesn't exist or is disabled permanently

Error Description: This error occurs when you trigger a backup for a backupsetID for which the backupset does not exist.

Error Solution: To ensure you are using the correct backupsetID in the backupNow request, list all your backupsets for a specific organization. You can use the ListBackupsets API (Reporting API link) to get the backupsetIDs corresponding to each backupset.

ORACLE_DTC514

Error Message:  Failed to trigger the backup job

Error Description: This error occurs due to multiple reasons.

Error Solution: Contact Support.

ORACLE_DTC515

Error Message: The job is already completed and cannot be cancelled.

Error Description: Druva Phoenix cannot cancel the jobs that are already completed.

Error Solution: Jobs with the following status cannot be cancelled:

  • Successful
  • Failed
  • Canceled
  • Successful With Errors

 ORACLE_DTC516

Error message: Failed to cancel job for the specified job ID.

Error description: This error occurs due to multiple reasons.

Error Solution: Contact Support.

ORACLE_DTC517

Error message: Failed to get external service response

Error description: This error occurs when the PhoenixOracleSBTConfig service is unable to interact with other services like PhoenixAuthorization, PhoenixCustomerConfig, and so on.

Error Solution: Contact Support.

ORACLE_DTC518

Error message: Failed to list backupsets for the specified backupset IDs

Error description: This error occurs when Druva Phoenix is unable to fetch the list of requested backupsets due to multiple reasons.

Error Solution: Contact Support.

ORACLE_DTC519

Error message: Failed to trigger the backup job because the specified backupset is in an invalid state.

Error description: This error occurs when you trigger a backup job for a backupset which is in an invalid state for backups. A backupset can be in an invalid state in the following scenarios:

  • Creation in progress: Backupset creation is in progress.
  • Storage cset state change: The backupset is either being created or recovered.
  • Marked for deletion, Storage cset deletion in progress, Deletion in progress : Backupset deletion is in progress
  • Permanently disabled: The backupset is permanently deactivated.

Error Solution: Make sure that you are using the correct Backupset ID by using the List Backupsets API. See the following table to resolve errors caused due to invalid states:

Sr. No Invalid State for Backups Solution
1.
  • Creation in progress
  • Storage cset state change
Backupset creation is in progress, please try after sometime.
2.
  • Marked for deletion 
  • Storage cset deletion in progress
  • Deletion in progress
You cannot trigger backup as the backupset is deleted. For more information, contact Support.
3. Permanently deactivated You can restore the existing snapshots of the databases, but you cannot backup them further.

 

 

  • Was this article helpful?