14 Upgrading Databases

Prerequisites

Before running the Deployment Procedure, meet the following prerequisites.

• To upgrade to 11.2.0.x, the existing database version must be 10.2.0.4 or higher, 11.1.0.6 or higher, or 11.2.0.1. Make sure the target version (that is, the version you are upgrading to) is always higher than the source version.

• Database user must have SYSDBA privileges or the OS user must be part of the DBA group.

• Database to be upgraded must be up and running.

• Ensure that you have created designer and operator roles with the requisite privileges. The designer must have EM_PROVISIONING_DESIGNER role and the oeprator must have EM_PROVISIONING_OPERATOR role.

Prerequisites for Designers

• Edit access to Software Library to manage Software Library entities such as gold images

• Add/Edit Target privileges

• Create Named Credentials privilege

Prerequisites for Operators

• View access to Software Library to view Software Library entities such as gold images.

• Add/View Target privileges.

• Privileges to the named credentials granted by designer.

Upgrade Procedure

Follow these steps:

1. Log in as a designer, and from the Enterprise menu, select Provisioning and Patching, then select Database Provisioning.

2. In the Database Provisioning console, select the Upgrade Oracle Database Deployment Procedure and click Launch. The Oracle Database Upgrade wizard is launched.

3. In the Select Databases page, select the databases to be upgraded. You can select:

   • Multiple databases in the same Oracle Home

   • Multiple databases across Oracle Homes on the same host

   • Multiple databases on different hosts

   In the Select Databases section, select the Platform and Version of the database to be upgraded. You can search for database, host, target group, or Oracle Home and then select the database.

   Click Schedule Backup to schedule a backup of the database. If you do not back up your databases before upgrade, you may not be able to restore the databases if upgrade fails.

   Note:

   If the database you want to upgrade does not appear in the table, verify that the database is available and there are no metrics collection errors for the target.

   In the Select Upgrade Path section, select the version you want to Move to. The upgrade version selected must be higher than the present version of the database. You can move to the latest database release available.

   Click on the Lock icon to lock the fields that you do not want to be editable. These fields will not be available for editing in the operator role. For example, locking Platform and Version fields will ensure that the operator selects databases from the specific list of platform and version for the upgrade.

   Click Next.

4. In the Specify Path details page, select Upgrade Option as one of the following:

   • Select Upgrade Database Software and Instance to install a new Oracle Home and upgrade the database instance. Specify the following details:

     1. In the Oracle Database Software Details section, select the Oracle Database Software from the Software Library for installing a new Oracle Home. Ensure that the zipped up Oracle Home contains all critical patches for the new Oracle Home.

        Note:

        To ensure that the gold image you create includes all the recommended patches, follow these steps:

        1. Click the 'Database Upgrade Planner' link and Log in to My Oracle Support using Cloud Control in the online mode.

        2. Select the following types of patches to be applied to the gold image:

           • Recommended patches on the release you want to upgrade to

           • Patches on top of the release that maintain the fixes in the base release

           • Patches resolving merge conflicts if any present between the patches chosen

        3. Apply the patches to an Oracle Home of the release to upgrade to using Patch Plans or manually. For more information about patch plans, see Chapter 24.

        4. Create a gold image from the Oracle Home and use it for the upgrade. For information about creating a gold image, see Creating Database Provisioning Entities.

     2. In the Specify New Software Location section, specify the Oracle Home and Oracle Base to upgrade the database. Select Same for all hosts to upgrade all databases from a host to the same Oracle Home by specifying the same Oracle home location.

     3. In the Advanced section, specify the Working Directory for the upgrade. Ensure that you have read-write permissions to this directory.

   • Select Upgrade Database Instance Only to upgrade the database instances in an existing Oracle Home. For example, if you have already upgraded some of the databases in the Oracle Home earlier and want to now upgrade other databases in the same Oracle Home. Specify the following:

     1. In the Select an existing location for Database Instance section, specify the Oracle Home on the host where you want to upgrade the database.

   Click on the Lock icon to lock the fields that you do not want to be editable. These fields will not be available for editing in the operator role.

   Click Next.

