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

UPDATE/DELETE OPERATION FROM A TABLE AFTER ONLINE TABLE MOVE CAUSES DB2
TO CRASH

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
After an Online Table Move following migration from V91 or V95 
to V97, any update/delete operation from the table causes DB2 to 
crash.  This occurs only if the V91 or V95 table contains XML 
documents that are validated with XML indexes defined on them. 
 
 
 
The message in db2diag.log indicated the key was not found: 
 
 
RETCODE : ZRC=0x8709002C=-2029453268=SQLI_NOKEY "Key not found 
within node" 
          DIA8541C The index key could not be found, the value 
was "". 
 
Stack trace in FODC shows the following: 
 
0x00002B38C56E2917 sqloDumpEDU + 0x0037 
                (/home/singgih/sqllib/lib64/libdb2e.so.1) 
0x00002B38C6E20004 address: 0x00002B38C6E20004 ; dladdress: 
0x00002B38C1EF8000 ; offset in lib: 0x0000000004F28004 ; 
                (/home/singgih/sqllib/lib64/libdb2e.so.1) 
0x00002B38C6E18CFB _Z8sqlischdP7SQLI_CBP11SQLI_SDGLOBtj + 0x0ecd 
                (/home/singgih/sqllib/lib64/libdb2e.so.1) 
0x00002B38C6D9AEB9 
_Z8sqlidelkP8sqeAgentP9SQLD_IXCBP10SQLI_IXPCRP8SQLD_KEY8SQLZ_RID 
mP16SQLB_OBJECT_DESC 
+ 0x0c55 
                (/home/singgih/sqllib/lib64/libdb2e.so.1) 
0x00002B38C7317D25 address: 0x00002B38C7317D25 ; dladdress: 
0x00002B38C1EF8000 ; offset in lib: 0x000000000541FD25 ; 
                (/home/singgih/sqllib/lib64/libdb2e.so.1) 
0x00002B38C7316BE7 
_Z26xmlsProcessValuesKeyBufferP8sqeAgentP13SQLD_DFM_WORK8SQLZ_RI 
DPP14SQLP_LOCK_INFOmmP16SQLD_TABLE_CACHE 
+ 0x0203 
                (/home/singgih/sqllib/lib64/libdb2e.so.1) 
0x00002B38C385BEEE 
_Z13sqldKeyDeleteP13SQLD_DFM_WORKP8SQLD_TCBP13SQLD_TDATAREC8SQLZ 
_RIDim 
+ 0x0b1a 
                (/home/singgih/sqllib/lib64/libdb2e.so.1) 
0x00002B38C385CE81 _Z13sqldRowDeleteP8sqeAgentP8SQLD_CCBm + 
0x0b13 
                (/home/singgih/sqllib/lib64/libdb2e.so.1) 
0x00002B38C5F2AD23 _Z8sqlridelP8sqlrr_cb + 0x068f 
                (/home/singgih/sqllib/lib64/libdb2e.so.1) 
0x00002B38C5E71FB1 _Z15sqlriExecThreadP8sqlrr_cbP12sqlri_opparm 
+ 0x0561 
                (/home/singgih/sqllib/lib64/libdb2e.so.1) 
0x00002B38C5F1D083 _Z15sqlriSectInvokeP8sqlrr_cbP12sqlri_opparm 
+ 0x051b 
                (/home/singgih/sqllib/lib64/libdb2e.so.1) 
0x00002B38C5ACE0B0 _Z23sqlrr_execute_immediateP8sqlrr_cbi + 
0x12c8 
                (/home/singgih/sqllib/lib64/libdb2e.so.1) 
0x00002B38C5AA2550 
_Z14sqlrr_execimmdP14db2UCinterfaceP16db2UCprepareInfo + 0x01d6 
                (/home/singgih/sqllib/lib64/libdb2e.so.1) 
0x00002B38C3E6E3C5 
_Z19sqljs_ddm_excsqlimmP14db2UCinterfaceP13sqljDDMObject + 
0x0199 
                (/home/singgih/sqllib/lib64/libdb2e.so.1) 
