Topic
  • 1 reply
  • Latest Post - ‏2010-07-09T13:46:12Z by SystemAdmin
SystemAdmin
SystemAdmin
228 Posts

Pinned topic Assert Failed: Page Check Error in rsread:bad data page

‏2010-01-05T05:28:59Z |
Hi,
We are seeing the following error in IDS logs. Can someone let us know what's going wrong here.
IDS Version is - 11.00.

23:49:44 Assert Failed: Page Check Error in rsread:bad data page
23:49:44 Who: Session(149889, dbcarsch@cucm6, -1, 0x4c35d0d8)
Thread(149936, sqlexec, 4c3426e4, 1)
File: rsdebug.c Line: 1056
23:49:44 Results: Possible inconsistencies in 'car:"informix".sysfragments'
We tried the oncheck command suggested in the IDS log, and its output is as follows.

root@cucm6 ciscotac# oncheck -cD 9437210

TBLspace data check for car:informix.sysfragments

WARNING: data page 0x4 in tablespace 0x90001a appears to be
more or less full than is indicated in the bitmap.
Bitmap mode: 0x4, Calculated mode: 0xc.
Reset the bitmap mode for this page?
n
WARNING: partition BLOB page 0x5 in tablespace 0x90001a appears to be
more or less full than is indicated in the bitmap.
Bitmap mode: 0xa, Calculated mode: 0xe.
Reset the bitmap mode for this page?
n
ERROR: Tablespace 0x90001a. Page 0x6 appears to be of type "data",
which is out of sync with its bitmap representation (0x6).
WARNING: The header of this page may have been corrupted. Resetting
the bitmap may not fully repair the problem and may even
result in more data corruption.
Reset the bitmap mode for this page?
n
BAD PAGE 9:228086: pg_chksum 0x9118 != PG_CHECKSUM 0x5351
ERROR: bstamp (0x8f00) on PNBLOB 0x970d != expected (0x2152) for rowid 0x9801
Invalid PBLOB piece - id 0xc000000ERROR: Bad Page 786432:38913x, page not found.
BAD PAGE 9:228380: Bad data row - rowid 38913
WARNING: data page 0xac in tablespace 0x90001a appears to be
more or less full than is indicated in the bitmap.
Bitmap mode: 0x4, Calculated mode: 0.
Reset the bitmap mode for this page?
n
WARNING: partition BLOB page 0xad in tablespace 0x90001a appears to be
more or less full than is indicated in the bitmap.
Bitmap mode: 0xa, Calculated mode: 0.
Reset the bitmap mode for this page?
n
WARNING: partition BLOB page 0xaf in tablespace 0x90001a appears to be
more or less full than is indicated in the bitmap.
Bitmap mode: 0xe, Calculated mode: 0.
Reset the bitmap mode for this page?
n
ERROR: Tablespace 0x90001a. Page 0xb0 appears to be of type "data",
which is out of sync with its bitmap representation (0xe).
WARNING: The header of this page may have been corrupted. Resetting
the bitmap may not fully repair the problem and may even
result in more data corruption.
Reset the bitmap mode for this page?
n
ERROR: Tablespace 0x90001a. Page 0xb1 appears to be of type "partition BLOB",
which is out of sync with its bitmap representation (0xc).
WARNING: The header of this page may have been corrupted. Resetting
the bitmap may not fully repair the problem and may even
result in more data corruption.
Reset the bitmap mode for this page?
n
WARNING: partition BLOB page 0xb2 in tablespace 0x90001a appears to be
more or less full than is indicated in the bitmap.
Bitmap mode: 0xe, Calculated mode: 0.
Reset the bitmap mode for this page?
n
ERROR: Tablespace 0x90001a. Page 0xb3 appears to be of type "data",
which is out of sync with its bitmap representation (0xe).
WARNING: The header of this page may have been corrupted. Resetting
the bitmap may not fully repair the problem and may even
result in more data corruption.
Reset the bitmap mode for this page?
n
ERROR: Tablespace 0x90001a. Page 0xb4 appears to be of type "partition BLOB",
which is out of sync with its bitmap representation (0xc).
WARNING: The header of this page may have been corrupted. Resetting
the bitmap may not fully repair the problem and may even
result in more data corruption.
Reset the bitmap mode for this page?
Interrupt received ...
The check has been aborted.

We are not able to get what's the output is saying, can somebody help us here.

Thanks,
Anil
Updated on 2010-07-09T13:46:12Z at 2010-07-09T13:46:12Z by SystemAdmin
  • SystemAdmin
    SystemAdmin
    228 Posts

    Re: Assert Failed: Page Check Error in rsread:bad data page

    ‏2010-07-09T13:46:12Z  
    It seems that your blobspace has been corrupted for some reason: first engine has dropped an assertion failure indicating data page inconsistence.Now oncheck found inconsistence for specific blobpages by comparing the page state against the bitmap entry and comparing calculated page checksum against the checksum that stored in page header; it suggests you to try to fix the pages structures. As it warns you, it may not fix the problem. I suggest you to do restore from backup or/and call to IDS support.