Repeating the Upgrade Process for Applications

The upgrade logic in this release is based on deploying a new software release and moving applications, data, and provisioning information from the earlier deployment to the new deployment. This approach allows the upgrade process to be repeatable. You start with a new database, delete existing configurations, and repeat the upgrade process as documented.

  To repeat the upgrade process for applications:

  1. Back up the existing 11.1.2.1 deployment.

  2. For every machine in the deployment:

    1. Rename the .oracle.instances file in the user home ($HOME for UNIX, Documents and Settings/<userid> for Windows), removing it from use.

    2. Rename the existing user_projects folder to another name, removing it from use.

  3. Reconfigure the deployment by following the regular 11.1.2.1 upgrade procedure as documented in the Upgrading Checklist.

    • Use a new database for the Shared Services Registry

    • Reuse the replicated product databases (from the previous release)

      Note:

      You can repeat this step as needed to get the latest data from the previous release.