SAP 5.1GA Pack NB_SAP_51_6_M README SAP December 5, 2006
Requirement: NB_CLT_51_6_M
================================================================================
** All 5.1 MP6 Maintenance Packs for NetBackup server, client, all Add-on
products, Database Agents, and Java user interface must be applied so that the
entire system is at the same Maintenance Pack level. **

This pack provides fixes for Veritas NetBackup (tm) for SAP Database Agent.
================================================================================


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

-- Installation of this pack requires version 1.19.4.36 of
the Vrts_pack.install.

-- NB_CLT_51_6_M must be installed prior to installing this pack.


I. DOWNLOAD INSTRUCTIONS
II. INSTALLATION INSTRUCTIONS
III. UNINSTALL INSTRUCTIONS
IV. DESCRIPTION OF PROBLEMS FIXED
Current Pack
NB_SAP_51_6_M

Pack History
NB_SAP_51_5_M
NB_SAP_51_3_M
NB_SAP_51_2_M
NB_SAP_51_1_M



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

where <6 digit number> is an internal tracking identifier

where <platform> is alpha_5, hp11.00, hpia64, linux2.4,linux64,
rs6000_433, rs6000_51, solaris7

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

This will create the files:
VrtsNB_SAP_51_6_M.README
VrtsNB_SAP_51_6_M.postinstall
VrtsNB_SAP_51_6_M.postuninstall
VrtsNB_SAP_51_6_M.SAP.<platform>.tar.Z
Vrts_pack.install



==============================
II. INSTALLATION INSTRUCTIONS
==============================
There are two ways to install database agent 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 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 to the affected database agent
clients. For more information on how to run update_dbclients, refer to
the NetBackup for SAP System Administrator's Guide.

----

Local Installation:

As root on the NetBackup for SAP client:

1) Install 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.



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

If a database agent is being used, such as SAP,
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 particular problem or feature 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 in this pack.


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

================================================================================
Etrack Incident = ET587366 ET589785 ET589788 ET589795 ET589791 ET589812 ET589780
ET589824 ET589797 ET589823 ET589778 ET589817 ET589786 ET603075 ET589813 ET589815
ET589805 ET605165 ET589800 ET589801 ET589799 ET589806 ET589774 ET605272 ET589807
ET589792 ET606821 ET589967 ET610322 ET608197 ET608193 ET589808 ET589810 ET589804
ET589781 ET608877 ET589818 ET611400 ET612012 ET612415 ET614013 ET614671 ET615007
ET617838 ET589775 ET618608 ET622226 ET620433 ET625390 ET633298 ET641184 ET645740
ET699937 ET634033 ET701955 ET781199 ET589809 ET837196 ET589821 ET787039 ET802665
ET814643

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_SAP_51_5_M
=============
Etrack Incident = ET526476

Description:
Added support for the SAP database agent on Windows AMD64 (x64) platforms.
--------------------------------------------------------------------------------
Etrack Incident = ET538177 ET538162 ET537511 ET537528 ET537537 ET537474 ET537520
ET537557 ET537414 ET542504

** Description:
Multiple buffer overflow vulnerabilities have been identified in daemons
that run on Veritas NetBackup master, media, and client servers. An
attacker, if able to access a vulnerable Veritas NetBackup server and
successfully exploit these issues, could potentially execute arbitrary
code resulting in possible unauthorized and elevated privilege access to
the targeted system.

For more information about this vulnerability, refer to TechNote 281521 on
the Symantec Support Web site (http://support.veritas.com/docs/281521 ).
--------------------------------------------------------------------------------
Etrack Incident = ET582327

Description:
This pack contains a fix that prevents a potential segmentation fault that
could occur during Windows SAP backups.
================================================================================



=============
NB_SAP_51_3_M
=============
Etrack Incident = ET312426

Description:
A problem existed with the LARGEFILES option for Linux. By creating
a file larger than 2GB (for example, 2301473760) and then trying to back
it up using backint, backint would fail with following error.

ERROR: unable to find file /home/sudhakar/large_files/file_1

(NetBackup Clients: Linux2.4 )
================================================================================


=============
NB_SAP_51_2_M
=============
Etrack Incident = ET223772

Description:
A dual-stream backup starts only one backup for each redo log group after
the first redo log group is backed up correctly (two backups).

This problem occurred in following configuration:
1. BRARCHIVE was called with an -f option.
2. The SAP Agent configuration file (init<SID>.utl) contained the
sched_log parameter.

The sched_log parameter is the value of the second schedule that SAP Agent
can use to backup archive logs. When this parameter is enabled two backup
of archive logs will be performed. This enables backing up same archive
logs to different media.

This parameter is processed correctly by the SAP Agent when BRARCHIVE is
called without -f option. However, when BRARCHIVE is called with a -f
option, only the first group of archive logs are backed up to both
schedules. Any subsequent group of archive logs are backed up to only one
(original) schedule.

(NetBackup Clients: ALPHA HP HPIA64 Intel-NT Intel64 Linux2.4 Linux64
RS6000_433 RS6000_51 Solaris )
================================================================================




=============
NB_SAP_51_1_M
=============
Etrack Incident = ET212072

Description:
The SAP Alternate Client restore no longer fails.

First, this problem occurred intermittently because the SAP Agent is unable
to read output file of restore_filter script. This failure would produce a
log similar to the following:

"14:30:00.381 [7082] <16> backint_restore_filter: cannot open restore
working file:
/oracle/BD1/sapbackup/backint_dir/.backint.filter.1085772595.7082
14:30:00.381 [7082] <16> backint_do_restore: ERROR: running restore filter"

Second, the restore_filter script was unable to handle a use case where the
source client (backed-up client) did not have soft links to the actual file
paths of the SAP data files. During a restore on target client (new
destination client), the agent would think that it should not adjust the
file paths to match the originally backed-up paths. The output of this
problem looked similar to the following:
"**************************************************************************
Program: ./backint 5.0GA
Input File: ./in_re
Profile: ./initSAP.utl
Function: RESTORE
****************************************************************************
#NOTFOUND <input file name>
***************************************************************************"

In the backint log, the output looked like the following:

"10:56:07.093 [2838] <2> backint_find_master_time: exit status = 2
10:56:07.094 [2838] <4> backint_do_restore: #NOTFOUND /tmp/bd1/file1"

(NetBackup Clients: ALPHA HP HPIA64 Intel-NT Intel64 Linux2.4 Linux64
RS6000_433 RS6000_51 Solaris )
--------------------------------------------------------------------------------
Etrack Incident = ET212099

Description:
The SAP DB Environment Agent reports a success despite an actual failure
occurring.

This problem does not occur when using the SAP Agent in a SAP environment
using an Oracle database. This problem only occurs when agent is called in
a SAP DB environment with an adapter program. The problem will occur if
there were previously successful backups and the current backup fails.

When this problem happens the log will look similar to the following:
"
...
08:16:49.143 [1433628] <16> backint_system: ERROR: executing
command /usr/openv/netbackup/bin/bpbackup -w -t 17 -h pollux_bk -S
frsux071 -c ASV_SAP_A30_online -s Default-Policy -
L /usr/openv/netbackup/logs/user_ops/sap/.backint.log.0.1083392186.1282186 -
08:16:51.208 [1282186] <16> dbc_Wait: ERR - job (1433628) failed status (71)
...
08:16:52.853 [1282186] <4> backint_do_backup: #SAVED
NS1083106428 /home/adasav/A10/NB_puffer1/STAGE3.0
08:16:52.853 [1282186] <4> backint_do_backup: #SAVED
NS1083364604 /home/adasav/A10/NB_puffer1/STAGE1.0"

The above log shows that the backup command failed, but the agent reported
input files were saved. This is because the agent saved these files in a
previous backup. This may lead user to conclude that the backup of SAP on
a SAP DB was successful when it actually failed. Again, this is not a
problem for SAP on Oracle.

(NetBackup Clients: ALPHA HP HPIA64 Intel-NT Intel64 Linux2.4 Linux64
RS6000_433 RS6000_51 Solaris )
--------------------------------------------------------------------------------
Etrack Incident = ET213234

Description:
The command, backint -p <utl file> -f inquire, may fail when it is called
without the input file list. This caused the SAP Agent to fail.
When user runs this command, the reported error looks similar to:
"ERROR: couldn't open file: <file name>"

The SAP BR-tools do not fail with this error because they always provide
input file list.

Workaround:
To avoid this issue, call "backint -p <utl file> -f inquire -i <file_name>".

(NetBackup Clients: ALPHA HP HPIA64 Intel-NT Intel64 Linux2.4 Linux64
RS6000_433 RS6000_51 Solaris )
================================================================================