Nonstop Database, HiRDB Version 9 System Operation Guide
![[Contents]](FIGURE/CONTENT.GIF)
![[Index]](FIGURE/INDEX.GIF)
![[Back]](FIGURE/FRONT.GIF)
3.10.3 HiRDB processing during automatic extension
(1) Automatic extension in response to Trigger 1
When HiRDB detects that the percentage of free area in the system log file has fallen below the warning value based on the function for monitoring the free area for system log files, the following processing by HiRDB occurs during automatic extension:
- If there are multiple swappable standby files, HiRDB sequentially extends the system log files, starting with the last one to be allocated to the current file.
- If file swapping occurs while a system log file is being extended, extension stops and the file becomes the current file and is excluded from extension. If this occurs, swapping might require some time.
- If a standby file becomes swappable while a system log file is being extended, that file also becomes subject to extension.
- During system log file extension, system log files that go into the current status, unswappable target status, or reserved status are excluded from extension.
- When all swappable standby files have been extended once, extension ends.
(2) Automatic extension in response to Trigger 2
If there is no swappable standby file when the current system log file becomes full, the following processing by HiRDB occurs during automatic extension:
- HiRDB extends the current file. If this occurs, system log input/output might require some time.
- If the number of files to be extended increases while the current file is being extended (for example, a standby file becomes swappable), extension of the current file stops and the system log file that has become subject to extension is extended. It might take some time before extension of the current file stops.
- During extension of the current file, system log files that go into the current status, unswappable target status, or reserved status are excluded from extension.
- When all swappable standby files have been extended once, extension ends.
(3) When a unit terminates abnormally during extension
If a unit terminates abnormally during automatic extension of a system log file, the status as to whether automatic extension is enabled is inherited after the unit is restarted.
Depending on the timing of the abnormal termination of the unit, an inconsistency might occur in the HiRDB file system area that contains the system log file that was being extended. In such a case, you must use the pdffsck command to verify and, if needed, repair the consistency of the HiRDB file system area.
All Rights Reserved. Copyright (C) 2011, 2015, Hitachi, Ltd.