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

DB2INIDB DOES NOT HANDLE ALL THE CONFIGURATION OPTIONS WHICH ARE VALID FOR
DB2RELOCATEDB

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
db2inidb does not handle all the configuration options which are 
valid for db2relocatedb.  The documentation for db2inidb points 
 
you to the db2relocatedb for the configuration files.  So it 
should handle them. 
 
If the configuration file contains any of the following the 
instance will trap: 
 
FAILARCHIVE_PATH 
LOGARCHMETH1 
LOGARCHMETH2 
MIRRORLOG_PATH 
OVERFLOWLOG_PATH 
 
db2diag.log 
 
2011-02-25-14.20.15.337564+060 I24720E433          LEVEL: 
Warning 
PID     : 26678                TID  : 47101861947712PROC : 
db2sysc 0 
INSTANCE: db2bw2               NODE : 000          DB   : BW2 
APPHDL  : 0-7                  APPID: *LOCAL.db2bw2.110225131942 
AUTHID  : DB2BW2 
EDUID   : 24                   EDUNAME: db2agent (BW2) 0 
FUNCTION: DB2 UDB, base sys utilities, sqledint, probe:30 
MESSAGE : Crash Recovery is needed. 
 
2011-02-25-14.20.21.214554+060 I25154E481          LEVEL: Error 
PID     : 26678                TID  : 47101861947712PROC : 
db2sysc 0 
INSTANCE: db2bw2               NODE : 000          DB   : BW2 
APPHDL  : 0-7                  APPID: *LOCAL.db2bw2.110225131942 
AUTHID  : DB2BW2 
EDUID   : 24                   EDUNAME: db2agent (BW2) 0 
FUNCTION: DB2 UDB, buffer pool services, sqlbStartPools, probe:5 
DATA #1 : String, 14 bytes 
Suspend Action 
DATA #2 : unsigned integer, 4 bytes 
2 
 
2011-02-25-14.21.02.073752+060 I25636E517          LEVEL: Severe 
PID     : 26678                TID  : 47101861947712PROC : 
db2sysc 0 
INSTANCE: db2bw2               NODE : 000          DB   : BW2 
APPHDL  : 0-7                  APPID: *LOCAL.db2bw2.110225131942 
AUTHID  : DB2BW2 
EDUID   : 24                   EDUNAME: db2agent (BW2) 0 
FUNCTION: DB2 UDB, buffer pool services, 
sqlbProcessPathRenameCfgFile, probe:120 
DATA #1 : String, 32 bytes 
SEVERE ERROR: Invalid line type. 
DATA #2 : unsigned integer, 4 bytes 
10 
 
2011-02-25-14.21.02.097389+060 E26154E907          LEVEL: 
Critical 
PID     : 26678                TID  : 47101861947712PROC : 
db2sysc 0 
INSTANCE: db2bw2               NODE : 000          DB   : BW2 
APPHDL  : 0-7                  APPID: *LOCAL.db2bw2.110225131942 
AUTHID  : DB2BW2 
EDUID   : 24                   EDUNAME: db2agent (BW2) 0 
FUNCTION: DB2 UDB, RAS/PD component, pdStartFODC, 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 
 
"/db2/BW2/db2dump/FODC_Panic_2011-02-25-14.21.02.082058/". 
Please 
          look in this directory for detailed evidence about 
what happened and 
          contact IBM support if necessary to diagnose the 
problem. 
 
2011-02-25-14.21.02.143920+060 I27062E534          LEVEL: Severe 
PID     : 26678                TID  : 47101861947712PROC : 
db2sysc 0 
INSTANCE: db2bw2               NODE : 000          DB   : BW2 
APPHDL  : 0-7                  APPID: *LOCAL.db2bw2.110225131942 
AUTHID  : DB2BW2 
EDUID   : 24                   EDUNAME: db2agent (BW2) 0 
FUNCTION: DB2 UDB, buffer pool services, sqlb_panic, probe:20 
RETCODE : ZRC=0x87020002=-2029912062=SQLB_BPSE "Debug logic 
error detected" 
          DIA8501C A buffer pool logic error has occurred. 
 
2011-02-25-14.21.02.150133+060 I27597E446          LEVEL: Severe 
PID     : 26678                TID  : 47101861947712PROC : 
db2sysc 0 
INSTANCE: db2bw2               NODE : 000          DB   : BW2 
APPHDL  : 0-7                  APPID: *LOCAL.db2bw2.110225131942 
AUTHID  : DB2BW2 
EDUID   : 24                   EDUNAME: db2agent (BW2) 0 
FUNCTION: DB2 UDB, buffer pool services, sqlb_panic, probe:20 
MESSAGE : Severe error in buffer pool services 
 
 
======================================== 
26678.24.000.trap.txt: 
 
<Header> 
DB2 build information: DB2 v9.7.0.2 special_24281 SQL09072 
timestamp: 2011-02-25-14.21.02.213346 
instance name: db2bw2.000 
EDU name     : db2agent (BW2) 0 
EDU ID       : 24 
Signal #6 
uname: S:Linux R:2.6.16.60-0.57.1-smp V:#1 SMP Tue Nov 3 
11:21:35 UTC 2009 M:x86_64 N:mm75ff 
process id: 26678 
thread id : 47101861947712 (0x2AD6C1BFE940) 
</Header> 
<SignalDetails> 
<Siginfo_t length="128"> 
06000000 00000000 FAFFFFFF 0A81FFFF 
36680000 480E0000 A9D51980 FFFFFFFF 
08000000 00000000 08000000 00000000 
80C49012 1881FFFF 477C1880 FFFFFFFF 
00000000 00000000 C01A4400 0C81FFFF 
80145EA6 0F81FFFF ACE91380 FFFFFFFF 
F077BDC1 D62A0000 01000000 00000000 
00000000 00000000 8073C1C6 D62A0000 
</Siginfo_t> 
Signal #6 (SIGABRT): si_pid is 26678, si_uid is 3656, si_value 
is 8019D5A9 
</SignalDetails> 
... 
<StackTrace> 
-----FUNC-ADDR---- ------FUNCTION + OFFSET------ 
0x00002AD6AE9B198F ossDumpStackTraceEx + 0x01ef 
(/home_sap/db2bw2/sqllib/lib64/libdb2osse.so.1) 
0x00002AD6AE9AC756 _ZN11OSSTrapFile6dumpExEmiP7siginfoPvm + 
0x00cc (/home_sap/db2bw2/sqllib/lib64/libdb2osse.so.1) 
0x00002AD6ABC5E910 sqlo_trce + 0x040a 
(/home_sap/db2bw2/sqllib/lib64/libdb2e.so.1) 
0x00002AD6ABCA3025 sqloEDUCodeTrapHandler + 0x023d 
(/home_sap/db2bw2/sqllib/lib64/libdb2e.so.1) 
0x00002AD6A92A4D60 address: 0x00002AD6A92A4D60 ; dladdress: 
0x00002AD6A9297000 ; offset in lib: 0x000000000000DD60 ; 
(/lib64/libpthread.so.0) 
0x00002AD6AF2C1F45 gsignal + 0x0035 (/lib64/libc.so.6) 
0x00002AD6AF2C3340 abort + 0x0110 (/lib64/libc.so.6) 
0x00002AD6AA7BA4FD sqloExitEDU + 0x014d 
(/home_sap/db2bw2/sqllib/lib64/libdb2e.so.1) 
0x00002AD6AB0AEDA3 _Z10sqle_panicv + 0x00ab 
(/home_sap/db2bw2/sqllib/lib64/libdb2e.so.1) 
0x00002AD6AAEB79CD sqlb_panic + 0x003b 
(/home_sap/db2bw2/sqllib/lib64/libdb2e.so.1) 
0x00002AD6AAED8769 sqlbProcessPathRenameCfgFile + 0x02a7 
(/home_sap/db2bw2/sqllib/lib64/libdb2e.so.1) 
0x00002AD6AA2E1B49 sqlbinit + 0x0bf1 
(/home_sap/db2bw2/sqllib/lib64/libdb2e.so.1) 
0x00002AD6AA3D5C19 address: 0x00002AD6AA3D5C19 ; dladdress: 
0x00002AD6A93B0000 ; offset in lib: 0x0000000001025C19 ; 
(/home_sap/db2bw2/sqllib/lib64/libdb2e.so.1) 
0x00002AD6AA3D38C9 
_ZN16sqeLocalDatabase12FirstConnectEP8SQLE_BWARcP8sqeAgentP8sqlo 
_gmtii 
+ 0x0d49 (/home_sap/db2bw2/sqllib/lib64/libdb2e.so.1) 
0x00002AD6AA3CB41A 
_ZN8sqeDBMgr23StartUsingLocalDatabaseEP8SQLE_BWAP8sqeAgentRccP8s 
qlo_gmt 
+ 0x0c8a (/home_sap/db2bw2/sqllib/lib64/libdb2e.so.1) 
0x00002AD6AA3B500F 
_ZN14sqeApplication13AppStartUsingEP8SQLE_BWAP8sqeAgentccP5sqlca 
Pc 
+ 0x0209 (/home_sap/db2bw2/sqllib/lib64/libdb2e.so.1) 
0x00002AD6AA3B1302 address: 0x00002AD6AA3B1302 ; dladdress: 
0x00002AD6A93B0000 ; offset in lib: 0x0000000001001302 ; 
(/home_sap/db2bw2/sqllib/lib64/libdb2e.so.1) 
0x00002AD6AA3B0134 
_ZN14sqeApplication13AppLocalStartEP14db2UCinterface + 0x01b8 
(/home_sap/db2bw2/sqllib/lib64/libdb2e.so.1) 
0x00002AD6AA40B94D _Z11sqlelostWrpP14db2UCinterface + 0x001d 
(/home_sap/db2bw2/sqllib/lib64/libdb2e.so.1) 
0x00002AD6AA40D0B4 _Z14sqleUCengnInitP14db2UCinterfacet + 0x0530 
    (/home_sap/db2bw2/sqllib/lib64/libdb2e.so.1) 
