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

A PURESCALE MEMBER MIGHT TRAP IN MON_GET_UNIT_OF_WORK PROCESSING WHILE
ANOTHER MEMBER IS STOPPING

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
In purescale environment, a member might trap and restart in 
MON_GET_UNIT_OF_WORK, MON_GET_CONNECTION, MON_GET_PKG_CACHE_STMT 
or PD_GET_DIAG_HIST UDF processing while another member is 
stopping.   When this case occurs, the following logs can be 
seen in db2diag.log: 
 
2014-12-04-16.07.03.845117+540 I4201485A587         LEVEL: Info 
PID     : 3671426              TID : 288566         PROC : 
db2sysc 0 
INSTANCE: *****             NODE : 000           DB   : ***** 
APPHDL  : 0-35690              APPID: *N0.*****.141211032904 
AUTHID  : *****             HOSTNAME: ***** 
EDUID   : 288566               EDUNAME: db2agent (*******) 0 
FUNCTION: DB2 UDB, relation data serv, sqlrkrpc_nl, probe:2368 
DATA #1 : String, 42 bytes 
RPC was re-sent because of DB deactivation 
DATA #2 : String, 10 bytes 
numRetries 
DATA #3 : unsigned integer, 8 bytes 
1 
... 
 
2014-12-04-16.07.23.314785+540 E4307950A1306        LEVEL: 
Severe 
PID     : 3671426              TID : 288566         PROC : 
db2sysc 0 
INSTANCE: *****             NODE : 000           DB   : ***** 
APPHDL  : 0-35690              APPID: *N0.*****.141211032904 
AUTHID  : *****               HOSTNAME: ***** 
EDUID   : 288566               EDUNAME: db2agent (*****) 0 
FUNCTION: DB2 UDB, oper system services, sqloEDUCodeTrapHandler, 
probe:90 
MESSAGE : ADM14011C  A critical failure has caused the following 
type of error: 
          "Trap". The DB2 database manager cannot recover from 
the failure. 
          First Occurrence Data Capture (FODC) was invoked in 
the following 
          mode: "Automatic". FODC diagnostic information is 
located in the 
          following directory: 
 
"/db2/*****/dump/DIAG0000/FODC_AppErr_2014-12-04-16.07.06.432309 
_ 
          3671426_288566_000/". 
DATA #1 : Signal Number Recieved, 4 bytes 
11 
DATA #2 : Siginfo, 64 bytes 
0x0A0000012940EDC0 : 0000 000B 0000 0000 0000 0032 0000 0000 
...........2.... 
0x0A0000012940EDD0 : 0000 0000 0000 0000 5449 4442 5641 4C31 
........******* 
0x0A0000012940EDE0 : 0000 0000 0000 0000 0000 0000 0000 0000 
................ 
0x0A0000012940EDF0 : 0000 0000 0000 0000 0000 0000 0000 0000 
................ 
 
2014-12-04-16.07.23.321243+540 I4309257A808         LEVEL: Event 
PID     : 3671426              TID : 288566         PROC : 
db2sysc 0 
INSTANCE: *****             NODE : 000           DB   : ***** 
APPHDL  : 0-35690              APPID: *N0.*****.141211032904 
AUTHID  : *****             HOSTNAME: ***** 
EDUID   : 288566               EDUNAME: db2agent (*******) 0 
FUNCTION: DB2 UDB, oper system services, 
sqloPGRPRegisterOneCrash, probe:2158 
MESSAGE : lastCrashCount 
DATA #1 : unsigned integer, 8 bytes 
0 
DATA #2 : String, 10 bytes 
inRecovery 
DATA #3 : Boolean, 1 bytes 
false 
CALLSTCK: (Static functions may not be resolved correctly, as 
they are resolved to the nearest symbol) 
  [0] 0x0900000035566AFC sqloPGRPRegisterOneCrash + 0x1D4 
  [1] 0x09000000355677B0 sqloEDUCodeTrapHandler + 0xB50 
 
In a trap file, stacktraces can be shown as following: 
<StackTrace> 
-------Frame------ ------Function + Offset------ 
0x0900000035E13548 
sqlkdDispatchRequest__FP23SQLKD_RQST_REPLY_FORMATP14sqeApplicati 
on + 0x2C0 
0x090000003529C198 
sqlrkrpc_nl__FP8sqlrr_cbiN22PCsP15SQLR_RPCMESSAGEP13SQLO_MEM_POO 
LP18SQLR_RPC_REPLY_HDRPbPlUlP17SQLR_WLM_BDSREPLY + 0x31BC 
0x09000000352983E8 
sqlrkrpc_all__FP8sqlrr_cbiP15SQLR_RPCMESSAGEP13SQLO_MEM_POOLPP18 
SQLR_RPC_REPLY_HDRT2UlP17SQLR_WLM_BDSREPLY + 0x785C 
0x09000000359B6B00 sqlerTrustedRtnCallbackRouter__FUiPPv + 
0x2E134 
0x09000000125FBE78 wlmGetNextBuffer + 0xF8 
0x09000000125FBE78 wlmGetNextBuffer + 0xF8 
0x090000001261CFD8 
monGetUnitOfWorkCommon__FP5sqlcaPFUiPPv_iR13uowParameters24sqlmM 
etricOutputFunctionPcN35P17sqludf_scratchpadP16sqludf_call_type 
+ 0x2F8 
0x090000001261CB54 monGetUnitOfWork_v105fp4 + 0x1CD4 
0x090000001261E7EC monGetUnitOfWork + 0x16AC
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.5 Fixpack 7.                       * 
****************************************************************
Local Fix:
Solution
First fixed in Version 10.5 Fixpack 7.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
23.01.2015
26.01.2016
26.01.2016
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.5.0.7 FixList