0x00002B38C3E4525E 
_Z21sqljsParseRdbAccessedP13sqljsDrdaAsCbP13sqljDDMObjectP14db2U 
Cinterface 
+ 0x0242 
                (/home/singgih/sqllib/lib64/libdb2e.so.1) 
0x00002B38C3E46260 
_Z10sqljsParseP13sqljsDrdaAsCbP14db2UCinterface + 0x019c 
                (/home/singgih/sqllib/lib64/libdb2e.so.1) 
0x00002B38C3E3CEDE address: 0x00002B38C3E3CEDE ; dladdress: 
0x00002B38C1EF8000 ; offset in lib: 0x0000000001F44EDE ; 
 
This problem is not limited to Online Table Move.  A 
LOAD from the migrated table, or INSERT-SELECT from the migrated 
table will also cause the same problem during update/delete 
operation.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users migrating from V9.1 or V9.5 to V9.7.                   * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* After an Online Table Move following migration from V91 or   * 
* V95                                                          * 
* to V97, any update/delete operation from the table causes    * 
* DB2 to                                                       * 
* crash.  This occurs only if the V91 or V95 table contains    * 
* XML                                                          * 
* documents that are validated with XML indexes defined on     * 
* them.                                                        * 
*                                                              * 
*                                                              * 
*                                                              * 
*                                                              * 
*                                                              * 
*                                                              * 
* The message in db2diag.log indicated the key was not found:  * 
*                                                              * 
*                                                              * 
*                                                              * 
*                                                              * 
*                                                              * 
* RETCODE : ZRC=0x8709002C=-2029453268=SQLI_NOKEY "Key not     * 
* found                                                        * 
* within node"                                                 * 
*                                                              * 
* DIA8541C The index key could not be found, the               * 
* value                                                        * 
* was "".                                                      * 
*                                                              * 
*                                                              * 
*                                                              * 
* Stack trace in FODC shows the following:                     * 
*                                                              * 
*                                                              * 
*                                                              * 
* 0x00002B38C56E2917 sqloDumpEDU + 0x0037                      * 
*                                                              * 
* (/home/singgih/sqllib/lib64/libdb2e.so.1)                    * 
*                                                              * 
* 0x00002B38C6E20004 address: 0x00002B38C6E20004 ; dladdress:  * 
*                                                              * 
* 0x00002B38C1EF8000 ; offset in lib: 0x0000000004F28004 ;     * 
*                                                              * 
* (/home/singgih/sqllib/lib64/libdb2e.so.1)                    * 
*                                                              * 
* 0x00002B38C6E18CFB _Z8sqlischdP7SQLI_CBP11SQLI_SDGLOBtj +    * 
* 0x0ecd                                                       * 
* (/home/singgih/sqllib/lib64/libdb2e.so.1)                    * 
*                                                              * 
* 0x00002B38C6D9AEB9                                           * 
*                                                              * 
* _Z8sqlidelkP8sqeAgentP9SQLD_IXCBP10SQLI_IXPCRP8SQLD_KEY8SQLZ_R 
* mP16SQLB_OBJECT_DESC                                         * 
*                                                              * 
* + 0x0c55                                                     * 
*                                                              * 
* (/home/singgih/sqllib/lib64/libdb2e.so.1)                    * 
*                                                              * 
* 0x00002B38C7317D25 address: 0x00002B38C7317D25 ; dladdress:  * 
*                                                              * 
* 0x00002B38C1EF8000 ; offset in lib: 0x000000000541FD25 ;     * 
*                                                              * 
* (/home/singgih/sqllib/lib64/libdb2e.so.1)                    * 
*                                                              * 
* 0x00002B38C7316BE7                                           * 
*                                                              * 
* _Z26xmlsProcessValuesKeyBufferP8sqeAgentP13SQLD_DFM_WORK8SQLZ_ 
* DPP14SQLP_LOCK_INFOmmP16SQLD_TABLE_CACHE                     * 
*                                                              * 
* + 0x0203                                                     * 
*                                                              * 
* (/home/singgih/sqllib/lib64/libdb2e.so.1)                    * 
*                                                              * 
* 0x00002B38C385BEEE                                           * 
*                                                              * 
* _Z13sqldKeyDeleteP13SQLD_DFM_WORKP8SQLD_TCBP13SQLD_TDATAREC8SQ 
* _RIDim                                                       * 
*                                                              * 
* + 0x0b1a                                                     * 
*                                                              * 
* (/home/singgih/sqllib/lib64/libdb2e.so.1)                    * 
*                                                              * 
* 0x00002B38C385CE81 _Z13sqldRowDeleteP8sqeAgentP8SQLD_CCBm +  * 
*                                                              * 
* 0x0b13                                                       * 
*                                                              * 
* (/home/singgih/sqllib/lib64/libdb2e.so.1)                    * 
*                                                              * 
* 0x00002B38C5F2AD23 _Z8sqlridelP8sqlrr_cb + 0x068f            * 
*                                                              * 
* (/home/singgih/sqllib/lib64/libdb2e.so.1)                    * 
*                                                              * 
* 0x00002B38C5E71FB1                                           * 
* _Z15sqlriExecThreadP8sqlrr_cbP12sqlri_opparm                 * 
* + 0x0561                                                     * 
*                                                              * 
* (/home/singgih/sqllib/lib64/libdb2e.so.1)                    * 
*                                                              * 
* 0x00002B38C5F1D083                                           * 
* _Z15sqlriSectInvokeP8sqlrr_cbP12sqlri_opparm                 * 
* + 0x051b                                                     * 
*                                                              * 
* (/home/singgih/sqllib/lib64/libdb2e.so.1)                    * 
*                                                              * 
* 0x00002B38C5ACE0B0 _Z23sqlrr_execute_immediateP8sqlrr_cbi +  * 
*                                                              * 
* 0x12c8                                                       * 
*                                                              * 
* (/home/singgih/sqllib/lib64/libdb2e.so.1)                    * 
*                                                              * 
* 0x00002B38C5AA2550                                           * 
*                                                              * 
* _Z14sqlrr_execimmdP14db2UCinterfaceP16db2UCprepareInfo +     * 
* 0x01d6                                                       * 
* (/home/singgih/sqllib/lib64/libdb2e.so.1)                    * 
*                                                              * 
* 0x00002B38C3E6E3C5                                           * 
*                                                              * 
* _Z19sqljs_ddm_excsqlimmP14db2UCinterfaceP13sqljDDMObject +   * 
*                                                              * 
* 0x0199                                                       * 
*                                                              * 
* (/home/singgih/sqllib/lib64/libdb2e.so.1)                    * 
*                                                              * 
* 0x00002B38C3E4525E                                           * 
*                                                              * 
* _Z21sqljsParseRdbAccessedP13sqljsDrdaAsCbP13sqljDDMObjectP14db 
* Cinterface                                                   * 
*                                                              * 
* + 0x0242                                                     * 
*                                                              * 
* (/home/singgih/sqllib/lib64/libdb2e.so.1)                    * 
*                                                              * 
* 0x00002B38C3E46260                                           * 
*                                                              * 
* _Z10sqljsParseP13sqljsDrdaAsCbP14db2UCinterface + 0x019c     * 
*                                                              * 
* (/home/singgih/sqllib/lib64/libdb2e.so.1)                    * 
*                                                              * 
* 0x00002B38C3E3CEDE address: 0x00002B38C3E3CEDE ; dladdress:  * 
*                                                              * 
* 0x00002B38C1EF8000 ; offset in lib: 0x0000000001F44EDE ;     * 
*                                                              * 
*                                                              * 
*                                                              * 
* This problem is not limited to Online Table Move.  A         * 
*                                                              * 
* LOAD from the migrated table, or INSERT-SELECT from the      * 
* migrated                                                     * 
* table will also cause the same problem during update/delete  * 
*                                                              * 
* operation.                                                   * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to fix pack 1                                        * 
****************************************************************
Local Fix:
Run REORG INDEX after Online Table Move is completed, or run 
Online Table Move with the REORG  option. 
 
Warning: Running reorgs on large tables may be time consuming.
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
This is fixed in V9.7 Fix pack 1.
Workaround
Run REORG INDEX after Online Table Move is completed, or run 
 
 
Online Table Move with the REORG  option. 
 
Warning: Running reorgs on large tables may be time consuming.
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
10.11.2009
18.01.2010
18.01.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