DB2 - Problem description
| Problem IC88178 | Status: Closed |
-901 ERROR MAY OCCUR WHILE REVALIDATING ROUTINE WITH UNUSED CTE,FOLLOWED BY INSTANCE TRAP AT SQLNQ_FTB. | |
| product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
| Problem description: | |
If an unused declaration of CTE (Common Tables Expressions)
exists ,the -901 error will raise while revalidating (For
example, by calling SYSPROC.ADMIN_REVALIDATE_DB_OBJECTS) the
routine.
From db2diag.log:
2012-10-29-00.56.39.625939-240 I117181E880 LEVEL: Severe
PID : 30465 TID : 46912824666432PROC :
db2sysc
INSTANCE: hujinpei NODE : 000 DB : ALANDB
APPHDL : 0-1886 APPID:
*LOCAL.hujinpei.121029045408
AUTHID : HUJINPEI
EDUID : 125 EDUNAME: db2agent (ALANDB)
FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_ffdc,
probe:300
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
sqlcaid : SQLCAL sqlcabc: 136 sqlcode: -901 sqlerrml: 52
sqlerrmc: No column information found in the packed descriptor
sqlerrp : SQLNQ1FD
sqlerrd : (1) 0x801A006D (2) 0x00000000 (3)
0x0000002D
(4) 0x00000000 (5) 0xFFFFFF9C (6)
0x00000000
sqlwarn : (1) (2) (3) (4) (5) (6)
(7) (8) (9) (10) (11)
sqlstate:
With the stack info from generated FODC_AppErr package:
<StackTrace>
-----FUNC-ADDR---- ------FUNCTION + OFFSET------
0x00002AAAB083F417 ossDumpStackTraceEx + 0x01ef
0x00002AAAB083A1D6 _ZN11OSSTrapFile6dumpExEmiP7siginfoPvm +
0x00cc
0x00002AAAAD756894 sqlo_trce + 0x040a
0x00002AAAAD79D3D5 sqloDumpDiagInfoHandler + 0x00ed
0x00002AAAAABD2005 pthread_kill + 0x0035
0x00002AAAAD79C7BF sqloDumpEDU + 0x0045
0x00002AAAAC9F4CEA _Z15sqldDumpContextP9sqeBsuEduiiiiiPKcPvi +
0x069e
0x00002AAAAC237541 _Z15sqlrr_dump_ffdcP8sqlrr_cbii + 0x0555
0x00002AAAAC4490AC _Z13sqlzeDumpFFDCP8sqeAgentjP5sqlcai + 0x0020
0x00002AAAAC448207
_Z12sqlzeSqlCodeP8sqeAgentjmjP5sqlcaitP13__va_list_tag + 0x00f7
0x00002AAAABF2BB8B _Z10sqlnn_erdsiiiiiz + 0x014b
0x00002AAAAC04D2EF _ZN9sqlnq_ftb14refftb_numcolsEPS_Pi + 0x046b
0x00002AAAAC0B3EA1
_Z27sqlnq_handle_qtb_extref_rec20sqlnq_multipart_namePP9sqlnq_qt
biP3loc21sqlnq_hierarchy_usage + 0x0a55
During the error handling in sqlnq_ftb::refftb_numcols that we
report -901 may later cause the instance trap with Signal #11:
<StackTrace>
-----FUNC-ADDR---- ------FUNCTION + OFFSET------
0x00002AAAB083F417 ossDumpStackTraceEx + 0x01ef
0x00002AAAB083A1D6 _ZN11OSSTrapFile6dumpExEmiP7siginfoPvm +
0x00cc
0x00002AAAAD756894 sqlo_trce + 0x040a
0x00002AAAAD79D78F sqloEDUCodeTrapHandler + 0x025f
0x00002AAAAC04D38D _ZN9sqlnq_ftb14refftb_numcolsEPS_Pi + 0x0509
0x00002AAAAC0B3EA1
_Z27sqlnq_handle_qtb_extref_rec20sqlnq_multipart_namePP9sqlnq_qt
biP3loc21sqlnq_hierarchy_usage + 0x0a55
0x00002AAAAC0AF022
_Z29sqlnq_handle_named_ref_in_srcP12sqlnq_stringiPP9sqlnq_qtbPP9
sqlnq_qunPP9sqlnq_qncP3loc21sqlnq_hierarchy_usageP20sqlnq_multip
art_name + 0x040a
0x00002AAAAC0DDD5E
_Z22sqlnq_handle_table_refP20sqlnq_multipart_namePP9sqlnq_qunP9s
qlnq_qtbP3locP9sqlnq_opr21sqlnq_hierarchy_usage + 0x0090
0x00002AAAAC0DD966
_Z27sqlnq_handle_from_table_refP20sqlnq_multipart_namePhiPP9sqln
q_qunP9sqlnq_qtbP3locP9sqlnq_opr21sqlnq_hierarchy_usagePP8stknod
e_ + 0x007a
0x00002AAAAE4FAD68 _Z9sqlnq_semPP8stknode_i10actiontypePhP3loc +
0xf1e4 | |
| Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL USERS * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to v10FP3 to get this problem fixed. * **************************************************************** | |
| Local Fix: | |
Removes 'unused' declaration of CTE (Common Tables Expressions) from the routine. | |
| available fix packs: | |
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows | |
| Solution | |
The problem will be fixed in v10FP3 | |
| Workaround | |
not known / see Local fix | |
| Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 13.11.2012 02.10.2013 02.10.2013 |
| Problem solved at the following versions (IBM BugInfos) | |
| Problem solved according to the fixlist(s) of the following version(s) | |
| 10.1.0.3 |
|
| 10.1.0.3 |
|