MSAMM
Back to course

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

Preparing the source without an outage

Lesson 59 of 184 · 3 min

What can be done on a running system and what cannot, and THE TIMING THAT KEEPS A CLONE CONSISTENT. The good news is that preparing the source needs no outage. The preparation utilities read configuration and write it out; they do not stop services and they do not change the running system. You can prepare production during the working day. THE CONSISTENCY QUESTION IS ABOUT THE DATABASE COPY, AND IT IS THE PART THAT MATTERS. A file copy of a running database is not consistent by itself — the files are being written while you read them, so you get a mixture of moments. That copy cannot simply be opened; it needs recovery applied to bring it to a single point in time, which is why a hot clone is built from a backup plus archives rather than from a plain copy. SO THE THREE OPTIONS ARE: SHUT THE SOURCE…

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