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

DB2 INSTANCE CRASHED IN DPF WHEN APPLICATION USES XML HOST VARIABLES

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
DB2 instance crashed during an "insert from select with xml host 
variable". 
 
INSERT INTO security (SECSYM, SDOC) 
SELECT T.SECSYM, T.SDOC FROM 
XMLTABLE('declare default element namespace 
"http://tpox-benchmark.com/security";$SDOC' passing xmlcast(? as 
xml) as "SDOC" 
         COLUMNS 
            "SECSYM"  VARCHAR(15) PATH '*:Security/*:Symbol', 
            "SDOC"    XML         PATH '.') AS T 
 
This happens because in DPF we try to collect rids for the XML 
document being bound in through the APPLICATION host variable 
and we record these rids in all subsections running on 
coordinator node which finally results in a bad page error 
during other operations. 
 
In db2diag.log, the first "severe" entry is this: 
 
2010-06-07-17.25.40.554291-240 I2116A4348         LEVEL: Severe 
PID     : 6471896              TID  : 9770        PROC : db2sysc 
0 
INSTANCE: kxie                 NODE : 000         DB   : 
TPOX_DSS 
APPHDL  : 0-255                APPID: 
9.26.119.79.4505.100607212534 
AUTHID  : KXIE 
EDUID   : 9770                 EDUNAME: db2agntp (TPOX_DSS) 0 
FUNCTION: DB2 UDB, Common Trace API, sqlbfix, probe:104 
DATA #1 : String, 45 bytes 
bfix detected an error - Current Descriptor = 
DATA #2 : Buffer page descriptor, PD_TYPE_SQLB_BPD, 152 bytes 
  Pagekey: {pool:1;obj:4;type:134} PPNum:9 
  objectPageNum:                         9 
  bucketGroupHashIndex:               1594 
  hashnext:             0x0000000000000000 
  hashprev:             0x0000000000000000 
  osslatch: 
{ 
   state         = 0x0000000000000001 
                 = { 
                       held X: 0 
                       reserved for X: 0 
                       shared holders: 1 
                       firstSharIndex: 0x0 
                       firstExclIndex: 0x0 
                   } 
   starve X mode = true 
   xWaitCount    = 0 
   requestCount  = 0 
   identity      = SQLB_BPD::bpdLatch (42) 
} 
  UFlags:                                3 
  pageStatusFlag:                        0 
  permanentState:                        0 
  transientState:                        0 
  fixcount:                              1 
  bpp:                  0x0700000035bb8000 
  pinCount: 
0x0700000033A76F60 : 0000 0000 
.... 
  weight:       02 
  dirtyprev:            0x0700000033a76480 
  dirtynext:            0x0700000033a779b0 
  blockDesc:            0x0000000000000000 
  pminlsn:              0000000000000000 
  hatenext:             0x0000000000000000 
  hateprev:             0x0000000000000000 
  onWhichHateList:                   65535 
  permanentHateList:                     5 
  newbpdidx:                    3221225472 
  diskRelativePageID:                         9 
DATA #3 : String, 18 bytes 
Current PageHead = 
DATA #4 : Page header, PD_TYPE_SQLB_PAGE_HEAD, 48 bytes 
pageHead: {tbspSeed:1;obj:4;type:134} PPNum:9 OPNum:9 
  begoff:                      48 
  datlen:                   32720 
  pagebinx:                  1045 
  revnum:                    1280 
  pagelsn:     0607172540552370  flag:                         2 
  future32:                    0 
  cbits1to31:                   0 
  cbits32to63:                  0 
DATA #5 : String, 7 bytes 
FixCB = 
DATA #6 : Fix control block, PD_TYPE_SQLB_FIX_CB, 168 bytes 
  accessMethod:  SQLB_POOL_RELATIVE 
  fixMode:                        2   SQLBOLD/SQLBOLDS 
  buffptr:       0x0000000000000000 
  bpdPtr:        0x0000000000000000 
  dmDebugHdl:                     0 
  objectPageNum:                  9 
  empDiskPageNum:         4294967295 
  unfixFlags:                     0 
  dirtyState:    SQLBCLEAN 
  fixInfoFlags: 
  regEDUid:      0 
  Pagekey: {pool:1;obj:4;type:134} PPNum:9 
      Obj: {pool:1;obj:4;type:134} Parent={1;4} 
  lifeLSN:       0607172540552370 
  tid:           0 0  0 
  extentAnchor:                   0 
  initEmpPages:                   0 
  poolPage0:                      0 
  poolflags:                   1111 
  objectState:                   27 
  lastSMP:                        0 
  pageSize:                   32768 
  extentSize:                    32 
  bufferPoolID:                   1 
  partialHash:           2248409089 
  bufferPool:    0x0700000033798100 
  pdef:          0x0700000033b03a60 
  glob:          0x0000000111251300 
DATA #7 : String, 21 bytes 
PageHead from FixCB = 
DATA #8 : Page header, PD_TYPE_SQLB_PAGE_HEAD, 48 bytes 
pageHead: {tbspSeed:1;obj:4;type:134} PPNum:9 OPNum:9 
  begoff:                      48 
  datlen:                   32720 
  pagebinx:                  1045 
  revnum:                    1280 
  pagelsn:     0607172540552370  flag:                         2 
  future32:                    0 
  cbits1to31:                   0 
  cbits32to63:                  0 
