Kbase 16072: Getting 1119 error during ONLINE PROBACKUP
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
5/10/1998 |
|
Getting 1119 error during ONLINE PROBACKUP
Getting 1119 error during ONLINE PROBACKUP
PURPOSE
---------------------------------------------------------------------
To explain why this error happens and how to work around the problem
so the customer can use ONLINE PROBACKUP.
WHY THIS HAPPENS
---------------------------------------------------------------------
There is a set of conditions that must apply for this error to occur.
SYSTEM ERROR: wrong BI blk, read <dbkey> from <dbkey> (1119)
The error means there is corruption in the bi file. If the following
conditions do NOT apply, then there probably is corruption in the bi
file and truncating the bi should fix the problem.
If the following conditions DO apply to the customer's situation,
please read the work around section of this kbase.
CONDITIONS
----------
1) Database must have a multi-extent bi, with at least one fixed
length extent.
2) The customer must have changed the -biblocksize from the default
at some time in the past. (use promon to check the biblocksize:
R&D -> 1. Status Displays -> 9. BI Log. If "Before-image block
size is anything but 1024, then it has been changed.)
3) The ONLINE PROBACKUP fails with this error, however, PROBACKUP
with server down (off line) works fine and so does PROCOPY.
This error occurs because of how we do two separate bi functions.
1) Changing the -biblock size. When we do this (with the proutil
dbname -C truncate bi -biblocksize #) operation we truncate the
bi file and format only the first four clusters and we format more
blocks in the bi as needed. (see examples below).
bi file blocks and block numbers by default
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
|01|02|03|04|05|06|07|08|09|10|11|12|13|14|15|16|17|18|19|20|21|22|
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
bi file blocks and block numbers after change to 4k blocksize
using the proutil dbname -C truncate bi -biblocksize 4
----------- ----------- ----------- ----------- -- -- -- -- -- --
| 01 | 02 | 03 | 04 |17|18|19|20|21|22|
----------- ----------- ----------- ----------- -- -- -- -- -- --
***notice reading the bi file the block numbers go from 04 to 17***
2) When doing an ONLINE PROBACKUP we backup ALL bi blocks in the
fixed extent. On off line backups and procopy we only backup the
active blocks in the bi file.
So with ONLINE PROBACKUP the utility is reading the bi block numbers
for the whole fixed bi extent (active, non-active & unused blocks)
and finds a block that goes from 04 to 17, the utility reads this as
corruption, aborts the backup and send the 1119 error.
WORK AROUNDS
---------------------------------------------------------------------
1) In Version 8.0B, there is a new utility called bigrow which will
pre format the blocks in the bi file, so it does not have to be
done interactively (causing performance slow downs). This will
make all the blocks in the bi preformatted with the correct block
numbers.
2) In Version 7, you will need to truncate the bi file and physically
remove it and then add the extents back in (truncating alone will
NOT fix this problem). The following steps will be necessary->
proutil dbname -C truncate bi
prostrct remove dbname bi
(this step will have to be repeated until all bi
extents are removed)
prostrct add dbname bi.st
(the bi.st is a structure file with just the new bi
extent information in it)
(now to reset the biblocksize to the larger value you wished)
proutil dbname -C truncate bi -biblocksize ##
revised rve 11/1/96
Progress Software Technical Support Note # 16072