SEO

All,

I am receiving the error, "ERROR - no error information available", in my
application that accesses a PgSQL 7.4.3 DB. This application runs fine
against an Oracle db with the same structure. I have tried taking the SQL
statements out of the code and putting them in the psql command line to
verify them; they worked fine. I looked on the web and some others have had
a similar issue, but know one has a solid answer.

I was using the 8000101 version of the pgsql odbc driver and I tried
downloading a newer version (8010102). This didn't help...actually made it
worse.


Any help with this would be greatly appreciated!

TIA,
dw

Daniel Wilkerson
SPARTA, Inc.
13501 Ingenuity Drive - Suite 132
Orlando, Fl. 32826-3009
email:dwilkerson@ideorlando.org


---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly

> I am receiving the error, "ERROR - no error information available", in my

When you got the error? I can't reproduce your error here with informations
you posted.

> I was using the 8000101 version of the pgsql odbc driver and I tried
> downloading a newer version (8010102). This didn't help...actually made it
> worse.

What do you mean with "made it worse"? I'm sorry but we aren't crystal
gazers.

It's good idea to post mylog output at least. Or complete minimalistic
example with problem (data and program - source or executable).

Regards,

Luf

---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster

Luf,

I apologize for not being clear the first time. Below is a snippet from my
log that I think maybe the suspect. The SELECT statement below is one (of
many) from the code that is dying. I have attached my whole mylog file too.

As far as a scenario goes, I have a data adapter that is responsible for
handling the querying of the database and some queries are executing fine,
other are not (e.g. like the one below). The queries work fine against other
databases. To troubleshoot, I have copied the offending statements out of
the code to a sql editor to verify the queries; they are fine and do what
they are supposed to. I keep getting a Windows crash dialog box (the one
that asks if you would like to send a report to Microsoft) and it shows the
psqlodbc.dll as the offending module. The message displayed when you click
the, "Click Here" link after the text, "To see what data this error report
contains" is:

Error Signature
-------------------
AppName: ctia.icts.dcp_main.exe AppVer: 1.0.2166.29176 ModName:
psqlodbc.dll
ModVer: 8.0.1.1 Offset: 0001ffef


Hope this level of detail is enough. If not let me know.

Thanks!
dw


mylog snippet
-----------------------

