MSAMM
Back to course

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

When it is the network

Lesson 173 of 184 · 3 min

The symptoms that point that way, what to measure, and HOW TO HAND IT OVER WITH SOMETHING MORE USEFUL THAN A SUSPICION. Network problems are the commonest non-database cause and the one most often handed over badly. THE SYMPTOMS ARE DISTINCTIVE ONCE YOU KNOW THEM. A query that is fast on the database host and slow from the application host — Lesson 2's fourth step. Slowness that correlates with LOCATION rather than with what people are doing: one office affected and another not. And a chatty operation being disproportionately slow, because a process making a thousand small round trips pays the latency a thousand times while one large query pays it once. THAT LAST PATTERN IS THE MOST DIAGNOSTIC. If a report is slow and a bulk operation moving far more data is fine, that is latency rather than bandwidth — and it points at the network even though the

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