Feature Pack NB_ORA_45_9_F.hp11.00.tar provides updates and fixes for VERITAS NetBackup (tm) for Oracle Database Agent on HP-UX 11.00 platforms.

Article:TECH44149  |  Created: 2005-01-04  |  Updated: 2013-10-23  |  Article URL http://www.symantec.com/docs/TECH44149
Article Type
Technical Solution

Product(s)

Environment

Issue



Feature Pack NB_ORA_45_9_F.hp11.00.tar provides updates and fixes for VERITAS NetBackup (tm) for Oracle Database Agent on HP-UX 11.00 platforms.

Solution



ORA 4.5FP_6 Pack NB_ORA_45_9_F README OEBU Ocotber 4, 2005
================================================================================
This Feature Pack provides updates and fixes for VERITAS NetBackup (tm) for
Oracle Database Agent.

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



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

-- 4.5 FP6 must be installed prior to installing this Feature Pack.

-- Installation of this Feature Pack requires version 1.8.2.25 of the
Vrts_pack.install.

-- NB_CLT_45_9_F and NB_45_9_F (UNIX Server) must be installed prior
to installing this Feature Pack.


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

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

where <6 digit number> is an internal tracking identifier

where <platform> is: alpha, dg_ux, hp11.00, hp11.11, linux2.2,
rs6000_433, rs6000_51, sgi65, solaris2.6

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

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


==============================
II. INSTALLATION INSTRUCTIONS
==============================
There are two ways to install database agent Feature 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:

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

As root on the NetBackup Master server:

2. Install the Feature 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. 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:

a. Log in as the Oracle user on the client and copy the library to
the LIBOBK_LOCATION.

If LIBOBK_LOCATION is not the same as /usr/openv/netbackup/bin

cp /usr/openv/netbackup/bin/libobk.[so,sl] ${LIBOBK_LOCATION}

cp /usr/openv/netbackup/bin/oracle_link ${LIBOBK_LOCATION}

b. Make the library visible to Oracle.

For RMAN:
Verify that the Oracle library is a link to the LIBOBK_LOCATION
library. If it is not, create a link:

ln -s ${LIBOBK_LOCATION}/libobk.[a,so,sl,so.1,so64,so64.1,sl64,a64] \
${ORACLE_HOME}/lib/libobk.[a,so,sl,so.1]

where LIBOBK_LOCATION is the pathname of the existing
NetBackup for Oracle library. LIBOBK_LOCATION is typically
/usr/openv/netbackup/bin.

c. Restart any Oracle instances.

----

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.(Required)

As root on the NetBackup for Oracle client:

2. Install the Feature 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. Execute the Oracle install script.

/usr/openv/netbackup/bin/install_oracle

4. Copy the library to the LIBOBK_LOCATION.

If LIBOBK_LOCATION is not the same as /usr/openv/netbackup/bin

cp /usr/openv/netbackup/bin/libobk.[so,sl] ${LIBOBK_LOCATION}

cp /usr/openv/netbackup/bin/oracle_link ${LIBOBK_LOCATION}

5. Make the library visible to Oracle.

For RMAN:
Verify that the Oracle library is a link to the LIBOBK_LOCATION library.
If it is not, create a link:

ln -s ${LIBOBK_LOCATION}/libobk.[a,so,sl,so.1,so64,so64.1,sl64,a64] \
${ORACLE_HOME}/lib/libobk.[a,so,sl,so.1]

where LIBOBK_LOCATION is the pathname of the existing
NetBackup for Oracle library. LIBOBK_LOCATION is typically
/usr/openv/netbackup/bin.

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

For help linking the NetBackup for Oracle library, 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 pack 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 or feature contained in this Feature 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
=============

================================================================================
Description:
Using Red Hat 3.0 ES, when an Oracle template is created using the Oracle
template wizard of the client GUI, the following warning message appears at
the beginning of the template summary: "Incorrectly built binary which
accesses errno or h_errno directly. Needs to be fixed."

(NetBackup Clients: Alpha Dgux HP Linux2.2 NCR RS6000_433 RS6000_51
Sequent4.2 SGI SOLARIS Solaris )
--------------------------------------------------------------------------------
Description:
After a controlfile autobackup the image verification fails.(ORA-27206:
REQUESTED FILE NOT FOUND IN MEDIA MANAGEMENT CATALOG)

Workaround:
To avoid this issue, add the touch file, USEDEFAULTDATERANGE to
/usr/openv/netbackup on UNIX or VERITAS\NetBackup on Windows.

(NetBackup Clients: HP Intel-NT Linux2.2 NCR RS6000_433 RS6000_51
Sequent4.2 SGI SOLARIS Solaris )
--------------------------------------------------------------------------------
Description:
Oracle production database gets corrupted after backup.

(NetBackup Clients: Dgux HP Linux2.4 RS6000_433 RS6000_51 Sequent4.2
SGI SOLARIS Solaris Solaris9 )
--------------------------------------------------------------------------------
Description:
After upgrade of file system from 3.5 to 4.0 Oracle Proxy incrementals do
not work.

(NetBackup Clients: SOLARIS Solaris )
================================================================================

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

(NetBackup Clients: Dgux HP Intel-NT Linux2.2 NCR RS6000_433
RS6000_51 Sequent4.2 SGI SOLARIS Solaris )



=============
NB_ORA_45_7_F
=============
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 Dgux HP Linux2.4 RS6000_433
SGI SOLARIS)
--------------------------------------------------------------------------------
Description:
On Japanese operating systems, the Oracle error message does not print
correctly.

(NetBackup Clients: Alpha HP Intel-NT Linux2.2 RS6000_433 RS6000_51
Sequent4.2 SGI SOLARIS Solaris )
--------------------------------------------------------------------------------
Description:
Oracle template execution has been modified so that the temporary files
used by the rman and sqlplus command line programs are owned by the user
executing the template. Because the temporary files may contain username
and password information, permissions on the files are set so only the
owner has read/write capabilities.

(NetBackup Clients: Alpha Dgux HP Linux2.2 RS6000_433 SGI SOLARIS )
--------------------------------------------------------------------------------
Description:
Add support for Oracle 10g.

(All NetBackup Windows Clients Alpha HP Linux2.2 RS6000_433 SOLARIS)
--------------------------------------------------------------------------------
Description:
Oracle 10G is not supported with the oracle_link scripts. The NetBackup for
Oracle installation will fail stating that Oracle 10G is not supported.

Workaround:
Oracle 10G can be supported if the link to libobk is configured manually.
To configure libobk do the following:
- 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 Solaris)
--------------------------------------------------------------------------------
Description:
This problem only occurs when using RMAN Proxy with BLI or any other
Frozen Image method. The backup will fail because a backup ID can
not be found by RMAN. This error occurs on databases that contain a large
number of data files. A database that has a 1000 or more data files may
encounter this problem. The following error is reported in the dbclient
logs.

<4> sbtinfo2: Image Information for file <bk_80_128_515425193> :
<16> sbtinfo2: bk_80_128_515425193 NOT found
<8> sbtpcend: terminating all outstanding backups
<4> terminateFsBackup: terminating all running backups
<4> terminateFsBackup: terminating pid <13453>

(NetBackup Clients: HP RS6000_433 RS6000_51 SOLARIS Solaris )
--------------------------------------------------------------------------------
Description:
By design, Oracle ServerFree agent creates a separate backup job for each
file system or raw device. If there is a large number of file systems or
raw volumes, then there will be a large number of backups. Some customers
have experienced problems on their systems because of a large number of
backups running at the same time. Now users can change the default behavior
by setting NB_ORA_PC_FILESYSTEMS variable to 0. In this case, the agent
will bypass the default behavior of initiating a separate job for each file
system or raw volume. The files will be divided into the streams based on
the value of the NB_ORA_PC_STREAMS variable and the file size.

(NetBackup Clients: HP SOLARIS Solaris )
================================================================================


Attachments

NB_ORA_45_9_F_279444.hp11.00.tar (2.2 MBytes)


Legacy ID



279444


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


Terms of use for this information are found in Legal Notices