Document ID: 280780
http://support.veritas.com/docs/280780
E-Mail this document to a colleague
http://support.veritas.com/docs/280780
E-Mail this document to a colleague
Maintenance Pack NB_DB2_50_6_M.hp11.00.tar provides fixes to VERITAS NetBackup (tm) 5.0 for DB2 Database Agent on HP-UX platforms.
Details:
THIS FILE HAS BEEN UPDATED! PLEASE CLICK HERE TO GET THE LATEST VERSION OF THE FILE
DB2 5.0GA Pack NB_DB2_50_6_M README DB2 November 29, 2005
Requirement: NB_CLT_50_6_M
================================================================================
This Maintenance Pack provides fixes to NetBackup (tm) for DB2 Database Agent.
=================
PACK DEPENDENCIES
=================
-- Installation of this Maintenance Pack requires version 1.17.4.34 of
the Vrts_pack.install script.
-- NB_CLT_50_6_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. INSTALLATION INSTRUCTIONS
III UNINSTALL INSTRUCTIONS
IV. DESCRIPTION OF PROBLEMS FIXED
Current Pack
NB_DB2_50_5_M
NB_DB2_50_4_M
NB_DB2_50_3_M
=========================
I. DOWNLOAD INSTRUCTIONS
=========================
1) Download NB_DB2_50_6_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_6_M_<6 digit number>.<platform>.tar
/bin/tar xvf NB_DB2_50_6_M_<6 digit number>.<platform>.tar
This will create the files
Vrts_pack.install
VrtsNB_DB2_50_6_M.README
VrtsNB_DB2_50_6_M.<platform>.tar.Z
==============================
II. 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.
============================
III. 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.
==================================
IV. 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 Maintenance 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 the "best practice" of being at the latest patch level.
Additional Notes
Any additional information regarding this problem or feature is included.
=============
Current pack
=============
================================================================================
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>\LOTUS_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
================================================================================
THIS FILE HAS BEEN UPDATED! PLEASE CLICK HERE TO GET THE LATEST VERSION OF THE FILE
Download Now
Click Below to Browse the FTP files by Product:
ftp.support.veritas.com/pub/support/products
THIS FILE HAS BEEN UPDATED! PLEASE CLICK HERE TO GET THE LATEST VERSION OF THE FILE
DB2 5.0GA Pack NB_DB2_50_6_M README DB2 November 29, 2005
Requirement: NB_CLT_50_6_M
================================================================================
This Maintenance Pack provides fixes to NetBackup (tm) for DB2 Database Agent.
=================
PACK DEPENDENCIES
=================
-- Installation of this Maintenance Pack requires version 1.17.4.34 of
the Vrts_pack.install script.
-- NB_CLT_50_6_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. INSTALLATION INSTRUCTIONS
III UNINSTALL INSTRUCTIONS
IV. DESCRIPTION OF PROBLEMS FIXED
Current Pack
NB_DB2_50_5_M
NB_DB2_50_4_M
NB_DB2_50_3_M
=========================
I. DOWNLOAD INSTRUCTIONS
=========================
1) Download NB_DB2_50_6_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_6_M_<6 digit number>.<platform>.tar
/bin/tar xvf NB_DB2_50_6_M_<6 digit number>.<platform>.tar
This will create the files
Vrts_pack.install
VrtsNB_DB2_50_6_M.README
VrtsNB_DB2_50_6_M.<platform>.tar.Z
==============================
II. 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.
============================
III. 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.
==================================
IV. 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 Maintenance 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 the "best practice" of being at the latest patch level.
Additional Notes
Any additional information regarding this problem or feature is included.
=============
Current pack
=============
================================================================================
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>\LOTUS_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
================================================================================
THIS FILE HAS BEEN UPDATED! PLEASE CLICK HERE TO GET THE LATEST VERSION OF THE FILE
Download Now
Click Below to Browse the FTP files by Product:
ftp.support.veritas.com/pub/support/products
Products Applied:
NetBackup Enterprise Server 5.0, 5.0 MP6
NetBackup Server 5.0, 5.0 MP6
NetBackup Enterprise Server 5.0, 5.0 MP6
NetBackup Server 5.0, 5.0 MP6
Last Updated: December 06 2005 11:45 PM GMT
Expires on: 12-04-2015
Subscribe to receive critical updates about this document
Expires on: 12-04-2015
Subscribe to receive critical updates about this document
Subjects:
NetBackup Enterprise Server
Application: Patch
NetBackup Server
Application: Patch
NetBackup Enterprise Server
Application: Patch
NetBackup Server
Application: Patch
Languages:
English (US)
English (US)
Operating Systems:
HP-UX
HP-UX
11.0, 11.11
Symantec World Headquarters:
20330 Stevens Creek Blvd. Cupertino, CA 95014
World Wide Web: http://www.symantec.com,
Tech Support Web: http://entsupport.symantec.com,
E-Mail Support: http://seer.entsupport.symantec.com/email_forms,
FTP: ftp://ftp.entsupport.symantec.com or http://ftp.entsupport.symantec.com
20330 Stevens Creek Blvd. Cupertino, CA 95014
World Wide Web: http://www.symantec.com,
Tech Support Web: http://entsupport.symantec.com,
E-Mail Support: http://seer.entsupport.symantec.com/email_forms,
FTP: ftp://ftp.entsupport.symantec.com or http://ftp.entsupport.symantec.com
THE INFORMATION PROVIDED IN THE SYMANTEC SOFTWARE KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. SYMANTEC SOFTWARE DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL SYMANTEC SOFTWARE OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES,EVEN IF SYMANTEC SOFTWARE OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.