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

MEMORY OVERWRITE WHEN USING UTL_FILE or DBMS_OUTPUT.ENABLE with buffer size
bigger then 32K.

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
Memory overwrite can happen if 
1) application is using DBMS_OUTPUT.ENABLE with buffer size 
bigger then 32K and data is written into the buffer which has no 
null terminators for longer then 32K bytes. 
 
2) application is using UTL_FILE.FCLOSE. 
 
The crash will have a message similar to the following in the 
db2diag.log: 
 2012-08-30-00.17.48.856591-240 E3800797A1291      LEVEL: Severe 
PID     : 22216748             TID  : 30431       PROC : db2sysc 
0 
INSTANCE: dbinst1             NODE : 000         DB   : SAMPLE 
APPHDL  : 0-34250              APPID: *LOCAL.DB2.120830052553 
AUTHID  : DB2INST1 
EDUID   : 30431                EDUNAME: db2agent (SAMPLE) 0 
FUNCTION: DB2 UDB, SQO Memory Management, 
sqloDiagnoseFreeBlockFailure, 
probe:999 
MESSAGE : Memory validation failure, diagnostic file dumped. 
DATA #1 : String, 28 bytes 
Corrupt pool free tree node. 
DATA #2 : File name, 34 bytes 
22216748.30431.mem_diagnostics.txt 
 
CALLSTCK: 
  [0] 0x09000000136BC624 pdLog + 0xD0 
  [1] 0x0900000012A1B5E0 
diagnoseMemoryCorruptionAndCrash__13SQLO_MEM_POOLFUlCPCc + 0x280 
  [2] 0x0900000012A1B288 
diagnoseMemoryCorruptionAndCrash__13SQLO_MEM_POOLFUlCPCc@glue7DC 
+ 0x78 
  [3] 0x090000001354F3E0 
.MemTreePut.fdpr.clone.499__13SQLO_MEM_POOLFP8SMemNodeUlP17SqloC 
hunkSubgroup + 0xC 
  [4] 0x09000000135563E8 sqlofmblkEx + 0x278 
  [5] 0x0900000015682AF4 sqlerTrustedRtnCallbackFmblk__FUiPPv 
+0x110 
  [6] 0x090000001566F690 sqlerTrustedRtnCallbackRouter__FUiPPv 
+0xC4 
  [7] 0x090000001B1952C8 freeMemory__FPv + 0x48 
  [8] 0x090000001B195414 poolFree__FPv@AF16_10 + 0x14 
  [9] 0x090000001B1965EC removeEntry__10hashBucketFPCvUl + 0x8C 
 
In the trap file produced, you will see the following: 
 -------Frame------ ------Function + Offset------ 
