ok i'm not talking pl/sql here. This is C Code. What i'm wondering more so if why is it picking up the .so rather than the .a is there a document out there explaining the change ?. ----- Original Message ---- From: Pedro Espinoza <raindoctor@xxxxxxxxx> To: fuadar@xxxxxxxxx; oracle-l <oracle-l@xxxxxxxxxxxxx> Sent: Tuesday, July 24, 2007 10:31:23 AM Subject: Re: anyone seens this or encountered this after a 9.2 to 10.2 upgrade Fuad, You find a difference between 10g and 9i libraries, and assume that this is the cause of the compilation problems (pl/sql ?). Whatever difference you found cannot be the cause, for .a shows that it is static library whereas .so shows that it is linked dynamically. The difference is that oracle has changed the way how libraries are linked. On 7/24/07, Fuad Arshad <fuadar@xxxxxxxxx> wrote: > > upgrading from 188.8.131.52 to 10.2.0.3 > dev environment > aix 5.3 > our developers are having issues compiling code and moving it to production > which is still 9i. > > > > It seems in 9i its using the libclntsh.a > /usr/local/oracle/product/9.2/lib > ls -lt libcl* > -rw-r--r-- 1 oracle dba 20878476 Jul 23 06:46 libclntst9.a > -rw-r--r-- 1 oracle dba 15528406 Jul 23 06:44 libclntsh.a > -rw-r--r-- 1 oracle dba 3770227 Aug 13 2006 libclient9.a > in 10.2 it is using libclntsh.so > > ls -lt libclnt* > -rwxrwxr-x 1 oracle dba 23724184 Feb 18 03:42 libclntsh.so.10.1 > lrwxrwxrwx 1 oracle dba 17 Feb 18 03:40 libclntsh.so -> > libclntsh.so.10.1 > -rw-rw-r-- 1 oracle dba 24300970 Feb 18 03:39 libclntsh.a > > > anyone seen this behaviour cant find any hits on google . > Is there any ways we can force the use of the .a library > i could put a dummy link point to the .a in the 9 library directory but > havent tested the consequences yet.