DB2 5.0GA Pack NB_DB2_50_7_M README DB2                         December 5, 2006
Requirement: NB_CLT_50_7_M
================================================================================
** All 5.0 MP7 Maintenance Packs for NetBackup server, client, all Add-on  
products, Database Agents, and Java GUI must be applied so that the entire  
system is at the same Maintenance Pack level. **

This Maintenance Pack provides fixes to Veritas NetBackup (tm) for DB2 Database  
Agent.
================================================================================


=================
PACK DEPENDENCIES
=================

    -- Installation of this Maintenance Pack requires version 1.17.4.40 of  
       the Vrts_pack.install script.

    -- NB_CLT_50_7_M must be installed prior to installing this Maintenance  
       Pack.

    -- The AIX 4.3.3 Maintenance Pack should not be installed on an AIX 5.1
       system.  Install the AIX 5.1 Maintenance Pack on an AIX 5.1 system.


I.   DOWNLOAD INSTRUCTIONS  
II.  KNOWN ISSUES    
III. INSTALLATION INSTRUCTIONS
IV.  UNINSTALL INSTRUCTIONS
V.   DESCRIPTION OF PROBLEMS FIXED
       Current Pack
          NB_DB2_50_7_M

       Pack History
          NB_DB2_50_6_M
          NB_DB2_50_5_M
          NB_DB2_50_4_M
          NB_DB2_50_3_M


=========================
I. DOWNLOAD INSTRUCTIONS
=========================
1) Download NB_DB2_50_7_M_<6 digit number>.<platform>.tar into the /tmp directory.

   where <platform> is:  hp11.00,linux2.4,rs6000_433,rs6000_51,solaris7

   where <6 digit number> is an internal tracking identifier

2) Extract NB_DB2_50_7_M_<6 digit number>.<platform>.tar
       /bin/tar xvf NB_DB2_50_7_M_<6 digit number>.<platform>.tar

       This will create the files
       Vrts_pack.install
       VrtsNB_DB2_50_7_M.README
       VrtsNB_DB2_50_7_M.DB2.<platform>.tar.Z



=================
II. KNOWN ISSUES
=================
There are no known issues associated with this Maintenance Pack.



==============================
III. INSTALLATION INSTRUCTIONS
==============================
There are two ways to install database agent maintenance pack software.

1.  Remote Installation:  Loads the software on a master server with
   the intent of pushing database software out to affected clients.

2.  Local Installation:   Loads and installs the software only to this
   local machine.

---

Remote Installation:

As root on the NetBackup Master server:

1. Install the Maintenance Pack binaries.

       cd /tmp
       /bin/sh Vrts_pack.install

  Pick option 1 (Remote Installation) when prompted for the installation
  method.

2. Run update_dbclients to push pack software affected database agent clients.
  For more information on how to run update_dbclients, refer to the NetBackup
  for DB2 System Administrator's Guide.

----

Local Installation:

As root on the NetBackup for DB2 client:

1. Install Maintenance Pack binaries.

       cd /tmp
       /bin/sh Vrts_pack.install
   
  If the pack is being installed on a master server, pick option 2,  
  Local Installation, when prompted.

  This will install NetBackup for DB2 onto the local client.



============================
IV. UNINSTALL INSTRUCTIONS
============================
1)  Close the NetBackup user interfaces.

    If a database agent is being used, such as DB2,  
    ensure that the database services are stopped.  

2)  Change directory to the patch save directory.  
   Substitute the pack name for $PACK in the following command:

    cd /usr/openv/pack/$PACK/save

3)  Run the un-install script:

    ./Vrts_pack.uninstall

4)  Verify that the pack uninstalled successfully by checking  
   /usr/openv/pack/pack.history.

5)  Only perform this step if the pack was originally pushed to remote  
   clients using update_dbclients.  Please run update_dbclients after  
   the pack was successfully uninstalled on the master server.



==================================
V. DESCRIPTION OF PROBLEMS FIXED
==================================
The following are descriptions of the problems fixed.  Please read the entire
document before installing.

README Conventions:

Description
    Describes a particular problem contained in this pack.

** Description **  
    Describes a problem that can lead to potential data loss. Please  
    read these problem descriptions carefully.

Workaround
    Any available workarounds to a problem are also listed. Workarounds  
    can be used INSTEAD of applying the patch, however, Symantec strongly  
    recommends that you are at the latest patch level.

Additional Notes  
    Any additional information regarding a problem is included.



=============  
Current pack  
=============  

================================================================================
Etrack Incident = ET536682

Description:  
   During a backup and a restore, the DB2 agent used the Policy listed
   in the db2.conf as a keyword.  If the policy name was changed between
   the backup and the restore, the restore failed because it could not
   find the image.  
--------------------------------------------------------------------------------
Etrack Incident = ET498145

Description:  
   This fix corrects a message catalog failure that prevented localized
   messages from being displayed in the DB2 script builder.  
