Hierarchy
⤷ BC-DB-INF (Application Component) Informix
⤷ STUI (Package) Informix Database Monitor
Basic Data
Data Element | CORR_3 |
Short Description | Logical log sizing by checkpoint |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | SINT4_NOS | |
Data Type | INT4 | 4-byte integer, integer number with sign |
Length | 10 | |
Decimal Places | 0 | |
Output Length | 10 | |
Value Table |
Further Characteristics
Search Help: Name | ||
Search Help: Parameters | ||
Parameter ID | ||
Default Component name | ||
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 0 | |
Medium | 0 | |
Long | 0 | |
Heading | 0 |
Documentation
Definition
This correlation coefficient is given as a guide to the sizing of a logical log. A value of 100 percent indicates that a single logical log on disk is filling, by average, to full capacity by the time the next checkpoint is issued. At least one checkpoint is required per logical log. Therefore a value of 100 percent implies that the triggering of the next checkpoint is due to the filling of a single logical log file.
This value should never reach 100 percent if the physical log is sized properly. That is, a minimum of one checkpoint is required for each individual logical log file.
The proper sizing guldline is by rule of thumb at best. A complete discussion of this topic can be found in "INFORMIX-OnLine Dynamic Server Administrators Guide Volume 1, Version 6.0" page 18-7.can be found under the "physical log file size" help screen.
The "RESET"/"SINCE RESET" buttons can be used to monitor activity for any predetermined window of time.
History
Last changed by/on | SAP | 20010130 |
SAP Release Created in |