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

ASYNCHRONOUS INDEX CLEANUP FAILS ON THE STAND-BY MACHINE IN AN HADR-PAIR

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
When using the deferred type of rollout cleanup on DELETE 
statements for multidimensional clustering (MDC) tables in an 
HADR-pair, the stand-by machine may encounter an error during 
asynchronous index cleanup.  The index cleanup on the standby 
machine will occur by replaying the index cleanup log records 
from the primary machine.  DB2 should not be starting an 
asynchronous index cleanup job on the standby machine and 
this job will be placed into error state when it is started. 
 
Deferred rollout cleanup can be specified by one of the 
following: 
- the CURRENT MDC ROLLOUT MODE special register 
- setting the registry variable DB2_MDC_ROLLOUT to DEFER 
 
The following errors will be seen in the db2diag.log on the 
stand-by machine: 
 
2011-07-29-21.21.42.130032-240 I89255A537         LEVEL: Warning 
PID     : 1060916              TID  : 17309       PROC : db2sysc 
INSTANCE: ztoth                NODE : 000         DB   : HADRDB 
APPHDL  : 0-27                 APPID: *LOCAL.DB2.110730012143 
AUTHID  : ZTOTH 
EDUID   : 17309                EDUNAME: db2taskp (HADRDB) 
FUNCTION: DB2 UDB, AIC, aicRolloutUpdateBlockMap, probe:590 
MESSAGE : ZRC=0x80100469=-2146433943=SQLP_HDRS_READ_ONLY 
          "The operation that attempted to modify the contents 
of the database failed" 
 
2011-07-29-21.21.42.130357-240 I89793A6811        LEVEL: Error 
PID     : 1060916              TID  : 17309       PROC : db2sysc 
INSTANCE: ztoth                NODE : 000         DB   : HADRDB 
APPHDL  : 0-27                 APPID: *LOCAL.DB2.110730012143 
AUTHID  : ZTOTH 
EDUID   : 17309                EDUNAME: db2taskp (HADRDB) 
FUNCTION: DB2 UDB, AIC, aicRolloutIndexCleanup, probe:2060 
MESSAGE : ZRC=0x80100469=-2146433943=SQLP_HDRS_READ_ONLY 
          "The operation that attempted to modify the contents 
of the database failed" 
 
... 
 
2011-07-29-21.21.42.130965-240 I96605A638         LEVEL: Error 
PID     : 1060916              TID  : 17309       PROC : db2sysc 
INSTANCE: ztoth                NODE : 000         DB   : HADRDB 
APPHDL  : 0-27                 APPID: *LOCAL.DB2.110730012143 
AUTHID  : ZTOTH 
EDUID   : 17309                EDUNAME: db2taskp (HADRDB) 
FUNCTION: DB2 UDB, AIC, aicTaskProcessorCleanup, probe:846 
MESSAGE : ZRC=0x80100469=-2146433943=SQLP_HDRS_READ_ONLY 
          "The operation that attempted to modify the contents 
of the database failed" 
RETCODE : ZRC=0x82A90067=-2102853529=ABP_TASK_PRO_ERROR 
          "Task processor encountered an error" 
 
... 
 
2011-07-29-21.21.42.145343-240 I104374A1400       LEVEL: Error 
PID     : 1060916              TID  : 17309       PROC : db2sysc 
INSTANCE: ztoth                NODE : 000         DB   : HADRDB 
APPHDL  : 0-27                 APPID: *LOCAL.DB2.110730012143 
AUTHID  : ZTOTH 
EDUID   : 17309                EDUNAME: db2taskp (HADRDB) 
FUNCTION: DB2 UDB, AIC, aicRolloutTaskProcessor, probe:2050 
MESSAGE : ZRC=0x82A90067=-2102853529=ABP_TASK_PRO_ERROR 
          "Task processor encountered an error" 
DATA #1 : String, 18 bytes 
pAicTaskProHandle: 
DATA #2 : Hexdump, 40 bytes 
0x07000000AF3FE258 : 0700 0001 2CE5 11A0 0700 0001 2CE5 1208 
....,.......,... 
0x07000000AF3FE268 : 0000 0000 0000 0000 0700 0001 2CE5 1298 
............,... 
0x07000000AF3FE278 : 0000 0000 0000 0000 
........ 
DATA #3 : AIC_RO_TASK_PRO_INFO, PD_AIC_TYPE_RO_TASK_PRO_INFO, 72 
bytes 
 
