Creating a Sybase patch package

This topic describes how to create a patch package for a Sybase Dataserver or Replication Server.

Before you begin

You should have already downloaded the patches that you want to apply. BMC Database Automation expects the patch format to be a gzip-compressed TAR archive (.tgz).

To create 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, click Create New Package.
  3. In the Package Information page, provision the following fields, and click Next.

    Patch Field

    Description

    Database Type

    Select the type of database for this patch package.

    Patch File

    Click Browse to locate the patch file that you want to include in this patch package.

    Note

    BMC Database Automation attempts to populate the fields in the remaining steps with information obtained from the patch file.

  4. In the Package Name page, provision the following fields, and click Next.

    Patch Field

    Description

    Package Name

    Enter a unique name for this patch package. This field cannot be edited after patch package creation.

    Description

    Enter a description of the patch package.

    Container

    Assign the patch package to a domain.

    Important: The domain selected as the Container determines which users can modify the patch package. Users with capabilities for the Container domain can perform all tasks against the patch package, whereas users with capabilities in the Available To domains can only use the patch package.

    Available To

    (Optional) Select additional domains to which this patch package is available for use.

    Selected Domains

    Lists the domains in which this patch package is available to authorized users.

  5. In the Package Attributes page, provision the following fields, and click Next.

    Patch Field

    Description

    EBF ID

    Enter the Sybase Emergency Bug Fix (EBF) number for this patch package.

    Set as Standard

    (Optional) Select to identify this patch package as standard, and have BMC Database Automation display targets that require remediation. The Patch Standard tab displays the patch packages marked as standard, enabling you to easily track, report, and fix databases that are out of compliance with your organizational standards. See also Managing standard patch packages.

    Command Line Options

    (Optional) Enter commands to be passed to the patch installer when this patch package is applied. Click Add Option to add CLI options. See Sybase patching CLI options template variables .

    Command Line

    (Optional) Click Populate Command Line to display the command line that is used to apply this patch package in the CLI.

  6. In the Package Targets page, provision the values by moving the wanted items to the Selected box for each field, and click Next.

    Patch Field

    Description

    Target Operating Systems

    Define the valid OS list that are considered legitimate candidates for this patch package.

    Target Architectures

    Define the list of valid processor types (architectures) that are considered legitimate candidates for this patch package. The target architecture must match the software it is patching.

    Target Applications

    Define the versions of applications that are considered legitimate candidates for this patch package.

    Note

    To add to the list of available choices for the Target Operating Systems and Target Applications fields, see Adding target OS and applications to a patch package.

  7. In the Package Scripts page, provision the following fields, and click Next.

    Section

    Field

    Description

    Install Scripts

    Pre-Install Shutdown

    (Optional) Specifies the location of the install script to be run before the application shutdown is initiated.

    Pre-Install

    (Optional) Specifies the location of the install script to be run before the patch package is installed.

    Post-Install

    (Optional) Specifies the location of the install script to be run after the patch package is installed.

    Post-Install Startup

    (Optional) Specifies the location of the install script to be run after the application startup is initiated.

  8. In the Package Additional Files page, specify any additional files as follows, and click Next.
    Additional files can be added to a patch package. They can be added one at a time or as a prepackaged .zipfile.

    Patch Field

    Description

    Additional Files

    Click Add File to add files, one at a time, for inclusion in this patch package.

    Additional Zip File

    Click Browse to locate and upload a .zip file containing files for inclusion in this patch package.

  9. 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.
  10. Click Create Package.
Was this page helpful? Yes No Submitting... Thank you

Comments