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

UPGRADE DB FAILS WITH SQL1226N DUE TO DEFERRED MDC ROLLOUT CLEANUP

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
UPGRADE DB command fails with SQL1226N due to deferred MDC 
rollout cleanup. 
 
The problem is caused by have outstanding async index cleanup to 
perform that were the result of deferred MDC rollout deletes. 
 
db2diag.log has the following error messages. 
 
2011-05-23-10.29.31.209047-240 I1952E262           LEVEL: 
Warning 
PID     : 32668                TID  : 47232692838320PROC : db2bp 
INSTANCE: db2inst1             NODE : 001 
FUNCTION: DB2 UDB, base sys utilities, sqlemgdb, probe:1 
MESSAGE : Restore flag is false 
 
2011-05-23-10.29.31.209439-240 I2215E262           LEVEL: 
Warning 
PID     : 32668                TID  : 47232692838320PROC : db2bp 
INSTANCE: db2inst1             NODE : 001 
FUNCTION: DB2 UDB, base sys utilities, sqlemgdb, probe:10 
MESSAGE : Begin engn migration 
 
..... 
 
2011-05-23-10.30.01.423810-240 I6513E454           LEVEL: Severe 
PID     : 16464                TID  : 47407702206784PROC : 
db2sysc 1 
INSTANCE: db2inst1             NODE : 001          DB   : SAMPLE 
APPHDL  : 1-284                APPID: *N1.db2inst1.110523143002 
AUTHID  : db2inst1 
EDUID   : 618                  EDUNAME: db2agent (SAMPLE) 1 
FUNCTION: DB2 UDB, base sys utilities, 
sqlePrepareForSerialization, probe:30 
RETCODE : ZRC=0xFFFFEC55=-5035 
 
2011-05-23-10.30.01.424217-240 I6968E460           LEVEL: Severe 
PID     : 16464                TID  : 47407702206784PROC : 
db2sysc 1 
INSTANCE: db2inst1             NODE : 001          DB   : SAMPLE 
APPHDL  : 1-284                APPID: *N1.db2inst1.110523143002 
AUTHID  : db2inst1 
EDUID   : 618                  EDUNAME: db2agent (SAMPLE) 1 
FUNCTION: DB2 UDB, base sys utilities, 
sqeDBMgr::StartUsingLocalDatabase, probe:10 
 
..... 
 
2011-05-23-10.30.11.189544-240 I17291E1145         LEVEL: Error 
PID     : 19395                TID  : 47325833587008PROC : 
db2sysc 14 
INSTANCE: db2inst1             NODE : 014          DB   : SAMPLE 
APPHDL  : 1-282                APPID: *N1.db2inst1.110523142931 
AUTHID  : db2inst1 
EDUID   : 1015                 EDUNAME: db2agntp (SAMPLE) 14 
FUNCTION: DB2 UDB, ABP, ABPIcoordAgent::spawnIcoordAgent, 
probe:200 
MESSAGE : ZRC=0x8005006D=-2147155859=SQLE_CA_BUILT 
          "SQLCA has been built and saved in component specific 
control block." 
CALLED  : DB2 UDB, base sys utilities, 
sqeIcoordCB::DispatchIndependentDBAgent 
RETCODE : ZRC=0x80A90442=-2136406974=ABP_NO_AGENT 
          "Maximum number of connections reached." 
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes 
 sqlcaid : SQLCA     sqlcabc: 136   sqlcode: -5035   sqlerrml: 0 
 sqlerrmc: 
 sqlerrp : SQL09073 
 sqlerrd : (1) 0x00000000      (2) 0x00000000      (3) 
0x00000000 
           (4) 0x00000000      (5) 0x00000000      (6) 
0x0000000E 
 sqlwarn : (1)      (2)      (3)      (4)        (5)       (6) 
 
           (7)      (8)      (9)      (10)        (11) 
 sqlstate: 
 
2011-05-23-10.30.11.190007-240 I18437E599          LEVEL: Severe 
PID     : 19395                TID  : 47325833587008PROC : 
db2sysc 14 
INSTANCE: db2inst1             NODE : 014          DB   : SAMPLE 
APPHDL  : 1-282                APPID: *N1.db2inst1.110523142931 
AUTHID  : db2inst1 
EDUID   : 1015                 EDUNAME: db2agntp (SAMPLE) 14 
FUNCTION: DB2 UDB, data management, sqldMigrateOtherDMSObjects, 
probe:2097 
RETCODE : ZRC=0x80A90442=-2136406974=ABP_NO_AGENT 
          "Maximum number of connections reached." 
MESSAGE : Error detected at line: 
DATA #1 : unsigned integer, 8 bytes 
1930 
 
