PROSTRCT reorder ai fails if AI extents are all FULL/LOCKED and busy extent is full

PROSTRCT reorder ai fails with error 12196 if AI extents are all FULL/LOCKED and the BUSY extent is full

Replication enable database.
BUSY AI extent surrounded by LOCKED AI extents in sequecne
BUSY AI file is full because it has reached its fixed extent size or has hit user, os or disk size limits on the filesize.

All extents are scanned from Area 6 (Schema Area) to the end of the database extent list to check for EMPTY, FULL and LOCKED states of each AI extent found to build the list for re-ordering these AI extents. The 12196 error is thrown when it finds an AI extent in a different state (BUSY)

Upgrade to OpenEdge 10.1B03 Service Pack or later where the BUSY extent is not checked when current AI extent status's are scanned to build the reorder list. 

Prior to OpenEdge 10.2B, when adding AI files to a database that already has fixed length AI extents, ensure that the new AI extents are the same size as the original ones.  For further information please Refer to Article  Error 9444 after adding AI extents and using PROSTRCT REORDER   

Workarounds:

1.  If any AI areas are marked as FULL, empty those areas and retry the PROSTRCT reorder ai command.

If OpenEdge Replication is enabled and all extents are LOCKED, there is currently no way to re-order the AI areas.  You will need to backup & restore the database:

1.  Backup the database using PROBKUP with the -norecover option and then restore the database into a new structure.

probkup <dbname> <dbname.bkup> -norecover

2. Restore the source database from a previous backup and roll-forward AI files, delete the recovery files, enable after imaging and replication and re-create the target database.

Progress Articles:

 Cannot disable replication if database is shutdown, AI extents are all LOCKED, and busy extent is full   
 PROSTRCT addonline hangs if all AI extents are LOCKED and BUSY extent is full