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

SQL0901N ENCOUNTERED BY APD CLEANUP PROCESSING DURING RANGE PARTITION
DETACH

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
During range partition detachment, the DETACH is stuck in 
'Waiting' in LIST UTILITIES output, while the Asynchronous 
Detach Process (APD) processes hit -901 with "A hard 
invalidation is already taking place for this object". In the 
db2diag.log, the -901 reported for the asynchronous detach 
process may appear similar to the entry below. 
 
 
2010-09-08-21.19.33.006553-240 I3532E878           LEVEL: Severe 
PID     : 15610                TID  : 47141393262912PROC : 
db2sysc 1 
INSTANCE: db2inst1             NODE : 001          DB   : SAMPLE 
APPHDL  : 1-38495              APPID: *N1.DB2.100909011946 
AUTHID  : DB2INST1 
EDUID   : 221680               EDUNAME: db2taskp (SAMPLE) 1 
FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_ffdc, 
probe:300 
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes 
 sqlcaid : SQLCA     sqlcabc: 136   sqlcode: -901   sqlerrml: 60 
 sqlerrmc: A hard invalidation is already taking place for this 
object! 
 sqlerrp : SQLRA0B5 
 sqlerrd : (1) 0x00000000      (2) 0x00000000      (3) 
0x00000000 
           (4) 0x00000000      (5) 0xFFFFFFEC      (6) 
0x00000001 
 sqlwarn : (1)      (2)      (3)      (4)        (5)       (6) 
           (7)      (8)      (9)      (10)        (11) 
 sqlstate: 
 
 
These entries would appear for other db2taskp EDUs. Stack dumps 
are generated for these EDUs, and the stack would have 
sqlra_inval_obj_hard before the -901 is returned, e.g. 
 
<StackTrace> 
-----FUNC-ADDR---- ------FUNCTION + OFFSET------ 
0x00002ADF2F8CCF5D ossDumpStackTraceEx + 0x01e5 
 
(/var/ibmdb2/nyqxt270/sqllib/lib64/libdb2osse.so.1) 
0x00002ADF2F8C7CE2 _ZN11OSSTrapFile6dumpExEmiP7siginfoPvm + 
0x00cc 
 
(/var/ibmdb2/nyqxt270/sqllib/lib64/libdb2osse.so.1) 
0x00002ADF2CC10493 sqlo_trce + 0x0365 
                (/var/ibmdb2/nyqxt270/sqllib/lib64/libdb2e.so.1) 
0x00002ADF2CC53C99 sqloDumpDiagInfoHandler + 0x00ed 
                (/var/ibmdb2/nyqxt270/sqllib/lib64/libdb2e.so.1) 
0x00002ADF2A1E54C0 address: 0x00002ADF2A1E54C0 ; dladdress: 
0x00002ADF2A1D7000 ; offset in lib: 0x000000000000E4C0 ; 
                (/lib64/libpthread.so.0) 
0x00002ADF2A1E26B2 pthread_kill + 0x0032 
                (/lib64/libpthread.so.0) 
0x00002ADF2CC53581 sqloDumpEDU + 0x0045 
                (/var/ibmdb2/nyqxt270/sqllib/lib64/libdb2e.so.1) 
0x00002ADF2BF34874 _Z15sqldDumpContextP9sqeBsuEduiiiiiPKcPvi + 
0x069e 
                (/var/ibmdb2/nyqxt270/sqllib/lib64/libdb2e.so.1) 
0x00002ADF2B821D73 _Z15sqlrr_dump_ffdcP8sqlrr_cbii + 0x04bb 
                (/var/ibmdb2/nyqxt270/sqllib/lib64/libdb2e.so.1) 
0x00002ADF2BA19B2A _Z13sqlzeDumpFFDCP8sqeAgentjP5sqlcai + 0x0020 
                (/var/ibmdb2/nyqxt270/sqllib/lib64/libdb2e.so.1) 
0x00002ADF2BA18EB7 
_Z12sqlzeSqlCodeP8sqeAgentjmjP5sqlcaitP13__va_list_tag + 0x00f7 
                (/var/ibmdb2/nyqxt270/sqllib/lib64/libdb2e.so.1) 
0x00002ADF2CE7BD74 sqlrrSqlCode + 0x00e2 
                (/var/ibmdb2/nyqxt270/sqllib/lib64/libdb2e.so.1) 
0x00002ADF2CEE696C 
_Z20sqlra_inval_obj_hardP8sqlrr_cbP23sqlra_anchor_dependencyP23s 
qlra_cached_dependencyjiPtj 
+ 0x0102 
                (/var/ibmdb2/nyqxt270/sqllib/lib64/libdb2e.so.1) 
0x00002ADF2CEE763E 
_Z21sqlra_inval_vars_hardP8sqlrr_cbhPhjS1_sjiPtj + 0x027c 
                (/var/ibmdb2/nyqxt270/sqllib/lib64/libdb2e.so.1) 
0x00002ADF2CEE7BF4 
_Z22sqlra_event_inval_hardP8sqlrr_cbP20sqlr_rpc_apm_request + 
0x009c 
                (/var/ibmdb2/nyqxt270/sqllib/lib64/libdb2e.so.1) 
