DB2 FOR LUW / DB2FORLUW / B10 - DB2

DB2 may trap when using select RID_BIT() function on a column
organized table

You may see message similar to below in db2diag.log:
2019-11-04-12.05.05.898928-480 I77054E1026 LEVEL: Severe
PID : 14836 TID : 139626555631360 PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB :
APPHDL : 0-277 APPID: .191104200501
UOWID : 1 ACTID: 1
AUTHID : HOSTNAME:
EDUID : 221 EDUNAME: db2agnts () 0
FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_sibling,
probe:160
MESSAGE : section stmt
DATA #1 : Hexdump, 91 bytes
0x00007F06C8566E40 : 5345 4C45 4354 2078 2E2A 2C52 4944 5F42
SELECT x.*,RID_B
0x00007F06C8566E50 : 4954 2878 2920 6173 2052 4944 5F42 4954
IT(x) as RID_BIT
0x00007F06C8566E60 : 2046 524F 4D20 5045 5253 4F4E 4E45 4C2E
FROM PERSONNEL.
0x00007F06C8566E70 : 5045 525F 534E 4150 5F41 4C4C 2078 0A57
PER_SNAP_ALL x.W
0x00007F06C8566E80 : 4845 5245 2078 2E45 4646 5F44 4154 4520
HERE x.EFF_DATE
0x00007F06C8566E90 : 3D20 274A 554C 3230 3139 27 = 'JUL2019'

2019-11-04-12.05.05.899273-480 I78081E222 LEVEL: Severe
PID:14836 TID:139626555631360 NODE:000 Title: section stmt
Dump
File:/db2data-11/db2/db2dump/FODC_Trap_2019-11-04-12.05.02.60098
2_0000/14836.221.000.dump.bin

2019-11-04-12.05.05.920409-480 I100191E599 LEVEL: Severe
PID : 14836 TID : 139626555631360 PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB :
APPHDL : 0-277 APPID:
UOWID : 1 ACTID: 1
AUTHID : HOSTNAME:
EDUID : 221 EDUNAME: db2agnts () 0
FUNCTION: DB2 UDB, index manager, sqliDumpPages, probe:390
MESSAGE : Index object = {TBSPACEID=; OBJECTID=} Parent
object =
{TBSPACEID=; OBJECTID=}

2019-11-04-12.05.09.181306-480 I238137E2236 LEVEL: Event
PID : 14836 TID : 139626555631360 PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB :
APPHDL : 0-277 APPID: .191104200501
UOWID : 1 ACTID: 1
AUTHID : HOSTNAME:
EDUID : 221 EDUNAME: db2agnts () 0
FUNCTION: DB2 UDB, oper system services,
sqloPGRPRegisterOneCrash, probe:2161
MESSAGE : lastCrashCount
DATA #1 : unsigned integer, 8 bytes
0
DATA #2 : String, 10 bytes
inRecovery
DATA #3 : Boolean, 1 bytes
false
CALLSTCK: (Static functions may not be resolved correctly, as
they are resolved to the nearest symbol)
[0] 0x00007F17E7DC8F9C sqloPGRPRegisterOneCrash + 0x20C
[1] 0x00007F17E7F21D92 sqloEDUCodeTrapHandler + 0xB22
[2] 0x00000035E960F7E0 /lib64/libpthread.so.0 + 0xF7E0
[3] 0x00007F17E2B8D34F
_Z22sqldLockDataPartFixTCBP8sqeAgentP8SQLD_CCBtm + 0xCF
[4] 0x00007F17E9954CA9
_Z17sqliSetupIpredRidP7SQLI_CBP10SQLD_IPRED8SQLZ_RID + 0x1D9
[5] 0x00007F17E9938474 /home/db2inst1/sqllib/lib64/libdb2e.so.1
+ 0x8E8D474
[6] 0x00007F17E992759E _Z8sqlifnxtP7SQLI_CBP11SQLI_SFGLOB +
0x2BE
[7] 0x00007F17E98E7720
_Z7sqlirdkP8sqeAgentP10SQLI_IXPCRP9SQLD_IXCBmP8SQLD_KEYP12SQLI_K
EYDATAP9sqli_scanPi + 0x2410
[8] 0x00007F17E2B3E720 _Z14sqldIndexFetchP8SQLD_CCBP8SQLZ_RID +
0x5F0
[9] 0x00007F17E2B3C8B6
_Z12sqldRowFetchP8sqeAgentP8SQLD_CCBmmPP10SQLD_VALUEP8SQLZ_RIDmP
12SQLD_ID_LISTP9SQLP_LSN8 + 0x1466
[10] 0x00007F17E8AE9FDD _Z10sqlriFetchP8sqlrr_cbP9sqlri_taol +
0x1ED
[11] 0x00007F17E8C74D56 _Z7sqlritaP8sqlrr_cb + 0x6C6
[12] 0x00007F17E8B9191D
_Z15sqlriSectInvokeP8sqlrr_cbP12sqlri_opparm + 0x4BD
[13] 0x00007F17E85B2608
_Z21sqlrr_subagent_routerP8sqeAgentP12SQLE_DB2RA_T + 0xDF8
[14] 0x00007F17E60A43E2 /home/db2inst1/sqllib/lib64/libdb2e.so.1
+ 0x55F93E2
[15] 0x00007F17E60A2CB0 _Z21sqleProcessSubRequestP8sqeAgent +
0x3E0
[16] 0x00007F17E60D7BE7 _ZN8sqeAgent6RunEDUEv + 0x5D7
[17] 0x00007F17E99F8EEE _ZN9sqzEDUObj9EDUDriverEv + 0x1BE
[18] 0x00007F17E7F1EB1A sqloEDUEntry + 0x57A
[19] 0x00000035E9607AA1 /lib64/libpthread.so.0 + 0x7AA1
[20] 0x00000035E92E8C4D clone + 0x6D

****************************************************************
* USERS AFFECTED:                                              *
* ALL                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Updated to Db2 11.1 Mod 4 Fixpack 5 or future releases       *
****************************************************************

There are two TEMPORARY workarounds:
1. Use  optimizer guidelines to avoid index scans on column
organized table when RID_BIT is being selected.
For example: db2 "select col1,RID_BIT() from T1 where col=3
//"

2.If possible, this is can be avoid by forcing not use indexes
on CDE tables:
db2set DB2_REDUCED_OPTIMIZATION="COL_IXSCAN_ALL_V1133 OFF"
-im option can be used, BUT Static sql will need to be rebund
and already compiled dynamic sql re-compiled as well.

Use above as temporary workaround and contact IBM DB2 Support.

not known / see Local fix

forerunner  : 
follow-up : IT31287 IT33284 

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

10.12.2019
16.11.2020
16.11.2020