Maintenance Pack NB_DB2_51_4_M.linux2.4.tar provides fixes to VERITAS NetBackup (tm) Enterprise Server / Server 5.1 for DB2 Database Agent on Linux platforms.

Article:TECH45037  |  Created: 2005-01-22  |  Updated: 2005-01-22  |  Article URL http://www.symantec.com/docs/TECH45037
Article Type
Technical Solution


Environment

Issue



Maintenance Pack NB_DB2_51_4_M.linux2.4.tar provides fixes to VERITAS NetBackup (tm) Enterprise Server / Server 5.1 for DB2 Database Agent on Linux platforms.

Solution



DB2 5.1GA Pack NB_DB2_51_4_M README DB2 November 21, 2005
Requirement: NB_CLT_51_4_M
================================================================================
This Maintenance Pack provides fixes to VERITAS NetBackup (tm) for DB2 Database
Agent.

================================================================================



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

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

-- NB_CLT_51_4_M should 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_51_3_M
NB_DB2_51_1_M


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

where <platform> is: hp11.00

where <6 digit number> is an internal tracking identifier

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

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


==============================
II. INSTALLATION INSTRUCTIONS
==============================

NOTE: Click on the "Download Now" link, near the bottom of this document
prior to running either of the following installation procedures for
this pack.

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 = ET379405

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

Description:
The backup of DB2 tablespaces would fail if the tablespace spanned
multiple directories.
--------------------------------------------------------------------------------
Etrack Incident = ET355418

Description:
The DB2 PFI-to-tape backups failed when executed from the template wizard.
When performing a DB2 proxy backup, the DB2 internal files were not being
enumerated.
--------------------------------------------------------------------------------
Etrack Incident = ET410877

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 = ET349778 ET320511 ET414804

Description:
Changes were made to allow DB2 restores between instances. In addition,
changes were made to allow the backup and the restore of DB2 log files
from a raw partition or device.
--------------------------------------------------------------------------------
Etrack Incident = ET323760

Description:
jbpSA was unable to enumerate DB2 instances on HP-UX 11.23, IA64 platforms.
--------------------------------------------------------------------------------
Etrack Incident = ET418273

Description:
The backup of DB2 logs without an associated entry in the db2.conf file
resulted in a good status being returned to DB2, however, the logs were
not backed up and were deleted from DB2.
--------------------------------------------------------------------------------
Etrack Incident = ET496110

Description:
The following error message would occur when performing a DB2 rollforward
after a restore.

For example:
$ db2 rollforward db sample to end of logs and stop
SQL1268N Roll-forward recovery stopped due to error "28" while retrieving
log file "S0000001.LOG" for database "SAMPLE" on node "0".
================================================================================

=============
NB_DB2_51_3_M
=============
Etrack Incident = ET292567

Description:
Added support for DB2 Stinger.

(All NetBackup Windows Clients HP HPIA64 Linux2.4 Linux64 RS6000_433
RS6000_51 Solaris)
--------------------------------------------------------------------------------
Etrack Incident = ET300349

Description:
The link script, db2_config, failed on Linux64.

Workaround:
The link for the DB2 user exit program can be made manually by entering
the following.

ln -s /usr/openv/netbackup/bin/db2uext2 $DB2_HOME_DIR/sqllib/adm/db2uext2

where DB2_HOME_DIR is the DB2 instance home path name.

(NetBackup Clients: Linux64 )
--------------------------------------------------------------------------------
Etrack Incident = ET300999

Description:
DB2 templates that were run at the same time on a remote system, would
overwrite one another on the client and cause one to fail

(NetBackup Clients: ALPHA HP HPIA64 Linux2.4 Linux64 RS6000_433 Solaris )
--------------------------------------------------------------------------------
Etrack Incident = ET304109

Description:
When doing a DB2 Proxy (Advance Client) backup, it was observed that on
some UNIX platforms/DB2 versions, DB2 does not archive the active log.
This may cause a problem as the resulting backup image may not be useful
in the event of the loss of an active log file.

