APAR status
Closed as program error.
Error description
There is a very specific scenario which can occur when executing select statements in Big SQL which can cause several different symptoms. This will happen only if a very specific condition is triggered: when the last byte of a full row is written into the very last byte of the communication buffer used to return rows from the Big SQL Readers to the Big SQL engine. The most common case is an SQLCODE -901 returned, with the following error in the diagnostic log (db2diag.log) : 2017-10-11-09.33.26.648978-420 I53534E835 LEVEL: Severe PID : 919 TID : 139883628717824 PROC : db2sysc 31 INSTANCE: bigsql NODE : 031 DB : BIGSQL APPHDL : 0-137 APPID: 172.16.158.238.34964.171011163320 AUTHID : BIGSQL HOSTNAME: xl45.fyre.ibm.com EDUID : 85 EDUNAME: db2agnts (BIGSQL) 31 FUNCTION: DB2 UDB, routine_infrastructure, sqerDFSRowDeserializer::startDeserializingRowSet, probe:389 MESSAGE : ZRC=0x82240001=-2111569919=SQLER_INTERNAL_ERROR "unexpected system error" DIA8532C An internal processing error has occurred. DATA #1 : String, 33 bytes Row set size exceeds max row size DATA #2 : unsigned integer, 8 bytes 3988 DATA #3 : signed integer, 4 bytes 1 DATA #4 : unsigned integer, 8 bytes 2017-10-11-09.33.26.650080-420 I54370E739 LEVEL: Severe PID : 919 TID : 139883628717824 PROC : db2sysc 31 INSTANCE: bigsql NODE : 031 DB : BIGSQL APPHDL : 0-137 APPID: 172.16.158.238.34964.171011163320 AUTHID : BIGSQL HOSTNAME: xl45.fyre.ibm.com EDUID : 85 EDUNAME: db2agnts (BIGSQL) 31 FUNCTION: DB2 UDB, routine_infrastructure, sqerDFSRowDeserializer::mHandleDeserializerError, probe:166 MESSAGE : ZRC=0x82240001=-2111569919=SQLER_INTERNAL_ERROR "unexpected system error" DIA8532C An internal processing error has occurred. DATA #1 : String, 55 bytes DFS Row Deserializer: internal error. Generating dumps. 2017-10-11-09.33.26.652456-420 I57999E1071 LEVEL: Severe PID : 919 TID : 139883628717824 PROC : db2sysc 31 INSTANCE: bigsql NODE : 031 DB : BIGSQL APPHDL : 0-137 APPID: 172.16.158.238.34964.171011163320 AUTHID : BIGSQL HOSTNAME: xl45.fyre.ibm.com EDUID : 85 EDUNAME: db2agnts (BIGSQL) 31 FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_ffdc, probe:250 MESSAGE : ZRC=0x82240001=-2111569919=SQLER_INTERNAL_ERROR "unexpected system error" DIA8532C An internal processing error has occurred. DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes sqlcaid : SQLCA sqlcabc: 136 sqlcode: -901 sqlerrml: 33 sqlerrmc: Row set size exceeds max row size sqlerrp : SQLER274 sqlerrd : (1) 0x82240001 (2) 0x00000001 (3) 0x00000000 (4) 0x00000000 (5) 0xFFFFF8C0 (6) 0x0000001F sqlwarn : (1) (2) (3) (4) (5) (6) (7) (8) (9) (10) (11) You might experience a query which appears to be hung, along with the following error in the db2diag.log: 2017-09-13-11.11.02.919053+120 E11209540E605 LEVEL: Severe PID : 33055 TID : 139740628117248 PROC : db2sysc 1 INSTANCE: bigsql NODE : 001 DB : BIGSQL APPHDL : 0-6470 APPID: *N0.bigsql.170913091133 AUTHID : DS_INT_DRF HOSTNAME: sriopdataa0102.recette.local EDUID : 3060 EDUNAME: db2agnts (BIGSQL) 1 FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_ffdc, probe:200 MESSAGE : ADM0001C A severe error has occurred. Examine the administration notification log and contact IBM Support if necessary. 2017-09-13-11.11.02.919489+120 I11210146E1066 LEVEL: Severe PID : 33055 TID : 139740628117248 PROC : db2sysc 1 INSTANCE: bigsql NODE : 001 DB : BIGSQL APPHDL : 0-6470 APPID: *N0.bigsql.170913091133 AUTHID : DS_INT_DRF HOSTNAME: sriopdataa0102.recette.local EDUID : 3060 EDUNAME: db2agnts (BIGSQL) 1 FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_ffdc, probe:250 MESSAGE : ZRC=0x82240001=-2111569919=SQLER_INTERNAL_ERROR "unexpected system error" DIA8532C An internal processing error has occurred. DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes sqlcaid : SQLCA sqlcabc: 136 sqlcode: -901 sqlerrml: 29 sqlerrmc: Continuation is not supported sqlerrp : SQLER23A sqlerrd : (1) 0x82240001 (2) 0x00000001 (3) 0x00000000 (4) 0x00000000 (5) 0xFFFFFA48 (6) 0x00000001 sqlwarn : (1) (2) (3) (4) (5) (6) (7) (8) (9) (10) (11) sqlstate: Either of these could also trigger a null pointer exception in the Big SQL Reader code with something like the following in the Big SQL log: 2017-10-13 05:35:32,360 ERROR com.ibm.biginsights.bigsql.dfsrw.reader.api.DfsScan [Master S:18.1001.1.0.0.4015] : Scan cancelled - null 2017-10-13 05:35:32,363 ERROR com.ibm.biginsights.bigsql.dfsrw.reader.DfsBaseReader [Master S:18.1001.1.0.0.4015] : [BSL-14-715bb878a] Exception raised by Reader at node: 14 Scan ID: S:18.1001.1.0.0.4015 Table: run.against45 Spark: false VORC: false VPQ: false Exception Label: UNMAPPED(java.lang.NullPointerException) java.lang.NullPointerException at com.ibm.biginsights.bigsql.dfsrw.reader.DfsHiveRowBufferSerializ er.serializeRow(DfsHiveRowBufferSerializer.java:496) at com.ibm.biginsights.bigsql.dfsrw.reader.DfsHiveRowBufferSerializ er.batch2Buffer(DfsHiveRowBufferSerializer.java:851) at com.ibm.biginsights.bigsql.dfsrw.reader.api.DfsBatchManager$Batc hRunnable.run(DfsBatchManager.java:76) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExec utor.java:1153) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExe cutor.java:628) at java.lang.Thread.run(Thread.java:785) at com.ibm.biginsights.bigsql.dfsrw.reader.api.DfsBatch2BufferThrea d.run(DfsBatch2BufferThread.java:59) or: 2017-09-19 08:18:13,756 ERROR com.ibm.biginsights.bigsql.dfsrw.reader.DfsBaseReader [Master S:15.1001.3.0.0.9152] : [BSL-2-69ab7d9fc] Exception raised by Reader at node: 2 Scan ID: S:15.1001.3.0.0.9152 Table: w.table1 Spark: false VORC: true VPQ: false Exception Label: UNMAPPED(java.lang.NullPointerException) java.lang.NullPointerException at com.ibm.biginsights.bigsql.dfsrw.orc.DfsOrcRowBufferSerializer.s erializeBatch(DfsOrcRowBufferSerializer.java:155) at com.ibm.biginsights.bigsql.dfsrw.orc.DfsOrcRowBufferSerializer.b atch2Buffer(DfsOrcRowBufferSerializer.java:564) at com.ibm.biginsights.bigsql.dfsrw.reader.api.DfsBatchManager$Batc hRunnable.run(DfsBatchManager.java:76) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExec utor.java:1153) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExe cutor.java:628) at java.lang.Thread.run(Thread.java:785) at com.ibm.biginsights.bigsql.dfsrw.reader.api.DfsBatch2BufferThrea d.run(DfsBatch2BufferThread.java:60)
Local fix
Problem summary
See error description
Problem conclusion
The problem is fixed in Version 5.0.2.0 and later fix packs
Temporary fix
Comments
APAR Information
APAR number
PI89558
Reported component name
BIG SQL 4 BI
Reported component ID
5725C09BQ
Reported release
400
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2017-10-30
Closed date
2018-02-28
Last modified date
2018-02-28
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
Unknown
Fix information
Fixed component name
BIG SQL 4 BI
Fixed component ID
5725C09BQ
Applicable component levels
R425 PSY
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSCRJT","label":"IBM Db2 Big SQL"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"400","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
25 August 2020