DB2 FOR LUW / DB2FORLUW / A10 - DB2

When you create an index on a SMS tablespace you may have the 
following entry in the db2diag.log 
 
2013-10-18-12.15.31.181895-240 I70414A3817          LEVEL: Event 
PID     : 9568676              TID : 2329           PROC : 
db2sysc 
INSTANCE: db2inst1             NODE : 000           DB   : 
TESTDB 
APPHDL  : 0-51                 APPID: 
*LOCAL.db2inst1.131018161610 
AUTHID  : DB2INST1             HOSTNAME: db2host 
EDUID   : 2329                 EDUNAME: db2agent (TESTDB) 
FUNCTION: DB2 UDB, oper system services, sqloopenp, probe:40 
DATA #1 : signed integer, 4 bytes 
0 
DATA #2 : signed integer, 4 bytes 
22 
DATA #3 : File name, 75 bytes 
/home/db2host/db2inst1/db2inst1/NODE0000/SQL00001/$HOME/ts1/SQL0 
0002.INX 
DATA #4 : Hex integer, 4 bytes 
0x00000000 
CALLSTCK: (Static functions may not be resolved correctly, as 
they are resolved to the nearest symbol) 
  [0] 0x09000000C2633E78 sqloopenp + 0x7B4 
  [1] 0x09000000C49C0EFC 
sqlbReadPageInfo__FPcT1UliT4P12SQLB_GLOBALSPbPUiP9SQLP_LSN8 + 
0xC4 
  [2] 0x09000000C49BFDD8 
@112@sqldCheckSMSObj__FP8sqeAgentP8SQLD_TCBP17SQLD_CREATEINX_CB 
+ 0x1D0 
  [3] 0x09000000C2FDC1A8 
sqldEndIndexCreate__FP8sqeAgentP17SQLD_CREATEINX_CBi + 0x2DFC 
  [4] 0x09000000C2FD9340 
sqlrlCreateIndexPart__FP8sqlrr_cbP8sqlrg_idP17SQLD_CREATEINX_CBi 
+ 0x330 
  [5] 0x09000000C2FD7C64 
sqlrlCreateLocalIndex__FP8sqlrr_cbP8sqlrg_pdP14sqlrg_partkeydP8s 
qlrg_idP18sqlrg_datapartinfoP17SQLD_CREATEINX_CBibT8 + 0x11E8 
  [6] 0x09000000C4A21E78 
sqlrl_create_index__FP8sqlrr_cbPUcsT2T3T2T3T2T3P11sqlrg_xinfoT3U 
lT2P16sqlrl_index_parmT3P22sqlrl_extendedIdx_infoT12_iT18_P18sq 
+ 0x5D10 
  [7] 0x09000000C5108FA0 
sqlnq_create_index_end__FP9sqlnq_qtbiN22 + 0x100C 
  [8] 0x09000000C513A79C 
sqlnq_create_index_stmt__FPP8stknode_i10actiontypePUcP3loc + 
0xA10 
  [9] 0x09000000C2318DC4 sqlnp_smactn__FP8sqlnp_cbi + 0x140 
  [10] 0x09000000C2318640 sqlnp_parser__FP8sqlnp_cb + 0x51C 
  [11] 0x09000000C22E8E98 
sqlnp_main__FP12sqlnq_stringbP3locPP9sqlnq_qur + 0x29C 
  [12] 0x09000000C22D48C0 
sqlnn_cmpl__FP8sqeAgentP11sqlrrstrings17sqlnn_compileModeT3P14sq 
lrr_cmpl_enviT7PP9sqlnq_qur + 0xD8C 
  [13] 0x09000000C22D847C 
sqlnn_cmpl__FP8sqeAgentP11sqlrrstrings17sqlnn_compileModeT3P14sq 
lrr_cmpl_env + 0x44 
  [14] 0x09000000C2657704 
