Kbase P121061: Is the bi file truncated during probkup?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
4/22/2009 |
|
Status: Verified
GOAL:
Is the bi file truncated during probkup?
GOAL:
Should truncating the bi be part of the probkup strategy?
FACT(s) (Environment):
All Supported Operating Systems
Progress/OpenEdge Product Family
FIX:
The bi blocks (files) are part of the probkup process when:
a.) An ONLINE probkup is taken
b.) An OFFLINE probkup is taken with the -norecover option
- the bi rollback REDO UNDO phases are delayed to when the probkup is restored. All bi blocks up to the High Water Mark (HWM) of the last bi file will be included, regardless. For example, a FULL probkup or an INCREMENTAL probkup will have all the bi blocks. The only difference in size of the probkup will be in which data blocks are included (all or only those changed since the previous backup)
The bi blocks (files) are not part of the probkup process when an OFFLINE probkup is taken. The first step of the offline probkup is to execute the bi rollback REDO UNDO phases and then backup the needed Data files to the HWM of each database extent.
In any of the above cases, the the bi rollback REDO UNDO phases do not truncate the bi files. ie resulting in variable bi file shrinking back to 16 x biblocksize. (typically, 128 KB)
There may be circumstances where abnormal bi growth may previously have occured, in which case there is a strong reason to truncate the bi file, followed by a bigrow to benefit the next startup of the database. Essentially, one first needs to decide why/if the truncation is necessary. It is not necessarily a 'default' consideration of the probkup strategy.