Skip to Content
avatar image
Former Member

Data check fails

Hello!

On this system, a maxdb 7.5.00.32 (32bit) the data check (db-verify from SAP perspective) fails.

How do I perform further analysis? The below extract is from knldiag.err on the system

//Fredrik

server:/sapdb/data/wrk/SID # more knldiag.err | grep CHECK | tail -10

2008-06-01 08:12:12 23586 ERR 53000 CHECK Check data finished unsuccessfully

2008-06-05 14:31:38 23590 ERR 53019 CHECK Base error: file_not_accessibl

2008-06-05 14:31:38 23590 ERR 53019 CHECK Root pageNo: 4533025

2008-06-05 21:15:03 23590 ERR 53000 CHECK Check data finished unsuccessfully

2008-06-08 00:32:30 23586 ERR 53019 CHECK Base error: file_not_accessibl

2008-06-08 00:32:30 23586 ERR 53019 CHECK Root pageNo: 4533025

2008-06-08 08:45:37 23586 ERR 53000 CHECK Check data finished unsuccessfully

2008-06-09 10:59:29 23590 ERR 53019 CHECK Base error: file_not_accessibl

2008-06-09 10:59:29 23590 ERR 53019 CHECK Root pageNo: 4533025

2008-06-09 15:11:39 23590 ERR 53000 CHECK Check data finished unsuccessfully

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Best Answer
    Jun 09, 2008 at 02:43 PM

    Hi Frederik,

    just follow notes

    #26837 MaxDB: Datenkorruption

    --> how to handle corruptions and get rid of them

    #839333 FAQ: MaxDB Fehler-Diagnose-> korrupte Daten-Pages

    --> if you really want to "further" analyze the corruption.

    The bottomline is simple:

    1. Find out which database objects are "behind" the root-numbers.

    2. As long as only indexes are affected - you can just rebuild them and you're done

    3. As soon as a table is affected, you better know where you put your last backup...

    KR Lars

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hello Lars!

      Thanks for your reply. This issue was solved by running "recreate" via DBMGUI => Recovery => Index => recreate (all).

      //Fredrik