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

RARE TIMING CONDITION MIGHT CAUSE DB2STOP FORCE AND ALTER TABLES PACE
REDUCE STOP TO HANG WHEN EXTENT MOVEMENT IS IN PROGRESS

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
If extent movement is in the middle of reducing containers, and 
if db2stop force, or alter tablespace reduce stop is issued, DB2 
will attempt to interrupt extent movement.  However, due to this 
problem the extent movement will not be able to receive the 
interrupt request, causing DB2 to hang. 
 
When this happens the extent movement thread will be showing the 
following stacks: 
 
_syscall(0xfffffffeef3c0840,0xfffffffea57fa7ac,0xfffffffeef3c084 
4,0xfffffffea57fa4b0,0x1,0xfffffffea57fa4a8) 
+ 0x70 
##### Object: /vbs/engn/lib/libdb2e.so.1 
__1cIsqeAgentOIntrptWaitLock6MpnQSQdDLO_EDUWAITPOST_ipIi_i_(0x20 
1210080,0xfffffffeef3c0840,0x64,0x0,0xffffffff7cf84f48,0xfffffff 
f870f00b9) 
+ 0x464 
__1cIsqlplnfd6FpnJsqeBsuEdu_pnOSQdDLP_LOCK_INFO_pnISQdDLP_LCB_pn 
JSQdDLP_LHSH_pnISQdDLP_LRB_IiLipnISQdDLP_AWB_i_i_(0x0,0xfffffffe 
ef3c0840,0x0,0xfffffffec1726f30,0xfffffffec273e500,0xffffffff7cf 
84f48) 
+ 0x1670 
__1cIsqlplhed6FpnJsqeBsuEdu_pnOSQdDLP_LOCK_INFO_pnISQdDLP_LCB_pn 
ISQdDLP_AWB_pnJSQdDLP_LHSH_pnISQdDLP_LRB_IiL_i_(0x201210080,0xff 
fffffea57fc0f8,0xfffffffec1780080,0xfffffffeef3c0838,0xfffffffec 
180cd00,0xfffffffec2398880) 
+ 0x1d4 
__1cHsqlplrq6FpnJsqeBsuEdu_pnOSQdDLP_LOCK_INFO__i_(0x3842,0xffff 
fffea57fc0f8,0xffffffff7c002150,0xfffffffeef3c0820,0xfffffffec17 
80080,0x0) 
+ 0x704 
__1cWsqlbEMReduceContainers6FpnMSQdDLB_POOL_CB_IpnJsqeBsuEdu__i_ 
(0xfffffffe00000000,0x20107dbf4,0x201210080,0x0,0x74,0x0) 
+ 0x2e8 
__1cWsqlbLockAndMoveExtents6FpnMSQdDLB_POOL_CB_bIpnJsqeBsuEdu__i 
_(0x1,0xfffffffea57fc4f0,0x3fffff,0x201210080,0xffffffff0dad90a0 
,0x1000) 
+ 0x784 
__1cbCsqlbExtentMovementEntryPoint6FpnJsqeBsuEdu_pv_v_(0x2012100 
80,0xfffffffef640a200,0x11,0xffffffff0dad90a0,0x1408,0x2) 
+ 0xd8 
__1cbAsqleIndCoordProcessRequest6FpnIsqeAgent__v_(0x15d0,0x20121 
0080,0x0,0x20000,0xffffffff7d62a908,0xffffffff7cf84f48) 
+ 0xf94 
__1cIsqeAgentGRunEDU6M_v_(0x201210080,0x201211590,0x18280400,0xf 
fffffff7c002150,0xffffffff7d62a8e0,0x7258) 
+ 0x72c 
 
while the agent attempting to interrupt the extent movement 
agent will be showing the following stacks: 
 
_syscall(0xffffffff0dada4b0,0xfffffffeab3e5814,0xffffffff0dada4b 
4,0x0,0x1,0xfffffffeab3e5618) 
+ 0x70 
##### Object: /vbs/engn/lib/libdb2e.so.1 
__1cbHsqlbTerminateExtentMovementIcoord6FHpnJsqeBsuEdu__i_(0x11, 
0xffffffff7af67e1c,0x0,0xffffffff44361300,0x1400,0xffffffff7c002 
150) 
+ 0x3a4 
__1cNsqlbAlterPool6FHpnbASQdDLB_TABLESPACE_ATTRIBUTES_IpnMSQdDLB 
_GLOBALS__i_(0x2,0x2,0x0,0xffffffff44361300,0x0,0x4000) 
+ 0x9b0 
__1cNsqldPoolAlter6FpnIsqeAgent_HpnbASQdDLB_TABLESPACE_ATTRIBUTE 
S__i_(0x201215da0,0x20112dbf4,0xfffffffeab3ec158,0x5e34,0xff,0xf 
fffffff7cf84f48) 
+ 0x38c 
__1cKsqlrldpalt6FpnIsqlrr_cb_pChpciipnIsqlr_tid_L22pnTsqlrl_tbsp 
ace_parms__i_(0x1000,0x0,0xffffffffffffffff,0x0,0x1b600000,0x11) 
+ 0xa40
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* If extent movement is in the middle of reducing containers,  * 
* and if db2stop force, or alter tablespace reduce stop is     * 
* issued, DB2 will attempt to interrupt extent movement.       * 
* However, due to this problem the extent movement will not be * 
* able to receive the interrupt request, causing DB2 to hang.  * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* On current release, avoid running ALTER TABLESPACE REDUCE    * 
* MAX or ALTER TABLESPACE LOWER HIGH WATER MARK that           * 
* might trigger extent movement; or when extent movement is in * 
* progress, do not attempt to run DB2STOP FORCE or ALTER       * 
* TABLESPACE REDUCE STOP.                                      * 
* Upgrade to DB2 Version 9.7 fix pack 3 or higher.             * 
****************************************************************
Local Fix:
Kill db2 and restart the instance
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
First Fixed in DB2 Version 9.7 fix pack 3
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
22.07.2010
23.09.2010
10.12.2010
Problem solved at the following versions (IBM BugInfos)
9.1.FP7,
9.7.FP3
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.3 FixList
9.7.0.3 FixList