MSAMM
Back to course

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

Killing a request safely

Lesson 88 of 184 · 2 min

Cancelling, terminating, and THE DATABASE SESSION UNDERNEATH. What each leaves behind, and THE ONE THAT LEAVES A LOCK. There are three levels of force here and they leave three different messes. CANCELLING A PENDING REQUEST IS COMPLETELY CLEAN. It has not started, so nothing has happened. Always available and always safe. TERMINATING A RUNNING REQUEST ASKS IT TO STOP, AND WHAT IT LEAVES DEPENDS ENTIRELY ON THE PROGRAM. A well-written program notices, rolls back and exits. A program halfway through a multi-step process may leave the data half-updated — and that is the risk, not the terminate itself. Before terminating anything that WRITES, ask what it was in the middle of. AND KILLING THE DATABASE SESSION IS THE LEVEL THAT LEAVES A LOCK, WHICH IS THE ONE TO UNDERSTAND. The session is killed and Oracle begins rolling back its transaction — which for a long-running job can take as long…

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