[5564][SQLGetDiagRecW][5564]PGAPI_GetDiagRec entering rec=1[5564]****
PGAPI_ConnectError: hdbc=134127624 <0>
[5564]enter CC_get_error
[5564]enter CC_create_errormsg
[5564]msg = 'The buffer was too small for the ConnStrOut.'
[5564]exit CC_create_errormsg
[5564]exit CC_get_error
[5564]CC_get_error: status = 215, msg = #The buffer was too small for the
ConnStrOut.#
[5564] szSqlState = '01004',len=44, szError='(null)'
[5564]PGAPI_GetDiagRec exiting 1
[5564][SQLGetDiagRecW][5564]PGAPI_GetDiagRec entering rec=1[5564]****
PGAPI_ConnectError: hdbc=134127624 <46>
[5564]enter CC_get_error
[5564]exit CC_get_error
[5564]CC_get_error: status = 215, msg = #The buffer was too small for the
ConnStrOut.#
[5564] szSqlState = '(null)',len=44, szError='The buffer was too small
for the ConnStrOut.'
[5564]PGAPI_GetDiagRec exiting 0
[5564][[SQLGetDiagFieldW]] Handle=(2,7fea008) Rec=1 Id=8
[5564]PGAPI_GetDiagField entering rec=1[5564]PGAPI_GetDiagField exiting 0
[5564][[SQLGetDiagFieldW]] Handle=(2,7fea008) Rec=1 Id=9
[5564]PGAPI_GetDiagField entering rec=1[5564]PGAPI_GetDiagField exiting 0
[5564][[SQLGetDiagFieldW]] Handle=(2,7fea008) Rec=1 Id=10
[5564]PGAPI_GetDiagField entering rec=1[5564]PGAPI_GetDiagField exiting 0
[5564][[SQLGetDiagFieldW]] Handle=(2,7fea008) Rec=1 Id=11
[5564]PGAPI_GetDiagField entering rec=1[5564]PGAPI_GetDiagField exiting 0
[5564][SQLGetDiagRecW][5564]PGAPI_GetDiagRec entering rec=2[5564]****
PGAPI_ConnectError: hdbc=134127624 <0>
[5564]PGAPI_GetDiagRec exiting 100
[5564][SQLGetFunctions][5564][SQLGetInfoW(30)][5564]PGAPI_GetInfo:
entering...fInfoType=23
[5564]PGAPI_GetInfo: p='<NULL>', len=2, value=2, cbMax=2
[5564][SQLGetInfoW(30)][5564]PGAPI_GetInfo: entering...fInfoType=24
[5564]PGAPI_GetInfo: p='<NULL>', len=2, value=2, cbMax=2
[5564][SQLGetInfoW(30)][5564]PGAPI_GetInfo: entering...fInfoType=1750
[5564]CONN ERROR: func=PGAPI_GetInfo30, desc='', errnum=209,
errmsg='Unrecognized key passed to SQLGetInfo30.'
[5564]CONN ERROR: func=SQLGetInfoW(30), desc='', errnum=209,
errmsg='Unrecognized key passed to SQLGetInfo30.'
[5564][SQLGetConnectAttrW][5564]PGAPI_GetConnectAttr 1209
[5564][[SQLAllocHandle]][5564]PGAPI_AllocStmt: entering...
[5564]**** PGAPI_AllocStmt: hdbc = 134127624, stmt = 99068032
[5564]CC_add_statement: self=134127624, stmt=99068032
[5564][SQLGetStmtAttrW][5564]PGAPI_GetStmtAttr Handle=99068032 10010
[5564][SQLGetStmtAttrW][5564]PGAPI_GetStmtAttr Handle=99068032 10011
[5564][SQLGetStmtAttrW][5564]PGAPI_GetStmtAttr Handle=99068032 10012
[5564][SQLGetStmtAttrW][5564]PGAPI_GetStmtAttr Handle=99068032 10013
[5564][SQLSetStmtAttrW][5564]PGAPI_SetStmtAttr Handle=99068032 0,30
[5564]PGAPI_SetStmtOption: entering...
[5564]SetStmtOption: SQL_QUERY_TIMEOUT, vParam = 30
[5564][SQLGetConnectAttrW][5564]PGAPI_GetConnectAttr 1209
[5564][SQLSetStmtAttrW][5564]PGAPI_SetStmtAttr Handle=99068032 1228,0
[5564]PGAPI_SetStmtOption: entering...
[5564][SQLSetStmtAttrW][5564]PGAPI_SetStmtAttr Handle=99068032 1227,0
[5564]PGAPI_SetStmtOption: entering...
[5564][SQLExecDirectW][5564]PGAPI_ExecDirect: entering...
[5564]recycle statement: self= 99068032
[5564]PDATA_free_params: ENTER, self=99068456
[5564]**** PGAPI_ExecDirect: hstmt=99068032, statement='SELECT DISTINCT
nominal_value FROM doctrine WHERE (nominal_value IS NOT NULL)'
[5564]PGAPI_ExecDirect: calling PGAPI_Execute...
[5564]PGAPI_Execute: entering...
[5564]PGAPI_Execute: clear errors...
[5564]recycle statement: self= 99068032
[5564]PDATA_free_params: ENTER, self=99068456
[5564]Exec_with_parameters_resolved: copying statement params:
trans_status=1, len=77, stmt='SELECT DISTINCT nominal_value FROM doctrine
WHERE (nominal_value IS NOT NULL)'
[5564] stmt_with_params = 'SELECT DISTINCT nominal_value FROM doctrine
WHERE (nominal_value IS NOT NULL)'
[5564] Sending SELECT statement on stmt=99068032,
cursor_name='SQL_CUR05E7A880'
[5564]send_query(): conn=134127624, query='SELECT DISTINCT nominal_value
FROM doctrine WHERE (nominal_value IS NOT NULL)'
[5564]send_query: done sending query
[5564]in QR_Constructor
[5564]exit QR_Constructor
[5564]read 49, global_socket_buffersize=8192
[5564]send_query: got id = 'P'
[5564]send_query: got id = 'T'
[5564]QR_fetch_tuples: cursor = '', self->cursor=0
[5564]num_fields = 1
[5564]READING ATTTYPMOD
[5564]CI_read_fields: fieldname='nominal_value', adtid=1043, adtsize=-1,
atttypmod=45
[5564]QR_fetch_tuples: past CI_read_fields: num_fields = 1
[5564]MALLOC: tuple_size = 100, size = 800
[5564]next_tuple: inTuples = true, falling through: fcount = 101,
fetch_count = 101
[5564]qresult: len=0, buffer=''
[5564]end of tuple list -- setting inUse to false: this = 99067856
[5564]_next_tuple: 'C' fetch_total = 1 & this_fetch = 1
[5564]send_query: got id = 'Z'
[5564] done sending the query:
[5564]extend_column_bindings: entering ... self=99068168,
bindings_allocated=0, num_columns=1
[5564]exit extend_column_bindings
[5564]PGAPI_ExecDirect: returned 0 from PGAPI_Execute
[5564][SQLNumResultCols][5564]PGAPI_NumResultCols: entering...
[5564]SC_pre_execute: status = 3
[5564]PGAPI_NumResultCols: result = 99067856, status = 3, numcols = 1
[5564][SQLGetConnectAttrW][5564]PGAPI_GetConnectAttr 1209
[5564][SQLColAttributeW][5564]PGAPI_ColAttributes: entering..col=1 1011
len=6144.
[5564]SC_pre_execute: status = 3
[5564]**** PGAPI_ColAtt: result = 99067856, status = 3, numcols = 1
[5564]colAttr: col 0 field_type = 1043
[5564]PGAPI_ColAttr: COLUMN_NAME = 'nominal_value'
[5564][SQLGetConnectAttrW][5564]PGAPI_GetConnectAttr 1209
[5564][SQLColAttributeW][5564]PGAPI_ColAttributes: entering..col=1 2
len=4096.
[5564]SC_pre_execute: status = 3
[5564]**** PGAPI_ColAtt: result = 99067856, status = 3, numcols = 1
[5564]colAttr: col 0 field_type = 1043
[5564]getCharColumnSize: type=1043, col=0, unknown = 0
[5564]COLUMN_TYPE=-9
[5564][[SQLFetch]][5564]PGAPI_ExtendedFetch: stmt=99068032

