My Oracle Support Banner

Corrective Action Only Works Once, The Second Time Is Requested But Never Executed (Doc ID 2587914.1)

Last updated on NOVEMBER 16, 2022

Applies to:

Enterprise Manager Base Platform - Version and later
Information in this document applies to any platform.


Having a target metric with a corrective action being set to both Warning and critical thresholds, the Corrective Action (CA) is no longer executed after the first execution( ie. the CA is executed the first time, then the alert is cleared, then the condition is met again and does not execute again).

The following scenario is happening:

- Create one CA to execute an OS command on a target DB, save it to the CA library
- Assign the ca to both warning and critical thresholds for a metric 
- Raise a warning alert. The CA is triggered successfully.
- Raise a critical alert. The CA is triggered successfully.
- Wait a day or two after the alert is cleared. Raise another warning alert. The CA is requested to be executed, but it's not
- Trigger a critical alert now. The CA is not executed and a new message is displayed:

Another Corrective Action MY_CA_TEST not run since there is an existing running execution of Corrective Action {1}"

The sysman.mgmt_system_error_log table will show errors as follows:

13-JUN-2018 11:18:31
ERROR Could not create CA for policy 911DA25A45509FBD69149CAE87B9E154 Target
D703D476A D9A77F4123A786A26C9E58E Violation GUID
CD051318F48E4FACB9D011F9422DAD69 Key Value E:\oracle\mydata\orcl\mydir:
ORA-20402: 1 required job parameter(s) missing: command





To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.