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

SQL1224N from select count() using XMLTABLE with COLUMN PATH that uses
FLWR statement

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
A select count() query is crashing the database because we are 
marking the "elements" node for extraction but not allocating a 
sqlz value for binding out the result. During navigation tuple 
construction we try to initialize the sqlz value but trap 
because it was never allocated previously. 
 
Sample Query: 
 
select count(1) 
FROM networkmessage n, 
     XMLTABLE ('$n/NetworkMessage' passing n.value as "n" 
       COLUMNS 
     cardId                         VARCHAR(100)    PATH 
'*:cardId', 
     groupId                        VARCHAR(100)    PATH 
'*:groupId', 
     res_p3_processing_cd_blast     VARCHAR(100)    PATH 'for $i 
in (*:response/*:elements) where $i/*:id = "3" return 
$i/*:value', 
     res_p3_processing_cd_visa      VARCHAR(100)    PATH 'for $i 
in (*:response/*:elements/*:elements) where $i/../*:id = "3" and 
$i/*:id = "1" return $i/*:value' 
) AS X 
LEFT JOIN Card c ON X.cardId = c.id; 
 
SQL ERROR: 
 
SQL1224N  The database manager is not able to accept new 
requests, has 
terminated all requests in progress, or has terminated your 
particular request 
due to an error or a force interrupt.  SQLSTATE=55032 
 
STACK: 
 
00002ADCF95E1BBC _ZN11OSSTrapFile6dumpExEmiP7siginfoPvm + 0x00b4 
00002ADCF95E1C83 _ZN11OSSTrapFile4dumpEmiP7siginfoPv + 0x0009 
00002ADCF5B4FA35 sqlo_trce + 0x03f3 
00002ADCF5B8E45D sqloEDUCodeTrapHandler + 0x0107 
0000003FA320DE70 address: 0x0000003FA320DE70 ; dladdress: 
0x0000003FA3200000 ; offset in lib: 0x000000000000DE70 ; 
00002ADCF4B3667F 
_ZN21XmlnvTupleConstructor12m_initZValueEP10sqlz_valueP16XmlnvBu 
fferArrayi + 0x0011 
00002ADCF65FBED8 
_ZN21XmlnvTupleConstructor22m_initTupleConstructorEP12sqlriXNavO 
bjP14XmlnvAutomaton + 0x03be 
00002ADCF65ED981 
_ZN14XmlnvAutomaton15m_initAutomatonEP14XmlnvNavigatorP12sqlriXN 
avObj + 0x02a1 
00002ADCF65F729B 
_ZN14XmlnvNavigator15m_initNavigatorEP13SQLO_MEM_POOLP11XMLSTORE 
_CBP12sqlriXNavObjP12XmlrnNodeMgrP8sqlrr_cb + 0x02d5 
00002ADCF65F6EC9 
_ZN14XmlnvNavigatorC9EP13SQLO_MEM_POOLP11XMLSTORE_CBP12sqlriXNav 
ObjP8sqlrr_cbPi + 0x0065 
00002ADCF65F6FC4 
_ZN14XmlnvNavigatorC1EP13SQLO_MEM_POOLP11XMLSTORE_CBP12sqlriXNav 
ObjP8sqlrr_cbPi + 0x0006 
00002ADCF5F45FD0 _Z12sqlriXMLScanP8sqlrr_cb + 0x0350 
00002ADCF675562C _Z14sqlriNljnPipedP8sqlrr_cb + 0x0230 
00002ADCF674E338 _Z15sqlriSectInvokeP8sqlrr_cbP12sqlri_opparm + 
0x00b2 
00002ADCF498394E 
_Z10sqlrr_openP14db2UCinterfaceP15db2UCCursorInfo + 0x076a 
00002ADCF46D00B4 
_Z16sqljs_ddm_opnqryP14db2UCinterfaceP13sqljDDMObject + 0x015c 
00002ADCF46C7202 
_Z21sqljsParseRdbAccessedP13sqljsDrdaAsCbP13sqljDDMObjectP14db2U 
Cinterface + 0x03b2 
00002ADCF46C757D _Z10sqljsParseP13sqljsDrdaAsCbP14db2UCinterface 
+ 0x030d 
00002ADCF46C5244 address: 0x00002ADCF46C5244 ; dladdress: 
0x00002ADCF35E3000 ; offset in lib: 0x00000000010E2244 ; 
00002ADCF46C4FD6 address: 0x00002ADCF46C4FD6 ; dladdress: 
0x00002ADCF35E3000 ; offset in lib: 0x00000000010E1FD6 ; 
00002ADCF46C2DF5 address: 0x00002ADCF46C2DF5 ; dladdress: 
0x00002ADCF35E3000 ; offset in lib: 0x00000000010DFDF5 ; 
00002ADCF46C2C9B _Z17sqljsDrdaAsDriverP18SQLCC_INITSTRUCT_T + 
0x0051 
00002ADCF462947A _ZN8sqeAgent6RunEDUEv + 0x00c2 
00002ADCF4B28291 _ZN9sqzEDUObj9EDUDriverEv + 0x006d 
00002ADCF4B28221 _Z10sqlzRunEDUPcj + 0x0009 
00002ADCF4913B04 sqloEDUEntry + 0x02d0 
0000003FA32062F7 address: 0x0000003FA32062F7 ; dladdress: 
0x0000003FA3200000 ; offset in lib: 0x00000000000062F7 ; 
0000003FA26D1B6D clone + 0x006d 
        (/lib64/libc.so.6)
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 LUW All Platforms                                        * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* A select count() query is crashing the database because we   * 
* are                                                          * 
* marking the "elements" node for extraction but not           * 
* allocating a                                                 * 
* sqlz value for binding out the result. During navigation     * 
* tuple                                                        * 
* construction we try to initialize the sqlz value but trap    * 
*                                                              * 
* because it was never allocated previously.                   * 
*                                                              * 
*                                                              * 
*                                                              * 
* Sample Query:                                                * 
*                                                              * 
*                                                              * 
*                                                              * 
* select count(1)                                              * 
*                                                              * 
* FROM networkmessage n,                                       * 
*                                                              * 
*      XMLTABLE ('$n/NetworkMessage' passing n.value as "n"    * 
*                                                              * 
*        COLUMNS                                               * 
*                                                              * 
*      cardId                         VARCHAR(100)    PATH     * 
*                                                              * 
* '*:cardId',                                                  * 
*                                                              * 
*      groupId                        VARCHAR(100)    PATH     * 
*                                                              * 
* '*:groupId',                                                 * 
*                                                              * 
*      res_p3_processing_cd_blast     VARCHAR(100)    PATH     * 
* 'for $i                                                      * 
* in (*:response/*:elements) where $i/*:id = "3" return        * 
*                                                              * 
* $i/*:value',                                                 * 
*                                                              * 
*      res_p3_processing_cd_visa      VARCHAR(100)    PATH     * 
* 'for $i                                                      * 
* in (*:response/*:elements/*:elements) where $i/../*:id = "3" * 
* and                                                          * 
* $i/*:id = "1" return $i/*:value'                             * 
*                                                              * 
* ) AS X                                                       * 
*                                                              * 
* LEFT JOIN Card c ON X.cardId = c.id;                         * 
*                                                              * 
*                                                              * 
*                                                              * 
* SQL ERROR:                                                   * 
*                                                              * 
*                                                              * 
*                                                              * 
* SQL1224N  The database manager is not able to accept new     * 
*                                                              * 
* requests, has                                                * 
*                                                              * 
* terminated all requests in progress, or has terminated your  * 
*                                                              * 
* particular request                                           * 
*                                                              * 
* due to an error or a force interrupt.  SQLSTATE=55032        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 v97 Fixpack 1                                 * 
****************************************************************
Local Fix:
Workaround query, replace "for" with "let" to avoid bad 
codepath. 
 
select count(1) 
FROM networkmessage n, 
     XMLTABLE ('$n/NetworkMessage' passing n.value as "n" 
       COLUMNS 
     cardId        VARCHAR(100) 
  PATH '*:cardId', 
     groupId       VARCHAR(100) 
 PATH '*:groupId', 
     res_p3_processing_cd_blast     VARCHAR(100)    PATH 
'*:response/*:elements[*:id = "3"]/*:value', 
     res_p3_processing_cd_visa      VARCHAR(100)    PATH 
'*:response/*:elements/*:elements[../*:id = "3" and *:id = 
"1"]/*:value' 
) AS X 
LEFT JOIN Card c ON X.cardId = c.id;
available fix packs:
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
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 10 for Linux, UNIX, and Windows

Solution
The fix allocates the sqlz value used for binding out results 
during navigation.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
29.09.2009
23.02.2010
23.02.2010
Problem solved at the following versions (IBM BugInfos)
9.7.FP1
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.1 FixList