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

DB2 MAY CRASH ON VIEW GENERATION AUTH CHECK.

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
In the trap file, a similar stack trace will be generated: 
 
<StackTrace> 
-----FUNC-ADDR---- ------FUNCTION + OFFSET------ 
0x00002AAAB045718F ossDumpStackTraceEx + 0x01ef 
0x00002AAAB0451F4E _ZN11OSSTrapFile6dumpExEmiP7siginfoPvm + 
0x00cc 
0x00002AAAAD39E21F sqlo_trce + 0x03fb 
0x00002AAAAD3E73DF sqloEDUCodeTrapHandler + 0x02db 
0x0000003F05A0ECA0 address: 0x0000003F05A0ECA0 ; dladdress: 
0x0000003F05A00000 ; offset in lib: 0x000000000000ECA0 ; 
0x00002AAAADA0D896 
_Z35sqlrlBuildTableOrViewAuthsRPCBufferP8sqlrr_cbPhsS1_sshiPsitb 
b11sqlr_aainfoP13SQLO_MEM_POOLPjPS1_b + 0x00ee 
0x00002AAAADA0EB5D 
_Z8sqlrlguaP8sqlrr_cbPhsS1_sshi11sqlr_aainfoP13SQLO_MEM_POOLP10s 
qlr_rolesbPsitbbPP9sqlrg_tadPib + 0x0935 
0x00002AAAACBA9E92 
_Z16sqlnn_auth_checkccP13SQLNQ_UPD_FCSPPjS1_PsPiS4_Pmi + 0x1154 
0x00002AAAACFE04B2 
_Z21sqlnq_view_finish_qgmP9sqlnq_qunbPmRP9sqlrg_tadRiS5_PjPS6_ + 
0x0838 
0x00002AAAACFE5262 _Z25sqlnq_ddl_create_view_endP9sqlnq_qtbPm + 
0x0170 
0x00002AAAACBB36B4 
_Z16sqlnn_regen_viewPhsS_sS_sS_sbP17sqlrl_table_parmsPbS2_S2_b + 
0x13aa 
0x00002AAAADA5DE24 
_Z16sqlrl_regen_viewP8sqlrr_cbPhsS1_sS1_sS1_ssbP17sqlrl_table_pa 
rmsPbS4_b + 0x058e 
0x00002AAAABCE8796 
_Z26sqlnq_check_referenced_qtbPP9sqlnq_qtbP9sqlnq_qunP3loc21sqln 
q_hierarchy_usage + 0x0c24 
0x00002AAAABCE7806 
_Z27sqlnq_handle_from_table_refP20sqlnq_multipart_namePhiPP9sqln 
q_qunP9sqlnq_qtbP3locP9sqlnq_opr21sqlnq_hierarchy_usagePP8stknod 
e_ + 0x00ee 
0x00002AAAAE14F7BF _Z9sqlnq_semPP8stknode_i10actiontypePhP3loc + 
0x120c1 
0x00002AAAAE132228 _Z12sqlnp_smactnP8sqlnp_cbi + 0x094c 
0x00002AAAABBABBF2 _Z12sqlnp_parserP8sqlnp_cb + 0x092e 
0x00002AAAABBAD3FE 
_Z10sqlnp_mainP12sqlnq_stringbP3locPP9sqlnq_qur + 0x02ba 
0x00002AAAABB227D1 
_Z10sqlnn_cmplP8sqeAgentP11sqlrrstrings17sqlnn_compileModesP14sq 
lrr_cmpl_enviiPP9sqlnq_qur + 0x0c27 
0x00002AAAABB21BA5 
_Z10sqlnn_cmplP8sqeAgentP11sqlrrstrings17sqlnn_compileModesP14sq 
lrr_cmpl_env + 0x0021 
0x00002AAAABE9A311 
_Z17sqlra_compile_varP8sqlrr_cbP14sqlra_cmpl_envPhitiiiiiP14SQLP 
_LOCK_INFOP16sqlra_cached_varPiPm + 0x0771 
0x00002AAAABEA6BEB 
_Z14sqlra_find_varP8sqlrr_cbP17sqlra_cached_stmt13sqlra_stmt_idj 
jPhjthP14sqlra_cmpl_env15sqlra_fill_modePiiS8_iiiS8_P14SQLP_LOCK 
_INFOPP16sqlra_cached_varS8_Pmb + 0x05df 
0x00002AAAABED01A8 _Z13sqlra_get_varP8sqlrr_cbiibPbS1_ + 0x0860 
0x00002AAAAD5B1EDD 
_Z13sqlrr_prepareP14db2UCinterfaceP16db2UCprepareInfo + 0x036d 
0x00002AAD5558EB56 sqlacall + 0x5af2 
0x00002AAD0B1CF7A1 address: 0x00002AAD0B1CF7A1 ; dladdress: 
0x00002AAD0B157000 ; offset in lib: 0x00000000000787A1 ; 
0x00002AAD0B1CC223 admin_revalidate_db_objects + 0x0b97 
0x00002AAAABD87E80 sqloInvokeFnArgs + 0x0040 
0x00002AAAABF4C862 
_Z19sqlriInvokerTrustedP10sqlri_ufobP21sqlriRoutineErrorIntfb + 
0x065e 
0x00002AAAABF46056 _Z9sqlricallP8sqlrr_cb + 0x0eee 
0x00002AAAAE18716E _Z15sqlriSectInvokeP8sqlrr_cbP12sqlri_opparm 
+ 0x013e 
0x00002AAAABE58C0D _Z29sqlrr_process_execute_requestP8sqlrr_cbib 
+ 0x07bf 
0x00002AAAABE50F19 _Z13sqlrr_executeP14db2UCinterfaceP9UCstpInfo 
+ 0x060f 
0x00002AAAAC4D18F9 _ZN10pvmPackage14executeSectionEP5sqlcajb + 
0x073b 
0x00002AAAAC4D3657 _ZN3PVM12executeQueryEjb + 0x0049 
0x00002AAAAC4D91E0 _ZN3PVM3runEv + 0x0828 
0x00002AAAAC4DD706 pvm_entry + 0x01d6 
0x00002AAAABD87E80 sqloInvokeFnArgs + 0x0040 
0x00002AAAABF4E801 
_Z19sqlriInvokerTrustedP10sqlri_ufobP21sqlriRoutineErrorIntfb + 
0x25fd 
0x00002AAAABF46056 _Z9sqlricallP8sqlrr_cb + 0x0eee 
0x00002AAAAE18716E _Z15sqlriSectInvokeP8sqlrr_cbP12sqlri_opparm 
+ 0x013e 
0x00002AAAABE58C0D _Z29sqlrr_process_execute_requestP8sqlrr_cbib 
+ 0x07bf 
0x00002AAAABE50F19 _Z13sqlrr_executeP14db2UCinterfaceP9UCstpInfo 
+ 0x060f 
0x00002AAAABA5A975 
_Z19sqljs_ddm_excsqlsttP14db2UCinterfaceP13sqljDDMObject + 
0x04e7 
0x00002AAAAE11E0E3 
_Z21sqljsParseRdbAccessedP13sqljsDrdaAsCbP13sqljDDMObjectP14db2U 
Cinterface + 0x007d 
0x00002AAAABA4369F 
_Z10sqljsParseP13sqljsDrdaAsCbP14db2UCinterfaceP8sqeAgentb + 
0x035b 
0x00002AAAABA37A6B address: 0x00002AAAABA37A6B ; dladdress: 
0x00002AAAAAABD000 ; offset in lib: 0x0000000000F7AA6B ; 
0x00002AAAABA3CF35 address: 0x00002AAAABA3CF35 ; dladdress: 
0x00002AAAAAABD000 ; offset in lib: 0x0000000000F7FF35 ; 
0x00002AAAABA3A83C address: 0x00002AAAABA3A83C ; dladdress: 
0x00002AAAAAABD000 ; offset in lib: 0x0000000000F7D83C ; 
0x00002AAAABA3A5AA _Z17sqljsDrdaAsDriverP18SQLCC_INITSTRUCT_T + 
0x0102 
0x00002AAAAB96A7C6 _ZN8sqeAgent6RunEDUEv + 0x0a74 
0x00002AAAAC067CE4 _ZN9sqzEDUObj9EDUDriverEv + 0x00a6 
0x00002AAAAC067C3B _Z10sqlzRunEDUPcj + 0x0009 
0x00002AAAABDC6424 sqloEDUEntry + 0x02f4 
0x0000003F05A0683D address: 0x0000003F05A0683D ; dladdress: 
0x0000003F05A00000 ; offset in lib: 0x000000000000683D ; 
0x0000003F052D500D clone + 0x006d 
</StackTrace> 
 
