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

DB2 MIGHT PRODUCE SQL0901N WHEN EXECUTING QUERY WITH SINGLE SUBTERM INLIST

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
Under rare scenarios, DB2 might fail with SQL0901N error message 
when the following conditions are true: 
1) The query contains one or more IN predicate 
2) Atleast one of the IN predicate is of type Col IN (CONST) 
 
eg. 
SELECT 1 
FROM TEMP_TABLE D 
WHERE D.TYPE IN ( VALUES ('abc') ); 
 
<StackTrace> 
-------Frame------ ------Function + Offset------ 
0x090000000055BF94 pthread_kill + 0xD4 
0x0900000003067474 sqloDumpEDU + 0xA4 
0x0900000003339CB4 sqldDumpContext__FP9sqeBsuEduiN42PCcPvT2 + 
0xCC 
0x09000000036AD294 
sqldDumpContext__FP9sqeBsuEduiN42PCcPvT2@glue5BB + 0x98 
0x0900000003232AE0 sqlrr_dump_ffdc__FP8sqlrr_cbiT2 + 0x320 
0x09000000058507D0 sqlzeDumpFFDC__FP8sqeAgentUiP5sqlcai + 0x50 
0x0900000003533870 sqlzeSqlCode__FP8sqeAgentUiUlT2P5sqlcaiUsPc + 
0x240 
0x0900000004E8E84C sqlnn_erds__FiN41e + 0x33C 
0x0900000003E6D7F4 
sqlng_build_INDX_key__FP9sqlng_blkP14sqlng_scan_blkP13sqlno_keyc 
ondT3P10sqlz_valueT5PUlT7PP16sqlriIXKeyUpdateT9PUc + 0xB40 
0x0900000006DE8D64 
sqlng_build_KEY_obj__FP9sqlng_blkP14sqlng_scan_blkP16sqlno_ixkey 
condsT313SQLNN_BOOLEANP19sqlng_skeleton_nodeUcPPUcT8PUsT10_PP10S 
QLD_IXKEYT12_PUiT14_ + 0x958 
0x0900000006DF88DC 
sqlng_build_INDX_obj__FP9sqlng_blkP14sqlng_scan_blkPP11SQLD_IXIN 
FO + 0x39C 
0x0900000006DF1E90 
sqlng_build_TA_op__FP9sqlng_blkP14sqlng_scan_blkP9sqlno_qtb + 
0x2BC 
0x0900000006E17300 
sqlng_process_iscan_op__FP9sqlng_blkP19sqlno_plan_operator + 
0x7F4 
0x09000000054930B4 
sqlng_build_thread__FP9sqlng_blkP14sqlng_thd_ctrl + 0x1B4 
0x0900000006E672BC 
sqlng_process_hsjn_op__FP9sqlng_blkP19sqlno_plan_operator + 
0xB20 
0x09000000054962AC 
sqlng_process_mate_op__FP9sqlng_blkP19sqlno_plan_operator + 
0x1BC 
0x09000000054959BC 
sqlng_process_pipe_op__FP9sqlng_blkP19sqlno_plan_operator + 
0x25C 
0x09000000054930B4 
sqlng_build_thread__FP9sqlng_blkP14sqlng_thd_ctrl + 0x1B4 
0x0900000006E672BC 
sqlng_process_hsjn_op__FP9sqlng_blkP19sqlno_plan_operator + 
0xB20 
0x09000000054962AC 
sqlng_process_mate_op__FP9sqlng_blkP19sqlno_plan_operator + 
0x1BC 
0x09000000054959BC 
sqlng_process_pipe_op__FP9sqlng_blkP19sqlno_plan_operator + 
0x25C 
0x09000000054930B4 
sqlng_build_thread__FP9sqlng_blkP14sqlng_thd_ctrl + 0x1B4 
0x0900000006E10F60 
sqlng_process_nljn_op__FP9sqlng_blkP19sqlno_plan_operator + 
0x2E3C 
0x09000000054962AC 
sqlng_process_mate_op__FP9sqlng_blkP19sqlno_plan_operator + 
0x1BC 
0x09000000054959BC 
sqlng_process_pipe_op__FP9sqlng_blkP19sqlno_plan_operator + 
0x25C 
0x0900000006E09418 
sqlng_process_sort_op__FP9sqlng_blkP19sqlno_plan_operator + 
0x6A8 
0x09000000054930B4 
sqlng_build_thread__FP9sqlng_blkP14sqlng_thd_ctrl + 0x1B4 
0x0900000006E1A20C 
sqlng_scan_derived_table__FP9sqlng_blkP19sqlno_plan_operatorUcP9 
sqlnq_qun + 0x1718 
0x0900000004EF877C 
sqlng_process_scan_op__FP9sqlng_blkP19sqlno_plan_operator + 0x54 
0x0900000006E056F0 
sqlng_process_groupby_op__FP9sqlng_blkP19sqlno_plan_operator + 
0x484 
0x09000000054962AC 
sqlng_process_mate_op__FP9sqlng_blkP19sqlno_plan_operator + 
0x1BC 
0x09000000054959BC 
sqlng_process_pipe_op__FP9sqlng_blkP19sqlno_plan_operator + 
0x25C 
0x0900000004F2C5E0 
sqlng_build_thread__FP9sqlng_blkP14sqlng_thd_ctrl + 0xA44 
0x0900000006E3A43C 
sqlng_process_smptq_op__FP9sqlng_blkP19sqlno_plan_operator + 
0x4DC 
0x0900000006E395B8 
sqlng_process_tq_op__FP9sqlng_blkP19sqlno_plan_operator + 0x38C 
0x09000000054962AC 
sqlng_process_mate_op__FP9sqlng_blkP19sqlno_plan_operator + 
0x1BC 
0x0900000006E06810 
sqlng_process_temp_op__FP9sqlng_blkP19sqlno_plan_operator + 
0x5CC 
0x09000000054930B4 
sqlng_build_thread__FP9sqlng_blkP14sqlng_thd_ctrl + 0x1B4 
0x0900000006E1A20C 
sqlng_scan_derived_table__FP9sqlng_blkP19sqlno_plan_operatorUcP9 
sqlnq_qun + 0x1718 
0x0900000004EF877C 
sqlng_process_scan_op__FP9sqlng_blkP19sqlno_plan_operator + 0x54 
0x09000000054930B4 
sqlng_build_thread__FP9sqlng_blkP14sqlng_thd_ctrl + 0x1B4 
0x0900000006E67018 
sqlng_process_hsjn_op__FP9sqlng_blkP19sqlno_plan_operator + 
0x87C 
0x09000000054930B4 
sqlng_build_thread__FP9sqlng_blkP14sqlng_thd_ctrl + 0x1B4 
0x0900000006E10F60 
sqlng_process_nljn_op__FP9sqlng_blkP19sqlno_plan_operator + 
0x2E3C 
0x09000000054962AC 
sqlng_process_mate_op__FP9sqlng_blkP19sqlno_plan_operator + 
0x1BC 
0x09000000054959BC 
sqlng_process_pipe_op__FP9sqlng_blkP19sqlno_plan_operator + 
0x25C 
0x09000000054930B4 
sqlng_build_thread__FP9sqlng_blkP14sqlng_thd_ctrl + 0x1B4 
0x0900000006E10F60 
sqlng_process_nljn_op__FP9sqlng_blkP19sqlno_plan_operator + 
0x2E3C 
0x09000000054962AC 
sqlng_process_mate_op__FP9sqlng_blkP19sqlno_plan_operator + 
0x1BC 
0x09000000054959BC 
sqlng_process_pipe_op__FP9sqlng_blkP19sqlno_plan_operator + 
0x25C 
0x09000000054930B4 
sqlng_build_thread__FP9sqlng_blkP14sqlng_thd_ctrl + 0x1B4 
0x0900000006E67018 
sqlng_process_hsjn_op__FP9sqlng_blkP19sqlno_plan_operator + 
0x87C 
0x09000000054962AC 
sqlng_process_mate_op__FP9sqlng_blkP19sqlno_plan_operator + 
0x1BC 
0x09000000054959BC 
sqlng_process_pipe_op__FP9sqlng_blkP19sqlno_plan_operator + 
0x25C 
0x09000000054930B4 
sqlng_build_thread__FP9sqlng_blkP14sqlng_thd_ctrl + 0x1B4 
0x0900000006E672BC 
sqlng_process_hsjn_op__FP9sqlng_blkP19sqlno_plan_operator + 
0xB20 
0x09000000054962AC 
sqlng_process_mate_op__FP9sqlng_blkP19sqlno_plan_operator + 
0x1BC 
0x09000000054959BC 
sqlng_process_pipe_op__FP9sqlng_blkP19sqlno_plan_operator + 
0x25C 
0x0900000006E09418 
sqlng_process_sort_op__FP9sqlng_blkP19sqlno_plan_operator + 
0x6A8 
0x09000000054930B4 
sqlng_build_thread__FP9sqlng_blkP14sqlng_thd_ctrl + 0x1B4 
0x0900000006E1A20C 
sqlng_scan_derived_table__FP9sqlng_blkP19sqlno_plan_operatorUcP9 
sqlnq_qun + 0x1718 
0x0900000004EF877C 
sqlng_process_scan_op__FP9sqlng_blkP19sqlno_plan_operator + 0x54 
0x09000000054962AC 
sqlng_process_mate_op__FP9sqlng_blkP19sqlno_plan_operator + 
0x1BC 
0x09000000054959BC 
sqlng_process_pipe_op__FP9sqlng_blkP19sqlno_plan_operator + 
0x25C 
0x090000000549562C 
sqlng_process_return_op__FP9sqlng_blkP19sqlno_plan_operator + 
0x1E4 
0x09000000054930B4 
sqlng_build_thread__FP9sqlng_blkP14sqlng_thd_ctrl + 0x1B4 
0x0900000005498378 sqlng_main__FP9sqlnq_qur + 0x6FC 
0x090000000591D004 sqlng_main__FP9sqlnq_qur@glue17F1 + 0x74 
0x090000000591CA30 
sqlnn_cmpl__FP8sqeAgentP11sqlrrstrings17sqlnn_compileModeT3P14sq 
lrr_cmpl_enviT7PP9sqlnq_qur + 0x304 
0x090000000560F100 
sqlnn_cmpl__FP8sqeAgentP11sqlrrstrings17sqlnn_compileModeT3P14sq 
lrr_cmpl_env + 0x40 
0x09000000058EA428 
sqlra_compile_var__FP8sqlrr_cbP14sqlra_cmpl_envPUciUsN54P14SQLP_ 
LOCK_INFOP16sqlra_cached_varPiPUl + 0x810 
0x09000000058ED5BC 
sqlra_find_var__FP8sqlrr_cbP17sqlra_cached_stmt13sqlra_stmt_idUi 
T4PUcT4UsUcP14sqlra_cmpl_env15sqlra_fill_modePiiT12_N313_T12_P14 
SQLP_LOCK_INFOPP16sqlra_cached_varT12_PUlb + 0x5DC 
0x09000000058EFB14 sqlra_get_var__FP8sqlrr_cbiT2bPbT5 + 0x6F4 
0x0900000003A163E8 
sqlrr_prepare__FP14db2UCinterfaceP16db2UCprepareInfo + 0x2B0 
0x0900000005A00D4C 
sqljs_ddm_prpsqlstt__FP14db2UCinterfaceP13sqljDDMObject + 0xC6C 
0x09000000037BC3E4 
sqljsParseRdbAccessed__FP13sqljsDrdaAsCbP13sqljDDMObjectP14db2UC 
interface + 0x280 
0x090000000570A304 
.sqljsParse.fdpr.clone.274__FP13sqljsDrdaAsCbP14db2UCinterfaceP8 
sqeAgentb + 0x6AC 
0x0900000005708FA4 @63@sqljsSqlam__FP14db2UCinterfaceP8sqeAgentb 
+ 0x2B0 
0x09000000055064B0 
@63@sqljsDriveRequests__FP8sqeAgentP14db2UCconHandle + 0xA4 
0x090000000550610C 
@63@sqljsDrdaAsInnerDriver__FP18SQLCC_INITSTRUCT_Tb + 0x278 
0x0900000005505BC0 sqljsDrdaAsDriver__FP18SQLCC_INITSTRUCT_T + 
0x1EC 
0x09000000055D917C RunEDU__8sqeAgentFv + 0x2F0 
0x09000000055D7968 EDUDriver__9sqzEDUObjFv + 0xE8 
0x09000000055DDE18 sqloEDUEntry + 0x250 
</StackTrace>
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 10.5.0.7                              * 
****************************************************************
Local Fix:
If the singleton predicate is a user defined predicate, then 
rewrite the query to convert it into an equality predicate. 
This might not be possible if the predicate was generated 
internally
Solution
Fixed in DB2 version 10.5.0.7
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

30.06.2015
05.02.2016
05.02.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