I just compared function name for both library and sqlplus NM output and there are 381 which are used in both cases. Now what does this mean...?
Ah, the funny thing is they just told me 5 minutes ago that the same configuration works in other servers and in some doesnt. Puzzled...
LD_PRELOAD allows you to hijack dynamicly loaded library functions. If sqlplus calls function X, then if this function X is exported from your /sbl/xxx.sl then this function X is called from /sbl/xxx.sl even if it exists in some other dll against which the executable is linked (like libclntsh* libraries).
Run: nm /sbl/xxx.sl to see which functions may be hijacked there, this could give some more indication what's going on.
And of course, the library's word-size has to match word-size of the executable. If the word sizes are different, you have to recompile the library.
------------------------------ *From:* oracle-l-bounce@xxxxxxxxxxxxx [mailto: oracle-l-bounce@xxxxxxxxxxxxx] *On Behalf Of *LS Cheng *Sent:* Thursday, August 31, 2006 04:45
*To:* Jesse, Rich *Cc:* oracle-l *Subject:* Re: LD_PRELOAD problem
However when I unset LD_PRELOAD sqlplus works but of course the application specific program fails.