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

POSSIBLE CACHE CORRUPTION(SEGV/CRASH): ENTRY CAN BE FREED BY ONE THREAD AND
ADDED TO LRU BY ANOTHER AT THE SAME TIME

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
It is possible that one thread removes an entry from the LRU and 
cached entries list and then 
frees that entry while another thread is currently adding it 
again to the LRU list. This results 
in using a freed entry that most likely will lead to a 
segv/crash. Typical stacks would look 
like the following (top part of stack): 
 
== Example 1 == 
 
0x00007FA06864E2FB sqlrlc_remove_from_lru + 0x006b 
0x00007FA0686439F4 sqlrlc_csm_lru_cache + 0x0144 
0x00007FA068640EDC sqlrlc_csm_lru + 0x04ac 
0x00007FA06863FC4D sqlrlc_csm_processing + 0x017d 
0x00007FA06863F825 sqlrlc_check_available_memory + 0x0175 
0x00007FA0686A2035 sqlrlcAuthidsUpdateEntries + 0x0565 
0x00007FA0686A3DFA sqlrlcAuthidsFindRolelist + 0x076a 
 
== Example 2 == 
 
0x00007F80B5E639E0 sqlo_xlatch11getIdentityEv + 0x0000 
0x00007F80B8AF0074 sqlrlc_update_lru + 0x01c4 
0x00007F80B8ADE81A sqlrlc_auth_find_insert + 0x035a 
0x00007F80B8B189D8 sqlrlc_sysuserauth_get_authPDs + 0x00d8 
0x00007F80B8B1874D sqlrlc_sysuserauth_request_auths + 0x023d 
0x00007F80B8A1ACF1 sqlrlgua + 0x0391 
 
2013-12-04-11.06.56.120423-300 
EDUID   : 62                   EDUNAME: db2agent (CAT) 
FUNCTION: DB2 UDB, catcache support, sqlrlc_create_insert_entry, 
probe:2445 
new entry:- p_entry = 0x00007f5fed53e600 
  [1] 0x00007F602C7774F5 sqlrlc_create_insert_entry + 0x105 
  [2] 0x00007F602C76C890 sqlrlc_auth_find_insert + 0x3D0 
  [3] 0x00007F602C7A6D78 sqlrlc_sysuserauth_get_authPDs + 0xD8 
  [4] 0x00007F602C7A6AED sqlrlc_sysuserauth_request_auths + 
0x23D 
 
2013-12-04-11.06.58.487657-300 
EDUID   : 62                   EDUNAME: db2agent (CAT) 
FUNCTION: DB2 UDB, catcache support, sqlrlc_auth_find_insert, 
probe:112 
updating LRU:- p_entry = 0x00007f5fed7c9d00 p_anchor = 
0x00007f5fec33cd70 
0x00007F5FED7C9D00 : 70CD 33EC 5F7F 0000 00E6 53ED 5F7F 0000 
p.3._.....S._... 
0x00007F5FED7C9D10 : 0000 0000 0000 0000 0000 0000 0000 0000 
................ 
0x00007F5FED7C9D20 : 0000 0000 0000 0000 0000 0000 0000 0000 
................ 
0x00007F5FED7C9D30 : 0E00 0000 0200 0000 
........ 
  [1] 0x00007F602C77E324 sqlrlc_update_lru + 0xD4 
  [2] 0x00007F602C76C81A sqlrlc_auth_find_insert + 0x35A 
  [3] 0x00007F602C7A6D78 sqlrlc_sysuserauth_get_authPDs + 0xD8 
  [4] 0x00007F602C7A6AED sqlrlc_sysuserauth_request_auths + 
0x23D 
 
2013-12-04-11.07.07.566089-300 
EDUID   : 51                   EDUNAME: db2agent (CAT) 
FUNCTION: DB2 UDB, catcache support, sqlrlc_auth_find_insert, 
probe:389 
Removing from LRU:- p_entry = 0x00007f5fed53e600 p_anchor = 
0x00007f5fec33cd70 
-- Remove from LRU and put on DEFUNCT list. 
0x00007F5FED53E600 : 70CD 33EC 5F7F 0000 E006 54ED 5F7F 0000 
p.3._.....T._... 
0x00007F5FED53E610 : 009D 7CED 5F7F 0000 0000 0000 0000 0000 
..|._........... 
0x00007F5FED53E620 : 0000 0000 0000 0000 0000 0000 0000 0000 
................ 
0x00007F5FED53E630 : 0E00 0000 0200 0000 
........ 
  [1] 0x00007F602C77E7A3 sqlrlc_remove_from_lru + 0xC3 
  [2] 0x00007F602C76D746 sqlrlc_authcache_update + 0x336 
  [3] 0x00007F602C775308 sqlrlc_execute_event + 0x188 
  [4] 0x00007F602C774666 sqlrlc_broadcast + 0x2B6 
 
