Installing a Sybase patch package

Before you begin

  • To install a Sybase patch package, you must have Domain Administrator privileges.
  • Ensure that the GNU Tar utility is installed in one of the following locations on the Agent hosts:

    Note

    The GNU Tar utility is available on the Solaris Freeware CD. 

  • Solaris
    • /usr/sfw/bin/gtar
    • /opt/sfw/bin/gtar/
    • usr/local/bin/tar
    • /bin/tar
  • Linux
    • /bin/tar

To install a Sybase patch package

  1. From the Management Console main page, select Patching > Patch Repository in the Context Frame.
  2. In the Patch Repository page, select a patch package and select Install from the list box for that row.
  3. In the Sybase Patch Install Candidates page, populate the following fields, and click Next.

    Patch Candidate Field

    Description

    Install Patch In

    Specify how to install this patch:

    Parallel: Apply patch package to all specified databases and hosts simultaneously.
    Serial: Apply patch package to all specified databases and hosts one at a time.

    Use the Same Password For All Dataservers

    (Optional) Select when you want to use the same SA password for all Sybase Dataservers.

    SA Password

    Enter the SA password for your Sybase Dataservers. This field is active when the Use the Same Password For All Dataservers option in selected.

    NEW IN 8.9.02Remove Pre-Staged PatchSelect this option if you want to remove the pre-staged patch media after installation of the patch irrespective of whether the installation was successful or not.

    Template

    Displays the default BMC Database Automation template selected from the Default Template field in the Edit Existing Package wizard. Optionally, you can select a template for this operation. See Managing templates for Sybase. If you select a template, you can click Skip Ahead to advance directly to the next step that requires input. An information message appears in the step, in green type, listing the fields that require entries before advancing to the next step.

    Homes

    Select the databases, hosts and instances that you want to patch with this patch package. The candidates for this patch are determined by the patch version number you entered when you created the patch package.

    Note: The candidates list does not get refreshed automatically. Click the Reload Candidates button to refresh the list.

  4. In the Custom Fields page, populate the custom fields you have defined in the template, and click Next.

    Note

    This page appears only when in the BMC Database Automation XML template, either custom fields are defined used for this activity 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, 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.

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

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

  8. In the Summary page, review the 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.
  9. Click Execute Job or Schedule Job (depending on your selection in the Scheduling page).
Was this page helpful? Yes No Submitting... Thank you

Comments