Latest versionsfixlist
11.1.0.6 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
Question in the chat LiveZilla Live Help

DB2 - Problem description

Problem IC63064 Status: Closed

THE DB2ACD PROCESS SHOWS HIGH CPU USAGE

product:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problem description:
the db2acd process shows high CPU usage, and the situation 
might persist even after the instance has been forced to 
shutdown. The issue can only be hit if Admin Task Scheduler 
(ATS) is being used 
 
For example, if you observe the CPU usage using the 
topas utility in AIX, you might see: 
 
 Name  PID  CPU%  PgSp Owner 
    db2fmp     3723314  75.7  13.1 db2inst1 
    db2fmp     3469516  19.4    9.9 db2inst2 
          NOTE: 
db2acd is actually a db2fmp process, so it is shown as 
db2fmp in above topas output. 
 
The stacks taken for the db2fmp process shows one of the 
thread is being stuck in the function 
AtsTaskList::~AtsTaskList(), 
i.e the destructor of the class AtsTaskList. 
 
For example: 
 
---------- tid# 5107911 (pthread ID: 772) ---------- 
 
0x0900000016e7deb0  AtsTaskList::~AtsTaskList()(??, ??) + 0x50 
 
0x0900000016e74628  AtsDbInfo::~AtsDbInfo()(??, ??, ??) + 0x128 
 
0x0900000016e73484  AtsDaemon::unregisterDb(char*)(??, ??) + 
0xa4 
0x0900000016e82448  db2HmonAtsPollDatabase(??) + 0x2c8 
 
0x0900000016e083d4  callFunction(0x1101768d0) + 0x674 
 
0x0900000016e08e88  hiCallExpr::reset(MonitoredObject*)(??, ??) 
+ 0x1a8 
0x0900000016dfe8d4 
HealthIndicator::reset(MonitoredObject*)(??,??) +  0x74 
 
       0x0900000016decc84 
hiDataMaintainer::deleteObjectAndChildren(hiDataCollector&,Monit 
oredObject*&,unsignedint)(??, ??, ??, ??) + 0x1c4 
0x0900000016dec6b8  hiDataMaintainer::clearObjects()(??) + 0x258 
 
0x0900000016de3c24  hiDataCollector::updateRefreshSets()(??) + 
0x444 
0x0900000016e97f5c  hmonMainLoop(HmonMainStruct*)(??) + 0x75c 
 
0x0900000016e964f8  hmonMain(??) + 0x1b8 
0x0900000016e0c5e0  hmonThreadWrapper(void*)(0x1100b9a90) + 
0x300 
0x09000000001864f4  _pthread_body(??) + 0xdc
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All users using Administrative Task Scheduler (ATS)          * 
* toautomate the execution of tasks might experience the       * 
* issue.                                                       * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* the db2acd process shows high CPU usage, and the             * 
* situationmight persist even after the instance has been      * 
* forced toshutdown. The issue can only be hit if Admin Task   * 
* Scheduler(ATS) is being used.For example, if you observe the * 
* CPU usage using the topasutility in AIX, you might see:Name  * 
* PID  CPU%  PgSp Ownerdb2fmp    3723314  75.7  13.1           * 
* db2inst1db2fmp    3469516  19.4    9.9 db2inst2NOTE:  db2acd * 
* is actually a db2fmp process, so it is shownas db2fmp in     * 
* above topas output.The stacks taken for the db2fmp process   * 
* shows one of thethread is being stuck in the                 * 
* functionAtsTaskList::~AtsTaskList(),i.e the destructor of    * 
* the class AtsTaskList.For example:---------- tid# 5107911    * 
* (pthread ID: 772) ----------0x0900000016e7deb0               * 
* AtsTaskList::~AtsTaskList()(??, ??) +0x500x0900000016e74628  * 
* AtsDbInfo::~AtsDbInfo()(??, ??, ??) +0x1280x0900000016e73484 * 
*  AtsDaemon::unregisterDb(char*)(??, ??)                      * 
* +0xa40x0900000016e82448  db2HmonAtsPollDatabase(??) +        * 
* 0x2c80x0900000016e083d4  callFunction(0x1101768d0) +         * 
* 0x6740x0900000016e08e88                                      * 
* hiCallExpr::reset(MonitoredObject*)(??,??) +                 * 
* 0x1a80x0900000016dfe8d4HealthIndicator::reset(MonitoredObject* 
* +                                                            * 
* 0x740x0900000016decc84hiDataMaintainer::deleteObjectAndChildre 
* ??, ??, ??) + 0x1c40x0900000016dec6b8                        * 
* hiDataMaintainer::clearObjects()(??)                         * 
* +0x2580x0900000016de3c24                                     * 
* hiDataCollector::updateRefreshSets()(??)+                    * 
* 0x4440x0900000016e97f5c  hmonMainLoop(HmonMainStruct*)(??)   * 
* +0x75c0x0900000016e964f8  hmonMain(??) +                     * 
* 0x1b80x0900000016e0c5e0                                      * 
* hmonThreadWrapper(void*)(0x1100b9a90)                        * 
* +0x3000x09000000001864f4  _pthread_body(??) + 0xdc           * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 UDB for Linux, Unix and Windows Version       * 
* 9.5Fix Pack 6                                                * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows

Solution
Problem was first fixed in Version 9.5 Fix Pack 6
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
09.09.2009
25.05.2010
25.05.2010
Problem solved at the following versions (IBM BugInfos)
9.5.FIX,
9.5.FP6
Problem solved according to the fixlist(s) of the following version(s)
This site uses cookies to make it easier for us to provide you with our services. By using our site you agree to the use of cookies.