Dell EMC Avamar 19.7 Release Notes

PDF

Oracle database plug-in known issues

The following table lists the Oracle database plug-in known issues in this release:

Table 1. Oracle database plug-in known issues
Issue ID	Subject/Functional area	Description	Workaround/Resolution
48182	RMAN CLI backups with Oracle RAC configuration do not reflect the scan name in Activity window	RMAN CLI backups with Oracle RAC configuration do not reflect the scan name in the Activity window. The interim solution for this problem is to copy $ORACLE_RAC_VAR/avoracle.cmd to $ORACLE_RAC_VAR/clientlogs/avoracle.cmd.	NA
273929	Best practices for Oracle and Lotus plug-ins to avoid issues with incremental backup when using a cloud tier	When a cloud tiering policy is configured for Avamar plug-ins for Oracle and Lotus, an earlier Full/L0 backup that is performed through the plug-in may already have been moved to the cloud tier. If this problem is the case, subsequent incremental/L1 backups do not complete, because no parent full/L0 backup is found on the active tier. For the Oracle plug-in, if this issue is encountered, the following error message is written to the plug-in log and the incremental backup fails: `An incremental backup was requested but there is no previous full backup. Please perform a full backup before any subsequent full backups.` For the Lotus plug-in, the following error message is written to the plug-in log and the incremental backup fails: `No Full backup found, Incremental backups cannot be taken without a full backup`	The best practice to avoid this issue is to select a Full/L0 backup interval that is smaller than the age threshold configured for moving backups to cloud tier. This step guarantees that the last Full/L0 backup is always available in the Active tier. For Oracle and Lotus plugins, after the incremental backup failure, you can either recall the last Full/L0 backup from the cloud tier, or perform a new Full/L0 backup instead of the incremental. Then subsequent incremental backups complete successfully.
277013	Data Domain authentication problem when Avamar Plug-in for Oracle installation has insufficient rights	On Windows systems, when the Avamar Plug-in for Oracle does not have sufficient rights to the <install-dir>\avs\etc\.tmp directory, the Data Domain is unable to write its authentication certificate to the directory, and backups fail. Interim solutions to this problem are: To allow full file access to the oracle user, manually change the privilege of the .tmp directory. Install the Avamar Plug-in for Oracle in a location that the Oracle user has full file access. Disable user authentication on the Windows host.	NA
281689	Known problem in Oracle, DB2, and Sybase plug-in for snapview failures	When a backup is initiated from the Avamar Administrator and fails in the late stages of the backup operation, it is possible that the plug-in application considers the backup to be successful. You cannot perform a restore operation on this backup from Avamar Administrator. Restoring such a backup might still be possible by using a command-line restore. This step is documented as a supported operation in the Oracle Plug-in user guide. How to identify the issue: The database reports the backup as successful, although the Avamar Administrator reports it as failed. Failed backup log messages include an error message that is generated during the late stages of the backup. For the Avamar Plug-in for Oracle, DB2, and Sybase ASE, the failure is logged with the error message `Failed to create the snapview. However, the database data has been successfully backed up and is marked as a hidden backup. Restore is available through CLI only. See the plug-in documentation for information about restoring hidden backups.` NOTE Best practice is to monitor all backup failures and ensure that such cases are followed with a successful full backup. This step requires that you create a successful full backup after any failed backup event.	NA
283392	Running two RMAN backups on same database results in unexpected results	When two concurrent backup sessions are initiated on the same database by using Oracle RMAN CLI by using a task file (for monitoring through the Avamar Administrator), one of the backups may fail. The following error message displays on the CLI: RMAN-03009: failure of backup command on c2 channel at 06/06/2017 11:32:25 ORA-19506: failed to create sequential file, name="ORCL_7us64227_1_1", parms="" ORA-27028: skgfqcre: sbtbackup returned error ORA-19511: Error received from media manager layer, error text: (UTF-8) sbtbackup: aborted!! Concurrent Oracle RMAN backups using a task file on the same database are currently not supported. Instead, run RMAN database backups using a task file, but archive logs or any other backup for the same database without using a task file.	NA
293174	In Windows, backup might fail if Oracle is installed with the New Windows User and the Avamar plug-in for Oracle software that is installed in the default path	Ensure that the Avamar Plug-in for Oracle software is installed outside of the default path C:\Program Files\avs.	If the Avamar Plug-in for Oracle software was installed in the default path, C:\Program Files\avs, perform either of the following steps to prevent authentication issues which might cause backups to fail: Manually change the privilege of C:\Program Files\avs\etc\.tmp to give the Oracle user full control. Disable the authentication.