Confirm the source and the topology
Oracle’s ODI 14.1.2 guide identifies 12.2.1.4 as the source release and provides different upgrade topologies. Use the procedure that matches the installed agents and domain configuration. Do not borrow a starting version from the Forms or WebLogic upgrade documentation.
Inventory each master and work repository, agent deployment, context, data server, Knowledge Module, mapping, scenario, load plan and schedule. Include external schedulers and scripts that invoke ODI. Identify shared WebLogic or database dependencies where present; a shared product family does not mean every installation shares a domain.
Plan recovery beyond the repository backup
The recovery boundary must cover the affected repositories and configuration at a consistent point. Rehearse restoration before production execution and prevent both environments from running the same schedules.
Repository restoration does not reverse changes already written to a source or target system. For each business-critical load, define how to identify partial output, resume or reverse it safely, and reconcile the result. Agree the owner and decision point for stopping the cutover.
Define acceptance before running the upgrade
| Area | What to establish |
|---|---|
| Topology | Each context resolves to the intended physical system and schema |
| Credentials and drivers | Supported connectivity works without copying production secrets into uncontrolled test environments |
| Agents | The selected runtime starts, connects and executes representative work |
| Mappings and Knowledge Modules | Custom code and generated operations produce the expected result |
| Scenarios and load plans | Required runs complete, failures are visible, and restart behavior is understood |
| Scheduling | Exactly one intended scheduler owns each production job after cutover |
| Data outputs | Counts, control totals, rejected records and business rules reconcile with the agreed baseline |
Follow Oracle’s exact-release upgrade and post-upgrade instructions when deciding which assets require regeneration or other changes. Compare behavior on an isolated representative dataset; successful agent startup alone is insufficient.
Coordinate the cutover
Use rehearsal results to estimate elapsed time, including validation and recovery decisions. Repository size alone cannot determine the window. Confirm downstream availability, job dependencies and the treatment of partially completed loads.
ODI 12.2.x lifecycle planning belongs alongside the rest of the estate. The support dates tool provides the policy dates; hosting a release on OCI does not change its support tier.
ECMWorks can help scope repository, agent and integration dependencies and define acceptance evidence. Discuss the ODI estate before choosing a production sequence.