DLP Hot Backups failing after upgrade to 14.x (Oracle to 11.2.0.4)

DLP Hot Backups failing after upgrade to 14.x (Oracle to 11.2.0.4) on tools like netbackup, backupexec, commvault, etc.

The below error is seen:

Failure Reason: ERROR CODE [82:127]:
Network send failed: Software caused connection abort Source: DLPSERVERNAME,
Process: clBackup

In certain cases, even the below error is seen:

ERROR CODE [19:1335]:
Oracle Backup [CVImpersonateLoggedOnUser() failed for oraUser=[protect]
ntDomain=[DLPSERVER] m_hToken=2bc.]
Source: DLPSERVER, Process: ClOraAgent

On further investigation its found the Oracle Home (in the Backup Tool) still pointing to the Old Oracle Home Location. (This is since, as recommended, for DLP we install a new Oracle instance/version and re-point variables). Hence, the Oracle Home needs a change in/for all tools (includes Backups, Monitoring, Tripwire, etc.)

Edit the Oracle Path to the New Path = Drive:\Oracle\Product\11.2.0.4\db_1

This should help in resolving both the above listed errors.

() Additional Notes on this Topic:

What is Oracle Home w.r.t DLP?

The Oracle base location is the location where Oracle Database binaries are stored. During installation, you are prompted for the Oracle base path. Typically, an Oracle base path for the database is created during Oracle Grid Infrastructure installation.

To prepare for installation, Oracle recommends that you only set the ORACLE_BASE environment variable to define paths for Oracle binaries and configuration files. Oracle Universal Installer (OUI) creates other necessary paths and environment variables in accordance with the Optimal Flexible Architecture (OFA) rules for well-structured Oracle software environments.

For example, with Oracle Database 11g, Oracle recommends that you do not set an Oracle home environment variable allow OUI to create it instead. If the Oracle base path is /u01/app/oracle, then by default, OUI creates the following Oracle home path:

What are Offline (Cold) Backups w.r.t. DLP

An offline cold backup is a physical backup of the database after it has been shutdown using the SHUTDOWN NORMAL command. If the database is shutdown with the IMMEDIATE or ABORT option, it should be restarted in RESTRICT mode and then shutdown with the NORMAL option. An operating system utility is used to perform the backup. For example, in Unix you could use cpio, tar, dd, fbackup or some third party utility. To have a complete cold backup the following files must be backed up.

• All datafiles
• All control files
• All online redo log files (optional)
• The init.ora file (can be recreated manually)

The location of all database files can be found in the data dictionary views, DBA_DATA_FILES, V$DATAFILE, V$LOGFILE and V$CONTROLFILE. These views can be queried even when the database is mounted and not open.

A cold backup of the database is an image copy of the database at a point in time. The database is consistent and restorable. This image copy can be used to move the database to another computer provided the same operating system is being used. If the database is in ARCHIVELOG mode, the cold backup would be the starting point for a point-in-time recovery. All archive logfiles necessary would be applied to the database once it is restored from the cold backup. Cold backups are useful if your business requirements allow for a shut-down window to backup the database. If your database is very large or you have 24x7 processing, cold backups are not an option, and you must use online (hot) backups.

What are Online (Hot) Backups w.r.t DLP

When databases must remain operational 24 hours a day, 7 days a week, or have become so large that a cold backup would take too long, Oracle provides for online (hot) backups to be made while the database is open and being used. To perform a hot backup, the database must be in ARCHIVELOG mode. Unlike a cold backup, in which the whole database is usually backed up at the same time, tablespaces in a hot backup scenario can be backed up on different schedules. The other major difference between hot and cold backups is that before a tablespace can be backed up, the database must be informed when a backup is starting and when it is complete. This is done by executing two commands:

Alter tablespace tablespace_name begin backup;

Perform Operating System Backup of tablespace_name datafiles

Alter tablespace tablespace_name end backup;

At the conclusion of a hot backup, the redo logs should be forced to switch and all archived redo log files and the control file should also be backed up, in addition to the datafiles The control file cannot be backed up with a backup utility. It must be backed up with the following Oracle command in server manager:

Alter database backup controlfile to 'file_name';