Kbase P32430: Administration that can be carried out on the bi file
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
18/07/2003 |
|
Status: Unverified
GOAL:
Administration that can be carried out on the bi file
GOAL:
Operations that can be carried out on the bi file
GOAL:
How to use proutil -C bigrow
GOAL:
How to use proutil -C truncate bi
FIX:
There are basically four administrative operations that can be carried out on the bi file -
- preformat the number of bi clusters (proutil bigrow)
- truncate the bi (proutil truncate bi)
- specify a new bi cluster size (proutil truncate bi -bi)
- specify a new bi blocksize (proutil truncate bi -biblocksize)
---------------------------------------------------------------------------------
The PROUTIL BIGROW qualifier specifies the number of BI clusters to preformat for a database.
SYNTAX:
proutil db-name -C bigrow n [ -r ]
db-name
Specifies the database where you want to create BI clusters.
n
Specifies the number of BI clusters to create for the specified database. Note that Progress creates 4 BI clusters at startup. If you specify a BIGROW value of 5, then you will have a total of 9 BI clusters.
-r
Nonreliable I/O startup parameter; turns off reliability.
NOTES
- You can calculate the number of BI clusters for a database by dividing the BI file physical size by the BI cluster size. For example, a database BI file with a BI cluster size of 128K and a physical size of 917,504 has 7 BI clusters.
- By default, Progress creates 4 BI clusters at startup.
- The database must be offline to use the BIGROW qualifier.
- Use the BIGROW qualifier immediately after truncating the BI file.
- Refer to the performance chapter in the documentation for information about using the BIGROW qualifier.
---------------------------------------------------------------------------------
The PROUTIL TRUNCATE BI Qualifier performs three functions:
- Uses the information in the before-image (BI) files to bring the database and after-image (AI) files 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 Cluster Size (-bi) parameter.
- Sets the BI block size using the Before-image Block Size (-biblocksize) parameter.
SYNTAX:
proutil db-name -C truncate bi { [ -G n ] | -bi size | -biblocksize size }
db-name
Specifies the database you are using.
-G n
Specifies the number of seconds the TRUNCATE BI qualifier waits after bringing the database and AI files up to date and before truncating the BI file. The default wait period is 60 seconds. You might specify a shorter period for practice or test purposes. However, do not do so for any significant database, because a system crash could damage the database if the BI file is truncated before the writes to the database and AI files are flushed from the operating system buffer cache.
-bi size
Specifies the size of the cluster in kilobytes. The number must be a multiple of 16 ranging from 16 to 262,128 (16K to 256MB). The default cluster size is 524K. If you use a value that is not a multiple of 16, PROUTIL rounds the value up to the next multiple of 16.
-biblocksize size
Specifies the size of the BI blocks in each buffer in kilobytes. The valid values are 1, 2, 4, 8, and 16. The default -biblocksize is 8K. A value of 0 tells Progress to use the default block size. The block size cannot be smaller than the database block size.
NOTES
- The Before-image Block Size (-biblocksize) parameter changes the BI block size so that Progress reads and writes the blocks as one block.
- Use the PROSTRCT STATISTICS qualifier to display the block size for a database.
- If you change the BI block size or cluster size before backing up a database, when you restore the database, the blocks and clusters will be the size you specified before the backup.
- Progress reads all the BI blocks according to the size of the first block it reads. For example, if the first BI block is 8K, Progress reads and writes each block on an 8K boundary.
- For performance reasons, you might want to run PROUTIL with the -C bigrow qualifier to increase the number of BI clusters available to your database before starting your server.