0x09000000132DED34 sqloCrashOnCriticalMemoryValidationFailure 
+0x30 
0x0900000012A1B5E8 
diagnoseMemoryCorruptionAndCrash__13SQLO_MEM_POOLFUlCPCc + 0x288 
0x0900000012A1B288 
diagnoseMemoryCorruptionAndCrash__13SQLO_MEM_POOLFUlCPCc@glue7DC 
+ 0x78 
0x090000001354F3E0 
.MemTreePut.fdpr.clone.499__13SQLO_MEM_POOLFP8SMemNodeUlP17SqloC 
hunkSubgroup + 0xC 
0x09000000135563E8 sqlofmblkEx + 0x278 
0x0900000015682AF4 sqlerTrustedRtnCallbackFmblk__FUiPPv + 0x110 
0x090000001566F690 sqlerTrustedRtnCallbackRouter__FUiPPv + 0xC4 
0x090000001B1952C8 freeMemory__FPv + 0x48 
0x090000001B195414 poolFree__FPv@AF16_10 + 0x14 
0x090000001B1965EC removeEntry__10hashBucketFPCvUl + 0x8C 
0x090000001B196460 remove__9hashTableFPCvUl + 0x20 
0x090000001B1B1604 sqleml_removeFile__FP18sqleml_sessionDatai 
+0x44 
0x090000001B1B1538 sqleml_utl_file_fclose + 0x1B8 
0x09000000136AF41C sqloInvokeFnArgs + 0xD0 
0x0900000013F38964 
sqlriInvokerTrusted__FP10sqlri_ufobP21sqlriRoutineErrorIntf +0xC 
0x09000000136ACE1C sqlriInvokeInvoker__FP10sqlri_ufobb + 0xB78 
0x090000001372A474 sqlricall__FP8sqlrr_cb + 0x188
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users of UTL_FILE or DBMS_OUTPUT.ENABLE                      * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Memory overwrite can happen if                               * 
* 1) application is using DBMS_OUTPUT.ENABLE with buffer size  * 
* bigger then 32K and data is written into the buffer which    * 
* has no                                                       * 
* null terminators for longer then 32K bytes.                  * 
*                                                              * 
* 2) application is using UTL_FILE.FCLOSE.                     * 
*                                                              * 
* The crash will have a message similar to the following in    * 
* the                                                          * 
* db2diag.log:                                                 * 
*  2012-08-30-00.17.48.856591-240 E3800797A1291      LEVEL:    * 
* Severe                                                       * 
* PID     : 22216748             TID  : 30431       PROC :     * 
* db2sysc                                                      * 
* 0                                                            * 
* INSTANCE: dbinst1             NODE : 000         DB   :      * 
* SAMPLE                                                       * 
* APPHDL  : 0-34250              APPID:                        * 
* *LOCAL.DB2.120830052553                                      * 
* AUTHID  : DB2INST1                                           * 
* EDUID   : 30431                EDUNAME: db2agent (SAMPLE) 0  * 
* FUNCTION: DB2 UDB, SQO Memory Management,                    * 
* sqloDiagnoseFreeBlockFailure,                                * 
* probe:999                                                    * 
* MESSAGE : Memory validation failure, diagnostic file dumped. * 
* DATA #1 : String, 28 bytes                                   * 
* Corrupt pool free tree node.                                 * 
* DATA #2 : File name, 34 bytes                                * 
* 22216748.30431.mem_diagnostics.txt                           * 
*                                                              * 
* CALLSTCK:                                                    * 
*   [0] 0x09000000136BC624 pdLog + 0xD0                        * 
*   [1] 0x0900000012A1B5E0                                     * 
* diagnoseMemoryCorruptionAndCrash__13SQLO_MEM_POOLFUlCPCc +   * 
* 0x280                                                        * 
*   [2] 0x0900000012A1B288                                     * 
* diagnoseMemoryCorruptionAndCrash__13SQLO_MEM_POOLFUlCPCc@glu * 
* e7DC                                                         * 
* + 0x78                                                       * 
*   [3] 0x090000001354F3E0                                     * 
* .MemTreePut.fdpr.clone.499__13SQLO_MEM_POOLFP8SMemNodeUlP17S * 
* qloC                                                         * 
* hunkSubgroup + 0xC                                           * 
*   [4] 0x09000000135563E8 sqlofmblkEx + 0x278                 * 
*   [5] 0x0900000015682AF4                                     * 
* sqlerTrustedRtnCallbackFmblk__FUiPPv                         * 
* +0x110                                                       * 
*   [6] 0x090000001566F690                                     * 
* sqlerTrustedRtnCallbackRouter__FUiPPv                        * 
* +0xC4                                                        * 
*   [7] 0x090000001B1952C8 freeMemory__FPv + 0x48              * 
*   [8] 0x090000001B195414 poolFree__FPv@AF16_10 + 0x14        * 
*   [9] 0x090000001B1965EC removeEntry__10hashBucketFPCvUl +   * 
* 0x8C                                                         * 
*                                                              * 
* In the trap file produced, you will see the following:       * 
*  -------Frame------ ------Function + Offset------            * 
* 0x09000000132DED34                                           * 
* sqloCrashOnCriticalMemoryValidationFailure                   * 
* +0x30                                                        * 
* 0x0900000012A1B5E8                                           * 
* diagnoseMemoryCorruptionAndCrash__13SQLO_MEM_POOLFUlCPCc +   * 
* 0x288                                                        * 
* 0x0900000012A1B288                                           * 
* diagnoseMemoryCorruptionAndCrash__13SQLO_MEM_POOLFUlCPCc@glu * 
* e7DC                                                         * 
* + 0x78                                                       * 
* 0x090000001354F3E0                                           * 
* .MemTreePut.fdpr.clone.499__13SQLO_MEM_POOLFP8SMemNodeUlP17S * 
* qloC                                                         * 
* hunkSubgroup + 0xC                                           * 
* 0x09000000135563E8 sqlofmblkEx + 0x278                       * 
* 0x0900000015682AF4 sqlerTrustedRtnCallbackFmblk__FUiPPv +    * 
* 0x110                                                        * 
* 0x090000001566F690 sqlerTrustedRtnCallbackRouter__FUiPPv +   * 
* 0xC4                                                         * 
* 0x090000001B1952C8 freeMemory__FPv + 0x48                    * 
* 0x090000001B195414 poolFree__FPv@AF16_10 + 0x14              * 
* 0x090000001B1965EC removeEntry__10hashBucketFPCvUl + 0x8C    * 
* 0x090000001B196460 remove__9hashTableFPCvUl + 0x20           * 
* 0x090000001B1B1604                                           * 
* sqleml_removeFile__FP18sqleml_sessionDatai                   * 
* +0x44                                                        * 
* 0x090000001B1B1538 sqleml_utl_file_fclose + 0x1B8            * 
* 0x09000000136AF41C sqloInvokeFnArgs + 0xD0                   * 
* 0x0900000013F38964                                           * 
* sqlriInvokerTrusted__FP10sqlri_ufobP21sqlriRoutineErrorIntf  * 
* +0xC                                                         * 
* 0x09000000136ACE1C sqlriInvokeInvoker__FP10sqlri_ufobb +     * 
* 0xB78                                                        * 
* 0x090000001372A474 sqlricall__FP8sqlrr_cb + 0x188            * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2  v9.7 FP8 or newer                            * 
****************************************************************
Local Fix:
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
Upgrade to DB2  v9.7 FP8 or newer
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC91743 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
13.12.2012
08.04.2013
08.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