1850344 Members
2806 Online
104054 Solutions
New Discussion

Bad magic number

 
SOLVED
Go to solution
Deborah Weatherspoon
Frequent Advisor

Bad magic number

Hello everyone,

I'm getting the following error message when I try to startup ORACLE 817.....

/usr/lib/dld.sl: Bad magic number for shared library: /u00/app/oracle/product/81
7/lib64/libclntsh.sl.8.0
/usr/lib/dld.sl: Exec format error
Abort(coredump)

Any help would be greatly appreciated....
3 REPLIES 3
James A. Donovan
Honored Contributor
Solution

Re: Bad magic number

Solution from Metalink:

Your SHLIB_PATH enviroment variable included the wrong directory: $ORACLE_HOME/lib64

As explained in the installation guide the enviroment variable LD_LIBRARY_PATH should include the $ORACLE_HOME/lib64 directory, but the SHLIB_PATH should include ORACLE_HOME/lib.

Setting the enviroment variable SHLIB_PATH to $ORACLE_HOME/lib should solve this problem.
Remember, wherever you go, there you are...
A. Clay Stephenson
Acclaimed Contributor

Re: Bad magic number

This can happen for a number of reasons but a very common one is mixing 32-bit and 64-bit libraries and code. It could also be the result of trying to use code for an Itanium box on a PA-RISC box.

Also if you copied the Oracle binaries from another machine, you might need to relink.

I'll assume that you are using svrmgr.
cd ${ORACLE_HOME}/bin
ldd svrmgrl

This will list all the dynamic libraries.
First, do a "file" command on svrmmgrl itself to make sure it is a PA-RISC executable and then do a "file" command on each of the shared libraries to make sure that they are the correct type as well.
If it ain't broke, I can fix that.
Sathish C
Frequent Advisor

Re: Bad magic number

pls check your oracle libs and the SHLIB_PATH variable that there no mis up of 32 and 64 bit libs of the same shared/dynamic links libs of oracle .
Some cause happiness wherever they go; others, whenever they go