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

ASYNCHRONOUS PARTITION DETACH (APD) MAY DEADLOCK WITH DDL OR DML STATEMENTS
ACTING ON THE SAME PARTITIONED TABLE.

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
As of v9.7 Fix Pack 1, detaching a partition from a data 
partitioned table schedules a database manager task to complete 
the detach process asynchronously after all remaining statements 
referencing the data partitioned table have completed their 
execution. 
 
This task may deadlock with concurrently executing DML or DDL 
statements being compiled which reference the data partitioned 
table.  Entries in the db2diag.log may appear as follows: 
 
--------------------------<snip>-------------------------------- 
 
2010-08-10-04.53.29.177231+540 I3851231A554       LEVEL: Error 
PID     : 442600               TID  : 19379       PROC : db2sysc 
0 
INSTANCE: dwadm                NODE : 000         DB   : LMDW 
APPHDL  : 0-11168              APPID: *N0.DB2.100809204623 
AUTHID  : BDUSR 
EDUID   : 19379                EDUNAME: db2taskp (LMDW) 0 
FUNCTION: DB2 UDB, catalog services, 
sqlrlCatalogScan::postUpdateCacheHandlin, probe:10 
RETCODE : ZRC=0x80100002=-2146435070=SQLP_LDED "Dead lock 
detected" 
          DIA8002C A deadlock has occurred, rolling back 
transaction. 
 
2010-08-10-04.53.29.187665+540 I3851786A538       LEVEL: Error 
PID     : 442600               TID  : 19379       PROC : db2sysc 
0 
INSTANCE: dwadm                NODE : 000         DB   : LMDW 
APPHDL  : 0-11168              APPID: *N0.DB2.100809204623 
AUTHID  : BDUSR 
EDUID   : 19379                EDUNAME: db2taskp (LMDW) 0 
FUNCTION: DB2 UDB, catalog services, sqlrlCatalogScan::update, 
probe:80 
RETCODE : ZRC=0x80100002=-2146435070=SQLP_LDED "Dead lock 
detected" 
          DIA8002C A deadlock has occurred, rolling back 
transaction. 
 
2010-08-10-04.53.29.191663+540 I3852325A542       LEVEL: Error 
PID     : 442600               TID  : 19379       PROC : db2sysc 
0 
INSTANCE: dwadm                NODE : 000         DB   : LMDW 
APPHDL  : 0-11168              APPID: *N0.DB2.100809204623 
AUTHID  : BDUSR 
EDUID   : 19379                EDUNAME: db2taskp (LMDW) 0 
FUNCTION: DB2 UDB, catalog services, 
sqlrlAlterDropCatalogChange,    probe:300 
RETCODE : ZRC=0x80100002=-2146435070=SQLP_LDED "Dead lock 
detected" 
          DIA8002C A deadlock has occurred, rolling back 
transaction. 
 
2010-08-10-04.53.29.195661+540 I3852868A544       LEVEL: Error 
PID     : 442600               TID  : 19379       PROC : db2sysc 
0 
INSTANCE: dwadm                NODE : 000         DB   : LMDW 
APPHDL  : 0-11168              APPID: *N0.DB2.100809204623 
AUTHID  : BDUSR 
EDUID   : 19379                EDUNAME: db2taskp (LMDW) 0 
FUNCTION: DB2 UDB, catalog services, 
sqlrlAlterDetachCatalogChange,   probe:100 
RETCODE : ZRC=0x80100002=-2146435070=SQLP_LDED "Dead lock 
detected" 
          DIA8002C A deadlock has occurred, rolling back 
transaction. 
 
2010-08-10-04.53.29.199664+540 I3853413A729       LEVEL: Error 
PID     : 442600               TID  : 19379       PROC : db2sysc 
0 
INSTANCE: dwadm                NODE : 000         DB   : LMDW 
APPHDL  : 0-11168              APPID: *N0.DB2.100809204623 
AUTHID  : BDUSR 
EDUID   : 19379                EDUNAME: db2taskp (LMDW) 0 
FUNCTION: DB2 UDB, AIC, apdTaskProcessor, probe:1128 
MESSAGE : ZRC=0x80100002=-2146435070=SQLP_LDED "Dead lock 
detected" 
          DIA8002C A deadlock has occurred, rolling back 
transaction. 
DATA #1 : String, 60 bytes 
APD ERROR DURING PROCESSING: poolID/objectID/partitionID !!! 
DATA #2 : unsigned integer, 2 bytes 
65530 
DATA #3 : unsigned integer, 2 bytes 
33002 
DATA #4 : unsigned integer, 2 bytes 
5 
 
2010-08-10-04.53.29.203663+540 I3854143A1013      LEVEL: Warning 
PID     : 442600               TID  : 19379       PROC : db2sysc 
0 
INSTANCE: dwadm                NODE : 000         DB   : LMDW 
APPHDL  : 0-11168              APPID: *N0.DB2.100809204623 
AUTHID  : BDUSR 
EDUID   : 19379                EDUNAME: db2taskp (LMDW) 0 
FUNCTION: DB2 UDB, AIC, apdTaskProcessorCleanup, probe:194 
MESSAGE : ZRC=0x80100002=-2146435070=SQLP_LDED "Dead lock 
detected" 
          DIA8002C A deadlock has occurred, rolling back 
