Kbase P136728: Which are the steps to archive the archival log
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
27/11/2008 |
|
Status: Unverified
GOAL:
Which are the steps to archive the archival log
GOAL:
How to truncate or clean up AI archive log
GOAL:
How to clean old information in AI archive log
GOAL:
How do I archive the db-name.archival.log without stopping the database?
GOAL:
How to archive the aiarchiver log file while the database is running
GOAL:
Is there a way to archive the aiarchiver log while the database is running?
FACT(s) (Environment):
All Supported Operating Systems
OpenEdge 10.1x
FIX:
There is no way to truncate the archival log at this time, but an enhancement request is being considered by development.
Therefore, the archival log can be truncated manually or via a script as long as some guidelines are followed.
Here are the steps to archive the archival log
1) Terminate the after-image management daemon using: _rfutil <dbname> -C aiarchiver end
2) Wait until the after-image management daemon ends.
3) Change to the database directory
4) Copy database.archivel.log to database.archival.log.save
5) The database.archival.log can now be deleted or edited.
6) If the file is edited, the following gide lines must be followed:
a) the first 5 lines should remain.
b) Delete all archival log record from there to a point in time in the file.
c) The 0255 record is always logged before any action.
d) The second field is always the date of the operation.
e) Save the most recent log records so that the data can be used in case a recovery is required.
f) Save as many or as few records as you want.
g)The entries in this file are designed to aid in recovery if required.
h) Be sure to do not delete the last carriage return.
i) See the sample log below which contains records from the 10.1C after-image management daemon.
7) Once the file is deleted or edited, restart the after-image management daemon using _mprshut database -C aimgt.
8) At this point, the after-image management daemon should be running and if the archival log was deleted it should now be recreated. If the file was edited new data will be appended to it.
--- #
| # OpenEdge RDBMS After-image Extent Manager Archival Log File
These lines | # Do not edit this file with an editor as it is automatically
should stay | # maintained by the OpenEdge RDBMS after-image extent manager.
| -- #
# After-image Extent Manager started on : Monday November 24, 2008 at 16:46:41
#
From here on 0255,20081124,164641,100200
should remain 0001,/dir/bin/krs,20081124,164742,20081124,164537,1,/dir/bin/krs.a1,/dir/bin/aiarcdir/dir~bin~krs.20081124.164537.00000001.krs.a1
0001,/dir/bin/krs,20081124,164747,20081124,164537,2,/dir/bin/krs.a2,/dir/bin/aiarcdir/dir~bin~krs.20081124.164537.00000002.krs.a2
&.nbsp; 0001,/dir/bin/krs,20081124,164752,20081124,164537,3,/dir/bin/krs.a3,/dir/bin/aiarcdir/dir~bin~krs.20081124.164537.00000003.krs.a3
0001,/dir/bin/krs,20081124,164803,20081124,164537,4,/dir/bin/krs.a1,/dir/bin/aiarcdir/dir~bin~krs.20081124.164537.00000004.krs.a1
0032,/dir/bin/krs,20081124,164832,1,2,20081124,164758,5,BACKUP_SET_20081124_164758,1,ks1.bak
0001,/dir/bin/krs,20081124,164848,20081124,164537,5,/dir/bin/krs.a2,/dir/bin/aiarcdir/dir~bin~krs.20081124.164537.00000005.krs.a2
0001,/dir/bin/krs,20081124,164853,20081124,164537,6,/dir/bin/krs.a3,/dir/bin/aiarcdir/dir~bin~krs.20081124.164537.00000006.krs.a3
#
# Operation being performed on : Monday November 24, 2008 at 16:49:54
#
Or from here on 0255,20081124,164954,100200
Should remain 0032,/dir/bin/krs,20081124,164954,0,3,20081124,164938,8,BACKUP_SET_20081124_164938,1,ks1.bak.