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

Create event monitor fails with -901 if no 4K pagesize tablespace exist

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
Create event monitor fails with -901 
 
db2 "CREATE EVENT MONITOR OPMN@xxxx FOR LOCKING WRITE TO 
UNFORMATTED EVENT TABLE (PCTDEACTIVATE 100) MANUALSTART" 
DB21034E  The command was processed as an SQL statement because 
it was not a 
valid Command Line Processor command.  During SQL processing it 
returned: 
SQL0901N  The SQL statement or command failed because of a 
database system 
error. (Reason "sqlri_ddl_common: unexpected sqlcode for DDL!".) 
 
 
db2diag.log entries 
2014-04-02-02.05.45.273695-240 E987964A1516         LEVEL: Info 
(Origin) 
PID     : 2555978              TID : 25202          PROC : 
db2sysc 0 
INSTANCE: xxx               NODE : 000           DB   : xxxx 
APPHDL  : 0-18393              APPID: 
30.128.133.133.58840.140402060546 
AUTHID  : xxx               HOSTNAME: xxxxxx 
EDUID   : 25202                EDUNAME: db2agent (EDADB) 0 
FUNCTION: DB2 UDB, SW- common services, sqlnn_cmpl, probe:650 
MESSAGE : ZRC=0x80040001=-2147221503=SQLD_NOREC "NO MORE RECORDS 
FOUND ON FETCH" 
          DIA8000C An unexpected end of file was reached "". 
DATA #1 : String, 62 bytes 
An unexpected error was detected during statement compilation. 
DATA #2 : Boolean, 1 bytes 
false 
DATA #3 : Boolean, 1 bytes 
false 
DATA #4 : Boolean, 1 bytes 
true 
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: 100   sqlerrml: 0 
 sqlerrmc: 
 sqlerrp : SQLRL083 
 sqlerrd : (1) 0x80040001      (2) 0x00000001      (3) 
0x00000000 
           (4) 0x00000000      (5) 0x00000000      (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, 172 bytes 
Compiler error stack for rc = -2147221503: 
sqlnn_cmpl[300] 
sqlnp_main[250] 
sqlnp_parser[510] 
sqlnp_smactn[100] 
sqlnq_create_evmon_stmt[130] 
sqlnq_ddl_create_evmon_end[280] 
 
<StackTrace> 
-----FUNC-ADDR---- ------FUNCTION + OFFSET------ 
0x00002B6DB1D7C1A5 
_Z25ossDumpStackTraceInternalmR11OSSTrapFileiP7siginfoPvmm + 
0x0385 
        (/home/regress1/sqllib/lib64/libdb2osse.so.1) 
0x00002B6DB1D7BDAC ossDumpStackTraceV98 + 0x002c 
        (/home/regress1/sqllib/lib64/libdb2osse.so.1) 
0x00002B6DB1D76EAD _ZN11OSSTrapFile6dumpExEmiP7siginfoPvm + 
0x00fd 
        (/home/regress1/sqllib/lib64/libdb2osse.so.1) 
0x00002B6DABBC9EFD sqlo_trce + 0x03ed 
        (/home/regress1/sqllib/lib64/libdb2e.so.1) 
0x00002B6DABCD6439 sqloDumpDiagInfoHandler + 0x0249 
        (/home/regress1/sqllib/lib64/libdb2e.so.1) 
0x00002B6DA56A8D60 address: 0x00002B6DA56A8D60 ; dladdress: 
0x00002B6DA569B000 ; offset in lib: 0x000000000000DD60 ; 
        (/lib64/libpthread.so.0) 
0x00002B6DA56A6005 pthread_kill + 0x0035 
        (/lib64/libpthread.so.0) 
0x00002B6DABCD5F72 sqloDumpEDU + 0x0052 
        (/home/regress1/sqllib/lib64/libdb2e.so.1) 
0x00002B6DA74169A3 _Z15sqldDumpContextP9sqeBsuEduiiiiiPKcPvi + 
0x1223 
        (/home/regress1/sqllib/lib64/libdb2e.so.1) 
0x00002B6DAC1D0C77 _Z15sqlrr_dump_ffdcP8sqlrr_cbii + 0x0567 
        (/home/regress1/sqllib/lib64/libdb2e.so.1) 
0x00002B6DAD3FC98C _Z13sqlzeDumpFFDCP8sqeAgentjP5sqlcai + 0x00ac 
        (/home/regress1/sqllib/lib64/libdb2e.so.1) 
0x00002B6DAD3FC7A3 
_Z12sqlzeSqlCodeP8sqeAgentjmjP5sqlcaitP13__va_list_tag + 0x01a3 
        (/home/regress1/sqllib/lib64/libdb2e.so.1) 
0x00002B6DAC2B2C41 sqlrrSqlCode + 0x00e1 
        (/home/regress1/sqllib/lib64/libdb2e.so.1) 
0x00002B6DAC6A2A25 _Z16sqlri_ddl_commonP8sqlrr_cb + 0x13c5 
        (/home/regress1/sqllib/lib64/libdb2e.so.1) 
0x00002B6DAC6A15A6 _Z8sqlriddlP8sqlrr_cb + 0x0026 
        (/home/regress1/sqllib/lib64/libdb2e.so.1) 
0x00002B6DAC6CA086 _Z15sqlriSectInvokeP8sqlrr_cbP12sqlri_opparm 
+ 0x04f6 
        (/home/regress1/sqllib/lib64/libdb2e.so.1) 
0x00002B6DAC2002E2 _Z23sqlrr_execute_immediateP8sqlrr_cbi + 
0x0582 
        (/home/regress1/sqllib/lib64/libdb2e.so.1) 
0x00002B6DAC1E2CE0 
_Z14sqlrr_execimmdP14db2UCinterfaceP16db2UCprepareInfo + 0x0850 
        (/home/regress1/sqllib/lib64/libdb2e.so.1) 
0x00002B6DAA65DF2E 
_Z19sqljs_ddm_excsqlimmP14db2UCinterfaceP13sqljDDMObject + 
0x04be 
        (/home/regress1/sqllib/lib64/libdb2e.so.1) 
0x00002B6DAA6251DC 
_Z21sqljsParseRdbAccessedP13sqljsDrdaAsCbP13sqljDDMObjectP14db2U 
Cinterface + 0x040c 
        (/home/regress1/sqllib/lib64/libdb2e.so.1) 
0x00002B6DAA626064 
_Z10sqljsParseP13sqljsDrdaAsCbP14db2UCinterfaceP8sqeAgentb + 
0x0524 
        (/home/regress1/sqllib/lib64/libdb2e.so.1) 
0x00002B6DAA6189A3 address: 0x00002B6DAA6189A3 ; dladdress: 
0x00002B6DA57B4000 ; offset in lib: 0x0000000004E649A3 ; 
        (/home/regress1/sqllib/lib64/libdb2e.so.1) 
0x00002B6DAA61F5F2 address: 0x00002B6DAA61F5F2 ; dladdress: 
0x00002B6DA57B4000 ; offset in lib: 0x0000000004E6B5F2 ; 
        (/home/regress1/sqllib/lib64/libdb2e.so.1) 
0x00002B6DAA62060F _Z17sqljsDrdaAsDriverP18SQLCC_INITSTRUCT_T + 
0x011f 
        (/home/regress1/sqllib/lib64/libdb2e.so.1) 
0x00002B6DAA105697 _ZN8sqeAgent6RunEDUEv + 0x0dd7 
        (/home/regress1/sqllib/lib64/libdb2e.so.1) 
0x00002B6DAD3FCEDA _ZN9sqzEDUObj9EDUDriverEv + 0x010a 
        (/home/regress1/sqllib/lib64/libdb2e.so.1) 
0x00002B6DABCD35A5 sqloEDUEntry + 0x05e5 
        (/home/regress1/sqllib/lib64/libdb2e.so.1) 
0x00002B6DA56A1193 address: 0x00002B6DA56A1193 ; dladdress: 
0x00002B6DA569B000 ; offset in lib: 0x0000000000006193 ; 
        (/lib64/libpthread.so.0) 
0x00002B6DB27B50DD __clone + 0x006d 
        (/lib64/libc.so.6) 
</StackTrace> 
 
Workaround: Ensure a 4k pagesize tablespace exist before 
attempting to create the event monitor
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users running DB2 10.1 before fix pack 4                     * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 10.1 Fix Pack 4 or later                      * 
****************************************************************
Local Fix:
Solution
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
23.05.2014
30.07.2015
30.07.2015
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.5 FixList