DB2 FOR LUW / DB2FORLUW / 970 - DB2

Deferred ASLHEAPSZ value is used by processes spawned outside of 
the db2sysc process instead of using the current value that the 
db2sysc process contains.  This leads to threads within the 
db2sysc process using a different value than those outside, 
hence leading to possible errors in the communication streams. 
 
For example, giving the statement: 
 
 
CALL ADMIN_CMD( ( SELECT 'IMPORT FROM /dev/null of DEL REPLACE 
INTO "SERVTYPE"' FROM SYSIBM.SYSDUMMY1 ) ) 
 
 
Attempt to execute one gives the error code: 
 
SQL30020N Execution of the command or SQL statement failed 
because of a 
syntax error in the communication data stream that will affect 
the successful 
execution of subsequent commands and SQL statements: Reason Code 
"0x124C"("0103")"". 
 
There, the ASLHEAPSZ in effect, is not truly being deferred 
until after the instance is restarted, which leads to these 
undesired effects.

**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 Version 9.7 GA through to Fix Pack 2 servers on Linux,   * 
* Unix and Windows platforms that perform deferred updates to  * 
* ASLHEAPSZ.                                                   * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* You have changed the value of ASLHEAPSZ and trying to call a * 
* DB2 utility using the ADMIN_CMD interface afterward without  * 
* having DB2 instance restarted. In attempt to call            * 
* ADMIN_CMD() you receive an error similar to one below:       * 
*                                                              * 
* SQL30020N Execution of the command or SQL statement failed   * 
* because of a                                                 * 
* syntax error in the communication data stream that will      * 
* affect the successful                                        * 
* execution of subsequent commands and SQL statements: Reason  * 
* Code                                                         * 
* "0x124C"("0103")"".                                          * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Apply DB2 Version 9.7 Fix Pack 3 or update ASLHEAPSZ when    * 
* the instance is down. See local fix for details.             * 
****************************************************************

Restart the instance. If the ASLHEAPSZ needs to be modified, it 
is safest to stop the instance, update the configuration 
parameter, then start the instance again.

DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
 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
 

Deferred ASLHEAPSZ value is used by processes spawned outside of 
the db2sysc process instead of using the current value that the 
db2sysc process contains.  This leads to threads within the 
db2sysc process using a different value than those outside, 
 
hence leading to possible errors in the communication streams. 
 
Problem is first fixed in DB2 Version 9.7 Fix Pack 3 and all 
subsequent Fix Packs

keiner bekannt / siehe Local-Fix

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

16.06.2010
28.09.2010
28.09.2010

9.7.FP3