Solution to Oracle bug vipca failure

An error is reported when srvctl is executed.

[Oracle @ rac01 bin] $ srvctl

/U01/app/oracle/product/10.2.0/db_1/jdk/jre/bin/java: error while loading shared libraries: libpthread. so.0: cannot open shared object file: No such file or directory
Srvctl cannot be started

To Solve Problem 1 above, edit vipca in the $ ORACLE_BASE/crs/bin directory of rac01 and rac02 to cancel the setting of LD_ASSUME_KERNEL.

After the IF Statement of about 120th rows, set nu adds an unset command to ensure that LD_ASSUME_KERNEL has not been set,

If ["$ arch" = "i686"-o "$ arch" = "ia64"]
Then
LD_ASSUME_KERNEL = 2.4.19
Export LD_ASSUME_KERNEL
Unset LD_ASSUME_KERNEL
Fi

For srvctl (under the CRS bin directory of all nodes and the ORACLE_HOME/bin and ASM bin Directories), you can add a line around 168th to cancel LD_ASSUME_KERNEL setting, as shown below:

LD_ASSUME_KERNEL = 2.4.19
Export LD_ASSUME_KERNEL
Unset LD_ASSUME_KERNEL <= Line to be added

Note: re-edit these files for all nodes:

<ORA_CRS_HOME>/bin/vipca
<ORA_CRS_HOME>/bin/srvctl
<ORACLE_HOME>/bin/srvctl
<ASM_HOME>/bin/srvctl #()
After applying the 10.2.0.2 or 10.2.0.3 Patch Set, these patch sets will still include additional settings for OEL5, RHEL5, or SLES10. This issue is caused by development and fixed in the 10.2.0.4 patch set.

In addition, we explicitly cancel the LD_ASSUME_KERNEL setting instead of simply marking it as a comment statement to cancel the setting. This is to deal with the situation where the user is in the environment (Login shell) this variable is set in.