ORA 5.1GA Pack NB_ORA_51_5_M README OEBU April 25, 2006
Requirement: NB_CLT_51_5_M
================================================================================
This Maintenance Pack provides updates and fixes for Veritas NetBackup(tm) for
Oracle Database Agent.

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


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

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

-- NB_CLT_51_5_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_ORA_51_5_M

Pack History
NB_ORA_51_4_M
NB_ORA_51_3_M
NB_ORA_51_2_M
NB_ORA_51_1_M


=========================
I. DOWNLOAD INSTRUCTIONS
=========================
1) Download NB_ORA_51_5_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, hp11.11, linux2.4, linux64
rs6000_433, rs6000_51, sgi65, solaris7

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

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


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

NOTE: Click on the "Download Now" link, near the bottom of this document
prior to running the following installation procedure 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:

Warning: Before installation - If production rman scripts are found in
the /usr/openv/netbackup/ext/db_ext/oracle/samples/rman, please save them
in another location to prevent them from being overwritten.

1. Log in as the Oracle user on the clients to receive the pack software
and shut down all Oracle instances. (Recommended)

Login as root on the NetBackup Master server:

2. Install the Maintenance Pack binaries.

cd /tmp
/bin/sh Vrts_pack.install

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

3. Run update_dbclients to push pack software affected database agent clients:
/cd <install_path>/netbackup/bin
./update_dbclients Oracle ALL ALL

This command will look at all possible clients and only update and only
update the ones currently in Oracle policy type. For more information on
how to run update_dbclients, refer to the NetBackup for Oracle System
Administrator's Guide.

4. For every client to which you pushed the pack software in step 3, the
following steps must be performed:

4.1 Verify that Oracle Agent library is located in /usr/openv/netbackup/bin
directory.

4.2 Verify that library is visible to Oracle.
If $ORACLE_HOME/lib[32,64]/libobk.<platform extension> is a soft link to
/usr/openv/netbackup/bin/libobk.<platform extension>
then library is visible to Oracle.

Perform step 4.3 only if library is not visible to Oracle.

4.3 Make the library visible to Oracle
Run /usr/openv/netbackup/bin/oracle_link script OR Perform manual linking.

For more information on how to manually link the library,
refer to Oracle System Administrator Guide.

4.4 Restart any Oracle instances. (Recommended)

----

Local Installation:

Warning: Before installation - If production rman scripts are found in
the /usr/openv/netbackup/ext/db_ext/oracle/samples/rman, please save them
in another location to prevent them from being overwritten.

1. Log in as the Oracle user and shut down all Oracle instances. (Recommended)

As root on the NetBackup for Oracle client:

2. Install the 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 the updated NetBackup files for the Oracle library
in /usr/openv/netbackup/bin.

3. Verify that Oracle Agent library is located in
/usr/openv/netbackup/bin directory.

4. Verify that library is visible to Oracle.
If $ORACLE_HOME/lib[32,64]/libobk.<platform extension> is a soft link to
/usr/openv/netbackup/bin/libobk.<platform extension> then library is
visible to Oracle.

Perform step 5 only if library is not visible to Oracle.

5. Make the library visible to Oracle
Run /usr/openv/netbackup/bin/oracle_link script OR
Perform manual linking.

For more information on how to manually link the library, refer to Oracle
System Administrator Guide.


6. Log in as the Oracle user and restart any Oracle instances. (Recommended.)

For help linking the NetBackup for Oracle library, you can also refer to the
support TechNote 233482, available on www.support.veritas.com.



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

If a database agent is being used, such as Oracle,
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 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 a problem is included.

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

================================================================================
Etrack Incident = ET521680

Description:
Oracle backups of multiple instances on the same client no longer fail
with a status 6.
--------------------------------------------------------------------------------
Etrack Incident = ET525108

Description:
The Oracle agent no longer ignores BPBACKUP_SCHED in the bp.conf file on
the client system.
--------------------------------------------------------------------------------
Etrack Incident = ET525795

Description:
A change has been made to prevent a potential segmentation fault that
would occur on Windows while performing multi-stream, Oracle backups.
--------------------------------------------------------------------------------
Etrack Incident = ET527988

Description:
Added error detection for Oracle restores that would fail because of
corruption.
--------------------------------------------------------------------------------
Etrack Incident = ET521974

Description:
Oracle users can now perform XML exports and imports on tables that
contain timestamp and interval data types.
--------------------------------------------------------------------------------
Etrack Incident = ET530196

Description:
A change was made to prevent a segmentation fault on Windows that would
occur when using the Backup Archive and Restore (BAR) user interface to
access multiple Oracle instances.
--------------------------------------------------------------------------------
Etrack Incident = ET525214

Description:
Oracle proxy backups using multiple Recovery Manager (RMAN) channels no
longer fail with the following error:

