On 3/1/06, Chuck Fox <[EMAIL PROTECTED]> wrote:
> One solution would be to install your own error handler and catch the
> 17001 and 2056 errors and ignore them.

I am hesitant to do this. I prefer to install error handlers to catch
errors that I know I am causing. However, the select that is causing
this problem in inside DBD::Sybase, during the connection phase. If
the protocol changes in a newer version of DBD::Sybase, these errors
could become legit and I wouldn't know. Better to fix at the point of
error; in this case, inside DBD::Sybase.

>
> HTH,
>
> Chuck
>
> [EMAIL PROTECTED] wrote:
>
> > This is not a very helpful answer, but are you sure this is worth
> > trying?  A Replication Server is not an Adaptive Server Enterprise.
> > Admittedly they both use the same Tabular Data Stream networking
> > protocol, but they have very different command languages.  A Rep
> > Server isn't even a database server.  Are you sure it is reasonable to
> > expect a DBI driver for Sybase ASE to work correctly with Rep Server?
> >
> > Maybe Sybperl is the way to go if you want your perl program to talk
> > to a Rep Server.
> >
> > Good luck,
> >
> > Mark
> >
> > Matthew Persico wrote:
> >
> >> This simple test program:
> >>
> >> use strict;
> >> use warnings;
> >> use DBI;
> >> my $dbh = DBI->connect('dbi:Sybase:server=REPP', 'REPP_login',
> >> 'REPP_passwd', {RaiseError => 1});
> >> my $dummy = 6;
> >>
> >> causes this:
> >>
> >> Server message number=17001 severity=10 state=0 line=0 server=REPP
> >> text=No SRV_OPTION handler installed.OpenClient message: LAYER = (1)
> >> ORIGIN = (1) SEVERITY = (1) NUMBER = (183)
> >> Server REPP, database
> >> Message String: ct_options(): user api layer: external error: An error
> >> was returned from the server while setting the options, check the
> >> server message for details.
> >> Server message number=2056 severity=12 state=0 line=0 server=REPP
> >> text=Line 1, character 8: Incorrect syntax with 'select'.
> >> [EMAIL PROTECTED] (DEV, uid=8030(persicom) gid=200(develop) depth=0)
> >>
> >> using Perl 5.6.1, DBI 1.48 and DBD::Sybase 1.07.
> >>
> >> However, when using Perl 5.6.1, DBI 1.37 and DBD::Sybase 1.00, I get
> >> no error message.
> >>
> >> What DBI trace flags/envars do I neet to set in order to diagnose this?
> >>
> >> --
> >> Matthew O. Persico
> >>
> >>
> >>
> >>
> >
>


--
Matthew O. Persico

Reply via email to