You are on page 1of 3

Concurrent Processes Window

View status information about the processes of a specific concurrent manager, whose
name and node are identified near the top of the window.
Displaying this window automatically queries all processes that are currently active,
migrating, or terminating, as well as processes that have been terminated or
deactivated.
Display order is by status value (Active, Migrating, Terminating, Terminated,
Deactivated) and within status, by the order in which processes were started.
If you wish to reduce the number of displayed processes, you can delete records by
submitting the "Purge Concurrent Request and Managers" report from the Run
Requests form. You can delete records according to the number of days since the
processes were started. However, you cannot delete the records of currently active
managers.
Status
This field cannot be updated. The following are valid status values:
Active
Currently running manager processes display as "Active".
Deactivated Manager processes that are no longer running display as "Deactivated".
These processes were deactivated by you choosing the Deactivate button in the
Administer Concurrent Managers block, or by the Internal Concurrent Manager
deactivating a concurrent manager at the end of that manager's work shift.
Migrating Managers that are migrating between primary and secondary nodes display as
"Migrating".
In a parallel concurrent processing environment, concurrent managers run on
either the primary or secondary node assigned to them. Managers migrate to the
secondary node if the primary node or the database instance on the primary node is
unavailable. Managers migrate back to the primary node once it becomes
available.
Terminating Manager processes that are being terminated display as "Terminating".
These processes were terminated by you choosing the Terminate button in the
Administer Concurrent Managers block, or by a user selecting "Terminate" in the
Concurrent Requests form.
Terminated Manager processes that have been terminated display as "Terminated".
These processes were terminated by you choosing the Terminate button in the
Administer Concurrent Managers block, or by a user selecting "Terminate" in the

Concurrent Requests form.

Manager Identifiers Concurrent


This field displays a number generated by the individual concurrent manager that
identifies the process. This field cannot be updated.
This number may be referenced if an operating system process ID is not available.
You can use this number to view the log file associated with the process. (This is the
same log file you view when you select Manager Log from the View field of the
Concurrent Requests form):
o At the operating system level, locate yourself in the log directory
$FND_TOP/APPLLOG.
o For concurrent managers, use W<number>.mgr.
o For Internal Monitor processes, use I<number>.mgr.
Manager Identifiers Oracle
This field displays the ORACLE process ID associated with the manager process.
This field cannot be updated.
Manager Identifiers System
This field displays the operating system process ID associated with the manager
process. This field cannot be updated.
Request Identifiers Running
Please note the following about this field:
o Normally this field is blank, as the run-time of a request is typically very
short.
o For a terminated manager, the ID of the request being processed at the
time of termination is displayed.
Request Identifiers System
This field displays the operating system process ID for a spawned concurrent process.

Viewing Log Files


Use the three buttons near the bottom of the window to view log files. Log files record
information that may be helpful when diagnosing problems.
Request Log

Choose this button to view the log file of the process associated with the
running request.
Internal Manager Choose this button to view the Internal Concurrent Manager's log file.
Log
Manager Log
Choose this button to view the log file of the concurrent manager who
started running the request.

Concurrent Requests Window


View all running and pending requests for a selected manager, whose name and node
are identified near the top of the window.

Request Diagnostics Window


This window informs you when the request completed or if it did not complete, shows
you a diagnostic message indicating why.
See Also
Concurrent Manager field help
Overview of Concurrent Processing
Life cycle of a concurrent request
Defining Managers and their Work Shifts
Controlling Concurrent Managers
Overview of Parallel Concurrent Processing
Previous

Next

Contents

Index

Navigation

Glossary

Library

You might also like