Performing minor version upgrades for Oracle on Linux and UNIX


Minor release versions of 10gr2 Oracle single-instance and Real Applications Cluster (RAC) databases can be upgraded by using BMC Database Automation. For example, you can upgrade from 10.2.0.1 to 10.2.0.4.

Before you begin

An Oracle database that meets all of the Oracle prerequisites must be available. The nodes must meet all of the Oracle prerequisites, including:

  • Minor version upgrades in RAC environments must be completed by using separate BMC Database Automation jobs. For example, if Cluster Ready Services (CRS), Automatic Storage Management (ASM) and DBMS are each in a separate home, the upgrade would be completed in three jobs starting with upgrading the CRS home. After CRS is upgraded, the other two upgrade buttons appear and are available.
  • Rolling upgrades are only supported for Oracle CRS 10.2.0.X minor version upgrades.
Warning

Note

If ASM and the database are using the same Oracle Home, the upgrade of the database is automatically accomplished by using the Upgrade ASM utility, because the upgrade candidate selection criteria is managed by the Oracle Home.

To upgrade an Oracle 10gr2 database

Warning

Note

Instructions are the same for single-instance and RAC databases unless noted otherwise.

  1. In the Grid view, navigate to the database to be upgraded.
  2. Select Management > Upgrade Oracle Database.

    Warning

    Note

    The Upgrade Version field lists the Oracle database versions available based on the Current Version.

  3. (Optional) In the General page, select a template from the Templatelist box.

    Warning

    Note

    For more information about templates, see Managing-templates-for-Oracle-on-Linux-and-UNIX.

  4. If you select a template, click Skip Ahead to advance directly to the next step that requires input. An informational message appears on these steps, in green type, listing the fields that require entries before advancing to the next step.
     If you do not select a template, go to the next step.
  5. In the Additional Databases page, view the information on other databases that are sharing the Oracle Home that will be upgraded, and click Next.
  6. In the Configuration page, populate the following fields, and click Next.

  7. In the Custom Scripts Configuration page, select any pre-provisioning or post-provisioning scripts that you want to run as follows, and click Next.

  8. In the Job Options page, specify any of the following Job options, and click Next.

  9. If the Change Control page displays, populate the following fields, and click Next.

    Warning

    Note

    The Change Control page appears only when change control is configured for your environment. See Configuring-change-control.

  10. In the Summary page, review the provisioning 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.
  11. Specify your verification preferences.
     For additional information, see Understanding pre-verification tests.
    • To continue with database creation after the pre-verification tests have been successfully run without manual intervention, select Automatically Continue If All Tests Succeed.
    • To create the database without having first run the pre-verification steps, select Skip Pre-Verification Tests.

      Warning

      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.

  12. Click Upgrade Oracle Database.
  13. If you disabled the Automatically Continue If All Tests Succeed and Skip Pre-Verification Tests options, you are prompted to click Continue after the pre-verification steps are done.

    Warning

    Note

    If you close your browser, the operation continues. You can return to this page by using the Jobs page.

 

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

BMC Database Automation 8.3