Week 2 of 8
Ownership and environments
On Fusion, Oracle patches, updates and hosts every environment. It does not test your configuration, your roles, your integrations or your reports. Oracle’s own guidance is to test in the non-production pod before production, and to raise a service request at once if something breaks.
Your test pods are only as good as their last refresh. A production-to-test (P2T) refresh takes up to 48 hours, can run at most once every 7 days, and cannot run in the 5 days before maintenance. It also does not copy integration endpoint URLs, scheduled process parameters, SSO or MFA settings.
This week: name the owners and write down what each pod is for
- List every environment in your family (production, test, development, any extra pods) with its purpose, owner and patching cadence.
- Fill in the Testing CoE RACI so update testing, refresh scheduling and Oracle service requests each have one accountable owner.
- Plan P2T refreshes outside the update window. Production is patched two weeks after test, so a P2T cannot run in that gap.
- Write a post-refresh checklist: re-point integration endpoints, re-enter scheduled process parameters, check credentials and SSO, then run a smoke test.
- Decide whether you need masked data in test. Oracle’s refresh masking is a separate subscription.
Number of the week
48 hours
is how long Oracle says a P2T or T2T refresh typically takes, with the target unavailable throughout. Longer with masking.
Source: Oracle, Refreshing an Environment (OCI documentation)Use this week
- Oracle OIC Integration & P2T Refresh Tracker →
Includes a P2T refresh checklist built from what Oracle does and does not copy.
- TCoE Operating Model & RACI →
One accountable owner per testing activity, with an automatic check.
Next week: Oracle has no public test methodology with named quality gates. We write the test strategy your program will inherit.
Get the playbook in your inbox, one week at a time
Subscribe free and every template in the library is yours.