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

DB2 INSTANCE CRASHES WITH PACKET DESCRIPTOR CORRUPTION ON A CATALOG TABLE.

product:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problem description:
Problem Description : 
 
This particular trap will occur anytime we're getting the packed 
descriptor in the engine for a catalog table. 
For regular tables, if they have this corruption, you will 
simply get the -901. 
DB2 instance crashes with Packet Descriptor corruption on a 
catalog table with the entry such as : 
 
---------------------------------------------------------------- 
 
2009-11-02-09.13.10.632373+060 I16743721A874      LEVEL: Severe 
PID     : 24521                TID  : 2199383959888PROC : 
db2sysc 0 
INSTANCE: db2iapx              NODE : 000         DB   : APXDB 
APPHDL  : 0-15                 APPID: 
*LOCAL.db2iapx.091102080625 
AUTHID  : DB2IAPX 
EDUID   : 17                   EDUNAME: db2agent (APXDB) 0 
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: 50 
sqlerrmc: Corrupt PD->length in table "SYSIBM  "."SYSCHECKS" 
sqlerrp : SQLRL2EF 
sqlerrd : (1) 0x00000000      (2) 0x00000000      (3) 0x00000000 
          (4) 0x00000000      (5) 0xFFFFFF38      (6) 0x00000000 
sqlwarn : (1)      (2)      (3)      (4)        (5)       (6) 
          (7)      (8)      (9)      (10)        (11) 
sqlstate: 
---------------------------------------------------------------- 
-------- 
with the stack trace as : 
 
0000020001E8F01E sqloCrashOnCriticalMemoryValidationFailure + 
0x002e 
 (/home/db2iapx/sqllib/lib64/libdb2e.so.1) 
0000020001E915E8 sqlofmblkEx + 0x0104 
 (/home/db2iapx/sqllib/lib64/libdb2e.so.1) 
000002000270DA3C 
_Z8sqlrlgtiP8sqlrr_cbPhiS1_iPtS2_S1_S2_PS1_iS3_iS3_PjS3_PsS3_S5_ 
i + 
 
 
The instance crash occurs because of free memory block failure. 
Instead of having graceful error handling by getting a -901, we 
get a -901 dumped in the db2diag.log, followed by a trap. 
 
It just happens to be one of the callers of the sqlrlgti 
function amongst others e.g. SYSIBM.SYSCHECKS
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All user prior to DB2 V95 FP6                                * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* This particular trap will occur anytime we're getting the    * 
* packed                                                       * 
* descriptor in the engine for a catalog table.                * 
*                                                              * 
* For regular tables, if they have this corruption, you will   * 
*                                                              * 
* simply get the -901.                                         * 
*                                                              * 
* DB2 instance crashes with Packet Descriptor corruption on a  * 
*                                                              * 
* catalog table with the entry such as :                       * 
*                                                              * 
*                                                              * 
*                                                              * 
* -------------------------------------------------------------- 
*                                                              * 
*                                                              * 
*                                                              * 
* 2009-11-02-09.13.10.632373+060 I16743721A874      LEVEL:     * 
* Severe                                                       * 
* PID     : 24521                TID  : 2199383959888PROC :    * 
*                                                              * 
* db2sysc 0                                                    * 
*                                                              * 
* INSTANCE: db2iapx              NODE : 000         DB   :     * 
* APXDB                                                        * 
* APPHDL  : 0-15                 APPID:                        * 
*                                                              * 
* *LOCAL.db2iapx.091102080625                                  * 
*                                                              * 
* AUTHID  : DB2IAPX                                            * 
*                                                              * 
* EDUID   : 17                   EDUNAME: db2agent (APXDB) 0   * 
*                                                              * 
* 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: * 
* 50                                                           * 
* sqlerrmc: Corrupt PD->length in table "SYSIBM  "."SYSCHECKS" * 
*                                                              * 
* sqlerrp : SQLRL2EF                                           * 
*                                                              * 
* sqlerrd : (1) 0x00000000      (2) 0x00000000      (3)        * 
* 0x00000000                                                   * 
*           (4) 0x00000000      (5) 0xFFFFFF38      (6)        * 
* 0x00000000                                                   * 
* sqlwarn : (1)      (2)      (3)      (4)        (5)          * 
* (6)                                                          * 
*           (7)      (8)      (9)      (10)        (11)        * 
*                                                              * 
* sqlstate:                                                    * 
*                                                              * 
* -------------------------------------------------------------- 
*                                                              * 
* --------                                                     * 
*                                                              * 
* with the stack trace as :                                    * 
*                                                              * 
*                                                              * 
*                                                              * 
* 0000020001E8F01E sqloCrashOnCriticalMemoryValidationFailure  * 
* +                                                            * 
* 0x002e                                                       * 
*                                                              * 
*  (/home/db2iapx/sqllib/lib64/libdb2e.so.1)                   * 
*                                                              * 
* 0000020001E915E8 sqlofmblkEx + 0x0104                        * 
*                                                              * 
*  (/home/db2iapx/sqllib/lib64/libdb2e.so.1)                   * 
*                                                              * 
* 000002000270DA3C                                             * 
*                                                              * 
* _Z8sqlrlgtiP8sqlrr_cbPhiS1_iPtS2_S1_S2_PS1_iS3_iS3_PjS3_PsS3_S 
*                                                              * 
* i +                                                          * 
*                                                              * 
*                                                              * 
*                                                              * 
*                                                              * 
*                                                              * 
* The instance crash occurs because of free memory block       * 
* failure.                                                     * 
* Instead of having graceful error handling by getting a -901, * 
* we                                                           * 
* get a -901 dumped in the db2diag.log, followed by a trap.    * 
*                                                              * 
*                                                              * 
*                                                              * 
* It just happens to be one of the callers of the sqlrlgti     * 
*                                                              * 
* function amongst others e.g. SYSIBM.SYSCHECKS                * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Local Fix:                                                   * 
* Avoid accessing that catalog table in any way. Even avoiding * 
* DDL   if possible. e.g. opearions like executing runstats.   * 
*                                                              * 
*                                                              * 
* Permanent Fix :                                              * 
* Please upgrade to DB2 V95 FP6 and above                      * 
**************************************************************** 
DB2 INSTANCE CRASHES WHEN PACKED DESCRIPTOR CORRUPTION IS 
DETECTED ON A CATALOG TABLE
Local Fix:
Avoid accessing that catalog table in any way. Even avoiding DDL 
if possible. e.g. opearions like executing runstats.
available fix packs:
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows

Solution
Fixed in V95 FP6
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC65721 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
19.11.2009
10.05.2011
10.05.2011
Problem solved at the following versions (IBM BugInfos)
9.5.FP6
Problem solved according to the fixlist(s) of the following version(s)