Prior to Progress 9.1D, it is not possible to enable or disable After-Imaging online. Only offline RFUTIL arguments are available:
$ rfutil dbname -C aimage begin
$ rfutil dbname -C aimage end
Progress 9.1D introduced a new RFUTIL aioff argument disable after-imaging online, but after imaging still has to be enabled offline:
$ rfutil dbname -C aimage begin
$ rfutil dbname -C aimage aioff
Subsequent versions also use rfutil dbname -C aimage aioff for disabling after-imaging.
OpenEdge 10.1B, introduced after-imaging (AI) enablement online The database must already have After Image extent(s) created (whether added offline with PROSTRCT ADD or online with PROSTRCT ADDONLINE).
$ probkup online dbname <devicename> enableai
Similarily, the AI Archiver can optionally be enabled at the same time.
$ probkup online dbname <devicename> enableai enableaiarchiver -aiarcdir <archiving directory>
Note: If error 830 is returned is because AI is already enabled, in that case remove the enableai portion of the command.
Also, -aistall parameter will be automatically be set to enabled while the ai archiver is enabled, this is a requirement.
PROBKUP ENABLEAI uses the existing online backup feature to turn the AI database feature on online. The full online backup is used as the base to which AI roll forward can then be applied. After-imaging needs shared-memory for certain data structures and for the AI buffers. This memory is pre-allocated during the database startup. If -aibufs is not specified at startup, the -bibufs setting will be used. Therefore, in OpenEdge 10.1B, the broker allocates AI related memory even if AI is not (initially) enabled to support the online enablement feature. On restarting the database, the -aibufs parameter should be appended to the database startup parameters (guideline: 1.5 x -bibufs)
PROBKUP ENABLEAI online does not start the AIW, which is only available with an Enterprise Database License:
$ proaiw dbname
While PROBKUP ENABLEAI online automatically sets the ai blocksize to be the same as the current bi blocksize for performance reasons, offline ai enablement does not. Offline AI enablement does not consider the ai blocksize. If the ai blocksize needs to be changed, AI will need to first be disabled then re-enabled. This is easiliest re-done with the online options discussed above.