DATA #9 : String, 15 bytes 
Tablespace ID = 
DATA #10: Pool ID, PD_TYPE_SQLB_POOL_ID, 2 bytes 
1 
DATA #11: String, 17 bytes 
Tablsepace Seed = 
DATA #12: Pool ID, PD_TYPE_SQLB_POOL_ID, 2 bytes 
0 
DATA #13: String, 29 bytes 
Address of Descriptor Array = 
DATA #14: Pointer, 8 bytes 
0x070000003379a520 
DATA #15: String, 29 bytes 
Address of Current Descriptor 
DATA #16: Pointer, 8 bytes 
0x0700000033a76f18 
 
Stacks 
 
<StackTrace> 
-------Frame------ ------Function + Offset------ 
0x09000000004AF6BC pthread_kill + 0x88 
0x090000000B21456C sqloDumpEDU + 0x54 
0x090000000BF25EC4 sqle_panic__Fv + 0x94 
0x090000000B215190 sqlb_panic + 0xD8 
0x090000000C203394 sqlb_panic@glue52F + 0x78 
0x090000000AE4AABC sqlbufix__FP11SQLB_FIX_CBcT2 + 0xAD0 
0x090000000B4382E4 xmls_MustResetWorkAreas__FP11XMLSTORE_CB + 
0x120 
0x090000000D58DA3C 
xmlrnTransportToXDMAddNextChunk__19XmlrnTransportToXDMFPcRUi + 
0x680 
0x090000000D5DDCD0 
nonTradObjectUnpackNextChunk__23@88@XmlrnTransportToXDMFPcRUi + 
0xC 
0x090000000D332F54 
sqlkt_unpack_tuple__FP9sqlri_taoPiT2P5sqlcaPUiT5 + 0x8C 
0x090000000D3632E0 sqlktftc__FP8sqeAgentP9sqlri_taoP5sqlcaPUiT4 
+ 0x808 
0x090000000D36218C sqlritqa__FP8sqlrr_cb + 0x1FC 
0x090000000B8A55CC sqlriSectInvoke__FP8sqlrr_cbP12sqlri_opparm + 
0x63C 
0x090000000C677D2C sqlrr_dss_router__FP8sqlrr_cb + 0x34 
0x090000000C406134 
sqlrr_subagent_router__FP8sqeAgentP12SQLE_DB2RA_T + 0x5C4 
0x090000000C804208 sqleSubRequestRouter__FP8sqeAgentPUiT2 + 
0x5F0 
0x090000000C8012C0 sqleProcessSubRequest__FP8sqeAgent + 0x71C 
0x090000000C36118C RunEDU__8sqeAgentFv + 0x318 
0x090000000B6EE15C EDUDriver__9sqzEDUObjFv + 0x100 
0x090000000B6F2EBC sqloEDUEntry + 0x278 
</StackTrace> 
 
<StackTrace> 
-------Frame------ ------Function + Offset------ 
0x09000000004AF6BC pthread_kill + 0x88 
0x09000000004AF0D0 _p_raise + 0x68 
0x090000000005D298 raise + 0x34 
0x0900000000088DAC abort + 0xB4 
0x090000000C74CAA8 abort@glue746 + 0x90 
0x090000000C74BBD0 sqloExitEDU + 0xB0 
0x090000000BE53AAC sqle_panic__Fv + 0x8 
0x090000000B215190 sqlb_panic + 0xD8 
0x090000000C203394 sqlb_panic@glue52F + 0x78 
0x090000000AE4AABC sqlbufix__FP11SQLB_FIX_CBcT2 + 0xAD0 
0x090000000B4382E4 xmls_MustResetWorkAreas__FP11XMLSTORE_CB + 
0x120 
0x090000000D58DA3C 
xmlrnTransportToXDMAddNextChunk__19XmlrnTransportToXDMFPcRUi + 
0x680 
0x090000000D5DDCD0 
nonTradObjectUnpackNextChunk__23@88@XmlrnTransportToXDMFPcRUi + 
0xC 
0x090000000D332F54 
sqlkt_unpack_tuple__FP9sqlri_taoPiT2P5sqlcaPUiT5 + 0x8C 
0x090000000D3632E0 sqlktftc__FP8sqeAgentP9sqlri_taoP5sqlcaPUiT4 
+ 0x808 
0x090000000D36218C sqlritqa__FP8sqlrr_cb + 0x1FC 
0x090000000B8A55CC sqlriSectInvoke__FP8sqlrr_cbP12sqlri_opparm + 
0x63C 
0x090000000C677D2C sqlrr_dss_router__FP8sqlrr_cb + 0x34 
0x090000000C406134 
sqlrr_subagent_router__FP8sqeAgentP12SQLE_DB2RA_T + 0x5C4 
0x090000000C804208 sqleSubRequestRouter__FP8sqeAgentPUiT2 + 
0x5F0 
0x090000000C8012C0 sqleProcessSubRequest__FP8sqeAgent + 0x71C 
0x090000000C36118C RunEDU__8sqeAgentFv + 0x318 
0x090000000B6EE15C EDUDriver__9sqzEDUObjFv + 0x100 
0x090000000B6F2EBC sqloEDUEntry + 0x278 
</StackTrace>
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 LUW ALL                                                  * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Refer to the APAR Error description.                         * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to v97 FP3.                                          * 
****************************************************************
Local Fix:
available fix packs:
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 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a 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
Fix available in v97 FP3 and future releases.
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC70186 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
23.07.2010
23.09.2010
23.09.2010
Problem solved at the following versions (IBM BugInfos)
9.7.FP3
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.3 FixList
9.7.0.3 FixList