Subject: | |
From: | |
Reply To: | |
Date: | Wed, 13 Sep 2000 00:06:13 -0600 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
I have been working with the new drivers from the HP Website and have
a problem with BLOB fields (actually VARCHAR(3000)) from the HP 30000.
I can read 2 records fine but the third record hangs the PC program
until I abort the ODBC job on the 3000.
I have traced both the Client and Server and have found that I hang on
a SQLFetchScroll routine but it is not logged on the PC and nothing
seems to be getting to the Server. I think I must have left something
out of my calling sequence, but I get two records fine and always hang
on the third. Here is a trace from the Client that shows the second
record being read and then it hangs.
19:48:59 SQLSetStmtOption(0) hdbc=0 hstmt=1 fOption=SQL_ASYNC_ENABLE
vParam=0
19:48:59 SQLBindParam(0) hdbc=0 hstmt=1 ipar=1 fParamType=1 fCType=1
fSqlType=12 cbColDef=30 pcbValue=NULL rgbValue='cGL_DEPT'
19:48:59 SQLBindParam(0) hdbc=0 hstmt=1 ipar=2 fParamType=1 fCType=1
fSqlType=12 cbColDef=8 pcbValue=NULL rgbValue='TB'
19:48:59 SQLBindParam(0) hdbc=0 hstmt=1 ipar=3 fParamType=1 fCType=1
fSqlType=12 cbColDef=30 pcbValue=NULL rgbValue='GB'
19:48:59 SQLExecDirect(0) hdbc=0 hstmt=1 select * from dc.dcconstraint
WHERE CONSTRID = ? AND CSTTYPE = ? AND CSTBASEID = ? AND
DATELASTCHG IS NULL
19:48:59 SQLFetch(0) hdbc=0 hstmt=1
19:48:59 SQLGetData(1) hdbc=0 hstmt=1 icol=5 fCType=BINARY
cbValueMax=0 pcbValue=136 rgbValue=
19:48:59 SQLError(0) hdbc=0 hstmt=1
pfNativeError=-36,szErrorMsg=[ODBCLN32.DLL] Data truncated
19:48:59 SQLError(100) hdbc=0 hstmt=1 pfNativeError=0,szErrorMsg=
19:48:59 SQLGetData(0) hdbc=0 hstmt=1 icol=5 fCType=BINARY
cbValueMax=136 pcbValue=136 rgbValue=Select Table_Entry,Global_Data
from GB.Table_Dtl
Where (Global_Tbl='GD') and (%s %s '%s%s') Order By %s
Table_Entry
Entry;Description
BTW, I have tried the new ODBC drivers with the prior version of
Allbase and the seem to work ok and do take care of the cursor
disconnect problems. You need to upgrade your client along with the
server. This is not stressed on the HP site, but the old client
doesn't really fix the problems.
Rgds
Mel Rees
CMT, Inc
|
|
|