DB2 - Problem description
Problem IT23474 | Status: Closed |
DB2READLOG API SOMETIMES SLOW DOWN UNDER HEAVY WORKLOAD. | |
product: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
Problem description: | |
The db2ReadLog with DB2READLOG_QUERY action may take several seconds. This problem can occur only with DB2READLOG_QUERY option. It can occur more likely on heavy workload, more likely with multiple concurrent read log agents, and more likely on purescale. If you take the db2trc or the stack trace for the slow down agent running db2ReadLog API, you will see the agent takes much time in sqloWaitEDUWaitPost called from sqlpshrScanClose as follows: 483747 35.493804810 ... | sqlpgReadLogAPI entry [eduid 63257 eduname db2agent] ..(snip).. 483759 35.493847931 ... | | | | sqlpgReadLogCleanUpShredderScan entry [eduid 63257 eduname db2agent] ..(snip).. 483770 35.493853925 ... | | | | | sqlpshrScanClose entry [eduid 63257 eduname db2agent] ..(snip).. 484112 35.495044791 ... | | | | | | sqloPostEDUWaitPost entry [eduid 63257 eduname db2agent] 484113 35.495045318 ... | | | | | | sqloPostEDUWaitPost exit 484114 35.495045533 ... | | | | | | sqloPostEDUWaitPost entry [eduid 63257 eduname db2agent] 484115 35.495045826 ... | | | | | | sqloPostEDUWaitPost exit 484116 35.495046365 ... | | | | | | sqloWaitEDUWaitPost entry [eduid 63257 eduname db2agent] | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Db2 10.5 Fix Pack 10 or higher * **************************************************************** | |
Local Fix: | |
Solution | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 12.12.2017 19.07.2018 19.07.2018 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |