HP3000-L Archives

October 1997, Week 3

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
"James J. Kanihan" <[log in to unmask]>
Reply To:
James J. Kanihan
Date:
Tue, 21 Oct 1997 01:48:32 GMT
Content-Type:
text/plain
Parts/Attachments:
text/plain (28 lines)
Hello MPE folks,

I've just discovered this amazingly informative newsgroup, so I hope
someone out there can help me.  So far, the HP Response Center sounds
like they're mostly guessing, and they haven't been able to help.  I'm
using Cognos Impromptu (version 4.01) to query an Allbase (version
A.G1.21) database, and I'm using the 32-bit ODBCLink/SE driver
(version E.55) under Windows NT Server 4.0, and MPE version 5.5.  If
the query tries to return a large (approx. 1 million) number of
records, it crashes with the error message "[ODBCLN32.DLL] Timeout on
data read" after about 15 minutes.  Cognos says that this is not their
message; it is being generated either by the database or ODBC driver.
When this whole thing started, we were using the old HP PC API Allbase
driver with Allbase version A.G1.14, and the error was slightly
different; the database generated a "Column out of range" error
immediately when the query was executed.  We tried the new ODBCLink/SE
driver and updated our Allbase version as per the HP Response Center's
suggestions, but we're still having problems.  In our SQLUTIL settings
for the Allbase DBE we have MAXIMUM TIMEOUT set to NONE and DEFAULT
TIMEOUT set to MAXIMUM.  On a DBE with the same structure but much
less data, everything runs fine.  If anyone out there is still with
me, I'd appreciate any insight you may have.

Thanks in advance,

Jim Kanihan
[log in to unmask]

ATOM RSS1 RSS2