Patch-ID# 108336-02
Keywords: Netbackup Oracle SAP
Synopsis: Netbackup 3.1.1 Database extention Jumbo Patch
Date: Aug/29/00
Solaris Release: 2.5.1

SunOS Release: 5.5.1

Unbundled Product: Sun StorEdge Enterprise NetBackup

Unbundled Release: 3.1.1

Topic: Netbackup 3.1.1: SAP database extention patch for Solaris 2.5.1

Relevant Architectures: sparc

BugId's fixed with this patch: 4188997 4276208

Changes incorporated in this version: 4276208

Patches accumulated and obsoleted by this patch:  

Patches which conflict with this patch:  

Patches required with this patch: 

Obsoleted by: 

Files included with this patch: 

<install_dir>/openv/netbackup/bin/backint

Problem Description: 

4276208 If a single stream fails only restart that stream and not whole backup

(from 108336-01)

4188997 cust trying to use SAP extension with netbackup

Patch Installation Instructions:
------------------------------------------------------------------------- 
Refer to the Install.info file within the patch for instructions on
using the generic 'installpatch' and 'backoutpatch' scripts provided
with each patch.  Any other special or non-generic installation
instructions should be described below.
-------------------------------------------------------------------------

Patch Installation Instructions:
------------------------------------------------------------------------- 
Refer to the Install.info file within the patch for instructions on
using the generic 'installpatch' and 'backoutpatch' scripts provided
with each patch.  Any other special or non-generic installation
instructions should be described below.
-------------------------------------------------------------------------

1. Verify that you are running NetBackup 3.1GA or 3.1.1GA.
   This patch will not work correctly with any other version.
      cat /usr/openv/netbackup/bin/version

2. Make sure no backups are running at the time of installation of this 
   patch


Additional Notes:

Description from Veritas patch S0800176

    This patch fixes three problems:
   
    Problem 1: SAP backups fail if client & master systimes are more
               then 24 hours off.
 
      If the client system time is +/- 24 hours different from the NetBackup
      master server, the backup will fail with an error.  After a backup runs 
      and succeeds, a bplist is done by backint to gather and report backup
      information to SAP.  Becuase the bplist has a 24 hour +/- window added
      to the start/end date, it fails with a 227 error and the SAP log shows
      a backup failure.
 
    Problem 2: SAP does not fail immediately when a backup job fails.
 
      If one of the backup jobs fails during an online backup,
      backint continues to backup all of the tablespaces and then
      fails the whole backup after all of the tablespaces have been
      processed. If a backup jobs fails, the whole backup job should
      fail immediately without any additional processing.
 
    Problem 3: The name of Progress logs for SAP backups are not unique.
 
      When performing an online backup, each backup jobs doesn't specify
      a unique progress log file. This make it difficult to debug NetBackup
      problems.
 


Description from Veritas Patch P0800111.

    This patch fixes two problems:
   
    Problem 1: Online backup
    If archive backups are executed at the same time as online database backup,
    the online database backup can fail.  The following error messages
    will appear in the backint and sap backup logs, if this problem occurs:

    ERROR: The switch.lis or switch.sem exist without a lock
    ERROR: cannot read switch = log file: /oracle/<SID>/sapbackup/.switch.log
   
    Problem 2: $SAP_DRIVES not used
    The SAP extension doesn't pick up the $SAP_DRIVES environmental variable.