MSAMM
Back to course

Oracle Apps DBA: Keeping E-Business Suite Alive · Module 6 · Cloning

Making it repeatable

Lesson 65 of 184 · 2 min

A clone that takes TWO DAYS AND A PERSON is a clone that HAPPENS RARELY. What to script, and WHAT TO LEAVE MANUAL ON PURPOSE. The cost of a clone decides how often the business gets one, and that has consequences well beyond convenience. An expensive clone means tests run against stale environments, patches are tested less thoroughly, and a disaster recovery rehearsal never happens — which is Module 5 Lesson 2's finding arriving through the back door. SO MAKING IT REPEATABLE IS A RECOVERABILITY INVESTMENT RATHER THAN A CONVENIENCE ONE, and that is the argument to make when asking for the time to do it. WHAT TO SCRIPT IS THE MECHANICAL AND REPETITIVE: the file transfer, the preparation and configuration calls, the service start, and — most valuably — the post-clone checklist from Lesson 6. Those items are the same every time and they are the ones skipped under…

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.

See the course and enrol9 free lessons

Get the free lessons by email

We will email you a link to every free lesson in this course. No account needed, and one message only.

In this module: Module 6 · Cloning

  1. 1Why anybody wants a clone
  2. 2The clone process, end to end
  3. 3Preparing the source without an outage
  4. 4Configuring the target
  5. 5What a clone does not copyFree preview
  6. 6The post-clone checklist
  7. 7Cloning between different hosts and versions
  8. 8Refreshing rather than cloning
  9. 9Making it repeatable
  10. 10What breaks: four cloning failures
  11. 11Lab briefing · Clone, then find what you missed