MSAMM
Back to course

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

What a clone does not copy

Lesson 61 of 184 · 2 min · Free preview

Printers, external directories, database links, credentials, scheduled jobs and email configuration. EVERY ITEM ON THAT LIST HAS SENT A TEST EMAIL TO A REAL CUSTOMER SOMEWHERE. A clone copies the database faithfully, and the database is full of pointers to the outside world. The clone utility reconfigures the system's identity; it has no idea what those pointers mean. EMAIL IS THE ONE THAT REACHES A CUSTOMER AND IT IS THE FIRST THING TO DISABLE. A clone with working mail configuration will send — statements, invoices, notifications, approval requests — to the real addresses in the copied data. Somebody runs a test batch on a training system and a thousand customers receive an invoice, and there is no recall. DATABASE LINKS POINT AT REAL SYSTEMS AND ARE THE QUIETEST HAZARD. A link that resolved to a production database still resolves to it from the clone. So a test on the clone…

This lesson is free

Watch the full lesson, with its written notes, without an account. It is one of the free lessons this course opens with.

Watch the full lesson

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