MSAMM
Back to course

Oracle Apps DBA: Keeping E-Business Suite Alive · Module 16 · Environments: what test must not have

What breaks: three environment failures

Lesson 169 of 184 · 2 min

A REFRESH OVER A LIVE TEST CYCLE, a test system that EMAILED CUSTOMERS, and a patch VALIDATED ON AN ENVIRONMENT TWO LEVELS BEHIND PRODUCTION. THE REFRESH OVER A LIVE TEST CYCLE IS THE ONE WHERE NOBODY DID ANYTHING TECHNICALLY WRONG. The refresh was requested legitimately, performed correctly, and completed cleanly — and three weeks of somebody else's test data and configuration is gone. The requester did not know about the other team; nobody asked more broadly. Module 6 Lesson 8 and Lesson 4, and the defence is an announcement rather than a technical control. THE TEST SYSTEM THAT EMAILED CUSTOMERS IS THE ONE THAT LEAVES THE BUILDING. A clone with working mail configuration, a test batch, and real invoices to real addresses. There is no recall — and the damage is to a client's relationship with their own customers rather than to any system. Lesson 2's first item, and Module…

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 16 · Environments: what test must not have

  1. 1How many environments, and why
  2. 2What test must not haveFree preview
  3. 3Masking, and its limits
  4. 4Refresh cadence, and who decides
  5. 5Keeping environments comparable
  6. 6Access, per environment
  7. 7Documenting an estate
  8. 8What breaks: three environment failures
  9. 9Lab briefing · Write the handover pack