suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IT36633 Status: Closed

DB2IPERIODICWATCH TIMEOUT MESSAGE

product:
DB2 FOR LUW / DB2FORLUW / B10 - DB2
Problem description:
In Db2 v11.1.4.5, the instance periodic task may run into a
timeout incorrectly leading to all future iterations of the task
to be skipped. This message can be safely ignored.

Example db2diag.log message of timeout hit -

2020-06-20-23.59.39.902856+120 I17858456E1272        LEVEL:
Error
PID     : 35016                TID : 46960685868800  PROC :
db2sysc 2
INSTANCE: db2inst1             NODE : 002
HOSTNAME: host1.domain.com
EDUID   : 5263                 EDUNAME: db2iperiodicWatch1 2
FUNCTION: DB2 UDB, base sys utilities,
sqleSALInstancePeriodicTaskWatch, probe:1087
MESSAGE : Timeout is reached for db2iperiodicWatch to complete.
DATA #1 : unsigned integer, 8 bytes
1
DATA #2 : unsigned integer, 8 bytes
110
DATA #3 : unsigned integer, 8 bytes
110
DATA #4 : SQLE_INSTANCE_PERIODIC_TASK_INFO,
PD_TYPE_SQLE_INSTANCE_PERIODIC_TASK_INFO, 88 bytes
db2iperiodicWatch EDU ID        = 5263
db2iperiodicExec EDU ID         = 5264
Total number of invocations     = 1811350
Total number of skips           = 3
Total number of spawn failures  = 0
Task Start Time                 = 2020-06-20-23.58.44.394670
Task End Time                   = 2020-06-20-23.58.39.894798
CALLSTCK: (Static functions may not be resolved correctly, as
they are resolved to the nearest symbol)
  [0] 0x00002AAAB0A07678 _Z32sqleSALInstancePeriodicTaskWatchPcj
+ 0x5D8
  [1] 0x00002AAAB27077BA sqloEDUEntry + 0x57A
  [2] 0x00002AAAAACD4DC5 /lib64/libpthread.so.0 + 0x7DC5
  [3] 0x00002AAABB2E176D clone + 0x6D


Example message of a future iteration of this task being skipped
-

2020-06-25-15.04.01.307345+120 I38140E952            LEVEL:
Warning
PID     : 35016                TID : 46913109878528  PROC :
db2sysc 2
INSTANCE: db2inst1             NODE : 002
HOSTNAME: host1.domain.com
EDUID   : 32                   EDUNAME: db2iperiodic 2
FUNCTION: DB2 UDB, base sys utilities,
sqleSALInstancePeriodicTaskMain, probe:295
MESSAGE : The previous iteration of this task is still running,
current
          iteration will be skipped.
DATA #1 : unsigned integer, 8 bytes
1
DATA #2 : signed integer, 4 bytes
0
DATA #3 : SQLE_INSTANCE_PERIODIC_TASK_INFO,
PD_TYPE_SQLE_INSTANCE_PERIODIC_TASK_INFO, 88 bytes
db2iperiodicWatch EDU ID        = 0
db2periodicExec EDU ID         = 5264
Total number of invocations     = 1811350
Total number of skips           = 79972
Total number of spawn failures  = 0
Task Start Time                 = 2020-06-20-23.58.44.394670
Task End Time                   = 2020-06-20-23.58.39.894798


This happens due to the way the timeout is calculated in this
Db2 version. The issue has been fixed in Db2 V11.1.4.6 and up.
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* ALL                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Apply v11.1 Mod 4 Fixpack 6 to DB2 database server           *
****************************************************************
Local Fix:
Restart DB2 instance.
Solution
Workaround
****************************************************************
* USERS AFFECTED:                                              *
* ALL                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Apply v11.1 Mod 4 Fixpack 6 to DB2 database server           *
****************************************************************
Comment
First fixed in v11.1 Mod 4 Fixpack 6
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
20.04.2021
22.04.2021
22.04.2021
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)