Recovering non-running and inconsistent managers


PATROL provides you with standard proactive management actions, or recovery actions, to apply to non-running and inconsistent managers. If one of the concurrent managers enters a non-running or inconsistent state, the ConMgrStatus state parameter enters an alarm state. If the internal manager enters a non-running or inconsistent state, the state parameter InternalMgrStatus will enter an alarm state.

You might encounter non-running or inconsistent managers in any of the following situations:

  • The concurrent manager is not running.
    In this case none of the concurrent manager's target processes are running. The ConMgrStatus parameter enters an alarm state and the icon of the non-running concurrent manager has an offline state.
  • The concurrent manager is in an inconsistent state.
    In this case one or more of the manager's target processes are down. The ConMgrStatus parameter enters an alarm state.
  • The standard concurrent manager, the Conflict Resolution Manager, and any other user-selected concurrent managers are not running.
    In this case the main concurrent managers are not running. The MGRMustExist parameter enters an alarm status.
  • The internal manager and/or the conflict resolution manager are not running.
    In this case none of the concurrent managers can run. The InternalMgrStatus parameter enters an alarm state.

If any of these situations occur, the corresponding parameter will alarm. In addition, a recovery action dialog box will inform you of the issue and prompt you for a response. The following table summarizes the situations covered by the parameters mentioned above.

Parameter

Green (OK)

Red (Alarm)

InternalMgrStatus

Internal Manager is running

Internal Manager is down

ConMgrStatus

All target processes of the concurrent manager are running

At least one of the target processes of the concurrent manager is down

MGRMustExist

Standard Manager, Conflict Resolution Manager, and all other selected managers are runninga

Standard Manager, Conflict Resolution Manager, or any other selected manager is down or offline 1

1 The Standard Manager and the Conflict Resolution Manager are monitored by default only if your language ID for Oracle Applications is US or AMERICAN.

The out-of-box setting for recovery actions is interactive recovery. For instructions on how to customize the recovery actions, see Customizing-KM-provided-recovery-actions.

Warning

Note

If multiple consoles are running, the recovery action for Internal Manager down will not work because PATROL will not be able to distinguish which user response is the correct response to accept. In this case, the recovery dialog box will provide instructions to manually start the Internal Manager.

For more information about the Conflict Resolution Manager, see the Oracle Applications System Administrator's Guide.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC PATROL for Oracle e-Business Suite 3.4