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

DB2STOP FORCE HANGS

product:
DB2 FOR LUW / DB2FORLUW / 980 - DB2
Problem description:
If the user has created a partitioned multi-dimensional 
clustering tables in DB2 9.7 FP1 or DB2 9.7 FP2, then may be 
exposed to this problem.  The problem occurs after performing 
rollout deletes from such a table.  If a db2stop force is then 
issued while the self-tuning memory manager is reducing the size 
of the bufferpool, then db2stop force may hang. 
 
The stack for the self tuning memory manager will look something 
like this: 
<StackTrace> 
##### Object: /lib/sparcv9/libc.so.1 
_syscall(0xfffffffee177e538,0xfffffffec6bfb7e4,0xfffffffee177e53 
c,0x0,0x1,0xfffffffec6bfb5e8) 
+ 0x70 
##### Object: 
/view/db2_v97fp3_sun64_s100714/vbs/engn/lib/libdb2e.so.1 
__1cbAsqlbDecreaseBufferpoolSize6FpnPSQdDLB_BufferPool_pnVSQdDLB 
_BP_UC_ALTER_INFO_pnMSQdDLB_GLOBALS__v_(0xfffffffec6bfff30,0x 
__1cUsqlbResizeBufferPool6FpnPSQdDLB_BufferPool_pnVSQdDLB_BP_UC_ 
ALTER_INFO_pnMSQdDLB_GLOBALS__i_(0xfffffffee177e340,0xfffffff 
__1cbCsqlbAlterAutomaticBufferPool6FIipnIsqeAgent__i_(0x58e,0x0, 
0x202865da0,0x58e,0x0,0xffffffff7af6e23d) 
+ 0x384 
__1cYsqlrlStmmAlterBufferPool6FpnIsqeAgent_pciipnOdb2UCinterface 
_pnFsqlca__i_(0x202865da0,0xffffffff6109bf10,0xb4c68,0x0,0xff 
__1cTstmmAlterBufferPool6FpnIsqeAgent_pcii_i_(0x202865da0,0xffff 
ffff6109bf10,0x3,0x58e,0x0,0x0) 
+ 0x1bc 
__1cbIstmmResizeEntriesAndRemoveFromList6FppnVstmmCostBenefitRec 
ord_pnQsqeLocalDatabase__i_(0xfffffffec6bfc770,0x2006fa000,0x 
__1cOstmmTuneMemory6FppnVstmmCostBenefitRecord_pnQsqeLocalDataba 
se__i_(0xfffffffec6bfc770,0x2006fa000,0xfffffffec6bfc5c0,0x0, 
stmmMemoryTunerMain(0x2006fa000,0x0,0xaa000,0x1,0x0,0xffffffff7b 
3b71fd) 
+ 0x30c 
__1cbAsqleIndCoordProcessRequest6FpnIsqeAgent__v_(0x80000051,0x2 
02865da0,0x0,0x20000,0xffffffff7d63bec8,0xffffffff7cf964d0) 
+ 
__1cIsqeAgentGRunEDU6M_v_(0x202865da0,0x2028672b0,0x18280400,0xf 
fffffff7c011068,0xffffffff7d63bea0,0x7258) 
+ 0x72c 
__1cKsqlzRunEDU6FpcI_v_(0x0,0xffffffff77d63fa8,0x184dae4,0x20286 
5da0,0x18d00000,0xffffffff7c88bac8) 
+ 0xd0 
sqloEDUEntry(0xfffffffec3bf4640,0xfffffffec6bfff30,0x8,0xfffffff 
f7d63bf18,0x18780000,0x0) 
+ 0x3d4 
##### Object: /lib/sparcv9/libc.so.1 
_thr_slot_offset(0x0,0x0,0x0,0x0,0x0,0x0) + 0x488 
</StackTrace>
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All users                                                    * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* If the user has created a partitioned multi-dimensional      * 
* clustering tables in DB2 9.7 FP1 or DB2 9.7 FP2, then may be * 
* exposed to this problem.  The problem occurs after           * 
* performing rollout deletes from such a table.  If a db2stop  * 
* force is then issued while the self-tuning memory manager is * 
* reducing the size of the bufferpool, then db2stop force may  * 
* hang.                                                        * 
*                                                              * 
* The stack for the self tuning memory manager will look       * 
* something like this:                                         * 
*                                                              * 
* <StackTrace>                                                 * 
*                                                              * 
* ##### Object:                                                * 
* /lib/sparcv9/libc.so.1_syscall(0xfffffffee177e538,0xfffffffec6 
* + 0x70                                                       * 
*                                                              * 
* ##### Object:                                                * 
* /view/db2_v97fp3_sun64_s100714/vbs/engn/lib/libdb2e.so.1__1cbA 
*                                                              * 
* __1cUsqlbResizeBufferPool6FpnPSQdDLB_BufferPool_pnVSQdDLB_BP_U 
*                                                              * 
* __1cbCsqlbAlterAutomaticBufferPool6FIipnIsqeAgent__i_(0x58e,0x 
* + 0x384                                                      * 
*                                                              * 
* __1cYsqlrlStmmAlterBufferPool6FpnIsqeAgent_pciipnOdb2UCinterfa 
*                                                              * 
* __1cTstmmAlterBufferPool6FpnIsqeAgent_pcii_i_(0x202865da0,0xff 
* + 0x1bc                                                      * 
*                                                              * 
* __1cbIstmmResizeEntriesAndRemoveFromList6FppnVstmmCostBenefitR 
*                                                              * 
* __1cOstmmTuneMemory6FppnVstmmCostBenefitRecord_pnQsqeLocalData 
*                                                              * 
* stmmMemoryTunerMain(0x2006fa000,0x0,0xaa000,0x1,0x0,0xffffffff 
* + 0x30c                                                      * 
*                                                              * 
* __1cbAsqleIndCoordProcessRequest6FpnIsqeAgent__v_(0x80000051,0 
* +                                                            * 
*                                                              * 
* __1cIsqeAgentGRunEDU6M_v_(0x202865da0,0x2028672b0,0x18280400,0 
* + 0x72c                                                      * 
*                                                              * 
* __1cKsqlzRunEDU6FpcI_v_(0x0,0xffffffff77d63fa8,0x184dae4,0x202 
* + 0xd0                                                       * 
*                                                              * 
* sqloEDUEntry(0xfffffffec3bf4640,0xfffffffec6bfff30,0x8,0xfffff 
* + 0x3d4                                                      * 
*                                                              * 
* ##### Object:                                                * 
* /lib/sparcv9/libc.so.1_thr_slot_offset(0x0,0x0,0x0,0x0,0x0,0x0 
* + 0x488                                                      * 
* </StackTrace>                                                * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 9.7 FP3.                                      * 
****************************************************************
Local Fix:
Issue the killdb2 command to stop DB2.
available fix packs:
DB2 Version 9.8 Fix Pack 4 for AIX and Linux
DB2 Version 9.8 Fix Pack 5 for AIX and Linux

Solution
The problem was first fixed in
Workaround
Issue the killdb2 command to stop DB2.
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
08.06.2011
08.06.2011
08.06.2011
Problem solved at the following versions (IBM BugInfos)
9.7.FP3
Problem solved according to the fixlist(s) of the following version(s)
9.8.0.4 FixList