Re: Perl versions conflict help

I smell Oracle here. Oracle comes with its own Perl, but uses it rarely or even not at all. There are some very obsure perl scripts in the Oracle directories that you usually do not need. Removing the Oracle's Perl using the Universal Installer is possible, but due to some dependancies, the UI will also remove lots of other parts of Oracle.

I've manually deleted the Perl directories that Oracle installed (D:\oracle\product\10.2.0\db_1\perl\ in your case) several times, no Oracle installation broke, and "my" Perl (ActiveState's ActivePerl in the old days, Strawberry Perl today) just worked.

From my experience with Perl on Windows, I strongly recommend NOT to have more than one Perl on a Windows machine. If you fear to break Oracle, use Oracles antique Perl. If you need a newer Perl, get rid of Oracle's Perl.

Alexander

--
Today I will gladly share my knowledge and experience, for there are no sweeter words than "I told you so". ;-)

Comment on Re: Perl versions conflict help

Replies are listed 'Best First'.
Re^2: Perl versions conflict help by Mr. Muskrat (Canon) on Nov 16, 2009 at 21:13 UTC
If you remove Oracle's version of Perl you may not know that you have broken something important until your data is hosed. Solution: Set the real PERL5LIB at the OS level for your users and override Oracle's PERL5LIB so that it can still find its own modules.	[reply]