Skip Headers
Oracle® Database Upgrade Guide
11g Release 1 (11.1)

Part Number B28300-01
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
View PDF

1 Introduction to the Database Upgrade Process

This chapter provides an overview of the database upgrade process, as well as information about running multiple releases of Oracle Database.

This chapter covers the following topics:

Overview of the Database Upgrade Process

This section includes an overview of the major steps required to upgrade an existing Oracle database to Oracle Database 11g Release 1 (11.1). These procedures transform an existing Oracle Database system (including associated applications) into an Oracle Database 11g Release 1 (11.1) system. Oracle Database 11g Release 1 (11.1) is compatible with all earlier Oracle Database releases. Therefore, databases upgraded using the procedures described in this guide can work in the same manner as in earlier releases and, optionally, can leverage new Oracle Database 11g Release 1 (11.1) features and functions.

Oracle Database 11g Release 1 (11.1) supports the following tools and methods for upgrading a database to the new release:

These tools and methods are described in more detail in "Choose an Upgrade Method".

The major steps in the upgrade process are illustrated in Figure 1-1.

Note:

The upgrade steps apply to all operating systems, with the possible exception of a few operating system-specific details identified in your operating system-specific Oracle documentation.

The following list outlines the major steps performed during the upgrade process. Detailed instructions are provided in the appropriate chapters later in this guide.

Step 1: Prepare to Upgrade

Step 2: Test the Upgrade Process

Step 3: Test the Upgraded Test Database

Chapter 2, "Preparing to Upgrade" provides detailed information about Steps 1 through 3.

Step 4: Prepare and Preserve the Production Database

Step 5: Upgrade the Production Database

Chapter 3 describes Steps 4 and 5 when using DBUA or when performing a manual upgrade. Chapter 4 describes the backup procedure after the upgrade and other post-upgrade tasks.

Step 6: Tune and Adjust the New Production Database

During the upgrade, consider running multiple releases of the database software so you can use the existing release as your production environment while you test the new release. See "Running Multiple Oracle Releases".

Oracle Release Numbers

This guide describes moving between different releases of the Oracle Database server. Figure 1-2 describes what each part of a release number represents.

Figure 1-2 Example of an Oracle Release Number

Description of Figure 1-2 follows
Description of "Figure 1-2 Example of an Oracle Release Number"

Note:

Starting with Oracle Database9i Release 2 (9.2), maintenance releases of Oracle Database are denoted by a change to the second digit of a release number. In previous releases, the third digit indicated a particular maintenance release.

See Also:

Oracle Database Administrator's Guide for more information about Oracle release numbers

When a statement is made in this guide about a major database release number, the statement applies to all releases within that major database release. References to Oracle Database include release 1 (11.1); references to Oracle Database 10g include Oracle Database 10g Release 1 (10.1) and Oracle Database 10g Release 2 (10.2); references to Oracle9i include release 1 (9.0.1) and release 2 (9.2).

Similarly, when a statement is made in this guide about a maintenance release, the statement applies to all component-specific (also referred to as patchset releases) and platform-specific releases within that maintenance release. So, a statement about Oracle Database9i Release 2 (9.2) applies to release 9.2.0.1, release 9.2.0.2, and all other platform-specific releases within release 2 (9.2).

Running Multiple Oracle Releases

You can run different releases of Oracle Database on the same computer at the same time. However, you must observe the following conditions when using multiple releases:

  • An Oracle Database release must be installed in a new Oracle home that is separate from previous releases of Oracle.

    There cannot be more than one release for each Oracle home. Oracle recommends that you adopt an Optimal Flexible Architecture (OFA) when creating multiple Oracle homes. See "Using Optimal Flexible Architecture (OFA)" for more information.

    Caution:

    It is not possible to install Oracle Database 11g Release 1 (11.1) products into an existing Oracle home of a prior major release. This feature was available only for certain previous releases and has not been continued.
  • Each database server can access only a database that is consistent with its release number.

    For example, if you have Oracle9i and Oracle Database 11g Release 1 (11.1) installed on the same computer, then the Oracle9i database server can access Oracle9i databases but not Oracle Database 11g Release 1 (11.1) databases, and the Oracle Database 11g Release 1 (11.1) database server can access Oracle Database 11g Release 1 (11.1) databases but not Oracle9i databases.

