Question
Which DB2Z utilities can cause table suspend?
Answer
In general, whenever there is an action/change in a table that is not logged to the db redo logs, Replicate is not aware of the change. In this case, if Replicate continues as if nothing happened, there is a risk of loss of data or causing target endpoint to get our of sync. When Replicate detects such an action, it usually suspends the table. The only way you can 'unsuspend' a table is by reloading it so that it assures that the target enpoint will be in sync with source as it includes all the changes perfromed in the action that was not captured by Replicate and Replicate can safely continue CDC without risk of data loss.
When working with DB2 ZOS endpoint there are serveral db utilis runs resulting in subtype 83 diagnostic log records being written to the db log that will casue table to be suspended.
The known DB2/Z utilities that will cause suspend table are:
- LOAD RESUME ( all except shrlevel change )
- LOAD REPLACE ( note that LOG YES vs. LOG NO has no impact on suspension from LOAD ) - the internal parameter db2LoadOption can be used whether to ignore action or suspend table (as of Replicate 7.0 this parameter is set by default to is "IGNORE", in which case a warning message will still be printed).
- REORG DISCARD ( if any data is deleted )
- CHECK DATA DELETE YES ( if any data is deleted )
- RECOVER TO POINT IN TIME