transaction. 
CALLED  : DB2 UDB, AIC, apdTaskProcessor 
RETCODE : ZRC=0x82A90066=-2102853530=ABP_SUSPEND_TASK_PRO 
          "Suspend the task processor" 
DATA #1 : String, 28 bytes 
Source Table Schema and Name 
DATA #2 : String, 8 bytes 
LM_DW 
DATA #3 : String, 13 bytes 
DY_STK_201008 
DATA #4 : String, 12 bytes 
Partition ID 
DATA #5 : unsigned integer, 2 bytes 
5 
DATA #6 : String, 28 bytes 
Target Table Schema and Name 
DATA #7 : String, 8 bytes 
LM_DW 
DATA #8 : String, 19 bytes 
DY_STK_201008_PART5 
 
--------------------------</snip>--------------------------- 
 
In a deadlock event, the APD process will always be chosen as 
the victim, and hence, rescheduled to complete its task at a 
later time.  If the same process continually encounters 
deadocks, then the newly detached target table will not be 
accessible.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* As of v9.7 Fix Pack 1, detaching a partition from a data     * 
* partitioned table schedules a database manager task to       * 
* complete                                                     * 
* the detach process asynchronously after all remaining        * 
* statements                                                   * 
* referencing the data partitioned table have completed their  * 
* execution.                                                   * 
*                                                              * 
* This task may deadlock with concurrently executing DML or    * 
* DDL                                                          * 
* statements being compiled which reference the data           * 
* partitioned                                                  * 
* table. Entries in the db2diag.log may appear as follows:     * 
*                                                              * 
* --------------------------<snip>------------------------------ 
*                                                              * 
* 2010-08-10-04.53.29.177231+540 I3851231A554 LEVEL: Error     * 
* PID : 442600 TID : 19379 PROC : db2sysc                      * 
* 0                                                            * 
* INSTANCE: dwadm NODE : 000 DB : LMDW                         * 
* APPHDL : 0-11168 APPID: *N0.DB2.100809204623                 * 
* AUTHID : BDUSR                                               * 
* EDUID : 19379 EDUNAME: db2taskp (LMDW) 0                     * 
* FUNCTION: DB2 UDB, catalog services,                         * 
* sqlrlCatalogScan::postUpdateCacheHandlin, probe:10           * 
* RETCODE : ZRC=0x80100002=-2146435070=SQLP_LDED "Dead lock    * 
* detected"                                                    * 
* DIA8002C A deadlock has occurred, rolling back               * 
* transaction.                                                 * 
*                                                              * 
* 2010-08-10-04.53.29.187665+540 I3851786A538 LEVEL: Error     * 
* PID : 442600 TID : 19379 PROC : db2sysc                      * 
* 0                                                            * 
* INSTANCE: dwadm NODE : 000 DB : LMDW                         * 
* APPHDL : 0-11168 APPID: *N0.DB2.100809204623                 * 
* AUTHID : BDUSR                                               * 
* EDUID : 19379 EDUNAME: db2taskp (LMDW) 0                     * 
* FUNCTION: DB2 UDB, catalog services,                         * 
* sqlrlCatalogScan::update,                                    * 
* probe:80                                                     * 
* RETCODE : ZRC=0x80100002=-2146435070=SQLP_LDED "Dead lock    * 
* detected"                                                    * 
* DIA8002C A deadlock has occurred, rolling back               * 
* transaction.                                                 * 
*                                                              * 
* 2010-08-10-04.53.29.191663+540 I3852325A542 LEVEL: Error     * 
* PID : 442600 TID : 19379 PROC : db2sysc                      * 
* 0                                                            * 
* INSTANCE: dwadm NODE : 000 DB : LMDW                         * 
* APPHDL : 0-11168 APPID: *N0.DB2.100809204623                 * 
* AUTHID : BDUSR                                               * 
* EDUID : 19379 EDUNAME: db2taskp (LMDW) 0                     * 
* FUNCTION: DB2 UDB, catalog services,                         * 
* sqlrlAlterDropCatalogChange, probe:300                       * 
* RETCODE : ZRC=0x80100002=-2146435070=SQLP_LDED "Dead lock    * 
* detected"                                                    * 
* DIA8002C A deadlock has occurred, rolling back               * 
* transaction.                                                 * 
*                                                              * 
* 2010-08-10-04.53.29.195661+540 I3852868A544 LEVEL: Error     * 
* PID : 442600 TID : 19379 PROC : db2sysc                      * 
* 0                                                            * 
* INSTANCE: dwadm NODE : 000 DB : LMDW                         * 
* APPHDL : 0-11168 APPID: *N0.DB2.100809204623                 * 
* AUTHID : BDUSR                                               * 
* EDUID : 19379 EDUNAME: db2taskp (LMDW) 0                     * 
* FUNCTION: DB2 UDB, catalog services,                         * 
* sqlrlAlterDetachCatalogChange, probe:100                     * 
* RETCODE : ZRC=0x80100002=-2146435070=SQLP_LDED "Dead lock    * 
* detected"                                                    * 
* DIA8002C A deadlock has occurred, rolling back               * 
* transaction.                                                 * 
*                                                              * 
* 2010-08-10-04.53.29.199664+540 I3853413A729 LEVEL: Error     * 
* PID : 442600 TID : 19379 PROC : db2sysc                      * 
* 0                                                            * 
* INSTANCE: dwadm NODE : 000 DB : LMDW                         * 
* APPHDL : 0-11168 APPID: *N0.DB2.100809204623                 * 
* AUTHID : BDUSR                                               * 
* EDUID : 19379 EDUNAME: db2taskp (LMDW) 0                     * 
* FUNCTION: DB2 UDB, AIC, apdTaskProcessor, probe:1128         * 
* MESSAGE : ZRC=0x80100002=-2146435070=SQLP_LDED "Dead lock    * 
* detected"                                                    * 
* DIA8002C A deadlock has occurred, rolling back               * 
* transaction.                                                 * 
* DATA #1 : String, 60 bytes                                   * 
* APD ERROR DURING PROCESSING: poolID/objectID/partitionID !!! * 
* DATA #2 : unsigned integer, 2 bytes                          * 
* 65530                                                        * 
* DATA #3 : unsigned integer, 2 bytes                          * 
* 33002                                                        * 
* DATA #4 : unsigned integer, 2 bytes                          * 
* 5                                                            * 
*                                                              * 
* 2010-08-10-04.53.29.203663+540 I3854143A1013 LEVEL: Warning  * 
* PID : 442600 TID : 19379 PROC : db2sysc                      * 
* 0                                                            * 
* INSTANCE: dwadm NODE : 000 DB : LMDW                         * 
* APPHDL : 0-11168 APPID: *N0.DB2.100809204623                 * 
* AUTHID : BDUSR                                               * 
* EDUID : 19379 EDUNAME: db2taskp (LMDW) 0                     * 
* FUNCTION: DB2 UDB, AIC, apdTaskProcessorCleanup, probe:194   * 
* MESSAGE : ZRC=0x80100002=-2146435070=SQLP_LDED "Dead lock    * 
* detected"                                                    * 
* DIA8002C A deadlock has occurred, rolling back               * 
* transaction.                                                 * 
* CALLED : DB2 UDB, AIC, apdTaskProcessor                      * 
* RETCODE : ZRC=0x82A90066=-2102853530=ABP_SUSPEND_TASK_PRO    * 
* "Suspend the task processor"                                 * 
* DATA #1 : String, 28 bytes                                   * 
* Source Table Schema and Name                                 * 
* DATA #2 : String, 8 bytes                                    * 
* LM_DW                                                        * 
* DATA #3 : String, 13 bytes                                   * 
* DY_STK_201008                                                * 
* DATA #4 : String, 12 bytes                                   * 
* Partition ID                                                 * 
* DATA #5 : unsigned integer, 2 bytes                          * 
* 5                                                            * 
* DATA #6 : String, 28 bytes                                   * 
* Target Table Schema and Name                                 * 
* DATA #7 : String, 8 bytes                                    * 
* LM_DW                                                        * 
* DATA #8 : String, 19 bytes                                   * 
* DY_STK_201008_PART5                                          * 
*                                                              * 
* --------------------------</snip>--------------------------- * 
*                                                              * 
* In a deadlock event, the APD process will always be chosen   * 
* as                                                           * 
* the victim, and hence, rescheduled to complete its task at a * 
* later time. If the same process continually encounters       * 
* deadocks, then the newly detached target table will not be   * 
* accessible.                                                  * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.7 Fix Pack 4.                       * 
****************************************************************
Local Fix:
APD processes will re-attempt to execute approximately every 5 
minutes.  Cease attempting to access the data partitioned table 
and the newly detached target table until the target has been 
fully detached.  You can scan the SYSCAT.DATAPARTITIONS catalog 
view, and look for 'L' or 'I' in the STATUS column for any 
remaining partitions which have yet to complete their 
asynchronous process (ie. both asynchronous partition detach and 
asynchronous index cleanup if applicable).
available fix packs:
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 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
Problem was first fixed in Version 9.7 Fix Pack 4.
Workaround
APD processes will re-attempt to execute approximately every 5 
minutes. Cease attempting to access the data partitioned table 
and the newly detached target table until the target has been 
fully detached. You can scan the SYSCAT.DATAPARTITIONS catalog 
view, and look for 'L' or 'I' in the STATUS column for any 
 
remaining partitions which have yet to complete their 
asynchronous process (ie. both asynchronous partition detach and 
asynchronous index cleanup if applicable).
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
23.08.2010
05.05.2011
05.05.2011
Problem solved at the following versions (IBM BugInfos)
9.7.FP4
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.4 FixList