MSAMM
Back to course

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

Keeping environments comparable

Lesson 166 of 184 · 3 min

A test that does not match production TESTS SOMETHING ELSE. Patch levels, configuration and data volume — THE THREE THAT MATTER. This is the single assumption everything in Modules 7 and 14 rests on, and it is the one most often untrue. PATCH LEVEL IS THE FIRST AND THE MOST ABSOLUTE. A patch validated on an environment two levels behind production was validated against a different system — Module 7 Lesson 13's fifth failure. The result is not less reliable; it is unrelated, and reporting it as a successful test is how a failure reaches production having been signed off. CONFIGURATION IS THE SECOND AND THE HARDEST TO KEEP. Profile options, setups, custom configuration — every change made in production has to reach test, and production changes are made under pressure by people who are not thinking about test. Drift here is invisible until a test passes and production does

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.

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