Yep, I saw this one on our HP-UX servers. I uninstalled Apache from most of our servers in response to the long list of security issues. After all, Rule 1 of the Oracle's secure configuration doc is "Only install what is required", and we aren't using the Apache stuff. Then, when I needed to use opatch, it wouldn't run until I put the perl module back in the Apache directory even though I had a working perl on the server and in my path. Fortunately, it's relatively easy to get the perl module back in place and after that, I went to 9.2.0.6 <http://9.2.0.6> and haven't had to mess with opatch since. Robyn On 5/20/05, Jared Still <jkstill@xxxxxxxxx> wrote: > > Wanna see something interesting with opatch? > *nix: perl -cw $ORACLE_HOME/OPatch/opatch.pl > > Windoze: perl -cw %ORACLE_HOME%\opatch\opatch.pl > > Anyone else have trouble with opatch and Perl 5.8.3? > > Windows 2003 > Perl 5.8.3 > Opatch 1.0....52 > > Opatch either exits with an error code that is a very long negative > number, > or just spits out its copyright information and quits. > > Interestingly, installing Perl 5.0.00503 in OH/Apache cures the problem, > as > the opatch.bat script will find it there and it runs happily. > > 5.8.3 seems to work fine on a Win2K box with the same version of opatch. > > -- > Jared Still > Certifiable Oracle DBA and Part Time Perl Evangelist > > -- > //www.freelists.org/webpage/oracle-l > -- //www.freelists.org/webpage/oracle-l