Handle execution conflicts predictably
Related topics
Control how High‑speed Apply Engine responds to SQL codes and database messages by defining conflict resolution rules and optional conflict files.
The benefits include:
- Precise Code-to-Action handling in accordance with the statement type Insert, Update, Delete, or DDLConflict
- Deferred output for later analysis or re‑execution via conflict files
- Clear configuration semantics (positional Code/Action groups)
Workflow for conflict handling
| Task | Product | Role | Action | Reference |
|---|---|---|---|---|
| 1 | BMC High‑speed Apply Engine | Db2 DBA | Define general rules in AnyConflict (for example, TimeOut to Retry) | |
| 2 | BMC High‑speed Apply Engine | Db2 DBA | Override behavior per statement type (Insert, Update, Delete, and DDLConflict) | |
| 3 | BMC High‑speed Apply Engine | Db2 DBA | Configure ConflictFile parameters (for example, FileNameModel, SingleFile) | |
| 4 | BMC High‑speed Apply Engine | Db2 DBA | (Optional) Tune multi‑row insert conflict behavior | MaxConflicts |
Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*