5. In the Specify Configuration Details page, you can configure the listener to be registered with the database after upgrade as follows:

   • Use an existing listener. The databases after upgrade, will be registered automatically with the Single Instance High Availability listener, if configured. If no Single Instance High Availability listener is available, and there are other listeners running in the Oracle Home, the upgraded databases will be registered with these listeners.

   • Add a new listener.

   If you are upgrading multiple databases in the same Oracle Home, you can use the same listener for these databases.

   Note:

   Migration of existing listeners is not supported.

   In the Listener Configuration section, click the plus sign (+) to select listener for the database. In the Select Listener for Database popup:

   1. Select the listener if it already exists. Otherwise, click Add to add a new listener to register with the database. Specify the Name and Port.

   2. Click OK.

   In the Backup and Restore section, you can select:

   • Backup and Restore Settings Only to restore configuration changes made during database upgrade and not actual data, in case upgrade fails.

   • Full Backup to backup the database and restore configuration and oratab settings if upgrade fails. The backup location is, by default, $ORACLE_BASE/admin/$GDB/backup where '$GDB' is the global database name.

   • Ignore if you have your own backup options and do not want Cloud Control to perform a backup of your database.

   In the Upgrade Options section:

   • Select Recompile invalid objects at the end of upgrade to make valid database objects for the new database version.

   • If archive logging has been turned on for the database, then you have the option to Turn off Archiving and flashback logging, for the duration of upgrade.

   • If you are upgrading to database version 11.2.0.2 or higher, you will be able to set the time zone upgrade option. You can select Upgrade Time Zone Version and Timestamp with Time Zone data.

   In the Advanced section, select custom scripts to run on the database before or after upgrade. Select Execute custom SQL script on the source database before upgrading the database to run custom script on the database before upgrade and then select the script from the Software Library. Select Execute custom SQL script on the upgraded database to run custom script on the upgraded database and then select the script from the Software Library.

   Click on the Lock icon to lock the fields that you do not want to be editable. These fields will not be available for editing in the operator role.

   Click Next.

6. The Custom Properties page will be displayed only for user customized deployment procedures that require custom parameters. Specify custom properties for the upgrade, if any. Click Next.

7. In the Select Credentials page, specify the Operating System, Privileged Operating System Credentials (run as root), and Database credentials. If you choose to specify Preferred Credentials, select either Normal Host or Privileged Host credentials. For Named Credentials, you can specify the same or different credentials for Oracle homes.

   If you have not set Named Credentials, click the plus sign (+) in the Credentials section. In the Add New Database Credentials popup, specify the User name, Password, Role, and specify the Save Details. Select Run As and specify root. Click OK.

   Click on the Lock icon to lock the fields that you do not want to be editable. These fields will not be available for editing in the operator role.

   Click Next.

8. In the Schedule page, specify a Deployment Instance and schedule for the upgrade job. If you want to run the procedure immediately, then retain the default selection, that is, Immediately. If you want to run the job later, then select Later and provide time zone, start date, and start time details. Specify a Grace Period, a duration after the start period for Cloud Control to attempt to start the upgrade if it cannot start at the specified time.

   In the Set Breakpoint section, configure to continue or stop the deployment procedure execution after each step is run. For example, if you set the breakpoint after analyzing the prerequisites, the upgrade will pause after the prerequisites are run. You can verify that the prerequisites have run successfully, fix any errors, and then run the upgrade.

   In the Set Notification Details section, select the events for which you want to be notified.

   Click Next.

9. In the Review page, verify that the details you have selected are correctly displayed. If you want to modify the details, then click Back repeatedly to reach the page where you want to make the changes.

   To save the deployment procedure for future use, click Save.

   To submit the deployment procedure, click Submit. When the deployment procedure is submitted for execution, the database upgrade instance tracking page is displayed. You can also navigate to this page by clicking the procedure instance in the Job Activity page.

10. You can run the saved deployment procedure as an Cloud Control user with operator role by selecting the configured and saved Database Upgrade Deployment Procedure instance in the Database Provisioning console, and clicking Launch.

11. Submit the configured Database Upgrade procedure after providing values for the editable fields. After you have submitted the procedure, the summary for the running procedure is displayed.

12. In the Upgrade Oracle Database procedure execution page, in the Current Run tab, view the upgrade job steps and status.

13. If you have specified a breakpoint, the procedure execution will pause at the step specified. From the Actions menu, select Resume. The possible actions are Stop, Resume, Suspend, Cleanup, Resubmit, and Skip Step. Click Resubmit to resubmit the current instance for execution.

14. If you want to execute certain steps, from the Run to step list, select the step you want to run.

15. If a step has status Failed, click View Log. The Job Run for the step is listed. Click Show in the Details column to view the entire log. Fix the error and click Retry.

16. After the procedure execution is completed, click on the Targets menu and select All Targets to navigate to the All Targets page and verify that the newly upgraded databases appear as Cloud Control targets.

Prerequisites

• The database version must be 10.2.0.4 or above for upgrade to 11.2.0.1 or higher.

• For Oracle Real Application Clusters databases, if you select an Oracle RAC database instance and start the database upgrade process, it will upgrade the entire cluster database.

• If OS authentication is not turned on, SYSDBA credentials are required for the upgrade.

• Database to be upgraded must be up and running.

• Ensure that you have DBA privileges to run this procedure.

Upgrade Procedure

Follow these steps:

1. From the Enterprise menu, select Targets, then select Database. In the Databases page, select the source database to be upgraded.

2. In the Database Instance home page, from the Oracle Database menu, select Provisioning, then select Upgrade Database.

   Note:

   For single instance database instances, you will see another menu option to upgrade the Oracle home and the instance. If you select that option, you will be taken to the wizard described in Upgrading Multiple Oracle Database Instances at a Time (Mass Upgrade), however, only the database instance, from where you navigated to the wizard, will be pre-selected for upgraded.

