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 IC96450 Status: Closed

The SQL routine using compiled compound statement might trigger reply only
window on HADR standby enabled for ROS

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
The SQL routines using dynamic SQL to construct a compiled 
compound statement (a.k.a an anonymous block): 
 
SET V_SQL = 'BEGIN ' || SQL STATEMENTS || ' END'; 
 
causes the SQL compiler to create a package in SYSPLAN for the 
compiled compound statement. As a result, DDL log records is 
written what triggers reply only window on HADR standby enabled 
for ROS. 
 
This APAR is to fix limitation mentioned above. Because 
anonymous block would never drop an existing package and have no 
impact to existing executions, for anonymous block there is no 
need to kick off the readers on standby.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ROS on HADR environment                                      * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 10.1 fixpack 3                        * 
****************************************************************
Local Fix:
To workaround the issue, you need to use an inline compound 
statement instead of a compiled one i.e.: 
 
SET V_SQL = 'BEGIN ATOMIC ' || SQL STATEMENTS || ' END'; 
 
instead of: 
 
SET V_SQL = 'BEGIN ' || SQL STATEMENTS || ' END';
available fix packs:
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
Problem was first fixed in DB2 version 10.1 fixpack 3
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
27.09.2013
02.10.2013
02.10.2013
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.3 FixList
10.1.0.3 FixList