Re: inquiry on informix problem
At 10:36 AM 7/24/96 -0300, you wrote:
> Dear Sir ,
> I would like to inquire about an error message appearing in my
>online.log ,I couldn't find any information about it in the errmsg manual.
>I am running informix online version 5.00 .
>This error appears a day after making DBEXPORT and DBIMPORT of the database
>during witch I changed some tables extent size.
>Despite this error the tbcheck -cI and tbcheck -cD are ok and users are working
>without problems.
>The error is :
> bfcheck: bad page :pg_addr 224ef5 !=bp->bf_pagenum
>233847,userp=801ea8,pid=23775,uid=0
>buffer header:
>89c408: a81e8000 00000000 00000000 d488a8500 ......... .........
>page header:
>fe6800: 17001008 001ff4b2c 00000200 810a22408
>slot table and stamp:
>fe6ffc: 7f286910
>fail consistency check-- isread:bad data page--pid 23775 user=0
>
> I really appreciate if you could help me in this matter.
>
> Best Regards
> Ossama Osman
> Informix DBA
> oriental group
> state of Bahrain
>
>
One of the consistency checks ran on data by the engine has failed (because
probably of
a corrupted page in shared memory).
When this happens, Informix recommends that you shutdown your OnLine system
immediatelly
without a checkpoint (tbmode -K), since the corrupted page may not yet have
been written to disk.
Run tbcheck -pe to find out where the corrupted page is (using the page
number you got in your
message log i.e. 233847).
1) If the corrupted page belongs to a table, run tbcheck -cDI tablename to
make sure that the table
is corrupted. If it is, tbcheck may be able to fix the problem.
If not, you'll have to do a unload, drop, create, load (you may have to skip
some corrputed records).
2) If the corrupted page belongs to an index, just recreate the index.
3) If none of the above two, restore your OnLine system from a level-0 archive.
NOTE: The above commands/procedures apply to OnLine 5.0. I don't know if
later versions have more
enhanced tools to deal with the situation. Also, external utility names
will be called differently
(eg. oncheck instead of tbcheck).
If you don't mind I would like to know how this information helped you and
if it resolved the problem.
Kleanthis