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

DB2 MIGHT ABEND OR FAIL WITH SQL0901N (BAD PLAN; UNRESOLVED QNC FOUND)
DURING BIND.

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
Under rare scenarios, DB2 might abend or give a SQL0901N (Bad 
Plan; Unresolved QNC found) error during bind. 
 
Stack Trace for trap: 
sqlnr_add_pushed_prd 
sqlnr_joinppd4sel_action 
sqlnr_comp 
qlnr_seq 
sqlnr_rcc 
sqlnr_magic_detail_action 
sqlnr_comp 
sqlnr_seq 
sqlnr_rcc 
sqlnr_endqtb_action 
 
For SQL0901N, users can see the db2diag.log entry like as below: 
2012-05-01-18.02.51.821690+540 E499790A773      LEVEL: Error 
PID     : 622766             TID  : 1544        PROC : db2sysc 
INSTANCE: db2inst1           NODE : 000         DB   : SAMPLE 
APPHDL  : 0-7                APPID: *LOCAL.db2inst1.120501090244 
AUTHID  : db2inst1 
EDUID   : 1544               EDUNAME: db2agent (SAMPLE) 0 
FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_ffdc, probe:10 
MESSAGE : ADM14005E  The following error occurred: "AppErr". 
First Occurrence 
          Data Capture (FODC) has been invoked in the following 
mode: 
          "Automatic".  Diagnostic information has been recorded 
in the 
          directory named 
          "/home/db2inst1/sqllib/db2dump/FODC_AppErr_2012-05-01- 
          18.02.51.811325_622766_1544_000/". 
. 
2012-05-01-18.02.51.825744+540 I502438A856      LEVEL: Severe 
PID     : 622766             TID  : 1544        PROC : db2sysc 
INSTANCE: db2inst1           NODE : 000         DB   : SAMPLE 
APPHDL  : 0-7                APPID: *LOCAL.db2inst1.120501090244 
AUTHID  : db2inst1 
EDUID   : 1544               EDUNAME: db2agent (SAMPLE) 0 
FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_ffdc, 
probe:300 
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes 
 sqlcaid : SQLCA     sqlcabc: 136   sqlcode: -901   sqlerrml: 30 
 sqlerrmc: Bad Plan; Unresolved QNC found 
 sqlerrp : SQLNG006 
 sqlerrd : (1) 0x00000000      (2) 0x00000000      (3) 
0x00000000 
           (4) 0x00000000      (5) 0xFFFFFFCE      (6) 
0x00000000 
 sqlwarn : (1)      (2)      (3)      (4)        (5)       (6) 
 
           (7)      (8)      (9)      (10)        (11) 
 sqlstate: 
 
The following db2diag.log entry also would be logged if 
DIAGLEVEL is set as 4. 
 
2012-05-01-18.02.51.929064+540 E544843A2106     LEVEL: Info 
(Origin) 
PID     : 622766             TID  : 1544        PROC : db2sysc 
INSTANCE: db2inst1           NODE : 000         DB   : SAMPLE 
APPHDL  : 0-7                APPID: *LOCAL.e97q5g.120501090244 
AUTHID  : db2inst1 
EDUID   : 1544               EDUNAME: db2agent (SAMPLE) 0 
FUNCTION: DB2 UDB, SW- common services, sqlnn_cmpl, probe:650 
MESSAGE : ZRC=0x801A006D=-2145779603=SQLZ_CA_BUILT 
          "SQLCA has already been built" 
DATA #1 : String, 62 bytes 
An unexpected error was detected during statement compilation. 
DATA #2 : Boolean, 1 bytes 
true 
DATA #3 : Boolean, 1 bytes 
false 
DATA #4 : Boolean, 1 bytes 
false 
DATA #5 : Boolean, 1 bytes 
false 
DATA #6 : Hex integer, 4 bytes 
0x00000000 
DATA #7 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes 
 sqlcaid : SQLCA     sqlcabc: 136   sqlcode: -901   sqlerrml: 30 
 sqlerrmc: Bad Plan; Unresolved QNC found 
 sqlerrp : SQLNG006 
 sqlerrd : (1) 0x801A006D      (2) 0x00000000      (3) 
0x00000000 
           (4) 0x00000000      (5) 0xFFFFFFCE      (6) 
0x00000000 
 sqlwarn : (1)      (2)      (3)      (4)        (5)       (6) 
 
           (7)      (8)      (9)      (10)        (11) 
 sqlstate: 
DATA #8 : Hex integer, 4 bytes 
0x00000040 
DATA #9 : String, 822 bytes 
Compiler error stack for rc = -2145779603: 
sqlnn_cmpl[415] 
sqlng_main[3163] 
sqlng_main[1687] 
sqlng_build_thread[742] 
sqlng_process_return_op[1066] 
sqlng_process_pipe_op[1413] 
sqlng_process_mate_op[1990] 
sqlng_process_pipe_op[1413] 
sqlng_process_mate_op[1990] 
sqlng_process_nljn_op[11038] 
sqlng_build_thread[742] 
sqlng_scan_derived_table[3823] 
sqlng_build_thread[742] 
sqlng_process_sort_op[12515] 
sqlng_process_nljn_op[11217] 
sqlng_build_thread[742] 
sqlng_process_nljn_op[11038] 
sqlng_build_thread[742] 
sqlng_process_nljn_op[11460] 
sqlng_build_thread[742] 
sqlng_process_f_iscan[7020] 
sqlng_process_eao_plan[2293] 
sqlng_build_thread[742] 
sqlng_process_pipe_op[1413] 
sqlng_process_mate_op[1990] 
sqlng_process_f_iscan[7206] 
sqlng_build_TA_op[4323] 
sqlng_build_INDX_obj[5213] 
sqlng_build_KEY_obj[6205] 
sqlng_build_INDX_key[50]
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Please upgrade to DB2 version 101 fix pack 2                 * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
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
The problem has been fixed in DB2 version 101 fix pack 2
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
04.11.2012
14.01.2013
14.01.2013
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.2 FixList
10.5.0.2 FixList