Bad Magic Number for liboracle.sl??

[DevikaM]

We are developing a DEV server for which uses oracle 11.2 version. For library files we just copied from the existing server, which uses oracle 8 (all we do is migration, therefore copying)

(Dev server - IA 64 and existing server is PA RISC 1.1)

And the executables are not running in the Dev Server saying,

/usr/lib/dld.sl: Bad magic number for shared library: /fnsw/lib/shobj/liboracle.sl
/usr/lib/dld.sl: Exec format error
[HP ARIES32]: Core file for 32-bit PA-RISC application
[HP ARIES32]:   /home/fnsw/bin/linksap saved to /home/fnsw/bin/core.linksap.
Abort(coredump)

 

Following are the settings,

us70thapp001(fnsw)/usr/lib/hpux32> echo $SHLIB_PATH
/u01/app/oracle/product/11.2.0.2/lib32:/u01/app/oracle/product/11.2.0.2/lib:/fnsw/lib/shobj

and

us70thapp001(fnsw)/usr/lib/hpux32> echo $LD_LIBRARY_PATH

 <<No Output displayed>>

Can someone help me out on this issue??

[Dennis Handly]

>We are developing a DEV server for which uses oracle 11.2 version. For library files we just copied from the existing server, which uses oracle 8 (all we do is migration, therefore copying)

(Dev server - IA64 and existing server is PA-RISC 1.1)

If you are using a newer Oracle for Integrity, you don't want to copy PA shlibs over.

Also, are you sure your old server is PA 1.1?  They haven't sold those for more than a decade.

>dld.sl: Bad magic number for shared library: /fnsw/lib/shobj/liboracle.sl

What does "file /fnsw/lib/shobj/liboracle.sl" show?

[DevikaM]

Hi Dennis, thanks for the reply:)

Here are the details you asked

liboracle.sl is linking to the path -> /u01/app/oracle/product/11.2.0.2/lib/libclntsh.so

Old server is 1.1 for sure and i dont know abt all the history behind that. But currently we are mgrating that thing to IA64.

And no way other than copying, as all the required files resides only in existing server.

[Dennis Handly]

>Here are the details you asked

Hmm, they don't look like what I asked for.

>liboracle.sl is linking to the path -> /u01/app/oracle/product/11.2.0.2/lib/libclntsh.so

Again, what does this show:

file /u01/app/oracle/product/11.2.0.2/lib/libclntsh.so /fnsw/lib/shobj/liboracle.sl

This is likely the problem.  A PA application can't access an Integrity shlib.

>Old server is 1.1 for sure

I would like proof:  file /stand/vmunix

>And no way other than copying, as all the required files resides only in existing server.

And what files are these?

[DevikaM]

/stand/vmunix: ELF-64 executable object file - PA-RISC 2.0 (LP64) - Proof

us70thapp001(fnsw)/home/fnsw/bin> file /u01/app/oracle/product/11.2.0.2/lib/libclntsh.so /fnsw/lib/shobj/liboracle.sl
/u01/app/oracle/product/11.2.0.2/lib/libclntsh.so:      ELF-32 shared object file - IA64
/fnsw/lib/shobj/liboracle.sl:   PA-RISC1.1 shared library -not stripped

 The files are nothing but the scripts,executables, lib files etc etc

[Dennis Handly]

>/stand/vmunix: ELF-64 executable object file - PA-RISC 2.0 (LP64) - Proof

(Yes, proof that you have a PA2.0 server, not PA1.1.  But this is moot to your problem.)

On what system did you do that "file" on the two shlibs?  They appear to be two different architectures and "PA-RISC1.1 shared library" shouldn't give that Bad Magic Number error.

>The files are nothing but the scripts, executables, lib files etc

If you are going to copy over load modules (executables and shlibs), you must copy over the whole application.

It seems you have copied over /home/fnsw/bin/linksap but not /fnsw/lib/shobj/liboracle.sl?

[DevikaM]

Ran file command in IA64 Server (Dev Server).
PA-RISC1.1 shared library -not stripped is the output for almost 95% of the file commands i use.
I didnt understand this,
It seems you have copied over /home/fnsw/bin/linksap but not /fnsw/lib/shobj/liboracle.sl?
Can you explain me again?

[Dennis Handly]

>PA-RISC1.1 shared library -not stripped is the output for almost 95% of the file commands I use.

Yes, that's typical for PA.

>I didn't understand this, Can you explain me again?
>>   It seems you have copied over /home/fnsw/bin/linksap but not /fnsw/lib/shobj/liboracle.sl?

Well, the only way you can get that Aries/dld.sl error is if /fnsw/lib/shobj/liboracle.sl is for IA64 or PA64.

But now you seem to have contradictory info:

dld.sl: Bad magic number for shared library: /fnsw/lib/shobj/liboracle.sl

/fnsw/lib/shobj/liboracle.sl: PA-RISC1.1 shared library -not stripped

What does "ll /fnsw/lib/shobj/liboracle.sl" show?