Date: Jan/2006
Affected NV Version: All
OS Version: All
Plugin version: Oracle
Application version:N/A
Description: RMAN isn't linking to library...
Linking Libraries in other UNIX-based O/S
Follow the procedures outlined in the section, Linking Libraries in Solaris (SPARC)-based O/S on page 48, based on the version of Oracle installed on the Oracle Database Server. However, when calling out the “orasbt.so” file for operations, its extension varies on the operating system installed:
Compaq Tru64: “orasbt.so” (the file name is the same, the process can be duplicated as is)
*HP-UX:
*“orasbt.sl” (for 32-bit versions of this O/S)
*“orasbt64” (for 64-bit versions of this O/S)
IBM AIX: “orasbt.a”
Important:
1. This extension differentiation only applies when calling out the file from the O/S for linking to the NetVault version of this file. When instructed to establish the link with the command,
“ln -s /usr/netvault/lib/orasbt.so orasbt.so”, only the first instance of the orasbt.so file would need to be modified to coincide with the proper O/S.
For example, if the target Oracle Database Server was running an
IBM-AIX O/S, the command would appear as follows:
ln -s /usr/netvault/lib/orasbt.a orasbt.so
A.1.5 Verifying the Link
After the symbolic link has been created, verify that the libraries are properly linked. This can be accomplished by performing the following steps:
1. From the Oracle Database Server, initiate a terminal session
2. From the prompt, input the following commands (in the order they appear).
** % rman nocatalog
** RMAN> connect target /
** RMAN> run {
** 2> allocate channel ch1 type 'SBT_TAPE';
** 3> backup tablespace TOOLS format prompt“%u”;
** 4>}
If this command is successful, a banner will indicate the name of the NetVault SBT library. If this command fails, verify that the procedures above were followed correctly (based on the O/S installed on the Oracle Database Server).
© 2021 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy