Re: Connection error with DBD-Sybase

From: Chuck Fox (chuckfox2_at_aol.com)
Date: 06/28/04

Next message: Nancy McMullin: "DBD Error on test"
Previous message: Peter J. Holzer: "Re: MultiByte Character Sets and False Matches"
In reply to: Eric Wimer: "Connection error with DBD-Sybase"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Date: Mon, 28 Jun 2004 08:57:53 -0400
To: "Eric Wimer" <eric.wimer@cimedia.com>

Eric,

You are using the TLI interface file. You might try using the DNS based
one.

Chuck

Eric Wimer wrote on 6/25/2004, 8:33 PM:

> We're running Solaris 2.8 with the Sybase ASE v12.5.1 client installed
> on it. I've confirmed that we can connect to a remote database using
> isql. Our current interfaces file:
>
> -------------file starts--------------
> foo
> query tli tcp /dev/tcp \x000207f1a98982020000000000000000
> master tli tcp /dev/tcp \x000207f1a98982020000000000000000
> -------------file ends----------------
>
> My working isql command:
>
> isql -P baz -S foo -U bar -D news
>
> My PWD file in the build directory:
>
> -------------file starts--------------
> # This file contains optional login id, passwd and server info for the
> test
> # programs:
> # You probably don't want to have it lying around after you've made
> # sure that everything works OK.
>
> PWD=baz
> SRV=foo
> UID=bar
> DB=news
> -------------file ends----------------
>
> I built DBD::Sybase v1.02 using DBI v1.14 with no problems reported.
> However, I get the following errors when I run make test:
>
> -------------command starts--------------
> make test
> PERL_DL_NONLAZY=1 /usr/local/bin/perl -Iblib/arch -Iblib/lib
> -I/usr/local/lib/perl5/5.6.0/sun4-solaris -I/usr/local/lib/perl5/5.6.0
> -e 'use Test::Harness qw(&runtests $verbose); $verbose=0; runtests
> @ARGV;' t/*.t
> t/autocommit........Can't call method "do" on an undefined value at
> t/autocommit.t line 29.
> t/autocommit........dubious
> Test returned status 255 (wstat 65280, 0xff00)
> DIED. FAILED tests 2-4
> Failed 3/4 tests, 25.00% okay
> t/base..............ok
> t/exec..............DBI->connect(server=foo;database=news) failed:
> OpenClient message: LAYER = (5) ORIGIN = (3) SEVERITY = (5) NUMBER = (4)
> Server foo, database
> Message String: ct_connect(): network packet layer: internal net library
> error: There was an error encountered while establishing the connection.
> at t/exec.t line 26
> Can't call method "prepare" on an undefined value at t/exec.t line 30.
> t/exec..............dubious
> Test returned status 255 (wstat 65280, 0xff00)
> DIED. FAILED tests 2-9
> Failed 8/9 tests, 11.11% okay
> t/fail..............Unable for connect to foo: OpenClient message: LAYER
> = (5) ORIGIN = (3) SEVERITY = (5) NUMBER = (4)
> Server foo, database
> Message String: ct_connect(): network packet layer: internal net library
> error: There was an error encountered while establishing the connection.
> t/fail..............dubious
> Test returned status 255 (wstat 65280, 0xff00)
> DIED. FAILED tests 2-13
> Failed 12/13 tests, 7.69% okay
> t/login.............ok 3/3FAILED test 2
> Failed 1/3 tests, 66.67% okay
> t/main..............Unable for connect to foo: OpenClient message: LAYER
> = (5) ORIGIN = (3) SEVERITY = (5) NUMBER = (4)
> Server foo, database
> Message String: ct_connect(): network packet layer: internal net library
> error: There was an error encountered while establishing the connection.
> t/main..............dubious
> Test returned status 255 (wstat 65280, 0xff00)
> DIED. FAILED tests 2-16
> Failed 15/16 tests, 6.25% okay
> t/nsql..............DBI->connect(server=foo;database=news) failed:
> OpenClient message: LAYER = (5) ORIGIN = (3) SEVERITY = (5) NUMBER = (4)
> Server foo, database
> Message String: ct_connect(): network packet layer: internal net library
> error: There was an error encountered while establishing the connection.
> at t/nsql.t line 24
> Can't call method "func" on an undefined value at t/nsql.t line 29.
> t/nsql..............dubious
> Test returned status 255 (wstat 65280, 0xff00)
> DIED. FAILED tests 2-4
> Failed 3/4 tests, 25.00% okay
> t/place.............Unable for connect to foo: OpenClient message: LAYER
> = (5) ORIGIN = (3) SEVERITY = (5) NUMBER = (4)
> Server foo, database
> Message String: ct_connect(): network packet layer: internal net library
> error: There was an error encountered while establishing the connection.
> t/place.............dubious
> Test returned status 255 (wstat 65280, 0xff00)
> DIED. FAILED tests 2-11
> Failed 10/11 tests, 9.09% okay
> t/xblob.............DBI->connect(server=foo;database=news) failed:
> OpenClient message: LAYER = (5) ORIGIN = (3) SEVERITY = (5) NUMBER = (4)
> Server foo, database
> Message String: ct_connect(): network packet layer: internal net library
> error: There was an error encountered while establishing the connection.
> at t/xblob.t line 26
> Can't call method "do" on an undefined value at t/xblob.t line 31.
> t/xblob.............dubious
> Test returned status 255 (wstat 65280, 0xff00)
> DIED. FAILED tests 2-6
> Failed 5/6 tests, 16.67% okay
> Failed Test Status Wstat Total Fail Failed List of failed
>
-------------------------------------------------------------------------------

>
> t/autocommit.t 255 65280 4 3 75.00% 2-4
> t/exec.t 255 65280 9 8 88.89% 2-9
> t/fail.t 255 65280 13 12 92.31% 2-13
> t/login.t 3 1 33.33% 2
> t/main.t 255 65280 16 15 93.75% 2-16
> t/nsql.t 255 65280 4 3 75.00% 2-4
> t/place.t 255 65280 11 10 90.91% 2-11
> t/xblob.t 255 65280 6 5 83.33% 2-6
> Failed 8/9 test scripts, 11.11% okay. 57/71 subtests failed, 19.72%
> okay.
> make: *** [test_dynamic] Error 2
> [ewimer@pentagon DBD-Sybase-1.02.ejw]$ make test
> PERL_DL_NONLAZY=1 /usr/local/bin/perl -Iblib/arch -Iblib/lib
> -I/usr/local/lib/perl5/5.6.0/sun4-solaris -I/usr/local/lib/perl5/5.6.0
> -e 'use Test::Harness qw(&runtests $verbose); $verbose=0; runtests
> @ARGV;' t/*.t
> t/autocommit........Can't call method "do" on an undefined value at
> t/autocommit.t line 29.
> t/autocommit........dubious
> Test returned status 255 (wstat 65280, 0xff00)
> DIED. FAILED tests 2-4
> Failed 3/4 tests, 25.00% okay
> t/base..............ok
> t/exec..............DBI->connect(server=foo;database=news) failed:
> OpenClient message: LAYER = (5) ORIGIN = (3) SEVERITY = (5) NUMBER = (4)
> Server foo, database
> Message String: ct_connect(): network packet layer: internal net library
> error: There was an error encountered while establishing the connection.
> at t/exec.t line 26
> Can't call method "prepare" on an undefined value at t/exec.t line 30.
> t/exec..............dubious
> Test returned status 255 (wstat 65280, 0xff00)
> DIED. FAILED tests 2-9
> Failed 8/9 tests, 11.11% okay
> t/fail..............Unable for connect to foo: OpenClient message: LAYER
> = (5) ORIGIN = (3) SEVERITY = (5) NUMBER = (4)
> Server foo, database
> Message String: ct_connect(): network packet layer: internal net library
> error: There was an error encountered while establishing the connection.
> t/fail..............dubious
> Test returned status 255 (wstat 65280, 0xff00)
> DIED. FAILED tests 2-13
> Failed 12/13 tests, 7.69% okay
> t/login.............ok 3/3FAILED test 2
> Failed 1/3 tests, 66.67% okay
> t/main..............Unable for connect to foo: OpenClient message: LAYER
> = (5) ORIGIN = (3) SEVERITY = (5) NUMBER = (4)
> Server foo, database
> Message String: ct_connect(): network packet layer: internal net library
> error: There was an error encountered while establishing the connection.
> t/main..............dubious
> Test returned status 255 (wstat 65280, 0xff00)
> DIED. FAILED tests 2-16
> Failed 15/16 tests, 6.25% okay
> t/nsql..............DBI->connect(server=foo;database=news) failed:
> OpenClient message: LAYER = (5) ORIGIN = (3) SEVERITY = (5) NUMBER = (4)
> Server foo, database
> Message String: ct_connect(): network packet layer: internal net library
> error: There was an error encountered while establishing the connection.
> at t/nsql.t line 24
> Can't call method "func" on an undefined value at t/nsql.t line 29.
> t/nsql..............dubious
> Test returned status 255 (wstat 65280, 0xff00)
> DIED. FAILED tests 2-4
> Failed 3/4 tests, 25.00% okay
> t/place.............Unable for connect to foo: OpenClient message: LAYER
> = (5) ORIGIN = (3) SEVERITY = (5) NUMBER = (4)
> Server foo, database
> Message String: ct_connect(): network packet layer: internal net library
> error: There was an error encountered while establishing the connection.
> t/place.............dubious
> Test returned status 255 (wstat 65280, 0xff00)
> DIED. FAILED tests 2-11
> Failed 10/11 tests, 9.09% okay
> t/xblob.............DBI->connect(server=foo;database=news) failed:
> OpenClient message: LAYER = (5) ORIGIN = (3) SEVERITY = (5) NUMBER = (4)
> Server foo, database
> Message String: ct_connect(): network packet layer: internal net library
> error: There was an error encountered while establishing the connection.
> at t/xblob.t line 26
> Can't call method "do" on an undefined value at t/xblob.t line 31.
> t/xblob.............dubious
> Test returned status 255 (wstat 65280, 0xff00)
> DIED. FAILED tests 2-6
> Failed 5/6 tests, 16.67% okay
> Failed Test Status Wstat Total Fail Failed List of failed
>
-------------------------------------------------------------------------------

-- 
Your Friendly Neighborhood DBA,
Chuck

Next message: Nancy McMullin: "DBD Error on test"
Previous message: Peter J. Holzer: "Re: MultiByte Character Sets and False Matches"
In reply to: Eric Wimer: "Connection error with DBD-Sybase"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Relevant Pages

Connection error with DBD-Sybase
... I've confirmed that we can connect to a remote database using ... FAILED tests 2-4 ... Server foo, database ... There was an error encountered while establishing the connection. ...
(perl.dbi.users)
Re: ADO Connection Timeout
... so what happens when a connection failure forces one station to revert ... to a local database? ... Further, you *will* have contention issues, Jet does not support record ... to the central server, but you are willing to live with periods where it ...
(microsoft.public.data.ado)
Re: ADO Connection Timeout
... When the first test is run, the results are stored in the central database. ... to the central server, but you are willing to live with periods where it ... i.e. a local database or even a text file. ... to function until the connection can be restored to the server. ...
(microsoft.public.data.ado)
Re: ADO Connection Timeout
... to the central server, but you are willing to live with periods where it ... i.e. a local database or even a text file. ... to function until the connection can be restored to the server. ...
(microsoft.public.data.ado)
Re: ADO Connection Timeout
... much rather write stored procedures and use server side cursors. ... local database, it is vital that I get the information to a central server. ... Once the connection is restored, ...
(microsoft.public.data.ado)