IDS Forum

Re: Archive detects that page x:xxxxx is corrupt

Posted By: tilleul17@web.de
Date: Monday, 28 July 2008, at 3:51 p.m.

In Response To: Re: Archive detects that page x:xxxxx is corrupt (Emiliano Romero)

Emiliano Romero wrote:
> I run oncheck -cID in the production enviroment and get the following:
> Validating indexes for db:informix.table...
>
> Index 146_117
>
> Index fragment partition datadbs1 in DBspace datadbs1
> Could not bfget pagenum 0x138374, iserrno 105
> ISAM error: bad isam file format.
> ERROR: Index 146_117 for db:informix.table is bad.
>
> Index idx_chst
>
> Index fragment partition datadbs1 in DBspace datadbs1
>
> Is that error being fixed with oncheck utility?

oncheck should as you something liek 'Ok to repair?'
if it did and you answered yes , it will have dropped and recreated the
index, the corruption will be gone then.
However, if you di not answer y or yes, it is probably still bad. In
that case I suggest to not use oncheck to repair the corrupt index but
to drop it and recreate it maually (with PDQPRIORITY set to 100 and
loads od DS_TOTAL_MEMORY configured (up 90 % of SHMVIRTSIZE)

...

>> Then, after a lot of those lines the backup finish with:
>> 12:11:17 Archive on rootdbs, datadbs, physdbs, datadbs2, datadbs1
>> Completed with 137 corrupted pages detected
>>
>> Like I see in the logs i have some wrong data in my chunk 6 in page
>> 6278896. I have check and I have one Table in that chunk. If I do a
>> select count(*) from table I get like the half of the rows I SHOULD have.
>>
>> I restore that backup in my development server and run oncheck -cID
>> database:informix.table, it took like 20 minutes but no luck.

What you mean No luck : oncheckk did not finish or not reprot any errors?
>>
>> I have some questions about this issue.
>> 1) If I restore that backup in another server. Can I try fixing in that
>> server before try in production? Or the backup is restore *without*
>> corrupted pages?

>> 2) Is there another way to deal with this problem?

I'd try and drop the bad index of the table - it seems to be bad.
Afterwards run oncheck -cD <database>:<table>
Doe it still report errors ?
if not , go recreate the index (i hope you saved the schema beforehand
with dbschema -d <db> -ss -t <table>

If yes - try to find the nature AND root cause of the corruption .
IBM Informix Tech support can help.
Also hae a look at the af-files in case any got generate dduring archive
or when accessing the bad pages.

>>
>> Thanks in advice and sorry about my really bad English.
>>
>>

Messages In This Thread

• Archive detects that page x:xxxxx is corrupt
  Emiliano Romero -- Monday, 28 July 2008, at 1:17 p.m.
  • Re: Archive detects that page x:xxxxx is corrupt
    Emiliano Romero -- Monday, 28 July 2008, at 1:39 p.m.
    • Re: Archive detects that page x:xxxxx is corrupt
      tilleul17@web.de -- Monday, 28 July 2008, at 3:51 p.m.
      • Re: Archive detects that page x:xxxxx is corrupt
        Emiliano Romero -- Tuesday, 29 July 2008, at 10:29 a.m.

IDS Forum is maintained by Administrator with WebBBS 5.12.