This topic describes how to run an Action.
Ensure that the following is in place:
To run SQL Actions, runme.sql is required. Before executing the Action, BMC Database Automation automatically replaces GA, GAC and GAD variables that are specified in runme.sql with the value that has been set in the environment when they are specified using curly brackets ({}); for example, {GA_DB_NAME}
and {GA_DB_ORACLE_HOME}
. This helps provide easy access to variables that are set in the environment of the SQL script. For more information about environment variables for Actions, see Actions environment variables.
In the Action page, populate the following fields, and click Next.
Section | Actions Field | Description |
---|---|---|
| Name | Displays the name of the Action. |
| Scope | Displays the scope defined for this Action. |
| Container | Displays the container defined for this Action. |
| Available to | Displays the target domains defined for this Action. |
| Description | Displays the description for this Action. |
| Template | Select the wanted template. |
Action Execution | Execution Sequence | Select how multiple Actions are run. |
| Rescan Nodes on Completion | (Optional) Select to scan the nodes after the Action has completed. |
| Continue on Error | (Optional) Select to allow serial activities to continue to run in the event of a failure. |
| Restrictions | Displays the restrictions specified for this Action. |
In the Job Options page, specify any of the following Job options, and click Next.
Type | Option | Description |
---|---|---|
Notification Emails | Email List | (Optional) Click Add Email to add email addresses to the notification list. |
| SNMP | (Displays when SNMP is configured) Select to send the results of this job to an SNMP destination. See Configuring SNMP. |
Job Administration | Cleanup Agent Logs | (Optional) Select to automatically remove logs that are generated by BMC Database Automation on the Agent after the job is complete. |
In the Scheduling page, select when to run this job in the Job Execution field, and click Next.
Note
The UNIX atd daemon must be installed and running on the Manager to schedule Actions. In addition, the crond daemon must be installed and running to schedule recurring Actions.
If the Change Control page displays, populate the following fields, and click Next.
Section | Field | Description |
---|---|---|
| Bypass Change Control | (Optional) Select to bypass using BMC Remedy ITSM to control the change process. Selecting this option removes the rest of the fields from this page. |
| Change Control Options | Select to determine whether to open a new BMC Remedy ITSM change ticket, or to use an existing BMC Remedy ITSM change ticket to control the change process.
|
Use Existing Change Ticket | ITSM Change ID | Specify the BMC Remedy ITSM change ticket number to associate with this change process. |
| ITSM Task ID | Specify the BMC Remedy ITSM task ID number to associate with this change process. |
Create New Change Ticket | Change Type | Assign the type of change for the new BMC Remedy ITSM change ticket. |
| Change Impact | Assign the impact level of this change process for the new BMC Remedy ITSM change ticket. |
| Change Urgency | Assign the urgency level for the new BMC Remedy ITSM change ticket. |
| Change Risk-Level | Assign the risk level of this change process for the new BMC Remedy ITSM change ticket. |
| Change Class | Assign the change class for the new BMC Remedy ITSM change ticket. |
| Change Summary | Type a summary of the change process. |
Note
The Change Control page appears only when change control is configured for your environment. See Configuring change control.
To run the Action without having first run the custom verification checks, select Skip Pre-Verification Tests.
Note
The Skip Pre-Verification Tests option should only be used when you are certain all tests can succeed. The option skips verification and advances directly to running the Action.
Click Execute Job or Schedule Job (depending on your selection in the Scheduling step).
If the Action is running, a progress page appears.
When you schedule an Action, it is added to the Jobs list. You can view scheduled Jobs by selecting Jobs from the Context Frame, specifying a start and end date, and filtering the Jobs list for a Scheduled status. After you schedule a job, the start date and time cannot be modified. If you need to change the schedule for a Job, you must cancel the Action and recreate it. See Cancelling an Action. After a Job has started running, it cannot be cancelled by using the Management Console.
If a target for an Action is in a Down state, or is no longer in the environment when the associated Job starts, the Job will stop due to the unavailability of the target, and the status of the Job changes to Failed.
Note
BMC Database Automation supports the ability to schedule and run multiple Jobs for Actions across different targets in parallel.
If you have uploaded custom verification checks, the Verification page displays. If all of the checks pass, click Continue to run the Action. If checks fail, resolve the identified issues and click Repeat Verification.