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

SELECT FROM SYSIBMADM.ADMINTABINFO CRASHES DATABASE WITH BFIX DETECTED AN
ERROR

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
If we have a table that has a very big size, we might get into a 
situation where a query on SYSIBMADM.ADMINTABINFO will crash the 
database. 
 
SELECT SUBSTR(TABSCHEMA,1,18) TABSCHEMA, 
SUBSTR(TABNAME,1,30) TABNAME, 
SUM(DATA_OBJECT_P_SIZE) DATA_OBJECT_P_SIZE, 
SUM(INDEX_OBJECT_P_SIZE) INDEX_OBJECT_P_SIZE, 
SUM(LONG_OBJECT_P_SIZE) LONG_OBJECT_P_SIZE, 
SUM(LOB_OBJECT_P_SIZE) LOB_OBJECT_P_SIZE, 
SUM(XML_OBJECT_P_SIZE) XML_OBJECT_P_SIZE 
FROM SYSIBMADM.ADMINTABINFO 
WHERE TABNAME LIKE 'TEST%' 
GROUP BY TABSCHEMA, TABNAME 
order by 3 desc, 4 desc 
; 
 
The db2diag.log will report the following messages: 
 
2010-03-16-12.07.40.909000-240 I46298553F4655     LEVEL: Severe 
PID     : 8172                 TID  : 1444        PROC : 
db2syscs.exe 
INSTANCE: DB2                  NODE : 000         DB   : TEST 
APPHDL  : 0-23826              APPID: *LOCAL.DB2.100316155850 
AUTHID  : DB2ADMIN 
EDUID   : 1444                 EDUNAME: db2agent (TEST) 0 
FUNCTION: DB2 UDB, Common Trace API, sqlbfix, probe:104 
DATA #1 : String, 45 bytes 
bfix detected an error - Current Descriptor = 
DATA #2 : Buffer page descriptor, PD_TYPE_SQLB_BPD, 160 bytes 
  Pagekey: {pool:27;obj:4;type:64} PPNum:3972 
  objectPageNum:                      5971 
 
 
Note when hitting this issue, there will always be the number 
3972 and 5971 as shown above. This is not a table corruption as 
it could be interpreted from the db2diag.log messages, but an 
error on the calculations when transversing the EMP (extent Map 
Pages) for the table. 
 
The stack of the crash will show the following entries: 
 
sqloDumpEDU 
sqle_panic 
sqlb_panic 
sqlbufix 
sqlbNumExtentsMappedBySingleIndirect 
sqlbNumExtentsMappedByDoubleIndirect 
sqlbGetExtentCount 
sqlbDMSGetObjActualSize 
sqlbGetObjActualSize 
sqldGetTableData 
sqlrlAdminGetTabInfo 
sqlerTrustedRtnCallbackRouter 
admin_get_tab_info_v97 
 
This problem only occurs when doing the following 
Select DATA_OBJECT_P_SIZE / INDEX_OBJECT_P_SIZE / 
LONG_OBJECT_P_SIZE / LOB_OBJECT_P_SIZE / XML_OBJECT_P_SIZE from 
sysibmadm.admintabinfo on a table that is very big. 
 
