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

STANDBY DATABASE FAILS TO START WITH SQL1224N WHEN CONNECT_PROC IS NOT NULL

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
When CONNECT_PROC variable is set in database configuration, 
error SQL1224N might occur during: 
db2 start hadr on db <DATABASE> as standby. 
 
Entries that can be found in db2diag.log: 
 
 
2012-07-30-12.43.47.767258+120 I16534E581          LEVEL: Error 
PID     : 15622                TID  : 140737089890048PROC : 
db2sysc 0 
INSTANCE: db2inst1                NODE : 000          DB   : DB 
APPHDL  : 0-8                  APPID: 
*LOCAL.db2inst1.120730104345 
AUTHID  : db2inst1 
EDUID   : 21                   EDUNAME: db2agent (DB) 0 
FUNCTION: DB2 UDB, base sys utilities, sqleagnt_sigsegvh, 
probe:9 
MESSAGE : Error in agent servicing application with PRODUCT 
SIGNATURE: 
DATA #1 : Hexdump, 8 bytes 
0x0000000200F3696C : 5351 4C30 3930 3736 
SQL09076 
 
2012-07-30-12.43.47.767297+120 I17116E578          LEVEL: Error 
PID     : 15622                TID  : 140737089890048PROC : 
db2sysc 0 
INSTANCE: db2inst1                NODE : 000          DB   : DB 
APPHDL  : 0-8                  APPID: 
*LOCAL.db2inst1.120730104345 
AUTHID  : db2inst1 
EDUID   : 21                   EDUNAME: db2agent (DB) 0 
FUNCTION: DB2 UDB, base sys utilities, sqleagnt_sigsegvh, 
probe:10 
MESSAGE : Error in agent servicing application with APPLICATION 
NAME: 
DATA #1 : Hexdump, 5 bytes 
0x0000000200F36842 : 6462 3262 70 
db2bp 
 
2012-07-30-12.43.47.767347+120 I17695E490          LEVEL: Severe 
PID     : 15622                TID  : 140737089890048PROC : 
db2sysc 0 
INSTANCE:                 NODE : 000          DB   : DB 
APPHDL  : 0-8                  APPID: 
*LOCAL.db2inst1.120730104345 
AUTHID  : db2inst1 
EDUID   : 21                   EDUNAME: db2agent (DB) 0 
FUNCTION: DB2 UDB, Query Gateway, sqlqg_signal_handler, probe:10 
MESSAGE : DIA0505I Execution of a component signal handling 
function has begun. 
 
2012-07-30-12.43.47.767616+120 I18186E225         LEVEL: Severe 
PID:15622 TID:140737089890048 NODE:000 Title: QG SQLCA 
Dump File: 
/db2/home/db2inst1/sqllib/db2dump/FODC_Trap_2012-07-30-12.43.47. 
650993_0000/15622.21.000.dump.bin 
 
FODC_Trap files are created with following stack: 
 
<StackTrace> 
-----FUNC-ADDR---- ------FUNCTION + OFFSET------ 
0x00007FFFF2036377 ossDumpStackTraceEx + 0x01ef 
                (/db2/home/arspi/sqllib/lib64/libdb2osse.so.1) 
0x00007FFFF2031136 _ZN11OSSTrapFile6dumpExEmiP7siginfoPvm + 
0x00cc 
                (/db2/home/arspi/sqllib/lib64/libdb2osse.so.1) 
0x00007FFFF4D561D7 sqlo_trce + 0x03fb 
                (/db2/home/arspi/sqllib/lib64/libdb2e.so.1) 
0x00007FFFF4D9CE95 sqloEDUCodeTrapHandler + 0x026b 
                (/db2/home/arspi/sqllib/lib64/libdb2e.so.1) 
0x00007FFFF7BCF500 address: 0x00007FFFF7BCF500 ; dladdress: 
0x00007FFFF7BC0000 ; offset in lib: 0x000000000000F500 ; 
                (/lib64/libpthread.so.0) 
0x00007FFFF396961D _ZN16sqlrlCatalogScan12buildIndexesEv + 
0x004d 
                (/db2/home/arspi/sqllib/lib64/libdb2e.so.1) 
0x00007FFFF396804D _ZN16sqlrlCatalogScan4openEv + 0x016d 
                (/db2/home/arspi/sqllib/lib64/libdb2e.so.1) 
0x00007FFFF399367B 
_Z29sqlrlBuildRoleListScanCatalogP8sqlrr_cbPhscjP13SQLO_MEM_POOL 
jjP16sqlrlCatalogScanS5_P10sqlr_rolesPj + 0x0263 
                (/db2/home/arspi/sqllib/lib64/libdb2e.so.1) 
0x00007FFFF3991E2C 
_Z34sqlrlcFetchRolesForAuthidsFromDiskP8sqlrr_cbPP19sqlrlcRolesR 
equiredPmS4_ + 0x0132 
                (/db2/home/arspi/sqllib/lib64/libdb2e.so.1) 
0x00007FFFF39900E5 
_Z25sqlrlcAuthidsFindRolelistP8sqlrr_cbP11sqlr_aainfomP13SQLO_ME 
M_POOLPP19sqlrlcRolesRequiredPmS8_m + 0x01e9 
                (/db2/home/arspi/sqllib/lib64/libdb2e.so.1) 
