home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
  • CURSOR Service Distribution
           
     

    CURSOR Service Distribution

    24x7 Always Up

    		 pfeil
  • Logistics and transportation
           
     

    Logistics and transportation

    24x7 Always Up

    		 pfeil
  • Industrial environments
           
     

    Industrial environments

    24x7 Always Up

    		 pfeil
  • Trade and commerce
           
     

    Trade and commerce

    24x7 Always Up

    		 pfeil
  • Online shopping
           
     

    Online shopping

    24x7 Always Up

    		 pfeil
  • We care about your databases
           
     

    We care about your databases

    24x7 Always Up

    		 pfeil
 

Erik Stahlhut

CURSOR Service Distribution

We keep your IBM databases running
             
 

Monitoring Monitoring

Monitoring

  • Companies with existentially important databases trust in our Informix Monitoring. We prevent system failures before they occur.

  • Automated monitoring around the clock. Early detection of bottlenecks based on history data with our CURSOR Admin-Scout.

  • Administration for all installation sizes. Standard, remote or standby administration, up to 24x7 availability for systems with high availability.

  • Individual adjustments to the service levels of our customers with short response times and personal contact persons in support.
Discover more about Informix Monitoring with the CURSOR Service Distribution!
 

ServiceService

Service

  • Requirements from all areas of data management. Service packages or individually agreed projects like:
    • Setup of replications or high availability systems;
    • Performance, runtime analysis, tuning;
    • Release, platform or cloud migration;
    • Access control, encryption, archiving.

  • CURSOR Service Distribution is a long-standing IBM High-Value Service Provider for IBM Informix.

  • Specially for Informix we offer additional online seminars, workshops and training courses.
Information about service and support, so feel free to contact us with your project!
 

SupportSupport

Support

  • Request for support services for IBM databases. Our customers benefit from the competence of more than 25 years of Informix support and system-oriented development of database tools.

  • In case of support we are the first and central contact persons. We have a direct line to the IBM and HCL support departments and are available for our customers with 24x7 agreements around the clock.

  • Even Informix customers without active IBM product maintenance can take advantage of our first-aid support.
Book a support ticket on our website or just call us!
 
 
 
 

IBM Software

for manufacturers

and technology partners

IBM Embedded Solution Agreement (ESA)
integration of IBM software into your solution!

   Service

  • Integrate IBM software into your solution!

  • Benefit from the power of IBM software, take advantage of the attractive conditions for IBM licenses and maintenance!

  • The employees of CURSOR Service Distribution have twenty years of experience in indirect sales of IBM software (OEM/ASL/ESA licensing). We show you how to become an IBM ESA Business Partner!

esa bp werden blue 1000x100

  
 
 
 

CompetenceService

in Informix Administration

  
 

the CURSOR

Admin-Scout for Informix

esa bp werden blue 1000x100

esa bp werden blue 1000x100

  

 

  • The Informix tool right from CURSOR Informix Support.

  • Developed by administrators for administrators.

    With a background of over 25 years of Informix support, administration and system-oriented programming, we have been developing and distributing the Admin Scout since 2015.

  • By our Managed Service approach, the Admin Scout is suitable for almost all application areas of the Informix database system. Our customers are IT departments and administrators in commerce, banks, universities, trade and industry.

  
 
 
 

About us

the CURSOR Service Distribution

  • High-Value Service Provider for IBM Informix.

  • Distribution for IBM Data-Management Software (OEM/ASL/ESA licensing for ISVs).

CURSOR Service Distribution is a business unit of CURSOR Software AG, resulting from the acquisition of the Informix and development tool specialist "Nonne & Schneider" at the end of 2005.

We offer extensive technical services for IBM Informix, and as a high-value service provider we are the direct contact for all our customers' service needs for these databases.

Our services are independent from licensing through our company. Well-known customers rely on our monitoring and use our tools, while licensing and update maintenance are contracted directly with IBM.

  

CURSOR Software AG

For over 25 years CURSOR has been developing and marketing CRM solutions for the upper middle class and large concerns.

  • Together.
    Together with you we will lead your CRM project to success. Our experts offer comprehensive services from a single source: software development, consulting, software introduction, training, support - and the ongoing optimization of your CRM system.

  • Inspiring.
    We "live" CRM and want to inspire you with CRM software and services Made in Germany. The benchmark for this is the enthusiasm and loyalty of our customers - and their customers.

  • Successful.
    For 30 years the name CURSOR has stood for excellent customer and business process management - CRM and BPM. We measure our success by the satisfaction and market success of our customers. Learn more about successful CRM projects directly from our customers.

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

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

product:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problem description:
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 Summary:
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
available fix packs:
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
Solution
Problem is first fixed in Version 9.5 Fix Pack 8
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

17.12.2010
05.07.2011
05.07.2011
Problem solved at the following versions (IBM BugInfos)
9.5.FP8
Problem solved according to the fixlist(s) of the following version(s)
9.5.0.8 FixList