how to understand error

L_DBA_L · #1 (**permalink**) 09-29-09, 18:47

How to understand error:

FUNCTION: DB2 UDB, database utilities, DIAG_ERROR, probe:0
DATA #1 : String, 146 bytes
LOADID: 12752.2009-09-29-04.11.39.987815.5 (12;14)
Failed to lock table and fix TCB , -2147221458, (nil), Detected in
file:sqluTarget.C, Line:2966

db2girl · #2 (**permalink**) 09-30-09, 10:02

You can use "db2diag -rc -2147221458"

L_DBA_L · #3 (**permalink**) 09-30-09, 18:48

okay. I do not understand why put this information in db2diag.log. How DBA knows about fix TCB and -2147221458, (nil), Detected in file:sqluTarget.C, Line:2966. No useful for me.

db2girl · #4 (**permalink**) 10-02-09, 12:04

Quote:

Originally Posted by L_DBA_L

okay. I do not understand why put this information in db2diag.log. How DBA knows about fix TCB and -2147221458, (nil), Detected in file:sqluTarget.C, Line:2966. No useful for me.

db2 support needs this information in order to debug problems

Cougar8000 · #5 (**permalink**) 10-02-09, 12:32

Quote:

Originally Posted by L_DBA_L

okay. I do not understand why put this information in db2diag.log. How DBA knows about fix TCB and -2147221458, (nil), Detected in file:sqluTarget.C, Line:2966. No useful for me.

Where do you suggest db2 logs this information?

Using Bella's suggestion earlier I was able to decipher what the error was on my side with out calling to Mother Ship.

Internet Services

Web Development

Digital Marketing

Consumer Tech