Try OpenEdge Now
skip to main content
User Guide
Planning for OpenEdge Replication : Understanding the importance of after-imaging in OpenEdge Replication planning : Understanding limitations and restrictions
 

Understanding limitations and restrictions

Before you begin implementing OpenEdge Replication, you should be aware of the following:
*If you perform a BI truncate on your database and the BI truncate alters the database in any way—for example, BI truncate after abnormal database end—there is a possibility that active transactions will be undone. This process generates AI transaction log records. Since OpenEdge Replication is not running at the time the BI truncate is run, all AI areas can potentially fill up. Therefore, be sure to have enough available space in your AI areas to handle this event.
*A database that is enabled for OpenEdge Replication cannot be restored unless OpenEdge Replication is first disabled. For more information about restoring a database, see Restoring a source database.
*In general, a database enabled for OpenEdge Replication cannot be modified in structure or data when OpenEdge Replication is not running.
When OpenEdge Replication is running, there are specific activities allowed on the source and target databases. If an attempt is made to perform unauthorized activity, an error message is logged and the activity is disallowed.
For specific details about activities that are allowed and disallowed, see Utilities and OpenEdge Replication.
*OpenEdge Replication does not support databases enabled with two-phase commit.
*OpenEdge Replication does support databases enabled for JTA transactions. You must enable your source database for JTA transactions. JTA transactions are automatically enabled on target database when once both databases are started and replication activity resumes. For more information on JTA transactions, see OpenEdge Data Management: Database Administration and OpenEdge Data Management: SQL Development.
*OpenEdge Replication requires at least one ABL broker in order to function. This ABL broker must be started before any secondary broker. Specifically, the ABL broker must be the first broker started, the -DBService startup argument must be specified, and the broker must support ABL clients. When secondary brokers are started, you must not specify the -DBService startup argument.