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

DB2PD -THRESHOLDS DOES NOT PRINT QUEUEING OR TICKETING INFORMATION

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
'db2pd' utility with '-thresholds' option does not print 
threshold queue information for CONCURRENTDBCOORDACTIVITIES and 
TOTALSCPARTITIONCONNECTIONS thresholds. 
The threshold ticket information may not be printed for 
CONCURRENTDBCOORDACTIVITIES either. 
If the first user created service class (Service Class ID  = 14) 
is 
not referenced by a threshold with queue properties 
(CONCURRENTDBCOORDACTIVITIES or TOTALSCPARTITIONCONNECTIONS) 
then queue information will not get printed for any threshold. 
If the first user created service class is not referenced by a 
 
threshold with threshold ticket properties 
(CONCURRENTDBCOORDACTIVITIES) then threshold ticket information 
will not get printed for any threshold. 
 
 
REPRODUCTION: 
****STEP 1****** 
 
db2 create service class sc1  //first user created service class 
(ID =14) 
db2 create service class sc2 
db2 create service class sc3 
 
db2 "create threshold th1 for service class sc1 activities 
enforcement database when ACTIVITYTOTALTIME > 10 minutes 
continue"    //threshold with no queue and no ticket properties 
 
db2 "create threshold th2 for service class sc2 activities 
enforcement database partition when TOTALSCPARTITIONCONNECTIONS 
> 10  continue"        //threshold with queue but no ticket 
properties 
db2 "create threshold th3 for service class sc3 activities 
enforcement database when CONCURRENTDBCOORDACTIVITIES > 200 
continue"                 //threshold with queue and with ticket 
properties 
 
$ db2pd -db sample -thresholds 
 
Service Class Thresholds: 
 
Threshold Name              = TH1 
Threshold ID                = 1 
Domain                      = 30 
Domain ID                   = 14 
.. 
 
Threshold Name              = TH2 
Threshold ID                = 2 
Domain                      = 30 
Domain ID                   = 16 
.. 
 
Threshold Name              = TH3 
Threshold ID                = 3 
Domain                      = 30 
Domain ID                   = 18 
.. 
 
Service Class Threshold Queues: 
 
 
//No queue and no ticket information was printed 
 
**************** 
****STEP 2****** 
 
//creating queue threshold for the first service class 
 
 
db2 "create threshold th4 for service class sc1 activities 
enforcement database partition when TOTALSCPARTITIONCONNECTIONS 
> 10  continue"     //threshold with queue and no ticket 
properties 
 
$ db2pd -db sample -thresholds 
 
Database Partition 0 -- Database SAMPLE -- Active -- Up 0 days 
00:09:20 -- Date 05/05/2011 05:10:09 
 
 
Service Class Thresholds: 
 
Threshold Name              = TH1 
Threshold ID                = 1 
Domain                      = 30 
Domain ID                   = 14 
... 
 
Threshold Name              = TH4 
Threshold ID                = 4 
Domain                      = 30 
Domain ID                   = 14 
... 
 
Threshold Name              = TH2 
.. 
 
Threshold Name              = TH3 
.. 
 
 
 
Service Class Threshold Queues: 
 
Queue information for threshold: TH4 
Max Concurrency             = 10 
Concurrency                 = 0 
Max Queue Size              = 0 
 
Queue information for threshold: TH2 
Max Concurrency             = 10 
Concurrency                 = 0 
Max Queue Size              = 0 
 
Queue information for threshold: TH3 
Max Concurrency             = 200 
Concurrency                 = 0 
Max Queue Size              = 0 
 
// threshold queue information was printed 
 
**************** 
****STEP 3****** 
 
// creating queue and ticket threshold for the first 
service class 
 
db2 "create threshold th5 for service class sc1 activities 
enforcement database when CONCURRENTDBCOORDACTIVITIES > 10 
continue"              //threshold with queue and ticket 
properties 
 
$ db2pd -db sample -thresholds 
 
Database Partition 0 -- Database SAMPLE -- Active -- Up 0 days 
00:11:56 -- Date 05/05/2011 05:12:45 
 
 
 
Service Class Thresholds: 
 
Threshold Name              = TH1 
Threshold ID                = 1 
Domain                      = 30 
Domain ID                   = 14 
... 
 
Threshold Name              = TH4 
Threshold ID                = 4 
Domain                      = 30 
Domain ID                   = 14 
... 
 
Threshold Name              = TH5 
Threshold ID                = 5 
Domain                      = 30 
Domain ID                   = 14 
... 
 
Threshold Name              = TH2 
... 
 
Threshold Name              = TH3 
... 
 
Service Class Threshold Queues: 
 
Queue information for threshold: TH4 
Max Concurrency             = 10 
Concurrency                 = 0 
Max Queue Size              = 0 
 
Queue information for threshold: TH5 
Max Concurrency             = 10 
Concurrency                 = 0 
Max Queue Size              = 0 
 
Queue information for threshold: TH2 
Max Concurrency             = 10 
Concurrency                 = 0 
Max Queue Size              = 0 
 
Queue information for threshold: TH3 
Max Concurrency             = 200 
Concurrency                 = 0 
Max Queue Size              = 0 
 
 
 
Service Class Threshold Tickets: 
 
Ticket information for threshold: TH5 with threshold ID 5 
No tickets currently held 
 
Ticket information for threshold: TH3 with threshold ID 3 
No tickets currently held 
 
//Threshold queue and ticket information was printed
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* The issue is due to incorrect checking while we are printing * 
* threshold queue and threshold ticket information with 'db2pd * 
* -db <> -thresholds'.                                         * 
* If the first user created service class (Service Class ID  = * 
* 14) is not referenced by a threshold with queue properties   * 
* (CONCURRENTDBCOORDACTIVITIES or TOTALSCPARTITIONCONNECTIONS) * 
* then threshold queue information will not be printed for any * 
* thresholds.                                                  * 
* Similar to that, if that service class (ID = 14) is not      * 
* referenced by a threshold with ticket properties             * 
* (CONCURRENTDBCOORDACTIVITIES) then threshold ticket          * 
* information will not get printed for any thresholds.         * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.7 and Fix Pack 5.                   * 
****************************************************************
Local Fix:
Have the first user created service class referenced by 
CONCURRENTDBCOORDACTIVITIES threshold to enable the printing of 
threshold ticket and queue information. A disabled dummy 
threshold may be created for this service class as a workaround, 
i.e. 
"create threshold dummy_th for service class sc1 activities 
enforcement database disable when CONCURRENTDBCOORDACTIVITIES > 
1000 continue"
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
Problem was first fixed in DB2 Version 9.7 and Fix Pack 5.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
04.05.2011
19.12.2011
19.12.2011
Problem solved at the following versions (IBM BugInfos)
9.7.
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.5 FixList