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

WITH DB2 V11.1 M1FP1 ON ZLINUX WITH HARDWARE LEVEL EQUAL OR OLDER THAN
ZEC12 DB2START WILL FAIL

product:
DB2 FOR LUW / DB2FORLUW / B10 - DB2
Problem description:
With DB2 v11.1 m1fp1 on zLinux: 
 
Informational tokens are "DB2 v11.1.1.1", "s1612051900", 
"DYN1612051900Z390", Fix Pack "1". 
 
with hardware level equal or older then zEC12 db2start will fail 
with the following... 
 
db2start 
01/12/2017 09:50:59     0   0   SQL1042C  An unexpected system 
error occurred. 
SQL1032N  No start database manager command was issued. 
SQLSTATE=57019 
 
In db2diag.log, the following messages can be seen: 
 
2017-01-12-09.50.13.821967-420 E15035A1474          LEVEL: 
Severe 
PID     : 35871                TID : 4397341862160  PROC : 
db2sysc 0 
INSTANCE: db2inst1               NODE : 000 
HOSTNAME: myhost 
EDUID   : 1                    EDUNAME: db2sysc 0 
FUNCTION: DB2 UDB, oper system services, sqloEDUCodeTrapHandler, 
probe:90 
MESSAGE : ADM14011C  A critical failure has caused the following 
type of error: 
          "Trap". The 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: 
 
"/home/db2inst1/sqllib/db2dump/FODC_Trap_2017-01-12-09.50.10.746 
429_0000 
          /". 
DATA #1 : Signal Number Recieved, 4 bytes 
4 
DATA #2 : Siginfo, 128 bytes 
0x000003FFD5FE4D10 : 0000 0004 0000 0000 0000 0001 FD69 A298 
.............i.. 
0x000003FFD5FE4D20 : 0000 03FF F05F 2E72 0000 03FF FD69 9F6C 
....._.r.....i.l 
0x000003FFD5FE4D30 : 0000 03FF D5FE 4CB8 0000 0000 0000 0000 
......L......... 
0x000003FFD5FE4D40 : 0000 03FF EA4E 2B98 0000 03FF D5FE 4DE8 
.....N+.......M. 
0x000003FFD5FE4D50 : 0000 0000 0000 0000 0000 0000 0000 0000 
................ 
0x000003FFD5FE4D60 : 0000 0000 0000 0005 0000 0000 02EE 450E 
..............E. 
0x000003FFD5FE4D70 : 0000 03FF D5FE 4F28 0000 03FF EA37 DCA0 
......O(.....7.. 
0x000003FFD5FE4D80 : 0000 03FF D5FE 4F18 0000 03FF D5FE 4DA0 
......O.......M. 
 
2017-01-12-09.50.13.879410-420 I16510A1486          LEVEL: Event 
PID     : 35871                TID : 4397341862160  PROC : 
db2sysc 0 
INSTANCE: db2inst1               NODE : 000 
HOSTNAME: myhost 
EDUID   : 1                    EDUNAME: db2sysc 0 
FUNCTION: DB2 UDB, oper system services, 
sqloPGRPRegisterOneCrash, probe:2161 
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] 0x000003FFF57D9C44 sqloPGRPRegisterOneCrash + 0x414 
  [1] 0x000003FFF592D466 sqloEDUCodeTrapHandler + 0x1A52 
  [2] 0x000003FFD5FE4D08 0x000003FFD5FE4D08 + 0x0 
  [3] 0x000003FFF05F2E78 
_ZN7ibm_cde5query14PackedBankSIMDILi2EE27initializePrecomputedTa 
blesEv + 0x310 
  [4] 0x000003FFEDE8D938 
_ZN7ibm_cde4data10cdeStartupENS0_11StartupModeE + 0x190 
  [5] 0x000003FFF1AECFE6 _ZN12cdeInterface14initCdeRuntimeEv + 
0x8A 
  [6] 0x0000000080017C32 
_Z15sqleInitSysCtlrPmPtP15sqleResyncAgtCB + 0x1636 
  [7] 0x0000000080014282 _Z11sqleSysCtlrv + 0x19E 
  [8] 0x000003FFF5925864 
/home/db2inst1/sqllib/lib64/libdb2e.so.1 + 0xB6C3864 
  [9] 0x000003FFF5924666 sqloRunInstance + 0x3CA 
  [10] 0x000000008000C9BC DB2main + 0x11D4 
  [11] 0x000003FFF59311F0 _Z16sqloEDUMainEntryPcj + 0x24 
  [12] 0x000003FFF592D87A sqloEDUEntry + 0x28A 
  [13] 0x000003FFFD658524 /lib64/libpthread.so.0 + 0x8524 
  [14] 0x000003FFE9957F4A /lib64/libc.so.6 + 0xE7F4A 
 
