Rob Bloodgood wrote:
> > Perrin Harkins wrote:
> > >Rafael Caceres wrote:
> > >>I'm facing a dilemma here. We are testing an Oracle 9iAS installation
> > >>(Apache 1.3.19, mod_ssl 2.8.1, mod_perl 1.25 as DSO, Perl 5.005_03) on
> > >>Red Hat Linux 7.2, which itself came with Perl 5.6.0, and from your
> > >>comments, that's bad..
> > >
> > >First of all, if it's working for you then don't worry about it.
> >
> > I have not started testing scripts that currently work on other boxes. I
> > will install the required modules for the 5.005_03 perl used by Oracle
> > 9iAS, and see what happens.
> > This road forces me to have the two perl versions coexisting, or,
> > to search
> > for all the perl modules installed for the 5.6 version by the rpm's on
> > initial installation, install them for the 5.005_03 version and
> > then remove
> > the 5.6 one permanently.
>
>OK, for starters:
>Oracle includes their own version of perl/apache/mod_perl for the Web
>interface they are bundling with the new 9i servers.  It's their own
>version, built by their own people, for their own usage, on their own
>product, in its own path, under the Oracle product installation tree.
>
>Let 'em have it.  It's only a few megs of disk space, and if your 9i
>installation works, GREAT.  Don't think of it as two versions co-existing.
>Think of it as Oracle's insurance to themselves that their system will have
>the exact parts it needs.  Besides, except for a few configuration files,
>shouldn't everything under $ORACLE_HOME be considered hands-off anyway?

They dont seem to use it though, there is no visible perl script on the 
default httpd.conf other than the printenv script under /cgi-bin.
But, they set PERL5LIB to point to their perl in apachectl and httpd.conf, 
which I guess can be fixed in the mentioned places.


>Now, on to the real world: 10 minutes ago I just saw a post by a RedHat
>employee stating that there are new RPM's for Perl 5.6.1 and the latest
>mod_perl.  Which means you can download and install them, and THEN begin
>installing other modules, like Apache::DBI, Apache::Session, etc etc
>according to your needs, into the "real" perl installation tree, where all
>of YOUR system's perl modules live.

I've always used DBI along with DBD::Oracle for Database access, and I 
intend to use them along  Oracle 9iAS's other capabilities.

So if I'm following you correctly, the steps involved are:
-get the 5.6.1 RPM (which doesn't seem to be in Red Hat's site anyway)
-get the Apache 1.3.19 sources (to be used in the next step), then 
'discarded' without installing Apache per se.
-get the mod_perl 1.24_01-2.src.rpm and compile it as a DSO
-reinstall all previously installed packages, so other programs using them 
keep working
-install the modules the mod_perl apps require
-change the apachectl and httpd.conf files to reflect the proper perl 'home'
-change httpd.conf to load the mod_perl.so file from it's new location

Is this list OK?

> > Yes, there are at least two modules: mod_plsql and mod_oprocmgr for which
> > there is no source, so rebuilding seems to be out of the question
>
>Those modules are *only* for the Oracle administrative webservice, as I
>mentioned above.  If you want to use Oracle from Perl/mod_perl, do it like
>everybody else: DBI and DBD::Oracle (for the record, I build them for 9i
>several months ago with 0 headaches).  This *does* include the ability to
>execute PL/SQL.

The mod_plsql is called heavily from the Oracle 9iAS Portal applets, so it 
needs to be kept in place.


>L8r,
>Rob
>
>#!/usr/bin/perl -w
>use Disclaimer qw/:standard/;

Regards,
Rafael

Reply via email to