Release 10.1B: OpenEdge Replication
User Guide
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 could 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 on restoring a database, see the "Restoring source and target databases" section.
- 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 on activities that are allowed and disallowed, see Table 5–17.
- OpenEdge Replication does not support two-phase commit enabled databases.
- OpenEdge Replication requires at least one ABL broker in order to function. This ABL broker must be started before any SQL broker. Specifically, the ABL broker must be the first broker started. When SQL brokers are started, you must not specify the -
DBService
startup argument.
Copyright © 2006 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095 |