MSAMM
Back to course

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

Why anybody wants a clone

Lesson 57 of 184 · 2 min

Testing a patch, reproducing a bug, training, and a support request. EACH WANTS A SLIGHTLY DIFFERENT CLONE. "Make me a copy of production" is one sentence covering four different requests, and clarifying which one saves days. TESTING A PATCH NEEDS THE CONFIGURATION AND THE PATCH LEVEL TO MATCH EXACTLY, AND THE DATA BARELY MATTERS. A subset is fine, provided the shape is realistic. What must be identical is everything the patch touches — because a patch tested against an estate at a different level tested nothing about yours. REPRODUCING A BUG NEEDS THE OPPOSITE: THE DATA IS THE POINT. The bug is in a specific record with a specific history, and a clone with clean or sampled data will not reproduce it. Which makes this the clone with the highest confidentiality exposure, and Lesson 5's post-clone list matters most here. TRAINING NEEDS NEITHER, AND WANTS SOMETHING THE OTHERS DO NOT.…

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