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

DB2 INSTANCE MAY CRASH IN ADD_AGNT_STMT_COUNTS.

product:
DB2 FOR LUW / DB2FORLUW / 910 - DB2
Problem description:
DB2 instance may crash in add_agnt_stmt_counts due to NULL 
pointer being referenced. 
 
Stack looks like : 
<StackTrace> 
-------Frame------ ------Function + Offset------ 
0x09000000041DDE24 
add_agnt_stmt_counts__11sqlmon_stmtFRC18sqlmon_stmt_countsPC11sq 
lmon_tqcbCUi 
+ 0x418 
0x090000000324762C 
agent_stmt_start__10sqlmon_acbFCUiPCUcN22CUsT1N25N21CiP8sqlrr_cb 
+ 0xB10 
0x09000000048371CC sqlra_agent_stmt_start__FP8sqlrr_cbCUiUsN33i 
+ 0x218 
0x0900000003B171A8 
sqlra_agent_stmt_start__FP8sqlrr_cbCUiUsN33i@glue636 + 
0x88 
0x09000000037AB770 
sqlricls_dbmon_start__FP8sqlrr_cbP9sqlr_apdrP25sqlra_sql_context 
_siblingP11sqlmon_stmtP11sqlmon_conni 
+ 0x24 
0x09000000037C003C sqlricls_complex__FP8sqlrr_cbilN23 + 0x20 
0x09000000033DB874 
@65@5@sqlra_close_section__FP8sqlrr_cbP25sqlra_sql_context_sibli 
ngiN63 + 
0xB8 
0x09000000033DAD40 sqlracal_finalcmt_rb__FP8sqlrr_cb + 0x3B0 
0x09000000033DB224 sqlracal__FP8sqlrr_cbUiT2 + 0x70 
0x09000000033DB0FC 
sqlrr_cleanup_tran_before_DPS__FP8sqlrr_cbiN62PiT9 + 
0x1A8 
0x090000000351EB3C sqlrrbck__FP8sqlrr_cbiN32P13sqlxaCallInfo + 
0x354 
0x0900000003654DA4 sqlrr_rds_common_post__FP14db2UCinterfaceiT2l 
+ 0x498 
0x0900000002AE06C0 
sqlrr_prepare__FP14db2UCinterfaceP13UCprepareInfo + 
0x2CC 
0x0900000002B1E5DC 
sqljs_ddm_prpsqlstt__FP14db2UCinterfaceP14sqljsDDMObject 
+ 0x9D4 
0x090000000364FF4C 
sqljsParseRdbAccessed__FP13sqljsDrdaAsCbP14sqljsDDMObjectP14db2U 
Cinterface 
+ 0x198 
0x09000000036687DC 
sqljsParse__FP13sqljsDrdaAsCbP14db2UCinterface + 0x28C 
0x090000000366753C 
@48@sqljsSqlam__FP14db2UCinterfaceP13sqle_agent_cbb + 
0x94 
0x090000000340379C 
@48@sqljsDriveRequests__FP13sqle_agent_cbP11UCconHandle 
+ 0xA4 
0x09000000034035F4 
@48@sqljsDrdaAsInnerDriver__FP17sqlcc_init_structb + 
0xD4 
0x0900000003403398 sqljsDrdaAsDriver__FP17sqlcc_init_struct + 
0x9C 
0x09000000034043C4 sqleRunAgent__FPcUi + 0x368 
0x090000000340272C 
sqloCreateEDU__FPFPcUi_vPcUlP13SQLO_EDU_INFOPi + 0x270 
0x0900000003401CCC sqloSpawnEDU + 0x234 
0x0900000003401798 
sqleCreateNewAgent__FiP8sqlekrcbP17sqlcc_init_structP16sqlkdRqst 
RplyFmtP18sqle_master_app_cbT1P20agentPoolLatchVectorP16SQLO_EDU 
WAITPOSTP17sqle_connect_infoPP13sqle_agent_cb 
+ 0x314 
0x090000000350DEE8 
sqleGetAgentFromPool__FiP17sqlcc_init_structT1P12sqlz_app_hdlP16 
sqlkdRqstRplyFmtP17sqle_connect_info 
+ 0x82C 
0x09000000037FC2D0 
sqleGetAgent__FiP17sqlcc_init_structT1P12sqlz_app_hdlP16sqlkdRqs 
tRplyFmtT1 
+ 0x44C 
0x090000000357F0E0 sqlcctcpconnmgr_child__FPcUi + 0x11E0 
0x090000000340272C 
sqloCreateEDU__FPFPcUi_vPcUlP13SQLO_EDU_INFOPi + 0x270 
0x0900000003401CCC sqloSpawnEDU + 0x234 
0x090000000420C120 
sqlcctcpconnmgr__FP15SQLCC_CONNMGR_TP9sqlf_kcfdUs + 
0x58C 
0x090000000420A0D4 sqlcctcp_start_listen + 0x44 
0x0900000004209FDC sqlcctcp_start_listen@glue44D + 0x74 
0x0900000003824134 sqlccstrts__FP9sqlf_kcfdP15SQLCC_CONNMGR_TRUs 
+ 0x2C4 
0x0000000100004C10 sqleInitSysCtlr__FPi + 0xE8C 
0x00000001000031D4 sqleSysCtlr__Fv + 0x320 
0x0900000002ED968C 
@49@sqloSystemControllerMain__FCUiPFv_iPFi_vPPvCPi + 
0x524 
0x09000000037F85F4 sqloRunInstance + 0xAC 
0x00000001000029F8 DB2main + 0x930 
0x0000000100003D50 main + 0x10 
</StackTrace>
Problem Summary:
DB2 instance may crash in add_agnt_stmt_counts due to NULL 
pointer being referenced. 
 
