Re: oncheck -cI
- From: "jda" <adamski@xxxxxxxxxxxxx>
- Date: 27 Feb 2006 12:22:45 -0800
Final update on this thread (I hope and pray):
Over the weekend I tried to dbexport our database and the dbexport
failed with the following errors when it got to systabauth
*** load table ***
-211 - Cannot read system catalog (systabauth).
-103 - ISAM error: illegal key descriptor (too many parts or too
long).
So IBM's option 1 to fix it went out the window, and we started to
see that the corruption was getting worse as in more rows affected.
This morning when our users started work some of them where getting
access and other strange errors, after a little investigation it seems
the systabauth index corruption had gotten to the point where it was
preventing people from access our tables. So got everyone off the
system and got IBM involved.
IBM Down Systems Department was able to log on and fix the corrupt
indexes. Took IBM over an hour to fix the indexes and a couple of
different attempts but they saved the day. Yaaaaaah!!!!
Things learned for this problem:
1 - When a sys table is involved get IBM support helping out sooner
then later.
2 - Don't try to drop/rebuild any tables matching the tabids that
are
corrupt systabauth index. (will leave records of
the old tabid and
also add the new tabid) - get the indexes fix
first.
John
.
- References:
- oncheck -cI
- From: jda
- Re: oncheck -cI
- From: Jonathan Leffler
- Re: oncheck -cI
- From: jda
- oncheck -cI
- Prev by Date: HDR on win2k
- Next by Date: Re: dbload
- Previous by thread: Re: oncheck -cI
- Next by thread: RE: oncheck -cI
- Index(es):
Relevant Pages
|