See Also:

Your operating system-specific Oracle documentation for more information about running multiple releases of Oracle on your operating system. Restrictions might apply on some operating systems.

The following sections provide general information about running multiple releases of Oracle Database.

Install Databases in Multiple Oracle Homes on the Same Computer

You can install Oracle8i, Oracle9i, and Oracle Database 10g databases in multiple (separate) Oracle homes on the same computer and have Oracle8i, Oracle9i, and Oracle Database 10g clients connecting to any or all of the databases.

Install Databases in Multiple Oracle Homes on Separate Computers

You can install Oracle8i, Oracle9i, Oracle Database 10g, and Oracle Database 11g Release 1 (11.1) databases in multiple (separate) Oracle homes on separate computers and have Oracle8i, Oracle9i, Oracle Database 10g, and Oracle Database 11g Release 1 (11.1) clients connecting to any or all of the databases.

Upgrade a Database to the Current Release

You can upgrade an Oracle8i, Oracle9i, or Oracle Database 10g database to Oracle Database 11g Release 1 (11.1) and have Oracle8i, Oracle9i, Oracle Database 10g, and Oracle Database 11g Release 1 (11.1) clients connecting to the upgraded database.

Upgrade Clients to the Current Release

You can upgrade any or all of your Oracle8i, Oracle9i, or Oracle Database 10g clients to Oracle Database 11g Release 1 (11.1). The Oracle Database 11g Release 1 (11.1) client can be used to access your Oracle8i, Oracle9i, Oracle Database 10g, and Oracle Database 11g Release 1 (11.1) databases.

Using Optimal Flexible Architecture (OFA)

Oracle recommends the Optimal Flexible Architecture (OFA) standard for your Oracle Database installations. The OFA standard is a set of configuration guidelines for efficient and reliable Oracle databases that require little maintenance.

OFA provides the following benefits:

If you are not currently using the OFA standard, then switching to the OFA standard involves modifying your directory structure and relocating your database files.

See Also:

Converting Databases to 64-bit Oracle Database Software

If you are installing 64-bit Oracle Database 11g Release 1 (11.1) software but were previously using a 32-bit Oracle Database installation, then the database is automatically converted to 64-bit during a patch release or major release upgrade to Oracle Database 11g Release 1 (11.1).

You must increase initialization parameters affecting the system global area, such as sga_target and shared_pool_size, to support 64-bit operation.

See Also:

Your platform-specific installation guide for additional information

Rolling Upgrades

A rolling upgrade upgrades different databases or different instances of the same database (in an Oracle Real Application Clusters environment) one at a time, without stopping the database. Depending on the method you choose, you can perform a rolling upgrade of the Oracle Database software version, apply patchsets, or apply individual patches (sometimes referred to as one-off patches), incurring little or no database downtime.

Oracle Database 11g Release 1 (11.1) provides the following methods for performing rolling upgrades:

Moving From the Standard Edition to the Enterprise Edition

If you have a Standard Edition database at a release prior to Oracle Database 11g Release 1 (11.1), then you can change it to an Enterprise Edition database by installing the Enterprise Edition and following the normal upgrade procedures, as described in this manual.

To change your existing Oracle Database 11g Standard Edition database to an Enterprise Edition database, follow these steps:

  1. Ensure that the release number of your Standard Edition server software is the same release as the Enterprise Edition server software.

    For example, if your Standard Edition server software is release 11.1.0.6, then you should upgrade to release 11.1.0.6 of the Enterprise Edition.

  2. Shut down your database.

  3. If your operating system is Windows, then stop all Oracle services, including the OracleServiceSID Oracle service, where SID is the instance name.

  4. Deinstall the Standard Edition server software.

  5. Install the Enterprise Edition server software using the Oracle Universal Installer.

    Select the same Oracle home that was used for the de-installed Standard Edition. During the installation, be sure to select the Enterprise Edition. When prompted, choose Software Only from the Database Configuration screen.

  6. Start up your database.

Your database is now upgraded to the Enterprise Edition.

Upgrading from Oracle Database Express Edition to Oracle Database

In order to upgrade Oracle Database 10g Express Edition (Oracle Database XE) to Oracle Database 11g, you need to install Oracle Database 11g on the same system as Oracle Database XE and use Database Upgrade Assistant to perform the upgrade.