From: Sathyaram Sannasi on
I notice that there is a difference between the system time and the
start/stop time of utilities.
For example, in the db2diag file entry below, the diaglog entry time
shows 4 mins more than the load start time.


2008-11-26-12.24.04.365000+240 I588034H480 LEVEL: Warning
PID : 4196 TID : 5120 PROC : db2syscs.exe
INSTANCE: EDW NODE : 000 DB : SAMPLE
APPHDL : 0-2528 APPID: 127.0.0.1.16143.081126082137
AUTHID : DB2ADMIN
EDUID : 5120 EDUNAME: db2agent (SAMPLE) 0^M
FUNCTION: DB2 UDB, database utilities, sqluvtld_route_in, probe:837^M
DATA #1 : <preformatted>
Starting LOAD operation (Q) (5) (R).

2008-11-26-12.24.04.443000+240 I588516H559 LEVEL: Warning
PID : 4196 TID : 7496 PROC : db2syscs.exe
INSTANCE: EDW NODE : 000 DB : SAMPLE
APPHDL : 0-2528 APPID: 127.0.0.1.16143.081126082137
AUTHID : DB2ADMIN
EDUID : 7496 EDUNAME: db2lfrm0 0
FUNCTION: DB2 UDB, database utilities, sqlulPrintPhaseMsg, probe:311
DATA #1 : String, 120 bytes
LOADID: 5120.2008-11-26-12.24.04.365000.0 (2;710)
Starting LOAD phase at 11/26/2008 12:20:45.723431. Table DB2ADMIN.T1

When checking the database history file, the load start time
corresponds to the diaglog entry file above, ie 1224

I have noticed a similar discrepancy for BACKUP also.

How do I 'synchronize' the two?

The database is DB2 9.5 FP 2a on Win 2003.

Thanks in Advance