Skip site navigation (1) Skip section navigation (2)

Re: Acucobol, ODBC and Postgres

From: Jonathan Foy <thefoy(at)gmail(dot)com>
To: Korry Douglas <korry(dot)douglas(at)enterprisedb(dot)com>
Cc: pgsql-odbc(at)postgresql(dot)org
Subject: Re: Acucobol, ODBC and Postgres
Date: 2010-04-07 20:55:45
Message-ID: o2t4b46b5f01004071355g93b8de2bw77cb75a72a55f573@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-odbc
The application is actually launched from a windows box via a thin
client...I'm not sure how I would run it with strace.

However, I'm fairly sure I'm pulling in the correct one, if I change the
port it fails, as it should.  Switch it back and it works. Of all the odbc
entries on the system (from a root level search for both odbc.ini and
.odbc.ini), only the one has this database entry in it at all.  And it WILL
connect, just not do what I want it to.


On Wed, Apr 7, 2010 at 4:06 PM, Korry Douglas <
korry(dot)douglas(at)enterprisedb(dot)com> wrote:

> I'm trying to configure the postgres odbc driver with our Acucobol
>> application (5.2 and 8.1), and was hoping that someone out there might have
>> some experience with this.
>>
>> The application currently connects to our postgres databases (8.1.3 up to
>> 8.4.2) without issue.  The problem came up when I started trying to use
>> pgbouncer.  I had it up and running from the command line, but connections
>> coming from the application are rejected due to a "bad packet header", which
>> seems to be because the connect packets are coming in with V2 in the data,
>> and pgbouncer only supports V3.  So, we downloaded the latest driver,
>> compiled it (RHEL 5.4), and (in theory) recompiled cobol with the new
>> library (libodbcpsql.so.2.0.0) linked in.  There was no apparent change.
>>
>> The application can still parse the odbc.ini file to get the database
>> name, server, port, user, and password, but any additional settings seem to
>> be ignored.  I can't get any logging, I can't set the Protocol version...I'm
>> not convinced that the proper driver is being used.
>>
>> Does anyone have any ideas?  Pulling my hair out...
>>
>
> I would start by running strace on your application while it is trying to
> connect.  When I've run into kind of problem that you describe, I've found
> that the ODBC Driver Manager is reading the wrong odbc.ini file (for
> example, reading from /etc/odbc.ini when I expected
> /usr/local/etc/odbc.ini).
>
> Just run:
>
>        $ strace -o /tmp/myapp.trc <your application name goes here>
>
> Then look through the /tmp/myapp.trc file, searching for attempts to open
> odbc.ini, odbcinst.ini, and the libodbcpsql.so library.
>
>                        -- Korry
>
>
>
>
> -----------------------------------------------------------------------
> Korry Douglas
> Senior Database Dude
> EnterpriseDB Corporation
> The Enterprise Postgres Company
>
> Phone: (804)241-4301
> Mobile: (620) EDB-NERD
>
>
>

In response to

pgsql-odbc by date

Next:From: Jonathan FoyDate: 2010-04-07 21:05:16
Subject: Re: Acucobol, ODBC and Postgres
Previous:From: Jonah H. HarrisDate: 2010-04-07 20:15:56
Subject: Re: Acucobol, ODBC and Postgres

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group