truncating BI
- Thread starter sureshp
- Start date
Performs three functions: Uses the information in the before-image (BI) files to bring the database up to date, waits to verify that the information has been successfully written to the disk, then truncates the before-image file to its original length. Sets the BI cluster size using the Before-image Filename (-bi) parameter. Sets the BI block size using the Before-image Block Size (-biblocksize) parameter.
TomBascom
Curmudgeon
Just to be clear... truncating the bi file should only be done on specific occasions and for specific needs. It should NOT, for instance, be part of a nightly shutdown script.
Good times to truncate the bi file:
For best performance you should use "proutil db-name -C bigrow" to return the bi file to its normal state after truncation and prior to production use. This avoids the need to allocate and format bi clusters as users commit work.
Good times to truncate the bi file:
- when you need to change the bi block or cluster sizes
- prior to upgrading
- after an unusual bi growth event (like a badly scoped transaction)
- when instructed by Progress
For best performance you should use "proutil db-name -C bigrow" to return the bi file to its normal state after truncation and prior to production use. This avoids the need to allocate and format bi clusters as users commit work.
RealHeavyDude
Well-Known Member
Nope. You can only truncate it.
Why would you want to empty it?
RealHeavyDude.
Why would you want to empty it?
RealHeavyDude.