From: Strahl, Torsten (torsten.strahlsap.com)
Date: Mon Apr 19 2004 - 01:56:33 CDT

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Hi Robson,
the error "file_not_accessible" means that you have a corrupted
index, which is not usable by the sql optimzer, perhaps this will
be a loss of performance. The index is identified by the root 15034.

Connect as systemdba and execute the following sql statement:
select * from roots where root = 15034

The result is the name of the index. Drop the index and rebuild it.
The next check data will not report this index as not accessible.

Note that indexes will be set to not accessible
- if the database kernel detects an inconsistency within the index or
- during a recovery, which contains "create index" log entries or
- during the upgrade from 7.3 to 7.4/7.5. if you have a single index
  with null values.

BTW:
"Check data" (db_state online) and "Check data with update" (db_state admin)
are doing the same checks. But "Check data with update" will removed unused
pages from the converter - if they exist - and the "check data with update"
was okay until now. Unreferenced pages in the converter could exist for example
if you stop the database during a huge drop table or drop index job.

Regards,
Torsten

SAP DB, SAP Labs Berlin

-----Original Message-----
From: Robson Paniago [mailto:rpdmirandahotmail.com]
Sent: Montag, 19. April 2004 01:06
To: maxdblists.mysql.com
Subject: Strange database erros

Hello,

I'm running MaxDB 7.5.0.8 in a Windows XP, after upgrading from MaxDB
7.5.0.5. After the upgrade process, I did a database structure check, and
I'm getting these erros in knldiagerr:
2004-04-18 20:02:59 0xAD4 ERR 53019 CHECK Base error: file_not_accessibl
2004-04-18 20:02:59 0xAD4 ERR 53019 CHECK Root pageNo: 15034
2004-04-18 20:03:01 0xAD4 ERR 53000 CHECK Check data finished unsuccessfully

If I check the database while in ADMIN mode, I also get
2004-04-18 19:59:24 0xAD4 ERR 53019 CHECK Base error:
file_not_accessibl
2004-04-18 19:59:24 0xAD4 ERR 53019 CHECK Root pageNo: 15034
2004-04-18 19:59:25 0xAD4 ERR 53000 CHECK Check data finished
unsuccessfully
2004-04-18 19:59:25 0xAD4 ERR 51080 SYSERROR -9041 BD Index not
accessible

I think this was not coused by the backup, since I did also a check in a
7.5.05 machine here, with a backup of the same database, and got the same
erros.

Is there something I can do? All indices marked as bad were recreated before
the check.

Thanks,
    Robson Paniago

--
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe: http://lists.mysql.com/maxdb?unsub=torsten.strahlsap.com

--
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]