and CRS utilities

SRVCTL and VIPCA Utilities Set the LD_ASSUME_KERNEL Parameter

This is common error when using Oracle 10gR2 CRS utilities : SRVCTL and VIPCA.

The SRVCTL and VIPCA utilities shipped with Oracle Database 10g release 2 and Oracle Clusterware software set the environmental variable LD_ASSUME_KERNEL.

On Oracle Enterprise Linux 5.0, Red Hat Enterprise Linux 5.0, and SUSE Linux Enterprise Server 10, because the older Linux threads API has been removed from GLIBC, setting this parameter causes the SRVCTL and VIPCA utilities to exit with the following error:

error while loading shared libraries: cannot open shared object file:
No such file or directory

Workaround: Comment out the lines that set the LD_ASSUME_KERNEL variable from the VIPCA and SRVCTL utilities. For the VIPCA utility alter the $CRS_HOME/bin/vipca script commenting out lines 119 through 123 as follows:

arch='uname -m'
#       if [ "$arch" = "i686" -o "$arch" = "ia64" -o "$arch" = "x86_64" ]
#       then
#            LD_ASSUME_KERNEL=2.4.19
#            export LD_ASSUME_KERNEL
#       fi

With the lines commented out, should be able to call VIPCA successfully. Ensure that you do not to comment out line 118 which sets the arch variable as that is needed by the script.

For the SRVCTL utility alter the $CRS_HOME/bin/srvctl and the $ORACLE_HOME/bin/srvctl scripts commenting out lines 173 and 174 as follows:

#Remove this workaround when the bug 3937317 is fixed


“Error 404–Not Found” While Accessing OSB Console Through URL http://hostname:port/osbconsole

While accessing Oracle Service Bus (OSB) Console through the URL http://<hostname&gt;:<osb-port>/osbconsole as mentioned in the OSB Installation Guide, browser returns “Error 404–Not Found”.

This applies to Oracle Service Bus – Version: and laterĀ  (any platform)

This is a documentation Bug 9797009. OSB Console can be accessed through URL http://<admin server host>:<admin-port>/sbconsole