Oracle Apps DBA: Keeping E-Business Suite Alive · Module 8 · Concurrent processing
Managers that will not start
Lesson 89 of 184 · 2 min
The handful of causes, IN THE ORDER THEY ARE WORTH CHECKING. USUALLY NOT THE ONE PEOPLE CHECK FIRST. A manager that will not start is a common and quickly-solved problem, provided you check in the right order — and the order people use is roughly the reverse of the useful one. FIRST: IS THE DATABASE OPEN AND REACHABLE? A manager cannot start without it. This is checked first because it is instant and because it explains the case where NOTHING starts — and people skip it precisely because it feels too basic. SECOND: IS THE NODE NAME RIGHT? Managers hold the node they belong to, and after a clone or a host change that value is the old one — so the manager refuses to start on a host that is not the one it thinks it is on. Module 6 Lesson 10's third failure, and it is the commonest…
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.
In this module: Module 8 · Concurrent processing
- 1What a concurrent request is
- 2Managers, queues and workers
- 3Specialisation rules
- 4Work shifts
- 5A request that will never finishFree preview
- 6Reading a request log
- 7Killing a request safely
- 8Managers that will not start
- 9Output, printing and delivery
- 10Purging: the table that ate the database
- 11What breaks: four concurrent processing failures