I found my error, there was a statement setting ORACLE_HOME where it did
not belong. I must have looked past it a dozen times. Thanks for the
help.
On Mon, 2002-02-04 at 16:29, Michael A Chase wrote:
> If you need to pursue that further here, a snippet of code that demonstrates
> the problem along with the exact values in $DBI::errstr and $DBI::err at the
> point of failure are necessary. The trace log from DBI->trace(2) might also
> help.
> --
> Mac :})
> ** I normally forward private questions to the appropriate mail list. **
> Ask Smarter: http://www.tuxedo.org/~esr/faqs/smart-questions.htm
> Give a hobbit a fish and he eats fish for a day.
> Give a hobbit a ring and he eats fish for an age.
> ----- Original Message -----
> From: "Chris Garringer" <[EMAIL PROTECTED]>
> To: "Michael A Chase" <[EMAIL PROTECTED]>
> Cc: <[EMAIL PROTECTED]>
> Sent: Monday, February 04, 2002 14:17
> Subject: Re: Connecting to 2 versions of Oracle
>
>
> > One one of the ERP boxes the 7.3.4 Oracle application was still there.
> > I set ORACLE_HOME to the 7.3.4 directory, and ran make on
> > DBD-Oracle-1.12, set ORACLE_HOME back to 8.1.7 for test and install.
> > The Perl program now connects properly to both the 7.3.4 on the
> > Peoplesoft box and 8.1.7 on its local ERP box. The only change is how
> > DBD-Oracle was compiled. The logs on the Peoplesoft box show the same
> > thing for connections with either method. It appears that the
> > connection is succeeding on the Peoplesoft box with the 8.1.7 compiled
> > DBD module, but the return information is saying it failed.
> > On Mon, 2002-02-04 at 16:00, Michael A Chase wrote:
> > > The only version of Oracle that matters to a DBI/DBD::Oracle script is
> the
> > > version of Oracle it was compiled against. Connections to the databases
> > > should go through SQL*Net.
> > >
> > > Make sure the session that the DBI script is running in has ORACLE_HOME,
> > > LD_LIBRARY_PATH (if applicable) and other similar variables pointing to
> the
> > > correct Oracle Home. Make sure the tnsnames.ora in that Oracle Home is
> > > correct for the 7.3 instance as well.
> > >
> > > If none of that helps, add 'DBI->trace(9, "log_file_name");' before the
> > > login to see more of what is happening.
> > > --
> > > Mac :})
> > > ** I normally forward private questions to the appropriate mail list. **
> > > Ask Smarter: http://www.tuxedo.org/~esr/faqs/smart-questions.htm
> > > Give a hobbit a fish and he eats fish for a day.
> > > Give a hobbit a ring and he eats fish for an age.
> > > ----- Original Message -----
> > > From: "Chris Garringer" <[EMAIL PROTECTED]>
> > > To: <[EMAIL PROTECTED]>
> > > Sent: Monday, February 04, 2002 13:13
> > > Subject: Connecting to 2 versions of Oracle
> > >
> > >
> > > > We had a system with Oracle 7.3.4. for Peoplesoft and 7.3.4.4 for our
> > > > ERP system (3 Oracle system in ERP). I had DBI-1.2 and DBD-Orace 1.12
> > > > working fine on the ERP systems. The program in question contacted
> the
> > > > Peoplesoft system to get HR data for new user creation on the ERP
> > > > systems. Recently we upgraded to 8.1.7 on the 2 ERP test systems. I
> > > > recompiled DBI1.2 and DBD-1.12 on the boxes (since oracle was now
> 8.1.7)
> > > > and the program cannot contact the Oracle on the Peoplesoft box
> > > > (7.3.4). I get a null password error, Oracle 01005. How can I connect
> > > > to both versions of Oracle from the same program?
>
>
>
--
Chris D. Garringer
LAN/WAN Supervisor
Toshiba International
713-466-0277 x3756
fax 713-896-5266
Red Hat Certified Engineer
Novell MCNE
Certified Solaris Administrator
