DB_FILE_GENERATIONS- UBroker configuration option
- Stonebranch (Deactivated)
Description
The DB_FILE_GENERATIONS option enables archival of databases that fail the validation which may occur at Universal Broker startup.
The Broker initiates this validation when a previous instance of Broker failed to properly close the databases at shutdown.
Databases eligible for archival include:
bcomponent.db
scomponent.db
uems.db
ues.db
Archives are saved under the location specified by the SPOOL_DIRECTORY option, in an .archive folder that the Broker will create if it does not exist.
The number of archived copies for each of the eligible databases is managed by this option. When a new archival would exceed the configured value, the oldest copy is removed to accommodate the new archive.
The Broker will make every attempt to start successfully. Whether the archival is successful or not, the Broker will recreate the affected database so startup may proceed.
Only the databases listed above will be recreated. Other databases contain persistent data that will not be deleted automatically.
Usage
Method | Syntax | IBM i | UNIX | Windows | z/OS |
Command Line, Short Form | n/a | ||||
Command Line, Long Form | -db_file_generations generations |
|
| ||
Environment Variable | UBRDBFILEGENERATIONS=generations |
|
|
| |
Configuration File Keyword | db_file_generations generations | | |
|
Value
generations is the number of archive files that will be saved within the archive directory.
The maximum number of generations of log files that can be saved is 9999.
Default is 3.
Note
If the value is decreased, only the specified number of generations will be maintained. The "excess" archive files are not cleaned up immediately, but as the archive files rotate, this "excess" will be cleaned up and reused.
This change removes the recreate_databases option added in 7.7.0.0, to copy the functionality of the recreate_databases option, simply set the value of the new db_file_generations option to 0.