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

MIGRATION FROM V8 TO V95 FAILED DUE TO ORPHAN ROWS IN SYSROUTINEAUTH

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
When orphan rows exist in SYSROUTINEAUTH, migration may fail 
with the following db2diag.log entries. 
 
2009-05-12-11.32.12.457885-240 I1804695A483 LEVEL: Warning 
PID : 962776 TID : 3125 PROC : db2sysc 0 
INSTANCE: inst1 NODE : 000 DB : GTM 
APPHDL : 0-32 APPID: *LOCAL.inst1.090512152942 
AUTHID : INST1 
EDUID : 3125 EDUNAME: db2agent (GTM ) 0 
FUNCTION: DB2 UDB, catalog migration, sqlrlm_catalog_migrate, 
probe:2912 
DATA #1 : <preformatted> 
Begin migrating catalog table: SYSROUTINEAUTH 
 
2009-05-12-11.32.13.086093-240 E1805179A618 LEVEL: Warning 
(Origin) 
PID : 962776 TID : 3125 PROC : db2sysc 0 
INSTANCE: inst1 NODE : 000 DB : GTM 
APPHDL : 0-32 APPID: *LOCAL.inst1.090512152942 
AUTHID : INST1 
EDUID : 3125 EDUNAME: db2agent (GTM ) 0 
FUNCTION: DB2 UDB, catalog migration, 
sqlrlm_8to9_sysroutineauth, 
probe:6779 
DATA #1 : String, 166 bytes 
Warning: Execute privilege has been granted on all methods of 
type GTM 
.CHANGE_I to DCHG , but that type name does not exist. This 
privilege is 
being revoked. 
 
-------Frame------ ------Function + Offset------ 
0x09000000004796BC pthread_kill + 0x88 
0x090000000431788C sqloDumpEDU + 0x24 
0x0900000003DFCC5C sqldDumpContext__FP8sqeAgentiN42PCcPvT2 + 
0x10C 
0x0900000003DFCA84 
sqldDumpContext__FP8sqeAgentiN42PCcPvT2@glueA0A + 0x94 
0x09000000041DA084 sqlrr_dump_ffdc__FP8sqlrr_cbiT2 + 0x310 
0x09000000037C442C sqlzeDumpFFDC__FP8sqeAgentUiP5sqlcai + 0x24 
0x09000000037C4270 sqlzeSqlCode__FP8sqeAgentUiUlT2P5sqlcaiUsPc + 
0x104 
0x090000000431A760 sqlrrSqlCode + 0x338 
0x0900000005BDB010 sqlrlmLogErr__FP8sqlrr_cbUiUlilPcT3 + 0x214 
0x0900000005C0F844 
sqlrlm_catalogFixup__FP8sqlrr_cbUslT3UlC17sqlrlm_catChangesPc8sq 
lr_tidP8sqlr_tid + 0x4A78 
0x0900000005C08484 sqlrlm_catalog_migrate__FP8sqeAgentsP5sqlca + 
0x436C 
0x0900000005DA0C6C sqlefmig__FPcP8SQLE_BWAP5sqlca + 0x2C 
0x0900000005C02524 sqlemigr__FP8SQLE_BWAP14db2UCinterface + 
0x1018 
0x090000000434F9F8 
sqlemigr__FP8SQLE_BWAP14db2UCinterface@glueAC3 + 0x70 
0x0900000003C825D4 
AppLocalStart__14sqeApplicationFP14db2UCinterface + 0x4AC 
0x09000000039920E8 sqlelostWrp__FP14db2UCinterface + 0x34 
0x0900000003992164 sqleUCengnInit__FP14db2UCinterfaceUs + 0x18 
0x0900000003A69F48 sqleUCagentConnect + 0x284 
0x0900000003A5FF60 
sqljsConnectAttach__FP13sqljsDrdaAsCbP14db2UCinterface + 0xE8 
0x0900000003A5F700 
sqljs_ddm_accsec__FP14db2UCinterfaceP13sqljDDMObject + 0x314 
0x0900000003A5F840 
sqljsParseConnect__FP13sqljsDrdaAsCbP13sqljDDMObjectP14db2UCinte 
rface + 0x64 
0x0900000003A5F900 
sqljsParse__FP13sqljsDrdaAsCbP14db2UCinterface + 0x24 
0x090000000397D3F0 @63@sqljsSqlam__FP14db2UCinterfaceP8sqeAgentb 
+ 0x224 
0x0900000003A46EF8 
@63@sqljsDriveRequests__FP8sqeAgentP14db2UCconHandle + 0x98 
0x0900000003A46C04 
@63@sqljsDrdaAsInnerDriver__FP18SQLCC_INITSTRUCT_Tb + 0xE0 
0x0900000003A4698C sqljsDrdaAsDriver__FP18SQLCC_INITSTRUCT_T + 
0x13C 
0x0900000003A23850 RunEDU__8sqeAgentFv + 0x11C 
0x0900000003A235B0 EDUDriver__9sqzEDUObjFv + 0x94 
0x0900000003A1E2EC sqloEDUEntry + 0x54C 
</StackTrace> 
 
One of the query could be used to determine whether there's 
duplicate rows that may cause the database migration to hit APAR 
IZ52606 
with datatypes as (select NAME, SCHEMA from SYSIBM.SYSDATATYPES) 
select RA.SCHEMA, RA.SPECIFICNAME, RA.TYPESCHEMA, RA.TYPENAME, 
RA.GRANTEE 
from SYSIBM.SYSROUTINEAUTH RA 
where RA.ROUTINETYPE = 'M' and RA.TYPENAME IS NOT NULL and 
RA.SPECIFICNAME IS NULL and 
      not exists (select NAME, SCHEMA from datatypes DT where 
DT.NAME = RA.TYPENAME and DT.SCHEMA = RA.TYPESCHEMA) 
 
with routines as (select ROUTINESCHEMA, SPECIFICNAME from 
SYSIBM.SYSROUTINES) 
select RA.SCHEMA, RA.SPECIFICNAME, RA.TYPESCHEMA, RA.TYPENAME, 
RA.GRANTEE 
from SYSIBM.SYSROUTINEAUTH RA 
where RA.ROUTINETYPE = 'M' and RA.TYPENAME IS NOT NULL and 
RA.SPECIFICNAME IS NOT NULL and 
      not exists (select R.ROUTINESCHEMA, R.SPECIFICNAME from 
routines R where R.ROUTINESCHEMA = RA.SCHEMA and R.SPECIFICNAME 
= RA.SPECIFICNAME)
Problem Summary:
Problem Description: 
MIGRATION FROM V8 TO V95 FAILED DUE TO ORPHAN ROWS IN 
SYSROUTINEAUTH 
 
Problem Summary: 
When orphan rows exist in SYSROUTINEAUTH, migration may fail 
 
with the following db2diag.log entries. 
 
2009-05-12-11.32.12.457885-240 I1804695A483 LEVEL: Warning 
PID : 962776 TID : 3125 PROC : db2sysc 0 
INSTANCE: inst1 NODE : 000 DB : GTM 
APPHDL : 0-32 APPID: *LOCAL.inst1.090512152942 
AUTHID : INST1 
EDUID : 3125 EDUNAME: db2agent (GTM ) 0 
FUNCTION: DB2 UDB, catalog migration, sqlrlm_catalog_migrate, 
probe:2912 
DATA #1 : <preformatted> 
Begin migrating catalog table: SYSROUTINEAUTH 
 
2009-05-12-11.32.13.086093-240 E1805179A618 LEVEL: Warning 
(Origin) 
PID : 962776 TID : 3125 PROC : db2sysc 0 
INSTANCE: inst1 NODE : 000 DB : GTM 
APPHDL : 0-32 APPID: *LOCAL.inst1.090512152942 
AUTHID : INST1 
EDUID : 3125 EDUNAME: db2agent (GTM ) 0 
FUNCTION: DB2 UDB, catalog migration, 
sqlrlm_8to9_sysroutineauth, 
probe:6779 
DATA #1 : String, 166 bytes 
Warning: Execute privilege has been granted on all methods of 
type GTM 
.CHANGE_I to DCHG , but that type name does not exist. This 
privilege is 
being revoked. 
 
-------Frame------ ------Function + Offset------ 
0x09000000004796BC pthread_kill + 0x88 
0x090000000431788C sqloDumpEDU + 0x24 
0x0900000003DFCC5C sqldDumpContext__FP8sqeAgentiN42PCcPvT2 + 
0x10C 
0x0900000003DFCA84 
sqldDumpContext__FP8sqeAgentiN42PCcPvT2@glueA0A + 0x94 
0x09000000041DA084 sqlrr_dump_ffdc__FP8sqlrr_cbiT2 + 0x310 
0x09000000037C442C sqlzeDumpFFDC__FP8sqeAgentUiP5sqlcai + 0x24 
0x09000000037C4270 sqlzeSqlCode__FP8sqeAgentUiUlT2P5sqlcaiUsPc + 
0x104 
0x090000000431A760 sqlrrSqlCode + 0x338 
0x0900000005BDB010 sqlrlmLogErr__FP8sqlrr_cbUiUlilPcT3 + 0x214 
0x0900000005C0F844 
sqlrlm_catalogFixup__FP8sqlrr_cbUslT3UlC17sqlrlm_catChangesPc8sq 
lr_tidP8sqlr_tid + 0x4A78 
0x0900000005C08484 sqlrlm_catalog_migrate__FP8sqeAgentsP5sqlca + 
0x436C 
0x0900000005DA0C6C sqlefmig__FPcP8SQLE_BWAP5sqlca + 0x2C 
0x0900000005C02524 sqlemigr__FP8SQLE_BWAP14db2UCinterface + 
0x1018 
0x090000000434F9F8 
sqlemigr__FP8SQLE_BWAP14db2UCinterface@glueAC3 + 0x70 
0x0900000003C825D4 
AppLocalStart__14sqeApplicationFP14db2UCinterface + 0x4AC 
0x09000000039920E8 sqlelostWrp__FP14db2UCinterface + 0x34 
0x0900000003992164 sqleUCengnInit__FP14db2UCinterfaceUs + 0x18 
0x0900000003A69F48 sqleUCagentConnect + 0x284 
0x0900000003A5FF60 
sqljsConnectAttach__FP13sqljsDrdaAsCbP14db2UCinterface + 0xE8 
0x0900000003A5F700 
sqljs_ddm_accsec__FP14db2UCinterfaceP13sqljDDMObject + 0x314 
0x0900000003A5F840 
sqljsParseConnect__FP13sqljsDrdaAsCbP13sqljDDMObjectP14db2UCinte 
rface + 0x64 
0x0900000003A5F900 
sqljsParse__FP13sqljsDrdaAsCbP14db2UCinterface + 0x24 
0x090000000397D3F0 @63@sqljsSqlam__FP14db2UCinterfaceP8sqeAgentb 
+ 0x224 
0x0900000003A46EF8 
@63@sqljsDriveRequests__FP8sqeAgentP14db2UCconHandle + 0x98 
0x0900000003A46C04 
@63@sqljsDrdaAsInnerDriver__FP18SQLCC_INITSTRUCT_Tb + 0xE0 
0x0900000003A4698C sqljsDrdaAsDriver__FP18SQLCC_INITSTRUCT_T + 
0x13C 
0x0900000003A23850 RunEDU__8sqeAgentFv + 0x11C 
0x0900000003A235B0 EDUDriver__9sqzEDUObjFv + 0x94 
0x0900000003A1E2EC sqloEDUEntry + 0x54C 
</StackTrace> 
 
One of the query could be used to determine whether there's 
duplicate rows that may cause the database migration to hit APAR 
IZ52606 
with datatypes as (select NAME, SCHEMA from SYSIBM.SYSDATATYPES) 
select RA.SCHEMA, RA.SPECIFICNAME, RA.TYPESCHEMA, RA.TYPENAME, 
RA.GRANTEE 
from SYSIBM.SYSROUTINEAUTH RA 
where RA.ROUTINETYPE = 'M' and RA.TYPENAME IS NOT NULL and 
RA.SPECIFICNAME IS NULL and 
      not exists (select NAME, SCHEMA from datatypes DT where 
DT.NAME = RA.TYPENAME and DT.SCHEMA = RA.TYPESCHEMA) 
 
with routines as (select ROUTINESCHEMA, SPECIFICNAME from 
SYSIBM.SYSROUTINES) 
select RA.SCHEMA, RA.SPECIFICNAME, RA.TYPESCHEMA, RA.TYPENAME, 
RA.GRANTEE 
from SYSIBM.SYSROUTINEAUTH RA 
where RA.ROUTINETYPE = 'M' and RA.TYPENAME IS NOT NULL and 
RA.SPECIFICNAME IS NOT NULL and 
      not exists (select R.ROUTINESCHEMA, R.SPECIFICNAME from 
routines R where R.ROUTINESCHEMA = RA.SCHEMA and R.SPECIFICNAME 
= RA.SPECIFICNAME)
Local Fix:
n/a
available fix packs:
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 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
Problem is first fixed in Version 9.7 Fixpack 4
Workaround
n/a
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
14.06.2010
29.04.2011
29.04.2011
Problem solved at the following versions (IBM BugInfos)
9.7.FP4
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.4 FixList