MSAMM
Back to course

Oracle Apps DBA: Keeping E-Business Suite Alive · Module 17 · When it is not the database

When it is storage

Lesson 174 of 184 · 3 min

Latency that LOOKS LIKE A DATABASE PROBLEM from every angle except THE ONE THAT MEASURES IT. Storage is the hardest of these to identify, because every database-level measurement points at the database. THE DATABASE REPORTS SESSIONS WAITING ON I/O, WHICH IS MODULE 11 LESSON 3'S SECOND CATEGORY. Everything looks like a database that is reading too much — and the ordinary response is to tune the SQL so it reads less, which is usually right. WHAT DISTINGUISHES A STORAGE PROBLEM IS THAT THE AMOUNT OF READING HAS NOT CHANGED AND THE TIME PER READ HAS. The same query reading the same blocks takes three times longer than last month. That is not a plan problem and no amount of tuning addresses it — the database is being answered more slowly by the thing underneath it. SO THE MEASUREMENT THAT SETTLES IT IS AVERAGE TIME PER READ, COMPARED AGAINST THE BASELINE.

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 17 · When it is not the database

  1. 1Why the database is always blamed first
  2. 2Ruling the database in or out quickly
  3. 3When it is the network
  4. 4When it is storage
  5. 5When it is the client
  6. 6When it is a person
  7. 7Writing a finding somebody will accept
  8. 8What breaks: two arguments that went badly