RAC Monitor incorrectly shuts down watchworx and agentservice process - Applications Manager

Products

• Automic Applications Manager

Issue/Introduction

This article addresses an issue where the Applications Manager RAC Monitor incorrectly shuts down all Master services (watchworx, agentservice, and rmiserver) when a database change is detected, instead of restarting only the RmiServer process.

Environment

• Applications Manager 9.6.2 and below
• Oracle RAC configuration

Cause

The issue is caused by a product defect (DE209633) where the RAC Monitor process does not correctly isolate the RmiServer process for restart due to an unintended interaction with stopso/startso parameters.

Resolution

Workaround

If the RAC Monitor issue is impacting your environment, you may keep the watchworx process offline.

• Recent observations in Applications Manager versions (v8 and v9) indicate a low incidence of agentservice or rmiserver processes unexpectedly terminating.
• The watchworx process primarily monitors the presence of these processes and is generally only required in rare scenarios where processes are terminated unexpectedly (e.g., via a kill -9 command).
• Keeping watchworx offline should not typically present an issue in these environments.

Resolution

This defect is fixed in in a future version of Applications Manager. 

For defects and enhancements only: please subscribe to this article (reference: How to subscribe to a Knowledge Base article) to be updated on fix status.