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

QUERY REFERENCING AGGREGATION AND OLAP FUNCTION IN SAME EXPRESSION MIGHT
GENERATE A -901

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
Under rare scenarios, if OLAP and aggregation functions are part 
of the same expression in the select list, 
DB2 might generate a SQL0901N error message. 
 
eg. Select row_number() over () + min(c1) from t1; 
 
SQL0901N  The SQL statement failed because of a non-severe 
system error. 
Subsequent SQL statements can be processed.  (Reason "Bad Opcode 
0, ref_arity 
2, sqlnq_pid ID 943 (SYSIBM.SCALAG)".)  SQLSTATE=58004 
 
Stack: 
0x0900000007FD6CC0 sqlzeDumpFFDC__FP8sqeAgentUiP5sqlcai + 0x28 
0x0900000007FD73A4 sqlzeSqlCode__FP8sqeAgentUiUlT2P5sqlcaiUsPc + 
0x140 
0x0900000007FD71B8 sqlnn_erds__FiN41e + 0x150 
0x09000000051E0494 sqlnn_erds__FiN41e@glue718 + 0xC0 
0x0900000006835834 
sqlng_build_S_X_op__FP9sqlng_blkPP12sqlri_opparmP9sqlnq_pid + 
0x1E20 
0x090000000835B7E0 
sqlng_process_parse_tree_node__FP9sqlng_blkP9sqlnq_pid + 0x30C 
0x090000000835BDAC 
sqlng_process_BF_node__FP9sqlng_blkP9sqlnq_pid + 0x114 
0x090000000835A698 sqlng_walk_HXP_chain__FP9sqlng_blk + 0x254 
0x090000000835A0BC 
sqlng_build_thread__FP9sqlng_blkP14sqlng_thd_ctrl + 0x140 
0x090000000835D394 
sqlng_process_mate_op__FP9sqlng_blkP19sqlno_plan_operator + 
0x254 
0x090000000835C9AC 
sqlng_process_pipe_op__FP9sqlng_blkP19sqlno_plan_operator + 
0x204 
0x090000000835C678 
sqlng_process_return_op__FP9sqlng_blkP19sqlno_plan_operator + 
0x1E4 
0x090000000835A128 
sqlng_build_thread__FP9sqlng_blkP14sqlng_thd_ctrl + 0x1AC 
0x090000000835F200 sqlng_main__FP9sqlnq_qur + 0x6BC 
0x090000000837E280 sqlng_main__FP9sqlnq_qur@glue17D0 + 0x114 
0x090000000837DDEC 
sqlnn_cmpl__FP8sqeAgentP11sqlrrstrings17sqlnn_compileModeT3P14sq 
lrr_cmpl_enviT7PP9sqlnq_qur + 0x320 
0x0900000008206B14 
sqlnn_cmpl__FP8sqeAgentP11sqlrrstrings17sqlnn_compileModeT3P14sq 
lrr_cmpl_env + 0x40 
0x0900000007F74D00 
sqlra_compile_var__FP8sqlrr_cbP14sqlra_cmpl_envPUciUsN54P14SQLP_ 
LOCK_INFOP16sqlra_cached_varPiPUl + 0x7C4 
0x0900000007F72948 
sqlra_find_var__FP8sqlrr_cbP17sqlra_cached_stmt13sqlra_stmt_idUi 
T4PUcT4UsUcP14sqlra_cmpl_env15sqlra_fill_modePiiT12_N313_T12_P14 
SQLP_LOCK_INFOPP16sqlra_cached_varT12_PUlb + 0x648 
0x0900000007F707FC sqlra_get_var__FP8sqlrr_cbiT2bPbT5 + 0x620 
0x0900000004DFC040 
sqlrr_prepare__FP14db2UCinterfaceP16db2UCprepareInfo + 0x2B8 
0x090000000587F8C8 
sqljs_ddm_prpsqlstt__FP14db2UCinterfaceP13sqljDDMObject + 0x858 
0x0900000003C1720C 
sqljsParseRdbAccessed__FP13sqljsDrdaAsCbP13sqljDDMObjectP14db2UC 
interface + 0x228 
0x0900000008120044 
.sqljsParse.fdpr.clone.223__FP13sqljsDrdaAsCbP14db2UCinterfaceP8 
sqeAgentb + 0x230 
0x090000000810660C @64@sqljsSqlam__FP14db2UCinterfaceP8sqeAgentb 
+ 0xAFC 
0x09000000082C79A8 
@64@sqljsDriveRequests__FP8sqeAgentP14db2UCconHandle + 0xA0 
0x0900000003D1B1F0 
@64@sqljsDrdaAsInnerDriver__FP18SQLCC_INITSTRUCT_Tb + 0x354 
0x09000000082C7184 sqljsDrdaAsDriver__FP18SQLCC_INITSTRUCT_T + 
0xE4 
0x0900000008281EC0 RunEDU__8sqeAgentFv + 0x7C 
0x090000000828451C EDUDriver__9sqzEDUObjFv + 0xDC 
0x090000000826C038 sqloEDUEntry + 0x270
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
* Under rare scenarios, if OLAP and aggregation functions are  * 
* part of the same expression in the select list,              * 
* DB2 might generate a SQL0901N error message.                 * 
*                                                              * 
* eg. Select row_number() over () + min(c1) from t1;           * 
*                                                              * 
* SQL0901N  The SQL statement failed because of a non-severe   * 
* system error.                                                * 
* Subsequent SQL statements can be processed.  (Reason "Bad    * 
* Opcode 0, ref_arity 2, sqlnq_pid ID 943 (SYSIBM.SCALAG)".)   * 
* SQLSTATE=58004                                               * 
*                                                              * 
* Stack:                                                       * 
* 0x0900000007FD6CC0 sqlzeDumpFFDC__FP8sqeAgentUiP5sqlcai +    * 
* 0x28                                                         * 
* 0x0900000007FD73A4                                           * 
* sqlzeSqlCode__FP8sqeAgentUiUlT2P5sqlcaiUsPc +0x140           * 
* 0x0900000007FD71B8 sqlnn_erds__FiN41e + 0x150                * 
* 0x09000000051E0494 sqlnn_erds__FiN41e@glue718 + 0xC0         * 
* 0x0900000006835834                                           * 
* sqlng_build_S_X_op__FP9sqlng_blkPP12sqlri_opparmP9sqlnq_pid  * 
* +0x1E20                                                      * 
* 0x090000000835B7E0                                           * 
* sqlng_process_parse_tree_node__FP9sqlng_blkP9sqlnq_pid +     * 
* 0x30C                                                        * 
* 0x090000000835BDAC                                           * 
* sqlng_process_BF_node__FP9sqlng_blkP9sqlnq_pid + 0x114       * 
* 0x090000000835A698 sqlng_walk_HXP_chain__FP9sqlng_blk +      * 
* 0x254                                                        * 
* 0x090000000835A0BC                                           * 
* sqlng_build_thread__FP9sqlng_blkP14sqlng_thd_ctrl + 0x140    * 
* 0x090000000835D394                                           * 
* sqlng_process_mate_op__FP9sqlng_blkP19sqlno_plan_operator +  * 
* 0x254                                                        * 
* 0x090000000835C9AC                                           * 
* sqlng_process_pipe_op__FP9sqlng_blkP19sqlno_plan_operator +  * 
* 0x204                                                        * 
* 0x090000000835C678                                           * 
* sqlng_process_return_op__FP9sqlng_blkP19sqlno_plan_operator  * 
* + 0x1E4                                                      * 
* 0x090000000835A128                                           * 
* sqlng_build_thread__FP9sqlng_blkP14sqlng_thd_ctrl + 0x1AC    * 
* 0x090000000835F200 sqlng_main__FP9sqlnq_qur + 0x6BC          * 
* 0x090000000837E280 sqlng_main__FP9sqlnq_qur@glue17D0 + 0x114 * 
* 0x090000000837DDEC                                           * 
* sqlnn_cmpl__FP8sqeAgentP11sqlrrstrings17sqlnn_compileModeT3P * 
* 14sqlrr_cmpl_enviT7PP9sqlnq_qur + 0x320                      * 
* 0x0900000008206B14                                           * 
* sqlnn_cmpl__FP8sqeAgentP11sqlrrstrings17sqlnn_compileModeT3P * 
* 14sqlrr_cmpl_env + 0x40                                      * 
* 0x0900000007F74D00                                           * 
* sqlra_compile_var__FP8sqlrr_cbP14sqlra_cmpl_envPUciUsN54P14S * 
* QLP_LOCK_INFOP16sqlra_cached_varPiPUl + 0x7C4                * 
* 0x0900000007F72948                                           * 
* sqlra_find_var__FP8sqlrr_cbP17sqlra_cached_stmt13sqlra_stmt_ * 
* idUiT4PUcT4UsUcP14sqlra_cmpl_env15sqlra_fill_modePiiT12_N313 * 
* _T12_P14                                                     * 
* SQLP_LOCK_INFOPP16sqlra_cached_varT12_PUlb + 0x648           * 
* 0x0900000007F707FC sqlra_get_var__FP8sqlrr_cbiT2bPbT5 +      * 
* 0x620                                                        * 
* 0x0900000004DFC040                                           * 
* sqlrr_prepare__FP14db2UCinterfaceP16db2UCprepareInfo + 0x2B8 * 
* 0x090000000587F8C8                                           * 
* sqljs_ddm_prpsqlstt__FP14db2UCinterfaceP13sqljDDMObject +    * 
* 0x858                                                        * 
* 0x0900000003C1720C                                           * 
* sqljsParseRdbAccessed__FP13sqljsDrdaAsCbP13sqljDDMObjectP14d * 
* b2UC                                                         * 
* interface + 0x228                                            * 
* 0x0900000008120044.sqljsParse.fdpr.clone.223__FP13sqljsDrdaA * 
* sCbP14db2UCinterfaceP8                                       * 
* sqeAgentb + 0x230                                            * 
* 0x090000000810660C                                           * 
* @64@sqljsSqlam__FP14db2UCinterfaceP8sqeAgentb + 0xAFC        * 
* 0x09000000082C79A8                                           * 
* @64@sqljsDriveRequests__FP8sqeAgentP14db2UCconHandle + 0xA0  * 
* 0x0900000003D1B1F0                                           * 
* @64@sqljsDrdaAsInnerDriver__FP18SQLCC_INITSTRUCT_Tb + 0x354  * 
* 0x09000000082C7184 sqljsDrdaAsDriver__FP18SQLCC_INITSTRUCT_T * 
* + 0xE4                                                       * 
* 0x0900000008281EC0 RunEDU__8sqeAgentFv + 0x7C                * 
* 0x090000000828451C EDUDriver__9sqzEDUObjFv + 0xDC            * 
* 0x090000000826C038 sqloEDUEntry + 0x270                      * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 UDB Version 9.7, FixPak 6                     * 
****************************************************************
Local Fix:
Workaround: 
Please rewrite the query to separate the OLAP function. 
eg. select row_number() over () + col1 from (select min(c1) as 
col1 from t1)
available fix packs:
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
First fixed in DB2 UDB Version 9.7, FixPak 6
Workaround
Please rewrite the query to separate the OLAP function. eg. 
select row_number() over () + col1 from (select min(c1) as col1 
from t1)
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC84338 IC87836 IT03640 IT03795 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
01.02.2012
08.06.2012
08.06.2012
Problem solved at the following versions (IBM BugInfos)
9.7.
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.6 FixList