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

A PANIC MAY OCCUR AFTER ISSUING DB2STOP FORCE ON HADR STANDBY WHILE
TAKEOVER HADR DB OPERATION IS IN PROGRESS

product:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problem description:
Running db2 takeover hadr on db on a standby machine followed by 
db2 stop force before the takeover command completes 
successfully can cause memory to be freed twice. This would lead 
to a panic in the system. This APAR can only occur on DB2 9.5 
FP7. 
 
2010-11-25-17.42.00.931548-300 I68908668E377       LEVEL: 
Warning 
PID     : 21039                TID  : 47382024677696PROC : 
db2sysc 
INSTANCE: svtdbm               NODE : 000 
EDUID   : 310                  EDUNAME: db2hadrp (SAKE) 
FUNCTION: DB2 UDB, High Availability Disaster Recovery, 
hdrSDoTakeover, probe:47003 
MESSAGE : Info: Standby has completed takeover (now primary). 
 
2010-11-25-17.42.00.944158-300 I68909046E342       LEVEL: 
Warning 
PID     : 21039                TID  : 47382024677696PROC : 
db2sysc 
INSTANCE: svtdbm               NODE : 000 
EDUID   : 310                  EDUNAME: db2hadrp (SAKE) 
FUNCTION: DB2 UDB, High Availability Disaster Recovery, hdrEduS, 
probe:20342 
MESSAGE : Info: Standby Finished. 
 
2010-11-25-17.42.00.945189-300 I68909389E553       LEVEL: 
Warning 
PID     : 21039                TID  : 47381592664384PROC : 
db2sysc 
INSTANCE: svtdbm               NODE : 000          DB   : SAKE 
APPHDL  : 0-28727              APPID: *LOCAL.svtdbm.101126110514 
AUTHID  : SVTDBM 
EDUID   : 630                  EDUNAME: db2agent (SAKE) 
FUNCTION: DB2 UDB, base sys utilities, 
sqeAgentServices::RequestAgent, probe:12 
MESSAGE : Coordinator request rejected. 
DATA #1 : Hexdump, 4 bytes 
0x00002B17E2FE9400 : 0700 0000 
.... 
 
2010-11-25-17.42.00.948897-300 I68909943E461       LEVEL: Error 
PID     : 21039                TID  : 47381592664384PROC : 
db2sysc 
INSTANCE: svtdbm               NODE : 000          DB   : SAKE 
APPHDL  : 0-28727              APPID: *LOCAL.svtdbm.101126110514 
AUTHID  : SVTDBM 
EDUID   : 630                  EDUNAME: db2agent (SAKE) 
FUNCTION: DB2 UDB, base sys utilities, 
sqeAgentServices::RequestAgent, probe:70 
MESSAGE : Agent not allocated, sqlcode = -6036 
 
2010-11-25-17.42.00.950313-300 E68910405E495       LEVEL: 
Warning 
PID     : 21039                TID  : 47381592664384PROC : 
db2sysc 
INSTANCE: svtdbm               NODE : 000          DB   : SAKE 
APPHDL  : 0-28727              APPID: *LOCAL.svtdbm.101126110514 
AUTHID  : SVTDBM 
EDUID   : 630                  EDUNAME: db2agent (SAKE) 
FUNCTION: DB2 UDB, base sys utilities, 
sqeAgentServices::RequestAgent, probe:100 
MESSAGE : ADM7519W  DB2 could not allocate an agent.  The 
SQLCODE is "-6036". 
 
2010-11-25-17.42.00.954150-300 I68910901E456       LEVEL: Severe 
PID     : 21039                TID  : 47381592664384PROC : 
db2sysc 
INSTANCE: svtdbm               NODE : 000          DB   : SAKE 
APPHDL  : 0-28727              APPID: *LOCAL.svtdbm.101126110514 
AUTHID  : SVTDBM 
EDUID   : 630                  EDUNAME: db2agent (SAKE) 
FUNCTION: DB2 UDB, base sys utilities, 
sqeIcoordCB::DispatchIndependentDBAgent, probe:110 
RETCODE : ZRC=0xFFFFE86C=-6036 
 
