The following Workarounds subvert this behaviour:
Option 1: Restart the database, the new AI files added online previously will switch as expected when their fixed-variable extent size is reached.
Option 2: Until the database can be restarted,
as opposed to relying on when the fixed variable size is reached force an ai switch.a. If the database is enabled for AI Management (AIMGT), change the aiarchive interval mode from "ON DEMAND" to "TIMED" to force the ai switch at a timed interval:
$ rfutil dbname -C aiarchiver setinterval {120 ... 86,400}
b. If the AIMGT deamon is not in use, then ensure that the 'rfutil' scripts which manage the database ai files include a manual switch at timed intervals:
$ rfutil dbname -C aimage new
Option 3: Restructure AI files to Fixed Extents as opposed to Fixed Variable extents if 'automatic' ai switching is required by the after-imaging implementation.
Stop the database then disable After Imaging:
$ rfutil dbname -C aimage end
Run the following command as many times as there are ai files:
$ prostrct remove dbname ai
Create a new structure file defining AI files with fixed AI extent format:
a . f 20480
a . f 20480
a . f 20480Add ai files back to the database:
$ prostrct add dbname addai.st
Re-enable After-Imaging and AI Archiver (if required):
$ rfutil dbname -C mark backedup
$ rfutil dbname -C aimage begin
$ rfutil dbname -C aiarchiver enable