0x00002ADF2CED292C 
_Z19sqlra_execute_eventP8sqlrr_cbP20sqlr_rpc_apm_request + 
0x0332 
                (/var/ibmdb2/nyqxt270/sqllib/lib64/libdb2e.so.1) 
0x00002ADF2CED2B80 
_Z27sqlra_broadcast_request_catP8sqlrr_cbP20sqlr_rpc_apm_request 
+ 0x0124 
                (/var/ibmdb2/nyqxt270/sqllib/lib64/libdb2e.so.1) 
0x00002ADF2CED38A3 
_Z23sqlra_broadcast_requestP8sqlrr_cbP20sqlr_rpc_apm_request + 
0x0309 
                (/var/ibmdb2/nyqxt270/sqllib/lib64/libdb2e.so.1) 
0x00002ADF2CEEAD2C 
_Z20sqlra_invalidate_pkgP8sqlrr_cbPhsP11sqlrrstringhS1_scm14sqln 
q_depUsageP13sqlra_columnsjib 
+ 0x0622 
                (/var/ibmdb2/nyqxt270/sqllib/lib64/libdb2e.so.1) 
0x00002ADF2D1E5B9A 
_Z21sqlrlAlterPartCatalogP8sqlrr_cbPhsS1_thS1_sS1_tiP19sqlrl_tbs 
pace_parmsPP8sqlrg_pdP18sqlrg_datapartinfoR23sqlrg_datapartinfo_ 
itert25sqlrlDPartStageTransitionS5_P21SQLD_ATTACH_INDEX_MAPP17sq 
lrlStatsCarrierjP21SqlthJo 
bProgressPhase + 0x14b8 
                (/var/ibmdb2/nyqxt270/sqllib/lib64/libdb2e.so.1) 
0x00002ADF2D1ED33D 
_Z19sqlrlPhysicalDetachP8sqlrr_cbPP8sqlrg_pdS2_P5doid1P18sqlrg_d 
atapartinfoR23sqlrg_datapartinfo_iterP6APD_CBP21SqlthJobProgress 
Phase 
+ 0x01d1 
                (/var/ibmdb2/nyqxt270/sqllib/lib64/libdb2e.so.1) 
0x00002ADF2BAB7BC7 apdTaskProcessor + 0x03bb 
                (/var/ibmdb2/nyqxt270/sqllib/lib64/libdb2e.so.1) 
0x00002ADF2B24B908 
_ZN8ABPAgent19taskProcessorDriverEP17ABPTaskProContext + 0x016a 
                (/var/ibmdb2/nyqxt270/sqllib/lib64/libdb2e.so.1) 
0x00002ADF2B24B49A _ZN8ABPAgent4mainEP17ABPTaskProContext + 
0x0126 
                (/var/ibmdb2/nyqxt270/sqllib/lib64/libdb2e.so.1) 
0x00002ADF2B2511DC 
_Z18abpAgentEntryPointP8sqeAgentP17ABPTaskProContext + 0x0054 
                (/var/ibmdb2/nyqxt270/sqllib/lib64/libdb2e.so.1) 
0x00002ADF2B38DD43 _Z26sqleIndCoordProcessRequestP8sqeAgent + 
0x0463 
                (/var/ibmdb2/nyqxt270/sqllib/lib64/libdb2e.so.1) 
0x00002ADF2B39AEC1 _ZN8sqeAgent6RunEDUEv + 0x0381 
                (/var/ibmdb2/nyqxt270/sqllib/lib64/libdb2e.so.1) 
0x00002ADF2BA19ED8 _ZN9sqzEDUObj9EDUDriverEv + 0x00a6 
                (/var/ibmdb2/nyqxt270/sqllib/lib64/libdb2e.so.1) 
0x00002ADF2BA19E2F _Z10sqlzRunEDUPcj + 0x0009 
                (/var/ibmdb2/nyqxt270/sqllib/lib64/libdb2e.so.1) 
0x00002ADF2B7ABB0E sqloEDUEntry + 0x02f0 
                (/var/ibmdb2/nyqxt270/sqllib/lib64/libdb2e.so.1) 
0x00002ADF2A1DD367 address: 0x00002ADF2A1DD367 ; dladdress: 
0x00002ADF2A1D7000 ; offset in lib: 0x0000000000006367 ; 
                (/lib64/libpthread.so.0) 
0x00002ADF305AC0AD clone + 0x006d 
                (/lib64/libc.so.6) 
</StackTrace> 
 
 
This -901 can occur if there is a concurrent DDL running on the 
table from which the detach is detaching a partition. The same 
symptom can occur if the ADMIN_MOVE_TABLE() procedure is called 
while DDL is being performed against the same table.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* During range partition detachment, the DETACH is stuck in    * 
* 'Waiting' in LIST UTILITIES output, while the Asynchronous   * 
* Detach Process (APD) processes hit -901 with "A hard         * 
* invalidation is already taking place for this object". This  * 
* -901 can occur if there is a concurrent DDL running on the   * 
* table from which the detach is detaching a partition. The    * 
* same symptom can occur if the ADMIN_MOVE_TABLE() procedure   * 
* is called while DDL is being performed against the same      * 
* table.                                                       * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Update to Version 9.7 Fix Pack 4                             * 
****************************************************************
Local Fix:
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
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC73646 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
04.10.2010
09.05.2011
09.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