Keep the following in mind when you are using after-imaging:

  • If the disk runs out of space and no empty after-image extent is available (even if you are using variable extents), you must perform emergency maintenance; otherwise, the database is forced to shut down. To prevent the database engine from shutting down when it exhausts after-image disk space, you must start your database with the after-image stall (-aistall) startup parameter.
  • You must archive and manage after-image extents as part of standard after-image processing. For further information about archiving your after-image extents, see Manage the OpenEdge Database.
  • If you use OpenEdge Replication with a TDE-enabled database where a hardware security module is enabled as a secondary authentication requirement, additional restrictions apply. For more information, see Ensure that replication or hot standby target can access HSM.