IT09918: DB2ACD MAY CAUSE LOCK

WAIT DUE TO NOT RELEASING

EXCLUSIVE CATALOG CACHE LOG
Check out the new support experience beta

APAR status

OPEN

Error description
A lock wait situation may occur after successful
collection of asynchronous statistics via JITS (just in
time statistics).
Asynchronous statistics collection
will update the statistics cache as well as the catalog
tables, for which an internal catalog cache is held in
exclusive mode. The JITS deamon may not release this lock
after a non successful return during commit of the
catalog changes. By still holding the internal catalog
cache in exclusive mode other agents will be blocked when
they attempt to look up information from the database
catalog.
Snapshots (application/lock snapshot)
will show the
db2acd process in UOW Waiting but holding an internal
catalog cache log:
Application name
Application status
Object Type

= db2acd
= UOW Waiting
= Internal Catalog Cache Lock

In the optstats log file one will see a warning like

following:
2014-08-11-14.51.21.240570+120 I2637247E537
LEVEL: Warning PID
: 5435
TID :
140251444623104 PROC : db2acd 0
INSTANCE: aaaaaa
NODE : 000
DB
: bbb
APPID
: *LOCAL.db2glp.140811114452
HOSTNAME: myhost
FUNCTION: DB2 UDB, Automatic Table Maintenance,
JitsDaemon::runstats, probe:7

MESSAGE : SQL10007N Message "99999" could not be

retrieved.
Reason code: "4".
DATA #1 : String, 45 bytes
AutoStats: Non zero code from Runstats commit
DATA #2 : String, 10 bytes
RTS Daemon

Local fix

To Avoid the lock wait scenario customer can try the

workaround by setting following registry variable
db2set DB2_ATM_CMD_LINE_ARGS="-low-priority-updatesystables"

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number
IT09918

Reported component name

DB2 FOR LUW

Reported component ID
DB2FORLUW

Reported release
970

Status
OPEN

PE
NoPE

HIPER
NoHIPER

Special Attention
NoSpecatt

Submitted date
2015-07-08

Closed date
Last modified date
2015-07-09

APAR is sysrouted FROM one or more of the following:

IT04230

APAR is sysrouted TO one or more of the following:

Fix information
Applicable component levels

Rate this page

Click to rate document as Poor. The average rating is 0 star(s) based on 0 user(s). The document reputation
is Poor.Click to rate document as Fair. The average rating is 0 star(s) based on 0 user(s). The document
reputation is Poor.Click to rate document as Average. The average rating is 0 star(s) based on 0 user(s). The
document reputation is Poor.Click to rate document as Good. The average rating is 0 star(s) based on 0
user(s). The document reputation is Poor.Click to rate document as Very good. The average rating is 0
star(s) based on 0 user(s). The document reputation is Poor.
Average rating (0 users)

Document information
More support for: DB2 for Linux, UNIX and Windows
Software version: 9.7
Reference #: IT09918
Modified date: 2015-07-09

IBM Technical Support mobile app is now available!

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the
fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.
Back to top
Close

Need support?

E-mail feedback to IBM support

1-800-IBM-7378 (USA)

Directory of worldwide contacts

Discover

Marketplace
Products
Services
Industries
Case studies

Information for...

Developers
Business Partners
Federal and state contracts

Connect with us

Support
Find a sales rep
Find a Business Partner

About IBM

Careers
Latest news
Investor relations
Corporate responsibility
About IBM

Select a country/region
United States - English

Contact
Privacy
Terms of use
Accessibility
Feedback
Cookie preferences