You should really include $DBI::errstr in your die() string. That would
tell you what Oracle didn't like about your connection attempt.
The problem is probably in your tnsnames.ora. Can you connect using the
same userid/pasword@instance in SQL*Plus?
Setting ORACLE_HOME is not required, but it might be useful in this case to
make sure you know which home DBD::Oracle is using to find tnsnames.ora and
various library and message files.
--
Mac :})
** I normally forward private questions to the appropriate mail list. **
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: "READY, MIKE P" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, October 18, 2001 13:51
Subject: Problem connecting from new PC
> Group-
> Okay, this is probably a really dumb one but I haven't run into this
before.
> I just moved to a new project group and took over an existing PC which has
> two OracleHomes (d:\Oracle\Ora81 or c:\Oracle\Ora81) one can switch
between.
> I installed Active State Perl 5.6.1 build 629, DBD-Oracle 1.06 and DBI
1.14.
> When I attempt to run a program (using either Oracle Home), I get an error
> at the connect string line - e.g. for line 29 below
>
> $dbh = DBI->connect("DBI:Oracle:$dbalias","$userid","$pwd") or die "Can't
> connect\n";
>
> I get:
>
> DBI->connect(classt) failed: (DBD: login failed, check your config, e.g.
> ORACLE_HOME/bin on your PATH etc) at PST.TMP line 29
> Can't connect
>
> Path contains:
>
d:\Oracle\Ora81\bin;C:\Oracle\Ora81\bin;D:\Python21\;D:\Perl\bin\;C:\Program
>
Files\Oracle\jre\1.1.7\bin;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\S
> ystem32\Wbem;C:\Oracle\Ora81\orb\bin;C:\Program Files\Common Files\MDL
> Shared\ISIS
>
> Like I said, this is probably trivial, but I have never had this on
several
> previous installations and am clueless. I will gladly accept any insults
> that accompany a description of what I need to fix.