Stack looks like : 
<StackTrace> 
-------Frame------ ------Function + Offset------ 
0x09000000041DDE24 
add_agnt_stmt_counts__11sqlmon_stmtFRC18sqlmon_stmt_countsPC11sq 
lmon_tqcbCUi 
+ 0x418 
0x090000000324762C 
agent_stmt_start__10sqlmon_acbFCUiPCUcN22CUsT1N25N21CiP8sqlrr_cb 
+ 0xB10 
0x09000000048371CC sqlra_agent_stmt_start__FP8sqlrr_cbCUiUsN33i 
+ 0x218 
0x0900000003B171A8 
sqlra_agent_stmt_start__FP8sqlrr_cbCUiUsN33i@glue636 + 
0x88 
0x09000000037AB770 
sqlricls_dbmon_start__FP8sqlrr_cbP9sqlr_apdrP25sqlra_sql_context 
_siblingP11sqlmon_stmtP11sqlmon_conni 
+ 0x24 
0x09000000037C003C sqlricls_complex__FP8sqlrr_cbilN23 + 0x20 
0x09000000033DB874 
@65@5@sqlra_close_section__FP8sqlrr_cbP25sqlra_sql_context_sibli 
ngiN63 + 
0xB8 
0x09000000033DAD40 sqlracal_finalcmt_rb__FP8sqlrr_cb + 0x3B0 
0x09000000033DB224 sqlracal__FP8sqlrr_cbUiT2 + 0x70 
0x09000000033DB0FC 
sqlrr_cleanup_tran_before_DPS__FP8sqlrr_cbiN62PiT9 + 
0x1A8 
0x090000000351EB3C sqlrrbck__FP8sqlrr_cbiN32P13sqlxaCallInfo + 
0x354 
0x0900000003654DA4 sqlrr_rds_common_post__FP14db2UCinterfaceiT2l 
+ 0x498 
0x0900000002AE06C0 
sqlrr_prepare__FP14db2UCinterfaceP13UCprepareInfo + 
0x2CC 
0x0900000002B1E5DC 
sqljs_ddm_prpsqlstt__FP14db2UCinterfaceP14sqljsDDMObject 
+ 0x9D4 
0x090000000364FF4C 
sqljsParseRdbAccessed__FP13sqljsDrdaAsCbP14sqljsDDMObjectP14db2U 
Cinterface 
+ 0x198 
0x09000000036687DC 
sqljsParse__FP13sqljsDrdaAsCbP14db2UCinterface + 0x28C 
0x090000000366753C 
@48@sqljsSqlam__FP14db2UCinterfaceP13sqle_agent_cbb + 
0x94 
0x090000000340379C 
@48@sqljsDriveRequests__FP13sqle_agent_cbP11UCconHandle 
+ 0xA4 
0x09000000034035F4 
@48@sqljsDrdaAsInnerDriver__FP17sqlcc_init_structb + 
0xD4 
0x0900000003403398 sqljsDrdaAsDriver__FP17sqlcc_init_struct + 
0x9C 
0x09000000034043C4 sqleRunAgent__FPcUi + 0x368 
0x090000000340272C 
sqloCreateEDU__FPFPcUi_vPcUlP13SQLO_EDU_INFOPi + 0x270 
0x0900000003401CCC sqloSpawnEDU + 0x234 
0x0900000003401798 
sqleCreateNewAgent__FiP8sqlekrcbP17sqlcc_init_structP16sqlkdRqst 
RplyFmtP18sqle_master_app_cbT1P20agentPoolLatchVectorP16SQLO_EDU 
WAITPOSTP17sqle_connect_infoPP13sqle_agent_cb 
+ 0x314 
0x090000000350DEE8 
sqleGetAgentFromPool__FiP17sqlcc_init_structT1P12sqlz_app_hdlP16 
sqlkdRqstRplyFmtP17sqle_connect_info 
+ 0x82C 
0x09000000037FC2D0 
sqleGetAgent__FiP17sqlcc_init_structT1P12sqlz_app_hdlP16sqlkdRqs 
tRplyFmtT1 
+ 0x44C 
0x090000000357F0E0 sqlcctcpconnmgr_child__FPcUi + 0x11E0 
0x090000000340272C 
sqloCreateEDU__FPFPcUi_vPcUlP13SQLO_EDU_INFOPi + 0x270 
0x0900000003401CCC sqloSpawnEDU + 0x234 
0x090000000420C120 
sqlcctcpconnmgr__FP15SQLCC_CONNMGR_TP9sqlf_kcfdUs + 
0x58C 
0x090000000420A0D4 sqlcctcp_start_listen + 0x44 
0x0900000004209FDC sqlcctcp_start_listen@glue44D + 0x74 
0x0900000003824134 sqlccstrts__FP9sqlf_kcfdP15SQLCC_CONNMGR_TRUs 
+ 0x2C4 
0x0000000100004C10 sqleInitSysCtlr__FPi + 0xE8C 
0x00000001000031D4 sqleSysCtlr__Fv + 0x320 
0x0900000002ED968C 
@49@sqloSystemControllerMain__FCUiPFv_iPFi_vPPvCPi + 
0x524 
0x09000000037F85F4 sqloRunInstance + 0xAC 
0x00000001000029F8 DB2main + 0x930 
0x0000000100003D50 main + 0x10 
</StackTrace>
Local Fix:


available fix packs:


DB2 Version 9.1 Fix Pack 9  for Linux, UNIX and Windows
 DB2 Version 9.1 Fix Pack 10  for Linux, UNIX and Windows
 DB2 Version 9.1 Fix Pack 11  for Linux, UNIX and Windows
 DB2 Version 9.1 Fix Pack 12  for Linux, UNIX and Windows
 


Solution


Problem was first fixed in Version 9.1 Fix Pack 9.


Workaround


not known / see Local fix


BUG-Tracking


forerunner  : APAR is sysrouted TO one or more of the following: IC65680 IC65813 
follow-up : 


Timestamps


Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

24.08.2009
12.04.2010
12.04.2010


Problem solved at the following versions (IBM BugInfos)


9.1.FP9



Problem solved according to the fixlist(s) of the following version(s)


9.1.0.9

FixList