3. Specify the Database user and password credentials and click Continue. The Database Upgrade wizard is launched.

4. In the Oracle Home page, select the New Oracle Home where you want the new Oracle Home for the upgrade to be installed, based on the version of the database to be upgraded. If the Oracle Home is not a discovered target in Cloud Control, either discover the Oracle Home using the Cloud Control Discovery feature and then initiate the upgrade process or type the path of the Oracle Home manually. For Oracle Real Application Clusters databases, specify the Oracle RAC home.

   For information about discovering targets in Cloud Control, see Chapter 3.

   When specifying the new Oracle Home, you must have DBA permissions on both the source and destination Oracle Homes and these Oracle Homes must reside on the same host.

   In the Oracle Home Credentials section, specify the host credentials. Host credentials must have DBA privileges and can be Preferred Credentials, or Named Credentials, or, you can select Enter Credentials and specify the user name and password and save it. Click More Details to view details about the host credentials you have selected. The specified Oracle Home credentials should have privileges on both the source database Oracle Home and the new Oracle Home. Click Test to verify that the credentials have the required privileges. If you are using Named Credentials, ensure that these are user and password credentials, else they will not be supported in Cloud Control.

   Click Next. The errors and warnings from the prerequisite checks are displayed. Fix all errors and warnings and revalidate. Click OK to proceed to next step.

5. In the Options page, the Diagnostics destination field is displayed only for database upgrade from version 10.2.x to 11.1.0.6. The diagnostic destination is defaulted to Oracle Base and all diagnostic and trace files are stored at this location.

   If you are upgrading from version 11.1.0.7 or higher to 11.2.x, the diagnostic destination field does not appear.

   If archive logging has been turned on for the database, then you have the option to disable or Keep archive logging enabled during upgrade.

   If flash recovery area has been configured for the database, then the Flash Recovery section will be displayed. Specify Flash Recovery Area Location and provide an adequate space for Size.

   If you are upgrading to database version 11.2.0.2 or higher, you will be able to set the time zone upgrade option. You can select to Upgrade Time Zone Version and Timestamp with Time Zone data.

   Note:

   If the database has ASM configured with it, the Backup section will not be displayed.

   In the Backup section, you can select:

   • Restore Settings Only to restore configuration changes made during database upgrade and not actual data, in case upgrade fails.

   • Perform full backup before upgrade and restore upon failure to restore oratab configuration. Specify a file system location for Backup Location. The credentials that you have specified earlier must have read-write permissions to this location.

   • None if you do not want to specify a database backup.

   In the Advanced section, specify the custom SQL scripts you want to run before and after the database upgrade. Copy these scripts to the host file system and select them. If your custom scripts are stored as a component in the Software Library, select Select these scripts from the Software Library and then browse the Software Library for these scripts. During execution, the main file specified in the Software Library component will be run. So, if you want to run a set of scripts, organize them in the main script file and specify the main script in the Software Library component.

   Select Recompile invalid objects at the end of upgrade to make valid database objects for the new database version. Setting a higher Degree of Parallelism will ensure faster recompilation of objects. The default setting is the number of CPU count of the host.

   Click Next.

6. The Listeners page is displayed only for single instance database upgrade. In the Listeners page, listeners that are registered with Oracle Restart and those that are running in the new Oracle Home are displayed. You can create a new listener or migrate your existing listener manually and then upgrade the database. If you create a new listener, the listener will then be an Cloud Control target and will be monitored. If you migrate your existing listener, the upgrade job will register the database with the listener.

   If you have listeners running in the source Oracle Home and need to maintain the same listener port after upgrade, migrate your listener manually to the new Oracle Home first.

   For Oracle Real Application Clusters database, the upgraded database will be registered with the Clusterware listener automatically and the Listeners page will not appear.

   To add a new listener, specify the Name and Port Number.

   Click Next.

7. In the Schedule page, edit or retain the Job Name and Description for the database upgrade. If you want to run the job immediately, then retain the default selection, that is, Immediately. If you want to run the job later, then select Later and provide time zone, start date, and start time details. Specify a Grace Period, a duration after the start period for Cloud Control to attempt to start the upgrade job if it cannot start at the specified time.

   Select Blackout the database target in Enterprise Manager during upgrade if you do not want the database to be monitored and alerts to be raised by Cloud Control during the upgrade.

   Click Next.

8. In the Review page, ensure that you review all warnings generated in the Validation Summary. Click the Validation Summary icon to view validation results and severity and action taken for any warnings. Verify that the details you have provided for the upgrade job appear correctly and then click Submit Job to run the job according to the schedule set. If you want to modify the details, then click Back repeatedly to reach the page where you want to make the changes. Click Save to save the deployment procedure for future deployment.

9. After you have submitted the job, the Database Upgrade Job page with the summary for the running job will be displayed. In the Jobs page, view the job summary and the list of steps and view their status.

10. After the upgrade job is completed successfully, click on the Targets menu and select All Targets to navigate to the All Targets page and verify that the newly upgraded database is displayed as an Cloud Control target with the correct database version.