|
Problem IT00990
|
Status: Closed |
SQL0901N ERROR WILL OCCUR ON FUNCTION SQLRI_HSJNFLUSHBLOCKS |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
The following -901 can be seen in db2diag.log:
2014-01-16-14.09.30.407982-300 E356436153E818 LEVEL:
Error
PID : 8033 TID : 46930591738176 PROC :
db2sysc 23
INSTANCE: db2inst1 NODE : 023 DB :
TESTDB
APPHDL : 1-15227 APPID:
10.195.192.45.42764.14012419082
AUTHID : DB2INST1 HOSTNAME: servedev1
EDUID : 193090 EDUNAME: db2agnts (TESTDB) 23
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/db2inst1/sqllib/db2dump/FODC_AppErr_2014-01-16-14.0
9.30.
277593_8033_193090_023/".
[...]
2014-01-16-14.09.30.409827-300 I356438990E896 LEVEL:
Severe
PID : 8033 TID : 46930591738176 PROC :
db2sysc 23
INSTANCE: db2inst1 NODE : 023 DB :
TESTDB
APPHDL : 1-15227 APPID:
10.195.192.45.42764.14012419082
AUTHID : DB2INST1 HOSTNAME: servedev1
EDUID : 193090 EDUNAME: db2agnts (TESTDB) 23
FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_ffdc,
probe:300
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
sqlcaid : SQLCA sqlcabc: 136 sqlcode: -901 sqlerrml: 24
sqlerrmc: reached retryCount limit
sqlerrp : SQLRI0FF
sqlerrd : (1) 0x00000000 (2) 0x00000000 (3)
0x00000000
(4) 0x00000000 (5) 0xFFFFEFB2 (6)
0x00000017
sqlwarn : (1) (2) (3) (4) (5) (6)
(7) (8) (9) (10) (11)
sqlstate:
stack output:
sqlrrSqlCode
sqlri_hsjnFlushBlocks
sqlri_hsjnPartitionFullb
sqlrihsjnProbePD
sqldReadNorm
address: 0x00002AAAAF014D40
sqldfrd
sqldRowFetchP8sqeAgent
sqlritaSimplePerm
sqlrihsjn
sqlrihsjn
sqlrihsjn
sqlriSectInvoke
sqlrr_smp_router |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description above. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version V10.1 Fix Pack 5. *
**************************************************************** |
| Local Fix: |
Make sure RUNSTATS is done and statistics are current and
updated. |
| Solution |
First Fixed in Version V10.1 Fix Pack 5. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 11.04.2014
23.10.2015
23.10.2015 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.5
|
 |
