Home |
Previous Page | Next Page Configuring and Monitoring Dynamic Server > Configuration Parameters >
- onconfig.std value
- None (not present in onconfig.std)
- if not present
- 90 (if DYNAMIC_LOGS is set to 1 or 2)
60 (if DYNAMIC_LOGS is set to 0)
- units
- Percent
- range of values
- LTXHWM through 100
- takes effect
- When the database server is shut down and restarted
- refer to
- The following material:
- DYNAMIC_LOGS
- LTXHWM
- Setting high-watermarks for rolling back long transactions, in the chapter
on managing logical logs in the IBM Informix Administrator's Guide
A transaction is long if it is not committed or rolled back when it reaches the long-transaction
high-watermark. LTXEHWM specifies the long-transaction,
exclusive-access, high-watermark. When the logical-log space reaches
the LTXEHWM threshold, the long transaction currently being rolled back is
given exclusive access to the logical log.
If your system runs out of log space before the rollback completes, lower
the LTXEHWM value.
If you do not want too many logical logs to be added, LTXEHWM should be
set to a smaller value (around 60). If dynamic logging is turned off (DYNAMIC_LOGS
= 0), LTXEHWM should be set lower (around 50) to avoid running out of logical
space.
Tip:
To allow users to continue to access
the logical logs, even during a long transaction rollback, set LTXEHWM to 100. Set DYNAMIC_LOGS to 1 or 2 so that the
database server can add log files as needed to complete the transaction or
rollback.
Home |
[ Top of Page | Previous Page | Next Page | Contents |
Index ]