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

During a recent DB2 to SQL Server conversion, I received the following run-time exception:

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

A little research showed me that the error typically occurs when a SQL query against a DB2 database runs an excessively long time. To address or get around this, you can adjust the CommandTimeout property of the DB2Command object. Increase the value to allow more time for your query.

While there's quite a few links concerning this issue, the following was most helpful:

http://www-01.ibm.com/support/docview.wss?uid=swg21424265

Addendum

Ideally, you should look into why the query ran so long in the first place. In my case, I found that a a single row in my Invoices table (and likewise in my Payments table) had some issues with a pseudo foreign key. That is, someone was using a column like a foreign key, there was no official foreign key constraint which used this column, and at some point the values for this row were in an invalid state. Thus, the query I was using was most likely caught in some sort of circular Hell.

Since I didn't and couldn't know what the proper values for this row should be, I ended up changing my exception handling (a trusty try...catch statement) so that in the Release build the application would log the offending row and continue on with the remaining rows.

Comments

Post a Comment

Popular posts from this blog

Using Reference Aliases

Image
I recently ran across a situation where two different libraries shared identical namespaces and class names. Visual Studio complained anytime I used one of these classes that it was an ambiguous reference. I needed both libraries -- each contained some unique elements -- so I couldn't ditch one or the other. But, as I said, anytime I tried to use a class that was common (again, via the class name and namespace), I received the ambiguous reference error. This was a real problem, so say the least. However, C# provides a way to specify exactly which library (reference) you mean when you use an object that's common to two or more libraries. Simply put, you use an extern alias  statement. The concept is fairly simple: Give the reference an alias (I used the Properties windows for the reference). Add an extern alias statement, putting it before your using statements. Add a using statement, which effectively links a specific object through the extern alias statement to th
Read more

List of Visual Studio Keyboard Shortcuts

Here's a link to a great list of keyboard shortcuts for Visual Studio: 149 Shortcuts for Visual Studio 2015 (Windows) While there's no need to memorize the list (that's why someone has created a cheat sheet, after all), it certainly doesn't hurt to look over the list from time to time and try to add one more command to your repertoire.
Read more