MSAMM
Back to course

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

When it is the client

Lesson 175 of 184 · 3 min

A browser, a Java version, a laptop, or ONE OFFICE. THE PATTERN OF WHO IS AFFECTED IS THE DIAGNOSTIC. Client-side problems are identified almost entirely by who is affected rather than by anything measurable on the server, which makes Module 11 Lesson 2's first question the whole method here. ONE PERSON IS THEIR MACHINE OR THEIR SESSION. Nothing on the server is wrong — and the useful check is whether they can reproduce it on a colleague's machine, which takes two minutes and settles it completely. ONE DEPARTMENT, DEFINED BY WHAT THEY USE, IS A CLIENT COMPONENT. Module 10 Lesson 7's failure: everybody using the Forms interface, because a Java update landed on their desktops. The population is defined by the tool rather than by the location or the role, which is the signature. ONE OFFICE IS THE NETWORK, AND IT IS LESSON 3. Defined by location rather than by

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