archecker against an ontape backup
Posted in 2007
Topics: Backup & Restore, Storage & Space Management, Versions, Editions & End-of-Life
Just as a spot check I'm trying to verify a backup of a ~200GB instance
backed up via ontape onto a single tape (running from IDS 7.31 on SCO
Unix). It runs all the way through the check (run via `archecker -tdsv`)
and everything passes, except at the top there are two errors:
02/08/2007 12:43:43
-----------------------------------------
STATUS: Informix Dynamic Server Version 7.31.UD7
Program Name: archecker
Version: 4.5
Released: 11/20/03 22:35
Compiled: 11/21/03 01:01 on SCO_SV 3.2 5.0.5
STATUS: AC_STORAGE /tmp
STATUS: AC_MSGPATH /tmp/ac_msg.log
STATUS: AC_VERBOSE on
STATUS: AC_TAPEDEV /dev/rStp0
STATUS: AC_TAPEBLOCK 16
TIME: [02/08/2007 12:43:43] All old validation files removed.
TIME: [02/08/2007 12:43:44] Tape 1 started
ERROR: BAD PAGE 100002: page->pg_frcnt 1204 != calculated 1208
ERROR: BAD PAGE 100003: page->pg_frcnt 1204 != calculated 1208
STATUS: Starting to scan dbspace 1 created on 02/07/2007 18:42:08
STATUS: Archive timestamp 0xB08E24E4
STATUS: Starting to scan dbspace 10 created on 02/07/2007 18:42:08
STATUS: Archive timestamp 0xB08E24E4
...
What does this mean? Should I be worried? I checked the backups for two
other instances on the same platform. One of them had the same errors,
the other didn't.
Thanks.
DC
DOUG CONREY
OCI(r)
Database Administrator
doug_conrey@oci.com
307.772.4193
www.oci.com
Doug Conrey wrote:
> Just as a spot check I'm trying to verify a backup of a ~200GB instance
> backed up via ontape onto a single tape (running from IDS 7.31 on SCO
> Unix). It runs all the way through the check (run via `archecker -tdsv`)
> and everything passes, except at the top there are two errors:
>
> 02/08/2007 12:43:43
> -----------------------------------------
> STATUS: Informix Dynamic Server Version 7.31.UD7
> Program Name: archecker
> Version: 4.5
> Released: 11/20/03 22:35
> Compiled: 11/21/03 01:01 on SCO_SV 3.2 5.0.5
>
> STATUS: AC_STORAGE /tmp
> STATUS: AC_MSGPATH /tmp/ac_msg.log
> STATUS: AC_VERBOSE on
> STATUS: AC_TAPEDEV /dev/rStp0
> STATUS: AC_TAPEBLOCK 16
> TIME: [02/08/2007 12:43:43] All old validation files removed.
> TIME: [02/08/2007 12:43:44] Tape 1 started
> ERROR: BAD PAGE 100002: page->pg_frcnt 1204 != calculated 1208
>
> ERROR: BAD PAGE 100003: page->pg_frcnt 1204 != calculated 1208
>
> STATUS: Starting to scan dbspace 1 created on 02/07/2007 18:42:08
> STATUS: Archive timestamp 0xB08E24E4
> STATUS: Starting to scan dbspace 10 created on 02/07/2007 18:42:08
> STATUS: Archive timestamp 0xB08E24E4
> ...
>
>
>
> What does this mean? Should I be worried? I checked the backups for two
> other instances on the same platform. One of them had the same errors,
> the other didn't.
Check the page headers for those two pages in sysmaster:syspaghdr and see
what the free byte count (pg_frcnt) is now. If it's 1208 then the error has
been corrected. If not you can try running onchecks to check the pages on
disk or contact tech support.
This is probably a minor problem, but I'm not certain of that. The free
count is used to determine if a new row will fit on a particular page, and
these are system reserved pages IB. Pages 1 & 2 are the checkpoint pages
and are used alternatingly. Pages 3 & 4 are the first DBspace list pages,
again used alternatingly. The worst that can happen is you'll leave more
unused space on the first dbspace page than is strictly neccessary, a
problem in 5.xx but not in later releases.
Art S. Kagel
Doug Conrey wrote:
> Just as a spot check I'm trying to verify a backup of a ~200GB instance
> backed up via ontape onto a single tape (running from IDS 7.31 on SCO
> Unix). It runs all the way through the check (run via `archecker -tdsv`)
> and everything passes, except at the top there are two errors:
>
> 02/08/2007 12:43:43
> -----------------------------------------
> STATUS: Informix Dynamic Server Version 7.31.UD7
> Program Name: archecker
> Version: 4.5
> Released: 11/20/03 22:35
> Compiled: 11/21/03 01:01 on SCO_SV 3.2 5.0.5
>
> STATUS: AC_STORAGE /tmp
> STATUS: AC_MSGPATH /tmp/ac_msg.log
> STATUS: AC_VERBOSE on
> STATUS: AC_TAPEDEV /dev/rStp0
> STATUS: AC_TAPEBLOCK 16
> TIME: [02/08/2007 12:43:43] All old validation files removed.
> TIME: [02/08/2007 12:43:44] Tape 1 started
> ERROR: BAD PAGE 100002: page->pg_frcnt 1204 != calculated 1208
>
> ERROR: BAD PAGE 100003: page->pg_frcnt 1204 != calculated 1208
>
> STATUS: Starting to scan dbspace 1 created on 02/07/2007 18:42:08
> STATUS: Archive timestamp 0xB08E24E4
> STATUS: Starting to scan dbspace 10 created on 02/07/2007 18:42:08
> STATUS: Archive timestamp 0xB08E24E4
> ...
>
>
>
> What does this mean? Should I be worried? I checked the backups for two
> other instances on the same platform. One of them had the same errors,
> the other didn't.
Check the page headers for those two pages in sysmaster:syspaghdr and see
what the free byte count (pg_frcnt) is now. If it's 1208 then the error has
been corrected. If not you can try running onchecks to check the pages on
disk or contact tech support.
This is probably a minor problem, but I'm not certain of that. The free
count is used to determine if a new row will fit on a particular page, and
these are system reserved pages IB. Pages 1 & 2 are the checkpoint pages
and are used alternatingly. Pages 3 & 4 are the first DBspace list pages,
again used alternatingly. The worst that can happen is you'll leave more
unused space on the first dbspace page than is strictly neccessary, a
problem in 5.xx but not in later releases.
Art S. Kagel