Monitoring jobs and viewing job history

In BMC Database Automation (BDA) you can monitor the status of automated database activities in addition to viewing the history of completed jobs.

Note

The activity timeout period within a BDA job is 12 hours.

When a provisioning task is initiated (such as creating a database or cluster, or adding a database instance), you can monitor the progress from the Jobs menu. The Jobs page enables you to view details of the completed jobs.  

For a comprehensive list of provisioning activities organized by database type, refer to Provisioning new databases.

To monitor a job or view the details of a completed job

  1. In the Context Frame, select Jobs.
    The following information is provided in the Jobs overview page.

    Jobs page item

    Description

    Filter

    Area where you can narrow down the results by date, status, or search for a specific job by Job ID. The valid values for status are as follows:

    • In Progress: Indicates that a job is still running.
    • Success: Indicates that a job is successfully completed.
    • Failed: Indicates that a job has failed.
    • Scheduled: Indicates that a job is scheduled for execution at a later date and time.
    • Canceled: Indicates that a job was canceled when it was running.
    • Expired: Indicates that a job has expired.
    • Pending Approval: indicates that a job is yet to be approved.
    • Approval Rejected: Indicates that a job was rejected.
    • NEW IN 8.9.02Verified: Indicates that a job completed the pre-verification phase and then the job stopped running.
      This option is available only if you have set the can_show_verified_jobs property to true in the /app/clarity/dmanager/etc/d2500_config file on the BDA Manager. By default, the value of this property is false.
    Job IDUnique identifier for the job

    Title

    Descriptive name of the job

    Start Time

    Month-day-year and hour-minute-second that the job was started

    Completion Time

    Month-day-year and hour-minute-second that the job was finished. If the job is not yet complete, In Progress is displayed.

    Elapsed Time

    Amount of time that has passed for the specified job

    Status

    Indication of whether the process is in progress, scheduled, expired, canceled, successful, or failed

  2. Under Title, click a specific job for more detailed information.

    The sections in the Job Summary page contain the following details about the job:
    • Information: Lists general information about the job, including the domain in which the job originated and the logon name and IP address of the user who initiated the job. Also lists the time the job began, ended, and length of time to complete the job as well as whether it was successful.
      Starting with version 8.9.01, the Results section of certain BDA job types (for example, Oracle and SQL Server patching) displays:
      • More verbose feedback text  
      • A link to view and save installer output for analysis and troubleshooting
      • External links to additional resources 
    • Pre-Verification: Lists the overall success rate of any pre-verification tests that were run as part of this job. Click View Details for additional information about the tests that were run. Also included are links to the log file and package for this job.
    • Provisioning: For provisioning jobs, lists the provisioning tasks that were performed for this job. Click View Details for additional information.
    • Provisioning Scripts: For provisioning jobs, lists any provisioning scripts that were run before or after the provisioning task. To rerun any of the scripts, click Rerun Scripts. You can then select the scripts that you want to rerun and click Rerun Scripts to execute these scripts.
    • Job Output: Displays the Action job output files (stdout and stderr) resulting from executed actions. Click View to view the contents of the output file, or click Download to download the output file to your system. When viewing the output file, you can also copy the contents to paste elsewhere for analysis or troubleshooting.
    • Rerun Job: (Applies to provisioning, patching, upgrade and Action jobs.) Launches the initial verification phase of the selected job again, by using the same input as the first job run. This job is executed based on the value of the Automatically continue if all tests succeed option in the original job.

If either of the following conditions is met, you can re-run a job:

    • You have RERUN_ANY_JOB capability on ALL entities in the job.
    • You are the same user who initiated the original job, and less than 24 hours have passed since the job create timestamp.
Was this page helpful? Yes No Submitting... Thank you

Comments