This chapter describes how to keep your Oracle Database software up-to-date with patch and software releases. This chapter contains the following sections:
Software management involves keeping your Oracle Database software up-to-date with the latest product fixes. When a product defect, or a bug, is discovered, a patch is created to fix the problem. A patch corrects a single defect in the installed software. Individual patches, also referred to as interim patches, are made available to customers who for business reasons cannot wait until the next patch set to receive the product fix.
Oracle periodically issues maintenance releases for its software, in the form of patch sets. A patch set is a collection of product fixes that have been released up to the time of the maintenance release. Patch sets are fully tested and integrated product fixes. All the product fixes in the patch set have been tested and are certified to work with each other.
Every patch or patch set is associated with a bug number for identification purposes. Patch sets are also associated with version numbers. For example, if you use Oracle Database 11g Release 184.108.40.206, then an available patch set might be 220.127.116.11. The version number of the patched software does not change if an interim patch is applied.
Every patch has an associated README file that describes how it fixes the software. The README file also has instructions for applying the patch.
Every patch set is accompanied by a Patch Set Notes file that contains installation instructions and information about the product fixes contained within the patch set. When you apply a patch set to your Oracle software, you change the maintenance release number for your installed software. Applying a patch set affects the software residing in your Oracle home only, with no change to the data in the database.
You can use Oracle Enterprise Manager Database Control to automate the staging and application of Oracle patches and patch sets. Database Control stages an Oracle patch by downloading it from the OracleMetaLink Web site and copying it to a directory on the server.
The steps involved in patching the Oracle software are as follows:
To select the appropriate patch set release for your environment, you need to know the following details about your Oracle environment:
Oracle Database version
Oracle home location
You can determine your Oracle Database version at the Enterprise Manager Database Control (Database Control) Database Home page.
View the Version number under General on the Database Home page.
Your Oracle home is the operating system location of your Oracle Database installation.
In the General section of the Database Home page, click View All Properties.
The View All Properties page appears.
This page displays the path to your Oracle home.
Click the path link next to Oracle Home.
The Oracle home:
Oracle_home page appears, as shown in Figure 12-1.
This page displays the file directory of your Oracle home, along with the installed Oracle components and time of installation.
In the Products table, click one of the links in the Component column, for example, Oracle Database 11g 18.104.22.168.0.
The Oracle Component: component_name page appears.
This page displays the following information about the selected component:
Interim patches affecting component_name with a description and installation time for each patch
Components that component_name depends upon and their installation times
Components that component_name is used by and their installation times
In the Oracle Home Targets table, click one of the links in the Name column to display pages for the Enterprise Manager agent, database instance, and listener.
Your hardware configuration consists of your database computer and operating system. You need this information to select the appropriate Oracle Database patch or patch set.
In the General section of the Database Home page, click the name of your Host.
The Host: host_name page appears.
This page displays the following information about your hardware configuration:
Number of CPUs
Memory size (MB)
Local file system (GB)
In the Configuration section, click the links to drill down to pages that describe your operating system, hardware platform, and local file system in more detail.
You can obtain patches and patch sets from OracleMetaLink at the following URL:
To download patches and patch sets from OracleMetalink, you must register using your customer support identifier, which your company obtains when it signs a support contract with Oracle. When you register with OracleMetaLink, you are given a user name and password that enables you to log in to this site from a Web browser.
Before you begin using the patching features of Database Control, you must configure your OracleMetaLink credentials. After you specify your OracleMetaLink credentials, an automated process called the RefreshFromMetalink job can search OracleMetaLink every day for patches that are applicable to your installed software. You also receive notification about critical patch advisories.
Click the Setup link located at the top and bottom of most Database Control pages.
The Setup page appears.
Click Patching Setup.
The Patching Setup subpage appears.
Enter the user name and password for logging in to OracleMetaLink in the MetaLink Username and MetaLink Password fields.
(Optional) Enter the maximum size of your patch cache in the Patch Cache Maximum Size (MB) field.
The patch cache is a temporary area where patches are stored. When the patch cache exceeds the specified maximum size, Database Control automatically performs a purge operation and tries to delete old patches until the patch cache is smaller than the specified maximum size.
Click Apply to set your OracleMetaLink credentials.
Applying a patch or patch set is the process of installing the staged, or locally stored, patch files in the Oracle home on the server. You must specify patching credentials before you can stage and apply a patch or patch set using Enterprise Manager.
From the Database Home page, click Software and Support.
The Database Instance: instance_name page appears.
In the Database Software Patching section, select Apply Patch.
The Select Patches page appears.
Click Add Patches to search for new patches to apply.
The Search and Select Patches page appears.
In the Search section, choose your current database release from the list of values in the Release list, for example, 22.214.171.124.0. From the Platform list choose the name that matches your installed operating system, for example, Linux x86. After you have made your selections, click Go.
You can optionally limit your search further by choosing different values for Product Family, Product, Patch Type, and Language, and then clicking Go.
(Optional) Select a patch or patch set and click View to view the patch details.
Select a patch or patch set and start the Patching wizard by clicking Select in the top right corner of the page.
The Select Patches page appears.
If the patch or patch set you selected in Step 5 does not appear in the Patches table, click Add Patch and repeat the search to locate the patch. When the patch or patch set you have selected is displayed in the Patches table, click Next.
The Credentials and Schedule page appears.
Enter the credentials for the operating system user that will perform the patching operation. If you have already configured Preferred Credentials, you can choose the Use Preferred option.
For the Schedule Type option, use the default value of One Time (Immediately). Optionally, you can choose to schedule the patching for a later time using the One Time (Later) option. Click Next to continue.
The Review page appears.
Review the information on this page. If any of the information is incorrect, you can click Back to return to a previous page and make corrections. When finished, click Finish to submit the job that patches the database.
The Deployment Procedure Manager page appears.
(Optional) To view the progress of the recently submitted patching operation, click Patch Oracle Standalone Database.
The Procedure Completion Status page appears.
As part of the patching procedure, the database instance and Database Control are shut down and then restarted. After they have restarted, you must log in again and navigate to the Procedure Completion Status page to check the status.
After you have reviewed the status of each step, you can click Refresh to update the display if the procedure has not yet completed.
When you have finished viewing the results, click Done.
Click the Database tab.
The Patch Advisor in Enterprise Manager describes critical software patches for your installed Oracle products. To help ensure a secure and reliable configuration, all relevant and current critical patches should be applied.
The Patch Advisor provides support for Remedies. When you select an advisory, you can view the calculated remedies from the context of that Advisory, as well as the affected Oracle homes.
The Patch Advisor also displays a list of available patches and patch sets for your installation, along with the name of the feature that is impacted. You can choose to display only patches for features that are used by your database, or all available patches.
Using Database Control, on the Database Home page, in the Policy Violations section, view the count for Critical Security Patches.
If any critical patches have not been applied to the Oracle home for the database, this section displays the number of critical patch advisories that are relevant to the Oracle home for the database. Also, a warning icon appears corresponding to the Oracle Home link on the Database Home page is the Oracle home is missing critical patches.
To view a list of available critical patch advisories, click the nonzero number next to the heading Critical Security Patches. Alternatively, from the Database Home page, select the Software and Support subtab, then, under the heading Database Software Patching, click Patch Advisor.
The Patch Advisor page appears, listing the available critical security patches and patch recommendations by feature.
(Optional) In the Critical Security Patches table, click a value in the Advisory column to view further details for that critical security patch.
(Optional) To view all available patches, in the Patch Recommendations by Feature table, in the View list, select the value All, then click Go.
Use Database Upgrade Assistant (DBUA) to upgrade an existing database to the current release of Oracle Database.
This section contains these topics:
Database Upgrade Assistant (DBUA) guides you through the upgrade process and configures your database for the new release. DBUA automates the upgrade process and makes appropriate recommendations for configuration options such as tablespaces and redo logs.
DBUA can be used to upgrade databases created using any edition of the Oracle Database software, including Express Edition (XE) databases.
DBUA does not begin the upgrade until it completes all of the following pre-upgrade steps:
Checks for any invalid user accounts or roles
Checks for any invalid data types or invalid objects
Checks for any desupported character sets
Checks for adequate resources, including rollback segments, tablespaces, and free disk space
Checks for any missing SQL scripts needed for the upgrade
Backs up all necessary files (optional)
After completing the pre-upgrade steps, DBUA automatically performs the following tasks:
Modifies or creates new required tablespaces
Invokes the appropriate upgrade scripts
Archives redo logs
Disables archiving during the upgrade phase (to improve performance)
While the upgrade is running, DBUA shows the upgrade progress for each component. DBUA writes detailed trace and log files and produces a complete HTML report for later reference. To enhance security, DBUA automatically locks new user accounts in the upgraded database. DBUA then proceeds to create new configuration files (initialization parameter and listener files) in the new Oracle home.
DBUA is fully compliant with Oracle Real Application Clusters (Oracle RAC) environments. In Oracle RAC environments, DBUA upgrades all database and configuration files on all nodes in the cluster.
DBUA supports upgrades of databases that use Automatic Storage Management (ASM). If an ASM instance is detected, then you have the choice of updating both the database and ASM or only the ASM instance.
DBUA supports the following versions of Oracle Database for upgrading to Oracle Database 11g Release 1 (11.1):
Oracle9i Release 2 (126.96.36.199) and beyond
Oracle Database 10g Release 1 (10.1)
Oracle Database 10g Release 2 (10.2)
If your database version is not in this list, then you need to upgrade first to the closest release listed. You can then upgrade the database to Oracle Database 11g Release 1 (11.1).
If you install the Oracle Database software only and specify that you are upgrading an existing database to the new Oracle Database release, then DBUA is launched automatically at the end of the software installation. You can then continue as described in "Upgrading a Database Using DBUA".
If you perform a software-only installation and do not upgrade your database at that time, then you can do so later by launching DBUA.
Be aware of the following before you begin using DBUA:
You must run Net Configuration Assistant (NETCA) before running DBUA.
If the database instance is not running, then DBUA will try to start the instance with the default initialization parameter file. If that fails, then you will be prompted to provide the name of the correct initialization parameter file or to start the instance. If the instance is already up and running, then DBUA connects to it.
If you stop the upgrade, but do not restore the database, then you should not restart DBUA until you start up the existing database in
UPGRADE mode using the Oracle Database 11g software. You cannot go back to the original server unless you restore your database.
If you restore your database manually (not using DBUA), then remove the following file before starting DBUA:
The presence of this file indicates to DBUA that this is a rerun operation.
Click Start, select Programs (or All Programs), then Oracle - HOME_NAME, then Configuration and Migration Tools, and then Database Upgrade Assistant.
The Database Upgrade Assistant: Welcome window appears.
Open a command window.
(Linux and UNIX systems only) Set the required environment variables by running the script
oraenv (for the Bourne, Korn, or Bash shells) or
coraenv (for the C shell).
These scripts are typically located in the
/usr/local/bin directory. They may prompt you for the desired value of the
ORACLE_SID environment variable. If so, supply the system ID (SID) that you chose when you installed Oracle Database. The default SID that the installer typically suggests is
(Linux and UNIX systems only) Either ensure that the
/bin directory is in your
PATH environment variable, or change directory to
Enter the following command:
The Database Upgrade Assistant: Welcome window appears.
dbuaexecutable is typically found in your
See Also:Oracle Database Upgrade Guide for more information about Database Upgrade Assistant
Complete the following steps to upgrade a database using DBUA. If you need help at any window or want to consult more documentation about DBUA, then click the Help button to access the online Help.
Start DBUA. See "Starting DBUA".
At the Welcome window of DBUA, make sure the database being upgraded meets the specified conditions. Then, click Next.
If an ASM instance is detected on the system, then the Upgrade Operations window appears. If no ASM instance is detected, then the Databases window appears.
(ASM detected only) From the Upgrade Operations window you can choose to upgrade only the ASM instance or the database. If you choose to upgrade the database and if the database is using ASM, then DBUA will ask you whether or not to upgrade the ASM instance along with the database. Oracle recommends that you upgrade the database and ASM in separate DBUA sessions, in separate Oracle homes.
At the Databases window, select the database you want to upgrade from the Available Databases table. Then, click Next.
You can select only one database at a time. If you are running DBUA from a user account that does not have
SYSDBA privileges, then enter the user name and password credentials to enable
SYSDBA privileges for the selected database.
DBUA displays a message saying it is getting database information. DBUA analyzes the selected database, performing pre-upgrade checks and displaying warnings as necessary:
It checks for any online redo log files of a size less than 4 megabytes (MB). If such files are found, then DBUA gives the option to drop or create new online redo log files.
It checks the initialization parameter file for any obsolete or deprecated initialization parameters.
If no problems are found, then the Diagnostic Destination window appears.
In the Diagnostic Destination field, do one of the following:
Leave the setting at its default value, which is the Oracle base directory.
Enter a new destination.
Click Browse and select a new destination.
Diagnostic Destination is the default location to store Oracle trace and diagnostic files. It replaces the initialization parameter settings for background dump destination, user dump destination and core dump destination from earlier Oracle Database releases.
The Move Database Files window appears.
Do one of the following:
Select Do Not Move Database Files as Part of Upgrade.
Select Move Database Files During Upgrade.
If you choose to move database files, then you must also select either File System or Automatic Storage Management (ASM).
The Recompile Invalid Objects window appears.
(Optional) Select Recompile invalid objects at the end of upgrade and modify the value of degree of parallelism.
When you upgrade your database to the new Oracle Database release, many of the PL/SQL modules in the database become invalid. By default, Oracle Database will recompile invalid PL/SQL modules as they are used, but this takes time and can result in poor performance. To eliminate these performance issues, select Recompile invalid objects at the end of upgrade. All the invalid PL/SQL modules will be recompiled immediately after the upgrade is performed. The task of recompiling all the invalid PL/SQL modules in your database can take a significant amount of time and increase the time it takes to complete your database upgrade.
If you have multiple CPUs, then DBUA automatically adds a Degree of Parallelism menu to the Recompile Invalid Objects window. Parallel processing reduces the time it takes to recompile all the invalid PL/SQL modules in your database. DBUA automatically sets the degree of parallelism to one less than the number of available CPUs. You can select a different value from the menu.
Note:Selecting Recompile invalid objects at the end of upgrade is equivalent to running the
/rdbms/admin/utlrp.sqlscript, which is used to recompile stored PL/SQL and Java code.
The Backup window appears.
Select one of the following options:
I have already backed up my database.
I would like this tool to back up the database.
If you use DBUA to back up your database, then DBUA makes a copy of all database files in the directory that you specify in the Backup Directory field. DBUA performs this consistent backup automatically after it shuts down the database and before it begins the upgrade process. The backup does not compress the database files.
In the Backup Directory field, do one of the following:
Leave the setting at its default value
Enter a different valid file system path. You cannot specify a raw device for the backup files.
Click Browse and select a new backup destination.
Oracle strongly recommends that you back up your database before starting the upgrade. If errors occur during the upgrade, then you may need to restore the database from the backup.
In addition to creating a backup of your database, DBUA creates an executable script in the directory specified in the Backup Directory field. If needed, you can use the executable script appropriate to your system to restore the database files:
Linux or UNIX systems:
The Recovery Configuration window appears.
In the Flash Recovery Area field, do one of the following:
Leave the setting at its default value
Enter a different Flash Recovery Area
Click Browse and select a different Flash Recovery Area.
The Flash Recovery Area can be used to recover data that would otherwise be lost during a failure. This location is also used by Enterprise Manager if you have enabled local management and daily backups on the Database Control Management Options page.
In the Flash Recovery Area Size field, select the units you want from the list and do one of the following:
Leave the setting at its default value.
Enter a different value for Flash Recovery Area Size.
Use the up and down arrows to set a different Flash Recovery Area Size.
In the Recovery Configuration window, you specify a Flash Recovery Area and enable archiving. It is important to configure these features for your database so you can recover your data in the event of a failure.
The Summary window appears.
Review the list the initialization parameters that will be set for the database during the upgrade. Click Back to correct any errors, or click Finish.
Note:The database will not be available for general use during the upgrade process that begins when you click Finish.
A Progress window appears and DBUA begins to perform the upgrade.
You might encounter error messages with Ignore and Abort choices:
Ignore - Ignores the error, skips the current step, and proceeds with the upgrade. The ignored errors are logged and shown later in the summary. After the upgrade is complete, you can fix the problem, restart DBUA, and complete the skipped steps.
Abort - Stops the upgrade process. DBUA prompts you to restore the database if the database backup was performed by DBUA. After the database has been restored, correct the error and restart DBUA to perform the upgrade again. If you do not restore the database, then DBUA leaves the database in its current state so that you can proceed with a manual upgrade.
After the upgrade has completed, the following message is displayed:
Upgrade is complete. Click "OK" to see the results of the upgrade.
The Upgrade Results window appears.
Examine the results of the upgrade. The upgrade results summary describes the original and upgraded databases and changes made to the initialization parameters.
The upgrade results also include an Upgrade Details section that describes the steps performed during the database upgrade. This section provides each step name, the log file for the step, and the status. In some cases, you can click the status to display details about the execution step. The Upgrade Details section also includes the directory where the various log files are stored after the upgrade. You can examine any of these log files to obtain more details about the upgrade process.
Note:An HTML version of the Upgrade Results is also saved in the log files directory.
Click Configure Database Passwords.
The Password Management dialog box appears.
The Password Management dialog box enables you to change the default password for a user after you upgrade the database.
Note:To prevent unauthorized use of the database, change all user passwords immediately after you upgrade your database.
Click the Lock Account? column for a user to lock or unlock an account. A check mark indicates that the account is locked.
Enter a new password for a user in its New Password column.
Confirm the new password by entering it in the Confirm Password column.
Click OK to return to the Upgrade Results window.
Click Restore if you are not satisfied with the upgrade results.
Depending on the method you used to back up your database, the restore operation performs one of the following tasks:
If you used DBUA to back up your database, then clicking Restore copies the original database files and the original database settings from the backup.
If you used your own backup procedure to back up the database, then clicking Restore copies only the original database settings. To restore the database itself, copy the datafiles from the backup you created using your own backup utilities.
Click Close to quit DBUA if you are satisfied with the upgrade results.
DBUA removes the entry of the upgraded database from the old
listener.ora file and restarts the listener.
If you retain the old Oracle Database software, then never start the upgraded database with it. Only start the database with the executable files in the new Oracle Database installation. Also, before you remove the old Oracle Database environment, make sure you relocate any datafiles in that environment to the new Oracle Database environment. See Oracle Database Administrator's Guide for information about relocating datafiles.
See Also:Oracle Database Upgrade Guide for information about additional tasks that should be completed after upgrading a database
Oracle By Example (OBE) has a series on the Oracle Database 2 Day DBA guide. This OBE steps you through the tasks in this chapter, and includes annotated screenshots.
To view the Managing Oracle Software OBE, in your browser, enter the following URL: