ORA 5.0GA Pack NB_ORA_50_7_M README OEBU 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 updates and fixes for Veritas NetBackup (tm) for
Oracle Database Agent.
================================================================================


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

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

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


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

Pack History
NB_ORA_50_6_M
NB_ORA_50_5_M
NB_ORA_50_4_M
NB_ORA_50_3_M
NB_ORA_50_2_M
NB_ORA_50_1_M


=========================
I. DOWNLOAD INSTRUCTIONS
=========================
1) Download NB_ORA_50_7_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, rs6000_433,
rs6000_51, sgi65, solaris7

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

This will create the files:
Vrts_pack.install
VrtsNB_ORA_50_7_M.README
VrtsNB_ORA_50_7_M.OEBU.<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:

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 http://support.veritas.com/docs/233482 .



============================
IV. 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.



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

Description:
Oracle backups of multiple instances on the same client no longer fail
with a status 6.
--------------------------------------------------------------------------------
Etrack Incident = ET521975
Associated Primary Etracks = ET799835

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

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

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

Status 156: snapshot error encountered.
--------------------------------------------------------------------------------
Etrack Incident = ET588740
Associated Primary Etracks = ET799820

Description:
Oracle backups that used Advanced Methods sporadically failed because
a SIGCHLD event could interfere with Oracle's signal handling.
--------------------------------------------------------------------------------
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

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_ORA_50_6_M
=============
Etrack Incident = ET363230

Description:
Oracle backups fail when a leading slash "/" is used in the format string.
--------------------------------------------------------------------------------
Etrack Incident = ET333277 ET333168

Description:
NetBackup for Oracle is not compatible with the RMAN "BACKUP BACKUPSET"
command. In addition, the Controlfile autobackup fails trying to verify
the image.
--------------------------------------------------------------------------------
Etrack Incident = ET343590

Description:
The Oracle database is no longer corrupted after a backup.
--------------------------------------------------------------------------------
Etrack Incident = ET371655

Description:
Oracle RMAN backup on an HP-UX system periodically failed with a license
check error "status 36" and a socket read error "status 23".

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

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

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

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

Description:
Unable to restore Encrypted Oracle images onto an alternate Oracle client.
--------------------------------------------------------------------------------
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 = ET410924

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

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

Description:
Oracle backup failed because bphdb.exe would quit with an Application
Error.


--------------------------------------------------------------------------------
Etrack Incident = ET414649

Description:
Oracle backup failed because bphdb.exe would quit with an Application
Error.

This problem could be encountered when using the following agents :
- ORACLE
- SAP
- SYBASE
- DB2
- BACKTRACK
================================================================================



=============
NB_ORA_50_5_M
=============
================================================================================
Etrack Incident = ET276090

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

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

Description:
Oracle restore failed with the following status after upgrading to
NetBackup 5.0 MP4:

app_ObjectOwner does not match: Oracle (6) vs (0)

(NetBackup Clients: ALPHA HP Linux2.4 RS6000_433 RS6000_51 SGI Solaris )
--------------------------------------------------------------------------------
Etrack Incident = ET287965

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

(NetBackup Clients: ALPHA HP Linux2.4 RS6000_433 SGI Solaris )
--------------------------------------------------------------------------------
Etrack Incident = ET161550

Description:
Oracle backups would fail when running concurrent RMAN jobs.


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



=============
NB_ORA_50_4_M
=============
Description:
A potential memory leak was encountered and fixed in the Oracle BLI code.

(NetBackup Clients: ALPHA HP Linux2.4 RS6000_433 RS6000_51 SGI Solaris )
--------------------------------------------------------------------------------
Description:
Untranslated error messages were discovered and corrected on the Oracle
agent user interface.

All NetBackup Windows Clients ALPHA HP Linux2.4 RS6000_433 Solaris
--------------------------------------------------------------------------------
Description:
In the localized verison of Oracle, the text, "WHOLE DATABASE", was
hardcoded. This has been fixed.


All NetBackup Windows Clients ALPHA HP Linux2.4 RS6000_433 SGI Solaris
--------------------------------------------------------------------------------
Description:
An Oracle autobackup of the control file is very slow because of the format
of the piece name.

(NetBackup Clients: HP Intel-NT Linux2.4 RS6000_433 RS6000_51 SGI Solaris )



=============
NB_ORA_50_3_M
=============

================================================================================
Description:
When running some of the client commands on an Irix 6.5.22m system, they
may core dump. This is a known problem for SGI and to workaround the
client binaries must be linked with -lC.

(NetBackup Clients: SGI65 )
--------------------------------------------------------------------------------
Description:
A memory fault occurred when running a user-initiated Oracle template
backup in a Japanese localized environment.

This problem is limited to Japanese localized environments.
It can happen when running a User Directed Oracle template backup. User
Directed Oracle backup is initiated in few different ways:
1.Using Oracle Wizard ? Go through wizard options and run template.
2.Using Administrator Templates option in the Actions Menu of the NetBackup
Client GUI ? Select a template and run it.
3.Running Oracle template from the command line using bpdbsbora

The name of the executable file that creates the memory fault is bpdbsbora.
Logs for this executable are located at,
/usr/openv/netbackup/logs/bpdbsbora/log.<date>

In case this problem occurs, the last couple of lines in bpdbsbora log
should look similar to:

17:44:50.593 [16702] <4> VxBSAGetPolicyInfo: INF - request string: <rue
am_ora NONE>
17:44:50.850 [16702] <4> VxBSAGetPolicyInfo: INF - Policy Info:STD

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


=============
NB_ORA_50_2_M
=============
Description:
Memory Fault When Running User Initiated Oracle Template Backups In
Japanese Localized Environment

This problem is limited to Japanese localized environments.
It can happen when running a User Directed Oracle template backup. A User
Directed Oracle backup is initiated in a few different ways:
1.Using the Oracle Wizard ? Go through the wizard options and run template.
2.Using the Administer Database Templates option in the Actions Menu in the
Backup, Archive, and Restore interface ? Select a template and run it.
3.Running the Oracle template from the command line using bpdbsbora

The name of the executable file that creates the memory fault is bpdbsbora.
Logs for this executable are located at:
/usr/openv/netbackup/logs/bpdbsbora/log.<date>

If this problem occurs, the last few of lines in bpdbsbora log should
look similar to the following:

17:44:50.593 [16702] <4> VxBSAGetPolicyInfo: INF - request string: <rue
am_ora NONE>
17:44:50.850 [16702] <4> VxBSAGetPolicyInfo: INF - Policy Info:STD

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


=============
NB_ORA_50_1_M
=============
Description:
The number of parallel streams specified in an Oracle RMAN template that is
built using the Oracle RMAN Backup Wizard will be used for Archived Redo
Log backups in addition to Tablespace and Datafile backups. Previously,
only one stream was used for Archived Redo Log backups even if a greater
number of streams was specified in the template.

All NetBackup Windows Clients ALPHA HP Linux2.4 RS6000_433 SGI Solaris
--------------------------------------------------------------------------------
Description:
Oracle Template backup initiated from the master server fails because the
Oracle user cannot read the RMAN CMDFILE created by the ROOT user during
the
bpdbsbora execution.


All NetBackup Windows Clients ALPHA HP Linux2.4 RS6000_433 SGI Solaris
--------------------------------------------------------------------------------
Description:
Individual Oracle Datafiles or Tablespaces do not appear, although the
entire
database can be selected and backed up/restored successfully.

All NetBackup Windows Clients ALPHA HP Linux2.4 RS6000_433 Solaris
--------------------------------------------------------------------------------
Description:
The oracle_link script does not support Oracle 10G.

Workaround:
Set up the link to libobk manually, as follows:

- Login into the Oracle user account
- Move Oracle libobk to a save location:
mv -f lib/libobk.?? lib/libobk.??.save
- Link libobk to NetBackup's libobk
ln -s /usr/openv/netbackup/bin/libobk.?? lib/libobk.??

Note: ?? depends on the platform type. For example, on Solaris the suffix
is "so."

(NetBackup Clients: ALPHA HP Linux2.4 RS6000_433 RS6000_51 SGI Solaris )
--------------------------------------------------------------------------------
Description:
RMAN scripts containing more than one BACKUP command will fail if they
contain a SEND command to reset the NBU server using the NBU_ORA_SERV
environment variable after the first BACKUP and the NBU server change is
applied to the previously allocated channel. The
dbclient debug log contains the error message: "The license for the
requested feature is not available". The problem occurs because the SEND
command can potentially change the NBU server that was used to perform the
first BACKUP, and the license is not being rechecked.

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