|
Problem IC97862
|
Status: Closed |
ERROR CODE -901 WHILE EXECUTING A SELECT STATEMENT - MESSAGE "COLUMN NUMBER OUT OF RANGE " |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
While executing a SELECT statement that fails with error code
-901 - message "Column
number out of range" can cause a DB2 crash.
You can see into the db2diag.log file messages like that:
2013-11-07-11.59.48.127369-300 I13203E863 LEVEL: Severe
PID : 18981 TID : 999999999999999PROC :
db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB : DB1
APPHDL : 0-24751 APPID: 1.1.1.1.1.1
AUTHID : DB2INST1
EDUID : 3474 EDUNAME: db2agent (DB1) 0
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: 26
sqlerrmc: column number out of range
sqlerrp : SQLNQ041
sqlerrd : (1) 0x00000000 (2) 0x00000000 (3)
0x00000000
(4) 0x00000000 (5) 0xFFFFFF9C (6)
0x00000000
sqlwarn : (1) (2) (3) (4) (5) (6)
(7) (8) (9) (10) (11)
sqlstate:
and also stacks like that into the stack file:
sqlnq_ftb::num2fcs
sqlnq_qtb::sel_verkey
sqlnq_select_ofn_sm
sqlnq_viewsel_ofn_sm
sqlnq_proc_enc
sqlnq_qun::check_key
sqlnr_inner_join_reordering
sqlnr_qrwprep_phase1
sqlnr_prep1_action |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 10.1 Fix Pack 4 *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Solution |
First fixed in Version 10.1 Fix Pack 4 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 21.11.2013
02.06.2014
02.06.2014 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.4
|
 |
