Enabling restart processing

This section describes the tasks that you must perform to enable restart processing for the High-speed Apply Engine.

Before you begin

If the DBMS or operating system fails during apply processing, the High-speed Apply Engine maintains its position in the request that was running when the failure occurred.

When you restart the request, High-speed Apply Engine uses information in the restart table to automatically resume processing.

To enable restart processing

• Include the appropriate Restart-parameters in the configuration for the apply request. To optimize restart processing, use configuration parameters to adjust the checkpoint frequency, the number of agents, or the COMMIT actions of an apply request.For more information, see Specifying-and-using-restart-parameters.
• Create one or more restart tables. By default, High-speed Apply Engine uses a single restart table for all apply requests. However, if you run many apply requests simultaneously on the same target database, you might experience resource contention for the single restart table. If you experience contention, create a restart table for each user that runs apply requests simultaneously on the target database. This practice reduces the possibility of contention for the restart table. For more information about creating restart tables, see Creating-a-restart-table.
• Rerun the apply request that was in-process at the point of failure by specifying the appropriate restart ID for the request. For more information, see Restarting-an-apply-request.