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

STARTING IN V10.1, DB2PD -DBCFG MIGHT RETURNS INCORRECT HADR ROLES

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
The reason is prior to v10.1, HADR role is stored in database 
configuration but in 10.1 code was changed to store information 
in the global structure which was not copied to database 
configuration file. Hence db2pd -dbcfg returned incorrect 
result. 
Primary: 
[test@Testmachine]/nfshome/test>db2pd -db drdb -dbcfg |grep -E 
"Description|role" 
Description                    Memory Value         Disk Value 
 
HADR database role             STANDARD             STANDARD 
 
 
[test@Testmachine]/nfshome/test>db2pd -db drdb -hadr 
 
Database Member 0 -- Database DRDB -- Active -- Up 0 days 
00:12:09 -- Date 2014-07-17-19.28.38.018023 
 
                            HADR_ROLE = PRIMARY 
                          REPLAY_TYPE = PHYSICAL 
                        HADR_SYNCMODE = SYNC 
                           STANDBY_ID = 1 
                        LOG_STREAM_ID = 0 
                           HADR_STATE = PEER 
                  PRIMARY_MEMBER_HOST = Testmachine 
                     PRIMARY_INSTANCE = test 
                       PRIMARY_MEMBER = 0 
                  STANDBY_MEMBER_HOST = gauss 
                     STANDBY_INSTANCE = test 
                       STANDBY_MEMBER = 0 
                  HADR_CONNECT_STATUS = CONNECTED 
             HADR_CONNECT_STATUS_TIME = 07/17/2014 
19:16:38.230848 (1405649798) 
          HEARTBEAT_INTERVAL(seconds) = 5 
                HADR_TIMEOUT(seconds) = 20 
        TIME_SINCE_LAST_RECV(seconds) = 5 
             PEER_WAIT_LIMIT(seconds) = 0 
           LOG_HADR_WAIT_CUR(seconds) = 0.000 
    LOG_HADR_WAIT_RECENT_AVG(seconds) = 0.000000 
   LOG_HADR_WAIT_ACCUMULATED(seconds) = 0.000 
                  LOG_HADR_WAIT_COUNT = 0 
SOCK_SEND_BUF_REQUESTED,ACTUAL(bytes) = 0, 16384 
SOCK_RECV_BUF_REQUESTED,ACTUAL(bytes) = 0, 87380 
            PRIMARY_LOG_FILE,PAGE,POS = S0000000.LOG, 0, 
40760046 
            STANDBY_LOG_FILE,PAGE,POS = S0000000.LOG, 0, 
40760046 
                  HADR_LOG_GAP(bytes) = 0 
     STANDBY_REPLAY_LOG_FILE,PAGE,POS = S0000000.LOG, 0, 
40760046 
       STANDBY_RECV_REPLAY_GAP(bytes) = 0 
                     PRIMARY_LOG_TIME = 07/01/2014 
18:20:59.000000 (1404264059) 
                     STANDBY_LOG_TIME = 07/01/2014 
18:20:59.000000 (1404264059) 
              STANDBY_REPLAY_LOG_TIME = 07/01/2014 
18:20:59.000000 (1404264059) 
         STANDBY_RECV_BUF_SIZE(pages) = 4300 
             STANDBY_RECV_BUF_PERCENT = 0 
           STANDBY_SPOOL_LIMIT(pages) = 0 
                 PEER_WINDOW(seconds) = 30 
                      PEER_WINDOW_END = 07/17/2014 
19:29:03.000000 (1405650543) 
             READS_ON_STANDBY_ENABLED = N 
 
[test@Testmachine]/nfshome/test>db2 connect to drdb 
 
   Database Connection Information 
 
 Database server        = DB2/LINUXX8664 10.1.4 
 SQL authorization ID   = test 
 Local database alias   = DRDB 
 
[test@Testmachine]/nfshome/test>db2 get db cfg for drdb show 
detail|grep -E "Value|database role" 
 Description                                   Parameter 
