RAC srvctl Command reports libpthread. so.0 cannot open shared object file no such file or directory solution

 

 

When you run the srvctl command, the following error occurs:

[Oracle @ Rac1 u01] $ srvctl remove ASM-N Rac1

/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

 

At first, I was surprised because I had modified the parameters of the srvctl command in vipca and ora_crs_home when installing CRS. The ld_assume_kernel parameter is commented out.

However, this error was reported during running, and the problem was discovered only after the which srvctl command was used:

 

[Oracle @ Rac1 u01] $ which srvctl

/U01/APP/Oracle/product/10.2.0/db_1/bin/srvctl

 

The system calls srvctl under ORACLE_HOME. So when you modify the ld_assume_kernel command, do not forget to modify the variable in ORACLE_HOME. If the variable is to put ORACLE_HOME in front, the srvctl command in ORACLE_HOME will be called.

 

[Oracle @ rac2 bin] $ echo $ path

. :. :/Usr/Kerberos/bin:/usr/local/bin:/usr/NX/bin:/home/Oracle/bin: /home/Oracle/bin:/u01/APP/Oracle/product/10.2.0/db_1/bin:/u01/APP/Oracle/product/CRS/bin:/usr/bin: /bin:/usr/bin/X11:/usr/local/bin:/u01/APP/Oracle/common/Oracle/bin:/home/Oracle/bin: /home/Oracle/bin:/u01/APP/Oracle/product/CRS/bin:/u01/APP/Oracle/product/10.2.0/db_1/bin: /u01/APP/Oracle/product/CRS/bin:/usr/bin/X11:/usr/local/bin: /u01/APP/Oracle/common/Oracle/bin

 

Settings in environment variables:

[Oracle @ rac2 ~] $ VI ~ /. Bash_profile

...

Export Path =. :$ {path }:$ home/bin: $ ORACLE_HOME/bin: $ ora_crs_home/bin

...

 

Modify the path sequence in the environment variable:

Export Path =. :$ {path }:$ home/bin: $ ora_crs_home/bin: $ ORACLE_HOME/bin

 

Re-open an SSH window, because the profile file will be loaded during connection, and the srvctl location will be changed to under ora_crs_home.

 

[Oracle @ rac2 ~] $ Which srvctl

/U01/APP/Oracle/product/CRS/bin/srvctl

 

 

There are two annotation methods:

(1) Use unset

# Remove this workaround when the bug 3937317 is fixed

Ld_assume_kernel = 2.4.19

Export ld_assume_kernel

Unset ld_assume_kernel

 

(2) Comment out:

# Remove this workaround when the bug 3937317 is fixed

# Ld_assume_kernel = 2.4.19

# Export ld_assume_kernel

 

 

 

 

Bytes ---------------------------------------------------------------------------------------------------

Blog: http://blog.csdn.net/tianlesoftware

Online Resources: http://tianlesoftware.download.csdn.net

Video: http://blog.csdn.net/tianlesoftware/archive/2009/11/27/4886500.aspx

Dba1 group: 62697716 (full); dba2 group: 62697977 (full) dba3 group: 62697850 (full)

Super DBA group: 63306533 (full); dba4 group: 83829929 dba5 group: 142216823

Chat group: 40132017

-- Add the group to describe the relationship between Oracle tablespace and data files in the remarks section. Otherwise, the application is rejected.