In db2diag.log, messages similar to these regarding a view 
generation and a consequent trap sustainability: 
2015-04-24-14.04.50.157914-240 I33565956E656       LEVEL: Error 
PID     : 28713                TID  : 46922878413120PROC : 
db2sysc 1 
INSTANCE: db2inst1             NODE : 001          DB   : 
DB_TST1 
APPHDL  : 1-24371              APPID: 
10.37.81.44.58678.150424150944 
AUTHID  : db2user 
EDUID   : 42584                EDUNAME: db2agent (DB_TST1) 1 
FUNCTION: DB2 UDB, catalog services, sqlrl_regen_view, probe:80 
MESSAGE : SQLRL_REGEN_VIEW: Failure in regenerating view 
DATA #1 : Hexdump, 29 bytes 
0x00002AAD157E46F8 : 0000 0000 0000 0000 0000 0000 0000 0000 
USER_SCHEMA.VIE 
0x00002AAD157E4708 : 0000 0000 0000 0000 0000 0000 59 
W_TESTE 
 
2015-04-24-14.04.50.196149-240 I33566613E726       LEVEL: Error 
PID     : 28713                TID  : 46922878413120PROC : 
db2sysc 1 
INSTANCE: db2inst1             NODE : 001          DB   : 
DB_TST1 
APPHDL  : 1-24371              APPID: 
10.37.81.44.58678.150424150944 
AUTHID  : db2user 
EDUID   : 42584                EDUNAME: db2agent (DB_TST1) 1 
FUNCTION: DB2 UDB, catalog services, sqlrl_regen_view, probe:80 
MESSAGE : SQLRL_REGEN_VIEW: Failure in regenerating view 
DATA #1 : Hexdump, 34 bytes 
0x00002AAD157E46F8 : 0000 0000 0000 0000 0000 0000 0000 0000 
USER_SCHEMA.VIEW 
0x00002AAD157E4708 : 0000 0000 0000 0000 0000 0000 0000 0000 
_TESTXXXXXXXXXXX 
0x00002AAD157E4718 : 0000 
XX 
. 
. 
. 
2015-04-24-14.04.51.079292-240 I33577252E650       LEVEL: Error 
PID     : 28713                TID  : 46922878413120PROC : 
db2sysc 1 
INSTANCE: db2inst1             NODE : 001          DB   : 
DB_TST1 
APPHDL  : 1-24371              APPID: 
10.37.81.44.58678.150424150944 
AUTHID  : db2user 
EDUID   : 42584                EDUNAME: db2agent (DB_TST1) 1 
FUNCTION: DB2 UDB, catalog services, sqlrl_regen_view, probe:80 
MESSAGE : SQLRL_REGEN_VIEW: Failure in regenerating view 
DATA #1 : Hexdump, 23 bytes 
0x00002AAD157E46F8 : 0000 0000 0000 0000 0000 0000 0000 0000 
USER_SCHEMA.VIEW 
0x00002AAD157E4708 : 0000 0000 0000 00 
_TESTXX 
 
