Timed mode archiving process with OpenEdge Replication
When you have OpenEdge Replication enabled on your database, the daemon follows a similar process for archiving extents:
1. Awake from five second sleep and archive all FULL and LOCKED AI extents.
2. Check to see if the time interval has expired. If the interval has expired, switch the current extent. Switching causes the current BUSY extent to be marked LOCKED, and the next EMPTY extent to be marked BUSY.
3. Mark archived FULL extents as EMPTY and LOCKED extents as ARCHIVED.
4. Sleep for five seconds.
The difference in the archiving process when OpenEdge Replication is enabled is that extents cannot be emptied until they have been fully replicated. Extents transition from the BUSY state to the LOCKED state. If a LOCKED extent is replicated before it is archived, it transitions to the FULL state and the AI File Management daemon archives it. If a LOCKED extent is archived before it is replicated, it transitions to an ARCHIVED state, and it becomes the responsibility of OpenEdge Replication to transition it to an EMPTY state when replicated.
The following figure shows the state transitions graphically.
