Weird message in db2diag.log
in [DB2]
|
From: dunleav1 on 10 Jul 2006 13:32 This is a bug that is corrected in FP12. I had to bind the db and the schema. Whoever applied the patchkit didn't bind the db correctly. Here's the IBM info: JR22451: SCHEDULED TASK HANGS AND NEVER FINISHES IN DB2 UDB V8.1 FP10 TASK CENTER Fixes are available DB2 Universal Database Version 8.1 FixPak 11 (also known as Version 8.2 FixPak 4 DB2 Universal Database Version 8.1 FixPak 12(also known as Version 8.2 FixPak 5) APAR status Closed as program error. Error description A scheduled task in the Task Center never finishes after upgrading to DB2 UDB Version 8.1 FixPak 10 (also known as DB2 UDB Version 8.2 FixPak 3). The Journal shows that the "Success" of the task is unknown; however, the job itself is completed. A DB2 Administration Server (DAS) trace shows that, because of a JNI error, the main DAS thread was unable to reconnect to the tools catalog database after executing the job successfully. The following error message is logged in the db2diag.log file: 2005-08-29-08.30.11.532000-300 I3142H386 LEVEL: Error PID : 512 TID : 4040 FUNCTION: DB2 Tools, DB2 administration server, MDUtility::connectMD, probe:10 DATA #1 : Sint32, 4 bytes -300 DATA #2 : Sint32, 4 bytes 0 DATA #3 : Sint32, 4 bytes 0 DATA #4 : String, 7 bytes TOOLSDB DATA #5 : String, 8 bytes SYSTOOLS DATA #6 : String, 4 bytes NULL
From: pshindle on 10 Jul 2006 16:40
dunleav1 wrote: > I have the following message in my db2diag.log file repeating every > minute. > Does anyone know what the error is ? > > 2006-07-10-10.27.08.921000-240 I95651H390 LEVEL: Error > PID : 3228 TID : 3240 > FUNCTION: DB2 Tools, DB2 administration server, MDUtility::connectMD, > probe:10 > DATA #1 : Sint32, 4 bytes > 1 > DATA #2 : Sint32, 4 bytes > -443 > DATA #3 : Sint32, 4 bytes > 38553 > DATA #4 : String, 7 bytes > TOOLSDB > DATA #5 : String, 8 bytes > SYSTOOLS > DATA #6 : String, 4 bytes > NULL |