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

UPDATE TO COLUMNAR TABLE CAN SOMETIMES LEAD TO DB2 CRASH

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
Update to columnar table can sometimes lead to DB2 crash 
 
The following will be seen in the trap diagnostics: 
 
</Siginfo_t> 
Signal #11 (SIGSEGV): si_addr is 0x0000000000000008, si_code is 
0x00000001 (SEGV_MAPERR:Address not mapped to object.) 
</SignalDetails> 
 
<POFDisassembly> 
 
_ZN7ibm_cde5query21LoadColValueEvaluator20cdeFastLoadColValueTIN 
S_5types7IntegerIlLb0EEEEEvmPKNS_4data13TableAccessorEPKNS6_6Col 
umnERKNS3_22TypeAllocatorResourcesERbP10sqlz_valuePPNS3_10ValUnc 
odedE + 0x026d 
(/db2/home/db2inst1/sqllib/lib64/libdb2e.so.1) 
 
    0x00007FB4CDE363ED : 498B4608458B6604 
</POFDisassembly> 
<StackTrace> 
-----FUNC-ADDR---- ------FUNCTION + OFFSET------ 
0x00007FB4CB6AB205 
_Z25ossDumpStackTraceInternalmR11OSSTrapFileiP7siginfoPvmm + 
0x0385 
        (/db2/home/db2inst1/sqllib/lib64/libdb2osse.so.1) 
0x00007FB4CB6AAE0C ossDumpStackTraceV98 + 0x002c 
        (/db2/home/db2inst1/sqllib/lib64/libdb2osse.so.1) 
0x00007FB4CB6A5F0D _ZN11OSSTrapFile6dumpExEmiP7siginfoPvm + 
0x00fd 
        (/db2/home/db2inst1/sqllib/lib64/libdb2osse.so.1) 
0x00007FB4D1B4A964 sqlo_trce + 0x0404 
        (/db2/home/db2inst1/sqllib/lib64/libdb2e.so.1) 
0x00007FB4D1B9FE9A sqloEDUCodeTrapHandler + 0x027a 
        (/db2/home/db2inst1/sqllib/lib64/libdb2e.so.1) 
0x000000380720F710 address: 0x000000380720F710 ; dladdress: 
0x0000003807200000 ; offset in lib: 0x000000000000F710 ; 
        (/lib64/libpthread.so.0) 
0x00007FB4CDE363ED 
_ZN7ibm_cde5query21LoadColValueEvaluator20cdeFastLoadColValueTIN 
S_5types7IntegerIlLb0EEEEEvmPKNS_4data13TableAccessorEPKNS6_6Col 
umnERKNS3_22TypeAllocatorResourcesERbP10sqlz_valuePPNS3_10ValUnc 
odedE + 0x026d 
        (/db2/home/db2inst1/sqllib/lib64/libdb2e.so.1) 
0x00007FB4D0EC70E2 
_ZN7ibm_cde5query21LoadColValueEvaluator19cdeFastLoadColValueEmP 
KNS_4data13TableAccessorEPKNS2_6ColumnERKNS_5types22TypeAllocato 
rResourcesERbP10sqlz_valuePPNS9_10ValUncodedE + 0x0152 
        (/db2/home/db2inst1/sqllib/lib64/libdb2e.so.1) 
0x00007FB4D0E91CE5 _ZN25cdeTableAccessorInterface6getPRTEmPm + 
0x0095 
        (/db2/home/db2inst1/sqllib/lib64/libdb2e.so.1) 
0x00007FB4D0E84114 _ZN12cdeInterface6getPRTEmPm + 0x00b4 
        (/db2/home/db2inst1/sqllib/lib64/libdb2e.so.1) 
0x00007FB4D28579FE address: 0x00007FB4D28579FE ; dladdress: 
0x00007FB4CBBC8000 ; offset in lib: 0x0000000006C8F9FE ; 
        (/db2/home/db2inst1/sqllib/lib64/libdb2e.so.1) 
0x00007FB4D2857D25 address: 0x00007FB4D2857D25 ; dladdress: 
0x00007FB4CBBC8000 ; offset in lib: 0x0000000006C8FD25 ; 
        (/db2/home/db2inst1/sqllib/lib64/libdb2e.so.1) 
0x00007FB4D285A641 address: 0x00007FB4D285A641 ; dladdress: 
0x00007FB4CBBC8000 ; offset in lib: 0x0000000006C92641 ; 
        (/db2/home/db2inst1/sqllib/lib64/libdb2e.so.1) 
0x00007FB4D2BFFF60 address: 0x00007FB4D2BFFF60 ; dladdress: 
0x00007FB4CBBC8000 ; offset in lib: 0x0000000007037F60 ; 
        (/db2/home/db2inst1/sqllib/lib64/libdb2e.so.1) 
0x00007FB4D2BFDF22 _Z8sqlischfP7SQLI_CBtj + 0x1122 
        (/db2/home/db2inst1/sqllib/lib64/libdb2e.so.1) 
