DB2DIAG.LOG MSG after Every Successful Load.

Fin

unread,

Jan 20, 2012, 10:07:56 PM1/20/12

to

I do a lot of LOADing CSV records from Rexx using the ADMIN_CMD to perform the load. The load works just fine but after every successful load I get the following msgs to my db2diag.log file.
I understand the :
Starting LOAD phase ...
Starting BUILD phase ...
Completed BUILD phase ... messages but why the
FUNCTION: DB2 UDB, runtime interpreter, sqlriInvokeInvoker, probe:170 warnings every time ? SQL464 error is regarding stored procedure dynamic result sets I think, is that to do with the ADMIN_CMD procedure having issues ? Anyway I can get rid of them ?

Thanks, regards, FIn.

Anyone got any clues as to how to get rid of them ?

2012-01-20-20.40.31.143000-300 I43879F576 LEVEL: Warning
PID : 7100 TID : 7444 PROC : db2syscs.exe
INSTANCE: DB2 NODE : 000 DB : TEST
APPHDL : 0-1374 APPID: *LOCAL.DB2.120121013338
AUTHID : DB2ADMIN
EDUID : 7444 EDUNAME: db2lfrm0
FUNCTION: DB2 UDB, database utilities, sqlulPrintPhaseMsg, probe:314
DATA #1 : String, 141 bytes
LOADID: 8044.2012-01-20-20.40.28.905000.0 (5;533)
Starting LOAD phase at 01/20/2012 20:40:31.142759. Table DB2ADMIN.TEST1

2012-01-20-20.40.31.565000-300 I44457F538 LEVEL: Warning
PID : 7100 TID : 7192 PROC : db2syscs.exe
INSTANCE: DB2 NODE : 000 DB : TEST
APPHDL : 0-1374 APPID: *LOCAL.DB2.120121013338
AUTHID : DB2ADMIN
EDUID : 7192 EDUNAME: db2lrid
FUNCTION: DB2 UDB, database utilities, sqlulPrintPhaseMsg, probe:314
DATA #1 : String, 104 bytes
LOADID: 8044.2012-01-20-20.40.28.905000.0 (5;533)
Completed LOAD phase at 01/20/2012 20:40:31.565301.

2012-01-20-20.40.31.565000-300 I44997F538 LEVEL: Warning
PID : 7100 TID : 7192 PROC : db2syscs.exe
INSTANCE: DB2 NODE : 000 DB : TEST
APPHDL : 0-1374 APPID: *LOCAL.DB2.120121013338
AUTHID : DB2ADMIN
EDUID : 7192 EDUNAME: db2lrid
FUNCTION: DB2 UDB, database utilities, sqlulPrintPhaseMsg, probe:314
DATA #1 : String, 104 bytes
LOADID: 8044.2012-01-20-20.40.28.905000.0 (5;533)
Starting BUILD phase at 01/20/2012 20:40:31.565571.

2012-01-20-20.40.32.027000-300 I45537F539 LEVEL: Warning
PID : 7100 TID : 7192 PROC : db2syscs.exe
INSTANCE: DB2 NODE : 000 DB : TEST
APPHDL : 0-1374 APPID: *LOCAL.DB2.120121013338
AUTHID : DB2ADMIN
EDUID : 7192 EDUNAME: db2lrid
FUNCTION: DB2 UDB, database utilities, sqlulPrintPhaseMsg, probe:314
DATA #1 : String, 105 bytes
LOADID: 8044.2012-01-20-20.40.28.905000.0 (5;533)
Completed BUILD phase at 01/20/2012 20:40:32.026828.

2012-01-20-20.40.32.193000-300 I46078F942 LEVEL: Warning
PID : 7100 TID : 8044 PROC : db2syscs.exe
INSTANCE: DB2 NODE : 000 DB : TEST
APPHDL : 0-1374 APPID: *LOCAL.DB2.120121013338
AUTHID : DB2ADMIN
EDUID : 8044 EDUNAME: db2agent (TEST)
FUNCTION: DB2 UDB, runtime interpreter, sqlriInvokeInvoker, probe:170
DATA #1 : String, 64 bytes
sqlriInvokeInvoker ignored because of prior condition, probe 170
DATA #2 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
sqlcaid : SQLCA sqlcabc: 136 sqlcode: 464 sqlerrml: 5
sqlerrmc: 1 0
sqlerrp : SQLCSMCB
sqlerrd : (1) 0x893E0019 (2) 0x00000019 (3) 0x00000000
(4) 0x00000000 (5) 0x00000000 (6) 0x00000000
sqlwarn : (1) (2) (3) (4) (5) (6)
(7) (8) (9) (10) (11)
sqlstate:

Mark A

unread,

Jan 21, 2012, 1:10:01 AM1/21/12

to

Change the message level for the diagnosis log to level 3 in the database manager configuration (db2
get dbm cfg).

Fin

unread,

Jan 21, 2012, 4:03:20 AM1/21/12

to

DIAGLEVEL was already set to 3, any other ideas ?

btw .. DB2 Express-C 9.7.4 64-bit on Windows 7 Pro SP1 64-bit.

Mark A

unread,

Jan 21, 2012, 9:40:56 AM1/21/12

to

On Sat, 21 Jan 2012 01:03:20 -0800, Fin wrote:

> DIAGLEVEL

My mistake. Level 3 includes warnings, so you will need level 2:

Valid values for this parameter are:

0 – No diagnostic data captured
1 – Severe errors only
2 – All errors
3 – All errors and warnings
4 – All errors, warnings and informational messages

db2 update dbm cfg using DIAGLEVEL 2

You may need to stop/stop instance to make sure all client connections get the new value.