The following restrictions and limitations exist in Event Replicator Target Adapter:

• Adabas changes to the primary key are not supported by Event Replicator Target Adapter because it requires a cascading update to the RDBMS tables. The Adabas primary key is used to relate the root table with the MU/PE tables in the RDBMS. At this time, most relational databases do not support such cascading updates via SQL commands. Consequently, if you change the primary key in Adabas, the referential integrity of the data in the RDBMS tables will be violated. Support for cascading changes will be implemented in a future release of Event Replicator Target Adapter.

• Transaction caching for replicated Adabas transactions is currently only supported when only one file is replicated per transaction and per subscription. If a single Event Replicator subscription is likely to send modifications to multiple files in a single transaction, you should not use the Transaction Cache feature. See the documentation for Event Replicator Target Adapter Administration for information on how to activate or deactivate transaction caching in the Engine configuration. As of Fix2 to Event Replicator Target Adapter, Transaction Caching is off by default.