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

SQL0901N "BAD IXM LISTOF" RETURNED WHEN RUNNING DB2ADVIS

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
When doing advise indexes on the table that has partitioning 
predicate ,  you may got -901 'bad ixm LISTOF' error , and the 
following stack information can also been find in db2diag.log 
file . 
Compiler error stack for rc = -2144272209: 
sqlnn_cmpl[420] 
sqlng_main[2791] 
sqlng_main[1657] 
sqlng_build_thread[10] 
sqlng_process_return_op[50] 
sqlng_process_pipe_op[30] 
sqlng_process_mate_op[1735] 
sqlng_process_delete_op[10] 
sqlng_process_pipe_op[30] 
sqlng_process_mate_op[1735] 
sqlng_process_mergejoin_op[30] 
sqlng_build_thread[10] 
sqlng_process_iscan_op[38] 
sqlng_build_TA_op[400] 
sqlng_handle_PBT_in_build_[100] 
sqlng_build_PBT_op[10] 
sqlng_build_PBT_obj[800] 
sqlng_build_PBT_IDX_ARRAYS[110] 
Besides , you can also get  the following stack information for 
 the problematic EDU 
<StackTrace> 
-------Frame------ ------Function + Offset------ 
0x09000000005CAC54 pthread_kill + 0xD4 
0x090000000370CF88 sqloDumpEDU + 0x74 
0x090000000370DE4C sqldDumpContext__FP8sqeAgentiN42PCcPvT2 + 
0x11C 
0x090000000370DC64 
sqldDumpContext__FP8sqeAgentiN42PCcPvT2@glueABB + 0x94 
0x0900000003A3FE8C sqlrr_dump_ffdc__FP8sqlrr_cbiT2 + 0x350 
0x0900000002EE020C sqlzeDumpFFDC__FP8sqeAgentUiP5sqlcai + 0x24 
0x0900000002EDFFB8 sqlzeSqlCode__FP8sqeAgentUiUlT2P5sqlcaiUsPc 
+ 0x120 
0x0900000002EDFCCC sqlnn_erds__FiN41e + 0x124 
0x0900000004A780C0 
sqlng_build_PBT_IdxArrays__FP9sqlng_blkP14sqlng_scan_blkP9sqlri_ 
taoP11sqlriPBTObj + 0xD10 
0x0900000004A743D8 
sqlng_build_PBT_obj__FP9sqlng_blkP14sqlng_scan_blkUlP9sqlri_taoP 
10sqlri_iudoPP11sqlriPBTObj + 0x8C8 
0x0900000004A739BC 
sqlng_build_PBT_op__FP9sqlng_blkP14sqlng_scan_blkUlP9sqlri_taoP1 
0sqlri_iudo + 0xAC 
0x0900000004A7B334 
sqlng_handle_PBT_in_build_TA_op__FP9sqlng_blkP14sqlng_scan_blkP9 
sqlri_taoT3 + 0x538 
0x0900000003F7E52C 
sqlng_build_TA_op__FP9sqlng_blkP14sqlng_scan_blkP9sqlno_qtb + 
0x205C 
0x0900000003F9E7CC 
sqlng_process_iscan_op__FP9sqlng_blkP19sqlno_plan_operator + 
0x63C 
0x0900000003F562B4 
sqlng_build_thread__FP9sqlng_blkP14sqlng_thd_ctrl + 0x158 
0x0900000003F989A8 
sqlng_process_mergeJoin_op__FP9sqlng_blkP19sqlno_plan_operator 
+ 0x488 
0x0900000003FA6EDC 
sqlng_process_mate_op__FP9sqlng_blkP19sqlno_plan_operator + 
0x480 
0x0900000003FAE53C 
sqlng_process_pipe_op__FP9sqlng_blkP19sqlno_plan_operator + 
0x368 
0x090000000450E30C 
sqlng_process_delete_op__FP9sqlng_blkP19sqlno_plan_operator + 
0x374 
0x0900000003FA6EDC 
sqlng_process_mate_op__FP9sqlng_blkP19sqlno_plan_operator + 
0x480 
0x0900000003FAE53C 
sqlng_process_pipe_op__FP9sqlng_blkP19sqlno_plan_operator + 
0x368 
0x0900000003FAEFC8 
sqlng_process_return_op__FP9sqlng_blkP19sqlno_plan_operator + 
0x854 
0x0900000003F562B4 
sqlng_build_thread__FP9sqlng_blkP14sqlng_thd_ctrl + 0x158 
0x0900000004A2D994 sqlng_main__FP9sqlnq_qur + 0x21A4 
0x0900000004A644A0 sqlng_main__FP9sqlnq_qur@glue1255 + 0x70 
0x090000000281A454 
sqlnn_cmpl__FP8sqeAgentP11sqlrrstrings17sqlnn_compileModeT3P14sq 
lrr_cmpl_enviT7PP9sqlnq_qur + 0x2A98 
0x0900000002ECF800 
sqlnn_cmpl__FP8sqeAgentP11sqlrrstrings17sqlnn_compileModeT3P14sq 
lrr_cmpl_env + 0x24 
0x0900000002E755C4 
sqlra_compile_var__FP8sqlrr_cbP14sqlra_cmpl_envPUciUsN54P16sqlra 
_cached_varPiPUl + 0x610 
0x0900000002E74240 
sqlra_find_var__FP8sqlrr_cbP17sqlra_cached_stmt13sqlra_stmt_idUi 
T4PUcT4UsUcP14sqlra_cmpl_enviPiT11_T12_N311_T12_P14SQLP_LOCK_INF 
OPP16sqlra_cached_varT12_PUlb + 0x404 
0x0900000002E73CAC sqlra_get_var__FP8sqlrr_cbiT2bPbT5 + 0x444 
0x0900000003323728 
sqlrr_prepare__FP14db2UCinterfaceP16db2UCprepareInfo + 0x138 
0x0900000002DDDFF8 
sqljs_ddm_prpsqlstt__FP14db2UCinterfaceP13sqljDDMObject + 0xAF0 
0x090000000290EEB4 
sqljsParseRdbAccessed__FP13sqljsDrdaAsCbP13sqljDDMObjectP14db2UC 
interface + 0x10C 
0x0900000002F76DE0 
sqljsParse__FP13sqljsDrdaAsCbP14db2UCinterface - 0x124 
0x0900000002F78730 
@63@sqljsSqlam__FP14db2UCinterfaceP8sqeAgentb + 0x1D8 
0x09000000030F6558 
@63@sqljsDriveRequests__FP8sqeAgentP14db2UCconHandle + 0x98 
0x09000000030F63C8 
@63@sqljsDrdaAsInnerDriver__FP18SQLCC_INITSTRUCT_Tb + 0xE0 
0x09000000030F613C sqljsDrdaAsDriver__FP18SQLCC_INITSTRUCT_T + 
0xD8 
0x09000000030F7E00 RunEDU__8sqeAgentFv + 0x11C 
0x0900000003102748 EDUDriver__9sqzEDUObjFv + 0x78 
0x090000000308F550 sqloEDUEntry + 0x57C 
</StackTrace> 
The issue can only occur when db2advis is used in conjunction 
with a UNION ALL that is eligible for parameterization .
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Anyone affected by the issue                                 * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* upgrade to db2_v105fp7                                       * 
****************************************************************
Local Fix:
Turning off union parameterization with following command to 
address this problem: 
db2set DB2_UNION_OPTIMIZATION="PARAMETERIZE OFF" 
db2stop 
db2start
Solution
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
09.07.2015
21.01.2016
21.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