In message <[EMAIL PROTECTED]>, joe bayer writes: >On my WinXP sp2, I have perl 5.6.1 installed and a lot of scripts depend on th >at. Recently I installed Oracle 10g Version 2, it added a new system variable > >------------------------------------------------------------------------------ >--------------------- > >PERL5LIB=d:\oracle\ora102\perl\5.8.3\lib\MSWin32-x86;d:\oracle\ora102\perl\5.8 >.3\lib;d:\oracle\ora102\perl\5.8.3\lib\MSWin32-x86;d:\oracle\ora102\perl\site\ >5.8.3;d:\oracle\ora102\perl\site\5.8.3\lib;d:\oracle\ora102\sysman\admin\scrip >ts; > >------------------------------------------------------------------------------ >--------------------- > >Now my poor DBI perl script stopped working. For example, (this is not a DBI >script, but just an example how Oracle 10G screwed things up)
We encountered this problem with an application we deliver for Windows. The solution was to unset PERL5LIB in the bat file which invokes our Perl script. I'm not a DOS expert, but I think the syntax is @set PERL5LIB= Happy hacking, John [EMAIL PROTECTED]
