Results 1 to 5 of 5
  1. #1
    Join Date
    Sep 2006
    Posts
    105

    Unanswered: db went down every hour

    Hi all

    we are using DB2 V8.1 and Fixpak 6 and os-AIX 5.2.We are facing a problem like our databse instance is down every hour and from the db2diag.logs, i could see the following error...
    2007-02-28-01.39.54.313598 Instance:dumclp1 Node:000
    PID:2109578(db2agent (instance) 0) TID:1 Appid:GA721C6E.PA05.013508014200
    base sys utilities sqleattach_agent Probe:60 Database:MCL01P1


    2007-02-28-05.00.10.650672 Instance:dumclp1 Node:000
    PID:2109578(db2agent (MCL01P1) 0) TID:1 Appid:GA6DA619.C438.002D98045717
    base sys utilities sqleagnt_sigsegvh Probe:1 Database:MCL01P1

    Error in agent servicing application with coor_node:
    0x0FFFFFFFFFFF3600 : 0x0000 ..

    2007-02-28-05.00.24.866073 Instance:dumclp1 Node:000
    PID:2109578(db2agent (MCL01P1) 0) TID:1 Appid:GA6DA619.C438.002D98045717
    base sys utilities sqleagnt_sigsegvh Probe:2 Database:MCL01P1

    Error in agent servicing application with coor_agent_index:
    0x0FFFFFFFFFFF3602 : 0x0281 ..

    2007-02-28-05.00.24.959073 Instance:dumclp1 Node:000
    PID:2109578(db2agent (MCL01P1) 0) TID:1 Appid:GA6DA619.C438.002D98045717
    base sys utilities sqleagnt_sigsegvh Probe:3 Database:MCL01P1

    Error in agent servicing application with CLIENT PID:
    0x0FFFFFFFFFFF3618 : 3636 3236 34 66264

    2007-02-28-05.00.24.964498 Instance:dumclp1 Node:000
    PID:2109578(db2agent (MCL01P1) 0) TID:1 Appid:GA6DA619.C438.002D98045717
    base sys utilities sqleagnt_sigsegvh Probe:4 Database:MCL01P1

    Error in agent servicing application with INBOUND APPLICATION ID:
    0x000000011003AF93 : 4741 3644 4136 3139 2E43 3433 382E 3030 GA6DA619.C438.00
    db2diag.log (19%)


    2007-02-28-05.00.24.970115 Instance:dumclp1 Node:000
    PID:2109578(db2agent (MCL01P1) 0) TID:1 Appid:GA6DA619.C438.002D98045717
    base sys utilities sqleagnt_sigsegvh Probe:5 Database:MCL01P1

    Error in agent servicing application with INBOUND SEQUENCE NUMBER:
    0x000000011003AFB4 : 0x0001 ..

    2007-02-28-05.00.24.975732 Instance:dumclp1 Node:000
    PID:2109578(db2agent (MCL01P1) 0) TID:1 Appid:GA6DA619.C438.002D98045717
    base sys utilities sqleagnt_sigsegvh Probe:6 Database:MCL01P1

    Error in agent servicing application with OUTBOUND APPLICATION ID:

    2007-02-28-05.00.24.980011 Instance:dumclp1 Node:000
    PID:2109578(db2agent (MCL01P1) 0) TID:1 Appid:GA6DA619.C438.002D98045717
    base sys utilities sqleagnt_sigsegvh Probe:7 Database:MCL01P1

    Error in agent servicing application with OUTBOUND SEQUENCE NUMBER:

    2007-02-28-05.00.24.984003 Instance:dumclp1 Node:000
    PID:2109578(db2agent (MCL01P1) 0) TID:1 Appid:GA6DA619.C438.002D98045717
    base sys utilities sqleagnt_sigsegvh Probe:8 Database:MCL01P1

    Error in agent servicing application with AUTHORIZATION ID:
    0x07800000001D6C65 : 4443 544D 5F44 4220 0000 0000 0000 0000 DCTM_DB ........
    0x07800000001D6C75 : 0000 0000 0000 0000 0000 0000 0000 00 ...............

    2007-02-28-05.00.24.989338 Instance:dumclp1 Node:000
    PID:2109578(db2agent (MCL01P1) 0) TID:1 Appid:GA6DA619.C438.002D98045717
    base sys utilities sqleagnt_sigsegvh Probe:9 Database:MCL01P1

    Error in agent servicing application with PRODUCT SIGNATURE:
    0x07800000001D6E88 : 0x53514C3038303136 SQL08016

    2007-02-28-05.00.24.994618 Instance:dumclp1 Node:000
    PID:2109578(db2agent (MCL01P1) 0) TID:1 Appid:GA6DA619.C438.002D98045717
    base sys utilities sqleagnt_sigsegvh Probe:10 Database:MCL01P1

    Error in agent servicing application with APPLICATION NAME:
    0x07800000001D6E5E : 646F 6375 6D65 6E74 756D documentum

    2007-02-28-05.00.25.014507 Instance:dumclp1 Node:000
    PID:2109578(db2agent (MCL01P1) 0) TID:1 Appid:GA6DA619.C438.002D98045717
    oper system services sqloEDUCodeTrapHandler Probe:10 Database:MCL01P1

    ADM0503C An unexpected internal processing error has occurred. ALL DB2
    PROCESSES ASSOCIATED WITH THIS INSTANCE HAVE BEEN SHUTDOWN. Diagnostic
    information has been recorded. Contact IBM Support for further assistance.

    2007-02-28-05.00.25.053871 Instance:dumclp1 Node:000
    PID:2109578(db2agent (MCL01P1) 0) TID:1 Appid:GA6DA619.C438.002D98045717
    oper system services sqloEDUCodeTrapHandler Probe:20 Database:MCL01P1

    Signal number received

    0x0FFFFFFFFFFF3730 : 0x0000000A ....

    PID:2109578 TID:1 Node:000 Title: siginfo_t...

    0x0FFFFFFFFFFF3A20 : 0000 000A 0000 0000 0000 0009 0000 0000 ................
    0x0FFFFFFFFFFF3A30 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
    0x0FFFFFFFFFFF3A40 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
    0x0FFFFFFFFFFF3A50 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

    2007-02-28-05.00.25.081306 Instance:dumclp1 Node:000
    PID:2109578(db2agent (MCL01P1) 0) TID:1 Appid:GA6DA619.C438.002D98045717
    relation data serv sqlrr_signal_handler Probe:50 Database:MCL01P1

    DIA0505I Execution of a component signal handling function has begun.


    PID:2109578 TID:1 Node:000 Title: SQLCA
    sqlcaid : SQLCA sqlcabc: 136 sqlcode: 0 sqlerrml: 0
    sqlerrmc:
    sqlerrp : SQL08016
    sqlerrd : (1) 0x00000000 (2) 0x00000000 (3) 0x00000000
    (4) 0x00000000 (5) 0x00000000 (6) 0x00000000
    sqlwarn : (1) (2) (3) (4) (5) (6)
    (7) (8) (9) (10) (11)
    sqlstate:

    PID:2109578 TID:1 Node:000 Title: SQLCA
    Dump File:/home/dumclp1/sqllib/db2dump/21095781.000


    PID:2109578 TID:1 Node:000 Title: CONTEXT MEM CB
    Dump File:/home/dumclp1/sqllib/db2dump/21095781.000

    PID:2109578 TID:1 Node:000 Title: PACKAGE ENTRY
    Dump File:/home/dumclp1/sqllib/db2dump/21095781.000

    PID:2109578 TID:1 Node:000 Title: CACHED PACKAGE ENTRY
    Dump File:/home/dumclp1/sqllib/db2dump/21095781.000

    Any help...

    Thanks and Regards
    Meena.s

  2. #2
    Join Date
    Aug 2001
    Location
    UK
    Posts
    4,650
    Its hard to tell ...

    Appears that db2 processes are being killed ...

    Is there any resouce governors running at the OS level ... like - when a process consumes more than x% of CPU, then 'kill' it ...

    Just my thought

    Sathyaram
    Visit the new-look IDUG Website , register to gain access to the excellent content.

  3. #3
    Join Date
    Jan 2007
    Location
    Jena, Germany
    Posts
    2,721
    You get a segmentation violation in the db2agent process. Unless someone sends signal 11 to that process, it is a bug in DB2 and all you can do is to open a PMR and get it fixed that way.
    Knut Stolze
    IBM DB2 Analytics Accelerator
    IBM Germany Research & Development

  4. #4
    Join Date
    May 2003
    Location
    USA
    Posts
    5,737
    Quote Originally Posted by stolze
    You get a segmentation violation in the db2agent process. Unless someone sends signal 11 to that process, it is a bug in DB2 and all you can do is to open a PMR and get it fixed that way.
    Most likely IBM support will suggest a higher fixpack. FP 6 about 2.5 years old.
    M. A. Feldman
    IBM Certified DBA on DB2 for Linux, UNIX, and Windows
    IBM Certified DBA on DB2 for z/OS and OS/390

  5. #5
    Join Date
    Jan 2007
    Location
    Jena, Germany
    Posts
    2,721
    Yeah, FP14 is the most current one. Upgrading is the first choice, of course.
    Knut Stolze
    IBM DB2 Analytics Accelerator
    IBM Germany Research & Development

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •