Before setting up the method, the procedure must be created on the repository database using the database account of the repository owner (such as SYSMAN).
For metric severities and policy violations, the syntax for the procedure is:
PROCEDURE p(severity IN MGMT_NOTIFY_SEVERITY)
For job status changes, the syntax for the procedure is:
PROCEDURE p(job_status_change IN MGMT_NOTIFY_JOB)
For corrective action status changes, the syntax for the procedure is:
PROCEDURE p(ca_status_change IN MGMT_NOTIFY_CORRECTIVE_ACTION)
Note: The PLSQL procedure needs to be configured by a privileged user before a user can select it while he is creating/editing a notification rule.
Specify the PLSQL procedure that will be called in Notification Rules. The following information is required for each PLSQL procedure:
Name
Description
PLSQL Procedure
You must enter a fully qualified procedure name and ensure that the owner of the Management Repository has EXECUTE privilege on the procedure. For example, OWNER.PKGNAME.PROCNAME.
An example of the required information is shown below.
Name Cleanup error log
Description Notification method to clean up the error log table
PLSQL Procedure mgmt_rep.log_util.cleanup_log
There can be more than one PLSQL procedure configured per system.
For information about the severity types that relate to a target's availability, and how metric severity/policy violation information is passed to the PLSQL procedure, see About Passing Metric Severity Information.
About Passing Metric Severity Information
Enterprise Manager Information Roadmap
Copyright © 1996, 2007, Oracle. All rights reserved.