2010-11-25-17.42.00.955750-300 I68911358E544       LEVEL: Error 
PID     : 21039                TID  : 47381592664384PROC : 
db2sysc 
INSTANCE: svtdbm               NODE : 000          DB   : SAKE 
APPHDL  : 0-28727              APPID: *LOCAL.svtdbm.101126110514 
AUTHID  : SVTDBM 
EDUID   : 630                  EDUNAME: db2agent (SAKE) 
FUNCTION: DB2 UDB, High Availability Disaster Recovery, 
hdrSpawnICoord, probe:30100 
MESSAGE : HADR ICoord Error: 
DATA #1 : Hexdump, 4 bytes 
0x00002B17E2FEA9B0 : 6D00 0580 
m... 
 
2010-11-25-17.42.00.957140-300 I68911903E533       LEVEL: Error 
PID     : 21039                TID  : 47381592664384PROC : 
db2sysc 
INSTANCE: svtdbm               NODE : 000          DB   : SAKE 
APPHDL  : 0-28727              APPID: *LOCAL.svtdbm.101126110514 
AUTHID  : SVTDBM 
EDUID   : 630                  EDUNAME: db2agent (SAKE) 
FUNCTION: DB2 UDB, High Availability Disaster Recovery, 
hdrSpawnICoord, probe:30101 
MESSAGE : sqlcode: 
DATA #1 : Hexdump, 4 bytes 
0x00002B17E2FEA9F0 : 6CE8 FFFF 
l... 
 
2010-11-25-17.42.00.958549-300 I68912437E558       LEVEL: 
Warning 
PID     : 21039                TID  : 47381592664384PROC : 
db2sysc 
INSTANCE: svtdbm               NODE : 000          DB   : SAKE 
APPHDL  : 0-28727              APPID: *LOCAL.svtdbm.101126110514 
AUTHID  : SVTDBM 
EDUID   : 630                  EDUNAME: db2agent (SAKE) 
FUNCTION: DB2 UDB, High Availability Disaster Recovery, 
hdrTakeoverHdrRouteIn, probe:55603 
 
RETCODE : ZRC=0x8005006D=-2147155859=SQLE_CA_BUILT 
          "SQLCA has been built and saved in component specific 
control block." 
 
2010-11-25-17.42.00.954201-300 I68912996E341       LEVEL: 
Warning 
PID     : 21039                TID  : 47382024677696PROC : 
db2sysc 
INSTANCE: svtdbm               NODE : 000 
EDUID   : 310                  EDUNAME: db2hadrp (SAKE) 
FUNCTION: DB2 UDB, High Availability Disaster Recovery, hdrEduP, 
probe:20301 
MESSAGE : Info: Primary Started. 
 
2010-11-25-17.42.00.965391-300 I68913338E389       LEVEL: 
Warning 
PID     : 21039                TID  : 47382024677696PROC : 
db2sysc 
INSTANCE: svtdbm               NODE : 000 
EDUID   : 310                  EDUNAME: db2hadrp (SAKE) 
FUNCTION: DB2 UDB, High Availability Disaster Recovery, 
hdrSetTcpWindowSize, probe:32201 
MESSAGE : Info: HADR Socket send buffer size, SO_SNDBUF: 16384 
bytes 
 
2010-11-25-17.42.00.966825-300 I68913728E392       LEVEL: 
Warning 
PID     : 21039                TID  : 47382024677696PROC : 
db2sysc 
INSTANCE: svtdbm               NODE : 000 
EDUID   : 310                  EDUNAME: db2hadrp (SAKE) 
FUNCTION: DB2 UDB, High Availability Disaster Recovery, 
hdrSetTcpWindowSize, probe:32251 
MESSAGE : Info: HADR Socket receive buffer size, SO_RCVBUF: 
87380 bytes 
 
2010-11-25-17.42.00.965075-300 I68914121E1738      LEVEL: Severe 
PID     : 21039                TID  : 47381592664384PROC : 
db2sysc 
INSTANCE: svtdbm               NODE : 000          DB   : SAKE 
APPHDL  : 0-28727              APPID: *LOCAL.svtdbm.101126110514 
AUTHID  : SVTDBM 
EDUID   : 630                  EDUNAME: db2agent (SAKE) 
FUNCTION: DB2 UDB, SQO Memory Management, 
sqloDiagnoseFreeBlockFailure, probe:10 
MESSAGE : Possible memory corruption detected. 
DATA #1 : ZRC, PD_TYPE_ZRC, 4 bytes 
0x820F0002 
DATA #2 : Corrupt block address, PD_TYPE_CORRUPT_BLK_PTR, 8 
bytes 
0x00002b1789615100 
DATA #3 : Block header, PD_TYPE_BLK_HEADER, 24 bytes 
0x00002B17896150E8 : 1596 78B1 0200 B0FA 0000 0000 0000 0000 
..x............. 
0x00002B17896150F8 : 0000 0000 0000 0000 
........ 
DATA #4 : Data header, PD_TYPE_BLK_DATA_HEAD, 48 bytes 
0x00002B1789615100 : 8000 0000 0000 0000 DDDD DDDD DDDD DDDD 
................ 
0x00002B1789615110 : DDDD DDDD DDDD DDDD DDDD DDDD DDDD DDDD 
................ 
CALLSTCK: 
  [0] 0x00002B1761A3CEEC pdLog + 0x18C 
  [1] 0x00002B1763F7042A /home/svtdbm/sqllib/lib64/libdb2e.so.1 
