Status: Verified
GOAL:
What is the AI File Management Utility?
GOAL:
How to run the AI File Management tool ?
GOAL:
How do I enable automated AI File Management?
GOAL:
What is the command to enable AI File Management?
GOAL:
What steps are required for automated AI File Management?
GOAL:
How to enable aiarchiver?
GOAL:
How to start the database with aiarchiver properties?
FACT(s) (Environment):
All Supported Operating Systems
OpenEdge 10.1x
OpenEdge Database Category: Maintenance
FIX:
It is not the intent of this Solution to repeat the OpenEdge Documentation on the subject.
The After-Imaging (AI) File Management tool was first included in the database license with OpenEdge 10.1A. This tool allows users to manage their After Image files without the need to script the 'rfutil' utilities, by creating an archive of all FULL AI extents before marking these as EMPTY for re-use once the OpenEdge database has been enabled for archiving.
This tool consist of an AIMGT daemon that needs to be enabled and initialised with the following Steps :
1. Create directories on disks with sufficient space to archive AI extents.
2. Make sure that the database has after-imaging extents and after-imaging is enabled.
$ prostrct list dbname dbname.st .. will display the current structure,
if no ai files are present they will need to be added with:
$ prostrct add dbname addai.st .. where addai.st contains only the ai structure definitions and file locations
a database backup is a pre-requisite to enabling after-imaging
$ probkup dbname dbname_preai.bak
-OR-
$ rfutil dbname -C mark backedup .. note this command only marks the database as backed up, there is no physical backup created should it be needed.
then after-imaging can be enabled:
$ rfutil dbname -C aimage begin
3. Enable the database for AI file management:
$ rfutil dbname -C aiarchiver enable
4. Add AI file management parameters to the database broker startup parameters:
$ proserve <dbname> [parameters] -aiarcdir /usr1/aiarchives/,/usr2/aiarchives/ -aiarcinterval 120
Where:
-aiarcdir = /dir/dir, /dir/dir, ... (the primary directory and non-mandatory secondary directories created in step 1 above.
-aiainterval = IntegerValue (seconds ). If unspecified, the AIMGT deamon will switch extents as soon as they are marked FULL
NOTE: Since OpenEdge 10.1B, both ai and the ai archiver can be enabled online at the same time:
$ probkup online <dbname> <dbname>.bak enableai enableaiarchiver -aiarcdir <dir>
The following are some options that can be changed while the database is online and the daemon is active:
Re-set the archiving interval ONLINE with active daemon, including (zero) 0 to unset the interval:
$ rfutil <dbname> -C aiarchiver setinterval <n>
Change the archiving directory location:
$ rfutil <dbname> -C aiarchiver setdir <new directory location, comma seperated, no spaces>
Stop the daemon running:
$ rfutil <dbname> -C aiarchiver end
Manually archive an ai extent after the AIMGT deamon has stopped (by running "rfutil <dbname> -C aiarchiver end" or when db is shutdown):
$ rfutil <dbname> -C aiarchive extent <dir>/dbname.a1 <archive_dir>\dbname.a1.archived.ai.filenaming.convention
It is not strictly necessary to have AIMGT enabled to run this command line. Any Progress database using after-imaging can use this utility eg:
$ rfutil dbname -C aiarchive extent stdout [ | gzip ...]
Disable archiving:
$ rfutil <dbname> -C aiarchiver disable
This utility writes to it's own log file separate from the database in the same directory as the database Control Area ie <dbname>.db file:
dbname.archival.log
To monitor the running status of the AIMGT deamon, please refer to Solution P126848, "How to check if the AI Archiver is running ?"