0x00007FB4D2BEE0F7 
_Z7sqlirdkP8sqeAgentP10SQLI_IXPCRP9SQLD_IXCBmP8SQLD_KEYP12SQLI_K 
EYDATAP9sqli_scanPi + 0x07e7 
        (/db2/home/db2inst1/sqllib/lib64/libdb2e.so.1) 
0x00007FB4D2A67BAB _Z14sqldIndexFetchP8SQLD_CCBP8SQLZ_RID + 
0x013b 
        (/db2/home/db2inst1/sqllib/lib64/libdb2e.so.1) 
0x00007FB4D2A656F8 
_Z12sqldRowFetchP8sqeAgentP8SQLD_CCBmmPP10SQLD_VALUEP8SQLZ_RIDmP 
12SQLD_ID_LISTP9SQLP_LSN8 + 0x0588 
        (/db2/home/db2inst1/sqllib/lib64/libdb2e.so.1) 
0x00007FB4D2BA8B51 _Z17sqlritaSimplePermP8sqlrr_cb + 0x00d1 
        (/db2/home/db2inst1/sqllib/lib64/libdb2e.so.1) 
0x00007FB4D2B9F6B7 _Z15sqlriSectInvokeP8sqlrr_cbP12sqlri_opparm 
+ 0x01b7 
        (/db2/home/db2inst1/sqllib/lib64/libdb2e.so.1) 
0x00007FB4CFE1E803 _Z23sqlrr_execute_immediateP8sqlrr_cbi + 
0x0553 
        (/db2/home/db2inst1/sqllib/lib64/libdb2e.so.1) 
0x00007FB4CFE0FD0F 
_Z14sqlrr_execimmdP14db2UCinterfaceP16db2UCprepareInfo + 0x012f 
        (/db2/home/db2inst1/sqllib/lib64/libdb2e.so.1) 
0x00007FB4CEFB35A2 
_Z19sqljs_ddm_excsqlimmP14db2UCinterfaceP13sqljDDMObject + 
0x0552 
        (/db2/home/db2inst1/sqllib/lib64/libdb2e.so.1) 
0x00007FB4D2AC4C76 
_Z21sqljsParseRdbAccessedP13sqljsDrdaAsCbP13sqljDDMObjectP14db2U 
Cinterface + 0x03f6 
        (/db2/home/db2inst1/sqllib/lib64/libdb2e.so.1) 
0x00007FB4CEF8ED2B 
_Z10sqljsParseP13sqljsDrdaAsCbP14db2UCinterfaceP8sqeAgentb + 
0x036b 
        (/db2/home/db2inst1/sqllib/lib64/libdb2e.so.1) 
0x00007FB4CEF88BBD address: 0x00007FB4CEF88BBD ; dladdress: 
0x00007FB4CBBC8000 ; offset in lib: 0x00000000033C0BBD ; 
        (/db2/home/db2inst1/sqllib/lib64/libdb2e.so.1) 
0x00007FB4CEF87079 address: 0x00007FB4CEF87079 ; dladdress: 
0x00007FB4CBBC8000 ; offset in lib: 0x00000000033BF079 ; 
        (/db2/home/db2inst1/sqllib/lib64/libdb2e.so.1) 
0x00007FB4CEF840E9 address: 0x00007FB4CEF840E9 ; dladdress: 
0x00007FB4CBBC8000 ; offset in lib: 0x00000000033BC0E9 ; 
        (/db2/home/db2inst1/sqllib/lib64/libdb2e.so.1) 
0x00007FB4CEF83CDB _Z17sqljsDrdaAsDriverP18SQLCC_INITSTRUCT_T + 
0x00eb 
        (/db2/home/db2inst1/sqllib/lib64/libdb2e.so.1) 
0x00007FB4CEC8A9D0 _ZN8sqeAgent6RunEDUEv + 0x0cb0 
        (/db2/home/db2inst1/sqllib/lib64/libdb2e.so.1) 
0x00007FB4D044FEF7 _ZN9sqzEDUObj9EDUDriverEv + 0x00f7 
        (/db2/home/db2inst1/sqllib/lib64/libdb2e.so.1) 
0x00007FB4CFC37741 sqloEDUEntry + 0x0301 
        (/db2/home/db2inst1/sqllib/lib64/libdb2e.so.1) 
0x00000038072079D1 address: 0x00000038072079D1 ; dladdress: 
0x0000003807200000 ; offset in lib: 0x00000000000079D1 ; 
        (/lib64/libpthread.so.0) 
0x0000003806EE8B6D clone + 0x006d 
        (/lib64/libc.so.6) 
</StackTrace>
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All users of column-organized tables                         * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 10.5.0.7.                             * 
****************************************************************
Local Fix:


Solution


The problem is first fixed in DB2 version 10.5.0.7.


Workaround


not known / see Local fix


Timestamps


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

20.07.2015
20.01.2016
20.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