|
Hi!
For a couple of nights now I have observed that at 18:00 diag.log is flooded with this message:
2008-11-18-18.13.20.151992+060 E672850E578 LEVEL: Warning
PID : 5102 TID : 183177832800 PROC : db2sysc 1
INSTANCE: thisinstance NODE : 001 DB : THISDB
APPHDL : 0-30480 APPID: 10.57.30.179.31107.081118171218
AUTHID : KONTO
EDUID : 112798 EDUNAME: db2agntp (THISDB) 1
FUNCTION: DB2 UDB, runtime interpreter, sqlriridc, probe:3471
DATA #1 : String, 62 bytes
thisnode is not the same as dynSectHdr->grid.recid.nodenumber
DATA #2 : unsigned integer, 2 bytes
1
DATA #3 : unsigned integer, 2 bytes
This goes on for about 20 minutes, then diag.log is saved as diag.log.sav and a new diag.log is created.
I have not noticed any impact on the system.
Can this be caused by a timeserver correcting the time at 1800?
DATA #1 : Build Level, 152 bytes
Instance "thisinstance" uses "64" bits and DB2 code release "SQL09051"
with level identifier "03020107".
Informational tokens are "DB2 v9.5.0.1", "s080328", "MI00225", Fix Pack "1".
DATA #2 : System Info, 440 bytes
System: Linux vfin8016 6 2 x86_64
CPU: total:4 online:4 Cores per socket:4 Threading degree per core:1
The instance uses 4 nodes on the same physical server.
--
Mvh
/dg
| 
