Engines & Platform Support
Engine coverage in DBReplay is gated by two different, independent things: a wire decoder for the source engine being migrated away from, and a driver plus emitter for the target engine being migrated to. Adding a source is specialised and expensive; adding a target is comparatively inexpensive. Commercially, that split falls the right way — the decoders already in hand are for the engines organisations migrate away from, and the emitters cover what they migrate to.
Source engines (capture & decode)
| Engine | Wire protocol | Notes |
|---|---|---|
| IBM Db2 LUW | DRDA | The reference decoder — framing, codepoint dispatch, the query and cursor protocol, the full handshake. |
| IBM Db2 z/OS DDF | DRDA | Same protocol as Db2 LUW; what differs is a negotiated dialect (manager levels, data representation, EBCDIC transcoding, S/390 hex float), identified explicitly on the wire at connect time rather than assumed from configuration. |
| IBM Db2 for i | DRDA | Same protocol family. Not yet a delivered decoder, but the least additional work of any candidate source given the existing DRDA foundation. |
| IBM Informix / HCL OneDB | DRDA (via the DRDA listener) | Reachable through the same DRDA decoder family where the DRDA listener is in use. |
What varies is the dialect, not the protocol
DRDA is an open standard spoken across the IBM estate. What changes
between a Db2 LUW source and a Db2 z/OS source is a negotiated dialect
— manager levels, data representation (TYPDEF), and a
handful of product-specific codepoints — not the protocol itself.
The negotiation happens explicitly at the start of the exchange, so the
decoder identifies the server product and its capability set from the
handshake rather than from configuration. That identification feeds the
capture manifest automatically.
Target engines (replay & dialect emission)
The dialect changer converts through a neutral intermediate representation — parse source dialect to neutral, emit target dialect — so engine pairs scale additively rather than multiplicatively as coverage grows. Db2 LUW and Amazon RDS for Db2 are the current target coverage; additional targets are added at the driver and emitter layer, independent of source decoder work.
Deployment platform
| Component | Runs as |
|---|---|
| Capture & replay | One combined container image, role selected at deployment. Same image, different privileges and secrets per role. |
| Storage | MongoDB, sized to the engagement's expected volume — statements-per-transaction and capture window length are what set the sizing, not raw transaction count alone. |
| Reporting | A generated, signed report per run, viewed through DBReplay's own dashboard — same framework and visual language as DBVoyeur, Oninit's SQL performance monitor. |
Confirming coverage for your engine pair
For a source or target not listed above, or to confirm current dialect coverage for a specific version, contact Oninit on +1 913 732 8892 (US) or +44 20 8133 7529 (UK), or email support.info@oninit.com.