Looking at the /var/log/messages file, the following can be 
seen: 
 
2017-01-12T09:50:13.887064-07:00 myhost kernel: User process 
fault: interruption code 0x60001 in libdb2e.so.1 
[3ffea262000+11847000] 
2017-01-12T09:50:13.887084-07:00 myhost kernel: CPU: 1 PID: 
35872 Comm: db2sysc Not tainted 3.12.28-4-default #1 
2017-01-12T09:50:13.887086-07:00 myhost kernel: task: 
000000023776a438 ti: 000000012ac50000 task.ti: 000000012ac50000 
2017-01-12T09:50:13.887097-07:00 myhost kernel: User PSW : 
0705200180000000 000003fff05f2e90 (0x3fff05f2e90) 
2017-01-12T09:50:13.887100-07:00 myhost kernel:           R:0 
T:1 IO:1 EX:1 Key:0 M:1 W:0 P:1 AS:0 CC:2 PM:0 EA:3 
2017-01-12T09:50:13.887101-07:00 myhost kernel: User GPRS: 
0000000000000001 000003fffd5f98e8 000003ff00000001 
000003ffd5fe4fd8 
2017-01-12T09:50:13.887103-07:00 myhost kernel: 
000000000000003e 0000000000000000 4000000000000000 
0000000000000001 
2017-01-12T09:50:13.887105-07:00 myhost kernel: 
5555555555555555 000003ffd5fe5030 000003ffd5fe4fe8 
0000000000000000 
2017-01-12T09:50:13.887107-07:00 myhost kernel: 
000003fffd605fa0 000003ffd5fe4ff8 0000000000000002 
000003ffd5fe4f18 
2017-01-12T09:50:13.887109-07:00 myhost kernel: User Code: 
000003fff05f2e7e: e380a0080004    lg    %r8,8(%r10) 
2017-01-12T09:50:13.887111-07:00 myhost kernel: 
000003fff05f2e84: ebe02000000d    sllg    %r14,%r0,0(%r2) 
2017-01-12T09:50:13.887113-07:00 myhost kernel: 
#000003fff05f2e8a: ecc820bf0059    risbgn    %r12,%r8,32,191,0 
2017-01-12T09:50:13.887116-07:00 myhost kernel: 
>000003fff05f2e90: b9040008        lgr    %r0,%r8 
2017-01-12T09:50:13.887118-07:00 myhost kernel: 
000003fff05f2e94: eb6e4000000d    sllg    %r6,%r14,0(%r4) 
2017-01-12T09:50:13.887120-07:00 myhost kernel: 
000003fff05f2e9a: b904002c        lgr    %r2,%r12 
2017-01-12T09:50:13.887129-07:00 myhost kernel: 
000003fff05f2e9e: eb480020000c    srlg    %r4,%r8,32 
2017-01-12T09:50:13.887131-07:00 myhost kernel: 
000003fff05f2ea4: b90c0007        msgr    %r0,%r7 
2017-01-12T09:50:13.887132-07:00 myhost kernel: Last 
Breaking-Event-Address: 
2017-01-12T09:50:13.887139-07:00 myhost kernel: 
[<0000000000619e48>] sysc_restore+0x22/0x26 
2017-01-12T09:50:13.887132-07:00 myhost rsyslogd-2007: action 
'action 2' suspended, next retry is Thu Jan 12 09:51:43 2017 
[try http://www.rsyslog.com/e/2007 ] 
 
NOTE this line: 
 
2017-01-12T09:50:13.887113-07:00 myhost kernel: 
#000003fff05f2e8a: ecc820bf0059    risbgn    %r12,%r8,32,191,0
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 11.1 Mod1 Fix Pack 1 iFix001                  * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 11.1 Mod1 Fix Pack1 iFix001 for Linux, UNIX, and Windows
DB2 Version 11.1 Mod 2 Fix Pack 2 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod2 Fix Pack2 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod2 Fix Pack2 iFix002 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod 3 Fix Pack 3 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix002 for Linux, UNIX, and Windows

Solution
First fixed in DB2 11.1 Mod1 Fix Pack 1 iFix001
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
19.01.2017
01.05.2017
01.05.2017
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)