Monitor BI Clusters with ABL code using Virtual System Tables:
BI clusters have been reused when
_ActBILog._BiLog-ClstrClose or
_ActSummary._Summary-Chkpts are higher than the
Total number of clusters within the BI file:
- ActBILog._BiLog-ClstrClose provides the Number of BI clusters filled and closed in preparation for reuse since the Database Broker started; it is an accumulative field.
- _ActSummary._Summary-Chkpts provides the Number of Checkpoints, i.e. the number of BI clusters filled since the Database Broker started.
- The Total number of clusters within the BI file can be calculated by dividing the logical bi size by the bi cluster size with information from _DbStatus:
_DBStatus-BiSize which provides the logical size of the BI file
_DbStatus-BiClSize which provides the size of the BI cluster.
Bi Clusters have been reused when:
_ActBILog._BiLog-ClstrClose > (_DbStatus._DBStatus-BiSize / _DbStatus._DbStatus-BiClSize)There is only ever
one active BI cluster in the BI cluster chain. To determine the cluster number of the active cluster, use either
- _ActSummary._Summary-Chkpts +1 or
- _ActBILog._BiLog-ClstrClose +1
Since Progress 9, the Virtual System Table:
- _AreaStatus can be used monitor if additional clusters are formatted within a BI as the _AreaStatus-Hiwater value increases for _AreaStatus-Areaname = "Primary Recovery Area".
Since OpenEdge 11.7, the following VST's were added:
- _Logging-BIClusterHWM - BI Cluster HWM. This is different from the bi file size since not all space in the bi file is necessarily associated with a formatted and used cluster
- _Logging-CurrBICluster - Current BI Cluster
For further information refer to Article:
What is the highest numbered bi cluster being used in a pre-grown cluster ring?
Monitor BI Clusters with PROMON
PROMON > R&D > 1. Status Displays > 9. BI Log
Before-image cluster age time: 0 seconds
Before-image block size: 16384 bytes
Before-image cluster size: 32768 kb (33554432 bytes)
Number of before-image extents: 2
Before-image log size (kb): 12353608
Bytes free in current cluster: 19522648 (59 %)
Last checkpoint was at: 02/15/21 21:17
Number of BI buffers: 60
Full buffers: 13
Current BI Cluster: 375
BI Cluster HWM: 12288072
Run online PROBKUP to parse the ACTIVE Bi Clusters
Since OpenEdge 11.3.0, only Active BI clusters within the BI cluster chain are backup by default, as opposed to the entire BI cluster chain in previous versions, unless the "bibackup all" parameter is explicitly used.
For example, periodic online incremental probkups:
$ probkup online dbname incremental dbname_incr.bak -Bp 32 -verbose
(6688) 61440 BI blocks will be dumped == Bi file HWM, the number of initialized BI blocks making up the whole BI cluster chain, considered for backup.
(16866) Dumped 16384 active BI blocks == number of BI blocks currently Active or Locked on the BI cluster chain that were backed up.
