Assert Failed: Page Check Error in bfput
Posted in 2005
Topics: Error Codes & Troubleshooting, Logging & Checkpoints, Platform-Specific Issues
I could use some help on the below message:
Informix Dynamic Server Version 7.31.UC6 on Solaris 7
09:24:21 Assert Failed: Page Check Error in bfput
09:24:21 Informix Dynamic Server Version 7.31.UC6
09:24:21 Who: Session(1577425, ac758200@emco11, 4732, 2137802408)
Thread(2569850, sqlexec, 79c2db10, 3)
File: rsdebug.c Line: 1036
09:24:21 Results: Possible inconsistencies in 'cdi:"informix".auth_l'
09:24:21 Action: Run 'oncheck -cDI cdi:"informix".auth_l'
09:24:31 Logical Log 444272 Complete.
09:24:41 See Also: /tmp/af.3a622485
09:24:41 Assert Failed: Rollback error 172
09:24:41 Informix Dynamic Server Version 7.31.UC6
09:24:41 Who: Session(1577425, ac758200@emco11, 4732, 2137802408)
Thread(2569850, sqlexec, 79c2db10, 3)
File: rsextlog.c Line: 1450
09:24:41 Results: Log record (OLDRSAM:DELITEM) in log 444271, offset 0x3e85d0was not rolled back
09:24:41 Action: Use 'onlog' to view the transaction and repair manually.
09:25:00 See Also: /tmp/af.3a622485
09:25:00 Checkpoint Completed: duration was 16 seconds.
I ran oncheck -cDI cdi:"informix".auth_l and got the following error:
BAD PAGE 30fcaa1: pg_addr 0 != bp->bf_pagenum 30fcaa1
I exported the table, no issues. Dropped the indexes. Renamed the table to
auth_l_bad. Created the new table and imported the data and indexed.
Do I need to address this beyond this point? Can I delete the renamed table or
is there something wrong with the space it's on?
Thanks
Gary Quiring
What does finderr 172 give?
Use onlog to look at what is in the logical logs at
log 444271, offset 0x3e85d0
It was not rolled back.
Also run
oncheck -cR
oncheck -ce
oncheck -cc
first.
If any of these fail you have real problems.
> BAD PAGE 30fcaa1: pg_addr 0 != bp->bf_pagenum 30fcaa1
tells that page 30fcaa1 is zeroed. or at least it's adress
check your af files. you also may want to dump the page:
oncheck -pP 0x3 0xfcaa1in order to check if it's really zeroed...
when you do not need the old table anymore you could try and drop
it; however it may fail.
you may also want to check the dev for chunk #3 maybe someone mucked it
up
Superboer.
Gary Quiring schreef:
> I could use some help on the below message:
>
> Informix Dynamic Server Version 7.31.UC6 on Solaris 7
>
> 09:24:21 Assert Failed: Page Check Error in bfput
> 09:24:21 Informix Dynamic Server Version 7.31.UC6
> 09:24:21 Who: Session(1577425, ac758200@emco11, 4732, 2137802408)
> Thread(2569850, sqlexec, 79c2db10, 3)
> File: rsdebug.c Line: 1036
> 09:24:21 Results: Possible inconsistencies in 'cdi:"informix".auth_l'
> 09:24:21 Action: Run 'oncheck -cDI cdi:"informix".auth_l'
> 09:24:31 Logical Log 444272 Complete.
> 09:24:41 See Also: /tmp/af.3a622485
> 09:24:41 Assert Failed: Rollback error 172
> 09:24:41 Informix Dynamic Server Version 7.31.UC6
> 09:24:41 Who: Session(1577425, ac758200@emco11, 4732, 2137802408)
> Thread(2569850, sqlexec, 79c2db10, 3)
> File: rsextlog.c Line: 1450
> 09:24:41 Results: Log record (OLDRSAM:DELITEM) in log 444271, offset 0x3e85d0> was not rolled back
> 09:24:41 Action: Use 'onlog' to view the transaction and repair manually.
> 09:25:00 See Also: /tmp/af.3a622485
> 09:25:00 Checkpoint Completed: duration was 16 seconds.>
> I ran oncheck -cDI cdi:"informix".auth_l and got the following error:
> BAD PAGE 30fcaa1: pg_addr 0 != bp->bf_pagenum 30fcaa1
>
>
> I exported the table, no issues. Dropped the indexes. Renamed the table to
> auth_l_bad. Created the new table and imported the data and indexed.
>
> Do I need to address this beyond this point? Can I delete the renamed table or
> is there something wrong with the space it's on?
>
> Thanks
> Gary Quiring