Hi,
I am about to make a change to DBD::ODBC with respect to cygwin
environments. If you use cygwin and unixODBC instead of cygwin and MS
ODBC Driver manager could you please let me know or the next release of
DBD::ODBC may not work for you without tinkering with it.
Thanks.
Martin
--
Martin J
Yes.
Thank you again.
Best regards,
Scott...
On Jun 30, 2009, at 11:52 AM, Martin Evans wrote:
Scott Stansbury wrote:
Getting closer :)
I'm trying to connect to a SQL Server 2008 instance from a CentOS5
box:
unixODBC: 2.2.14
FreeTDS:0.82
Easysoft: odbc-sqlserver-1.1.26-
Scott Stansbury wrote:
> Getting closer :)
>
> I'm trying to connect to a SQL Server 2008 instance from a CentOS5 box:
>
> unixODBC: 2.2.14
> FreeTDS:0.82
> Easysoft: odbc-sqlserver-1.1.26-linux-x86 (this morning, thank you
> again Martin and Wez...)
>
On Thu, 25 Jun 2009 21:40:07 +0100
"Martin J. Evans" wrote:
> >
> I'm not sure the --enable-rtldgroup=no works now because of libtool
> changes. I think you may need to configure unixODBC then edit the
> file and delete the LT_GROUP. This appears to be an
On Fri, 26 Jun 2009 17:47:13 +0100
Martin Evans wrote:
> col wrote:
> > So far nothing suggested to apply in the compile stage is fixing it.
>
> Can I just verify whether you have configured unixODBC then removed
> the LT_GLOBAL from the dlopen call then configured again and e
Getting closer :)
I'm trying to connect to a SQL Server 2008 instance from a CentOS5 box:
unixODBC: 2.2.14
FreeTDS:0.82
Easysoft: odbc-sqlserver-1.1.26-linux-x86 (this morning, thank you
again Martin and Wez...)
osql/isql work fine with both the FreeTDS and the Easysoft dr
col wrote:
> On Fri, 26 Jun 2009 08:44:28 +0200 "John Escott"
> wrote:
>
>> (the first reply in the same page) helpful, since unixODBC 2.2.8 is
>> the default version in RHEL3 and a recent Fedora containing 2.2.11
>> worked correctly.
>
> John -
On Fri, 26 Jun 2009 08:44:28 +0200
"John Escott" wrote:
> (the first reply in the same page) helpful, since unixODBC 2.2.8 is
> the default version in RHEL3 and a recent Fedora containing 2.2.11
> worked correctly.
John --
Thanks for your reply. Actually, the problem is con
e reminded me why this can happen.
>
>Thanks *very* much for that.
>
>> See
>> http://www.easysoft.com/support/kb/kb00664.html
>>
>http://groups.google.com/group/perl.dbi.users/browse_thread/thread/995131d999ca388/370b10f358e31729?hl=en&lnk=gst&q=Segmen>tation+fault+on+R
e links. I had already run across this and attempted to
rebuild unixODBC --enable-rtldgroup=no to no apparent effect. I'll try again.
It is probably down to using RTLD_GLOBAL on the dlopen call which
causes symbols to be resolved top down instead of from where the
symbol was found to be undef
thanks for the links. I had already run across this and attempted to
rebuild unixODBC --enable-rtldgroup=no to no apparent effect. I'll try again.
>
> It is probably down to using RTLD_GLOBAL on the dlopen call which
> causes symbols to be resolved top down instead of from where the
Scott Stansbury wrote:
> I'm trying to connect to a SQL Server 2008 instance from a CentOS5 box:
>
> unixODBC: 2.2.14
> FreeTDS:0.82
> Easysoft: odbc-sqlserver-1.1.4-linux-x86 (trial for now)
>
> osql/isql worked fine with both the FreeTDS and the Easysoft dri
I'm trying to connect to a SQL Server 2008 instance from a CentOS5 box:
unixODBC: 2.2.14
FreeTDS:0.82
Easysoft: odbc-sqlserver-1.1.4-linux-x86 (trial for now)
osql/isql worked fine with both the FreeTDS and the Easysoft drivers.
Connecting to a SQL Server 2008 instance running
Setting LD_BIND_NOW *does* work in this situation, however. But it has to be
>> set outside the perl script.
>>
>> This lead me to adding /usr/lib/libtdsodbc.so to /etc/ld.so.preload.
>> Magically, all the segfault problems go away. But since this is only needed
>> for
et outside the perl script.
>
> This lead me to adding /usr/lib/libtdsodbc.so to /etc/ld.so.preload.
> Magically, all the segfault problems go away. But since this is only needed
> for DBD::ODBC, I think it's better to fix the problem there, or with
> unixODBC, which should
c/ld.so.preload. Magically,
all the segfault problems go away. But since this is only needed for DBD::ODBC,
I think it's better to fix the problem there, or with unixODBC, which should
successfully load libtdsodbc before it's needed, since it's linked to it. If
that's, indeed, the
col wrote:
> [x-posted to unixODBC list]
>
> Is not possible in this combination since many version updates now.
>
> I'd like to get current AND with a working configuration.
>
> Working tunnel: ssh u...@the.pub.ip.add -q -f -N -L 1799:192.168.243.140:1433
> (Yes,
[x-posted to unixODBC list]
Is not possible in this combination since many version updates now.
I'd like to get current AND with a working configuration.
Working tunnel: ssh u...@the.pub.ip.add -q -f -N -L 1799:192.168.243.140:1433
(Yes, tsql works, no problems with the tunnel.)
Very s
[EMAIL PROTECTED] wrote:
When I try to run a perl script that uses ODBC drivers to insert data
more than 7 rows I am getting the following error
DBD::ODBC::st execute failed: [unixODBC][FreeTDS][SQL
Server]Procedure has no parameters and arguments were supplied.
(SQL-42000)(DBD
When I try to run a perl script that uses ODBC drivers to insert data
more than 7 rows I am getting the following error
DBD::ODBC::st execute failed: [unixODBC][FreeTDS][SQL
Server]Procedure has no parameters and arguments were supplied.
(SQL-42000)(DBD: st_execute/SQLExecute err=-1
Hi folks.
I am attempting to get freetds to work with unixODBC. I found this
tutorial:
http://www.unixodbc.org/doc/FreeTDS.html
It calls for creating a file called tds.driver.template with the
following lines:
[FreeTDS]
Description = v0.63 with protocol v8.0
Driver = /usr
I think you would be wise to ask Netezza SQL who wrote the ODBC driver
as they should be able to tell you what the error means. This is not a
driver I know.
Martin
--
Martin J. Evans
Easysoft Limited
http://www.easysoft.com
On Tue, 2006-09-05 at 12:29 -0700, Loo, Peter # PHX wrote:
> Hi Martin,
Hi Martin,
Here it is. I have removed the host names.
$ cat /usr/local/etc/odbc.ini
[ODBC]
DebugFile = /tmp/oplhsodbc.log
TraceFile = /tmp/ihsodbc.log
Trace = 1
[ODBC Data Sources]
[AB01]
Driver= /usr/local/nz/lib/libnzsqlodbc.so
Description = NetezzaSQL ODBC
Servername
> Sent: Tuesday, September 05, 2006 11:45 AM
> To: dbi-users@perl.org
> Subject: RE: :ODBC::st execute failed: [unixODBC]ERROR: crossed reserve
> :Out of memory
>
> On Tue, 2006-09-05 at 12:34 -0600, Reidy, Ron wrote:
> > So, which is it - errors at 3.8M rows, or 350K rows?
Martin,
Here is the version:
$ perl -M'DBD::ODBC' -le 'print $DBD::ODBC::VERSION'
1.13
Peter
-Original Message-
From: Martin J. Evans [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 05, 2006 11:45 AM
To: dbi-users@perl.org
Subject: RE: :ODBC::st execute fai
use it has not inserted its
name into the error - this is a bug in itself - it should appear in [ ]
after [unixODBC]. The -1 is SQL_ERROR and there should be a native error
too - that is also missing. I've no idea why it shows "SQL-" - this also
seems incorrect.
This probably does not he
00 rows.
Peter
-Original Message-
From: Reidy, Ron [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 05, 2006 11:34 AM
To: Loo, Peter # PHX; DBI-Users
Subject: RE: :ODBC::st execute failed: [unixODBC]ERROR: crossed reserve
: Out of memory
So, which is it - errors at 3.8M rows, or 350K rows? When y
: Loo, Peter # PHX; Reidy, Ron; DBI-Users
Subject: RE: :ODBC::st execute failed: [unixODBC]ERROR: crossed reserve
: Out of memory
Now I am getting the following error after fetching approximately
350,000 rows.
DBD::ODBC::st fetch failed: [unixODBC] (SQL-)(DBD: st_fetch/SQLFetch
err=-1) at /usr
Now I am getting the following error after fetching approximately
350,000 rows.
DBD::ODBC::st fetch failed: [unixODBC] (SQL-)(DBD: st_fetch/SQLFetch
err=-1) at /usr/local/apps/ppv/devl/bin/sdl.pl line 228, line 53.
Peter
-Original Message-
From: Loo, Peter # PHX [mailto:[EMAIL
URE;
sub_exit();
}
print STDERR "RETURN STATEMENT HANDLE IS: $sth\n\n";
return($sth);
} #<=== (End of sub_execute)
Peter
-Original Message-
From: Reidy, Ron [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 05, 2006 10:41 AM
To: Loo, Peter # PHX; DB
-Users
Subject: DBD::ODBC::st execute failed: [unixODBC]ERROR: crossed reserve
: Out of memory
Hi,
Will you kindly tell me what this error message is talking about?
DBD::ODBC::st execute failed: [unixODBC]ERROR: crossed reserve : Out of
memory
(SQL-HY000)(DBD: st_execute/SQLExecute err=-1) at
Hi,
Will you kindly tell me what this error message is talking about?
DBD::ODBC::st execute failed: [unixODBC]ERROR: crossed reserve : Out of
memory
(SQL-HY000)(DBD: st_execute/SQLExecute err=-1) at
/usr/local/apps/common/devl/bin/GlobalRoutines.pm line 88, line 53.
Thanks.
Peter
unixODBC/FreeTDS on Linux
Hello,
I am using DBD:ODBC (unixODBC/FreeTDS) with Perl 5.8.5 on Solaris and I
am able to connect to a MS SQL 2000 database successfully. I am now
trying to migrate the app to RHEL3 and for some reason I cannot connect
to the same SQL db.
I can connect to the MS SQL db
Hello,
I am using DBD:ODBC (unixODBC/FreeTDS) with Perl 5.8.5 on Solaris and I
am able to connect to a MS SQL 2000 database successfully. I am now
trying to migrate the app to RHEL3 and for some reason I cannot connect
to the same SQL db.
I can connect to the MS SQL db using the isql tool. I
;
> Maybe our Intranet document will help you? I attached it. If not, I'll need a
> lot more info about what errors you're seeing.
>
> Cheers,
>
> j
>
I upgraded my server to FC4 now I'm using
GCC 4.00
Perl v5.8.6
unixODBC 2.2.11
freetds 0.63
Same results.
> > Not us. We use DBD::Sybase and FreeTDS to connect to MS-SQL from Linux.
> Could you give me a pointer on how to set this up?
> I did a couple of tests the other day but I couldn't make it work.
Maybe our Intranet document will help you? I attached it. If not, I'll need a
lot more info about
roblem, because when I call the scripts with
PERL_DL_NONLAZY=1 they work
Any ideas on how to make this work?
This is my setup:
* unixODBC-2.2.11-2, fresh build made sure that the rtlgroup flag was on
while building
* freetds-0.62.3-1.1.fc3.rf
* perl 5.8.5
Thanks in advance
Pablo
--
Pablo
> Has anyone made this work?
Not us. We use DBD::Sybase and FreeTDS to connect to MS-SQL from Linux.
j
Hello,
Has anyone made this work?
I've upgraded to unixODBC-2.2.11 with no luck (I checked the RTLGRUOP
flag and built the rpm mysql) with no luck.
I tried with a newer DBD::ODBC same result.
Any Ideas? Any info I can provide to solve this?
Thanks in advance for your help
On 23-Feb-2005 Walter Obermiller wrote:
> Martin,
>
> New deck of cards. I have completely cleaned out the perl-odbc
> environment and replaced it with:
>
>
> Unixodbc 2.2.10 (configured without threading enabled)
> perl 5.8.6 (unthreaded)
> DBI-1.47
> D
Martin,
New deck of cards. I have completely cleaned out the perl-odbc
environment and replaced it with:
Unixodbc 2.2.10 (configured without threading enabled)
perl 5.8.6 (unthreaded)
DBI-1.47
DBD::ODBC 1.13 (configured for 5.8.6 and unixodbc2.2.10)
unixODBC 2.2.10
DRIVERS
Martin,
I've decided to take a new tack, throwing out the suse DBD-ODBC and
compiling DBD-ODBC 1.13 from scratch, starting with a clean slate.
Martin J. Evans wrote:
if (DBIc_DEBUGIV(imp_dbh) >= 8)
PerlIO_printf(DBIc_LOGPIO(imp_dbh), "Driver connect '%s',
'%s', '%s'\n", dbname, uid, pwd);
1.1
On 23-Feb-2005 Walter Obermiller wrote:
> Martin,
>
> this is because as I said in my last mail, the program
> loses itself in an endless loop. The sql.log file (20 mb) for this
> execution shows a couple of zillion messages complaining about the
> adabas driver receiving an empty password
>
Martin,
this is because as I said in my last mail, the program
loses itself in an endless loop. The sql.log file (20 mb) for this
execution shows a couple of zillion messages complaining about the
adabas driver receiving an empty password
The question is: what is tacking an empty UID=;PWD=; ont
I'd certainly use -w:
Note: perl is running without the recommended perl -w option
There appears to be a bit missing from your trace. It should show
something like:
"Driver connect 'DSN=test;uid=Martin_Evans;pwd=easysoft;', '', ''"
after
dbih_setup_attrib(DBI::db=HASH(0x8248c00), H
pplications, drivers and driver managers problem on Linux
is. We think the problem is that the internal structure used by dlopen is bigger
when built threaded. You can reproduce this with an ODBC app built without
-D_REENTRANT an without linking with pthreads (e.g. without gcc -pthread) and
then r
ded my what the mixing
thread/non-thread applications, drivers and driver managers problem on Linux
is. We think the problem is that the internal structure used by dlopen is bigger
when built threaded. You can reproduce this with an ODBC app built without
-D_REENTRANT an without linking with pthrea
ler wrote:
Martin, thanks.
I checked. my unixodbc is indeed threaded.
The driver library however, is not:
/usr/local/lib/odbclib.so
/lib/libNoVersion.so.1 => /lib/libNoVersion.so.1 (0x400a9000)
linux-gate.so.1 => (0xe000)
libsqlrte.so => /usr/local/lib/libsqlrte.so (0x400ce0
ans
Easysoft Ltd, UK
Development
On 22-Feb-2005 Walter Obermiller wrote:
> Martin, thanks.
>
> I checked. my unixodbc is indeed threaded.
>
> The driver library however, is not:
>
>/usr/local/lib/odbclib.so
>/lib/libNoVersion.so.1 => /lib/libNoVersion.so.1 (0
Martin, thanks.
I checked. my unixodbc is indeed threaded.
The driver library however, is not:
/usr/local/lib/odbclib.so
/lib/libNoVersion.so.1 => /lib/libNoVersion.so.1 (0x400a9000)
linux-gate.so.1 => (0xe000)
libsqlrte.so => /usr/local/lib/libsqlrte.so (0x400ce000)
Quoting Walter Obermiller <[EMAIL PROTECTED]>:
> Martin,
>
> thanks for your reply.
>
> as to the version of unixodbc, I use what is part of SuSe 9.2:
>
> Name: unixODBC Relocations: (not relocatable)
> Version : 2.2.9 Vendor: SUS
Martin,
thanks for your reply.
as to the version of unixodbc, I use what is part of SuSe 9.2:
Name: unixODBC Relocations: (not relocatable)
Version : 2.2.9 Vendor: SUSE LINUX AG, Nuernberg, Germany
Release : 4 Build Date: Mo 04 Okt 2004 22:49:44
Is
I might be wrong - my info is well out of date... but on Linux, Perl built
multithreaded always segfaulted with unixODBC. I think this happened even if
unixODBC was built threaded (--enable-threads=yes - the default for unixODBC's
configure but I'd check your unixODBC was built threaded
Hi, all
I am experiencing a puzzling problem while trying to get an DBD::ODBC
connection (via unixODBC) working from a client machine A (Suse linux)
to a an ADABAS-D-11 database running on a remote machine (B, also Suse
linux)
-- Machine A (client)
Linux 2.6.8-2
I am experiencing an annoying problem getting an DBD::ODBC connection
(via unixODBC) working from a client machine A (Suse linux) to a an
ADABAS-D-11 database running on a remote machine (B, also Suse linux)
-- Machine A (client)
Linux 2.6.8-2
Perl
On Wed, 2005-01-05 at 09:48, Honza Pazdziora wrote:
> On Wed, Jan 05, 2005 at 08:55:26AM +0100, Cosimo Streppone wrote:
> >
> > I have successfully used this combination:
> >
> > - DBI :-)
> > - DBD::Sybase 1.04, compiled with $ENV{SYBASE}='/your/freetds/install'
> > - freetds 0.6x
>
> The comb
Honza Pazdziora wrote:
I have succesfully installed
freetds-0.62.3-1.1.fc3.rf from Dag Wieers's rpm repository
unixODBC-2.2.9-42
unixODBC-devel-2.2.9-42 from Fedora Core 3's rpm repository
DBD::ODBC 1.13 from sources from C
On Wed, Jan 05, 2005 at 08:55:26AM +0100, Cosimo Streppone wrote:
>
> I have successfully used this combination:
>
> - DBI :-)
> - DBD::Sybase 1.04, compiled with $ENV{SYBASE}='/your/freetds/install'
> - freetds 0.6x
The combination with DBD::Sybase used to work for me, but then in an
attempt t
Honza Pazdziora wrote:
On Wed, Jan 05, 2005 at 08:55:26AM +0100, Cosimo Streppone wrote:
> I have successfully used this combination:
>
> - DBI :-)
> - DBD::Sybase 1.04, compiled with $ENV{SYBASE}='/your/freetds/install'
> - freetds 0.6x
The combination with DBD::Sybase used to work for me, but th
driver
bypassing the driver manager (or vice versa).
If you imagine the process from calling DBI->connect:
1. DBI loads DBD::ODBC which is dependent on libodbc.so
2. call to SQLAllocHandle for the environment. libodbc.so is loaded so resolved
in unixODBC driver manager and handle returned.
3. c
Hello,
I have succesfully installed
freetds-0.62.3-1.1.fc3.rf from Dag Wieers's rpm repository
unixODBC-2.2.9-42
unixODBC-devel-2.2.9-42 from Fedora Core 3's rpm repository
DBD::ODBC 1.13 from sources from CPAN
On 09-Sep-2004 Christian Stalp wrote:
>
>> You don't call unixODBC. You setup a data source for unixODBC, then you
>> reference the datasource as if it was a dataserver. I just went through
>> this exercise. The odbc.ini and odbcinst.ini need to have the correct
&g
> You don't call unixODBC. You setup a data source for unixODBC, then you
> reference the datasource as if it was a dataserver. I just went through
> this exercise. The odbc.ini and odbcinst.ini need to have the correct
> entries for the source of your data. The name that is cr
You don't call unixODBC. You setup a data source for unixODBC, then you reference the
datasource as if it was a dataserver. I just went through this exercise. The odbc.ini
and odbcinst.ini need to have the correct entries for the source of your data. The
name that is created in brackets i
I tryed to call UnixODBC via DBI.
my $data_source = "dbi:UnixODBC:refdb";
$dbh = DBI->connect ( $data_source, $user, $password )
or die "unable to connect !\n";
.
and got :
install_driver(UnixODBC) failed: Can't locate DBD/UnixODB
Am Dienstag, 7. September 2004 11:09 schrieben Sie:
> > Hello there,
> > one brief question: needs UnixODBC the DBI or is it totally
> > indipendent?
> >
> > Gruss Christian
>
> DBI are Perl related. unixODBC it's a C library.
>
Sure, but there is
DBI does not need unixODBC.
If you want to use the DBD::ODBC driver under DBI you'll need an ODBC driver or
(more likely) an ODBC driver manager (like unixODBC) and an ODBC driver.
Martin
--
Martin J. Evans
Easysoft Ltd, UK
Development
On 07-Sep-2004 Christian Stalp wrote:
> Hello ther
Hello there,
one brief question: needs UnixODBC the DBI or is it totally indipendent?
Gruss Christian
--
Christian Stalp
Institut für Medizinische Biometrie, Epidemiologie und Informatik (IMBEI)
Obere Zahlbacher Straße 69
55131 Mainz
Tel.: 06131/ 17-6852
E-Mail: [EMAIL PROTECTED]
Internet
On Sat, 28 Dec 2002 03:16:02 -0500 Chris <[EMAIL PROTECTED]> wrote:
> Sorry for the spam! not sure what happened there - deepest apologies!
You should have trimmed the excess from your apology.
--
Mac :})
** I normally forward private questions to the appropriate mail list. **
Ask Smarter: htt
Sorry for the spam! not sure what happened there - deepest apologies!
On Fri, 27 Dec 2002 18:32:24 -0500, Chris <[EMAIL PROTECTED]> wrote:
Hello,
I was hoping that someone could help me out with my stored procedure problems...
Here is my code:
#!/usr/bin/perl -w
use DBI();
#connect to DB
my
Hello,
I was hoping that someone could help me out with my stored procedure
problems...
Here is my code:
#!/usr/bin/perl -w
use DBI();
#connect to DB
my $dbh = DBI->connect("DBI:ODBC:SBS",
"xx", "xx",
{'RaiseError' => 1});
DBI->trace(2);
my
Hello,
I was hoping that someone could help me out with my stored procedure
problems...
Here is my code:
#!/usr/bin/perl -w
use DBI();
#connect to DB
my $dbh = DBI->connect("DBI:ODBC:SBS",
"xx", "xx",
{'RaiseError' => 1});
DBI->trace(2);
my
Hello,
I was hoping that someone could help me out with my stored procedure
problems...
Here is my code:
#!/usr/bin/perl -w
use DBI();
#connect to DB
my $dbh = DBI->connect("DBI:ODBC:SBS",
"xx", "xx",
{'RaiseError' => 1});
DBI->trace(2);
my
this email for the
start of this email thread. The issue is a basic seg fault when using isql
to connect to a MS SQL 2k server. I have freetds0.60, unixODBC 2.2.2-3, and
Sybase 11.9 family of rpms installed on a redhat 7.2 linux. Using perl
5.8.0 with DBI and DBD::ODBC (most up to date versions
Hello again,
I was able to connect to mysql via isql (I'm having a difficult time with
postgresql). Do you think that puts unixODBC in the clear and I should look
around at other packages as the perpetrators of this seg fault? Or does
postgresql hold a significance that I'm not gettin
Nick...this is what I get:
[root@ns3 DBD-ODBC-0.43]# isql -v wibble
[unixODBC][Driver Manager]Data source name not found, and no default driver
specified
[ISQL]ERROR: Could not SQLConnect
I tried to used ODBCconfig to get connected to anything at this point,
postgres or tds but ODBCconfig seg
build]# isql -mn
Segmentation fault
.you get the idea...isql seg faults on most every command. --version is
the only one that doesn't seg fault. I upgrade to unixODBC 2.2.2 in hopes
of fixing this, but no avail.
Hi,
Try isql -v wibble
You "should" get a DSN not found error.
If
fault
.you get the idea...isql seg faults on most every command. --version is
the only one that doesn't seg fault. I upgrade to unixODBC 2.2.2 in hopes
of fixing this, but no avail.
Also, I've tried to recompile DBD::ODBC but make test fails...probably
because unixodbc is seg fau
Matthew,
You are stomping on shaky ground. The last I tried UnixODBC and FreeTDS was
..53 and I had issues. I haven't tried .60, but I'd suggest doing the
following:
1) Login as your www user (if possible) and try isql.
2) adding a logging function in FreeTDS'
e the version numbers that I'm running:
Freetds .60
UnixODBC 2.1.1-1
DBD::ODBC 0.43
DBI->connect(SQL) failed: [unixODBC]tds_connect failed (SQL-08001)(DBD:
db_login/SQLConnect err=-1) at cgiscript.cgi line 100
Connecting : [unixODBC]tds_connect failed (SQL-08001)(DBD:
db_login/SQLConne
ved.
Regards,
Jeff
>
>
> I'm sure I'm overlooking something really simple, but I can't find any
> documentation to help troubleshoot my problem.
>
> When running a cgi script that uses DBI and the DBD::ODBC pm,
> this is error
> message is deposited into
I'm sure I'm overlooking something really simple, but I can't find any
documentation to help troubleshoot my problem.
When running a cgi script that uses DBI and the DBD::ODBC pm, this is error
message is deposited into my www error logs.
DBI->connect(SQL) failed: [unixODBC]
EMAIL PROTECTED]'
> Subject: RE: Problem installing DBD:ODBC(UnixODBC).
>
>
> I tried to make out the exact error. This is using iODBC in
> mycase, But the
> same applies for unixODBC also. I have both.
> To make out the error, i tried to compile dbdimp.c alone with
I tried to make out the exact error. This is using iODBC in mycase, But the
same applies for unixODBC also. I have both.
To make out the error, i tried to compile dbdimp.c alone with erroff option
to suppress the warnings.
Here is the error.
janarthp@sys1:/u/janarthp/DBD> cc -c -erroff
-
for the next few weeks.
Regards,
Jeff
> -Original Message-
> From: Janarthanan, Prasanna [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, September 25, 2002 2:13 AM
> To: Janarthanan, Prasanna; '[EMAIL PROTECTED]';
> '[EMAIL PROTECTED]'; '[EMAIL PROTECTED]&
oblem installing DBD:ODBC(UnixODBC).
Its fine..
i tried it ... errors are at dbdimp.c.
ERROR
-
janarthp@sys1:/u/janarthp/DBD> make
/usr/local/bin/perl -I/usr/local/lib/perl5/5.6.1/sun4-solaris
-I/usr/local/lib/perl5/5.6.1 -MExtUtils::Command -e mkpath blib/lib/DBD/ODBC
rm -f bli
usr/local/lib/perl5/5.6.1/ExtUtils/xsubpp
-typemap /usr/local/lib/perl5/5.6.1/ExtUtils/typemap ODBC.xs > ODBC.xsc &&
mv ODBC.xsc ODBC.c
cc -c -I/u/janarthp/ODBC/unixODBC/include -I.
-I/usr/local/lib/perl5/site_perl/5.6.1/sun4-solaris/auto/DBI
-I/usr/local/include -I/usr/include -I/usr/local/g
:
CCCMD = $(CC) -c $(DEFINE) $(INC) $(CCFLAGS) $(OPTIMIZE) \
$(PERLTYPE) $(MPOLLUTE) $(DEFINE_VERSION) \
$(XS_DEFINE_VERSION)
This will make sure unixODBC comes first. Every time you run Makefile.PL,
you will have to perform this edit. I do not believe that changing
Makefile.PL in
Prasanna,
I'm not sure what's really happening other than there must be some sqlext.h
in your /usr/include or /usr/local/include *before* it gets to sqlext.h
that's defined by unixODBC. It looks as if it's not looking in ODBCHOME...I
think, if you haven't, try *insta
Here is the complete perl MakeFile and make.
Iam able to connect to the database using isql.
---
janarthp@sys1:/u/janarthp/DBD> perl Makefile.PL -o /u/janarthp/ODBC/unixODBC
Configuring DBD::ODBC ...
>>> Remember to actually *READ* the README file!
And re-read it
Please post the output of makeifle.pl and all of make. I believe it's not
properly picking up the unixODBC headers.
regards,
Jeff
> -Original Message-
> From: Janarthanan, Prasanna [mailto:[EMAIL PROTECTED]]
> Sent: Saturday, September 21, 2002 5:09 AM
> To:
hi,
I now installed the unixODBC Driver manager and tested with isql. Its
working fine. Still get problem when running 'make' after makeFile.PL of
DBD:ODBC.
A piece of that error:
"dbdimp.c", line 1232: warning: improper pointer/integer combination: arg #1
"dbdi
does anyone know where i can find documentation on how to properly link
DBD::ODBC to unixODBC?
On Thursday 28 February 2002 11:08, Ken Miller wrote:
> Well, there wasn't a problem with DBI at all.
>
> Problem was (and still is, actually) that I had a reference loop. Th
i am getting an error message tds_connect failed message when i try to
connect to a database through isql -v dbname sa password, i also get an
error message about constructing property list when i try to add another
dsn in odbcconfig. anyone gt an idea.
The water is more murky now...
>
> On 30-Jan-2002 Jeff Urlwin wrote:
> > Tim,
> >
> > Ok -- that was a big help in describing the problem and letting me
> > understand it. Right now, here's the situation:
> > DBD::ODBC *assumes* that all binds are of type VARCHAR
> and only when
> > overid
On 30-Jan-2002 Jeff Urlwin wrote:
> Tim,
>
> Ok -- that was a big help in describing the problem and letting me
> understand it. Right now, here's the situation:
> DBD::ODBC *assumes* that all binds are of type VARCHAR and only when
> overidden on the bind_col will it actually change that
> From: Tim Harsch [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, January 29, 2002 8:35 PM
> To: Jeff Urlwin; [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]; Jeff Urlwin
> Subject: RE: [unixODBC-DEV] - Re: String data, right truncation error
> int
>
>
> Here it is! and than
DBD:Sybase
option would be better supported, as the freeTDS coders are not that focused on
ODBC.
>
>
> Jeff
>
> >
> > Hi
> >I am having problems working with the DBD::ODBC driver.
> >
> >I am using unixODBC and FreeTDS connecting to MS SQL Ser
[EMAIL PROTECTED]]
> Sent: Friday, October 26, 2001 7:48 PM
> To: Amit Gandre; [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]
> Subject: RE: unixODBC and FreeTDS to MS SQL Server.
>
>
> Well, I'm not especially solid on the FreeTDS. I did not realize that
> FreeTDS supplied a
Well, I'm not especially solid on the FreeTDS. I did not realize that
FreeTDS supplied an ODBC driver. I thought that FreeTDS was to be used with
DBD::Sybase to talk to SQL Server.
Jeff
>
> Hi
>I am having problems working with the DBD::ODBC driver.
>
> I am using
1 - 100 of 102 matches
Mail list logo
