Restart and recovery
This section provides an overview of restart processing for the High-speed Apply Engine product.
If your operating environment or DBMS fails while the High-speed Apply Engine is running, you can use the information in a restart table to continue apply processing from the failure point. Restart processing prevents High-speed Apply Engine from repeating transactions that have already been processed.
The High-speed Apply Engine restart table resides in your target database. For Db2 on mainframe targets, it must reside on the target Db2 subsystem. If you enable restart processing, High-speed Apply Engine stores information in the restart table during each run of an apply request. Depending on your target database environment, the structure of the restart table is shown in the following samples in Creating a restart table:
- Sample DDL to create a restart table: Db2
- Sample DDL to create a restart table: Db2 LUW
- Sample DDL to create a restart table: Oracle
If you need more information about the content of the restart table, contact BMC Support.
You must create a default restart table during installation. You can define additional (personal) restart tables as needed in your environment. The procedures in this topic describe how to create restart tables, specify the appropriate configuration parameters, and restart an apply request. Specifying and using restart parameters summarizes two different ways that you can define restart parameters in your environment.
Warning
In general, do not modify the input file of an apply request between initial run and restart. Modify the configuration file only to the extent required to resolve error conditions. Ensure that changes to the configuration do not alter the distribution of work between agents. For example, do not change the values of configuration parameters such as MaxAgents, DistributionType, PartitionClustering, or RIClustering.
Comments
Log in or register to comment.