2015-04-24-14.04.51.396021-240 I33577903E573       LEVEL: Severe 
PID     : 28713                TID  : 46922878413120PROC : 
db2sysc 1 
INSTANCE: db2inst1             NODE : 001          DB   : 
DB_TST1 
APPHDL  : 1-24371              APPID: 
10.37.81.44.58678.150424150944 
AUTHID  : db2user 
EDUID   : 42584                EDUNAME: db2agent (DB_TST1) 1 
FUNCTION: DB2 UDB, RAS/PD component, 
pdResilienceIsSafeToSustain, probe:800 
DATA #1 : String, 37 bytes 
Trap Sustainability Criteria Checking 
DATA #2 : Hex integer, 8 bytes 
0x0000000400071401 
DATA #3 : Boolean, 1 bytes 
false 
. 
. 
. 
2015-04-24-14.04.51.399769-240 I33579628E574       LEVEL: Error 
PID     : 28713                TID  : 46922878413120PROC : 
db2sysc 1 
INSTANCE: db2inst1             NODE : 001          DB   : 
DB_TST1 
APPHDL  : 1-24371              APPID: 
10.37.81.44.58678.150424150944 
AUTHID  : db2user 
EDUID   : 42584                EDUNAME: db2agent (DB_TST1) 1 
FUNCTION: DB2 UDB, base sys utilities, sqleagnt_sigsegvh, 
probe:3 
MESSAGE : Error in agent servicing application with CLIENT PID: 
DATA #1 : Hexdump, 4 bytes 
0x00002AAD1500F460 : 3736 3638 
7668 
 
2015-04-24-14.04.51.399834-240 I33580203E678       LEVEL: Error 
PID     : 28713                TID  : 46922878413120PROC : 
db2sysc 1 
INSTANCE: db2inst1             NODE : 001          DB   : 
DB_TST1 
APPHDL  : 1-24371              APPID: 
10.37.81.44.58678.150424150944 
AUTHID  : db2user 
EDUID   : 42584                EDUNAME: db2agent (DB_TST1) 1 
FUNCTION: DB2 UDB, base sys utilities, sqleagnt_sigsegvh, 
probe:4 
MESSAGE : Error in agent servicing application with INBOUND 
APPLICATION ID: 
DATA #1 : Hexdump, 30 bytes 
0x000000020D406830 : 3130 2E33 372E 3831 2E34 342E 3538 3637 
10.37.81.44.5867 
0x000000020D406840 : 382E 3135 3034 3234 3135 3039 3434 
8.150424150944 
 
This APAR will prevent the consequent crash in the database.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 v9.7 FP11                                     * 
****************************************************************
Local Fix:
Solution
Upgrade to DB2 v9.7 FP11
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
18.05.2015
03.11.2015
03.11.2015
Problem solved at the following versions (IBM BugInfos)
9.7.FP11
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.11 FixList