Results 1 to 6 of 6
  1. #1
    Join Date
    Sep 2012
    Posts
    5

    Unanswered: DB2 Possible memory corruption detected

    Hi folks,

    I could really need your help. One of the databases was shut down because of a Possible memory corruption detected. It dumped the FODC, panic and marked the db as bad.

    EDUID : 65286 EDUNAME: db2agent (xxxxx) 0
    FUNCTION: DB2 UDB, SQO Memory Management, sqloDiagnoseFreeBlockFailure, probe:10
    MESSAGE : Possible memory corruption detected.
    DATA #1 : ZRC, PD_TYPE_ZRC, 4 bytes
    0x820F0002
    DATA #2 : Corrupt block address, PD_TYPE_CORRUPT_BLK_PTR, 8 bytes
    0x07000001a0214320
    DATA #3 : Block header, PD_TYPE_BLK_HEADER, 24 bytes
    0x07000001A0214308 : FAB0 7000 001A 0210 5F11 DF27 13DE 0076 ..p....._..'...v
    0x07000001A0214318 : FAB0 7000 001A 0210 ..p.....
    DATA #4 : Data header, PD_TYPE_BLK_DATA_HEAD, 48 bytes
    0x07000001A0214320 : 0000 0000 0000 0002 0700 0001 A021 4320 .............!C
    0x07000001A0214330 : 0700 0001 A021 4320 0000 0000 0000 0000 .....!C ........
    0x07000001A0214340 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
    CALLSTCK:
    [0] 0x09000000074C61AC pdLog + 0xC0
    [1] 0x0900000004B56F3C @79@sqloDiagnoseFreeBlockFailure__FP8SMemFBlk + 0x15C
    [2] 0x0900000003B02E08 sqlofmblkEx + 0x438
    [3] 0x09000000075381AC sqlrr_nested_cb_term__FP14sqle_nested_cbP8sqlrr_cb + 0xD8
    [4] 0x0900000007536884 sqlrr_appl_free_appl_cbs__FP8sqlrr_cbi + 0x110
    [5] 0x0900000007534D2C sqlrr_appl_term__FP8sqeAgentiP5sqlca + 0x4BC
    [6] 0x09000000033B22F0 sqlrr_appl_term__FP8sqeAgentiP5sqlca@glue189 + 0x78
    [7] 0x0900000003C71550 AppStopUsing__14sqeApplicationFP8sqeAgentUcP5sqlca + 0xEA4
    [8] 0x090000000757DF14 sqlesrspWrp__FP14db2UCinterface + 0xF4
    [9] 0x090000000757E16C sqleUCagentConnectReset + 0xCC

    2012-09-28-14.35.45.545054+060 E184658743A965 LEVEL: Critical
    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
    "xxxxxxx/dump/FODC_Panic_2012-09-28-14.35.45.543948_
    0000/". Please look in this directory for detailed evidence about
    what happened and contact IBM support if necessary to diagnose the
    problem.
    What is a way to fix this or the steps I should go through? I have heard of db2dart and inspect to check the database. Can I activate and start the database again without risk?
    Thank you in advance.

  2. #2
    Join Date
    May 2003
    Location
    USA
    Posts
    5,737
    Contact IBM support.
    M. A. Feldman
    IBM Certified DBA on DB2 for Linux, UNIX, and Windows
    IBM Certified DBA on DB2 for z/OS and OS/390

  3. #3
    Join Date
    Nov 2011
    Posts
    87
    You can try RECOVER DB then run the INSPECT.

  4. #4
    Join Date
    Aug 2008
    Location
    Toronto, Canada
    Posts
    2,367
    You do not need to recover/restore the db and don't need to run db2dart/inspect unless you really want to. Memory corruption is different from db corruption. You can restart the instance/db, but do open a pmr to investigate the crash.

  5. #5
    Join Date
    Sep 2012
    Posts
    5
    Thank you very much guys, I will contact IBM. Does the memory corruption cause no consequences when starting up the DB again? What is it usually caused from and is there nothing I can do at the moment?

    edit: I did bring the database up again, had to do db2rbind all the invalid packages. No table or tablespace pending states, it looks ok at the moment.
    Last edited by paramedic; 09-30-12 at 12:28.

  6. #6
    Join Date
    Aug 2008
    Location
    Toronto, Canada
    Posts
    2,367
    Quote Originally Posted by paramedic View Post
    Does the memory corruption cause no consequences when starting up the DB again?
    As long as crash recovery completes successfully, the db is healthy on restart.


    Quote Originally Posted by paramedic View Post
    What is it usually caused from and is there nothing I can do at the moment?
    In most cases, a db2 bug.

Posting Permissions

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