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

For online load without specifying USE <tablespace>, when an int
ernal lock escalation is needed, Load might fail and mark db bad

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
For online load (ALLOW READ ACCESS) without specifying USE 
<tablespace> option, the shadow index will be created in the 
same tablespace as the index object, and if an escalation of an 
internal extent movement lock is needed at the same time, the 
Load might fail in acquiring the extent movement lock followed 
by an "Invalid pool ID" error, then subsequent commit operation 
might ultimately mark the database bad. 
 
Additionally, subsequent crash recovery might fail with the same 
symptoms as what you saw from failed load previously so that 
the database cannot be recovered. 
 
The errors in db2diag.log are as below. 
 
2012-07-29-15.33.25.412726+480 I8038741E568        LEVEL: Error 
PID     : 12348                TID  : 139821397829968PROC : 
db2sysc 24 
INSTANCE: db2inst1             NODE : 024          DB   : SAMPLE 
APPHDL  : 998-10015            APPID: 
*N998.db2inst1.120729081747 
AUTHID  : JOB_ETL 
EDUID   : 32298                EDUNAME: db2lrid 24 
FUNCTION: DB2 UDB, database utilities, DIAG_ERROR, probe:0 
DATA #1 : String, 145 bytes 
LOADID: 206.2012-07-29-15.32.36.252376.998 (65530;36218) 
Error requiring extent movement lock. , 1, (nil), Detected in 
file:sqlulinx.C, Line:1677 
 
<strip> 
 
2012-07-29-15.34.00.649555+480 I8083036E498        LEVEL: Error 
PID     : 12348                TID  : 139827399878992PROC : 
db2sysc 24 
INSTANCE: db2inst1             NODE : 024          DB   : SAMPLE 
 
APPHDL  : 998-10015            APPID: 
*N998.db2inst1.120729081747 
AUTHID  : JOB_ETL< 
EDUID   : 161                  EDUNAME: db2agnta (SAMPLE) 24 
FUNCTION: DB2 UDB, database utilities, DIAG_ERROR, probe:0 
MESSAGE : Check pool , -2029911946, 0x10040, Detected in 
file:sqluvppo.C,< 
          Line:2895 
 
2012-07-29-15.34.00.649806+480 I8083535E459        LEVEL: 
Warning 
PID     : 12348                TID  : 139827399878992PROC : 
db2sysc 24 
INSTANCE: db2inst1             NODE : 024          DB   : SAMPLE 
 
APPHDL  : 998-10015            APPID: 
*N998.db2inst1.120729081747 
AUTHID  : JOB_ETL< 
EDUID   : 161                  EDUNAME: db2agnta (SAMPLE) 24 
FUNCTION: DB2 UDB, database utilities, DIAG_NOTE, probe:0 
DATA #1 : String, 27 bytes 
 
TS info 0, 139827399872756 
 
<strip> 
 
2012-07-29-15.34.00.650140+480 I8084519E498        LEVEL: Severe 
 
PID     : 12348                TID  : 139827399878992PROC : 
db2sysc 24 
INSTANCE: db2inst1             NODE : 024          DB   : Sample 
 
APPHDL  : 998-10015            APPID: 
*N998.db2inst1.120729081747 
AUTHID  : JOB_ETL 
EDUID   : 161                  EDUNAME: db2agnta (SAMPLE) 24 
FUNCTION: DB2 UDB, database utilities, 
sqlu_process_pending_operation, probe:1904 
RETCODE : ZRC=0x87020076=-2029911946=SQLB_INV_POOLID "Invalid 
pool ID" 
 
<strip> 
 
2012-07-29-15.34.01.133561+480 E8130570E465        LEVEL: Severe 
 
PID     : 12348                TID  : 139827399878992PROC : 
db2sysc 24 
INSTANCE: db2inst1             NODE : 024          DB   : SAMPLE 
 
APPHDL  : 998-10015            APPID: 
*N998.db2inst1.120729081747 
AUTHID  : JOB_ETL< 
EDUID   : 161                  EDUNAME: db2agnta (SAMPLE) 24 
FUNCTION: DB2 UDB, base sys utilities, 
sqeLocalDatabase::MarkDBBad, probe:10 
MESSAGE : ADM7518C  "SAMPLE   " marked bad. 
 
 
Subsequent crash recovery may fail with following error message 
in db2diag.log. 
 
 
2012-07-29-19.20.16.799120+480 E3337E457           LEVEL: 
Warning 
PID     : 32185                TID  : 139900972165456PROC : 
db2sysc 24 
INSTANCE: db2inst1             NODE : 024          DB   : SAMPLE 
APPHDL  : 24-64                APPID: *N24.db2inst1.120729112008 
AUTHID  : DB2INST1 
EDUID   : 38                   EDUNAME: db2agent (SAMPLE) 24 
FUNCTION: DB2 UDB, recovery manager, sqlpresr, probe:410 
MESSAGE : ADM1530E  Crash recovery has been initiated. 
 
<strip> 
 
2012-07-29-19.20.18.424328+480 I7474E542           LEVEL: Severe 
PID     : 32185                TID  : 139900863113552PROC : 
db2sysc 24 
INSTANCE: db2inst1             NODE : 024          DB   : SAMPLE 
APPHDL  : 24-64                APPID: *N24.db2inst1.120729112008 
AUTHID  : DB2INST1 
EDUID   : 68                   EDUNAME: db2redom (SAMPLE) 24 
FUNCTION: DB2 UDB, data management, sqldLoadTCBObjDesc, 
probe:1744 
RETCODE : ZRC=0x87020036=-2029912010=SQLB_BADHDR "Bad Page 
Header" 
          DIA8547C An error occurred in a database page header. 
 
<strip> 
 
2012-07-29-19.20.18.425125+480 I10137E743          LEVEL: Severe 
PID     : 32185                TID  : 139900863113552PROC : 
db2sysc 24 
INSTANCE: db2inst1             NODE : 024          DB   : SAMPLE 
APPHDL  : 24-64                APPID: *N24.db2inst1.120729112008 
AUTHID  : DB2INST1 
EDUID   : 68                   EDUNAME: db2redom (SAMPLE) 24 
FUNCTION: DB2 UDB, data management, sqldFixTCBObj, probe:6459 
MESSAGE : ZRC=0x87020036=-2029912010=SQLB_BADHDR "Bad Page 
Header" 
          DIA8547C An error occurred in a database page header. 
DATA #1 : Object control block, PD_TYPE_SQLB_OBJECT, 12 bytes 
Obj: {pool:39;obj:29465;type:1} Parent={39;29465} 
DATA #2 : tcbFixFlags, PD_TYPE_SQLD_TCB_FIXFLAGS, 4 bytes 
0x00000020 
   - TCB_EXPECT_NOTAVAIL 
 
<strip> 
 
2012-07-29-19.20.18.427185+480 I13813E480          LEVEL: 
Warning 
PID     : 32185                TID  : 139900863113552PROC : 
db2sysc 24 
INSTANCE: db2inst1             NODE : 024          DB   : SAMPLE 
APPHDL  : 24-64                APPID: *N24.db2inst1.120729112008 
AUTHID  : DB2INST1 
EDUID   : 68                   EDUNAME: db2redom (SAMPLE) 24 
FUNCTION: DB2 UDB, database utilities, DIAG_NOTE, probe:0 
DATA #1 : String, 49 bytes 
 
Following tablespace does not exist. TS ID: 0, 0 
 
<strip> 
 
2012-07-29-19.20.23.464184+480 E35002E955          LEVEL: 
Critical 
PID     : 32185                TID  : 139900972165456PROC : 
db2sysc 24 
INSTANCE: db2inst1             NODE : 024          DB   : SAMPLE 
APPHDL  : 24-64                APPID: *N24.db2inst1.120729112008 
AUTHID  : DB2INST1 
EDUID   : 38                   EDUNAME: db2agent (SAMPLE) 24 
FUNCTION: DB2 UDB, base sys utilities, 
sqeLocalDatabase::MarkDBBad, probe:10 
 
