Prev: SQL1224N - A database agent could not be started to service a request
Next: No remote connections available
From: Serge Rielau on 9 Jun 2006 08:43
eap90210 wrote:
> Big thanks again.
> After DIAGLEVEL=4 , in the db2diag.log file I find this information
> [cut]
> 2006-06-09-14.24.25.571166+120 I20992C949 LEVEL: Error
> PID : 33556 TID : 1 PROC : inv_crea_dett
> INSTANCE: inet NODE : 000
> APPID : *LOCAL.inet.060609122424
> FUNCTION: DB2 UDB, oper system services, sqlofica, probe:10
> DATA #1 : Hexdump, 136 bytes
> 0x20001328 : 5351 4C43 4120 2020 0000 0088 FFFF FF98 SQLCA ........
> 0x20001338 : 0013 3DFF 4956 4F5F 494E 5445 524E 4F20 ..=.IVO_INTERNO
> 0x20001348 : FF4A 4F49 4E20 2020 2020 2020 2020 2020 .JOIN
> 0x20001358 : 2020 2020 2020 2020 2020 2020 2020 2020
> 0x20001368 : 2020 2020 2020 2020 2020 2020 2020 2020
> 0x20001378 : 2020 2020 2020 2020 5351 4C4E 5030 3132 SQLNP012
> 0x20001388 : 801A 006D 0000 0000 0000 0000 0000 0000 ...m............
> 0x20001398 : FFFF FD3F 0000 0000 2020 2020 2020 2020 ...?....
> 0x200013A8 : 2020 2034 3236 3031 42601
> [cut]
>
> 2006-06-09-14.24.25.658745+120 I22946C332 LEVEL: Info
> PID : 33556 TID : 1 PROC : inv_crea_dett
> INSTANCE: inet NODE : 000
> APPID : *LOCAL.inet.060609122424
> MESSAGE : SQO semop=> pSSemSetID:
> DATA #1 : Hexdump, 4 bytes
> 0x20C239FC : 017C 000F .|..
>
> 2006-06-09-14.24.25.659124+120 I23279C390 LEVEL: Info
> PID : 33556 TID : 1 PROC : inv_crea_dett
> INSTANCE: inet NODE : 000
> APPID : *LOCAL.inet.060609122424
> FUNCTION: DB2 UDB, DRDA Communication Manager, sqljcReceive, probe:30
> MESSAGE : CCI Error:
> DATA #1 : Hexdump, 4 bytes
> 0x2FF22328 : 0000 0047 ...G
>
> 2006-06-09-14.24.25.675458+120 I23670C377 LEVEL: Info
> PID : 33556 TID : 1 PROC : inv_crea_dett
> INSTANCE: inet NODE : 000
> APPID : *LOCAL.inet.060609122424
> FUNCTION: DB2 UDB, DRDA Communication Manager, sqljcReceive, probe:30
> RETCODE : ZRC=0x8136001C=-2127167460=SQLZ_RC_NO_CONNECTION, SQLT_SQLJC
> "No connection"
>
> 2006-06-09-14.24.25.716831+120 I24048C550 LEVEL: Info
> PID : 33556 TID : 1 PROC : inv_crea_dett
> INSTANCE: inet NODE : 000
> APPID : *LOCAL.inet.060609122424
> FUNCTION: DB2 UDB, DRDA Communication Manager, sqljcReceive, probe:30
> DATA #1 : String, 242 bytes
> CALL STACK:
> [0] 0xD1537544 sqljcReceive__FP10sqljCmnMgr + 0x158
> [1] 0xD154A890 sqljrDrdaArDisconnect__FP7UCintfc + 0x1C0
> [2] 0xD15751FC sqleUCdisconnect + 0x64
> [3] 0xD1574EFC sqleUCtermAllCtx + 0x210
> [4] 0xD1528558 sqleterm__FcP5sqlca + 0x50
>
> Now Do you have any idea, suggest or other for to help me ?
Darn, I hoped DB2 would dump the statement text and not just the error.
I'll ask to get that fixed for the future.
Anyway... have you ever done a CLI trace? I think that's the next step.
I don't buy that what you logged is what DB2 saw.
The parser is to robust and central to be generating syntax errors for
no good reason.
Feel free to send me the code that is generating the query and the log.
Maybe I can eyeball it.

Cheers
Serge
--
Serge Rielau
DB2 Solutions Development
IBM Toronto Lab

IOD Conference
http://www.ibm.com/software/data/ondemandbusiness/conf2006/
First  |  Prev  | 
Pages: 1 2
Prev: SQL1224N - A database agent could not be started to service a request
Next: No remote connections available