Hierarchy
⤷
⤷
Basic Data
| Data Element | PHYSFILE |
| Short Description | Physical log file size (KB) |
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
The physical log file is a set of contiguous disk pages where Online stores before-immages. Adjusting the size of the physical log file can be complicated and is determined by applying the following formula.
PHYSFILE = USERTHREADS * maximum log pages per critical section * 4,
where the value for USERTHREADS can be found in the ONCONFIG* file located in $INFORMIXDIR/etc. The "maximum log pages per critical section" constant is fixed at 5.
This is the minimum setting which should be used as the size of the physical log file. If the physical log file is frequently approaching full, you might want to consider decreasing the checkpoint interval. If you plan to increase the checkpoint interval you probably want to increase the size of the physical log.
History
| Last changed by/on | SAP | 20010130 |
| SAP Release Created in |