AutoSub is the sample implementation of a tool to automate the recovery of subscriptions of IBM Data Replication product in the event of DDL operation over the replicated tables in the source databases.
This tool uses CHCCLP embedded scripting and CDC engine commands to do its job. It periodically monitors the defined list of subscriptions. If it detects a recoverable failure of the replication process (subscription), it tries to fix it.
Pre-built binaries are available on the Releases page.
Basic installation and configuration instructions are provided in the README.txt file, which is also included in the installation binary file.
AutoSub depends on the IBM CDC Access Server libraries, which are not included in the binary package. IBM CDC Access Server needs to be installed on the host where AutoSub will be running. This copy of Access Server may be left unconfigured and does not need to be running, as AutoSub supports both local and remote connections to the CDC Access Server.
Version 2.0 has been created to avoid the data loss. There are still situations which cannot be recovered without the Refresh operation, the main example being the DDL -> DML -> DDL sequence on a single table. Some of the CDC engines (e.g. PostgreSQL and MSSQL) are just not DDL-aware enough to handle DDL operations on source tables without a Refresh.
By adding the Refresh operation to this sample, with some logic to detect those "nonrecoverable" situations, it is now possible to support the full set of cases, at the cost of an automated Refresh (which is also probably not a best option for all customers).
The application has been tested on Oracle, Db2, MSSQL and PostgreSQL data sources. The primary tested target is Kafka, although some checks have been done against DataStage and relational targets.
Build uses Maven. IBM CDC Access Server jars need to be installed
into the local Maven repository, see the example in the
iidr-cdc-setup-maven-libs.sh script.
Required Eclipse libraries are grabbed from central Maven repository, their versions should be validated against the particular Access Server version (through the names of jar files).