2013-12-04-11.07.07.567390-300 
EDUID   : 62                   EDUNAME: db2agent (CAT) 
FUNCTION: DB2 UDB, catcache support, sqlrlc_auth_find_insert, 
probe:112 
updating LRU:- p_entry = 0x00007f5fed53e600 p_anchor = 
0x00007f5fec33cd70 
-- Here we put that entry on the LRU but it seems that we do not 
hold 
-- the LRU latch nor the ANCHOR latch at this point. 
0x00007F5FED53E600 : 70CD 33EC 5F7F 0000 E006 54ED 5F7F 0000 
p.3._.....T._... 
0x00007F5FED53E610 : 009D 7CED 5F7F 0000 0000 0000 0000 0000 
..|._........... 
0x00007F5FED53E620 : 0000 0000 0000 0000 0000 0000 0000 0000 
................ 
0x00007F5FED53E630 : 0E00 0000 0200 0000 
........ 
  [1] 0x00007F602C77E324 sqlrlc_update_lru + 0xD4 
  [2] 0x00007F602C76EE56 sqlrlc_auth_update_entries + 0x486 
  [3] 0x00007F602C7A6EFD sqlrlc_sysuserauth_get_authPDs + 0x25D 
  [4] 0x00007F602C7A6AED sqlrlc_sysuserauth_request_auths + 
0x23D 
 
2013-12-04-11.07.35.070324-300 
EDUID   : 58                   EDUNAME: db2agent (CAT) 
FUNCTION: DB2 UDB, catcache support, sqlrlc_auth_find_insert, 
probe:709 
freeing entry:- p_entry = 0x00007f5fed53e600 p_anchor = 
0x00007f5fec33cd70 
-- CSM comes in picks up the entry from the DEFUNCT list and 
frees it. 
-- So entry is freed but added to the LRU by EDU 62 because 
-- EDU 62 called sqlrlc_update_lru() with no latch on anchor or 
lru. 
0x00007F5FED53E600 : 70CD 33EC 5F7F 0000 0000 0000 0000 0000 
p.3._........... 
0x00007F5FED53E610 : 0000 0000 0000 0000 009D 7CED 5F7F 0000 
..........|._... 
0x00007F5FED53E620 : 0000 0000 0000 0000 0000 0000 0000 0000 
................ 
0x00007F5FED53E630 : 0E00 0000 0600 0000 
........ 
  [1] 0x00007F602C7700C9 sqlrlc_csm_defunct + 0x329 
  [2] 0x00007F602C76FB16 sqlrlc_csm_processing + 0x46 
  [3] 0x00007F602C76F825 sqlrlc_check_available_memory + 0x175 
  [4] 0x00007F602C77F382 sqlrlc_find_request_usage_lock + 0x422 
  [5] 0x00007F602C7A1046 sqlrlc_systables_fetch + 0x816 
 
2013-12-04-11.07.45.596906-300 
EDUID   : 208                  EDUNAME: db2agent (CAT) 
enter function with p_anchor = 0x00007f5fec33cd70 
-- We follow the LRU list and find that entry that is now 
-- freed by CSM. 
FUNCTION: DB2 UDB, base sys utilities, sqleagnt_sigsegvh, 
probe:10 
  0x00007F6029AF19E0 sqlo_xlatch + 0x0000 
  0x00007F602C773B63 sqlrlc_csm_lru_cache + 0x00a3 
  0x00007F602C770FEC sqlrlc_csm_lru + 0x04ac 
  0x00007F602C76FC4D sqlrlc_csm_processing + 0x017d 
  0x00007F602C76F825 sqlrlc_check_available_memory + 0x0175 
  0x00007F602C7A2BE3 sqlrlc_systables_fetch_from_disk + 0x1333
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Problem Description above.                               * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 Fix Pack 4                       * 
****************************************************************
Local Fix:
Increasing CATALOGCACHE_SZ to higher value so that catalog cache 
does not overflow.
available fix packs:
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
 DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows
Solution
First fixed in DB2 Version 10.1 Fix Pack 4
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC99642 IT10249 IT10298 IT10299 IT10300 IT10303 
follow-up :
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

11.02.2014
29.07.2014
29.07.2014
Problem solved at the following versions (IBM BugInfos)


Problem solved according to the fixlist(s) of the following version(s)


10.1.0.4

FixList



10.5.0.5

FixList