43
21-14 Oracle E-Business Suite Developer's Guide
Concurrent Manager Process Terminations
When you start up your concurrent processing facility, the internal concurrent manager
starts up all the concurrent manager processes defined. The internal concurrent
manager monitors the operation of these concurrent manager processes to make sure
they function as defined. If any of these processes exits abnormally, the internal
concurrent manager starts up a new process to ensure the correct number of concurrent
manager processes are running. This monitoring process is completely invisible to you
or your users.
Typically, if a concurrent manager process terminates abnormally while running a
request, the request then completes with a phase/status of Complete/Error. If the
running request is a sub-request (such as a member of a report set), the request
completes with an Error status. When the parent request (such as a report set) restarts
and detects the failure of the report, it notifies the concurrent manager process whether
to abort or continue processing other sub-requests. If the running request is a parent
request (such as a report set), the request completes with an Error status and the status
of its sub-requests are all updated to Error.
If the failing concurrent manager process is an internal concurrent manager process, all
you need to do is to restart your concurrent processing facility. Although the internal
concurrent manager terminates abnormally, other concurrent manager processes
continue to operate and newly submitted concurrent requests keep going into other
available concurrent manager queues.
The only concurrent requests affected by a failure of the internal concurrent manager
process are run alone concurrent programs and concurrent programs that have
incompatibilities. If these concurrent requests are submitted after the internal
concurrent manager exits abnormally, they remain in pending status until you restart
the internal concurrent manager process. If these concurrent requests are submitted
before the internal concurrent manager's abnormal exit, they remain pending and hold
up all other concurrent requests belonging to the same logical database unless you put
these affected requests on hold. Once your internal concurrent manager is running
again, it resumes the duty of monitoring other concurrent manager processes and
coordinating the processing of concurrent programs that are run alone or have
incompatibilities.
Shutdowns of Operating System and Database
Unusual operating system exits and abnormal database shutdowns are two common
reasons that cause concurrent manager processes to fail. In these situations, all the
concurrent manager processes are terminated without any notice and the phase and
status of your concurrent requests remain as they are. All you have to do to resume
normal concurrent processing is restart your concurrent processing facility. Once you
restart your concurrent processing facility, your concurrent managers rerun all the
requests that were running at the time the concurrent manager processes failed. After
processing the previously running requests, the concurrent managers then process
other pending concurrent requests.
