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

In a DPF environment, an access plan with a listener TQ operator may
encouter a NULL pointer and cause DB2 to crash.

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
A DB2 crash occurs in an access plan with a listener TQ operator 
if the following conditions are true: 
 
1) In a DPF environment 
2) A query is run that features a correlated subquery. 
3) The query compiler chose an access plan for this query that 
contains a listener TQ to flow the correlated values. 
4) There is an operation against the correlated column in the 
subquery that happens as a pushdown operation.  This problem was 
discovered for a scenario where an aggregation (for example, 
sum, min, max...) was being done against the correlated column. 
 
This crash produces similar errors in the db2diag.log: 
2013-04-24-16.36.52.495582-240 I42353678E620         LEVEL: 
Severe 
PID     : 16424                TID : 140291218597632 PROC : 
db2sysc 0 
INSTANCE: userid               NODE : 000            DB   : 
SAMPLE 
APPHDL  : 0-152                APPID: *N0.userid.130424203620 
AUTHID  : USERID               HOSTNAME: lab01 
EDUID   : 1373                 EDUNAME: db2agntp 0 
FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_ffdc, 
probe:250 
RETCODE : ZRC=0x87120007=-2028863481=SQLR_SEVERE_PGM_ERROR 
          "Severe programming error" 
          DIA8516C A severe internal processing error has 
occurred. 
 
2013-04-24-16.36.52.684856-240 E42504930E1608        LEVEL: 
Severe 
PID     : 16424                TID : 140291218597632 PROC : 
db2sysc 0 
INSTANCE: userid               NODE : 000            DB   : 
SAMPLE 
APPHDL  : 0-152                APPID: *N0.userid.130424203620 
AUTHID  : USERID               HOSTNAME: lab01 
EDUID   : 1373                 EDUNAME: db2agntp 0 
FUNCTION: DB2 UDB, oper system services, sqloEDUCodeTrapHandler, 
probe:90 
MESSAGE : ADM14011C  A critical failure has caused the following 
type of error: 
          "Trap". The DB2 database manager cannot recover from 
the failure. 
          First Occurrence Data Capture (FODC) was invoked in 
the following 
          mode: "Automatic". FODC diagnostic information is 
located in the 
          following directory: 
 
"/db_log/userid/db2dump/FODC_Trap_2013-04-24-16.36.42.792877_000 
0/". 
DATA #1 : Signal Number Recieved, 4 bytes 
11 
DATA #2 : Siginfo, 128 bytes 
0x00007F981800FD70 : 0B00 0000 0000 0000 0100 0000 0000 0000 
................ 
0x00007F981800FD80 : 0000 0000 0000 0000 0000 0000 0000 0000 
................ 
0x00007F981800FD90 : 0000 0000 0000 0000 0000 0000 0000 0000 
................ 
0x00007F981800FDA0 : 0000 0000 0000 0000 0000 0000 0000 0000 
................ 
0x00007F981800FDB0 : 0000 0000 0000 0000 0000 0000 0000 0000 
................ 
0x00007F981800FDC0 : 0000 0000 0000 0000 0000 0000 0000 0000 
................ 
0x00007F981800FDD0 : 0000 0000 0000 0000 0000 0000 0000 0000 
................ 
0x00007F981800FDE0 : 0000 0000 0000 0000 0000 0000 0000 0000 
................ 
 