Status 156: snapshot error encountered.
--------------------------------------------------------------------------------
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 ).
================================================================================

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

=============
NB_ORA_51_4_M
=============
Etrack Incident = ET333137

Description:
Oracle backups fail when a leading ?/? is used in the format sting.
For example, FORMAT '/bk_%s_%p_%t'. The backup finishes with a status 0,
however the overall job fails with an error 6. If you remove the ?/? the
problem does not occur.
--------------------------------------------------------------------------------
Etrack Incident = ET371654

Description:
Oracle rman backup on an HP system periodically fails with a license check
error "status 36" and a socket read error "status 23".

The following error message occurs:
ORA-19511: Error received from media manager layer, error
text:VxBSAValidateFeatureId: Failed with error:Server Status: socket read
failed.


--------------------------------------------------------------------------------
Etrack Incident = ET333681 ET333278

Description:
The Oracle agent does not support the RMAN command "BACKUP BACKUPSET",
causing control-file, auto-backups to fail during the verification of the
image that was cataloged.
--------------------------------------------------------------------------------
Etrack Incident = ET347549

Description:
Oracle backups were not using the value of BPBACKUP_SCHED from the bp.conf
file.
--------------------------------------------------------------------------------
Etrack Incident = ET343591

Description:
Oracle database would become corrupt during a backup.
--------------------------------------------------------------------------------
Etrack Incident = ET292569

Description:
RMAN - alternate client restore times out after a successful partial
restore by media server.

Though this problem was encountered while doing an Oracle alternate client
restore, the nature of the problem is such that it can happen for any
XBSA-based partial restore.

When the client is done restoring - partial restore - but there is still
data to be read, the client sockets are closed but bptm/bpdm wait for the
data to be read causing it to eventually time out with an error.
--------------------------------------------------------------------------------
Etrack Incident = ET406315

Description:
The newdataSock was not being closed before a backup was requeued. This led
to sockets remaining in the WAIT_CLOSE state on Windows after the backup
completed.
--------------------------------------------------------------------------------
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 = ET410883

Description:
Unable to restore Encrypted Oracle images onto an alternate Oracle client.
--------------------------------------------------------------------------------
Etrack Incident = ET410922

Description:
Oracle RMAN backups failed with intermittent ORA-27192 errors.

Even though the client has closed the socket, bptm does not recognize that
fact and eventually times out the client.
--------------------------------------------------------------------------------
Etrack Incident = ET416984

Description:
Variables being set by using the RMAN PARMS option were not being used by
the Oracle Agent.
================================================================================



=============
NB_ORA_51_3_M
=============
Etrack Incident = ET297819

Description:
The VxBSA global Handles[] and debugFD were not thread safe.

(NetBackup Clients: ALPHA HP Intel-NT Linux2.4 RS6000_51
SGI Solaris Solaris9 )
--------------------------------------------------------------------------------
Etrack Incident = ET300999

Description:
Oracle templates that were run at the same time on a remote system, would
likely overwrite one another on the client, causing one to fail.

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

Description:
Added Linux support for 64-bit AMD.

(NetBackup Clients: Linux2.4 Linux64 )
--------------------------------------------------------------------------------
Etrack Incident = ET284903

Description:
Support for Linux 64-bit.

(NetBackup Clients: Linux2.4 Linux64 )
--------------------------------------------------------------------------------
Etrack Incident = ET313409

Description:
Oracle shared-memory restores failed on the newly supported Linux 2.4,
64-bit platform.

(NetBackup Clients: Linux2.4 )
--------------------------------------------------------------------------------
Etrack Incident = ET284903

Description:
The Oracle Archiver fails to load required libraries on IA64 Linux.

(NetBackup Clients: Linux64 )



=============
NB_ORA_51_2_M
=============

Etrack Incident = ET258421 ET258293 ET261720 ET221167

Description:
When a database agent gets queued again, multiple times in a very short
period of time, there were cases where the server would time out waiting for
the client to connect. This fix prevents the client from getting behind the
server in these instances.

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

Description:
Oracle autobackup of a control file is very slow because of the format of
the piece name.

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

Description:
Added 64-bit Oracle support for Linux on the AMD64 and EM64T platforms.

(NetBackup Clients: Linux2.4 )
--------------------------------------------------------------------------------
Etrack Incident = ET283509

Description:
After upgrading to NetBackup 5.1 MP2, an Oracle restore would fail with the
following error message: app_ObjectOwner does not match: Oracle (6) vs. (0)

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




=============
NB_ORA_51_1_M
=============
Etrack Incident = ET206031

Description:
A memory leak encountered in XBSA library has been fixed.

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

Description:
Proxy block level incremental backups that have more than 2 streams may
fail.

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

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