Current Value              Delayed Value 
 HADR database role                                      = 
PRIMARY                    PRIMARY 
 
 
Standby: 
[test@gauss]/nfshome/test>db2pd -db drdb -dbcfg |grep -E 
"Description|role" 
Description                    Memory Value         Disk Value 
 
HADR database role             STANDARD             STANDBY 
 
 
[test@gauss]/nfshome/test>db2pd -db drdb -hadr 
 
Database Member 0 -- Database DRDB -- Standby -- Up 0 days 
00:21:24 -- Date 2014-07-17-19.36.47.318351 
 
                            HADR_ROLE = STANDBY 
                          REPLAY_TYPE = PHYSICAL 
                        HADR_SYNCMODE = SYNC 
                           STANDBY_ID = 0 
                        LOG_STREAM_ID = 0 
                           HADR_STATE = PEER 
                  PRIMARY_MEMBER_HOST = Testmachine 
                     PRIMARY_INSTANCE = test 
                       PRIMARY_MEMBER = 0 
                  STANDBY_MEMBER_HOST = gauss 
                     STANDBY_INSTANCE = test 
                       STANDBY_MEMBER = 0 
                  HADR_CONNECT_STATUS = CONNECTED 
             HADR_CONNECT_STATUS_TIME = 07/17/2014 
19:16:38.234573 (1405649798) 
          HEARTBEAT_INTERVAL(seconds) = 5 
                HADR_TIMEOUT(seconds) = 20 
        TIME_SINCE_LAST_RECV(seconds) = 4 
             PEER_WAIT_LIMIT(seconds) = 0 
           LOG_HADR_WAIT_CUR(seconds) = 0.000 
    LOG_HADR_WAIT_RECENT_AVG(seconds) = 0.000000 
   LOG_HADR_WAIT_ACCUMULATED(seconds) = 0.000 
                  LOG_HADR_WAIT_COUNT = 0 
SOCK_SEND_BUF_REQUESTED,ACTUAL(bytes) = 0, 16384 
SOCK_RECV_BUF_REQUESTED,ACTUAL(bytes) = 0, 87380 
            PRIMARY_LOG_FILE,PAGE,POS = S0000000.LOG, 0, 
40760046 
            STANDBY_LOG_FILE,PAGE,POS = S0000000.LOG, 0, 
40760046 
                  HADR_LOG_GAP(bytes) = 0 
     STANDBY_REPLAY_LOG_FILE,PAGE,POS = S0000000.LOG, 0, 
40760046 
       STANDBY_RECV_REPLAY_GAP(bytes) = 0 
                     PRIMARY_LOG_TIME = 07/01/2014 
18:20:59.000000 (1404264059) 
                     STANDBY_LOG_TIME = 07/01/2014 
18:20:59.000000 (1404264059) 
              STANDBY_REPLAY_LOG_TIME = 07/01/2014 
18:20:59.000000 (1404264059) 
         STANDBY_RECV_BUF_SIZE(pages) = 4300 
             STANDBY_RECV_BUF_PERCENT = 0 
           STANDBY_SPOOL_LIMIT(pages) = 0 
                 PEER_WINDOW(seconds) = 30 
                      PEER_WINDOW_END = 07/17/2014 
19:37:13.000000 (1405651033) 
             READS_ON_STANDBY_ENABLED = N 
 
[test@gauss]/nfshome/test>db2 get db cfg for drdb |grep -i role 
 HADR database role                                      = 
STANDBY
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All DB2 V10.5 Users                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 V10.5 Fix Pack 5 or higher.                   * 
****************************************************************
Local Fix:
Use 'db2pd -hadr' or 'db2 get db cfg' instead
Solution
Fixed in DB2 V10.5 Fix Pack 5.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
11.08.2014
16.04.2015
16.04.2015
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.5.0.5 FixList