2013-04-24-16.36.52.688762-240 I42506539E2268        LEVEL: 
Event 
PID     : 16424                TID : 140291218597632 PROC : 
db2sysc 0 
INSTANCE: userid               NODE : 000            DB   : 
SAMPLE 
APPHDL  : 0-152                APPID: *N0.userid.130424203620 
AUTHID  : USERID               HOSTNAME: lab01 
EDUID   : 1373                 EDUNAME: db2agntp 0 
FUNCTION: DB2 UDB, oper system services, 
sqloPGRPRegisterOneCrash, probe:2154 
MESSAGE : lastCrashCount 
DATA #1 : unsigned integer, 8 bytes 
0 
DATA #2 : String, 10 bytes 
inRecovery 
DATA #3 : Boolean, 1 bytes 
false 
CALLSTCK: (Static functions may not be resolved correctly, as 
they are resolved to the nearest symbol) 
  [0] 0x00007F9CD3BF05FE pdLog + 0x38E 
  [1] 0x00007F9CD604D25D sqloPGRPRegisterOneCrash + 0x17D 
  [2] 0x00007F9CD6093B11 sqloEDUCodeTrapHandler + 0x871 
  [3] 0x000000334C60F4A0 /lib64/libpthread.so.0 + 0xF4A0 
  [4] 0x00007F9CD4B473E4 _Z8sqlrirelP8sqlrr_cb + 0x84 
  [5] 0x00007F9CD6F24DC6 _Z8sqlriag2P8sqlrr_cb + 0x376 
  [6] 0x00007F9CD4B371C8 
_Z19sqlriExecSargThreadP8sqlrr_cbP12sqlri_opparm + 0x38 
  [7] 0x00007F9CD4B3709C 
_Z30sqlriPDGroupInvokePostPDThreadP8sqlrr_cbP21sqlriPushdownGrou 
pObjPi + 0x3C 
  [8] 0x00007F9CD6F24D59 _Z8sqlriag2P8sqlrr_cb + 0x309 
  [9] 0x00007F9CD6D7D5DB 
_Z16sqldEvalDataPredP13SQLD_DFM_WORKPmP10SQLD_DPRED + 0x19B 
  [10] 0x00007F9CD6F576EA 
_Z8sqlsfetcP8sqeAgentP8SQLD_CCBiP10SQLD_DPREDPP10SQLD_VALUEP8SQL 
Z_RIDPc + 0xC2A 
  [11] 0x00007F9CD6F2FFF3 _Z10sqlriFetchP8sqlrr_cbP9sqlri_taol + 
0x183 
  [12] 0x00007F9CD6F3F114 _Z7sqlritaP8sqlrr_cb + 0x514 
  [13] 0x00007F9CD6F331BD 
_Z15sqlriSectInvokeP8sqlrr_cbP12sqlri_opparm + 0x1AD 
  [14] 0x00007F9CD62DDA6D _Z16sqlrr_dss_routerP8sqlrr_cb + 0x6CD 
  [15] 0x00007F9CD4A85E8E 
_Z21sqlrr_subagent_routerP8sqeAgentP12SQLE_DB2RA_T + 0x4BE 
  [16] 0x00007F9CD3EBD4E2 
/db_config/userid/sqllib/lib64/libdb2e.so.1 + 0x12184E2 
  [17] 0x00007F9CD3EBC743 _Z21sqleProcessSubRequestP8sqeAgent + 
0xE3 
  [18] 0x00007F9CD3ED6E04 _ZN8sqeAgent6RunEDUEv + 0x604 
  [19] 0x00007F9CD4EBC213 _ZN9sqzEDUObj9EDUDriverEv + 0xF3 
  [20] 0x00007F9CD4EBC119 _Z10sqlzRunEDUPcj + 0x9 
  [21] 0x00007F9CD4948FC1 sqloEDUEntry + 0x2A1 
  [22] 0x000000334C6077F1 /lib64/libpthread.so.0 + 0x77F1 
  [23] 0x000000334C2E570D clone + 0x6D
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Problem Description Above.                               * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 Fix Pack 3                       * 
****************************************************************
Local Fix:
workaround: 
It may be possible to rewrite the query text to avoid the 
correlation and/or the listener TQ.
available fix packs:
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
First Fixed in Version 10.1 Fix Pack 3
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC95386 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
16.05.2013
17.10.2013
17.10.2013
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.3 FixList
10.1.0.3 FixList