There is no Progress utility to truncate the archival.log file at this time. For example PROLOG cannot be used to archive the archival log file. In order to manage the
archival.log file size while the AI Management enabled database is online is as follows:
1. Stop the AIMGT daemon online without shutting down the database server or ai or disabling the aiarchiver feature:
$ rfutil dbname -C aiarchiver end
2. Once the AIMD has stopped, backup the current archival log for future roll forward reference or aimage scan verbose analysis.
3. Either delete the
dbname.archival.log file or 'truncate' the content as required with OS Utilities.
When truncating the content of archival.log file, for example deleting old data entries and preserving current entries by editing or parsing the file, the following guidelines should be observed:
a. The first 5 lines must remain.
Example:
#
# OpenEdge RDBMS After-image Extent Manager Archival Log File
# Do not edit this file with an editor as it is automatically
# maintained by the OpenEdge RDBMS after-image extent manager.
#
Delete all archival log record from here to a point in time in the file. Save as many or as few records as needed, entries in this file are designed to aid in recovery when required.
Typically all entries after the most recent log records are preserved so that the data can be used in case roll forward recovery is required.
- The 0255 record is logged before any action any lines after these should be maintained.
- The second field is the date of the operation.
- The subsequent entries are those that followed
- Be sure to do not delete the last carriage return.
The sample log below contains records from the 11.6 after-image management daemon entries.
#
# OpenEdge RDBMS After-image Extent Manager Archival Log File
# Do not edit this file with an editor as it is automatically
# maintained by the OpenEdge RDBMS after-image extent manager.
#
0255,20160128,155847,100200
# A new archive interval 0 has been set.
0001,C:\db\dbname,20160128,160213,20151030,103610,5,C:\db\dbname.a5,C:\db\ais1\C!~db~dbname.20151030.103610.00000005.dbname.a5
0032,C:\db\dbname,20160128,160227,1,4,20160128,160226,7,BACKUP_SET_20160128_160226,1,dbname0.back
0001,C:\db\dbname,20160128,160228,20151030,103610,6,C:\db\dbname.a6,C:\db\ais1\C!~db~dbname.20151030.103610.00000006.dbname.a6
0003,C:\db\dbname,20160128,160455,20151030,103610,7,C:\db\dbname.a1,C:\db\ais2\dbnamebak.a1
0001,C:\db\dbname,20160128,160625,20151030,103610,8,C:\db\dbname.a2,C:\db\ais1\C!~db~dbname.20151030.103610.00000008.dbname.a2
0001,C:\db\dbname,20160128,160746,20151030,103610,9,C:\db\dbname.a3,C:\db\ais1\C!~db~dbname.20151030.103610.00000009.dbname.a3
<< Be sure to do not delete the last carriage return.
4. Re-start the AIMGT deamon online, which will then either re-create the archival log if deleted or continue writing to the truncated log file:
$ _mprshut dbname -C aimgt -aiarcdir xxxx -aiarcinterval n
