When hit this problem, the client application may receive
SQL0901N, may find below messages at db2diag.log and
FODC_AppErr_xxx directory may be created.
The problem has been in the code since V10.1 GA (2012.04.30)
and firstly discovered on year 2016 with V10.5 FP5. So it might
be
suggested that the problem rarely occurred by a complicated
select
statement.
From db2diag.log
-----
2016-12-25-20.14.39.511758-300 E560995A802 LEVEL: Error
PID : 27656216 TID : 3086 PROC :
db2sysc
INSTANCE: hidehy NODE : 000 DB :
SAMPLE
APPHDL : 0-108 APPID: *LOCAL.hidehy.161226011601
AUTHID : HIDEHY HOSTNAME: p6db2serv
EDUID : 3086 EDUNAME: db2agent (SAMPLE)
FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_ffdc, probe:30
MESSAGE : ADM14005E The following error occurred: "AppErr".
First Occurrence
Data Capture (FODC) has been invoked in the following
mode:
"Automatic". Diagnostic information has been recorded
in the
directory named
"/home/hidehy/sqllib/db2dump/FODC_AppErr_2016-12-25-20.14.39.510
599_2
7656216_3086_000/".
2016-12-25-20.14.39.516350-300 E561798A586 LEVEL:
Severe
PID : 27656216 TID : 3086 PROC :
db2sysc
INSTANCE: hidehy NODE : 000 DB :
SAMPLE
APPHDL : 0-108 APPID: *LOCAL.hidehy.161226011601
AUTHID : HIDEHY HOSTNAME: p6db2serv
EDUID : 3086 EDUNAME: db2agent (SAMPLE)
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.
2016-12-25-20.14.39.516857-300 I562385A919 LEVEL:
Severe
PID : 27656216 TID : 3086 PROC :
db2sysc
INSTANCE: hidehy NODE : 000 DB :
SAMPLE
APPHDL : 0-108 APPID: *LOCAL.hidehy.161226011601
AUTHID : HIDEHY HOSTNAME: p6db2serv
EDUID : 3086 EDUNAME: db2agent (SAMPLE)
FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_ffdc,
probe:250
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
sqlcaid : SQLCA sqlcabc: 136 sqlcode: -901 sqlerrml: 57
sqlerrmc: sqlrsopen: forgot to create a sort? table->lstptr is
NULL
sqlerrp : SQLRI124
sqlerrd : (1) 0x00000000 (2) 0x00000000 (3)
0x00000000
(4) 0x00000000 (5) 0xFFFFF4B2 (6)
0x00000000
sqlwarn : (1) (2) (3) (4) (5) (6)
(7) (8) (9) (10) (11)
sqlstate:
----- |