0x00002AD6AA40BF83 sqleUCagentConnect + 0x02c1 
(/home_sap/db2bw2/sqllib/lib64/libdb2e.so.1) 
0x00002AD6AA49BDBE 
_Z18sqljsConnectAttachP13sqljsDrdaAsCbP14db2UCinterface + 0x0092 
(/home_sap/db2bw2/sqllib/lib64/libdb2e.so.1) 
0x00002AD6AA479E3F 
_Z16sqljs_ddm_accsecP14db2UCinterfaceP13sqljDDMObject + 0x007f 
(/home_sap/db2bw2/sqllib/lib64/libdb2e.so.1) 
0x00002AD6AA471496 
_Z17sqljsParseConnectP13sqljsDrdaAsCbP13sqljDDMObjectP14db2UCint 
erface 
+ 0x0068 (/home_sap/db2bw2/sqllib/lib64/libdb2e.so.1) 
0x00002AD6AA4719B7 
_Z10sqljsParseP13sqljsDrdaAsCbP14db2UCinterfaceP8sqeAgentb + 
0x035b (/home_sap/db2bw2/sqllib/lib64/libdb2e.so.1) 
0x00002AD6AA467116 address: 0x00002AD6AA467116 ; dladdress: 
0x00002AD6A93B0000 ; offset in lib: 0x00000000010B7116 ; 
(/home_sap/db2bw2/sqllib/lib64/libdb2e.so.1) 
0x00002AD6AA46DFBC address: 0x00002AD6AA46DFBC ; dladdress: 
0x00002AD6A93B0000 ; offset in lib: 0x00000000010BDFBC ; 
(/home_sap/db2bw2/sqllib/lib64/libdb2e.so.1) 
0x00002AD6AA46B985 address: 0x00002AD6AA46B985 ; dladdress: 
0x00002AD6A93B0000 ; offset in lib: 0x00000000010BB985 ; 
(/home_sap/db2bw2/sqllib/lib64/libdb2e.so.1) 
0x00002AD6AA46B6E3 _Z17sqljsDrdaAsDriverP18SQLCC_INITSTRUCT_T + 
0x0111 (/home_sap/db2bw2/sqllib/lib64/libdb2e.so.1) 
0x00002AD6AA3A6DBB _ZN8sqeAgent6RunEDUEv + 0x09f3 
(/home_sap/db2bw2/sqllib/lib64/libdb2e.so.1) 
0x00002AD6AAA316B0 _ZN9sqzEDUObj9EDUDriverEv + 0x00a6 
(/home_sap/db2bw2/sqllib/lib64/libdb2e.so.1) 
0x00002AD6AAA31607 _Z10sqlzRunEDUPcj + 0x0009 
(/home_sap/db2bw2/sqllib/lib64/libdb2e.so.1) 
0x00002AD6AA7BAC9F sqloEDUEntry + 0x02e9 
(/home_sap/db2bw2/sqllib/lib64/libdb2e.so.1) 
0x00002AD6A929D193 address: 0x00002AD6A929D193 ; dladdress: 
0x00002AD6A9297000 ; offset in lib: 0x0000000000006193 ; 
(/lib64/libpthread.so.0) 
0x00002AD6AF352DFD __clone + 0x006d (/lib64/libc.so.6) 
</StackTrace>
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All Platforms                                                * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* db2inidb does not handle all the configuration options which * 
* are                                                          * 
* valid for db2relocatedb.                                     * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 V9.7 Fix Pack 5.                              * 
****************************************************************
Local Fix:
Remove any of the following options from the configuration file, 
and look to update the database after the db2inidb completes. 
 
FAILARCHIVE_PATH 
LOGARCHMETH1 
LOGARCHMETH2 
MIRRORLOG_PATH 
OVERFLOWLOG_PATH
available fix packs:
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 9 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
Solution
This problem was first fixed in DB2 V9.7 Fix Pack 5.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

03.03.2011
27.12.2011
27.12.2011
Problem solved at the following versions (IBM BugInfos)
9.7.FP5
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.5 FixList