home clear 64x64
en blue 200x116 de orange 200x116 info letter User
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 IC91719 Status: Closed

QUERY MAY HANG WITH FEDERATED AND DB2_COMPATIBILITY_VECTOR=ORA

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
When db2set DB2_COMPATIBILITY_VECTOR=ORA with FEDERATED=YES, 
query may hang without 
any output. 
 
The query stuck in compile phase, here is two stack traceback 
 
stack 1: 
 
0x00002AAAAD248444 
_Z17sqlnd_derived_qncP9sqlnq_qncPS0_R17sqlnq_qunElemListRi + 
0x009a 
      (/home/db2inst1/sqllib/lib64/libdb2e.so.1) 
0x00002AAAAD2488DF 
_Z22sqlnd_rtype_capabilityP9sqlnq_pidS0_sR17sqlnq_qunElemListRiS 
3_P9sqlnq_sat22sqlnd_pid_Context_Flag + 0x010d 
      (/home/db2inst1/sqllib/lib64/libdb2e.so.1) 
0x00002AAAAD23C64F 
_Z20sqlnd_inlist_pad_pdaP9sqlnq_expP9sqlnq_pidR17sqlnq_qunElemLi 
stiRiRS2_P9sqlnq_sat + 0x215f 
      (/home/db2inst1/sqllib/lib64/libdb2e.so.1) 
0x00002AAAAD2157EB 
_Z20sqlnd_exp_qunset_pdaP9sqlnq_expP9sqlnq_pidR17sqlnq_qunElemLi 
stiRiRS2_P9sqlnq_sat + 0xb755 
      (/home/db2inst1/sqllib/lib64/libdb2e.so.1) 
0x00002AAAAD203907 
_Z21sqlnd_prd_qun_vis_pdaP9sqlnq_prdP9sqlnq_qun + 0x0a73 
      (/home/db2inst1/sqllib/lib64/libdb2e.so.1) 
0x00002AAAAD1ECB3D 
_Z27sqlnd_oprprd_qunset_vis_pdaP9sqlnq_oprR17sqlnq_qunElemList + 
0x0273 
      (/home/db2inst1/sqllib/lib64/libdb2e.so.1) 
0x00002AAAAD1DDF29 _Z13sqlnd_opr_pdaRP9sqlnq_oprRiRP9sqlnq_sati 
+ 0x0421 
      (/home/db2inst1/sqllib/lib64/libdb2e.so.1) 
0x00002AAAAD1DD403 _Z13sqlnd_qtb_pdaRP9sqlnq_qtbS1_ii + 0x0d33 
      (/home/db2inst1/sqllib/lib64/libdb2e.so.1) 
0x00002AAAAD1DC633 _Z13sqlnd_qtb_pdaRP9sqlnq_qtbi + 0x00a7 
      (/home/db2inst1/sqllib/lib64/libdb2e.so.1) 
0x00002AAAAD1DB0C6 _Z17sqlnd_qtb_pda_qrwP9sqlnq_qtb + 0x0176 
      (/home/db2inst1/sqllib/lib64/libdb2e.so.1) 
0x00002AAAAE1044F9 
_Z21sqlnr_sel_mrg_precondP9sqlnq_qtbP9sqlnq_qunPi + 0x0823 
      (/home/db2inst1/sqllib/lib64/libdb2e.so.1) 
0x00002AAAAE104D83 
_Z18sqlnr_sel_mrg_condP14sqlnr_progressP10sqlnr_qrwaPi + 0x00ff 
 
      (/home/db2inst1/sqllib/lib64/libdb2e.so.1) 
 
stack 2: 
 
0x00002AAAAD1DC277 _Z16sqlnd_sat_of_qunP9sqlnq_qun + 0x001f 
      (/home/db2inst1/sqllib/lib64/libdb2e.so.1) 
0x00002AAAAD25D130 _Z19sqlnd_sat_of_qunsetR17sqlnq_qunElemList + 
0x0122 
      (/home/db2inst1/sqllib/lib64/libdb2e.so.1) 
0x00002AAAAD248870 
_Z22sqlnd_rtype_capabilityP9sqlnq_pidS0_sR17sqlnq_qunElemListRiS 
3_P9sqlnq_sat22sqlnd_pid_Context_Flag + 0x009e 
      (/home/db2inst1/sqllib/lib64/libdb2e.so.1) 
0x00002AAAAD23C64F 
_Z20sqlnd_inlist_pad_pdaP9sqlnq_expP9sqlnq_pidR17sqlnq_qunElemLi 
stiRiRS2_P9sqlnq_sat + 0x215f 
      (/home/db2inst1/sqllib/lib64/libdb2e.so.1) 
0x00002AAAAD2157EB 
_Z20sqlnd_exp_qunset_pdaP9sqlnq_expP9sqlnq_pidR17sqlnq_qunElemLi 
stiRiRS2_P9sqlnq_sat + 0xb755 
      (/home/db2inst1/sqllib/lib64/libdb2e.so.1) 
0x00002AAAAD203907 
_Z21sqlnd_prd_qun_vis_pdaP9sqlnq_prdP9sqlnq_qun + 0x0a73 
      (/home/db2inst1/sqllib/lib64/libdb2e.so.1) 
0x00002AAAAD1ECB3D 
_Z27sqlnd_oprprd_qunset_vis_pdaP9sqlnq_oprR17sqlnq_qunElemList + 
0x0273 
      (/home/db2inst1/sqllib/lib64/libdb2e.so.1) 
0x00002AAAAD1DDF29 _Z13sqlnd_opr_pdaRP9sqlnq_oprRiRP9sqlnq_sati 
+ 0x0421 
      (/home/db2inst1/sqllib/lib64/libdb2e.so.1) 
0x00002AAAAD1DD403 _Z13sqlnd_qtb_pdaRP9sqlnq_qtbS1_ii + 0x0d33 
      (/home/db2inst1/sqllib/lib64/libdb2e.so.1) 
0x00002AAAAD1DC633 _Z13sqlnd_qtb_pdaRP9sqlnq_qtbi + 0x00a7 
      (/home/db2inst1/sqllib/lib64/libdb2e.so.1) 
0x00002AAAAD1DB0C6 _Z17sqlnd_qtb_pda_qrwP9sqlnq_qtb + 0x0176 
      (/home/db2inst1/sqllib/lib64/libdb2e.so.1) 
0x00002AAAAE1044F9 
_Z21sqlnr_sel_mrg_precondP9sqlnq_qtbP9sqlnq_qunPi + 0x0823 
      (/home/db2inst1/sqllib/lib64/libdb2e.so.1) 
0x00002AAAAE104D83 
_Z18sqlnr_sel_mrg_condP14sqlnr_progressP10sqlnr_qrwaPi + 0x00ff 
      (/home/db2inst1/sqllib/lib64/libdb2e.so.1)
Problem Summary:
User affected: 
  Users who use  InfoSphere Federation Server 
Problem description and summay: 
  See error description
Local Fix:


available fix packs:


DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
 


Solution


Problem was fistly fixed in Version 10.1, FixPak 3. This 
fix should be applied on the federation Server.


Workaround


not known / see Local fix


Timestamps


Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

22.04.2013
21.10.2013
21.10.2013


Problem solved at the following versions (IBM BugInfos)




Problem solved according to the fixlist(s) of the following version(s)


10.1.0.3

FixList



10.1.0.3

FixList