MSAMM
Back to course

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

Cloning between different hosts and versions

Lesson 63 of 184 · 2 min

When the platforms differ, what is supported, and THE CASES WHERE A CLONE IS NOT THE RIGHT TOOL. A clone assumes the target can run what the source produced, and that assumption holds less often than people expect. A DIFFERENT OPERATING SYSTEM IS THE HARD LIMIT. Executables are platform-specific, so a file system copied from one platform to another is not runnable — and the database files themselves may be in a different byte order. Moving between platforms is a MIGRATION, with its own tools and its own project, and calling it a clone is how somebody promises a two-day job that is a two-month one. A DIFFERENT VERSION OF THE SAME PLATFORM IS USUALLY FINE AND OCCASIONALLY IS NOT. The prerequisites differ, so a target on an older release may be missing a package or a kernel setting the source depended on — which surfaces as a component that…

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