RE : Can"t connect to Sybase Rep server
RE : Can"t connect to Sybase Rep server
am 28.02.2006 11:47:27 von aselvakumar
------_=_NextPart_001_01C63C54.5DB0FD3C
Content-Type: text/plain;
charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Dear All,
=20
I was trying to install DBD-Oracle and am getting the following error
while execuritng=20
=20
perl Makefile.PL
=20
Can't locate ExtUtils/MakeMaker.pm in @INC (@INC contains:
=20
Can anyone help me...
=20
Regards
Selva
-------- Message d'origine--------=20
De: michael.peppler@bnpparibas.com
[mailto:michael.peppler@bnpparibas.com]=20
Date: mar. 28.02.2006 07:54=20
Ã: matthew.persico@gmail.com=20
Cc: dbi-users@perl.org=20
Objet: Re: Can't connect to Sybase Rep server
=09
=09
This is a known problem, and has been fixed in either 1.07 or
1.07_01.
=09
DBD::Sybase tries to see if chained transactions are supported
at startup,
and tries to find the @@version of the server. Both of these
requests fail
against a replication server, but the failure is expected, so
should simply
be hidden from the user...
=09
Michael
=09
=09
=09
=09
Extranet
matthew.persico@gmail.com - 27/02/2006 20:39
=09
To: dbi-users, Michael PEPPLER
=09
cc:
=09
=09
Subject: Can't connect to Sybase Rep server
=09
=09
This simple test program:
=09
use strict;
use warnings;
use DBI;
my $dbh =3D DBI->connect('dbi:Sybase:server=3DREPP', 'REPP_login',
'REPP_passwd', {RaiseError =3D> 1});
my $dummy =3D 6;
=09
causes this:
=09
Server message number=3D17001 severity=3D10 state=3D0 line=3D0
server=3DREPP
text=3DNo SRV_OPTION handler installed.OpenClient message: LAYER =3D
(1)
ORIGIN =3D (1) SEVERITY =3D (1) NUMBER =3D (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=3D2056 severity=3D12 state=3D0 line=3D0
server=3DREPP
text=3DLine 1, character 8: Incorrect syntax with 'select'.
persicom@nydux-ast401 (DEV, uid=3D8030(persicom) gid=3D200(develop)
depth=3D0)
=09
using Perl 5.6.1, DBI 1.48 and DBD::Sybase 1.07.
=09
However, when using Perl 5.6.1, DBI 1.37 and DBD::Sybase 1.00, I
get
no error message.
=09
What DBI trace flags/envars do I neet to set in order to
diagnose this?
=09
--
Matthew O. Persico
=09
=09
=09
=09
This message and any attachments (the "message") is
intended solely for the addressees and is confidential.
If you receive this message in error, please delete it and
immediately notify the sender. Any use not in accord with
its purpose, any dissemination or disclosure, either whole
or partial, is prohibited except formal approval. The internet
can not guarantee the integrity of this message.
BNP PARIBAS (and its subsidiaries) shall (will) not
therefore be liable for the message if modified.
=09
---------------------------------------------
=09
Ce message et toutes les pieces jointes (ci-apres le
"message") sont etablis a l'intention exclusive de ses
destinataires et sont confidentiels. Si vous recevez ce
message par erreur, merci de le detruire et d'en avertir
immediatement l'expediteur. Toute utilisation de ce
message non conforme a sa destination, toute diffusion
ou toute publication, totale ou partielle, est interdite, sauf
autorisation expresse. L'internet ne permettant pas
d'assurer l'integrite de ce message, BNP PARIBAS (et ses
filiales) decline(nt) toute responsabilite au titre de ce
message, dans l'hypothese ou il aurait ete modifie.
==================== =====3D=
==================== =====3D=
====================
This message (and any associated files) is intended only for the=20
use of the individual or entity to which it is addressed and may=20
contain information that is confidential, subject to copyright or
constitutes a trade secret. If you are not the intended recipient=20
you are hereby notified that any dissemination, copying or=20
distribution of this message, or files associated with this message,=20
is strictly prohibited. If you have received this message in error,=20
please notify us immediately by replying to the message and deleting=20
it from your computer. Messages sent to and from us may be monitored.=20
Internet communications cannot be guaranteed to be secure or error-free=20
as information could be intercepted, corrupted, lost, destroyed, arrive=20
late or incomplete, or contain viruses. Therefore, we do not accept=20
responsibility for any errors or omissions that are present in this=20
message, or any attachment, that have arisen as a result of e-mail=20
transmission. If verification is required, please request a hard-copy=20
version. Any views or opinions presented are solely those of the author=20
and do not necessarily represent those of the company.
==================== =====3D=
==================== =====3D=
====================
------_=_NextPart_001_01C63C54.5DB0FD3C--
Re: Can"t connect to Sybase Rep server
am 28.02.2006 13:55:17 von scoles
Hard to say for sure it could be one of a number of things. First what are
the details on your system version of perl and DBI and DBD:Oracle here are a
few things to check
Some causes could be
1) You have not installed
http://search.cpan.org/~mschwern/ExtUtils-MakeMaker-6.30/lib /ExtUtils/MakeMaker.pm
MakeMaker.pl mod
2) It is installed but you do not have proper RWE permission to use it
3) You may not have C++ installed.
""Ammayappa SELVAKUMAR"" wrote in message
news:840CBA03650F8444B13DD04584D1F0822E5248@toms_ex_srv01.to mssa.com...
Dear All,
I was trying to install DBD-Oracle and am getting the following error
while execuritng
perl Makefile.PL
Can't locate ExtUtils/MakeMaker.pm in @INC (@INC contains:
Can anyone help me...
Regards
Selva
-------- Message d'origine--------
De: michael.peppler@bnpparibas.com
[mailto:michael.peppler@bnpparibas.com]
Date: mar. 28.02.2006 07:54
À: matthew.persico@gmail.com
Cc: dbi-users@perl.org
Objet: Re: Can't connect to Sybase Rep server
This is a known problem, and has been fixed in either 1.07 or
1.07_01.
DBD::Sybase tries to see if chained transactions are supported
at startup,
and tries to find the @@version of the server. Both of these
requests fail
against a replication server, but the failure is expected, so
should simply
be hidden from the user...
Michael
Extranet
matthew.persico@gmail.com - 27/02/2006 20:39
To: dbi-users, Michael PEPPLER
cc:
Subject: Can't connect to Sybase Rep server
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'.
persicom@nydux-ast401 (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
This message and any attachments (the "message") is
intended solely for the addressees and is confidential.
If you receive this message in error, please delete it and
immediately notify the sender. Any use not in accord with
its purpose, any dissemination or disclosure, either whole
or partial, is prohibited except formal approval. The internet
can not guarantee the integrity of this message.
BNP PARIBAS (and its subsidiaries) shall (will) not
therefore be liable for the message if modified.
---------------------------------------------
Ce message et toutes les pieces jointes (ci-apres le
"message") sont etablis a l'intention exclusive de ses
destinataires et sont confidentiels. Si vous recevez ce
message par erreur, merci de le detruire et d'en avertir
immediatement l'expediteur. Toute utilisation de ce
message non conforme a sa destination, toute diffusion
ou toute publication, totale ou partielle, est interdite, sauf
autorisation expresse. L'internet ne permettant pas
d'assurer l'integrite de ce message, BNP PARIBAS (et ses
filiales) decline(nt) toute responsabilite au titre de ce
message, dans l'hypothese ou il aurait ete modifie.
============================================================ ==========
This message (and any associated files) is intended only for the
use of the individual or entity to which it is addressed and may
contain information that is confidential, subject to copyright or
constitutes a trade secret. If you are not the intended recipient
you are hereby notified that any dissemination, copying or
distribution of this message, or files associated with this message,
is strictly prohibited. If you have received this message in error,
please notify us immediately by replying to the message and deleting
it from your computer. Messages sent to and from us may be monitored.
Internet communications cannot be guaranteed to be secure or error-free
as information could be intercepted, corrupted, lost, destroyed, arrive
late or incomplete, or contain viruses. Therefore, we do not accept
responsibility for any errors or omissions that are present in this
message, or any attachment, that have arisen as a result of e-mail
transmission. If verification is required, please request a hard-copy
version. Any views or opinions presented are solely those of the author
and do not necessarily represent those of the company.
============================================================ ==========
Re: Can"t connect to Sybase Rep server
am 01.03.2006 01:53:24 von matthew.persico
> -------- Message d'origine--------
> De: michael.peppler@bnpparibas.com
> [mailto:michael.peppler@bnpparibas.com]
> Date: mar. 28.02.2006 07:54
> =C0: matthew.persico@gmail.com
> Cc: dbi-users@perl.org
> Objet: Re: Can't connect to Sybase Rep server
>
>
>
> This is a known problem, and has been fixed in either 1.07 or
> 1.07_01.
Must be 1.07_01 'cause I am running 1.07. I will download and try it.
is the _01 designation ok for production use?
And by the way, I hopefully fixed the email chaining - someone grabbed
the thread for a completely unrelated question.
>
> DBD::Sybase tries to see if chained transactions are supported
> at startup,
> and tries to find the @@version of the server. Both of these
> requests fail
> against a replication server, but the failure is expected, so
> should simply
> be hidden from the user...
>
> Michael
> matthew.persico@gmail.com - 27/02/2006 20:39
>
> To: dbi-users, Michael PEPPLER
>
> cc:
>
>
> Subject: Can't connect to Sybase Rep server
>
>
> This simple test program:
>
> use strict;
> use warnings;
> use DBI;
> my $dbh =3D DBI->connect('dbi:Sybase:server=3DREPP', 'REPP_login',
> 'REPP_passwd', {RaiseError =3D> 1});
> my $dummy =3D 6;
>
> causes this:
>
> Server message number=3D17001 severity=3D10 state=3D0 line=3D0
> server=3DREPP
> text=3DNo SRV_OPTION handler installed.OpenClient message: LAYER =3D
> (1)
> ORIGIN =3D (1) SEVERITY =3D (1) NUMBER =3D (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=3D2056 severity=3D12 state=3D0 line=3D0
> server=3DREPP
> text=3DLine 1, character 8: Incorrect syntax with 'select'.
> persicom@nydux-ast401 (DEV, uid=3D8030(persicom) gid=3D200(develop)
> depth=3D0)
>
> 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
>
Re: Can"t connect to Sybase Rep server
am 01.03.2006 16:06:44 von matthew.persico
On 2/28/06, Matthew Persico wrote:
> > -------- Message d'origine--------
> > De: michael.peppler@bnpparibas.com
> > [mailto:michael.peppler@bnpparibas.com]
> > Date: mar. 28.02.2006 07:54
> > =C0: matthew.persico@gmail.com
> > Cc: dbi-users@perl.org
> > Objet: Re: Can't connect to Sybase Rep server
> >
> >
> >
> > This is a known problem, and has been fixed in either 1.07 or
> > 1.07_01.
>
> Must be 1.07_01 'cause I am running 1.07. I will download and try it.
> is the _01 designation ok for production use?
Better yet, can anyone point me to where 1.07_01 lives? It's not on CPAN.
>
> And by the way, I hopefully fixed the email chaining - someone grabbed
> the thread for a completely unrelated question.
>
> >
> > DBD::Sybase tries to see if chained transactions are supported
> > at startup,
> > and tries to find the @@version of the server. Both of these
> > requests fail
> > against a replication server, but the failure is expected, so
> > should simply
> > be hidden from the user...
> >
> > Michael
>
> > matthew.persico@gmail.com - 27/02/2006 20:39
> >
> > To: dbi-users, Michael PEPPLER
> >
> > cc:
> >
> >
> > Subject: Can't connect to Sybase Rep server
> >
> >
> > This simple test program:
> >
> > use strict;
> > use warnings;
> > use DBI;
> > my $dbh =3D DBI->connect('dbi:Sybase:server=3DREPP', 'REPP_login',
> > 'REPP_passwd', {RaiseError =3D> 1});
> > my $dummy =3D 6;
> >
> > causes this:
> >
> > Server message number=3D17001 severity=3D10 state=3D0 line=3D0
> > server=3DREPP
> > text=3DNo SRV_OPTION handler installed.OpenClient message: LAYER =3D
> > (1)
> > ORIGIN =3D (1) SEVERITY =3D (1) NUMBER =3D (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=3D2056 severity=3D12 state=3D0 line=3D0
> > server=3DREPP
> > text=3DLine 1, character 8: Incorrect syntax with 'select'.
> > persicom@nydux-ast401 (DEV, uid=3D8030(persicom) gid=3D200(develop)
> > depth=3D0)
> >
> > 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
Re: Can"t connect to Sybase Rep server
am 01.03.2006 16:12:37 von matthew.persico
On 3/1/06, Matthew Persico wrote:
> On 2/28/06, Matthew Persico wrote:
> > > -------- Message d'origine--------
> > > De: michael.peppler@bnpparibas.com
> > > [mailto:michael.peppler@bnpparibas.com]
> > > Date: mar. 28.02.2006 07:54
> > > =C0: matthew.persico@gmail.com
> > > Cc: dbi-users@perl.org
> > > Objet: Re: Can't connect to Sybase Rep server
> > >
> > >
> > >
> > > This is a known problem, and has been fixed in either 1.07 or
> > > 1.07_01.
> >
> > Must be 1.07_01 'cause I am running 1.07. I will download and try it.
> > is the _01 designation ok for production use?
>
> Better yet, can anyone point me to where 1.07_01 lives? It's not on CPAN.
Never mind:
http://www.peppler.org/downloads/
>
> >
> > And by the way, I hopefully fixed the email chaining - someone grabbed
> > the thread for a completely unrelated question.
> >
> > >
> > > DBD::Sybase tries to see if chained transactions are supported
> > > at startup,
> > > and tries to find the @@version of the server. Both of these
> > > requests fail
> > > against a replication server, but the failure is expected, so
> > > should simply
> > > be hidden from the user...
> > >
> > > Michael
> >
> > > matthew.persico@gmail.com - 27/02/2006 20:39
> > >
> > > To: dbi-users, Michael PEPPLER
> > >
> > > cc:
> > >
> > >
> > > Subject: Can't connect to Sybase Rep server
> > >
> > >
> > > This simple test program:
> > >
> > > use strict;
> > > use warnings;
> > > use DBI;
> > > my $dbh =3D DBI->connect('dbi:Sybase:server=3DREPP', 'REPP_login',
> > > 'REPP_passwd', {RaiseError =3D> 1});
> > > my $dummy =3D 6;
> > >
> > > causes this:
> > >
> > > Server message number=3D17001 severity=3D10 state=3D0 line=3D0
> > > server=3DREPP
> > > text=3DNo SRV_OPTION handler installed.OpenClient message: LAYER =3D
> > > (1)
> > > ORIGIN =3D (1) SEVERITY =3D (1) NUMBER =3D (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=3D2056 severity=3D12 state=3D0 line=3D0
> > > server=3DREPP
> > > text=3DLine 1, character 8: Incorrect syntax with 'select'.
> > > persicom@nydux-ast401 (DEV, uid=3D8030(persicom) gid=3D200(develop)
> > > depth=3D0)
> > >
> > > 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
>
--
Matthew O. Persico
Re: Can"t connect to Sybase Rep server
am 01.03.2006 18:57:27 von matthew.persico
Edited for brevity
On 3/1/06, Matthew Persico wrote:
> On 3/1/06, Matthew Persico wrote:
> > On 2/28/06, Matthew Persico wrote:
> > > > -------- Message d'origine--------
> > > > De: michael.peppler@bnpparibas.com
> > > > [mailto:michael.peppler@bnpparibas.com]
> > > > Date: mar. 28.02.2006 07:54
> > > > =C0: matthew.persico@gmail.com
> > > > Cc: dbi-users@perl.org
> > > > Objet: Re: Can't connect to Sybase Rep server
> > > >
> > > >
> > > >
> > > > This is a known problem, and has been fixed in either 1.07 or
> > > > 1.07_01.
> > >
> > > Must be 1.07_01 'cause I am running 1.07. I will download and try it.
> > > is the _01 designation ok for production use?
> >
> > Better yet, can anyone point me to where 1.07_01 lives? It's not on CPA=
N.
>
> Never mind:
>
> http://www.peppler.org/downloads/
>
I did a diff on 1.07 vs 1.07_01 and I didn't notice any differences
that would indicate this problem being solved.
I also diffed 1.00 vs 1.07_01 and didn't notice any differences that
would indicate this problem being solved.
What should I be looking for?
Re: Can"t connect to Sybase Rep server
am 02.03.2006 09:32:07 von michael.peppler
Here's the code that checks to see if the remote server understands the=20
ct_option call.
/* Check to see if the server supports the ct_option() call */
if(!imp_dbh->optSupported) {
CS_BOOL val;
CS_RETCODE ret =3D ct_capability(connection, CS_GET,=20
CS_CAP_REQUEST,
CS_OPTION_GET, (CS_VOID*)&val);
if(DBIc_DBISTATE(imp_dbh)->debug >=3D 3)
PerlIO_printf(DBIc_LOGPIO(imp_dbh), " syb_db_login() ->=20
checking for ct_option support (ret =3D %d, val =3D %d)\n", ret, val);
if(ret !=3D CS_SUCCEED || val == CS_FALSE)
imp_dbh->optSupported =3D 0;
else
imp_dbh->optSupported =3D 1;
if(DBIc_DBISTATE(imp_dbh)->debug >=3D 3)
PerlIO_printf(DBIc_LOGPIO(imp_dbh), " syb_db_login() ->=20
ct_option is %ssupported\n", imp_dbh->optSupported == 1 ?"":"not ");
}
BTW - which version of DBI are you using?
Michael
Extranet
matthew.persico@gmail.com - 01/03/2006 18:57
=20
To: dbi-users
cc:=20
Subject: Re: Can't connect to Sybase Rep server
Edited for brevity
On 3/1/06, Matthew Persico wrote:
> On 3/1/06, Matthew Persico wrote:
> > On 2/28/06, Matthew Persico wrote:
> > > > -------- Message d'origine--------
> > > > De: michael.peppler@bnpparibas.com
> > > > [mailto:michael.peppler@bnpparibas.com]
> > > > Date: mar. 28.02.2006 07:54
> > > > =C0: matthew.persico@gmail.com
> > > > Cc: dbi-users@perl.org
> > > > Objet: Re: Can't connect to Sybase Rep server
> > > >
> > > >
> > > >
> > > > This is a known problem, and has been fixed in either 1.07 or
> > > > 1.07_01.
> > >
> > > Must be 1.07_01 'cause I am running 1.07. I will download and try=20
it.
> > > is the _01 designation ok for production use?
> >
> > Better yet, can anyone point me to where 1.07_01 lives? It's not on=20
CPAN.
>
> Never mind:
>
> http://www.peppler.org/downloads/
>
I did a diff on 1.07 vs 1.07_01 and I didn't notice any differences
that would indicate this problem being solved.
I also diffed 1.00 vs 1.07_01 and didn't notice any differences that
would indicate this problem being solved.
What should I be looking for?
This message and any attachments (the "message") is
intended solely for the addressees and is confidential.=20
If you receive this message in error, please delete it and=20
immediately notify the sender. Any use not in accord with=20
its purpose, any dissemination or disclosure, either whole=20
or partial, is prohibited except formal approval. The internet
can not guarantee the integrity of this message.=20
BNP PARIBAS (and its subsidiaries) shall (will) not=20
therefore be liable for the message if modified.=20
---------------------------------------------
Ce message et toutes les pieces jointes (ci-apres le=20
"message") sont etablis a l'intention exclusive de ses=20
destinataires et sont confidentiels. Si vous recevez ce=20
message par erreur, merci de le detruire et d'en avertir=20
immediatement l'expediteur. Toute utilisation de ce=20
message non conforme a sa destination, toute diffusion=20
ou toute publication, totale ou partielle, est interdite, sauf=20
autorisation expresse. L'internet ne permettant pas=20
d'assurer l'integrite de ce message, BNP PARIBAS (et ses
filiales) decline(nt) toute responsabilite au titre de ce=20
message, dans l'hypothese ou il aurait ete modifie.
Fwd: Can"t connect to Sybase Rep server
am 02.03.2006 16:21:24 von matthew.persico
---------- Forwarded message ----------
From: Matthew Persico
Date: Mar 2, 2006 10:21 AM
Subject: Re: Can't connect to Sybase Rep server
To: "michael.peppler@bnpparibas.com"
On 3/2/06, michael.peppler@bnpparibas.com
wrote:
> Here's the code that checks to see if the remote server understands the
> ct_option call.
>
> /* Check to see if the server supports the ct_option() call */
> if(!imp_dbh->optSupported) {
> CS_BOOL val;
> CS_RETCODE ret =3D ct_capability(connection, CS_GET,
> CS_CAP_REQUEST,
> CS_OPTION_GET, (CS_VOID*)&val);
> if(DBIc_DBISTATE(imp_dbh)->debug >=3D 3)
> PerlIO_printf(DBIc_LOGPIO(imp_dbh), " syb_db_login() ->
> checking for ct_option support (ret =3D %d, val =3D %d)\n", ret, val);
> if(ret !=3D CS_SUCCEED || val == CS_FALSE)
> imp_dbh->optSupported =3D 0;
> else
> imp_dbh->optSupported =3D 1;
> if(DBIc_DBISTATE(imp_dbh)->debug >=3D 3)
> PerlIO_printf(DBIc_LOGPIO(imp_dbh), " syb_db_login() ->
> ct_option is %ssupported\n", imp_dbh->optSupported == 1 ?"":"not ");
> }
>
> BTW - which version of DBI are you using?
>
DBI =3D 1.48. It also turns out that I have two versions of repserver
running 12.1 and 12.5. Too many variables in this equasion!
What I will do this weekend is set up a small program that simply
attempts to connect to a rep server. I will use the following matrix:
DBI/DBD RepServer Success?
1.37/1.00 12.1
1.48/1.07 12.1
1.37/1.00 12.5
1.48/1.07 12.5
What setting of DBI trace should I use to get useful diagnostics?
> Michael
>
>
>
>
> Extranet
> matthew.persico@gmail.com - 01/03/2006 18:57
>
>
> To: dbi-users
> cc:
> Subject: Re: Can't connect to Sybase Rep server
>
>
> Edited for brevity
>
> On 3/1/06, Matthew Persico wrote:
> > On 3/1/06, Matthew Persico wrote:
> > > On 2/28/06, Matthew Persico wrote:
> > > > > -------- Message d'origine--------
> > > > > De: michael.peppler@bnpparibas.com
> > > > > [mailto:michael.peppler@bnpparibas.com]
> > > > > Date: mar. 28.02.2006 07:54
> > > > > =C0: matthew.persico@gmail.com
> > > > > Cc: dbi-users@perl.org
> > > > > Objet: Re: Can't connect to Sybase Rep server
> > > > >
> > > > >
> > > > >
> > > > > This is a known problem, and has been fixed in either 1.07 or
> > > > > 1.07_01.
> > > >
> > > > Must be 1.07_01 'cause I am running 1.07. I will download and try
> it.
> > > > is the _01 designation ok for production use?
> > >
> > > Better yet, can anyone point me to where 1.07_01 lives? It's not on
> CPAN.
> >
> > Never mind:
> >
> > http://www.peppler.org/downloads/
> >
>
> I did a diff on 1.07 vs 1.07_01 and I didn't notice any differences
> that would indicate this problem being solved.
>
> I also diffed 1.00 vs 1.07_01 and didn't notice any differences that
> would indicate this problem being solved.
>
> What should I be looking for?
>
>
> This message and any attachments (the "message") is
> intended solely for the addressees and is confidential.
> If you receive this message in error, please delete it and
> immediately notify the sender. Any use not in accord with
> its purpose, any dissemination or disclosure, either whole
> or partial, is prohibited except formal approval. The internet
> can not guarantee the integrity of this message.
> BNP PARIBAS (and its subsidiaries) shall (will) not
> therefore be liable for the message if modified.
>
> ---------------------------------------------
>
> Ce message et toutes les pieces jointes (ci-apres le
> "message") sont etablis a l'intention exclusive de ses
> destinataires et sont confidentiels. Si vous recevez ce
> message par erreur, merci de le detruire et d'en avertir
> immediatement l'expediteur. Toute utilisation de ce
> message non conforme a sa destination, toute diffusion
> ou toute publication, totale ou partielle, est interdite, sauf
> autorisation expresse. L'internet ne permettant pas
> d'assurer l'integrite de ce message, BNP PARIBAS (et ses
> filiales) decline(nt) toute responsabilite au titre de ce
> message, dans l'hypothese ou il aurait ete modifie.
>
>
--
Matthew O. Persico
--
Matthew O. Persico