DB2 FOR LUW / DB2FORLUW / A10 - DB2

DB2 trapped with the following stack: 
sqloCleanupEnvironment(0xffffffffffffffff) at 0x900000016c22d8c 
sqloFreeOSSInternalMemory() at 0x900000016c232dc 
sqloAppLibTerm() at 0x900000016c237b8 
mod_fini1(??, ??) at 0x9fffffff00020ac 
usl_fini_mods(??, ??, ??, ??) at 0x9fffffff0002c70 
usl_exit_fini_mods(??) at 0x9fffffff0002b64 
__modfini64() at 0x9000000000461bc 
exit(??) at 0x90000000006dc0c 
sqloexit(??, ??) at 0x900000016bb4fd4 
clp_fp_exit.fdpr.chunk.4__Fi(0x0) at 0x900000016bb4f44 
clp_api(0x8fffffff00017b8, 0x0, 0x800200140000000, 0x0, 
0xffffffffffffffff, 0x0, 0x0) at 0x900000016bb4ce8 
main(??, ??) at 0x100000904 
 
Since the trapping signal is ignored, one of symptoms is that 
the file descriptor of db2diag.log is not released after 
trapping, that can prevent the other thread writing into the 
db2diag.log

**************************************************************** 
* USERS AFFECTED:                                              * 
* All users, DPF env is more susceptible to this issue         * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* DB2 trapped with the following stack:                        * 
* sqloCleanupEnvironment(0xffffffffffffffff) at                * 
* 0x900000016c22d8c                                            * 
* sqloFreeOSSInternalMemory() at 0x900000016c232dc             * 
* sqloAppLibTerm() at 0x900000016c237b8                        * 
* mod_fini1(??, ??) at 0x9fffffff00020ac                       * 
* usl_fini_mods(??, ??, ??, ??) at 0x9fffffff0002c70           * 
* usl_exit_fini_mods(??) at 0x9fffffff0002b64                  * 
* __modfini64() at 0x9000000000461bc                           * 
* exit(??) at 0x90000000006dc0c                                * 
* sqloexit(??, ??) at 0x900000016bb4fd4                        * 
* clp_fp_exit.fdpr.chunk.4__Fi(0x0) at 0x900000016bb4f44       * 
* clp_api(0x8fffffff00017b8, 0x0, 0x800200140000000, 0x0,      * 
* 0xffffffffffffffff, 0x0, 0x0) at 0x900000016bb4ce8           * 
* main(??, ??) at 0x100000904                                  * 
*                                                              * 
* Since the trapping signal is ignored, one of symptoms is     * 
* that                                                         * 
* the file descriptor of db2diag.log is not released after     * 
* trapping, that can prevent the other thread writing into the * 
* db2diag.log                                                  * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 10.1 FixPak 3                         * 
****************************************************************

Rename the current db2diag.log.

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
 

keiner bekannt / siehe Local-Fix

Vorgänger  : APAR is sysrouted TO one or more of the following: IC95281 
Nachfolger : 

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

17.01.2013
06.01.2014
06.01.2014