DB2 FOR LUW / DB2FORLUW / B10 - DB2

SQL0901, SQL0404 or Abend (abnormal termination) possible when 
compiling an UPDATE statement. 
 
Examples of symptoms below: 
 
SQL0901N  The SQL statement or command failed because of a 
database system 
error. (Reason "(12) SQLRI_MAX sanity check failed".) 
SQLSTATE=58004 
 
SQL0901N  The SQL statement or command failed because of a 
database system 
error. (Reason "column number out of range".)  SQLSTATE=58004 
 
SQL0404N or a panic causing the instance to abend that produces 
the following stack: 
 
sqle_panic__Fi + 0x7A4 
sqloCrashOnCriticalMemoryValidationFailure + 0x48 
diagnoseMemoryCorruptionAndCrash__13SQLO_MEM_POOLFUlCPCcCb + 
0x4F0 
MemTreeGet__13SQLO_MEM_POOLFCUlT1PP17SqloChunkSubgroupPUi + 
0x930 
allocateMemoryBlock__13SQLO_MEM_POOLFCUlT1UiT1PP17SqloChunkSubgr 
oupPUiCP12SMemLogEvent + 0xFC 
sqloGetMemoryBlockExtended + 0xAA0 
sqlnn_new_invocation__FP8sqlrr_cbP19sqlrr_invocation_cbiPP19sqln 
n_invocation_cb + 0x118 
sqlnn_cmpl__FP8sqeAgentP11sqlrrstrings17sqlnn_compileModeT3P14sq 
lrr_cmpl_enviT7PP9sqlnq_qur + 0x4EC 
sqlnn_cmpl__FP8sqeAgentP11sqlrrstrings17sqlnn_compileModeT3P14sq 
lrr_cmpl_env + 0x28 
sqlra_compile_var__FP8sqlrr_cbP14sqlra_cmpl_envPUciUsN54P14SQLP_ 
LOCK_INFOP16sqlra_cached_varPiT11_Pb + 0xBDC 
sqlra_find_var__FP8sqlrr_cbP17sqlra_cached_stmt13sqlra_stmt_idUi 
T4PUcT4UsUcP14sqlra_cmpl_env15sqlra_fill_modePiiT12_N313_T12_P14 
SQLP_LOCK_INFOPP16sqlra_cached_varT12_bT19_Pb + 0xA50 
sqlra_get_var__FP8sqlrr_cbiT2bPbT5 + 0xBFC 
sqlrr_process_excsqlset__FP8sqlrr_cb + 0xA40 
sqlrr_excsqlset__FP14db2UCinterface + 0x4B0 
sqljs_ddm_excsqlset__FP14db2UCinterfaceP13sqljDDMObject + 0x146C 
sqljsParseRdbAccessed__FP13sqljsDrdaAsCbP13sqljDDMObjectP14db2UC 
interface + 0x310 
sqljsParse__FP13sqljsDrdaAsCbP14db2UCinterfaceP8sqeAgentb + 
0x2264 
IPRA.$sqljsSqlam__FP14db2UCinterfaceP8sqeAgentb + 0xE9C 
sqljsDriveRequests__FP8sqeAgentP14db2UCconHandle + 0xB4 
IPRA.$sqljsDrdaAsInnerDriver__FP18SQLCC_INITSTRUCT_Tb + 0x13E0 
sqljsDrdaAsDriver__FP18SQLCC_INITSTRUCT_T + 0x334 
RunEDU__8sqeAgentFv + 0xB60 
EDUDriver__9sqzEDUObjFv + 0x2E0 
sqloEDUEntry + 0x374

**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Apply v11.1 Mod 3 Fixpack 3 to DB2 server.                   * 
****************************************************************

The workaround is set the registry key 
NO_SCALARQ2LOJ . 
Setting this registry might have negative impact to the UPDATE 
statements so we recommend to only apply this registry key to 
the UPDATE statements that have this issue. There are two 
options to use: 
 
a) This affects all UPDATE statements. Beware of the possible 
negative impact. 
 
db2set -im DB2COMPOPT=NO_SCALARQ2LOJ 
 
OR 
 
b) Set optimizer guideline below for the affected queries: 
 
b.1) Append to end of each UPDATE statement like: 
 
UPDATE. .... 
/* <OPTGUIDELINES> 
<REGISTRY> 
<OPTION NAME='DB2COMPOPT' VALUE='NO_SCALARQ2LOJ'/> 
 
</REGISTRY> 
</OPTGUIDELINES> 
*/; 
 
b.2) The comments /* */ should be removed if placed into opt 
profile instead of appending to the end of the statement as a 
comment.

Db2 Version 11.1 Mod 3 Fix Pack 3 for Linux, UNIX, and Windows
 Db2 Version 11.1 Mod3 Fix Pack3 iFix001 for Linux, UNIX, and Windows
 Db2 Version 11.1 Mod3 Fix Pack3 iFix002 for Linux, UNIX, and Windows
 

First fixed in v11.1 Mod xx Fixpack 3

See LOCAL FIX.

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

14.07.2017
15.03.2018
15.03.2018