Supported upgrade paths

The following list shows the supported upgrade paths from earlier versions to the most recent 8.2 service pack level of BMC Server Automation (that is, 8.2 SP4 or version 8.2.04).

Note

 For information about upgrading to any previous 8.2 service pack, see the relevant service pack page (Service Pack 3, Service Pack 2, or Service Pack 1).

Current build information

Release

Build number

EPD version number

Release date

Service Pack 4

8.2.04.437

8.2.04

February 15, 2013

Service Pack 3

8.2.03.416

8.2.03

Nov 14, 2012

Service Pack 2

8.2.02.321

8.2.02

Aug 14, 2012

Service Pack 1 Patch 2

8.2.01.290

8.2.01.0002

Jun 27, 2012

Service Pack 1 Patch 1

8.2.01.281

8.2.01.0001

May 30, 2012

Service Pack 1

8.2.01.273

8.2.01

May 18, 2012

Base version 8.2

8.2.00.158

8.2.00

Feb 29, 2012

Pre-upgrade tasks

 Click here to see a list of pre-upgrade tasks.

Note

These tasks should be performed in order. Many steps are prerequisites for other steps that occur later in the process.

  • BMC strongly recommends that you back up the database before performing database migration and post-migration tasks.
  • If your BMC Server Automation environment includes BMC BladeLogic Decision Support for Server Automation, upgrade BMC BladeLogic Decision Support for Server Automation before upgrading BMC Server Automation.
  • For special considerations for your specific upgrade path, see Upgrade considerations.
  • Prepare the BMC Server Automation environment for upgrade. See Preparing for upgrade.
  • If you are using Microsoft Windows 2003 or 2008, you must upgrade in Install mode instead of Execute mode, see Using Install mode instead of Execute mode.

For additional information, see the topics listed in Upgrading.

Supported upgrade paths

Upgrading from this version

Perform these tasks

Upgrading from version 8.2 SP1, 8.2 SP2, or 8.2 SP3

Complete the following tasks:

  1. Upgrade the Application Server to version 8.2 SP4.

  2. Run the 8.2 SP4 SQL scripts provided in the 82-SP4-SQL_Update_Scripts.zip file (not the 8.2 SP4 external files). This file is available in the BMC Server Automation 8.2.04 section of EPD. Run these scripts as the BMC Server Automation database owner (as provided to blasadmin), according to the instructions provided for your database type in the readme file in the .zip. This step upgrades the database to a state that is compatible with the 8.2 SP4 Application Server.

Upgrading from versions 8.2, 8.1 — 8.1 SP5, or 8.0 GA — 8.0 SP11

Complete the following tasks:

  1. Upgrade the Application Server to version 8.2 SP4.

  2. Run the Data Migration Manager using the 8.2.04 external files to upgrade the database to 8.2 SP1. See Migrating your database by using BMC BladeLogic Data Migration Manager.

  3. Run the 8.2 SP4 SQL scripts provided in the 82-SP4-SQL_Update_Scripts.zip file (not the 8.2 SP4 external files). This file is available in the BMC Server Automation 8.2.04 section of EPD. Run these scripts as the BMC Server Automation database owner (as provided to blasadmin), according to the instructions provided for your database type in the readme file in the .zip. This step upgrades the database to a state that is compatible with the 8.2 SP4 Application Server.

Upgrading from version 7.6

Complete the following tasks:

  1. Upgrade the Application Server to version 8.2 SP4.

  2. Run the Data Migration Manager using the 8.2.04 external files to upgrade the database to 8.2 SP1. See Migrating your database by using BMC BladeLogic Data Migration Manager.

  3. Run the 8.2 SP4 SQL scripts provided in the 82-SP4-SQL_Update_Scripts.zip file (not the 8.2 SP4 external files). This file is available in the BMC Server Automation 8.2.04 section of EPD. Run these scripts as the BMC Server Automation database owner (as provided to blasadmin), according to the instructions provided for your database type in the readme file in the .zip. This step upgrades the database to a state that is compatible with the 8.2 SP4 Application Server.

  4. Migrate compliance rules and discovery signatures in the database.

Note

Upgrading to a new release can potentially create mismatches between the version of a custom configuration object, an agent, and any model objects that reference custom configuration objects. For more information, see Upgrading custom configuration objects.

Was this page helpful? Yes No Submitting... Thank you

Comments

  1. Martin Doeller

    Warning ,,, When you use "alter current schema "

    in Oracle 11 you need change script updDbVersion.sql  line :

    'SELECT count(*) INTO v_stored_proc_exists FROM USER_PROCEDURES WHERE object_name = 'CR_CLEAN_PUSH_GROUP_RESULT';'

    for these  ''FROM ALL_PROCEDURES '' instead USER_PROCEDURES

     

    edgard

     

    Dec 10, 2013 04:58
    1. Moiz Nalwalla

      Thanks for reporting this issue Martin. This issue was present in the 8.2.04 release and has been fixed in the later releases.

      May 09, 2014 07:33