Problems using an old version of DBI to connect to a remote Oracle 10g database

------_=_NextPart_001_01C7333E.A1E7ABF9
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Dear all,

Appreciate if someone can help me with this.

I have a Solaris 5.6 Generic_105181-33 box on which I have Perl version
5.005_03.
I also have Perl modules DBI (version 1.14) and DBD::Oracle (version
1.06 - I think?? - how can I check this?)
I am using the following string to connect to a remote Oracle 10g
instance:

my $dbh =3D DBI->connect
("dbi:Oracle:$environment",$nsm_login,$nsm_password) || die "Unable to
connect to $environment: $DBI::errstr\n";

....where $environment is the instance name - this is defined in
tnsnames.ora.

I am getting the following error:

ORA-03113: end-of-file on communication channel (DBD: login failed)

I can connect OK from the command line using:

sqlplus login/password@instance_name

I suspect that I need newer versions of Perl, DBI and DBD.

Can anyone confirm this?

Thanks,
Dave S

------_=_NextPart_001_01C7333E.A1E7ABF9--

Re: Problems using an old version of DBI to connect to a remote Oracle 10g database

I would say yes as DBD::Oracel 1.06 is about 13 revisoins out of date.

----- Original Message -----
From:
To:
Sent: Monday, January 08, 2007 11:04 AM
Subject: Problems using an old version of DBI to connect to a remote Oracle
10g database


Dear all,

Appreciate if someone can help me with this.

I have a Solaris 5.6 Generic_105181-33 box on which I have Perl version
5.005_03.
I also have Perl modules DBI (version 1.14) and DBD::Oracle (version
1.06 - I think?? - how can I check this?)
I am using the following string to connect to a remote Oracle 10g
instance:

my $dbh = DBI->connect
("dbi:Oracle:$environment",$nsm_login,$nsm_password) || die "Unable to
connect to $environment: $DBI::errstr\n";

....where $environment is the instance name - this is defined in
tnsnames.ora.

I am getting the following error:

ORA-03113: end-of-file on communication channel (DBD: login failed)

I can connect OK from the command line using:

sqlplus login/password@instance_name

I suspect that I need newer versions of Perl, DBI and DBD.

Can anyone confirm this?

Thanks,
Dave S

RE: Problems using an old version of DBI to connect to a remote Oracle 10g database

This may not be a DBD::Oracle issue, although your modules look a little
dated. Did you check you instance alert log and find the generated
trace file?

--
Ron Reidy
Lead DBA
Array BioPharma, Inc.

-----Original Message-----
From: dave.salisbury@bt.com [mailto:dave.salisbury@bt.com]=20
Sent: Monday, January 08, 2007 9:04 AM
To: dbi-users@perl.org
Subject: Problems using an old version of DBI to connect to a remote
Oracle 10g database

Dear all,

Appreciate if someone can help me with this.

I have a Solaris 5.6 Generic_105181-33 box on which I have Perl version
5.005_03.
I also have Perl modules DBI (version 1.14) and DBD::Oracle (version
1.06 - I think?? - how can I check this?)
I am using the following string to connect to a remote Oracle 10g
instance:

my $dbh =3D DBI->connect
("dbi:Oracle:$environment",$nsm_login,$nsm_password) || die "Unable to
connect to $environment: $DBI::errstr\n";

....where $environment is the instance name - this is defined in
tnsnames.ora.

I am getting the following error:

ORA-03113: end-of-file on communication channel (DBD: login failed)

I can connect OK from the command line using:

sqlplus login/password@instance_name

I suspect that I need newer versions of Perl, DBI and DBD.

Can anyone confirm this?

Thanks,
Dave S

This electronic message transmission is a PRIVATE communication which =
contains
information which may be confidential or privileged. The information is =
intended=20
to be for the use of the individual or entity named above. If you are =
not the=20
intended recipient, please be aware that any disclosure, copying, =
distribution=20
or use of the contents of this information is prohibited. Please notify =
the
sender of the delivery error by replying to this message, or notify us =
by
telephone (877-633-2436, ext. 0), and then delete it from your system.