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

db2 backup database DBname online use TSM will hang.

product:
DB2 FOR LUW / DB2FORLUW / 980 - DB2
Problem description:
db2 backup database DBname online use TSM will hang because of 
the following reason. 
 
db2vend will loop , if db2vend can not attach specified address. 
 
Found db2vend is looping. 
From db2trc.flw 
pid = 9765096 tid = 1 node = -1 
 
714792        53.159179048   | sqloChangeName entry 
714793        53.159180757   | | sqloChangeProcessName entry 
714794        53.159182720   | | sqloChangeProcessName data 
[probe 5] 
714794  data DB2 UDB oper system services sqloChangeProcessName 
cei (3.3.15.116.2.5) 
        pid 9765096 tid 1 cpid -1 node -1 sec 53 nsec 159182720 
probe 5 
        bytes 43 
 
        Data1   (PD_TYPE_STRING,35) String: 
        db2vend (db2med - 38603 (SAMPLE)) 0 0 
 
714795        53.159183681   | | sqloChangeProcessName exit 
714796        53.159184798   | sqloChangeName exit 
 
714811        53.159294583   | sqlocshr errtrans [probe 180] [ 
OSERRNO = 22 -->  ZRC = 0x850F00C4 = -2062614332 = 
SQLO_ADDR_CONFLICT ] 
2011-02-01-14.05.27.466367+540 I37656A890           LEVEL: Error 
(OS) 
PID     : 9765096              TID  : 1             PROC : 
db2vend (db2med - 38603 (SAMPLE)) 
INSTANCE: db2inst1              NODE : 000 
EDUID   : 1                    EDUNAME: db2vend (db2med - 38603 
(TPCC)) 
FUNCTION: DB2 UDB, SQO Memory Management, sqlocshr, probe:180 
MESSAGE : ZRC=0x850F00C4=-2062614332=SQLO_ADDR_CONFLICT 
          "An address space conflict was detected attaching to 
shared memory." 
CALLED  : OS, -, shmat 
OSERR   : EINVAL (22) "Invalid argument" 
DATA #1 : Memory set handle, PD_TYPE_OSS_MEM_SET_HDL, 48 bytes 
0x0FFFFFFFFFFFEAD0 : 0A00 0200 2000 0000 0A00 0200 2000 0000 
.... ....... ... 
0x0FFFFFFFFFFFEAE0 : 0000 0000 0000 0000 0000 0000 0000 0000 
................ 
0x0FFFFFFFFFFFEAF0 : 0000 0000 7329 0000 0020 0015 0001 0000 
....s)... ...... 
DATA #2 : Pointer, 8 bytes 
0x0a00020020000000 
 
714950        53.161282673   DB2VEND_main data [probe 1060] 
2011-02-01-14.05.27.467939+540 I38547A461           LEVEL: Event 
PID     : 9765096              TID  : 1             PROC : 
db2vend (db2med - 38603 (SAMPLE)) 
INSTANCE: db2inst1              NODE : 000 
EDUID   : 1                    EDUNAME: db2vend (db2med - 38603 
(SAMPLE)) 
FUNCTION: DB2 UDB, oper system services, DB2VEND_main, 
probe:1060 
MESSAGE : Process must re-exec due to address space conflicts. 
DATA #1 : String, 32 bytes 
/home/db2inst1/sqllib/bin/db2vend 
 
714951        53.161284417   | | | sqloclose entry 
714952        53.161298271   | | | sqloclose exit 
714953        53.161300101   | | | sqloSigMask entry 
714954        53.161302236   | | | sqloSigMask exit 
714955        53.161302986   | | | sqloSigMask entry 
714956        53.161304566   | | | sqloSigMask exit 
714957        53.161305171   | | pdLogInternal exit 
714958        53.161305705   | pdLogRC exit 
714985        53.200666708   | sqloGetEnvInternal entry 
714986        53.200676572   | sqloGetEnvInternal exit [rc = 
0x870F0104 = -2029059836 = RC_ENV_NOT_FOUND] 
714987        53.200695179   | DB2VEND_main entry // 2nd try.... 
716375        53.272203177   | | DB2VEND_main data [probe 1060] 
716376        53.272204533   | | | | | sqloclose entry 
716377        53.272216314   | | | | | sqloclose exit 
716378        53.272217580   | | | | | sqloSigMask entry 
716379        53.272219484   | | | | | sqloSigMask exit 
716380        53.272219986   | | | | | sqloSigMask entry 
716381        53.272221306   | | | | | sqloSigMask exit 
716382        53.272221666   | | | | pdLogInternal exit 
716383        53.272222236   | | | pdLogRC exit 
716447        53.313609972   | | | sqloGetEnvInternal entry 
716448        53.313619658   | | | sqloGetEnvInternal exit [rc = 
0x870F0104 = -2029059836 = RC_ENV_NOT_FOUND] 
716449        53.313638826   | | | DB2VEND_main entry // 3rd 
try... 
Infinit Loop... 
 
