Re: Assert Failed: Page Check Error in bfput
Gary Quiring's archive on IDS 7.31.UC6 completed with one corrupted page (assert in rsarcbu.c, page 0x30fcaa1), and he asked how to find the bad log. Another poster suggested oncheck -cR, which checks reserved pages and logs. He listed likely causes: another process overwriting the page, a hardware error, or least likely an Informix bug. No outcome was reported.
Auto-generated by Claude from the posts below — may be imperfect; read the full thread.
On Wed, 14 Sep 2005 11:20:33 -0400, Gary Quiring <gquiring@msn.com> wrote:
The archive finished today with a different error:
07:39:44 Archive on rootdbs, logdbs, plogdbs, data2dbs Completed with 1 corrupted pages detected.
The page appears to be in my transaction logs. How can I figure out what log is
bad?
Thanks
Gary Quiring
On Fri, 16 Sep 2005 11:27:07 -0400, Gary Quiring <gquiring@msn.com> wrote:
>On Wed, 14 Sep 2005 11:20:33 -0400, Gary Quiring <gquiring@msn.com> wrote:
>
>The archive finished today with a different error:
>
>07:39:44 Archive on rootdbs, logdbs, plogdbs, data2dbs Completed with 1 corrupt>ed pages detected.
>
>The page appears to be in my transaction logs. How can I figure out what log is
>bad?
>
>Thanks
>Gary Quiring
Sorry about that, I am not thinking today. The log still shows the archive
error:
02:13:27 Assert Failed: Archive detects that page 0x30fcaa1 is corrupt.
02:13:27 Informix Dynamic Server Version 7.31.UC6
02:13:27 Who: Session(1628593, root@emco5, 3836, 1997004520)
Thread(2641968, arcbackup1, 77072c40, 3)
File: rsarcbu.c Line: 2482
the dd finished returning 36 bytes of all nulls.
oncheck -cR
R = check reserved pages AND LOGS.
Either a) Informix bug - v unlikely to generate all 0's b) something else overwrote the page (likely) c) hardware error - any hardware errors reported in the operating system message logs?