MSAMM
Back to course

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

The post-clone checklist

Lesson 62 of 184 · 3 min

What must be changed BEFORE ANYBODY IS ALLOWED IN — starting with ANYTHING THAT CAN REACH THE OUTSIDE WORLD. The ordering principle is the whole checklist: outward-facing first, because those are the only items whose failure cannot be undone. A wrong port number is fixed in a minute; an email that left the building is not. SO THE FIRST GROUP IS DONE BEFORE THE APPLICATION TIER IS EVEN STARTED, WHICH IS WHY THE ORDER MATTERS RATHER THAN THE LIST. Disable outbound email at the system level, not by trusting a profile setting. Drop or repoint every database link. Disable printer definitions. Disable or repoint every scheduled job. Every one of these is doable with the services down, and every one of them is a Lesson 5 hazard that does not need a user. THE SECOND GROUP IS ACCESS. Reset or disable the accounts that should not carry production passwords into…

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