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

DATABASE MAY ABEND DURING A MERGE STATEMENT IF SOURCE COLUMNS ARE MARKED AS
IMPLICITLY HIDDEN

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
If the source table has ROW CHANGE TIMESTAMP columns which are 
marked as IMPLICITLY HIDDEN then performing a merge query might 
lead to database crash with the following stack trace: 
 
Windows: 
<StackTrace> 
 
<![CDATA[ 
 
--EBP------EIP------ARGS----------------------------- 
 
044668D8 6D662F97 00000000 54B4F234 55330060 54B4F228 offset: 
00000003 
in <?op@sqlnq_attattdpparent@@QAEPAVsqlnq_atd@@XZ> 
 
<T:/db2_v95fp6/nt32/s100918/engn/include/sqlnq_reldef.h:1377> 
 
04466A9C 6D9BF11C 553A031C 00000003 00000711 553A9400 offset: 
0000258E 
in 
<?sqlnq_sem_merge@@YAHQAPAUstknode_@@HW4actiontype@@PAEPAVloc@@@ 
Z> 
 
<sqlnq_sem_merge.C:2211> 
 
04466AEC 6D7E3BE4 553A0220 000007E4 00000020 00000001 offset: 
00000544 
in <?sqlnp_smactn@@YAHPAUsqlnp_cb@@H@Z> <sqlnp_prs.C:655> 
 
04466B58 6D7E2E89 553A0220 0365093C 4CD32BF2 0008A6D8 offset: 
000001CF 
in <?sqlnp_parser@@YAHPAUsqlnp_cb@@@Z> 
 
<T:/db2_v95fp6/nt32/s100918/engn/sqnp/inc/sqlnp_lpgprse.h:1031> 
 
04466BA8 6D7DEF83 044680B0 00000001 044680F4 20202020 offset: 
000002D7 
in <?sqlnp_main@@YAHPAVsqlnq_string@@FPAPAVsqlnq_qur@@@Z> 
 
<sqlnp_main.C:455> 
 
044681BC 6D6AA67D 7B0AA3E0 04468D44 00000001 00000002 offset: 
00000861 
in<?sqlnn_cmpl@@YAHPAVsqeAgent@@PAUsqlrrstring@@FW4sqlnn_compile 
Mode@@FPAU 
 
sqlrr_cmpl_env@@HHPAPAVsqlnq_qur@@@Z> <sqlnn_cmpl.C:2518> 
 
044681E8 6D6A9E14 7B0AA3E0 04468D44 00000001 00000002 offset: 
00000024 
in<?sqlnn_cmpl@@YAHPAVsqeAgent@@PAUsqlrrstring@@FW4sqlnn_compile 
Mode@@FPAU 
 
sqlrr_cmpl_env@@@Z> <sqlnn_cmpl.C:498> 
 
04468DB8 6DD9FDA6 5515DFB0 54AD2AC0 5570FE40 00000185 offset: 
000005E2 
in<?sqlra_compile_var@@YAHPAUsqlrr_cb@@PAUsqlra_cmpl_env@@PAEHGH 
HHHHPAUsql 
 
ra_cached_var@@PAHPA_K@Z> <sqlra_cmpl.C:955> 
 
04469790 6DDA3E9D 5515DFB0 55A680B0 00000000 00000000 offset: 
00000449 
in<?sqlra_find_var@@YAHPAUsqlrr_cb@@PAUsqlra_cached_stmt@@Usqlra 
_stmt_id@@ 
 
IIPAEIGEPAUsqlra_cmpl_env@@HPAHH5HHH5PAUSQLP_LOCK_INFO@@PAPAUsql 
ra_cached_var@@5PA_K_N@Z> 
<sqlra_dyn.C:3509> 
04469EA8 6DDADDD0 5515DFB0 00000001 00000000 00000000 offset: 
000004B6 
in <?sqlra_get_var@@YAHPAUsqlrr_cb@@HH_NPA_N2@Z> 
<sqlra_var.C:589> 
04469F48 6DD45E75 5515DFB0 00000000 545E07F4 545E0060 offset: 
000000D7 
in <?sqlrr_execute_immediate@@YAHPAUsqlrr_cb@@H@Z> 
<sqlrr_sql.C:1798> 
04469F78 6DCC7D1E 5608FDD0 5608FDD0 00000001 0000002F offset: 
00000112 
in <?sqlrr_execimmd@@YAHPAUdb2UCinterface@@@Z> 
<sqlrr_req_sql.C:3224> 
0446A02C 6D56E13B 5608FDD0 0446A0DC 7B0BFC90 0446A074 offset: 
00000811 
in 
<?sqljs_ddm_excsqlimm@@YAHPAUdb2UCinterface@@PAUsqljDDMObject@@@ 
Z> 
 
<sqljsexe.C:1983> 
 
0446A08C 6D561468 545E07F4 00000355 00000000 7B0BFC90 offset: 
0000020C 
in<?sqljsParseRdbAccessed.@@YAHPAUsqljsDrdaAsCb@@PAUsqljDDMObjec 
t@@PAUdb2UCinterface@@@Z> 
<sqljspar.C:410> 
 
On Unix: 
 
<StackTrace> 
--Frame--- ------Function + Offset------ 
0x17CF54A8 _ZN17sqlnq_fcsqclchild2ppEv + 0x0006 
                (/home/dbguest3/sqllib/lib32/libdb2e.so.1) 
0x17CF5674 _Z15sqlnq_sem_mergePP8stknode_i10actiontypePhP3loc + 
0x286b 
                (/home/dbguest3/sqllib/lib32/libdb2e.so.1) 
0x17CF56B4 _Z12sqlnp_smactnP8sqlnp_cbi + 0x0480 
                (/home/dbguest3/sqllib/lib32/libdb2e.so.1) 
0x17CF5724 _Z12sqlnp_parserP8sqlnp_cb + 0x01f8 
                (/home/dbguest3/sqllib/lib32/libdb2e.so.1) 
0x17CF5784 _Z10sqlnp_mainP12sqlnq_stringsPP9sqlnq_qur + 0x036a 
                (/home/dbguest3/sqllib/lib32/libdb2e.so.1) 
0x17CF6DB0 
_Z10sqlnn_cmplP8sqeAgentP11sqlrrstrings17sqlnn_compileModesP14sq 
lrr_cmpl_enviiPP9sqlnq_qur 
+ 0x09b8 
                (/home/dbguest3/sqllib/lib32/libdb2e.so.1) 
0x17CF6DEC 
_Z10sqlnn_cmplP8sqeAgentP11sqlrrstrings17sqlnn_compileModesP14sq 
lrr_cmpl_env 
+ 0x0034 
                (/home/dbguest3/sqllib/lib32/libdb2e.so.1) 
0x17CF7910 
_Z17sqlra_compile_varP8sqlrr_cbP14sqlra_cmpl_envPhitiiiiiP16sqlr 
a_cached_varPiPy 
+ 0x05bf 
                (/home/dbguest3/sqllib/lib32/libdb2e.so.1) 
0x17CF82D0 
_Z14sqlra_find_varP8sqlrr_cbP17sqlra_cached_stmt13sqlra_stmt_idj 
jPhjthP14sqlra_cmpl_enviPiiS7_iiiS7_P14SQLP_LOCK_INFOPP16sqlra_c 
ached_varS7_Pyb 
+ 0x03c4 
                (/home/dbguest3/sqllib/lib32/libdb2e.so.1) 
0x17CF89F0 _Z13sqlra_get_varP8sqlrr_cbiibPbS1_ + 0x047b 
                (/home/dbguest3/sqllib/lib32/libdb2e.so.1) 
0x17CF8A74 _Z23sqlrr_execute_immediateP8sqlrr_cbi + 0x1235 
                (/home/dbguest3/sqllib/lib32/libdb2e.so.1) 
0x17CF8AAC _Z14sqlrr_execimmdP14db2UCinterface + 0x0340 
 
(...)
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Customer using a MERGE with implicitly hidden columns        * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* If the source table has ROW CHANGE TIMESTAMP columns which   * 
* are marked as IMPLICITLY HIDDEN then performing a merge      * 
* query might lead to database crash.                          * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to V9.7 fixpack 5 or later                           * 
****************************************************************
Local Fix:
Reverse the order of processing with UPDATE operation before 
INSERT operation. The workaround might not work if there is no 
UPDATE clause in the matching condition.
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
This problem was first fixed in V9.7 Fixpack 5
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
23.03.2011
20.01.2012
20.01.2012
Problem solved at the following versions (IBM BugInfos)
9.7.FP5
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.5 FixList