If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

 
Go Back  dBforums > Database Server Software > DB2 > Sqlstate=57014

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 09-22-05, 17:34
ravman ravman is offline
Registered User
 
Join Date: Sep 2005
Posts: 4
Sqlstate=57014

I am querying a DB2 database, using VB.NET & the IBM ODBC drivers that were provided to me by our support group.

When I query the database, I get the following error:

"ERROR [HY008] [IBM][CLI Driver][DB2/NT] SQL0952N Processing was cancelled due to an interrupt. SQLSTATE=57014"

It's a very simple Select statement.

I have used both the ODBCDataAdaptor and the ExecuteReader objects in VB.NET and I still get the same error.

Has anyone had this error before and managed to resolve it? Do I need to change my ODBC drivers at all?

Thanks
Reply With Quote
  #2 (permalink)  
Old 09-22-05, 17:42
n_i n_i is offline
:-)
 
Join Date: Jun 2003
Location: Toronto, Canada
Posts: 5,054
How long does it take to return the error after the query is issued?

Find the file named db2cli.ini and check if QueryTimeoutInterval value is set too low.
Reply With Quote
  #3 (permalink)  
Old 09-22-05, 17:45
ravman ravman is offline
Registered User
 
Join Date: Sep 2005
Posts: 4
Times

From stepping thru the code, it queries the dataase and returns a result set. It's only when I then try to step thru the result set, does the error occur. I am going thru the Microsoft site and I think it might be an error relating to ADO.NET.

Ive not had this problem before with SQL Server or Oracle. I've only been using DB2 for a couple of weeks now, so these are all new problems to me.
Reply With Quote
  #4 (permalink)  
Old 09-23-05, 11:46
ravman ravman is offline
Registered User
 
Join Date: Sep 2005
Posts: 4
I fixed the problem

It turns out that there is a known issue with using the IBM DB2 drivers, when using Visual Studio & ADO.NET. ADO has a problem with the IBM ODBC drivers.

The only work around for this right now (until Microsoft develops a hotfix) is to use another ODBC driver, like Directconnect etc. I downloaded their drivers and it works fine now.
Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On