+ 0x382E42A 
  [2] 0x00002B1763F70F52 sqlofmblkEx + 0x130 
  [3] 0x00000000004147B6 _Z9sqlofmblkPv + 0x18 
  [4] 0x00002B1763EE040A sqlo_acs_fblk + 0x1C 
  [5] 0x00002B176259A889 
_Z26sqlexAgentCleanUserSecInfoP16SQLEX_AUTHINFO_TP5sqlca + 0xA3 
  [6] 0x00002B1762385917 
_ZN14sqeApplication12AppStopUsingEP8sqeAgenthP5sqlca + 0xF67 
  [7] 0x00002B1762532B3C _Z11sqlesrspWrpP14db2UCinterface + 
0x2D8 
  [8] 0x00002B176253306D sqleUCagentConnectReset + 0x17D 
  [9] 0x00002B17626B852C /home/svtdbm/sqllib/lib64/libdb2e.so.1 
+ 0x1F7652C 
 
2010-11-25-17.42.00.976550-300 I68915860E456       LEVEL: Severe 
PID     : 21039                TID  : 47381592664384PROC : 
db2sysc 
INSTANCE: svtdbm               NODE : 000          DB   : SAKE 
APPHDL  : 0-28727              APPID: *LOCAL.svtdbm.101126110514 
AUTHID  : SVTDBM 
EDUID   : 630                  EDUNAME: db2agent (SAKE) 
FUNCTION: DB2 UDB, SQO Memory Management, 
sqloDiagnoseFreeBlockFailure, probe:30 
DATA #1 : String, 12 bytes 
Double free. 
 
2010-11-25-17.42.00.978148-300 E68916317E928       LEVEL: 
Critical 
PID     : 21039                TID  : 47381592664384PROC : 
db2sysc 
INSTANCE: svtdbm               NODE : 000          DB   : SAKE 
APPHDL  : 0-28727              APPID: *LOCAL.svtdbm.101126110514 
AUTHID  : SVTDBM 
EDUID   : 630                  EDUNAME: db2agent (SAKE) 
FUNCTION: DB2 UDB, base sys utilities, sqle_panic, probe:10 
MESSAGE : ADM14001C  An unexpected and critical error has 
occurred: "Panic". 
          The instance may have been shutdown as a result. 
"Automatic" FODC 
          (First Occurrence Data Capture) has been invoked and 
diagnostic 
          information has been recorded in directory 
 
"/home/svtdbm/sqllib/db2dump/FODC_Panic_2010-11-25-17.42.00.9780 
28/". 
          Please look in this directory for detailed evidence 
about what 
          happened and contact IBM support if necessary to 
diagnose the 
          problem.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* HADR environments                                            * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Running db2 takeover hadr on db on a standby machine         * 
* followed by                                                  * 
* db2 stop force before the takeover command completes         * 
*                                                              * 
* successfully can cause memory to be freed twice. This would  * 
* lead                                                         * 
* to a panic in the system. This APAR can only occur on DB2    * 
* 9.5                                                          * 
* FP7.                                                         * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 9.5 FP8 or higher                             * 
****************************************************************
Local Fix:
Don't issue db2stop force on standby instance while HADR 
takeover database operation is being performed.
available fix packs:
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
 DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
 DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows
Solution
The fix to avoid the double free of memory in this situation is 
included in DB2 9.5 FP8.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

22.02.2011
27.06.2011
27.06.2011
Problem solved at the following versions (IBM BugInfos)
9.5.FP8
Problem solved according to the fixlist(s) of the following version(s)
9.5.0.8 FixList