home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC80088 Status: Closed

EXTRANEOUS MESSAGES FROM SQLNQ_FCS::NEED_STATISTICS IN DB2DIAG.LOG

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
Under certain scenarios,a message was added to the db2diag.log 
to provide additional 
information.  The new message by itself is not necessarily an 
indication of a problem 
and there could be legitimate reasons statistics were not 
present when the test surrounding 
the message is checked. 
 
Unless there are other failures occurring, the message by itself 
does not necessarily mean there is a problem. 
 
Below is a sample message: 
2011-11-22-09.18.24.852532-120 I224142E1587        LEVEL: Severe 
PID    : 24446                TID  : 47274847627584PROC : 
db2sysc 0 
INSTANCE: db2inst1            NODE : 000          DB  : SAMPLE 
APPHDL  : 0-14298              APPID: 
*LOCAL.db2inst1.111122093345 
AUTHID  : DB2INST1 
EDUID  : 22                  EDUNAME: db2agent (SAMPLE) 0 
FUNCTION: DB2 UDB, SW- query graph, sqlnq_fcs::need_statistics, 
probe:140 
MESSAGE : cst population error 
DATA #1 : signed integer, 4 bytes 
3 
DATA #2 : String with size, 24 bytes 
TABLE1 
CALLSTACK: 
  [0] 0x00002AFEF0B7B637 pdLog + 0xD7 
  [1] 0x00002AFEF1D21DB7 _ZN9sqlnq_fcs15need_statisticsEP3loc + 
0x1E7 
  [2] 0x00002AFEF1B41621 
_Z25sqlno_kc_get_eff_colcountP13sqlno_globalsP9sqlnq_qnc22SQLNO_ 
SET_EFF_COLCOUNTPP3locPS2_Pf + 0x3BF 
  [3] 0x00002AFEF1B41156 
_Z22sqlno_kc_func_colcountP13sqlno_globalsP9sqlnq_qncP9sqlnq_pid 
22SQLNO_SET_EFF_COLCOUNTPP3locPS2_Pf + 0x8C4 
  [4] 0x00002AFEF1B418AD 
_Z25sqlno_kc_get_eff_colcountP13sqlno_globalsP9sqlnq_qnc22SQLNO_ 
SET_EFF_COLCOUNTPP3locPS2_Pf + 0x64B 
  [5] 0x00002AFEF1BDF02E 
_Z32sqlno_int_order_arrange_grby_ordP13sqlno_globalsP9sqlno_qtbP 
16sqlno_listheader + 0x31A 
  [6] 0x00002AFEF1C5D49D 
_Z20sqlno_plan_begin_oprP13sqlno_globalsP9sqlno_sfbP9sqlnq_opr + 
0x4E9 
  [7] 0x00002AFEF0DC8F58 
_Z13sqlno_call_sfP13sqlno_globalsP8sqlno_sfP9sqlno_sfbPvS5_i13SQ 
LNN_BOOLEAN + 0x8E 
  [8] 0x00002AFEF1C65436 
_Z14sqlno_each_oprP13sqlno_globalsP9sqlno_sfbP9sqlnq_qunP9sqlnq_ 
opr + 0x9C 
  [9] 0x00002AFEF0DC8F58 
_Z13sqlno_call_sfP13sqlno_globalsP8sqlno_sfP9sqlno_sfbPvS5_i13SQ 
LNN_BOOLEAN + 0x8E
Problem Summary:
Local Fix:
Ignore the message unless other failures are occurring. 
Alternately, reduce DIAGLEVEL to 0 to turn off all messages to 
the db2diag.log.
available fix packs:
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Solution
Workaround
not known / see Local fix
Comment
Extra messages are removed to avoid confusion
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
30.11.2011
06.06.2012
06.06.2012
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.6 FixList