We might also see a crash when dropping such table, due to the 
purging transversing the EMP pages to calculate the physical 
size of the table.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* If we have a table that has a very big size, we might get    * 
* into a                                                       * 
* situation where a query on SYSIBMADM.ADMINTABINFO will crash * 
* the                                                          * 
* database.                                                    * 
*                                                              * 
*                                                              * 
*                                                              * 
* SELECT SUBSTR(TABSCHEMA,1,18) TABSCHEMA,                     * 
*                                                              * 
* SUBSTR(TABNAME,1,30) TABNAME,                                * 
*                                                              * 
* SUM(DATA_OBJECT_P_SIZE) DATA_OBJECT_P_SIZE,                  * 
*                                                              * 
* SUM(INDEX_OBJECT_P_SIZE) INDEX_OBJECT_P_SIZE,                * 
*                                                              * 
* SUM(LONG_OBJECT_P_SIZE) LONG_OBJECT_P_SIZE,                  * 
*                                                              * 
* SUM(LOB_OBJECT_P_SIZE) LOB_OBJECT_P_SIZE,                    * 
*                                                              * 
* SUM(XML_OBJECT_P_SIZE) XML_OBJECT_P_SIZE                     * 
*                                                              * 
* FROM SYSIBMADM.ADMINTABINFO                                  * 
*                                                              * 
* WHERE TABNAME LIKE 'TEST%'                                   * 
*                                                              * 
* GROUP BY TABSCHEMA, TABNAME                                  * 
*                                                              * 
* order by 3 desc, 4 desc                                      * 
*                                                              * 
* ;                                                            * 
*                                                              * 
*                                                              * 
*                                                              * 
* The db2diag.log will report the following messages:          * 
*                                                              * 
*                                                              * 
*                                                              * 
* 2010-03-16-12.07.40.909000-240 I46298553F4655    LEVEL:      * 
* Severe                                                       * 
* PID    : 8172                TID  : 1444        PROC :       * 
*                                                              * 
* db2syscs.exe                                                 * 
*                                                              * 
* INSTANCE: DB2                  NODE : 000        DB  : TEST  * 
* APPHDL  : 0-23826              APPID:                        * 
* *LOCAL.DB2.100316155850                                      * 
* AUTHID  : DB2ADMIN                                           * 
*                                                              * 
* EDUID  : 1444                EDUNAME: db2agent (TEST) 0      * 
* FUNCTION: DB2 UDB, Common Trace API, sqlbfix, probe:104      * 
*                                                              * 
* DATA #1 : String, 45 bytes                                   * 
*                                                              * 
* bfix detected an error - Current Descriptor =                * 
*                                                              * 
* DATA #2 : Buffer page descriptor, PD_TYPE_SQLB_BPD, 160      * 
* bytes                                                        * 
*   Pagekey: {pool:27;obj:4;type:64} PPNum:3972                * 
*                                                              * 
*   objectPageNum:                      5971                   * 
*                                                              * 
*                                                              * 
*                                                              * 
*                                                              * 
*                                                              * 
* Note when hitting this issue, there will always be the       * 
* number                                                       * 
* 3972 and 5971 as shown above. This is not a table corruption * 
* as                                                           * 
* it could be interpreted from the db2diag.log messages, but   * 
* an                                                           * 
* error on the calculations when transversing the EMP (extent  * 
* Map                                                          * 
* Pages) for the table.                                        * 
*                                                              * 
*                                                              * 
*                                                              * 
* The stack of the crash will show the following entries:      * 
*                                                              * 
*                                                              * 
*                                                              * 
* sqloDumpEDU                                                  * 
*                                                              * 
* sqle_panic                                                   * 
*                                                              * 
* sqlb_panic                                                   * 
*                                                              * 
* sqlbufix                                                     * 
*                                                              * 
* sqlbNumExtentsMappedBySingleIndirect                         * 
*                                                              * 
* sqlbNumExtentsMappedByDoubleIndirect                         * 
*                                                              * 
* sqlbGetExtentCount                                           * 
*                                                              * 
* sqlbDMSGetObjActualSize                                      * 
*                                                              * 
* sqlbGetObjActualSize                                         * 
*                                                              * 
* sqldGetTableData                                             * 
*                                                              * 
* sqlrlAdminGetTabInfo                                         * 
*                                                              * 
* sqlerTrustedRtnCallbackRouter                                * 
*                                                              * 
* admin_get_tab_info_v97                                       * 
*                                                              * 
*                                                              * 
*                                                              * 
* This problem only occurs when doing the following            * 
*                                                              * 
* Select DATA_OBJECT_P_SIZE / INDEX_OBJECT_P_SIZE /            * 
*                                                              * 
* LONG_OBJECT_P_SIZE / LOB_OBJECT_P_SIZE / XML_OBJECT_P_SIZE   * 
* from                                                         * 
* sysibmadm.admintabinfo on a table that is very big.          * 
*                                                              * 
*                                                              * 
*                                                              * 
* We might also see a crash when dropping such table, due to   * 
* the                                                          * 
* purging transversing the EMP pages to calculate the physical * 
*                                                              * 
* size of the table.                                           * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 9.7 and Fixpack 3                     * 
****************************************************************
Local Fix:
Do not run a query on sysibmadm.admintabinfo if there are very 
big tables on the system. 
Avoid dropping very big tables.
available fix packs:
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
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 DB2 version 9.7 and Fixpack 3
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC69320 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
21.05.2010
29.06.2010
29.06.2010
Problem solved at the following versions (IBM BugInfos)
9.7.
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.3 FixList
9.7.0.3 FixList