... 
 
2011-07-29-21.21.42.145779-240 E105775A833        LEVEL: Error 
PID     : 1060916              TID  : 17309       PROC : db2sysc 
INSTANCE: ztoth                NODE : 000         DB   : HADRDB 
APPHDL  : 0-27                 APPID: *LOCAL.DB2.110730012143 
AUTHID  : ZTOTH 
EDUID   : 17309                EDUNAME: db2taskp (HADRDB) 
FUNCTION: DB2 UDB, ABP, 
ABPDispatcher::updateAssignedTaskProCont, probe:100 
MESSAGE : ADM13500E  An agent executing an asynchronous 
background task 
          processor encountered an unrecoverable error. The task 
processor has 
          been suspended and diagnostic information was written 
to the db2diag 
          log file. Contact IBM Support for assistance. The task 
processor 
          context is "0x070000012CE511A0". The task processor 
description is 
          "MDC Rollout Index Cleaner".
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users using an HADR configuration                            * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* When using the deferred type of rollout cleanup on DELETE    * 
* statements for multidimensional clustering (MDC) tables in   * 
* an                                                           * 
* HADR-pair, the stand-by machine may encounter an error       * 
* during                                                       * 
* asynchronous index cleanup.  The index cleanup on the        * 
* standby                                                      * 
* machine will occur by replaying the index cleanup log        * 
* records                                                      * 
* from the primary machine.  DB2 should not be starting an     * 
* asynchronous index cleanup job on the standby machine and    * 
* this job will be placed into error state when it is started. * 
*                                                              * 
* Deferred rollout cleanup can be specified by one of the      * 
* following:                                                   * 
* - the CURRENT MDC ROLLOUT MODE special register              * 
* - setting the registry variable DB2_MDC_ROLLOUT to DEFER     * 
*                                                              * 
* The following errors will be seen in the db2diag.log on the  * 
* stand-by machine:                                            * 
*                                                              * 
* 2011-07-29-21.21.42.130032-240 I89255A537        LEVEL:      * 
* Warning                                                      * 
* PID    : 1060916              TID  : 17309      PROC :       * 
* db2sysc                                                      * 
* INSTANCE: ztoth                NODE : 000        DB  :       * 
* HADRDB                                                       * 
* APPHDL  : 0-27                APPID: *LOCAL.DB2.110730012143 * 
* AUTHID  : ZTOTH                                              * 
* EDUID  : 17309                EDUNAME: db2taskp (HADRDB)     * 
* FUNCTION: DB2 UDB, AIC, aicRolloutUpdateBlockMap, probe:590  * 
* MESSAGE : ZRC=0x80100469=-2146433943=SQLP_HDRS_READ_ONLY     * 
*           "The operation that attempted to modify the        * 
* contents                                                     * 
* of the database failed"                                      * 
*                                                              * 
*                                                              * 
* 2011-07-29-21.21.42.130357-240 I89793A6811        LEVEL:     * 
* Error                                                        * 
* PID    : 1060916              TID  : 17309      PROC :       * 
* db2sysc                                                      * 
* INSTANCE: ztoth                NODE : 000        DB  :       * 
* HADRDB                                                       * 
* APPHDL  : 0-27                APPID: *LOCAL.DB2.110730012143 * 
*                                                              * 
* AUTHID  : ZTOTH                                              * 
*                                                              * 
* EDUID  : 17309                EDUNAME: db2taskp (HADRDB)     * 
*                                                              * 
* FUNCTION: DB2 UDB, AIC, aicRolloutIndexCleanup, probe:2060   * 
*                                                              * 
* MESSAGE : ZRC=0x80100469=-2146433943=SQLP_HDRS_READ_ONLY     * 
*                                                              * 
*           "The operation that attempted to modify the        * 
* contents                                                     * 
* of the database failed"                                      * 
*                                                              * 
* ...                                                          * 
*                                                              * 
* 2011-07-29-21.21.42.130965-240 I96605A638        LEVEL:      * 
* Error                                                        * 
* PID    : 1060916              TID  : 17309      PROC :       * 
* db2sysc                                                      * 
* INSTANCE: ztoth                NODE : 000        DB  :       * 
* HADRDB                                                       * 
* APPHDL  : 0-27                APPID: *LOCAL.DB2.110730012143 * 
*                                                              * 
* AUTHID  : ZTOTH                                              * 
*                                                              * 
* EDUID  : 17309                EDUNAME: db2taskp (HADRDB)     * 
*                                                              * 
* FUNCTION: DB2 UDB, AIC, aicTaskProcessorCleanup, probe:846   * 
*                                                              * 
* MESSAGE : ZRC=0x80100469=-2146433943=SQLP_HDRS_READ_ONLY     * 
*                                                              * 
*           "The operation that attempted to modify the        * 
* contents                                                     * 
* of the database failed"                                      * 
* RETCODE : ZRC=0x82A90067=-2102853529=ABP_TASK_PRO_ERROR      * 
*                                                              * 
*           "Task processor encountered an error"              * 
*                                                              * 
* ...                                                          * 
*                                                              * 
* 2011-07-29-21.21.42.145343-240 I104374A1400      LEVEL:      * 
* Error                                                        * 
* PID    : 1060916              TID  : 17309      PROC :       * 
* db2sysc                                                      * 
* INSTANCE: ztoth                NODE : 000        DB  :       * 
* HADRDB                                                       * 
* APPHDL  : 0-27                APPID: *LOCAL.DB2.110730012143 * 
*                                                              * 
* AUTHID  : ZTOTH                                              * 
* EDUID  : 17309                EDUNAME: db2taskp (HADRDB)     * 
* FUNCTION: DB2 UDB, AIC, aicRolloutTaskProcessor, probe:2050  * 
* MESSAGE : ZRC=0x82A90067=-2102853529=ABP_TASK_PRO_ERROR      * 
*           "Task processor encountered an error"              * 
* DATA #1 : String, 18 bytes                                   * 
* pAicTaskProHandle:                                           * 
* DATA #2 : Hexdump, 40 bytes                                  * 
* 0x07000000AF3FE258 : 0700 0001 2CE5 11A0 0700 0001 2CE5 1208 * 
* ....,.......,...                                             * 
* 0x07000000AF3FE268 : 0000 0000 0000 0000 0700 0001 2CE5 1298 * 
* ............,...                                             * 
*                                                              * 
* 0x07000000AF3FE278 : 0000 0000 0000 0000                     * 
* ........                                                     * 
*                                                              * 
* DATA #3 : AIC_RO_TASK_PRO_INFO,                              * 
* PD_AIC_TYPE_RO_TASK_PRO_INFO, 72 bytes                       * 
*                                                              * 
* ...                                                          * 
*                                                              * 
* 2011-07-29-21.21.42.145779-240 E105775A833        LEVEL:     * 
* Error                                                        * 
* PID    : 1060916              TID  : 17309      PROC :       * 
* db2sysc                                                      * 
* INSTANCE: ztoth                NODE : 000        DB  :       * 
* HADRDB                                                       * 
* APPHDL  : 0-27                APPID: *LOCAL.DB2.110730012143 * 
* AUTHID  : ZTOTH                                              * 
* EDUID  : 17309                EDUNAME: db2taskp (HADRDB)     * 
* FUNCTION: DB2 UDB, ABP,                                      * 
* ABPDispatcher::updateAssignedTaskProCont, probe:100          * 
* MESSAGE : ADM13500E  An agent executing an asynchronous      * 
* background task                                              * 
*           processor encountered an unrecoverable error. The  * 
* task processor has                                           * 
*           been suspended and diagnostic information was      * 
* written to the db2diag                                       * 
*           log file. Contact IBM Support for assistance. The  * 
* taskprocessor                                                * 
*           context is "0x070000012CE511A0". The task          * 
* processor description is                                     * 
*           "MDC Rollout Index Cleaner".                       * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 9.7.0.5.                                      * 
****************************************************************
Local Fix:
Contact DB2 support for assistance in removing the MDC Rollout 
Index Cleaner task processor that is in error state.
available fix packs:
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
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
The problem is first fixed in DB2 9.7.0.5.
Workaround
Contact DB2 support for assistance in removing the MDC Rollout 
Index Cleaner task processor that is in error state.
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
03.08.2011
08.12.2011
08.12.2011
Problem solved at the following versions (IBM BugInfos)
9.7.0.5
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.5 FixList