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

RLSCONV REUSE AND SQLSTT ARE WRONGLY RETURNED AGAINST UNIT OF WORK
COMMITTED SYNCTYPE IN RECEIVED RQSDSS ON XA INTERFACE

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
During XA transaction processing, RLSCONV REUSE and SQLSTT are 
wrongly returned after Unit of work committed SYNCTYPE is 
received in RQSDSS, then it can induce the "DSS chained with 
same id at end of same id chain parse. ERRORCODE=-4499" error on 
the client. 
 
  In the case of a jcc application, we can see the following 
exception. 
 
  Exception message = [jcc][2035][11153][3.61.75] DSS chained 
with same id at end of same id chain parse. ERRORCODE=-4499, 
SQLSTATE=null 
  com.ibm.db2.jcc.am.DisconnectRecoverableException: 
[jcc][2035][11153][3.61.75] DSS chained with same id at end of 
same id chain parse. ERRORCODE=-4499, SQLSTATE=null 
        at com.ibm.db2.jcc.am.ed.a(ed.java:317) 
        at com.ibm.db2.jcc.am.ed.a(ed.java:356) 
        at com.ibm.db2.jcc.t4.z.a(z.java:1170) 
        at com.ibm.db2.jcc.t4.z.w(z.java:1164) 
        at com.ibm.db2.jcc.uw.UWReply.e(UWReply.java:372) 
        at com.ibm.db2.jcc.t4.o.e(o.java:54) 
        at com.ibm.db2.jcc.t4.b.zb(b.java:2565) 
        at com.ibm.db2.jcc.am.jb.o(jb.java:1105) 
        at com.ibm.db2.jcc.am.jb.i(jb.java:1034) 
        at com.ibm.db2.jcc.t4.b.i(b.java:5000) 
        at com.ibm.db2.jcc.am.jb.j(jb.java:1041) 
        at com.ibm.db2.jcc.am.vm.k(vm.java:616) 
        at com.ibm.db2.jcc.am.vm.d(vm.java:510) 
        at com.ibm.db2.jcc.am.vm.c(vm.java:414) 
        at com.ibm.db2.jcc.am.vm.next(vm.java:308) 
 
 
  "db2trc fmt -c" output shows the following information during 
the problem reproduction. 
 
4739237 data DB2 UDB DRDA Communication Manager sqljcReceive fnc 
(3.3.54.3.0.1178) 
    pid 4063270 tid 55101 cpid 9371728 node 0 sec 7525616 nsec 
751238230 probe 1178 
    bytes 48 
 
    RECEIVE BUFFER(AS): 
 
            SYNCCTL RQSDSS                   (ASCII) 
(EBCDIC) 
         0 1 2 3 4 5 6 7  8 9 A B C D E F   0123456789ABCDEF 
0123456789ABCDEF 
  0000  001FD00100010019 1055000511870300   .........U...... 
..}..........g.. 
  0010  081801FFFFFFFF00 08190310000000     ............... 
............... 
 
  DDM Format: d0 RECV(AS) RQSDSS - Request Data Stream Structure 
  LL: 31  CORR: 0001  CHAINED: n  CONT ON ERR: n  SAME CORR FOR 
NEXT DSS: n 
 
    NM: SYNCCTL - Sync Point Control Request 
      LL: 25    CP: 1055 
      NM: SYNCTYPE - Sync Point Operation Type 
        LL: 5    CP: 1187 
        Unit of work committed (0X03) 
      NM: XID - Transaction Indentifier (XID) 
        LL: 8    CP: 1801 
        DATA: FFFFFFFF 
      NM: XAFLAGS - XA Flags 
        LL: 8    CP: 1903 
        FLAGS: 10000000 
          Local Transaction 
 
 
4739370 data DB2 UDB DRDA Communication Manager sqljcSend fnc 
(3.3.54.5.0.1177) 
    pid 4063270 tid 55101 cpid 9371728 node 0 sec 7525616 nsec 
751365812 probe 1177 
    bytes 87 
 
    SEND BUFFER(AS): 
 
            SYNCCRD OBJDSS                   (ASCII) 
(EBCDIC) 
         0 1 2 3 4 5 6 7  8 9 A B C D E F   0123456789ABCDEF 
0123456789ABCDEF 
  0000  0017D05300010011 1248000819040000   ...S.....H...... 
..}............. 
  0010  00000005119FF2                      ....... 
......2 
 
            SQLSTT OBJDSS                    (ASCII) 
(EBCDIC) 
         0 1 2 3 4 5 6 7  8 9 A B C D E F   0123456789ABCDEF 
0123456789ABCDEF 
  0000  002FD00300010029 2414FF000000001F   ./.....)$....... 
..}............. 
  0010  5345542043555252 454E542053434845   SET CURRENT SCHE 
.........+...... 
  0020  4D41203D20224143 30312020202022     MA = "xxxx    " 
(.............. 
 
  DDM Format: d0 SEND(AS) OBJDSS - Object Data Stream Structure 
  LL: 23  CORR: 0001  CHAINED: y  CONT ON ERR: n  SAME CORR FOR 
NEXT DSS: y 
 
    NM: SYNCCRD - Sync Point Control Reply 
      LL: 17    CP: 1248 
      NM: XARETVAL - XA return Value 
        LL: 8    CP: 1904 
        OK (0) 
      NM: RLSCONV - Release Conversation 
        LL: 5    CP: 119F 
        RLSCONV REUSE 
 
  DDM Format: d0 SEND(AS) OBJDSS - Object Data Stream Structure 
  LL: 47  CORR: 0001  CHAINED: n  CONT ON ERR: n  SAME CORR FOR 
NEXT DSS: n 
 
    NM: SQLSTT - SQL Statement 
      LL: 41    CP: 2414 
      DATA:                              (ASCII) 
(EBCDIC) 
      FF000000001F5345 542043555252454E  ......SET CURREN 
...............+ 
      5420534348454D41 203D202241433031  T SCHEMA = "xxxx 
......(......... 
      2020202022                             "            .....
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* XA transaction user                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* During XA transaction processing, RLSCONV REUSE and SQLSTT   * 
* arewr ongly returned after Unit of work committed SYNCTYPE   * 
* is re ceived in RQSDSS, then it can induce the "DSS chained  * 
* with sa me id at end of same id chain parse.                 * 
* ERRORCODE=-4499" error onth e client.                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to db2 Version 9.7 FixPak 5                          * 
****************************************************************
Local Fix:
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 Version 9.7 FixPak 5
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
25.03.2011
15.12.2011
15.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