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

DB2 CAN TRAP IN SQLNO_ZZ_STARJN_COMPUTE_INDEX_QUNS_REFD

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
DB2 can trap when compiling an SQL statement that meets all of 
the 
conditions below: 
 
(1) The query fits the required criteria for zigzag join. Refer 
to the topic "Ensuring that queries fit the required criteria 
for the zigzag join" in DB2 InfoCentre for details about the 
criteria. 
(2) The fact table has an XML column, and there is an XML index 
on the XML column. 
 
The stack can look like the following: 
 
sqlno_zz_starjn_compute_index_quns_refd__FP13sqlno_globalsP9sqln 
o_qtbP10sqlno_apcbP11sqlno_tableiP24sqlno_zz_starjn_qun_infoP9sq 
lnq_attP10sqlno_isetUiT5P16sqlno_listheader + 0x29C 
sqlno_zz_starjn_compute_fact_indexes__FCP13sqlno_globalsCP9sqlno 
_qtbCP10sqlno_apcbC9sqlno_setCbP9sqlno_setP24sqlno_zz_starjn_qun 
_infoPb + 0x988 
sqlno_zz_starjn_compute_star__FCP13sqlno_globalsCP9sqlno_qtbCP10 
sqlno_apcbCPP22sqlno_adjacency_matrixCbT5C9sqlno_setCP24sqlno_zz 
_starjn_qun_infoCP9sqlno_setT9T8CPb + 0x4DC 
sqlno_zz_starjn_init__FCP13sqlno_globalsCP9sqlno_qtb + 0x310 
sqlno_prop_compute_ff_adjustments__FP13sqlno_globalsP9sqlno_qtb 
+ 0x1E8 
sqlno_plan_begin_opr__FP13sqlno_globalsP9sqlno_sfbP9sqlnq_opr + 
0x3C8 
sqlno_each_opr__FP13sqlno_globalsP9sqlno_sfbP9sqlnq_qunP9sqlnq_o 
pr + 0x230 
sqlno_walk_qun__FP13sqlno_globalsP9sqlno_sfbP9sqlnq_oprP9sqlnq_q 
un + 0x124 
sqlno_each_opr__FP13sqlno_globalsP9sqlno_sfbP9sqlnq_qunP9sqlnq_o 
pr + 0x42C 
sqlno_walk_qun__FP13sqlno_globalsP9sqlno_sfbP9sqlnq_oprP9sqlnq_q 
un + 0x124 
sqlno_each_opr__FP13sqlno_globalsP9sqlno_sfbP9sqlnq_qunP9sqlnq_o 
pr + 0x42C 
sqlno_walk_qun__FP13sqlno_globalsP9sqlno_sfbP9sqlnq_oprP9sqlnq_q 
un + 0x124 
sqlno_each_opr__FP13sqlno_globalsP9sqlno_sfbP9sqlnq_qunP9sqlnq_o 
pr + 0x42C 
sqlno_walk_qun__FP13sqlno_globalsP9sqlno_sfbP9sqlnq_oprP9sqlnq_q 
un + 0x124 
sqlno_each_opr__FP13sqlno_globalsP9sqlno_sfbP9sqlnq_qunP9sqlnq_o 
pr + 0x42C 
sqlno_walk_qun__FP13sqlno_globalsP9sqlno_sfbP9sqlnq_oprP9sqlnq_q 
un + 0x124 
sqlno_each_opr__FP13sqlno_globalsP9sqlno_sfbP9sqlnq_qunP9sqlnq_o 
pr + 0x42C 
sqlno_walk_qun__FP13sqlno_globalsP9sqlno_sfbP9sqlnq_oprP9sqlnq_q 
un + 0x124 
sqlno_each_opr__FP13sqlno_globalsP9sqlno_sfbP9sqlnq_qunP9sqlnq_o 
pr + 0x42C 
sqlno_walk_qun__FP13sqlno_globalsP9sqlno_sfbP9sqlnq_oprP9sqlnq_q 
un + 0x124 
sqlno_each_opr__FP13sqlno_globalsP9sqlno_sfbP9sqlnq_qunP9sqlnq_o 
pr + 0x42C 
sqlno_top_qtb__FP13sqlno_globalsP9sqlno_sfbP9sqlnq_qurP9sqlnq_qt 
b + 0x104 
sqlno_each_qur__FP13sqlno_globalsP9sqlno_sfbP9sqlnq_qurT3 + 
0x2DC 
sqlno_scan_qgm__FP13sqlno_globalsP9sqlno_sfbP9sqlnq_qur + 0x2B8 
sqlno_planning_scan__FP13sqlno_globalsP9sqlnq_quri + 0xC0 
sqlno_planning_phase__FP13sqlno_globalsP9sqlnq_quriT3 + 0xC44 
sqlno_exe__FP9sqlnq_qur + 0x7FC 
sqlnn_cmpl__FP8sqeAgentP11sqlrrstrings17sqlnn_compileModeT3P14sq 
lrr_cmpl_enviT7PP9sqlnq_qur + 0x188 
sqlnn_cmpl__FP8sqeAgentP11sqlrrstrings17sqlnn_compileModeT3P14sq 
lrr_cmpl_env + 0x28 
sqlrr_cmpl__FP8sqlrr_cbP11sqlrrstrings17sqlnn_compileModeUcP5sql 
daPiPUiPP9sqlri_shdP11compileInfo + 0x5EC 
sqlrr_compile__FP14db2UCinterfaceP11compileInfo + 0x964 
addStatement__13psmPackageGenFPciT2P18psmPackageVariableT2RUs + 
0x380 
makeSection__14psmQueryStringFP19psmPVMCodeGeneratoriUsR12pvmQue 
ryDesc + 0x280 
generate__19psmPVMCodeGeneratorFP23psm_DECLARE_CURSOR_node + 
0x32C 
generate__27@75@psm_DECLARE_CURSOR_nodeFP16psmCodeGenerator + 
0x70 
generate__19psmPVMCodeGeneratorFP14psm_block_node + 0x2AC 
generate__18@75@psm_block_nodeFP16psmCodeGenerator + 0x70 
generate__19psmPVMCodeGeneratorFP18psm_procedure_node + 0x2A0 
generate__22@75@psm_procedure_nodeFP16psmCodeGenerator + 0x70 
genProgram__19psmPVMCodeGeneratorFP10psmProgram + 0x3CC 
psm_generate_PVM__8psm_ctrlFv + 0x27C 
psm_gen_program__FP8psm_ctrl + 0x82C 
sqlnq_create_proc_end__FP12sqlnq_string + 0x62C 
sqlnq_proc_create_stmt__FPP8stknode_i10actiontypePUcP3loc + 
0xCA0 
sqlnp_smactn__FP8sqlnp_cbi + 0x134 
sqlnp_parser__FP8sqlnp_cb + 0x4FC 
sqlnp_main__FP12sqlnq_stringbP3locPP9sqlnq_qur + 0x258 
sqlnn_cmpl__FP8sqeAgentP11sqlrrstrings17sqlnn_compileModeT3P14sq 
lrr_cmpl_enviT7PP9sqlnq_qur + 0x560 
sqlnn_cmpl__FP8sqeAgentP11sqlrrstrings17sqlnn_compileModeT3P14sq 
lrr_cmpl_env + 0x28 
sqlra_compile_var__FP8sqlrr_cbP14sqlra_cmpl_envPUciUsN54P14SQLP_ 
LOCK_INFOP16sqlra_cached_varPi + 0x778 
sqlra_find_var__FP8sqlrr_cbP17sqlra_cached_stmt13sqlra_stmt_idUi 
T4PUcT4UsUcP14sqlra_cmpl_env15sqlra_fill_modePiiT12_N313_T12_P14 
SQLP_LOCK_INFOPP16sqlra_cached_varT12_b + 0x8AC 
sqlra_get_var__FP8sqlrr_cbiT2bPbT5 + 0x1A20 
sqlri_ddl_get_section__FP8sqlrr_cb + 0x68 
sqlri_ddl_common__FP8sqlrr_cb + 0x474 
sqlriddl__FP8sqlrr_cb + 0x38 
sqlriSectInvoke__FP8sqlrr_cbP12sqlri_opparm + 0x24 
sqlrr_execute_immediate__FP8sqlrr_cbi + 0x4F8 
sqlrr_execimmd__FP14db2UCinterfaceP16db2UCprepareInfo + 0x4E8 
sqljs_ddm_excsqlimm__FP14db2UCinterfaceP13sqljDDMObject + 0xDB8 
sqljsParseRdbAccessed__FP13sqljsDrdaAsCbP13sqljDDMObjectP14db2UC 
interface + 0x3C 
.sqljsParse.fdpr.clone.102__FP13sqljsDrdaAsCbP14db2UCinterfaceP8 
sqeAgentb + 0x13A4 
@73@sqljsSqlam__FP14db2UCinterfaceP8sqeAgentb + 0x280 
@73@sqljsDriveRequests__FP8sqeAgentP14db2UCconHandle + 0xB4 
@73@sqljsDrdaAsInnerDriver__FP18SQLCC_INITSTRUCT_Tb + 0x4E8 
sqljsDrdaAsDriver__FP18SQLCC_INITSTRUCT_T + 0x21C 
RunEDU__8sqeAgentFv + 0x584 
EDUDriver__9sqzEDUObjFv + 0x13C 
sqlzRunEDU__FPcUi + 0x10 
sqloEDUEntry + 0x264
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version  10.1 Fix Pack 3.                     * 
****************************************************************
Local Fix:
db2set DB2_REDUCED_OPTIMIZATION="STAR_DETECTION IXA_ONLY"
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
First fixed in DB2 Version  10.1 Fix Pack 3.
Workaround
See Local Fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC95445 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
18.03.2013
01.10.2013
01.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