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

DB2START RESTART NEEDS SERIAL FAILOVER CODE RE-USE FROM V91 IN V98
(Parallel failover getting Time out errors or SQL6031N )

product:
DB2 FOR LUW / DB2FORLUW / 980 - DB2
Problem description:
Customers migrating from v91 to v98 are facing difficulties when 
trying to setup high availability (HA) environments. They are 
accustomed to using v8 and v91 methods for node fail-over. 
 
The functionality introduced in v95 and later for failover is: 
 
If no port 0 exists on the target machine (that is, no nodes are 
currently associated with it), then there are two steps to 
fail-over: 
1. Serially move any node from the source machine that is not 
port 0 to the target at port 0. 
2. In parallel, move all remaining nodes (or one by one if so 
desired with port 0 on source being last) 
 
If there does exist nodes on the target machine already, this 
operation does not require the serial step. All nodes can be 
moved in parallel. 
 
To move nodes in parallel, follow the following is necessary: 
 
Given: 
0 one.ca.ibm.com 0 
1 one.ca.ibm.com 1 
2 one.ca.ibm.com 2 
 
Port 0 non-existent on target machine 
1. Serial 
$ db2start dbpartitionnum 2 restart hostname two.ca.ibm.com port 
0 
2. In Parallel 
$ db2start dbpartitionnum 1 restart hostname two.ca.ibm.com port 
1 & 
$ db2start dbpartitionnum 0 restart hostname two.ca.ibm.com port 
2 & 
 
Port 0 exists on target machine 
In Parallel 
$ db2start dbpartitionnum 2 restart hostname two.ca.ibm.com port 
1 & 
$ db2start dbpartitionnum 1 restart hostname two.ca.ibm.com port 
2 & 
$ db2start dbpartitionnum 0 restart hostname two.ca.ibm.com port 
3 & 
 
Otherwise the following error will occur: 
 
SQL6031N Error in the db2nodes.cfg file at line number "3". 
Reason code "13". 
 
Also when trying to start on the target machine a node that is 
port 0 on the source machine first, the failover might appear to 
hung showing timeout errors in the db2diag.log: 
 
FUNCTION: DB2 UDB, base sys utilities, sqleGetSpinLock, probe:40 
DATA #1 : String, 64 bytes 
Waited for other mlns to complete(mlns,elapsed time in seconds): 
DATA #2 : Hexdump, 4 bytes 
0x0FFFFFFFFFFF74C8 : 0000 000A .... 
DATA #3 : Hexdump, 4 bytes 
0x0FFFFFFFFFFF74CC : 0000 000C .... 
... 
FUNCTION: DB2 UDB, base sys utilities, sqleGetSpinLock, probe:50 
DATA #1 : String, 88 bytes 
Time out in port zero host restart,while waiting for other mlns 
on sam 
host to complete 
DATA #2 : Hexdump, 4 bytes 
0x0FFFFFFFFFFF74C8 : 0000 000A .... 
DATA #3 : Hexdump, 4 bytes 
0x0FFFFFFFFFFF74CC : 0000 00F0 
 
The functionality for v9.5 and later introduced a parallel start 
feature, which means that logical port 0 will have to be moved 
last, not first. 
 
This APAR will allow for the old v9.1 behaviour to be available 
in v9.5 and later
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* The default behaviour will be Parallel:                      * 
*                                                              * 
* Use the following to turn on the Parallel feature:           * 
*                                                              * 
* db2set DB2_PMODEL_SETTINGS=SERIAL_RESTART:FALSE              * 
*                                                              * 
* The Serial is reset by:                                      * 
*                                                              * 
* db2set DB2_PMODEL_SETTINGS=SERIAL_RESTART:TRUE               * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.8 Fixpack 0                         * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 9.8 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.8 Fix Pack 4 for AIX and Linux
DB2 Version 9.8 Fix Pack 5 for AIX and Linux

Solution
Problem was first fixed in DB2 Version 9.8 Fixpack 0
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
16.03.2010
10.01.2011
18.02.2011
Problem solved at the following versions (IBM BugInfos)
9.8.FP0
Problem solved according to the fixlist(s) of the following version(s)
9.8.0.3 FixList