Note: To skip crash recovery on the damaged tablespace, please 
contact DB2 support.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* For online load (ALLOW READ ACCESS) without specifying USE   * 
* <tablespace> option, the shadow index will be created in the * 
* same tablespace as the index object, and if an escalation of * 
* an                                                           * 
* internal extent movement lock is needed at the same time,    * 
* the                                                          * 
* Load might fail in acquiring the extent movement lock        * 
* followed                                                     * 
* by an "Invalid pool ID" error, then subsequent commit        * 
* operation                                                    * 
* might ultimately mark the database bad.                      * 
*                                                              * 
* Additionally, subsequent crash recovery might fail with the  * 
* same                                                         * 
* symptoms as what you saw from failed load previously so that * 
* the database cannot be recovered.                            * 
*                                                              * 
* The errors in db2diag.log are as below.                      * 
*                                                              * 
* 2012-07-29-15.33.25.412726+480 I8038741E568        LEVEL:    * 
* Error                                                        * 
* PID     : 12348                TID  : 139821397829968PROC :  * 
* db2sysc 24                                                   * 
* INSTANCE: db2inst1             NODE : 024          DB   :    * 
* SAMPLE                                                       * 
* APPHDL  : 998-10015            APPID:                        * 
* *N998.db2inst1.120729081747                                  * 
* AUTHID  : JOB_ETL                                            * 
* EDUID   : 32298                EDUNAME: db2lrid 24           * 
* FUNCTION: DB2 UDB, database utilities, DIAG_ERROR, probe:0   * 
* DATA #1 : String, 145 bytes                                  * 
* LOADID: 206.2012-07-29-15.32.36.252376.998 (65530;36218)     * 
* Error requiring extent movement lock. , 1, (nil), Detected   * 
* in                                                           * 
* file:sqlulinx.C, Line:1677                                   * 
*                                                              * 
* <strip>                                                      * 
*                                                              * 
* 2012-07-29-15.34.00.649555+480 I8083036E498        LEVEL:    * 
* Error                                                        * 
* PID     : 12348                TID  : 139827399878992PROC :  * 
* db2sysc 24                                                   * 
* INSTANCE: db2inst1             NODE : 024          DB   :    * 
* SAMPLE                                                       * 
*                                                              * 
* APPHDL  : 998-10015            APPID:                        * 
* *N998.db2inst1.120729081747                                  * 
* AUTHID  : JOB_ETL<                                           * 
* EDUID   : 161                  EDUNAME: db2agnta (SAMPLE) 24 * 
* FUNCTION: DB2 UDB, database utilities, DIAG_ERROR, probe:0   * 
* MESSAGE : Check pool , -2029911946, 0x10040, Detected in     * 
* file:sqluvppo.C,<                                            * 
*           Line:2895                                          * 
*                                                              * 
* 2012-07-29-15.34.00.649806+480 I8083535E459        LEVEL:    * 
* Warning                                                      * 
* PID     : 12348                TID  : 139827399878992PROC :  * 
* db2sysc 24                                                   * 
* INSTANCE: db2inst1             NODE : 024          DB   :    * 
* SAMPLE                                                       * 
*                                                              * 
* APPHDL  : 998-10015            APPID:                        * 
* *N998.db2inst1.120729081747                                  * 
* AUTHID  : JOB_ETL<                                           * 
* EDUID   : 161                  EDUNAME: db2agnta (SAMPLE) 24 * 
* FUNCTION: DB2 UDB, database utilities, DIAG_NOTE, probe:0    * 
* DATA #1 : String, 27 bytes                                   * 
*                                                              * 
* TS info 0, 139827399872756                                   * 
*                                                              * 
* <strip>                                                      * 
*                                                              * 
* 2012-07-29-15.34.00.650140+480 I8084519E498        LEVEL:    * 
* Severe                                                       * 
*                                                              * 
* PID     : 12348                TID  : 139827399878992PROC :  * 
* db2sysc 24                                                   * 
* INSTANCE: db2inst1             NODE : 024          DB   :    * 
* Sample                                                       * 
*                                                              * 
* APPHDL  : 998-10015            APPID:                        * 
* *N998.db2inst1.120729081747                                  * 
* AUTHID  : JOB_ETL                                            * 
* EDUID   : 161                  EDUNAME: db2agnta (SAMPLE) 24 * 
* FUNCTION: DB2 UDB, database utilities,                       * 
* sqlu_process_pending_operation, probe:1904                   * 
* RETCODE : ZRC=0x87020076=-2029911946=SQLB_INV_POOLID         * 
* "Invalid                                                     * 
* pool ID"                                                     * 
*                                                              * 
* <strip>                                                      * 
*                                                              * 
* 2012-07-29-15.34.01.133561+480 E8130570E465        LEVEL:    * 
* Severe                                                       * 
*                                                              * 
* PID     : 12348                TID  : 139827399878992PROC :  * 
* db2sysc 24                                                   * 
* INSTANCE: db2inst1             NODE : 024          DB   :    * 
* SAMPLE                                                       * 
*                                                              * 
* APPHDL  : 998-10015            APPID:                        * 
* *N998.db2inst1.120729081747                                  * 
* AUTHID  : JOB_ETL<                                           * 
* EDUID   : 161                  EDUNAME: db2agnta (SAMPLE) 24 * 
* FUNCTION: DB2 UDB, base sys utilities,                       * 
* sqeLocalDatabase::MarkDBBad, probe:10                        * 
* MESSAGE : ADM7518C  "SAMPLE   " marked bad.                  * 
*                                                              * 
*                                                              * 
* Subsequent crash recovery may fail with following error      * 
* message                                                      * 
* in db2diag.log.                                              * 
*                                                              * 
*                                                              * 
* 2012-07-29-19.20.16.799120+480 E3337E457           LEVEL:    * 
* Warning                                                      * 
* PID     : 32185                TID  : 139900972165456PROC :  * 
* db2sysc 24                                                   * 
* INSTANCE: db2inst1             NODE : 024          DB   :    * 
* SAMPLE                                                       * 
* APPHDL  : 24-64                APPID:                        * 
* *N24.db2inst1.120729112008                                   * 
* AUTHID  : DB2INST1                                           * 
* EDUID   : 38                   EDUNAME: db2agent (SAMPLE) 24 * 
* FUNCTION: DB2 UDB, recovery manager, sqlpresr, probe:410     * 
* MESSAGE : ADM1530E  Crash recovery has been initiated.       * 
*                                                              * 
* <strip>                                                      * 
*                                                              * 
* 2012-07-29-19.20.18.424328+480 I7474E542           LEVEL:    * 
* Severe                                                       * 
* PID     : 32185                TID  : 139900863113552PROC :  * 
* db2sysc 24                                                   * 
* INSTANCE: db2inst1             NODE : 024          DB   :    * 
* SAMPLE                                                       * 
* APPHDL  : 24-64                APPID:                        * 
* *N24.db2inst1.120729112008                                   * 
* AUTHID  : DB2INST1                                           * 
* EDUID   : 68                   EDUNAME: db2redom (SAMPLE) 24 * 
* FUNCTION: DB2 UDB, data management, sqldLoadTCBObjDesc,      * 
* probe:1744                                                   * 
* RETCODE : ZRC=0x87020036=-2029912010=SQLB_BADHDR "Bad Page   * 
* Header"                                                      * 
*           DIA8547C An error occurred in a database page      * 
* header.                                                      * 
*                                                              * 
* <strip>                                                      * 
*                                                              * 
* 2012-07-29-19.20.18.425125+480 I10137E743          LEVEL:    * 
* Severe                                                       * 
* PID     : 32185                TID  : 139900863113552PROC :  * 
* db2sysc 24                                                   * 
* INSTANCE: db2inst1             NODE : 024          DB   :    * 
* SAMPLE                                                       * 
* APPHDL  : 24-64                APPID:                        * 
* *N24.db2inst1.120729112008                                   * 
* AUTHID  : DB2INST1                                           * 
* EDUID   : 68                   EDUNAME: db2redom (SAMPLE) 24 * 
* FUNCTION: DB2 UDB, data management, sqldFixTCBObj,           * 
* probe:6459                                                   * 
* MESSAGE : ZRC=0x87020036=-2029912010=SQLB_BADHDR "Bad Page   * 
* Header"                                                      * 
*           DIA8547C An error occurred in a database page      * 
* header.                                                      * 
* DATA #1 : Object control block, PD_TYPE_SQLB_OBJECT, 12      * 
* bytes                                                        * 
* Obj: {pool:39;obj:29465;type:1} Parent={39;29465}            * 
* DATA #2 : tcbFixFlags, PD_TYPE_SQLD_TCB_FIXFLAGS, 4 bytes    * 
* 0x00000020                                                   * 
*       - TCB_EXPECT_NOTAVAIL                                  * 
*                                                              * 
* <strip>                                                      * 
*                                                              * 
* 2012-07-29-19.20.18.427185+480 I13813E480          LEVEL:    * 
* Warning                                                      * 
* PID     : 32185                TID  : 139900863113552PROC :  * 
* db2sysc 24                                                   * 
* INSTANCE: db2inst1             NODE : 024          DB   :    * 
* SAMPLE                                                       * 
* APPHDL  : 24-64                APPID:                        * 
* *N24.db2inst1.120729112008                                   * 
* AUTHID  : DB2INST1                                           * 
* EDUID   : 68                   EDUNAME: db2redom (SAMPLE) 24 * 
* FUNCTION: DB2 UDB, database utilities, DIAG_NOTE, probe:0    * 
* DATA #1 : String, 49 bytes                                   * 
*                                                              * 
* Following tablespace does not exist. TS ID: 0, 0             * 
*                                                              * 
* <strip>                                                      * 
*                                                              * 
* 2012-07-29-19.20.23.464184+480 E35002E955          LEVEL:    * 
* Critical                                                     * 
* PID     : 32185                TID  : 139900972165456PROC :  * 
* db2sysc 24                                                   * 
* INSTANCE: db2inst1             NODE : 024          DB   :    * 
* SAMPLE                                                       * 
* APPHDL  : 24-64                APPID:                        * 
* *N24.db2inst1.120729112008                                   * 
* AUTHID  : DB2INST1                                           * 
* EDUID   : 38                   EDUNAME: db2agent (SAMPLE) 24 * 
* FUNCTION: DB2 UDB, base sys utilities,                       * 
* sqeLocalDatabase::MarkDBBad, probe:10                        * 
*                                                              * 
* Note: To skip crash recovery on the damaged tablespace,      * 
* please                                                       * 
* contact DB2 support.                                         * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 V97FP8 or higher version                      * 
****************************************************************
Local Fix:
Please specify a system temporary table space explicitly for the 
online Load.
available fix packs:
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 APAR was fixed on DB2 V97FP8 or higher version
Workaround
Please specify a system temporary table space explicitly for the 
online Load.
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
30.08.2012
15.04.2013
15.04.2013
Problem solved at the following versions (IBM BugInfos)
9.7.FP8
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.8 FixList