home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC73334 Status: Geschlossen

SQL0901N WHEN RUNNING A QUERY, REASON CODE IS (REASON "INVALID LPOP
NUMBER".)

Produkt:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problembeschreibung:
SQL0901 error is reported when running a query, with reason code 
(Reason "Invalid lpop number".) 
 
A possible stack looks like: 
<StackTrace> 
-------Frame------ ------Function + Offset------ 
0x0900000000455470 pthread_kill + 0xB0 
0x090000005B300CA0 sqloDumpEDU + 0xA4 
0x090000005B303908 sqldDumpContext__FP9sqeBsuEduiN42PCcPvT2 + 
0xF8 
0x090000005B304DE4 
sqldDumpContext__FP9sqeBsuEduiN42PCcPvT2@glue59C + 0x98 
0x090000005C305428 sqlrr_dump_ffdc__FP8sqlrr_cbiT2 + 0x384 
0x090000005F690530 sqlzeDumpFFDC__FP8sqeAgentUiP5sqlcai + 0x50 
0x090000005BA825C4 sqlzeSqlCode__FP8sqeAgentUiUlT2P5sqlcaiUsPc + 
0x24 
0x090000005B03D630 sqlnn_erds__FiN41e + 0x33C 
0x090000005C728C18 
sqlngStoreLolepop__FP9sqlng_blkP19sqlno_plan_operatorT2UlRPUiR13 
sqlngPlanInfo + 0x604 
0x090000005C727940 
sqlngStoreLolepop__FP9sqlng_blkP19sqlno_plan_operatorT2UlRPUiR13 
sqlngPlanInfo + 0xF74 
0x090000005C727C38 
sqlngStoreLolepop__FP9sqlng_blkP19sqlno_plan_operatorT2UlRPUiR13 
sqlngPlanInfo + 0x126C 
0x090000005C727CA4 
sqlngStoreLolepop__FP9sqlng_blkP19sqlno_plan_operatorT2UlRPUiR13 
sqlngPlanInfo + 0x12D8 
0x090000005C727C38 
sqlngStoreLolepop__FP9sqlng_blkP19sqlno_plan_operatorT2UlRPUiR13 
sqlngPlanInfo + 0x126C 
0x090000005C727CA4 
sqlngStoreLolepop__FP9sqlng_blkP19sqlno_plan_operatorT2UlRPUiR13 
sqlngPlanInfo + 0x12D8 
0x090000005C7276E8 
sqlngStoreLolepop__FP9sqlng_blkP19sqlno_plan_operatorT2UlRPUiR13 
sqlngPlanInfo + 0xD1C 
0x090000005C726778 
sqlngStoreLolepop__FP9sqlng_blkP19sqlno_plan_operatorT2UlRPUiR13 
sqlngPlanInfo@glue17EB + 0x74 
0x090000005BC6B578 sqlngStorePlanInfo__FP9sqlng_blk + 0x2DC 
0x090000005FA59B50 sqlng_main__FP9sqlnq_qur + 0x38C 
0x090000005FA783E0 sqlng_main__FP9sqlnq_qur@glue174B + 0x84 
0x090000005FA77A3C 
sqlnn_cmpl__FP8sqeAgentP11sqlrrstrings17sqlnn_compileModeT3P14sq 
lrr_cmpl_enviT7PP9sqlnq_qur + 0x320 
0x090000005F8D6C28 
sqlnn_cmpl__FP8sqeAgentP11sqlrrstrings17sqlnn_compileModeT3P14sq 
lrr_cmpl_env + 0x40 
0x090000005F5BFDA8 
sqlra_compile_var__FP8sqlrr_cbP14sqlra_cmpl_envPUciUsN54P14SQLP_ 
LOCK_INFOP16sqlra_cached_varPiPUl + 0x798 
0x090000005F5C3980 
sqlra_find_var__FP8sqlrr_cbP17sqlra_cached_stmt13sqlra_stmt_idUi 
T4PUcT4UsUcP14sqlra_cmpl_env15sqlra_fill_modePiiT12_N313_T12_P14 
SQLP_LOCK_INFOPP16sqlra_cached_varT12_PUlb + 0x52C 
0x090000005F5C5580 sqlra_get_var__FP8sqlrr_cbiT2bPbT5 + 0x720 
0x090000005E2E76B8 
sqlrr_prepare__FP14db2UCinterfaceP16db2UCprepareInfo + 0x2B8 
0x090000005D3783C8 
sqljs_ddm_prpsqlstt__FP14db2UCinterfaceP13sqljDDMObject + 0x840 
0x090000005B8E3C3C 
sqljsParseRdbAccessed__FP13sqljsDrdaAsCbP13sqljDDMObjectP14db2UC 
interface + 0x1F8 
0x090000005F7D9790 
.sqljsParse.fdpr.clone.26__FP13sqljsDrdaAsCbP14db2UCinterfaceP8s 
qeAgentb + 0x248 
0x090000005F7BDFA8 @64@sqljsSqlam__FP14db2UCinterfaceP8sqeAgentb 
+ 0xB5C 
0x090000005F9FDFA4 
@64@sqljsDriveRequests__FP8sqeAgentP14db2UCconHandle + 0xA0 
0x090000005F9FDC30 
@64@sqljsDrdaAsInnerDriver__FP18SQLCC_INITSTRUCT_Tb + 0x260 
0x090000005F9FD654 sqljsDrdaAsDriver__FP18SQLCC_INITSTRUCT_T + 
0xEC 
0x090000005F91190C RunEDU__8sqeAgentFv + 0x234 
0x090000005F9135B8 EDUDriver__9sqzEDUObjFv + 0xE0 
0x090000005F90CFC8 sqloEDUEntry + 0x260 
</StackTrace>
Problem-Zusammenfassung:
Problem Description: 
SQL0901N WHEN RUNNING A QUERY, REASON CODE IS (REASON "INVALID 
LPOP NUMBER".) 
Problem Summary: 
SQL0901 error is reported when running a query, with reason code 
 
(Reason "Invalid lpop number".) 
 
A possible stack looks like: 
<StackTrace> 
-------Frame------ ------Function + Offset------ 
0x0900000000455470 pthread_kill + 0xB0 
0x090000005B300CA0 sqloDumpEDU + 0xA4 
0x090000005B303908 sqldDumpContext__FP9sqeBsuEduiN42PCcPvT2 + 
0xF8 
0x090000005B304DE4 
sqldDumpContext__FP9sqeBsuEduiN42PCcPvT2@glue59C + 0x98 
0x090000005C305428 sqlrr_dump_ffdc__FP8sqlrr_cbiT2 + 0x384 
0x090000005F690530 sqlzeDumpFFDC__FP8sqeAgentUiP5sqlcai + 0x50 
0x090000005BA825C4 sqlzeSqlCode__FP8sqeAgentUiUlT2P5sqlcaiUsPc + 
0x24 
0x090000005B03D630 sqlnn_erds__FiN41e + 0x33C 
0x090000005C728C18 
sqlngStoreLolepop__FP9sqlng_blkP19sqlno_plan_operatorT2UlRPUiR13 
sqlngPlanInfo + 0x604 
0x090000005C727940 
sqlngStoreLolepop__FP9sqlng_blkP19sqlno_plan_operatorT2UlRPUiR13 
sqlngPlanInfo + 0xF74 
0x090000005C727C38 
sqlngStoreLolepop__FP9sqlng_blkP19sqlno_plan_operatorT2UlRPUiR13 
sqlngPlanInfo + 0x126C 
0x090000005C727CA4 
sqlngStoreLolepop__FP9sqlng_blkP19sqlno_plan_operatorT2UlRPUiR13 
sqlngPlanInfo + 0x12D8 
0x090000005C727C38 
sqlngStoreLolepop__FP9sqlng_blkP19sqlno_plan_operatorT2UlRPUiR13 
sqlngPlanInfo + 0x126C 
0x090000005C727CA4 
sqlngStoreLolepop__FP9sqlng_blkP19sqlno_plan_operatorT2UlRPUiR13 
sqlngPlanInfo + 0x12D8 
0x090000005C7276E8 
sqlngStoreLolepop__FP9sqlng_blkP19sqlno_plan_operatorT2UlRPUiR13 
sqlngPlanInfo + 0xD1C 
0x090000005C726778 
sqlngStoreLolepop__FP9sqlng_blkP19sqlno_plan_operatorT2UlRPUiR13 
sqlngPlanInfo@glue17EB + 0x74 
0x090000005BC6B578 sqlngStorePlanInfo__FP9sqlng_blk + 0x2DC 
0x090000005FA59B50 sqlng_main__FP9sqlnq_qur + 0x38C 
0x090000005FA783E0 sqlng_main__FP9sqlnq_qur@glue174B + 0x84 
0x090000005FA77A3C 
sqlnn_cmpl__FP8sqeAgentP11sqlrrstrings17sqlnn_compileModeT3P14sq 
lrr_cmpl_enviT7PP9sqlnq_qur + 0x320 
0x090000005F8D6C28 
sqlnn_cmpl__FP8sqeAgentP11sqlrrstrings17sqlnn_compileModeT3P14sq 
lrr_cmpl_env + 0x40 
0x090000005F5BFDA8 
sqlra_compile_var__FP8sqlrr_cbP14sqlra_cmpl_envPUciUsN54P14SQLP 
LOCK_INFOP16sqlra_cached_varPiPUl + 0x798 
0x090000005F5C3980 
sqlra_find_var__FP8sqlrr_cbP17sqlra_cached_stmt13sqlra_stmt_idUi 
T4PUcT4UsUcP14sqlra_cmpl_env15sqlra_fill_modePiiT12_N313_T12_P14 
SQLP_LOCK_INFOPP16sqlra_cached_varT12_PUlb + 0x52C 
0x090000005F5C5580 sqlra_get_var__FP8sqlrr_cbiT2bPbT5 + 0x720 
0x090000005E2E76B8 
sqlrr_prepare__FP14db2UCinterfaceP16db2UCprepareInfo + 0x2B8 
0x090000005D3783C8 
sqljs_ddm_prpsqlstt__FP14db2UCinterfaceP13sqljDDMObject + 0x840 
0x090000005B8E3C3C 
sqljsParseRdbAccessed__FP13sqljsDrdaAsCbP13sqljDDMObjectP14db2UC 
interface + 0x1F8 
0x090000005F7D9790 
.sqljsParse.fdpr.clone.26__FP13sqljsDrdaAsCbP14db2UCinterfaceP8s 
qeAgentb + 0x248 
0x090000005F7BDFA8 @64@sqljsSqlam__FP14db2UCinterfaceP8sqeAgentb 
+ 0xB5C 
0x090000005F9FDFA4 
@64@sqljsDriveRequests__FP8sqeAgentP14db2UCconHandle + 0xA0 
0x090000005F9FDC30 
@64@sqljsDrdaAsInnerDriver__FP18SQLCC_INITSTRUCT_Tb + 0x260 
0x090000005F9FD654 sqljsDrdaAsDriver__FP18SQLCC_INITSTRUCT_T + 
0xEC 
0x090000005F91190C RunEDU__8sqeAgentFv + 0x234 
0x090000005F9135B8 EDUDriver__9sqzEDUObjFv + 0xE0 
0x090000005F90CFC8 sqloEDUEntry + 0x260 
</StackTrace>
Local-Fix:
n/a
verfügbare FixPacks:
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows

Lösung
Problem is first fixed in Version 9.5 Fix Pack 8
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
17.12.2010
05.07.2011
05.07.2011
Problem behoben ab folgender Versionen (IBM BugInfos)
9.5.FP8
Problem behoben lt. FixList in der Version
9.5.0.8 FixList