Support Db2 recovery processing
Related topics
By using BMC High‑speed Apply Engine during Db2 recovery, you can undo incorrect transactions or redo correct transactions after a Db2 recovery operation, with controlled execution and reliable restart behavior.
The benefits include:
- Running targeted undo or redo changes as part of a structured recovery workflow
- Resuming from the point of failure via restart tables and restart IDs (no need to reprocess completed work)
- Maintaining predictable runs via configuration parameters and optional conflict resolution rules
Workflow for supporting Db2 recovery processing
| Task | Product | Role | Action | Reference |
|---|---|---|---|---|
| 1 | BMC High‑speed Apply Engine | Db2 DBA | Prepare input for recovery (undo or redo), using SQL statements or logical log files | Input sources for apply requests |
| 2 | BMC High‑speed Apply Engine | Db2 DBA | Enable restart processing to resume from failure points and create or assign the restart table | |
| 3 | BMC High‑speed Apply Engine | Db2 DBA | Create an apply request (batch job or command) that references the input and configuration | |
| 4 | BMC High‑speed Apply Engine | Db2 DBA | Run the apply request to perform undo or redo and monitor job output and verify results | Using |
| 5 | BMC High‑speed Apply Engine | Db2 DBA | If a failure occurs, restart the request using the correct restart ID and avoid modifying input sequence | |
| 6 (optional) | BMC High‑speed Apply Engine | Db2 DBA | (Optional) Define conflict resolution rules to control behavior for SQL codes or messages during recovery |
Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*