2011-05-23-10.30.11.192032-240 I19037E630          LEVEL: Severe 
PID     : 19395                TID  : 47325833587008PROC : 
db2sysc 14 
INSTANCE: db2inst1             NODE : 014          DB   : SAMPLE 
APPHDL  : 1-282                APPID: *N1.db2inst1.110523142931 
AUTHID  : db2inst1 
EDUID   : 1015                 EDUNAME: db2agntp (SAMPLE) 14 
FUNCTION: DB2 UDB, data management, sqldMigrateTablespaces, 
probe:2610 
MESSAGE : ZRC=0x80A90442=-2136406974=ABP_NO_AGENT 
          "Maximum number of connections reached." 
DATA #1 : String, 27 bytes 
Error migrating tablespace! 
DATA #2 : poolID, PD_TYPE_SQLD_POOL_ID, 2 bytes 
0x0006 
 
2011-05-23-10.30.11.192194-240 I19668E11328        LEVEL: Severe 
PID     : 19395                TID  : 47325833587008PROC : 
db2sysc 14 
INSTANCE: db2inst1             NODE : 014          DB   : SAMPLE 
APPHDL  : 1-282                APPID: *N1.db2inst1.110523142931 
AUTHID  : db2inst1 
EDUID   : 1015                 EDUNAME: db2agntp (SAMPLE) 14 
FUNCTION: DB2 UDB, data management, sqldMigrateTablespaces, 
probe:2610 
MESSAGE : ZRC=0x80A90442=-2136406974=ABP_NO_AGENT 
          "Maximum number of connections reached." 
DATA #1 : Pool control block, PD_TYPE_SQLB_POOL_CB, 5280 bytes 
  name:                   PROC_IX 
  poolID:                                  6 
  flags:                                4122 
  flags2:                                  0 
  tflags:                                  0 
  runtimeBufferPoolID:                     3 
  ondiskBufferPoolID:                      3 
  otblLastConsecPage:                     15 
  extent_size:                            16 
  prefetch_size:                          64 
  page_size:                           16384 
  truncThreshold:                          0 
  readLatch: 
{ 
   state         = 0x0000000000000000 
                 = { 
                       held X: 0 
                       reserved for X: 0 
                       shared holders: 0 
                       firstSharIndex: 0x0 
                       firstExclIndex: 0x0 
                   } 
   starve X mode = false 
   xWaitCount    = 0 
   requestCount  = 0 
   identity      = SQLB_POOL_CB::readLatch (208) 
} 
  writeLatch: 
{ 
   state         = 0x0000000000000000 
                 = { 
                       held X: 0 
                       reserved for X: 0 
                       shared holders: 0 
                       firstSharIndex: 0x0 
                       firstExclIndex: 0x0 
                   } 
   starve X mode = false 
   xWaitCount    = 0 
   requestCount  = 0 
   identity      = SQLB_POOL_CB::writeLatch (211) 
} 
  sysTempInUseLatch: 
{ 
   state         = 0x0000000000000000 
                 = { 
                       held X: 0 
                       reserved for X: 0 
                       shared holders: 0 
                       firstSharIndex: 0x0 
                       firstExclIndex: 0x0 
                   } 
   starve X mode = true 
   xWaitCount    = 0 
   requestCount  = 0 
   identity      = SQLB_POOL_CB::sysTempInUseLatch (209) 
} 
  reorgPoolID:                             0 
  reorgObjID:                              0 
  tokenMap:               0x0000000000000000 
  spillMap:               0x0000000000000000 
  StateChangeObjectID:                     0 
  StateChangePoolID:                       0 
  version:                              8543 
  pool_state:                              0 
  quiesce_count:                           0 
  state_id: 
 
..... 
 
2011-05-23-10.30.18.664463-240 I265498E294         LEVEL: 
Warning 
PID     : 32668                TID  : 47232692838320PROC : db2bp 
INSTANCE: db2inst1             NODE : 001 
FUNCTION: DB2 UDB, base sys utilities, sqlemgdb, probe:20 
MESSAGE : End engn migration: with rc = -1226, sqlcode = -1226
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* UPGRADE DB fails with SQL1226N due to deferred MDC rollout   * 
* cleanup                                                      * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.7 Fixpack 5.                        * 
****************************************************************
Local Fix:
1. db2stop 
2. db2set DB2_DISABLE_ABP=ON 
3. db2start 
4. upgrade the database 
5. db2stop 
6. db2set DB2_DISABLE_ABP= 
7. db2start
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
First Fixed in DB2 Version 9.7 Fixpack 5.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
20.06.2011
09.01.2012
09.01.2012
Problem solved at the following versions (IBM BugInfos)
9.7.FP5
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.5 FixList