Oracle Grid Control agents - Upgrade => mismatched ABI

[PatRoy]

Hi.

My DBA is trying to upgrade the EM Grid Control agents software on our HPUX 11.23 (ia64) box.

It seems to fail giving him the following error:

ld: Can't find library or mismatched ABI for -lclntsh
Fatal error.

For starters I've seen such errors a few times when compiling stuff. However, I have no clue what "mismatched ABI" means. If I knew I could perhaps understand a bit more how to resolve the issue.

Secondly, I DO have *clntsh* libs under the $ORACLE_HOME environment (Oracle 10g2). I have them in both, $ORACLE_HOME/lib and $ORACLE_HOME/lib32.

Here's another question: should he have exported LD_LIBRARY_PATH=$ORACLE_HOME/lib and/or SHLIB_PATH=$ORACLE_HOME/lib32 ??? And what IS the difference between theses 2 variables? One is for 32 bit and the other for 64bit just like I have it written, right? Or am I mistaking??? And I'm assuming I should only need the 64 bit right?

Thank you all such much for your help.

Cheers! Pat

[Dennis Handly]

>ld: Can't find library or mismatched ABI for -lclntsh

This means that either it can't find the library, or it found one but it was not the right data model, 32 vs 64 bit.

(I've asked that they not combine the two error cases into one confusing error messages. Newer linkers should have that fixed.)

>I have them in both, $ORACLE_HOME/lib and $ORACLE_HOME/lib32

Is one 64 and the other 32? For ELF linkers, it should pick the right one, if both paths are in different -L options, or LPATH is used.

>should he have exported LD_LIBRARY_PATH=$ORACLE_HOME/lib and/or SHLIB_PATH=$ORACLE_HOME/lib32?

This is a link time error, these are ignored.

>And what IS the difference between theses 2 variables? One is for 32 bit and the other for 64bit just like I have it written, right?

Yes. Except SHLIB_PATH works for both because of compatibility. But LD_LIBRARY_PATH is standard and should be used for PA64 and all cases on IPF.

>And I'm assuming I should only need the 64 bit right?

Yes, if you are on PA, that error only occurs when you are doing a 64 bit (ELF) link.

[Tim Nelson]

This is probably not the answer but..

Every issue I have had with OEM agent installs were due to an outdated linker patch.

Make sure you are relatively current.