Results 1 to 3 of 3
  1. #1
    Join Date
    Apr 2008
    Location
    Colorado Springs, CO
    Posts
    2

    Unhappy Unanswered: Auto maintenance crashing DB2 9.1 fp4a Solaris 10

    Hello,

    Any time I activate any of the auto maintenance features on any db in our instance, I get errors similar to the following and the instance crashes:

    2008-04-26-10.24.27.742905-360 I6531A507 LEVEL: Error
    PID : 19571 TID : 1 PROC : db2agent (LOGAN) 0
    INSTANCE: ilaw NODE : 000 DB : LOGAN
    APPHDL : 0-158 APPID: *LOCAL.ilaw.080426162436
    AUTHID : ILAW
    FUNCTION: DB2 UDB, base sys utilities, sqleagnt_sigsegvh, probe:1
    MESSAGE : Error in agent servicing application with coor_node:
    DATA #1 : Hexdump, 2 bytes
    0xFFFFFFFF7FFE811C : 0000 ..

    2008-04-26-10.24.36.877007-360 I24905A514 LEVEL: Severe
    PID : 19571 TID : 1 PROC : db2agent (LOGAN) 0
    INSTANCE: ilaw NODE : 000 DB : LOGAN
    APPHDL : 0-158 APPID: *LOCAL.ilaw.080426162436
    AUTHID : ILAW
    FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_ffdc, probe:20
    RETCODE : ZRC=0x87120007=-2028863481=SQLR_SEVERE_PGM_ERROR
    "Severe programming error"
    DIA8516C A severe internal processing error has occurred.

    At first I thought it was runstats, because it always crashed right after attempting an auto runstats. I disabled AUTO_RUNSTATS in all dbs and restarted the instance, but next time it crashed after trying an auto reorg. If I disable AUTO_* the instance does not crash.

    I would rather enable the auto maintenance features, so if anyone can help it would be greatly appreciated. I have attached one of the logs. Thanks!

    Patrick Allen
    Attached Files Attached Files

  2. #2
    Join Date
    Jan 2007
    Location
    Jena, Germany
    Posts
    2,721
    Call IBM support. That's the only way to really get such problems tracked down and fixed for good.

    There is a simple rule: If DB2 goes down - under whichever conditions - it is a DB2 problem. Period. The usual exceptions:
    - you kill DB2 processes manually as system administrator
    - you run a buggy trusted (not fenced) routine
    Knut Stolze
    IBM DB2 Analytics Accelerator
    IBM Germany Research & Development

  3. #3
    Join Date
    Jun 2003
    Location
    Toronto, Canada
    Posts
    5,516
    Provided Answers: 1
    When you see something like this: "A severe internal processing error has occurred.", your best (and likely the only) bet will be to contact DB2 support.
    ---
    "It does not work" is not a valid problem statement.

Posting Permissions

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