--------------------------------------------------------------------------------
Etrack Incident = ET575347 ET609338 ET609487 ET609540 ET608376 ET609623 ET614668
ET612687 ET616976 ET617837 ET616940 ET622225 ET624432 ET633297 ET641183 ET699951
ET701953 ET781198 ET597210 ET598796 ET575338 ET596635 ET612761 ET787052 ET788824
ET786896 ET814652 ET575351 ET575352 ET575097 ET575330 ET575331 ET575345 ET575337
ET575335 ET577778 ET575333 ET596395 ET575334 ET575313 ET583770 ET575353 ET581028
ET575346 ET575329 ET575343 ET575308 ET575732 ET575309 ET575341 ET577306 ET575350
ET596637 ET596130 ET597780 ET601849 ET596188 ET596645 ET596654 ET596697 ET597281
ET597219 ET597298 ET596342 ET597379 ET598052 ET598865 ET599823 ET598813 ET600384
ET601396 ET601454 ET601344 ET600735 ET602205 ET600844 ET602349 ET603659 ET605285
ET602850 ET575311 ET607666 ET608687    

Description:  
   Buffer overflow areas have been identified and corrected in daemons running
   on Veritas NetBackup master, media, and client servers.  Successful access
   to a vulnerable Veritas NetBackup server and the ability to successfully
   execute arbitrary code could potentially result in unauthorized access with
   elevated privilege on a system.  
================================================================================



============
Pack History
============

=============
NB_DB2_50_6_M
=============
Etrack Incident = ET411553

Description:  
   If using the command line bpubsora and bpubsdb2 would core dump  
   immediately upon execution.
       
   If using the jbpSA interface, and the Oracle instance was clicked on, the  
   application would immediately exit with the message, "bin sh:6491 abort
   status 134" and it would dump a core file.  
--------------------------------------------------------------------------------
Etrack Incident = ET349781 ET289405

Description:  
   DB2 can now restore between instances and allow backups and restores of  
   the DB2 log files from a raw partition/device.  
--------------------------------------------------------------------------------
Etrack Incident = ET379394

Description:  
   The DB2 BAR interface does not enable you to browse an instance created on
   drives other than the default.  
--------------------------------------------------------------------------------
Etrack Incident = ET416983

Description:  
   NetBackup configuration variables that were set using the RMAN PARMS  
   option were not being used by the Oracle Agent.  

Workaround:  
   To avoid this issue, use the RMAN SEND command to specify NetBackup
   configuration variables.    
--------------------------------------------------------------------------------
Etrack Incident = ET418275 ET419072

Description:  
   Backup of DB2 logs without an associated entry in the db2.conf file results
   in a good status being returned to DB2, but the logs are not backed up and
   are deleted from DB2.  
--------------------------------------------------------------------------------
Etrack Incident = ET319000

Description:  
   Changes have been made to provide the following capabilities:
   -  Option to change the replica ID of unlogged databases
   -  Option to skip recovery of logged databases  

Additional Notes:  
   The touch file at <NetBackup Install Path>_NO_RECOVERY can be used
   To control recovery of logged Lotus Notes databases.  During restore,  
   The presence of the file will bypass recovery of logged Lotus Notes
   databases.  
================================================================================



=============
NB_DB2_50_5_M
=============
================================================================================
Etrack Incident = ET287965

Description:  
   DB2 templates that ran at the same time on a remote system seemed to  
   over-write each other on the client, causing one to fail.  

   (NetBackup Clients:  HP Linux2.4 RS6000_433 Solaris )
--------------------------------------------------------------------------------
Etrack Incident = ET292566

Description:  
   Support was added for DB2 Stinger.  

   All NetBackup Windows Clients HP Linux2.4 RS6000_433 RS6000_51 Solaris  
================================================================================


=============
NB_DB2_50_4_M
=============
Description:  
   The LIBRARY_PATH for loading the DB2 (IBM) shared library was incorrect.  

   (NetBackup Clients:  HP Linux2.4 RS6000_433 Solaris )


=============  
NB_DB2_50_3_M
=============  
Description:  
   The DB2 configuration script, db2_config.sh, fails on 64-bit HP-UX and  
   32-bit database.  

Workaround:  
   To avoid this issue, manually create the following link for the 32-bit  
   database instance.
   
   Link <DB2_INSTANCE_HOME>/sqllib/adm/db2uext2  
   to /usr/openv/netbackup/bin/db2uext2  

   (NetBackup Clients:  HP )
--------------------------------------------------------------------------------
Description:  
   On AIX, a scheduled backup of the DB2 template fails.  The actual backup is
   successful but AFTER the backup and just before exiting, the process
   (bpdbsbdb2) core dumps.  

Workaround:  
   For a scheduled backup/restore, convert the template into a script using  
   the following command.
   
   "/usr/openv/netbackup/bin/bpdbsbdb2 -g <script_name> -t <template_name>"
   
   Next, add the script to the file list of the DB2 policy.  

   All NetBackup Windows Clients HP Linux2.4 RS6000_433 Solaris  
================================================================================