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

SET SESSION AUTHORIZATION/SET SESSION_USER with string constant inside SQL
routine causes trap

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
When you use SET SESSION AUTHORIZATION or SET SESSION_USER with 
a 
string constant inside of an SQL routine, compiling the routine 
will cause your instance to terminate abnormally. 
 
For example: 
 
CREATE PROCEDURE SP_TEST 
LANGUAGE SQL 
BEGIN 
  SET SESSION_USER = 'UNIUSR';  -- will cause a trap when 
compiled 
END 
 
CREATE PROCEDURE SP_TEST 
LANGUAGE SQL 
BEGIN 
  SET SESSION_USER = UNIUSR; -- will compile successfully 
END 
 
At db2diag.log, you will see a similar messages as: 
--------------------------- 
2010-01-13-13.41.51.639516+540 I26466G1291        LEVEL: Severe 
PID     : 15456                TID  : 2950687632  PROC : db2sysc 
0 
INSTANCE: db2inst1             NODE : 000         DB   : SAMPLE 
APPHDL  : 0-7                  APPID: 
*LOCAL.db2inst1.100113044121 
AUTHID  : DB2INST1 
EDUID   : 19                   EDUNAME: db2agent (SAMPLE) 0 
FUNCTION: DB2 UDB, trace services, sqlt_logerr_data (secondary 
logging func, probe:0 
MESSAGE : RDS UCINTFC: pStatementText = 
DATA #1 : Hexdump, 168 bytes 
0xAD86ABA0 : 4352 4541 5445 2050 524F 4345 4455 5245    CREATE 
PROCEDURE 
0xAD86ABB0 : 2053 505F 5445 5354 0A4C 414E 4755 4147 
SP_TEST.LANGUAG 
0xAD86ABC0 : 4520 5351 4C0A 4245 4749 4E0A 2053 4554    E 
SQL.BEGIN. SET 
0xAD86ABD0 : 2053 4553 5349 4F4E 5F55 5345 5220 3D20 
SESSION_USER = 
0xAD86ABE0 : 2755 4E49 5553 5227 3B20 2D2D 2054 6865 
'UNIUSR'; -- The 
0xAD86ABF0 : 2069 6E73 7461 6E63 6520 6973 2064 6F77 
instance is dow 
0xAD86AC00 : 6E65 642E 0A2D 2D20 5345 5420 5345 5353    ned..-- 
SET SESS 
0xAD86AC10 : 494F 4E5F 5553 4552 203D 2055 4E49 5553    ION_USER 
= UNIUS 
0xAD86AC20 : 523B 2020 202D 2D20 5468 6520 696E 7374    R;   -- 
The inst 
0xAD86AC30 : 616E 6365 2069 7320 6E6F 7420 646F 776E    ance is 
not down 
0xAD86AC40 : 6564 2E0A 454E 440A                        ed..END. 
--------------------------- 
 
And the associated trap file, in this case 
15456.19.000.trap.txt, 
could contain below stack trace: 
----------------------- 
  <snip> 
<POFDisassembly> 
 _ZNK9sqlnq_pid6myqncpEv + 0x0006 
(/home/db2inst1/sqllib/lib32/libdb2e.so.1) 
 
        0xB4696D1E : 8B426483F8127507 
</POFDisassembly> 
<StackTrace> 
--Frame--- ------Function + Offset------ 
0xAFDF3C54 _ZNK9sqlnq_pid6myqncpEv + 0x0006 
                (/home/db2inst1/sqllib/lib32/libdb2e.so.1) 
0xAFDF3F30 _Z18sqlnq_set_registerPP8stknode_i10actiontypePhP3loc 
+ 0x1e46 
                (/home/db2inst1/sqllib/lib32/libdb2e.so.1) 
0xAFDF3F84 _Z12sqlnp_smactnP8sqlnp_cbi + 0x087c 
                (/home/db2inst1/sqllib/lib32/libdb2e.so.1) 
0xAFDF3FDC _Z12sqlnp_parserP8sqlnp_cb + 0x0707 
                (/home/db2inst1/sqllib/lib32/libdb2e.so.1) 
0xAFDF40F8 _Z10sqlnp_mainP12sqlnq_stringsPP9sqlnq_qur + 0x03fd 
                (/home/db2inst1/sqllib/lib32/libdb2e.so.1) 
0xAFDF560C 
_Z10sqlnn_cmplP8sqeAgentP11sqlrrstrings17sqlnn_compileModesP14sq 
lrr_cmpl_enviiPP9sqlnq_qur 
+ 0x09bb 
                (/home/db2inst1/sqllib/lib32/libdb2e.so.1) 
0xAFDF5638 
_Z10sqlnn_cmplP8sqeAgentP11sqlrrstrings17sqlnn_compileModesP14sq 
lrr_cmpl_env 
+ 0x0024 
                (/home/db2inst1/sqllib/lib32/libdb2e.so.1) 
0xAFDF6290 
_Z17sqlra_compile_varP8sqlrr_cbP14sqlra_cmpl_envPhitiiiiiP14SQLP 
_LOCK_INFOP16sqlra_cached_varPiPy 
+ 0x0605 
                (/home/db2inst1/sqllib/lib32/libdb2e.so.1) 
0xAFDF6C34 
_Z14sqlra_find_varP8sqlrr_cbP17sqlra_cached_stmt13sqlra_stmt_idj 
jPhjthP14sqlra_cmpl_env15sqlra_fill_modePiiS8_iiiS8_P14SQLP_LOCK 
_INFOPP16sqlra_cached_varS8_Pyb 
+ 0x03ae 
                (/home/db2inst1/sqllib/lib32/libdb2e.so.1) 
0xAFDF7358 _Z13sqlra_get_varP8sqlrr_cbiibPbS1_ + 0x05db 
                (/home/db2inst1/sqllib/lib32/libdb2e.so.1) 
<snip> 
-----------------------
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 UDB Version 9.7.                                         * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error description field for more information.            * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Version 9.7 FixPack 2.                            * 
****************************************************************
Local Fix:
Basically none but removing the single quotes may be a 
workaround.
available fix packs:
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
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 9a 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 10 for Linux, UNIX, and Windows

Solution
Problem was first fixed in DB2 UDB Version 9.7 FixPack 2.
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC67532 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
14.01.2010
16.06.2010
16.06.2010
Problem solved at the following versions (IBM BugInfos)
9.7.FP2
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.2 FixList