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

STMM MIGHT INCORRECTLY CALCULATE DATABASE MEMORY TARGETS SIZE UNDER CERTAIN
CIRCUMSTANCES

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
STMM incorrectly calculates database memory targets size and an 
overflow happened due to the free memory target being greater 
than database configured memory set when there isn't enough free 
memory in the machine. 
 
STMM tries to leave a certain percentage of memory as free 
memory, called the free memory target. When the free memory 
target is bigger than a database memory set while there isn't 
enough free memory in the machine, STMM may "incorrectly" decide 
to shrink the database memory set below 0. This leads to an 
overflow of the target database memory set size and the target 
consumer size those are reported in STMM.log 
 
Additionally, the error message like "ZRC=0xFFFFEC49=-5047" will 
appear in db2diag.log whenever the free memory in the box runs 
out, The error will also disappear on its own when some free 
memory becomes available in the box. 
 
Here is an example db2diag.log entry : 
 
2010-08-23-01.22.46.494522+480 E47256126A631      LEVEL: Warning 
PID     : 303152               TID  : 35746       PROC : db2sysc 
0 
INSTANCE: DB2INST1             NODE : 000         DB   : SAMPLE 
APPHDL  : 1-60027              APPID: *N1.DB2.100822171046 
AUTHID  : DB2INST1 
EDUID   : 35746                EDUNAME: db2stmm (SAMPLE) 0 
FUNCTION: DB2 UDB, Self tuning memory manager, 
stmmCheckIfFreeMemoryIsEnoughForSizeIncr, probe:667 
MESSAGE : ZRC=0xFFFFEC49=-5047 
DATA #1 : String, 143 bytes 
There is not enough free memory for size increase. Free memory 
in pages: Physical memory = 0, Instance memory = 160917, 
Database memory = 33072 
 
Here is an example stmm.X.log entry: 
 
2010-08-23-01.22.46.493934+480 I8862389A929       LEVEL: Event 
PID     : 303152               TID  : 35746       PROC : db2sysc 
0 
INSTANCE: DB2INST1             NODE : 000         DB   : SAMPLE 
APPHDL  : 1-60027              APPID: *N1.DB2.100822171046 
AUTHID  : DB2INST1 
EDUID   : 35746                EDUNAME: db2stmm (SAMPLE) 0 
FUNCTION: DB2 UDB, Self tuning memory manager, 
stmmGetDBMemDataAutomatic, probe:3824 
DATA #1 : String, 489 bytes 
Configured memory on the system: 2621440 
Memory currently available on the system: 147239 
Configured memory on the partition: 1102245 
Memory currently available on the partition: 160917 
Set's configured size: 199968 
Overflow left: 33072 
Uncommited size: 86256 
Target consumer size: 4500081190153110 
Current consumer size: 166896 
Max growth: 0 
Current overflow percent: 0.200000 
Target overflow percent: 0.000781 
Average benefit: 0 
Global benefit: Instance: DB2INST1 DB: SAMPLE     Benefit: 0 
 
2010-08-23-01.22.46.494730+480 I8863319A631       LEVEL: Warning 
PID     : 303152               TID  : 35746       PROC : db2sysc 
0 
INSTANCE: DB2INST1             NODE : 000         DB   : SAMPLE 
APPHDL  : 1-60027              APPID: *N1.DB2.100822171046 
AUTHID  : DB2INST1 
EDUID   : 35746                EDUNAME: db2stmm (SAMPLE) 0 
FUNCTION: DB2 UDB, Self tuning memory manager, 
stmmCheckIfFreeMemoryIsEnoughForSizeIncr, probe:667 
MESSAGE : ZRC=0xFFFFEC49=-5047 
DATA #1 : String, 143 bytes 
There is not enough free memory for size increase. Free memory 
in pages: Physical memory = 0, Instance memory = 160917, 
Database memory = 33072 
 
2010-08-23-01.22.46.529929+480 I8863951A627       LEVEL: Error 
PID     : 303152               TID  : 35746       PROC : db2sysc 
0 
INSTANCE: DB2INST1             NODE : 000         DB   : SAMPLE 
APPHDL  : 1-60027              APPID: *N1.DB2.100822171046 
AUTHID  : DB2INST1 
EDUID   : 35746                EDUNAME: db2stmm (SAMPLE) 0 
FUNCTION: DB2 UDB, Self tuning memory manager, 
stmmUpdateDBConfig, probe:275 
MESSAGE : ZRC=0x82AE00A7=-2102525785=STMM_CONFIG_UPDATE_FAILED 
          "An attempted configuration update failed" 
DATA #1 : String, 79 bytes 
Error updating parameter Database_memory, updateValue = 208620, 
sqlcode = -5047 
 
2010-08-23-01.22.46.530322+480 I8864579A664       LEVEL: Event 
PID     : 303152               TID  : 35746       PROC : db2sysc 
0 
INSTANCE: DB2INST1             NODE : 000         DB   : SAMPLE 
APPHDL  : 1-60027              APPID: *N1.DB2.100822171046 
AUTHID  : DB2INST1 
EDUID   : 35746                EDUNAME: db2stmm (SAMPLE) 0 
FUNCTION: DB2 UDB, Self tuning memory manager, 
stmmMaintainOverflowSize, probe:4403 
DATA #1 : String, 225 bytes 
Original overflow size: 33072 
Target DBMem size: 4503599627361988 
Growth limit: 68719276752 
Expected DBMem size: 208620 
Current DBMem size: 199968 
Current consumer size: 166896 
Overflow size: 39993 
Overflow percent: 0.200000 
 
If you could see that unrealistically big figures for 'Target 
DBMem size' and 'Target consumer size' are appeared in 
STMM.x.log, in the example above, they are '4503599627361988' 
and '4500081190153110' respectively, then it is an indication 
that this problem applies to your environment.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* see ERROR DESCRIPTION                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.7 Fix Pack 5.                       * 
****************************************************************
Local Fix:
N/A
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 Fix Pack 5.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
18.02.2011
08.12.2011
08.12.2011
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