Fixes are available
DB2 Version 9.5 Fix Pack 3b for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 4a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 5 for Linux, UNIX, and Windows
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
APAR status
Closed as program error.
Error description
You may encounter hang situations within DB2 environment due to locking issue on the local DB2 database directory files. To update the local database directory a process needs to open the corresponding files. Unclosed files may then lead to hangs due to OS locking on these files. Many db2 processes are waiting for latch. They have similar call stacks as follow: ... _global_lock_common ... ... _mutex_lock ... ... pthread_mutex_lock ... ... sqloxltc_app ... ... sqljrGetBestSrvAddr ... ... sqljrInternalConnect ... ... sqljrLookupAddressAndConnect ... Meanwhile, a db2 process is trying to open the DB2 database directory file (i.e. sqllib/sqldbdir/sqldbdir). Its call stack might be silimar to: ... open64 ... ... sqloopenp ... ... sqlegopn ... ... sqledogd ... ... sqledrcv ... ... sqledeop ... ... sqleUpdateSysDbDirServerInfo ... ... sqlexUpdDbDirEntry ... ... sqleUpdateActiveAlternateServer ... Although the stack indicates that this is special to environments which make use of the DB2 client reroute feature every DB2 installation is exposed to this issue.
Local fix
n/a
Problem summary
**************************************************************** * USERS AFFECTED: * * All * **************************************************************** * PROBLEM DESCRIPTION: * * ERROR DESCRIPTION: * * You may encounter hang situations within DB2 environment due * * to * * locking issue on the local DB2 database directory files. * * To update the local database directory a process needs to * * open * * the corresponding files. Unclosed files may then lead to * * hangs * * due to OS locking on these files. * * Many db2 processes are waiting for latch. They have similar * * call * * stacks as follow: * * ... _global_lock_common ... * * ... _mutex_lock ... * * ... pthread_mutex_lock ... * * ... sqloxltc_app ... * * ... sqljrGetBestSrvAddr ... * * ... sqljrInternalConnect ... * * ... sqljrLookupAddressAndConnect ... * * Meanwhile, a db2 process is trying to open the DB2 database * * directory file (i.e. sqllib/sqldbdir/sqldbdir). Its call * * stack * * might be silimar to: * * ... open64 ... * * ... sqloopenp ... * * ... sqlegopn ... * * ... sqledogd ... * * ... sqledrcv ... * * ... sqledeop ... * * ... sqleUpdateSysDbDirServerInfo ... * * ... sqlexUpdDbDirEntry ... * * ... sqleUpdateActiveAlternateServer ... * * Althought the stack indicates that this is special to * * environments which make use of the DB2 client reroute * * feature * * every DB2 installation is exposed to this issue. * * LOCAL FIX: * * n/a * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 V9.5 FP3 * ****************************************************************
Problem conclusion
Problem was first fixed in Version 9.5 Fix Pack 3
Temporary fix
Comments
APAR Information
APAR number
IZ23730
Reported component name
DB2 CEE AIX
Reported component ID
5765F3000
Reported release
950
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2008-06-03
Closed date
2009-10-27
Last modified date
2011-06-15
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
DB2 CEE AIX
Fixed component ID
5765F3000
Applicable component levels
R950 PSN
UP
Document Information
Modified date:
15 June 2011