The features of the IBC messaging are as follows:

• An IBC always causes any previous update activity to be flushed before delivery.

• As an administrator, you can decide the sequence of activities at the Secondary after receiving the message. For example you may decide to continue with the updates that have been received from the Primary or you may decide to freeze the replication and perform the activity mentioned in the IBC message.

• The IBC messaging functionality ensures that the messages are delivered correctly at least once.

• In the case of a network failure or system crash during the delivery of an IBC message, the IBC may be delivered more than once. The applications using the facility must be able to handle multiple delivery of the same IBC.

• Some IBC messages may freeze replication activity, until the application releases it. The delivery definition must therefore include the complete instruction to freeze and unfreeze.

• All the IBC messages are also logged in the Primary Replicator Log Volume.