Workaround:
To avoid this issue, explicitly backup an archive log after a successful
Proxy Backup.

(NetBackup Clients: HP HPIA64 RS6000_433 Solaris )
--------------------------------------------------------------------------------
Etrack Incident = ET316954

Description:
Add support for HPIA64 platform for DB2.

(NetBackup Clients: HPIA64 )



=============
NB_DB2_51_1_M
=============

Etrack Incident = ET211885 ET204900ET209071

Description:
DB2 advance client backup failed when another session established a
database connection. To avoid this issue, support was added for DB2 BLI.

(All NetBackup Windows Clients HP HPIA64 Linux2.4 Linux64 RS6000_433
RS6000_51 SGI Solaris)
--------------------------------------------------------------------------------
Etrack Incident = ET216511

Description:
A problem using a template with a DB2 scheduled backup has been resolved.

(All NetBackup Windows Clients HP HPIA64 Linux2.4 Linux64 RS6000_433
RS6000_51 Solaris)
--------------------------------------------------------------------------------
Etrack Incident = ET211834

Description:
DB2 block level incremental backups with more than 2 streams may fail.

Workaround:
Perform Proxy BLI backups with no more that 2 streams (1 is safest).

(NetBackup Clients: ALPHA HP HPIA64 Linux2.4 Linux64 RS6000_433 RS6000_51
SGI Solaris Solaris9 )
--------------------------------------------------------------------------------
Etrack Incident = ET217320

Description:
A DB2 Proxy restore was being attempted for an incomplete Proxy Backup. The
restore did not check for the availability of all the backup images before
attempting the restore. This caused some of the files to be restored whose
images were available and this left the database in an inconsistent state.

(All NetBackup Windows Clients HP HPIA64 Linux2.4 Linux64 RS6000_433 Solaris)
--------------------------------------------------------------------------------
Etrack Incident = ET218484 ET219090

Description:
ET 218484 : The NetBackup server from the user's configuration was ignored
when the DB2 policy was read. As a result, a backup started from a policy
residing on a server listed in the user's configuration would fail if the
same policy was not present on the server listed in the master's
configuration.

ET 219090 : Starting BLI Incremental backups from the scheduler using an
Advanced Client Backup (Proxy) script starts a full BLI backup.

Workaround:
ET218484 : Ensure that the required NetBackup server is configured in the
master's configuration (/usr/openv/netbackup/bp.conf).

ET219090 : The problem is encountered on a BLI scheduled backup using a
Proxy (Advance client) script. The workaround is to use a template instead
of a script.

(All NetBackup Windows Clients HP HPIA64 Linux2.4 Linux64 RS6000_433 Solaris)
--------------------------------------------------------------------------------
Etrack Incident = ET222556 ET222796

Description:
ET222556 : bpdb2proxy failed to perform the backup. The DB2 library cannot
be loaded.

ET222796 : Proxy Restore failed. Incorrect keyword used.

(All NetBackup Windows Clients HP HPIA64 Linux2.4 Linux64 RS6000_433 Solaris)
--------------------------------------------------------------------------------
Etrack Incident = ET233426

Description:
A DB2 Proxy shell script generated from a template fails when executed from
the command line. The same script runs when executed from the scheduler.

(All NetBackup Windows Clients HP HPIA64 Linux2.4 Linux64 RS6000_433 Solaris)
--------------------------------------------------------------------------------
Etrack Incident = ET234544

Description:
DB2 block level incremental cannot restore the database if a create table
is made during backup.

Workaround:
After creating a database table in the DB2 database, expire the existing
FULL BLI backups. This will cause the backup operation to:
1. Enforce a FULL backup.
2. All the files will be regrouped/distributed across the specified number
of sessions depending on their sizes.

(NetBackup Clients: HP HPIA64 Linux2.4 RS6000_433 RS6000_51 SGI Solaris)
================================================================================


Attachments

NB_DB2_51_4_M_280434.linux2.4.tar (1.2 MBytes)


Legacy ID



280434


Article URL http://www.symantec.com/docs/TECH45037


Terms of use for this information are found in Legal Notices