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 IT34775 Status: Closed

SQL STATEMENT CALLING NTILE FUNCTION FAILS WITH : -901 BAD DYN INDEX.
IDX=4294967294 SIZE=87 (OFF=5)

product:
DB2 FOR LUW / DB2FORLUW / B10 - DB2
Problem description:
The following error is logged into db2diag.log  when SQL
statement calling NTILE function
fails with -901 :

2019-10-29-01.36.58.937361-240 I198590552A912       LEVEL:
Severe
PID     : 21430464             TID : 118528         PROC :
db2sysc 1
INSTANCE: xxxxx            NODE : 001           DB   : xxxx
APPHDL  : 1-7964               APPID:xxxx
THID  : xxxxxxxx              HOSTNAME: xxxxxxxx
EDUID   : 118528               EDUNAME: db2agent (FITDB) 1
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: 46
sqlerrmc: Bad dyn index.  idx=4294967294 size=87 (off=5)
sqlerrp : SQLNG0C4
sqlerrd : (1) 0x00000000      (2) 0x00000000      (3) 0x00000000
          (4) 0x00000043      (5) 0xFFFFEEEA      (6) 0x00000001
sqlwarn : (1)      (2)      (3)      (4)        (5)       (6)
          (7)      (8)      (9)      (10)        (11)

FODC_AppErr folder is generated in the DB2DUMP  and the stack
agent reports
the following functions calls  :
-------Frame------ ------Function + Offset------
0x0900000000582F94 pthread_kill + 0xD4
0x090000000F9722FC sqloDumpEDU + 0x9C
0x090000000FAE807C sqlzeDumpFFDC__FP8sqeAgentUiP5sqlcai + 0x11C
0x090000000FAE7B9C sqlzeSqlCode__FP8sqeAgentUiUlT2P5sqlcaiUsPc +
0x27C
0x090000001184DC90 sqlnn_erds__FiN41e + 0x110
0x0900000011865A08
sqlngMemBlockLookup__FP9sqlng_blkPvUlRP15sqlngSectObject + 0x888
0x0900000011864A88 sqlngSectResolveDeps__FP9sqlng_blkUl + 0xCC8
0x0900000015EBB238 sqlngSectOptimize__FP9sqlng_blk + 0x78
0x09000000158AE8B0 sqlng_main__FP9sqlnq_qur + 0x2E90
0x0900000013231D64
sqlnn_cmpl__FP8sqeAgentP11sqlrrstrings17sqlnn_compileModeT3P14sq
lrr_cmpl_enviT7PP9sqlnq_qur + 0x6004
0x090000001322BCE8
sqlnn_cmpl__FP8sqeAgentP11sqlrrstrings17sqlnn_compileModeT3P14sq
lrr_cmpl_env + 0x28
0x09000000151E8CE4
sqlra_compile_var__FP8sqlrr_cbP14sqlra_cmpl_envPUciUsN54P14SQLP_
LOCK_INFOP16sqlra_cached_varPiT11_Pb + 0xBE4
0x09000000106E05E4
sqlra_find_var__FP8sqlrr_cbP17sqlra_cached_stmt13sqlra_stmt_idUi
T4PUcT4UsUcP14sqlra_cmpl_env15sqlra_fill_modePiiT12_N313_T12_P14
SQL
P_LOCK_INFOPP16sqlra_cached_varT12_bT19_Pb + 0xA84
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* All                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See error description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* None                                                         *
****************************************************************
Local Fix:
Solution
Workaround
****************************************************************
* USERS AFFECTED:                                              *
* All                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See error description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* None                                                         *
****************************************************************
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
04.11.2020
19.03.2021
19.03.2021
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)