| |
|
If this is your first visit, be sure to check out the FAQ by clicking the link above.
You may have to register before you can post: click the register link above to proceed.
To start viewing messages, select the forum that you want to visit from the selection below.
|
 |
08-23-07, 03:53
|
|
Registered User
|
|
Join Date: Dec 2006
Posts: 3
|
|
|
Strange messages in db2diag.log
|
|
I have a partitioned (3 servers 6 partitions) DB2 vers 9 fp2 64 bits database.
When I use db2 top or run for example:
db2_all db2 get snapshot for application applid *N0.db2inst1.070823051832 |grep "rows read"
I get this message in db2diag.log file:
2007-08-23-09.48.01.507402+120 I993048E403 LEVEL: Warning
PID : 30618 TID : 183029672288PROC : db2agent (instance) 5
INSTANCE: db2inst1 NODE : 005
APPHDL : 5-616 APPID: *N5.db2inst1.070823074801
FUNCTION: DB2 UDB, database monitor, sqm_check_user_system_times, probe:5
DATA #1 : String, 51 bytes
recalculated time is incorrect 132 930000 0 10000 0
2007-08-23-09.48.01.510982+120 I993452E397 LEVEL: Warning
PID : 30618 TID : 183029672288PROC : db2agent (instance) 5
INSTANCE: db2inst1 NODE : 005
APPHDL : 5-616 APPID: *N5.db2inst1.070823074801
FUNCTION: DB2 UDB, database monitor, sqm_check_user_system_times, probe:4
DATA #1 : String, 45 bytes
time has gone backwards 206 680000 206 680000
Have anyone seen this?
regards
/christofer
|
|
08-23-07, 07:22
|
|
:-)
|
|
Join Date: Jun 2003
Location: Toronto, Canada
Posts: 4,449
|
|
Quote:
|
Originally Posted by chrfr
Have anyone seen this?
|
Probably not, but if I were you I would check that system time is properly synchronized between the servers.
|
|
08-23-07, 07:46
|
|
Registered User
|
|
Join Date: Dec 2006
Posts: 3
|
|
|
|
Well, It looks like an easy one but the time is synchronized.
/Christofer
|
|
08-23-07, 09:45
|
|
:-)
|
|
Join Date: Jun 2003
Location: Toronto, Canada
Posts: 4,449
|
|
Quote:
LI72267: REPEATED SQM_CHECK_USER_SYSTEM_TIMES MSGS WITH FREQENT SNAPSHOT OCCURS ONLY ON 64BIT X86_64 PROCCESSORS.
APAR status
OPEN
Error description
ERROR DESCRIPTION:
Repeated messages from sqm_check_user_system_times about time
going backwards.
These messages might be due to the snapshot commands executed
frequently and the monitor not finding a time difference between
the current snapshot command with respect to the previous
executed snapshot command.
The details are as below.
PID : 23929 TID : 182958416320PROC :
db2agntp 0
INSTANCE: db2inst1 NODE : 000
APPHDL : 0-1045
FUNCTION: DB2 UDB, database monitor,
sqm_check_user_system_times, probe:5
DATA #1 : String, 49 bytes
recalculated time is incorrect 1 80000 0 110000 0
2007-02-22-18.26.46.013225+330 I1634E343 LEVEL: Warning
PID : 23929 TID : 182958416320PROC :
db2agntp 0
INSTANCE: db2inst1 NODE : 000
APPHDL : 0-1045
FUNCTION: DB2 UDB, database monitor,
sqm_check_user_system_times, probe:5
DATA #1 : String, 49 bytes
recalculated time is incorrect 1 80000 0 100000 0
2007-02-22-18.26.46.055319+330 I1978E343 LEVEL: Warning
PID : 23929 TID : 182958416320PROC :
db2agntp 0
INSTANCE: db2inst1 NODE : 000
APPHDL : 0-1045
FUNCTION: DB2 UDB, database monitor,
sqm_check_user_system_times, probe:5
DATA #1 : String, 49 bytes
recalculated time is incorrect 1 80000 0 100000 0
2007-02-22-18.26.51.155428+330 I2322E334 LEVEL: Warning
PID : 6435 TID : 182958416320PROC :
db2agntp 28
INSTANCE: db2inst1 NODE : 028
APPHDL : 0-1045
FUNCTION: DB2 UDB, database monitor,
sqm_check_user_system_times, probe:3
DATA #1 : String, 39 bytes
time has gone backwards 6 90000 6 90000
2007-02-22-18.26.51.155980+330 I2657E338 LEVEL: Warning
PID : 6435 TID : 182958416320PROC :
db2agntp 28
INSTANCE: db2inst1 NODE : 028
APPHDL : 0-1045
FUNCTION: DB2 UDB, database monitor,
sqm_check_user_system_times, probe:3
DATA #1 : String, 43 bytes
time has gone backwards 22 340000 22 340000
2007-02-22-18.26.51.156216+330 I2996E338 LEVEL: Warning
PID : 6435 TID : 182958416320PROC :
db2agntp 28
INSTANCE: db2inst1 NODE : 028
APPHDL : 0-1045
FUNCTION: DB2 UDB, database monitor,
sqm_check_user_system_times, probe:3
DATA #1 : String, 43 bytes
time has gone backwards 30 900000 30 900000
LOCAL FIX:
DBM diaglevel can be changed to 0.
!!!!CAUTION!!!!: This will eleminate ALL messages from the
db2diag.log >>>0 - No diagnostic data captured<<<
NOTE:
The message is not an indication of any serious problem with
database integrity or database engine stability. The only reason
the message is seen is the addition of some debug code added to
fp14.
|
http://www-1.ibm.com/support/entdocv...UpdateReferer=
|
|
08-24-07, 01:48
|
|
Registered User
|
|
Join Date: Dec 2006
Posts: 3
|
|
Thank you!
I understand that it has something to do with the snapshots, but have not find a fix.
For me there is no option setting diaglevel to 0.
Maybe there will be a fix in a future fixpack.
/christofer
|
|
08-24-07, 04:32
|
|
Registered User
|
|
Join Date: Jan 2007
Location: Jena, Germany
Posts: 2,662
|
|
Could you run the snapshots less frequently? From the description I gather that this would be a solution as well.
__________________
Knut Stolze
IBM DB2 Analytics Accelerator
IBM Germany Research & Development
|
|
| Thread Tools |
Search this Thread |
|
|
|
| Display Modes |
 Linear Mode
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
|
|
dBforums
>
Strange messages in db2diag.log
