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

DB2 V9.1 CRASH DURING IDENTITY COLUMN PROCESSING in DPF.

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
Crash during identity column processing. 
 
The problem applies to 
a) DPF (partitioned database) 
b) identity columns 
c) tables that have been dropped or altered 
d) static SQL issued after the alter/drop of the table within 
the same transaction as the alter/drop. 
 
The db2diag.log in DB2 V9.1 shows the message 
 
     43 2011-05-23-09.05.02.701007-300 I2022A1695         LEVEL: 
Severe 
     44 PID     : 415322               TID  : 1           PROC : 
db2agntp (SAMPLE) 0 
     45 INSTANCE: db2inst             NODE : 000 
     46 APPHDL  : 0-582                APPID: 
GA1C61E8.H0C9.110523140502 
     47 AUTHID  : USERID 
     48 FUNCTION: DB2 UDB, data management, 
sqldSeqFetchUpdateGen, probe:1 
     49 MESSAGE : DTS mismatch: Sequence Request: 
     50 DATA #1 : Hexdump, 248 bytes 
     51 0x0FFFFFFFFFFFCC28 : 0000 0000 0000 0000 0000 0011 0000 
000B    ................ 
     52 0x0FFFFFFFFFFFCC38 : 0000 0001 0000 0000 0000 0000 0000 
0001    ................ 
     53 0x0FFFFFFFFFFFCC48 : 0000 0000 0000 0000 0000 0000 0000 
2011    .............. . 
     54 0x0FFFFFFFFFFFCC58 : 0520 0905 0187 8612 0000 0000 0000 
0000    . .............. 
     55 0x0FFFFFFFFFFFCC68 : 0000 0000 0000 0000 0000 0000 0000 
0000    ................ 
     56 0x0FFFFFFFFFFFCC78 : 0000 0000 0000 0000 0000 0000 0000 
0000    ................ 
     57 0x0FFFFFFFFFFFCC88 : 0000 0000 0000 0000 0000 0000 0000 
0000    ................ 
     58 0x0FFFFFFFFFFFCC98 : 0000 0000 0000 0000 0000 0000 0000 
0000    ................ 
     59 0x0FFFFFFFFFFFCCA8 : 0002 1F00 0001 0000 0FFF FFFF FFFF 
CCF0    ................ 
     60 0x0FFFFFFFFFFFCCB8 : 0000 0000 0000 0000 0000 0000 0000 
0000    ................ 
     61 0x0FFFFFFFFFFFCCC8 : 0000 0000 0000 0000 0000 0000 0000 
0000    ................ 
     62 0x0FFFFFFFFFFFCCD8 : 0000 0000 0000 0000 0000 0000 0000 
0000    ................ 
     63 0x0FFFFFFFFFFFCCE8 : 0000 0000 0000 0000 0000 0000 0000 
0000    ................ 
     64 0x0FFFFFFFFFFFCCF8 : 0000 0000 0000 0000 0000 0000 0000 
0000    ................ 
     65 0x0FFFFFFFFFFFCD08 : 0000 0000 0000 0000 0000 0000 0000 
0000    ................ 
     66 0x0FFFFFFFFFFFCD18 : 0000 0000 0000 0000 
       ........ 
 
and eventually the message that marks the database bad 
 
3495 2011-05-23-09.05.02.913135-300 E141962A374        LEVEL: 
Severe 
   3496 PID     : 415322               TID  : 1           PROC : 
db2agntp (SAMPLE) 0 
   3497 INSTANCE: db2inst             NODE : 000 
   3498 APPHDL  : 0-582                APPID: 
GA1C61E8.H0C9.110523140502 
   3499 AUTHID  : USERID 
   3500 FUNCTION: DB2 UDB, base sys utilities, sqleMarkDBad, 
probe:10 
   3501 MESSAGE : ADM7518C  "SAMPLE" marked bad. 
   3502 
   3503 2011-05-23-09.05.02.913285-300 I142337A387        LEVEL: 
Severe 
   3504 PID     : 415322               TID  : 1           PROC : 
db2agntp (SAMPLE) 0 
   3505 INSTANCE: db2inst             NODE : 000 
   3506 APPHDL  : 0-582                APPID: 
GA1C61E8.H0C9.110523140502 
   3507 AUTHID  : USERID 
   3508 FUNCTION: DB2 UDB, base sys utilities, sqleMarkDBad, 
probe:210 
   3509 MESSAGE : Database logging stopped due to mark db bad. 
 
The corresponding trap file, t415322.000, for PID 415322 shows 
the following 
... 
   4984 <StackTrace> 
   4985 -------Frame------ ------Function + Offset------ 
   4986 0x09000000022E0D08 sqloDumpEDU + 0x14 
   4987 0x0900000002561678 
sqldDumpContext__FP20sqle_agent_privatecbiN42PcPvT2 + 0x130 
   4988 0x09000000023D85E4 sqlrr_dump_ffdc__FP8sqlrr_cbiT2 + 
0x464 
   4989 0x09000000023D8030 
sqlzeDumpFFDC__FP20sqle_agent_privatecbUiP5sqlcai + 0x24 
   4990 0x09000000023DBD68 
sqlzeDumpFFDC__FP20sqle_agent_privatecbUiP5sqlcai@glue6B + 0x7C 
   4991 0x09000000025E03E0 
sqlzeMapZrc__FP20sqle_agent_privatecbUiUlT2P5sqlcai + 0x1A8 
   4992 0x090000000361312C sqlri_SeqGetNext__FP8sqlrr_cb + 0x320 
   4993 0x09000000033387E8 
sqlriSectInvoke__FP8sqlrr_cbP12sqlri_opparm + 0x4 
   4994 0x09000000039AE4E4 sqlrr_dss_router__FP8sqlrr_cb + 0x234 
   4995 0x090000000233E0D4 
sqlrr_subagent_router__FP20sqle_agent_privatecbP10sqle_db2ra + 
0x4A0 
   4996 0x09000000021E2278 
sqleSubRequestRouter__FP13sqle_agent_cbPUiT2 + 0x420 
   4997 0x0900000003879A98 
sqleProcessSubRequest__FP13sqle_agent_cb + 0x230 
   4998 0x09000000022DDC7C sqleRunAgent__FPcUi + 0x8E8 
   4999 0x09000000033E6EE4 
sqloCreateEDU__FPFPcUi_vPcUlP13SQLO_EDU_INFOPi + 0x260 
   5000 0x09000000033E6724 @49@sqloRunGDS__Fv + 0xDC 
   5001 0x09000000033E5C38 sqloInitEDUServices + 0x17C 
   5002 0x0900000002AED898 
@49@sqloSystemControllerMain__FCUiPFv_iPFi_vPPvCPi + 0x730 
   5003 0x09000000031FC99C sqloRunInstance + 0xA8 
   5004 0x00000001000029FC DB2main + 0x934 
   5005 0x0000000100003D58 main + 0x10 
   5006 </StackTrace> 
... 
   6692 -------Frame------ ------Function + Offset------ 
   6693 0x09000000022E0D08 sqloDumpEDU + 0x14 
   6694 0x0900000002186B54 sqleMarkDBad__FP8sqledbcb + 0x1A8 
   6695 0x0900000003879B70 
sqleProcessSubRequest__FP13sqle_agent_cb + 0x308 
   6696 0x09000000022DDC7C sqleRunAgent__FPcUi + 0x8E8 
   6697 0x09000000033E6EE4 
sqloCreateEDU__FPFPcUi_vPcUlP13SQLO_EDU_INFOPi + 0x260 
   6698 0x09000000033E6724 @49@sqloRunGDS__Fv + 0xDC 
   6699 0x09000000033E5C38 sqloInitEDUServices + 0x17C 
   6700 0x0900000002AED898 
@49@sqloSystemControllerMain__FCUiPFv_iPFi_vPPvCPi + 0x730 
   6701 0x09000000031FC99C sqloRunInstance + 0xA8 
   6702 0x00000001000029FC DB2main + 0x934 
   6703 0x0000000100003D58 main + 0x10 
   6704 </StackTrace> 
...
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* The problem applies to                                       * 
* a) DPF (partitioned database)                                * 
* b) identity columns                                          * 
* c) tables that have been dropped or altered                  * 
* d) static SQL issued after the alter/drop of the table       * 
* within                                                       * 
* the same transaction as the alter/drop.                      * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
* Crash during identity column processing.                     * 
*                                                              * 
* The problem applies to                                       * 
* a) DPF (partitioned database)                                * 
* b) identity columns                                          * 
* c) tables that have been dropped or altered                  * 
* d) static SQL issued after the alter/drop of the table       * 
* within                                                       * 
* the same transaction as the alter/drop.                      * 
*                                                              * 
* The db2diag.log in DB2 V9.1 shows the message                * 
*                                                              * 
*      43 2011-05-23-09.05.02.701007-300 I2022A1695            * 
* LEVEL:                                                       * 
* Severe                                                       * 
*      44 PID     : 415322               TID  : 1              * 
* PROC :                                                       * 
* db2agntp (SAMPLE) 0                                          * 
*      45 INSTANCE: db2inst             NODE : 000             * 
*      46 APPHDL  : 0-582                APPID:                * 
* GA1C61E8.H0C9.110523140502                                   * 
*      47 AUTHID  : USERID                                     * 
*      48 FUNCTION: DB2 UDB, data management,                  * 
* sqldSeqFetchUpdateGen, probe:1                               * 
*      49 MESSAGE : DTS mismatch: Sequence Request:            * 
*      50 DATA #1 : Hexdump, 248 bytes                         * 
*      51 0x0FFFFFFFFFFFCC28 : 0000 0000 0000 0000 0000 0011   * 
* 0000                                                         * 
* 000B    ................                                     * 
*      52 0x0FFFFFFFFFFFCC38 : 0000 0001 0000 0000 0000 0000   * 
* 0000                                                         * 
* 0001    ................                                     * 
*      53 0x0FFFFFFFFFFFCC48 : 0000 0000 0000 0000 0000 0000   * 
* 0000                                                         * 
* 2011    .............. .                                     * 
*      54 0x0FFFFFFFFFFFCC58 : 0520 0905 0187 8612 0000 0000   * 
* 0000                                                         * 
* 0000    . ..............                                     * 
*      55 0x0FFFFFFFFFFFCC68 : 0000 0000 0000 0000 0000 0000   * 
* 0000                                                         * 
* 0000    ................                                     * 
*      56 0x0FFFFFFFFFFFCC78 : 0000 0000 0000 0000 0000 0000   * 
* 0000                                                         * 
* 0000    ................                                     * 
*      57 0x0FFFFFFFFFFFCC88 : 0000 0000 0000 0000 0000 0000   * 
* 0000                                                         * 
* 0000    ................                                     * 
*      58 0x0FFFFFFFFFFFCC98 : 0000 0000 0000 0000 0000 0000   * 
* 0000                                                         * 
* 0000    ................                                     * 
*      59 0x0FFFFFFFFFFFCCA8 : 0002 1F00 0001 0000 0FFF FFFF   * 
* FFFF                                                         * 
* CCF0    ................                                     * 
*      60 0x0FFFFFFFFFFFCCB8 : 0000 0000 0000 0000 0000 0000   * 
* 0000                                                         * 
* 0000    ................                                     * 
*      61 0x0FFFFFFFFFFFCCC8 : 0000 0000 0000 0000 0000 0000   * 
* 0000                                                         * 
* 0000    ................                                     * 
*      62 0x0FFFFFFFFFFFCCD8 : 0000 0000 0000 0000 0000 0000   * 
* 0000                                                         * 
* 0000    ................                                     * 
*      63 0x0FFFFFFFFFFFCCE8 : 0000 0000 0000 0000 0000 0000   * 
* 0000                                                         * 
* 0000    ................                                     * 
*      64 0x0FFFFFFFFFFFCCF8 : 0000 0000 0000 0000 0000 0000   * 
* 0000                                                         * 
* 0000    ................                                     * 
*      65 0x0FFFFFFFFFFFCD08 : 0000 0000 0000 0000 0000 0000   * 
* 0000                                                         * 
* 0000    ................                                     * 
*      66 0x0FFFFFFFFFFFCD18 : 0000 0000 0000 0000             * 
*        ........                                              * 
*                                                              * 
* and eventually the message that marks the database bad       * 
*                                                              * 
* 3495 2011-05-23-09.05.02.913135-300 E141962A374              * 
* LEVEL:                                                       * 
* Severe                                                       * 
*    3496 PID     : 415322               TID  : 1              * 
* PROC :                                                       * 
* db2agntp (SAMPLE) 0                                          * 
*    3497 INSTANCE: db2inst             NODE : 000             * 
*    3498 APPHDL  : 0-582                APPID:                * 
* GA1C61E8.H0C9.110523140502                                   * 
*    3499 AUTHID  : USERID                                     * 
*    3500 FUNCTION: DB2 UDB, base sys utilities, sqleMarkDBad, * 
* probe:10                                                     * 
*    3501 MESSAGE : ADM7518C  "SAMPLE" marked bad.             * 
*    3502                                                      * 
*    3503 2011-05-23-09.05.02.913285-300 I142337A387           * 
* LEVEL:                                                       * 
* Severe                                                       * 
*    3504 PID     : 415322               TID  : 1              * 
* PROC :                                                       * 
* db2agntp (SAMPLE) 0                                          * 
*    3505 INSTANCE: db2inst             NODE : 000             * 
*    3506 APPHDL  : 0-582                APPID:                * 
* GA1C61E8.H0C9.110523140502                                   * 
*    3507 AUTHID  : USERID                                     * 
*    3508 FUNCTION: DB2 UDB, base sys utilities, sqleMarkDBad, * 
* probe:210                                                    * 
*    3509 MESSAGE : Database logging stopped due to mark db    * 
* bad.                                                         * 
*                                                              * 
* The corresponding trap file, t415322.000, for PID 415322     * 
* shows                                                        * 
* the following                                                * 
* ...                                                          * 
*    4984 <StackTrace>                                         * 
*    4985 -------Frame------ ------Function + Offset------     * 
*    4986 0x09000000022E0D08 sqloDumpEDU + 0x14                * 
*    4987 0x0900000002561678                                   * 
* sqldDumpContext__FP20sqle_agent_privatecbiN42PcPvT2 + 0x130  * 
*    4988 0x09000000023D85E4 sqlrr_dump_ffdc__FP8sqlrr_cbiT2 + * 
* 0x464                                                        * 
*    4989 0x09000000023D8030                                   * 
* sqlzeDumpFFDC__FP20sqle_agent_privatecbUiP5sqlcai + 0x24     * 
*    4990 0x09000000023DBD68                                   * 
* sqlzeDumpFFDC__FP20sqle_agent_privatecbUiP5sqlcai@glue6B +   * 
* 0x7C                                                         * 
*    4991 0x09000000025E03E0                                   * 
* sqlzeMapZrc__FP20sqle_agent_privatecbUiUlT2P5sqlcai + 0x1A8  * 
*    4992 0x090000000361312C sqlri_SeqGetNext__FP8sqlrr_cb +   * 
* 0x320                                                        * 
*    4993 0x09000000033387E8                                   * 
* sqlriSectInvoke__FP8sqlrr_cbP12sqlri_opparm + 0x4            * 
*    4994 0x09000000039AE4E4 sqlrr_dss_router__FP8sqlrr_cb +   * 
* 0x234                                                        * 
*    4995 0x090000000233E0D4                                   * 
* sqlrr_subagent_router__FP20sqle_agent_privatecbP10sqle_db2ra * 
* +                                                            * 
* 0x4A0                                                        * 
*    4996 0x09000000021E2278                                   * 
* sqleSubRequestRouter__FP13sqle_agent_cbPUiT2 + 0x420         * 
*    4997 0x0900000003879A98                                   * 
* sqleProcessSubRequest__FP13sqle_agent_cb + 0x230             * 
*    4998 0x09000000022DDC7C sqleRunAgent__FPcUi + 0x8E8       * 
*    4999 0x09000000033E6EE4                                   * 
* sqloCreateEDU__FPFPcUi_vPcUlP13SQLO_EDU_INFOPi + 0x260       * 
*    5000 0x09000000033E6724 @49@sqloRunGDS__Fv + 0xDC         * 
*    5001 0x09000000033E5C38 sqloInitEDUServices + 0x17C       * 
*    5002 0x0900000002AED898                                   * 
* @49@sqloSystemControllerMain__FCUiPFv_iPFi_vPPvCPi + 0x730   * 
*    5003 0x09000000031FC99C sqloRunInstance + 0xA8            * 
*    5004 0x00000001000029FC DB2main + 0x934                   * 
*    5005 0x0000000100003D58 main + 0x10                       * 
*    5006 </StackTrace>                                        * 
* ...                                                          * 
*    6692 -------Frame------ ------Function + Offset------     * 
*    6693 0x09000000022E0D08 sqloDumpEDU + 0x14                * 
*    6694 0x0900000002186B54 sqleMarkDBad__FP8sqledbcb + 0x1A8 * 
*    6695 0x0900000003879B70                                   * 
* sqleProcessSubRequest__FP13sqle_agent_cb + 0x308             * 
*    6696 0x09000000022DDC7C sqleRunAgent__FPcUi + 0x8E8       * 
*    6697 0x09000000033E6EE4                                   * 
* sqloCreateEDU__FPFPcUi_vPcUlP13SQLO_EDU_INFOPi + 0x260       * 
*    6698 0x09000000033E6724 @49@sqloRunGDS__Fv + 0xDC         * 
*    6699 0x09000000033E5C38 sqloInitEDUServices + 0x17C       * 
*    6700 0x0900000002AED898                                   * 
* @49@sqloSystemControllerMain__FCUiPFv_iPFi_vPPvCPi + 0x730   * 
*    6701 0x09000000031FC99C sqloRunInstance + 0xA8            * 
*    6702 0x00000001000029FC DB2main + 0x934                   * 
*    6703 0x0000000100003D58 main + 0x10                       * 
*    6704 </StackTrace>                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 9.7 FP6.                                      * 
****************************************************************
Local Fix:
Workarounds are : 
a) commit the drop/alter 
b) use declare global temporary table (DGTT). 
c) if the failure is within a SQL stored procedure then 
recompile the stored procedure by dropping and recreating it.
available fix packs:
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 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 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Solution
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
14.09.2011
25.06.2012
25.06.2012
Problem solved at the following versions (IBM BugInfos)
9.7.FP6
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.6 FixList