Kbase P121432: BI changes associated with 10.1B which could result in more checkponts
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
11/03/2009 |
|
Status: Verified
GOAL:
What database changes need to occur when migrating to 10.1B?
GOAL:
What BI changes are associated with 10.1B?
GOAL:
Why is my BI file growing larger since migrating to 10.1B?
GOAL:
Why is the database performing more checkpoints in 10.1B?
GOAL:
Does 10.1B support 64-bit RECIDs?
GOAL:
Does 10.1B support 64-bit integers?
GOAL:
Does 10.1B support 64-bit sequences?
GOAL:
Are large key entries supported in 10.1B?
FACT(s) (Environment):
OpenEdge 10.1B
OpenEdge 10.1B 64-bit
All Supported Operating Systems
FIX:
OpenEdge 10.1B adds support for 64-bit RECID, 64-bit integers, 64-bit sequences, and large key entries that can hold index keys of nearly 2,000 bytes.
As a result of these changes, the size of some journal file entries written to Before Image (BI) files has been increased. There are also some new notes that can be written as well. This means that more data will be written to the BI files, and that can potentially cause checkpoints to become more frequent. The volume of data written to the BI files is application dependent, so the frequency of checkpoints will vary from application to application.
If an application checkpoints more frequently (as seen in promon's Checkpoints display) when run with the Enterprise version of OpenEdge 10.1B, the BI cluster size should be increased. The increase will extend the time interval between checkpoints. The interval should be extended until it is a minute or more. This interval gives page writers time to write out modified database blocks, so there will be no blocks written out at checkpoint time.
If the application is not run with the Enterprise database version, no further tuning is needed, because there will not be any page writers to write modified blocks to disk. A cluster size of 512K or less is appropriate.