Running an Action
This topic describes how to run an Action in BMC Database Automation (BDA). BDA supports the ability to schedule and run multiple Jobs for Actions across different targets in parallel.
Before you begin
Ensure that the following is in place:
- To schedule a job to run later, the UNIX atd daemon must be installed and running on the Manager to schedule Actions.
- To schedule recurring Actions, the crond daemon must be installed and running.
Note
To run SQL Actions, runme.sql is required. Before executing the Action, BDA 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.
To run an Action
- From the Management Console main page, select Actions > Action Repository.
- In the Action Repository page, locate the Action you want to run and select Run from the list box in that row.
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.
Parallel: Runs the Action in parallel across nodes containing the selected candidates, with activities on each node running in serial. Candidates that share a dependency (that is, are on the same host) would revert to running in serial.
Serial: Runs the Action to completion on one candidate at a time.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 Custom Fields page, select or enter the values for any custom fields that appear, and click Next.
Note
This page appears only when in the BMC Database Automation XML template, either custom fields are defined used for this action or NEW IN 8.9.03any custom fields are defined for the scheduling options (present on the Scheduling page in this wizard). If you have defined custom fields for scheduling options, value of those options on the Scheduling page will be derived from these custom fields. For more information, see Adding custom fields to a template.
In the Candidates page, select the candidates on which this Action is run, and click Next.
Note
The candidates list does not get refreshed automatically. Click the Reload Candidates button to refresh the list.
You can sort the list of servers in the Candidates list to make it easier to find the server, or type a string in the Find Candidates field and click Find.
The following example shows Oracle Pluggable Database (PDB) including hostnames and Container Database (CDB) names in the Candidates list so that you can distinguish a PDB-scoped Action and its attributes from other PDBs.Note
You can select multiple PDB candidates to apply changes across multiple PDBs while running a just single 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.
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.
NEW IN 8.9.03If you choose to run the job now or at a future time, optionally, you can use the Set Maintenance Window option to specify the Maintenance Window Start Time and the Maintenance Window End Time during which the job should be scheduled and running.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.
- Selecting Use Existing Change Ticket displays the fields in the Use Existing Change Ticket section on this page.
- Selecting Create New Change Ticket displays the fields in the Create New Change Ticket section on this page.
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.
- In the Summary page, review the provisioning information.
To make changes, do the following:- Click Go to to return to the provisioning step that you want to edit.
- Make your changes.
- Click Save and Review to return to the Summary page.
- If you have uploaded custom verification checks for this Action, specify your verification preferences.
- To run the Action after the custom verification checks have been successfully run without manual intervention, select Automatically Continue If All Tests Succeed.
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 before the start of the Action by removing the job associated with the Action. After a job has started running, it cannot be canceled by using the Management Console. See Removing scheduled jobs for more information.
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.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.
Comments
Log in or register to comment.