Cannot disable replication offline when AI extents are LOCKED and the BUSY extent is full

Cannot disable replication if database is shutdown and there are no AI space remaining in the current AI sequence error 3775

Cannot disable replication offline when AI extents are all LOCKED and the BUSY extent is full.
Disabling Replication offline requires an AI switch

Disabling Replication online with DSRUTIL does not trigger an AI switch

A one entry transaction table is allocated when the database is opened in single user mode. Since there is no space in the current BUSY AI file to save this entry, an AI switch is needed which then fails due to no EMPTY AI extents available in sequence.

Upgrade to OpenEdge 10.1B02 Service Pack or later.

Add additional AI areas:

Adding AI areas will only work if the BUSY area is physically the last AI area, so that any newly added EMPTY areas would follow.   There is a known issue with PROSTRCT reorder ai, whereby the reorder fails when these conditions are not met.  Refer to Article 000011649  

The following Workarounds will need after imaging and replication to be re-established once complete.

1.  Backup the database using probkup with the -norecover option and then restore the database into a new structure.
2.  Restore the source database from a previous backup and roll-forward AI files.

3.  Disable replication by rebuilding the Control Area:

With source db down:

Ensure structure file is current:
Rename the Control Area
Rebuild the Control Area
$  prostrct builddb dbname.

At this point replication will need to be re-established. 

4.  Force entry into the database and dump/load the data.  Not recommended because the force option can cause corruption.

 

Progress Articles: 

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