sqlra_compile_var__FP8sqlrr_cbP14sqlra_cmpl_envPUciUsN54P14SQLP_ 
LOCK_INFOP16sqlra_cached_varPi + 0x770 
  [15] 0x09000000C2A8E9BC 
sqlra_find_var__FP8sqlrr_cbP17sqlra_cached_stmt13sqlra_stmt_idUi 
T4PUcT4UsUcP14sqlra_cmpl_env15sqlra_fill_modePiiT12_N313_T12_P1 
+ 0x674 
  [16] 0x09000000C2668E3C sqlra_get_var__FP8sqlrr_cbiT2bPbT5 + 
0x1A4 
  [17] 0x09000000C2B1299C sqlri_ddl_get_section__FP8sqlrr_cb + 
0x68 
  [18] 0x09000000C2B13070 sqlri_ddl_common__FP8sqlrr_cb + 0x474 
  [19] 0x09000000C2B12AE8 sqlriddl__FP8sqlrr_cb + 0x38 
  [20] 0x09000000C249FB08 
sqlriSectInvoke__FP8sqlrr_cbP12sqlri_opparm + 0x24 
  [21] 0x09000000C2B594D0 sqlrr_execute_immediate__FP8sqlrr_cbi 
+ 0x4E8 
  [22] 0x09000000C2B58AE4 
sqlrr_execimmd__FP14db2UCinterfaceP16db2UCprepareInfo + 0x4E8 
  [23] 0x09000000C2B5692C 
sqljs_ddm_excsqlimm__FP14db2UCinterfaceP13sqljDDMObject + 0xDC8 
  [24] 0x09000000C2B53A6C 
sqljsParseRdbAccessed__FP13sqljsDrdaAsCbP13sqljDDMObjectP14db2UC 
interface + 0x48 
  [25] 0x09000000C256DAF4 
.sqljsParse.fdpr.clone.137__FP13sqljsDrdaAsCbP14db2UCinterfaceP8 
sqeAgentb + 0x1084 
  [26] 0x09000000C2574188 
@73@sqljsSqlam__FP14db2UCinterfaceP8sqeAgentb + 0x2D8 
  [27] 0x09000000C2A0FE20 
@73@sqljsDriveRequests__FP8sqeAgentP14db2UCconHandle + 0xB4 
  [28] 0x09000000C2A10778 
@73@sqljsDrdaAsInnerDriver__FP18SQLCC_INITSTRUCT_Tb + 0x458 
  [29] 0x09000000C2A0FAEC 
sqljsDrdaAsDriver__FP18SQLCC_INITSTRUCT_T + 0x21C 
  [30] 0x09000000C27FA66C RunEDU__8sqeAgentFv + 0x594 
  [31] 0x09000000C27F42CC EDUDriver__9sqzEDUObjFv + 0x13C 
  [32] 0x09000000C27F4154 sqlzRunEDU__FPcUi + 0x10 
  [33] 0x09000000C2806F00 sqloEDUEntry + 0x264 
  [34] 0x09000000007CBC90 _pthread_body + 0xF0 
  [35] 0xFFFFFFFFFFFFFFFC ?unknown + 0xFFFFFFFF 
 
 
This is a harmless message that gets populated in the 
db2diag.log and it cannot be avoided by changing diaglevel as it 
is recorded as an 'Event' type and may cause disk growth. 
 
 
We can do a repo with the following commands: 
 
db2stop force; 
db2start; 
create db testdb; 
connect to testdb; 
create tablespace ts1 managed by system using ('$HOME/ts1'); 
create table t1 (x int) in ts1; 
create index inx1 on t1(x); 
 
When you scan through the db2diag.log you may find the entries 
similar to above.

**************************************************************** 
* USERS AFFECTED:                                              * 
* AIX                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* upgrade to DB2 V10.1 FP4                                     * 
****************************************************************

DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
 

Fixed in DB2 V10.1 FP4

not known / see Local fix

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

27.11.2013
02.06.2014
02.06.2014