Patch-ID# 112410-01
Keywords: NetBackup 4.5 SAP
Synopsis: NetBackup 4.5 NB_SAP_45_4_M fix
Date: May/15/2003

Install Requirements: None                      
                      
Solaris Release: 2.6 7 8 9

SunOS Release: 5.6 5.7 5.8 5.9

Unbundled Product: Veritas NetBackup

Unbundled Release: 4.5

Xref: 

Topic: Veritas NetBackup 4.5 SAP jumbo patch

Relevant Architectures: sparc

BugId's fixed with this patch: 4860463

Changes incorporated in this version: 4860463

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/dbext/SAP.solaris2.6.tar.Z
<install_dir>/openv/netbackup/dbext/SAP.solaris2.6.version

Problem Description:

4860463 Convert Veritas patch NB_SAP_45_4_M_257037.solaris2.6.tar to sun patchadd format

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

Special Install Instructions:
1. Log in as the Oracle user and shut down all Oracle instances.(Recommended)
 
As root on the NetBackup for Oracle client:
 
2. add Sun-patch
 
 
3. - Server Remote installation instructions:
 
 
 To run installation of database clients (including local box if present).
 Run update_dbclients script located at /usr/openv/netbackup/bin.
 
 Example:
        update_dbclients <dbextension_name> -ClientList <filename>
 
         or
 
        update_dbclients <dbextension_name> <hardware_type> <operating_system>
 
If the 32-bit NetBackup DataBase Agent is currently installed,
the script /usr/openv/netbackup/bin/update_dbclients will report
in the trace file:
 
        Extension version files match - no update needed.
 
  The following is displayed to standard output:
 
        [N_number] client update(s) had up-to-date software according to
        the database extension version file.
 
        To force the installation of the database extension software
        for these client updates, you need to execute:
 
        update_dbclients -ForceInstall <dbextension_name> -ClientList <filename>
 
         or
 
        update_dbclients -ForceInstall <dbextension_name> <hardware_type> <operating_system>
 
  For more information look in the NetBackup SAP System Administrator's Guide.
 
3.  - Local installation instructions:
 
      Run  /usr/openv/netbackup/dbext/install_dbext
 
============================================
 
Description: 
    When using the SAP agent on a server which is running two SAP instances,
    the backint agent fails and produces an error/exit code of 2.
 
    This problem occurs when the /usr/openv/netbackup/bin/backint executable
    initiates.  This executable creates a directory named 
    /usr/openv/netbackup/logs/user_ops/sap. The backint executable creates a
    directory named "sap" with the following UNIX owner and permissions: 
 
    drwxr-xr-x 2 orasid dba .... sap 
 
    The owner of the directory is set to the userid of the oracle user 
    running the backup(ora<sid>) with the group owner set to "dba" and 
    permissions set to "755" (only owner can write). When the next backup is 
    started by the second SAP instance whose backup is running as a different 
    Oracle user, the backint executable exits with error code 2 because it 
    cannot write to the directory. 
 
Workaround: 
    To avoid this problem, manually change the permissions of the directory
    to 777. 
 
    (NetBackup Clients:  Alpha HP Intel-NT RS6000_433 RS6000_51 Solaris )
--------------------------------------------------------------------------------
Description: 
    Executing an SAP alternate raw path restore results in the error
    message, "Could not open device file". 
 
    (NetBackup Clients:  Alpha HP Intel-NT RS6000_433 Solaris )
================================================================================
 
Description: 
    Currently the $SAP_CLIENT environmental variable is ignored for backup 
    and stores the image under the physical host name.
 
    This would be an alternate host environmental variable to pass a 
    virtual name instead of a physical client name.

README -- Last modified date:  Thursday, May 15, 2003