[IBM][CLI Driver][DB2/6000] SQL0952N - HELP

japuentem

I'm triyng to run this query

SELECT .NUMSUCURSALORIGEN, G.CLVORIGEN, G.CLVDESTINO, G.CLVTIPOSERVICIO, COUNT(DISTINCT(G.NUMEROGUIA)) AS NUMEROGUIAS, SUM(P.PESO) PESOREAL, SUM(P.LONGITUD*P.ALTO*P.ANCHO*1000/6) PESOVOL, SUM(FN_POSITIVO(MAYORRPK(P.PESO,P.LONGITUD*P.ALTO* P.ANCHO*1000/6))) PESOMAX
FROM DOCUMENTACION.GUIA AS G,DOCUMENTACION.PAQUETE AS P
WHERE P.NUMEROGUIA=G.NUMEROGUIA
AND P.CLVSITUACION<>20
AND G.FECHADOCUMENTACIONORIGEN>='2007-05-01-00.00.00.000000'
GROUP BY G.NUMSUCURSALORIGEN,G.CLVORIGEN,G.CLVDESTINO,
G.CLVTIPOSERVICIO
ORDER BY G.CLVORIGEN,G.NUMSUCURSALORIGEN

but i have this error
[IBM][CLI Driver][DB2/6000] SQL0952N Processing was cancelled due to an interrupt. SQLSTATE=57014

somebody tell my why please?

regards

Jun 27 '07 #1

r035198x

I'm triyng to run this query

SELECT .NUMSUCURSALORIGEN,G.CLVORIGEN,G.CLVDESTINO,G.CLVT IPOSERVICIO,COUNT(DISTINCT(G.NUMEROGUIA)) AS NUMEROGUIAS,SUM(P.PESO) PESOREAL,SUM(P.LONGITUD*P.ALTO*P.ANCHO*1000/6) PESOVOL,SUM(FN_POSITIVO(MAYORRPK(P.PESO,P.LONGITUD *P.ALTO*P.ANCHO*1000/6))) PESOMAX
FROM DOCUMENTACION.GUIA AS G,DOCUMENTACION.PAQUETE AS P
WHERE P.NUMEROGUIA=G.NUMEROGUIA
AND P.CLVSITUACION<>20
AND G.FECHADOCUMENTACIONORIGEN>='2007-05-01-00.00.00.000000'
GROUP BY G.NUMSUCURSALORIGEN,G.CLVORIGEN,G.CLVDESTINO,
G.CLVTIPOSERVICIO
ORDER BY G.CLVORIGEN,G.NUMSUCURSALORIGEN

but i have this error
[IBM][CLI Driver][DB2/6000] SQL0952N Processing was cancelled due to an interrupt. SQLSTATE=57014

somebody tell my why please?

regards

What is your QUERYTIMEOUTINTERVAL set to.
You may need to increase that in your db2cli.ini file.

Jun 28 '07 #2

japuentem

What is your QUERYTIMEOUTINTERVAL set to.
You may need to increase that in your db2cli.ini file.

I increase the QUERYTIMEOUTINTERVAL to 500 but it doesn't work

Jun 28 '07 #3

banic

Did you ever resolve this issue?
We have this issue in two of our applications.

I'm having the developers test for the -952 in the error handling after the SQL,
but we don't have a clue what to do after the error. Rerun the query? Disconnect and reconnect?
Any info would be greatly appreciated

Oct 10 '07 #4

banic

Here is the scoop...
I believe this is a new behavior in DB2 V8 CM.

In V7 the VB application had some setting for timeout. When the hand-shake with DB2 Z happens, application asks whether DB2 Z supports interrupt. DB2 Z responds that it does not support. So application did not send interrupt request. The query completed and passed all the requested data back to the application.

In V8, when the hand shake happens, DB2 Z responds that it now supports interrupt. The application now request an interrupt based on the same timeout setting. Now DB2 V8 honors the request and passes the SQL Return Code
-952 back to the application.

Oct 18 '07 #5