-----Original Message-----
From: pgsql-odbc-owner@postgresql.org
[mailtogsql-odbc-owner@postgresql.org]On Behalf Of Ludek Finstrle
Sent: Tuesday, December 06, 2005 5:33 PM
To: DWilkerson
Cc: pgsql-odbc@postgresql.org
Subject: Re: [ODBC] ERROR - no error information available


> I am receiving the error, "ERROR - no error information available", in my

When you got the error? I can't reproduce your error here with informations
you posted.

> I was using the 8000101 version of the pgsql odbc driver and I tried
> downloading a newer version (8010102). This didn't help...actually made it
> worse.

What do you mean with "made it worse"? I'm sorry but we aren't crystal
gazers.

It's good idea to post mylog output at least. Or complete minimalistic
example with problem (data and program - source or executable).

Regards,

Luf

---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster


---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster

> psqlodbc.dll
> ModVer: 8.0.1.1 Offset: 0001ffef

Please try upgrade to 8.1.1.2 (or development 8.1.1.3). There are
a lot of changes.

If it doesn't help I need whole mylog output. This one isn't display your
datasource settings. It started with error message but it doesn't show
which steps lead to the error. Feel free to pack the mylog into zip
or rar and mail it to me direclty.
Unfortunately I'm still unable to reproduce it here.

Regards,

Luf

---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?

http://archives.postgresql.org

> I apologize for not being clear the first time. Below is a snippet from my
> log that I think maybe the suspect. The SELECT statement below is one (of
> many) from the code that is dying. I have attached my whole mylog file too.

I can't make you happy. I see no problem in whole mylog :-(
If I don't reproduce it here I can't help you. I'm sorry.
The first "error" is SQL_SUCCESS_WITH_INFO and there isn't supported
SQL_DTC_TRANSITION_COST in SQLGetInfo in the second one.
But both situation are ok.

Could you trace your program and said me where the error raise?

Regards,

Luf

---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster

Thanks for your help Luf, I sincerely appreciate it! I am not familiar with
the ODBC log format and the items in it, so I can't truly make heads or
tails of it. Your help was of great service! If the log is not showing
anything out of the ordinary, then it might be something else.

The funny part is that the driver I was originally using has been working
fine for a long time. This just recently started happening. I loaded new
data into the database for testing purposes, however, this **shouldn't**
have caused any grief like this. I mentioned before, the SQL statements were
tested outside of the code using psql. Weird.

The error(s) happen intermittently in the code when tracing. Sometimes
things go nuts when it's in the initialization phase, and other times it's
deeper in the app when buttons are clicked, etc. Again, weird.


I will keep digging at it. Let me know if new suggestions pop-up!

Regards,
dw

-----Original Message-----
From: Ludek Finstrle [mailto:luf@pzkagis.cz]
Sent: Wednesday, December 07, 2005 3:52 PM
To: DWilkerson
Cc: pgsql-odbc@postgresql.org
Subject: Re: [ODBC] ERROR - no error information available


> I apologize for not being clear the first time. Below is a snippet from my
> log that I think maybe the suspect. The SELECT statement below is one (of
> many) from the code that is dying. I have attached my whole mylog file
too.

I can't make you happy. I see no problem in whole mylog :-(
If I don't reproduce it here I can't help you. I'm sorry.
The first "error" is SQL_SUCCESS_WITH_INFO and there isn't supported
SQL_DTC_TRANSITION_COST in SQLGetInfo in the second one.
But both situation are ok.

Could you trace your program and said me where the error raise?

Regards,

Luf


---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings

> The funny part is that the driver I was originally using has been working
> fine for a long time. This just recently started happening. I loaded new

Do you change ODBC driver for PgSQL? What version had you used?
Could you create mylog with ODBC driver which was working properly?

> data into the database for testing purposes, however, this **shouldn't**

Are you sure? What about unicode chars? I see no unicode char but
traversing so much fetched rows ...
Did you try ANSI driver?

> The error(s) happen intermittently in the code when tracing. Sometimes
> things go nuts when it's in the initialization phase, and other times it's
> deeper in the app when buttons are clicked, etc. Again, weird.

Could you log in your application if ODBC driver return what you expect?

Regards

Luf

---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings