Installing an SQL Server patch package

Perform the following steps to install an SQL Server patch package:

Note

A node might host:

  • Both primary and secondary instances of multiple clustered instances
  • Both primary and secondary replicas of multiple availability groups
  • A combination of the preceding types

BDA does not reboot such nodes during patching. The following reason appears in the Middle Tier:

<yyyy/mm/dd> HH:MM:SS [WARN] GA.MiddleTier.Process.RunMssqlPatch (pid: <processID> - line: <lineNumber> - file: <fileName>) These nodes will not be considered for reboot before or after patching or rollback activity: <nodeName1> <nodeName2> <nodeName3> ...
The reason being one of the below:
1. These nodes host both primary and secondary instance of multiple clustered instances
2. These nodes host both primary and secondary replicas of multiple availability groups
3. Combination of 1 and 2


  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 drop down box of that row.

  3. In the MS SQL Server Patch Install Candidates page, populate the following fields, and click Next.

    Note

    BDA supports rolling updates for SQL Server Instances hosting SQL Server Availability Groups, which is the process of patching SQL Server instances in series and failing over the primary replica in the middle and at the end of the series. Selecting all instances hosting an Availability Group automatically triggers this function. If you select some, but not all, of the instances hosting an Availability Group, BDA will prompt you to remind you of this function. In BDA 8.9, this function is supported for instances hosting a single Availability Group only. For more information, see http://support.microsoft.com/kb/958734 http://msdn.microsoft.com/en-us/library/ms191295.aspx.

    When patching SQL Server Instances which participate in a SQL Server Availability Group, if you do not select all the instances participating in the Availability Group, BDA will prompt you to indicate that there are more instances that should be patched. If you continue after receiving this prompt, BDA will patch the selected instances without performing any of the steps necessary to maintain high availability for the Availability Group.

    When patching a set of SQL Server Instances that host replicas for an AlwaysOn Availability Group, BDA polls the Availability Group to see if all its databases are synchronized and, if not, continues to poll until 30 minutes has elapsed. If the databases are synchronized, it exits successfully. If the maximum time has elapsed and the databases are not synchronized, BDA displays a failure message, but the operation  will still exit successfully .

    The maximum polling time can be changed in the new  GAC_Max_Wait_For_AvGrp_Synchronization custom variable  using a time interval in seconds.

    You can view a list of the targets that were excluded from the installation candidates list, and the reason for the exclusion, by clicking Excluded Candidates.

  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 (BDA version 8.9.03) any 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.

  6. In the Scheduling page, select when to run this job in the Job Execution field, and click Next.
    (BDA version 8.9.03) If 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.

    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. Specify your verification preferences.
    • To continue with patching the SQL Server Instances after the pre-verification tests have been successfully run without manual intervention, select Automatically Continue If All Tests Succeed.

    • To patch the instances without having first run the pre-verification steps, 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 the actual provisioning activity.

  10. Click Execute Job or Schedule Job (depending on your selection in the Scheduling page).

    Note

    Databases that are in an Up state before the patch package installation process began are restarted after the installation is completed. Clustered SQL Server instances are required to be started before service packs and hot fixes are applied. When the patch package installation process is complete, the instance is left running.

Related topic

Patching-a-database

 

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