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

  1. From the Management Console main page, select Actions > Actions Repository.
  2. In the Actions Repository page, locate the Action you want to run and select Run from the list box in that row.
  3. In the Action page, populate the following fields, and click Next.

  4. In the Custom Fields page, select or enter the values for any custom fields that appear, and click Next.
  5. In the Candidates page, select the candidates on which this Action is run, and click Next.
    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.
    Run Action Candidates List PDB.gif

    Note

    You can select multiple PDB candidates to apply changes across multiple PDBs while running a just single Action.

  6. In the Job Options page, specify any of the following Job options, and click Next.

  7. 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.

  8. If the Change Control page displays, populate the following fields, and click Next.

    Note

    The Change Control page appears only when change control is configured for your environment. See Configuring-change-control.

  9. In the Summary page, review the provisioning information.
    To make changes, do the following:
    1. Click Go to to return to the provisioning step that you want to edit.
    2. Make your changes.
    3. Click Save and Review to return to the Summary page.
  10. 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.

  11. 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.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*