Synchronization Limitation with IBM Db2 for i

When CLRPFM is Not Supported in Synchronization

If you are planning a synchronization replication with IBM Db2 for i (iSeries/AS400) as a source or target database, note that any CLRPFM commands which Syniti Replicate encounters in the journal will not be propagated to the destination table. Synchronization does not support the use of clear on physical members, although clear commands are supported for mirroring replications.

To work around this restriction, avoid calling the CLRPFM command, replacing it with DELETE FROM TABLE without adding a WHERE condition.

Note

Syniti Replicate does not support LOB data types.

When Synchronization Requires Usernames in the Db2 Journal

If you are performing replications in Synchronization mode with IBM Db2 for i (iSeries/AS/400), you must ensure that all database operations performed by Syniti Replicate are logged (journaled) using the username DBMOTO or another username dedicated exclusively to Syniti Replicate, as specified during setup.

The algorithm used to identify database changes that must be synchronized, looks for changes made by specific users other than the one you have identified exclusively for Syniti Replicate use. Therefore, usernames must be included in the journal.

To verify that journal and receiver settings include username information:

1. Open a console on IBM i (iSeries/AS400.)

2. Check the journal properties using the command CHGJRN and supplying the journal and library name.