home clear 64x64
en blue 200x116 de orange 200x116 info letter User
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 IC77586 Status: Closed

DBLATCH HELD A LONG TIME DURING DYNAMIC SQL SNAPSHOT

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
When Dynamic SQL snapshots are issued it will hold the dblatch 
during processing, but holding the dblatch will affect other 
processes running at the same time that also need to hold the 
dblatch.  This can unduly affect performance.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All users that use dynamic SQL snapshots.                    * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* When dynamic SQL snapshots are issued it will hold the       * 
* dblatch during processing.   Here are two sample stacks.     * 
* The first is running a dynamic SQL snapshot and the second   * 
* is turning off monitor switches but waiting for the dblatch. * 
*                                                              * 
* <StackTrace>                                                 * 
* -------Frame------ ------Function                            * 
* 0x0900000003675D08 find_stmt                                 * 
* 0x090000000367C584 adjust_anchor_stmt                        * 
* 0x090000000367C4E8 adjust_apm_snap                           * 
* 0x090000000367C428 adjust_dyn_sql                            * 
* 0x090000000367AFB0 format_apm_buffer                         * 
* 0x0900000004C23430 sqlra_load_dyn_stmt                       * 
* 0x0900000004C4CE40 sqlmw_dyn_sql                             * 
* 0x0900000004AD4444 sqlmonssagnt                              * 
* 0x0900000004BBBE8C sqlmonssbackend                           * 
* 0x0900000004C14278 sqlesrvr                                  * 
* 0x0900000006E81260 sqleMappingFnServer                       * 
* 0x0900000006E80B58 sqlerKnownProcedure                       * 
* 0x0900000006DE995C sqlerCallDL                               * 
* 0x0900000006DE9FB4 .sqljs_ddm_excsqlstt.fdpr.clone.          * 
* 0x0900000006FD927C sqljsParseRdbAccessed                     * 
* 0x0900000006FD96D0 .sqljsParse.fdpr.clone                    * 
* 0x0900000006FC2EA8 sqljsSqlam                                * 
* 0x090000000718086C sqljsDriveRequests                        * 
* 0x0900000007180534 sqljsDrdaAsInnerDriver                    * 
* 0x090000000717FF58 sqljsDrdaAsDriver                         * 
* 0x0900000006E75314 RunEDU                                    * 
* 0x0900000006E76F10 EDUDriver                                 * 
* 0x0900000006E713CC sqloEDUEntry                              * 
* </StackTrace>                                                * 
*                                                              * 
* 0x090000000709B928 sqloXlatchConflict                        * 
* 0x090000000709B4FC sqloXlatchConflict                        * 
* 0x0900000004C1E0D4 sqm_get_next_dbcb                         * 
* 0x0900000004C50F34 turn_off_switches                         * 
* 0x0900000006DC0A60 update_switches                           * 
* 0x0900000004BDA828 sqlmonagnt                                * 
* 0x09000000041DA7F4 sqlmonbackend                             * 
* 0x0900000004C14264 sqlesrvr                                  * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Version 9.7 Fix Pack 5                            * 
****************************************************************
Local Fix:
For large databases that have lots of statements in the cache 
carefully consider when DYNAMIC SQL snapshots are issued so that 
they do not unduly affect processing by holding the dblatch for 
long periods of time.
available fix packs:
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Solution
Problem was first fixed in Version 9.7 Fix Pack 5
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
17.07.2011
21.12.2011
21.12.2011
Problem solved at the following versions (IBM BugInfos)
9.7.FP5
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.5 FixList