MSAMM
Back to course

Oracle Apps DBA: Keeping E-Business Suite Alive · Module 8 · Concurrent processing

Output, printing and delivery

Lesson 90 of 184 · 2 min

Where output goes, WHY A PRINTER DEFINITION SURVIVES A CLONE WHEN IT SHOULD NOT, and WHAT A USER MEANS BY "IT DID NOT PRINT". Output is written to the file system and then delivered — viewed on screen, printed, emailed, or dropped somewhere for another system. The request succeeding and the user receiving something are two separate events, and most complaints in this area are about the second. "IT DID NOT PRINT" MEANS ONE OF FOUR THINGS AND ONLY ONE IS A PRINTING PROBLEM. The request failed, so there is no output — Lesson 5, and the log has the answer. The request succeeded and produced empty output, which is a data or parameter question rather than a technical failure. The output exists and was never sent to a printer, because none was specified. Or it was sent and the printer did not produce paper, which is the only one…

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 8 · Concurrent processing

  1. 1What a concurrent request is
  2. 2Managers, queues and workers
  3. 3Specialisation rules
  4. 4Work shifts
  5. 5A request that will never finishFree preview
  6. 6Reading a request log
  7. 7Killing a request safely
  8. 8Managers that will not start
  9. 9Output, printing and delivery
  10. 10Purging: the table that ate the database
  11. 11What breaks: four concurrent processing failures