0x00007FFFF398F82D 
_Z31sqlrlcRequestRolelistsForAuthidP8sqlrr_cbP11sqlr_aainfobbb + 
0x00c7 
                (/db2/home/arspi/sqllib/lib64/libdb2e.so.1 
0x00007FFFF38AA127 
_Z21sqlra_set_stmt_authidP8sqlrr_cbiPcic21sqlraTrustKnownAuthid 
+ 0x0405 
                (/db2/home/arspi/sqllib/lib64/libdb2e.so.1) 
0x00007FFFF387F83E _Z30sqlra_set_stmt_authid_dynrulesP8sqlrr_cb 
+ 0x005e 
                (/db2/home/arspi/sqllib/lib64/libdb2e.so.1) 
0x00007FFFF5B21F31 
_Z17sqlra_get_sectionP8sqlrr_cbPhsS1_sS1_tmP16db2UCprepareInfoP1 
5db2UCCursorInfo + 0x12c7 
                (/db2/home/arspi/sqllib/lib64/libdb2e.so.1) 
0x00007FFFF5B16479 
_Z21sqlrr_sql_request_preP14db2UCinterfacejiP16db2UCprepareInfoP 
15db2UCCursorInfo + 0x04ed 
                (/db2/home/arspi/sqllib/lib64/libdb2e.so.1) 
0x00007FFFF3838C7B 
_Z14sqlrr_execimmdP14db2UCinterfaceP16db2UCprepareInfo + 0x00ab 
                (/db2/home/arspi/sqllib/lib64/libdb2e.so.1) 
0x00007FFFF4F608FE _Z21sqlrr_callConnectProcP14db2UCinterfaceb + 
0x040e 
                (/db2/home/arspi/sqllib/lib64/libdb2e.so.1) 
0x00007FFFF346C398 
_Z32sqljsPostProcessingConnectAttachP13sqljsDrdaAsCbP14db2UCinte 
rfacei + 0x0192 
                (/db2/home/arspi/sqllib/lib64/libdb2e.so.1) 
0x00007FFFF346B721 
_Z18sqljsConnectAttachP13sqljsDrdaAsCbP14db2UCinterface + 0x00e7 
                (/db2/home/arspi/sqllib/lib64/libdb2e.so.1) 
0x00007FFFF3447A24 
_Z16sqljs_ddm_accsecP14db2UCinterfaceP13sqljDDMObject + 0x0084 
                (/db2/home/arspi/sqllib/lib64/libdb2e.so.1) 
0x00007FFFF3440C1A 
_Z17sqljsParseConnectP13sqljsDrdaAsCbP13sqljDDMObjectP14db2UCint 
erface + 0x0068 
                (/db2/home/arspi/sqllib/lib64/libdb2e.so.1) 
0x00007FFFF344113A 
_Z10sqljsParseP13sqljsDrdaAsCbP14db2UCinterfaceP8sqeAgentb + 
0x035a 
                (/db2/home/arspi/sqllib/lib64/libdb2e.so.1) 
0x00007FFFF343576C address: 0x00007FFFF343576C ; dladdress: 
0x00007FFFF24D1000 ; offset in lib: 0x0000000000F6476C ; 
                (/db2/home/arspi/sqllib/lib64/libdb2e.so.1) 
0x00007FFFF343A99D address: 0x00007FFFF343A99D ; dladdress: 
0x00007FFFF24D1000 ; offset in lib: 0x0000000000F6999D ; 
                (/db2/home/arspi/sqllib/lib64/libdb2e.so.1) 
0x00007FFFF34382A4 address: 0x00007FFFF34382A4 ; dladdress: 
0x00007FFFF24D1000 ; offset in lib: 0x0000000000F672A4 ; 
                (/db2/home/arspi/sqllib/lib64/libdb2e.so.1) 
0x00007FFFF3438012 _Z17sqljsDrdaAsDriverP18SQLCC_INITSTRUCT_T + 
0x0102 
                (/db2/home/arspi/sqllib/lib64/libdb2e.so.1) 
0x00007FFFF336A5A6 _ZN8sqeAgent6RunEDUEv + 0x0a72 
                (/db2/home/arspi/sqllib/lib64/libdb2e.so.1) 
0x00007FFFF3A53390 _ZN9sqzEDUObj9EDUDriverEv + 0x00a6 
                (/db2/home/arspi/sqllib/lib64/libdb2e.so.1) 
0x00007FFFF3A532E7 _Z10sqlzRunEDUPcj + 0x0009 
                (/db2/home/arspi/sqllib/lib64/libdb2e.so.1) 
0x00007FFFF37BAE9A sqloEDUEntry + 0x02f4 
                (/db2/home/arspi/sqllib/lib64/libdb2e.so.1) 
0x00007FFFF7BC7851 address: 0x00007FFFF7BC7851 ; dladdress: 
0x00007FFFF7BC0000 ; offset in lib: 0x0000000000007851 ; 
                (/lib64/libpthread.so.0) 
0x00007FFFF13ED67D clone + 0x006d 
                (/lib64/libc.so.6) 
</StackTrace>
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Update to DB2 9.7  Fix Pack 8                                * 
****************************************************************
Local Fix:
To circumvent the error, disable the connection procedure 
parameter by  setting CONNECT_PROC to  NULL in database 
configuration.
available fix packs:
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
Problem was first fix in DB2 9.7  Fix Pack 8
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC88685 IC88701 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
02.08.2012
08.04.2013
08.04.2013
Problem solved at the following versions (IBM BugInfos)
9.7.
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.8 FixList