Collected truss and found the following. 
 
7471118:        65470541: 2.2534:        shmat(7340051, 
0x0A00020020000000, 0) Err#22 EINVAL 
7471118:        65470541: 2.2536:        shmat(7340051, 
0x0000000000000000, 0) = 0x0A00030000000000 
7471118:        65470541: 2.2539: 
shmdt(0x0A00030000000000) = 0 
7471118:        65470541: 2.4490:        shmget(-1879043968, 
664, 8624) = 9 
7471118:        65470541: 2.4492:        shmat(9, 
0x0000000000000000, 0) = 0x0A00020000000000 
7471118:        65470541: 2.4494:        shmat(10, 
0x0000000000000000, 0) = 0x0A00020010000000 
7471118:        65470541: 2.4497:        shmat(11, 
0x0000000000000000, 0) = 0x0A00020020000000 
7471118:        65470541: 2.6015:        shmget(1182522484, 0, 
0) = 12 
7471118:        65470541: 2.6017:        shmat(12, 
0x0770000000000000, 8192) = 0x0770000000000000 
7471118:        65470541: 2.6537:        shmat(5283, 
0x0000000000000000, 6144) = 0x0A00030000000000 
7471118:        65470541: 2.6589:        shmat(5286, 
0x0000000000000000, 6144) = 0x0A00030010000000 
7471118:        65470541: 2.6592: 
shmdt(0x0A00030000000000) = 0 
7471118:        65470541: 2.6596: 
shmdt(0x0A00030010000000) = 0 
7471118:        65470541: 2.6607:        shmat(5283, 
0x0000000000000000, 6144) = 0x0A00030000000000 
7471118:        65470541: 2.6609:        shmat(5286, 
0x0000000000000000, 6144) = 0x0A00030010000000 
7471118:        65470541: 2.6612: 
shmdt(0x0A00030000000000) = 0 
7471118:        65470541: 2.6616: 
shmdt(0x0A00030010000000) = 0 
7471118:        65470541: 2.6921:        shmat(7340051, 
0x0A00020020000000, 0) Err#22 EINVAL 
7471118:        65470541: 2.6923:        shmat(7340051, 
0x0000000000000000, 0) = 0x0A00030000000000 
7471118:        65470541: 2.6925: 
shmdt(0x0A00030000000000) = 0 
7471118:        65470541: 2.8819:        shmget(-1879043968, 
664, 8624) = 9 
7471118:        65470541: 2.8821:        shmat(9, 
0x0000000000000000, 0) = 0x0A00020000000000 
7471118:        65470541: 2.8823:        shmat(10, 
0x0000000000000000, 0) = 0x0A00020010000000 
 
Calling shmat with 0 then returned address 0x0A00020020000000. 
Same base address of db2vend was used , then EINVAL was 
occurred.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* First Fixed in DB2 9.8 Fix Pack 4                            * 
****************************************************************
Local Fix:
Create dummy database,then activate dummy database.
available fix packs:
DB2 Version 9.8 Fix Pack 5 for AIX and Linux
DB2 Version 9.8 Fix Pack 4 for AIX and Linux

Solution
First Fixed in DB2 9.8 Fix Pack 4
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
14.02.2011
09.05.2017
09.05.2017
Problem solved at the following versions (IBM BugInfos)
9.8.FP4
Problem solved according to the fixlist(s) of the following version(s)
9.8.0.4 FixList