Oracle Apps DBA: Keeping E-Business Suite Alive · Module 6 · Cloning
Refreshing rather than cloning
Lesson 64 of 184 · 2 min
Overwriting an existing environment. What is PRESERVED, what is DESTROYED, and WHO NEEDS TO BE TOLD FIRST. A refresh is a clone onto an environment that already exists and already has people using it, and that changes everything about the risk. A new clone destroys nothing; a refresh destroys whatever was there. WHAT IS DESTROYED IS EVERYTHING THAT ENVIRONMENT ACCUMULATED SINCE THE LAST REFRESH. Test data somebody built over three weeks. Configuration under test. A half-finished test cycle. A custom object a developer deployed there and nowhere else. All of it, silently, because the refresh does not know any of it was special. WHAT IS PRESERVED IS ONLY WHAT YOU DELIBERATELY PRESERVE, AND THAT MEANS EXPORTING IT FIRST. There is no partial refresh — the environment becomes a copy of the source, and anything that must survive has to be taken out beforehand and put back afterwards. SO THE "WHO…
The full lesson is part of the course
The video, the complete written lesson and the module quiz are included in Oracle Apps DBA: Keeping E-Business Suite Alive, with a certificate on completion and a fourteen-day refund window.
In this module: Module 6 · Cloning
- 1Why anybody wants a clone
- 2The clone process, end to end
- 3Preparing the source without an outage
- 4Configuring the target
- 5What a clone does not copyFree preview
- 6The post-clone checklist
- 7Cloning between different hosts and versions
- 8Refreshing rather than cloning
- 9Making it repeatable
- 10What breaks: four cloning failures
- 11Lab briefing · Clone, then find what you missed