DB2 FOR LUW / DB2FORLUW / A10 - DB2

Customer can hit this issue depending on memory usage. The much 
higher virtual memory usage than physical memory made more 
chance to create unmapped virtual memory segments and exposed 
the defect. The problem will no be recreated on non memory 
constraint DB2 instance. 
 
On db2diag.log there will be the messages related to the "ALTER 
TABLE <table_name> DROP": 
 
 
 
2014-11-24-10.07.14.686000-360 I22048038F922        LEVEL: 
Severe 
PID     : 2264                 TID : 16936          PROC : 
db2syscs.exe 
INSTANCE: DB2                  NODE : 000           DB   : 
DWPRD1 
APPHDL  : 0-49117              APPID: 
10.10.10.90.54258.141124160126 
AUTHID  : PIDDBA1              HOSTNAME: JBVUDBP09A 
EDUID   : 16936                EDUNAME: db2agent (DWPRD1) 0 
FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_sibling, 
probe:200 
MESSAGE : section stmt 
DATA #1 : Hexdump, 78 bytes 
0x00000014B5F73E14 : 616C 7465 7220 7461 626C 6520 5346 432E 
alter table SFC. 
0x00000014B5F73E24 : 4443 535F 5245 5155 4553 5420 6472 6F70 
DCS_REQUEST drop 
0x00000014B5F73E34 : 2063 6F6C 756D 6E20 4352 4D5F 4154 4C41 
column CRM_ATLA 
0x00000014B5F73E44 : 535F 4443 535F 454E 4749 4E45 4552 5F44 
S_DCS_ENGINEER_D 
0x00000014B5F73E54 : 4553 4947 4E5F 5245 515F 4944 5F43 
ESIGN_REQ_ID_C 
 
..... 
 
2014-11-24-10.12.55.089000-360 E22093803F947        LEVEL: 
Severe 
PID     : 2264                 TID : 16936          PROC : 
db2syscs.exe 
INSTANCE: DB2                  NODE : 000           DB   : 
DWPRD1 
APPHDL  : 0-49117              APPID: 
10.10.10.90.54258.141124160126 
AUTHID  : PIDDBA1              HOSTNAME: JBVUDBP09A 
EDUID   : 16936                EDUNAME: db2agent (DWPRD1) 0 
FUNCTION: DB2 UDB, oper system services, sqloEDUExceptionFilter, 
probe:90 
MESSAGE : ADM14011C  A critical failure has caused the following 
type of error: 
          "Trap". The DB2 database manager cannot recover from 
the failure. 
          First Occurrence Data Capture (FODC) was invoked in 
the following 
          mode: "Automatic". FODC diagnostic information is 
located in the 
          following directory: 
 
"C:\DB2\INSTANCE\DB2\FODC_Trap_2014-11-24-10.01.45.172000_0000\" 
. 
DATA #1 : Signal Number Recieved, 4 bytes 
-1073741819 
 
 
 
On the trap file we can see the following stacktrace: 
 
    <StackTrace> 
 
   sqlpCopyPSO 
   sqlrl_alter_col 
   sqlrlalt 
   sqlnq_alter_table_end 
   sqlnq_alter_table_stmt 
   sqlnp_smactn 
   sqlnp_parser 
   sqlnp_main 
   sqlnn_cmpl 
   sqlnn_cmpl 
   sqlra_compile_var 
   sqlra_find_var 
   sqlra_get_var 
   sqlri_ddl_get_section 
   sqlri_ddl_common 
   sqlriddl 
   sqlriSectInvoke 
   sqlrr_execute_immediate 
   sqlrr_execimmd 
   sqljs_ddm_excsqlimm 
   sqljsParse 
   sqljsSqlam 
   sqljsDriveRequests 
   sqljsDrdaAsInnerDriver 
   sqljsDrdaAsDriver 
   sqeAgent::RunEDU 
   sqlzRunEDU 
   sqloEDUEntry

**************************************************************** 
* USERS AFFECTED:                                              * 
* NA                                                           * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 v10.1 Fix Pack 5 or higher.                   * 
****************************************************************

Fixed in DB2 V10.1 Fix Pack 5

not known / see Local fix

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

16.01.2015
16.07.2015
16.07.2015