The thing that nailed me in this situation is the $ORACLE_HOME/lib moved = from 32-bit to 64-bit. You *might* be able to get away without = recompiling by pointing environment variable LD_LIBRARY_PATH or = SHLIB_PATH (you don't mention what platform you're on) to = $ORACLE_HOME/lib32 for the 32-bit libs. A quick Google should help, = too. HTH! Rich -----Original Message----- Sent: Friday, December 03, 2004 10:34 AM To: 'Ravi.Kulkarni@xxxxxxxxxxxxxxxxxxx'; oracle-l@xxxxxxxxxxxxx Subject: RE: Perl Connect error after Oracle Upgrade Well, if your libclntsh.so has changed and if your DBI was using it, then I suppose that you should reinstall your DBI. I believe that the layout of Oracle shared client library might change when switching from=20 one major version to another, especially if oracle home swithched from something like /oracle/product/8.1.7 to something like /oracle/product/9.2.0. You should readjust your environment variables = (ask your favorite Unix system administrator to run regedit32 or regedit64, depending on how many bits does your platform have) and relink anything that was dependent upon the old libraries. -- Mladen Gogala Ext. 121 -----Original Message----- Sent: Friday, December 03, 2004 11:21 AM To: oracle-l@xxxxxxxxxxxxx Subject: Perl Connect error after Oracle Upgrade Hi All -=20 Oracle DB upgraded from 817 to 920 : Perl Program connecting to DB fails which worked fine before with :=20 DBI connect('db','sch',...) failed: ERROR OCIEnvInit at /opt1/app/tb/lib/perl/DL-db-lib.pl line 89.=20 Did you have to re-install DBD also after Oracle upgrade ?=20 -- //www.freelists.org/webpage/oracle-l