Oracle® Database Patch Set Notes
11g Release 1 (11.1.0.7) Patch Set 1 for Microsoft Windows (32-Bit)
Part Number E12584-01
Oracle® Database
Patch Set Notes
11g Release 1 (11.1.0.7) Patch Set 1 for Microsoft Windows (32-Bit)
E12584-01
October 2008
These patch set notes accompany the Oracle Database release 11.1.0.7 patch set. This document contains the following sections:
Patch Set Overview
Critical Patch Updates
Accessing the Latest Version of this Document
Oracle Universal Installer Version Requirements
Patch Set Documentation
System Requirements
Preinstallation Tasks
Installation Tasks
Postinstallation Tasks
Removing the Patch Set Software
Reinstalling the Patch Set Software
Known Issues
Documentation Accessibility
1 Patch Set Overview
Patch sets are a mechanism for delivering fully tested and integrated
product fixes. Patch sets provide bug fixes only; they do not include
new functionality and they do not require certification on the target
system.
Patch sets include all of the libraries that have been rebuilt to
implement the bug fixes in the set. All of the fixes in the patch set
have been tested and are certified to work with each other. Because the
patch set includes only low impact patches, it does not require you to
certify applications or tools against the server.
You can apply the Oracle Database release 11.1.0.7 patch set to the following Oracle Database 11g release 1 installations:
Oracle Database
Oracle Real Application Clusters
Oracle Database Client
Oracle Database Examples
Oracle Clusterware
Oracle Automatic Storage Management Only instance
2 Critical Patch Updates
Review the latest Critical Patch Update information at http://www.oracle.com/technology/deploy/security/alerts.htm.
3 Accessing the Latest Version of this Document
This document may be updated after release. To check for updates to this document, see document 454507.1, ALERT: Oracle 11g release 1 (11.1) Support Status and Alerts, on the OracleMetaLink Web site:
http://metalink.oracle.com
To locate document 454507.1:
Log on to OracleMetaLink.
Click Advanced at the top of the OracleMetaLink page.
Enter 454507.1 in the Document ID field, then click Submit.
4 Oracle Universal Installer Version Requirements
This patch set includes Oracle Universal Installer release 11.1.0.7,
which is also installed when you install this patch set. This is to
ensure that the Oracle home can be patched in the future. You should not
use Oracle Universal Installer from the earlier maintenance release
media or Oracle home.
This is not a complete software distribution. You must install it in an existing Oracle Database 11g (11.1.0.6) installation.
5 Patch Set Documentation
The Oracle Database List of Bugs Fixed, 11g release 1 (11.1.0.7)
document is no longer available as a separate document that ships with
the software. A mechanism for finding fixed bugs is available from
document 454507.1, ALERT: Oracle 11g Release 1 (11.1) Support Status and Alerts.
There is a platform-specific document, Oracle Database Patch Set Notes, 11g release 1 (11.1.0.7) Patch Set, related to each platform for this release of the Oracle Database patch set. This document provides:
Information about how to install, reinstall, or remove the patch set.
A list of known issues relating to Oracle Database on the platform.
This document is included with the patch set software. In addition,
this document and the mechanism for finding fixed bugs are available
from document 454507.1, ALERT: Oracle 11g Release 1 (11.1) Support Status and Alerts on the OracleMetaLink Web site:
http://metalink.oracle.com
To locate document 454507.1:
Log on to OracleMetaLink.
Click Advanced at the top of the OracleMetaLink page.
Enter 454507.1 in the Document ID field, then click Submit.
6 System Requirements
Check your platform-specific installation guide for a list of supported operating systems. Check Certify on the OracleMetaLink Web site for the latest certification information.
7 Preinstallation Tasks
Complete the following preinstallation tasks before installing the patch set:
Review Known Preinstallation Issues
Identify the Oracle Database Installation
Check Postrelease Updates
Download and Extract the Installation Software
Update Oracle Time Zone Definitions
Stop All Services
Back Up the System
7.1 Review Known Preinstallation Issues
Review the information in the following sections. If any of the
issues apply to the Oracle installation, follow the instructions before
installing the patch set.
Upgrading Oracle E-Business Suite Databases
Upgrading Oracle Clusterware
Using ASM Rolling Upgrades
Notes to Oracle OLAP Users
Notes to Oracle Text Users
7.1.1 Upgrading Oracle E-Business Suite Databases
If you are an Oracle E-Business Suite customer and you want to upgrade the Oracle E-Business Suite release 11i
database server to this patch set, then you must check the latest
certification status and Interoperability Notes available on the OracleMetaLink Web site:
http://metalink.oracle.com
7.1.2 Upgrading Oracle Clusterware
The Oracle Clusterware software must be at the same or newer level as
the Oracle software in the Oracle RAC Oracle home or ASM Home.
Therefore, you should always upgrade Oracle Clusterware before you
upgrade Oracle RAC or Oracle ASM. This patch does not allow you to
upgrade Oracle RAC or Oracle ASM before you upgrade Oracle Clusterware.
7.1.3 Using ASM Rolling Upgrades
Automatic Storage Management (ASM) rolling upgrades enable you to
independently upgrade or patch clustered ASM nodes without affecting
database availability, thus providing greater uptime. Rolling upgrade
means that all of the features of a clustered ASM environment function
when one or more of the nodes in the cluster uses different software
versions.
To perform a rolling upgrade, your environment must be prepared. If
you are using Oracle Clusterware, then your Oracle Clusterware must be
fully upgraded to the next patch or release version before you start the
ASM rolling upgrade. In addition, you should prepare your Oracle
Clusterware in a rolling upgrade manner to ensure high availability and
maximum uptime.
For information about ASM rolling upgrades, see Chapter 3, "Administering ASM Instances", in Oracle Database Storage Administrator's Guide.
7.1.4 Notes to Oracle OLAP Users
To apply this patch set, Oracle OLAP users should ensure that the
base release is Enterprise Edition 11.1.0.6.0 with the Oracle OLAP
option installed. Oracle highly recommends the Data Warehouse
configuration type to optimize the database for Oracle OLAP.
If you are moving the Oracle Database from a 32-bit operating system
to a 64-bit operating system, either prior to applying the patch set or
after applying the patch set, review document 352306.1 on the OracleMetaLink Web site:
http://metalink.oracle.com
To locate document 352306.1:
Log on to OracleMetaLink.
Click Advanced at the top of the OracleMetaLink page.
Enter 352306.1 in the Document ID field, then click Submit.
7.1.5 Notes to Oracle Text Users
After upgrade to 11.1.0.7, Oracle Text uses Oracle Outside In HTML
Export for document filtering instead of filtering technology licensed
from Autonomy, Inc.
This product requires the Visual C++ libraries included in the Visual
C++ Redistributable Package available from Microsoft. There are three
versions of this package (x86, x64, and IA64) for each corresponding
version of Windows.
These libraries can be downloaded from http://www.microsoft.com/downloads/, by searching the site for the vcredist_x86.exe, vcredist_x64.exe, or vcredist_IA64.exe
packages. The required version of each of these downloads is the 2005
SP1 Redistributable Package. The redistributable module that Outside In
requires is msvcr80.dll.
With migration to Oracle Outside In HTML Export, several document formats are no longer supported. Refer to Appendix B of Oracle Text Reference
for a complete list of filter-supported document formats in 11.1.0.7.
The document formats no longer supported in 11.1.0.7 are listed in the
following sections.
7.1.5.1 Word Processing Formats
The following word processing formats are no longer supported:
Applix Words (AW), versions 3.11, 4.0, 4.1, 4.2, 4.3, 4.4
JustSystems Ichitaro (JTD), version 2005
Folio Flat File (FFF), version 3.1
Fujitsu Oasys (OA2), version 7
Lotus Word Pro (LPW), versions 9.7 and 9.8
WordPerfect for Linux, all versions
7.1.5.2 Desktop Publishing Format
The following desktop publishing format is no longer supported:
Adobe FrameMaker (MIF), version 7
7.1.5.3 Spreadsheet Formats
The following spreadsheet formats are no longer supported:
Applix Spreadsheets (AS), versions 4.2, 4.3, 4.4
Lotus 1-2-3 (123), Millenium Edition R9, version 9.8
Microsoft Works Spreadsheet (DOS), versions 3 and 4
Microsoft Works Spreadsheet (Mac), versions 3 and 4
Comma Separated Values (CSV)
7.1.5.4 Presentation Formats
The following presentation formats are no longer supported:
Applix Presents (AG), versions 4.0, 4.2, 4.3, 4.4
Lotus Freelance Graphics (PRE) Millenium Edition R9, version 9.8
Microsoft Visio XML format, version 2003
7.1.5.5 Graphics Formats
The following graphics formats are no longer supported:
SGI RGB Image (RGB), no specific version
Windows Animated Cursor (ANI), no specific version
WordPerfect Graphics 2 (WPG2), version 7
Microsoft Office Drawing (MSO), no specific version
Microsoft Icon Cursor (ICO), no specific version
7.2 Identify the Oracle Database Installation
This is not a complete software distribution. You must install it in an existing Oracle Database 11g
release 11.1.0.6 Oracle home. Use Oracle Universal Installer to
identify Oracle home directories. From the Welcome screen, click Installed Products, then click the Environment tab.
You should then cross-check this by executing the following command:
opatch lsinventory -all
7.3 Check Postrelease Updates
Before installing this patch set in a production environment, review document 454507.1, ALERT: Oracle 11g release 1 (11.1) Support Status and Alerts, available on the OracleMetaLink Web site:
http://metalink.oracle.com
To locate this document:
Log on to OracleMetaLink.
Click Advanced at the top of the OracleMetaLink page.
Enter 454507.1 in the Document ID field, then click Submit.
This document is created by Oracle Support Services and provides
information about the status of issues discovered after this patch set
was released. If you are unable to access this site, then contact Oracle
Support Services before installing this patch set in a production
environment.
7.4 Download and Extract the Installation Software
To download and extract the patch set installation software:
Download patch 6890831 to a directory that is not the Oracle home directory or under the Oracle home directory.
Compare the downloaded zip file size to the actual file size on OracleMetaLink.
Use the unzip command to unzip and extract the patch set files.
7.5 Update Oracle Time Zone Definitions
The 11.1.0.7 patch set includes the Oracle time zone definitions
Version 4. This version of the time zone definitions includes the
changes to daylight savings time in the USA in 2007 and other updates.
In the Oracle database the TIMESTAMP WITH LOCAL TIME ZONE (TSLTZ) and TIMESTAMP WITH TIME ZONE (TSTZ) data types and the TZ_OFFSET function select the time zone information from the time zone files.
It may be necessary to take action on existing TIMESTAMP WITH LOCAL TIME ZONE (TSLTZ) and TIMESTAMP WITH TIME ZONE (TSTZ) data or to re-apply DST patches afterwards.
For full overview please see OracleMetaLink document 568125.1 Actions for the DSTv4 update in the 11.1.0.7 patchset.
When upgrading directly from a 10.2 or 10.1 release or updating
11.1.0.6 to 11.1.0.7, check the current version of the Oracle time zone
definitions with the following command:
SELECT version FROM v$timezone_file;
If the query reports version 4, no action is required.
If the query reports a version lower or higher then 4, see OracleMetaLink document 568125.1, Actions for the DSTv4 update in the 11.1.0.7 patchset.
On upgrading from Oracle9i directly to Release 11.1.0.7, see OracleMetaLink document 568125.1, Actions for the DSTv4 update in the 11.1.0.7 patchset.
7.6 Stop All Services
Go to the following sections based on the Oracle Database installation type:
Stopping All Services for a Single Instance Installation
Stopping All Services for an Oracle Clusterware Installation
Stopping All Processes for an Oracle RAC Installation
Stopping the Oracle Warehouse Builder (OWB) Control Center
See also:
"How to Stop Processes in an Existing Oracle Real Application Clusters Database" in Oracle Database Oracle Real Application Clusters Installation Guide.
7.6.1 Stopping All Services for a Single Instance Installation
Shut down the following Oracle Database 11g services in the order specified before installing the patch set:
Shut down all services in the Oracle home that might be accessing a
database, for example Oracle Enterprise Manager Database Control:
C:\> ORACLE_BASE\ORACLE_HOME\bin\emctl stop dbconsole
You can also stop these services using Windows Control Panel. In the Services window, this service is named OracleDBConsoleSID.
Note:
Before you shut down all processes that are monitored by Oracle
Enterprise Manager Grid Control, set a blackout in Grid Control for the
processes that you intend to shut down. This is necessary so that the
availability records for these processes indicate that the shutdown was
planned downtime rather than an unplanned system outage.
Shut down all listeners running in the Oracle home directory where
you will install the patch set. You can execute this command to stop a
listener:
C:\> lsnrctl stop [listener_name]
or from the Services window of Windows Control Panel, stop the listener service OracleHOME_NAMETNSListenerLISTENER_nodename.
Set the values for ORACLE_HOME and ORACLE_SID and then shut down all database instances running in the Oracle home directory where you will install the patch set.
Execute these commands to shut down a database instance:
C:\> sqlplus /NOLOG
SQL> CONNECT SYS AS SYSDBA
Enter password:SYS_PasswordSQL> SHUTDOWN
Then, from the Services window of Windows Control Panel, stop the Oracle Database service. The service name is OracleServiceSID, where SID is the system identifier of the database.
If the Automatic Storage Management instance is running in the Oracle
home directory where you need to install the patch set, then perform
the following steps:
Set the ORACLE_HOME environment variable to ASM_HOME. Set the ORACLE_SID environment variable to +ASM.
Shut down the Automatic Storage Management instance:
C:\> sqlplus /NOLOG
SQL> CONNECT SYS AS SYSASM
Enter password:SYS_passwordSQL> SHUTDOWN IMMEDIATE
Shut down the Oracle Cluster Synchronization Services instance by entering the following command:
C:\> ORACLE_BASE\ORACLE_HOME\bin\crsctl stop crs
Shut down the OracleASMServiceASMSID service from the Services Control Panel.
Shut down the OracleCSService service from the Services Control Panel.
7.6.2 Stopping All Services for an Oracle Clusterware Installation
This section contains the following information:
Rolling Upgrade
Non Rolling Upgrade
7.6.2.1 Rolling Upgrade
By default, Oracle supports rolling upgrade for Oracle Clusterware. Complete the following steps only on one node:
Shut down all services in the Oracle home on the node that might be
accessing a database, for example Oracle Enterprise Manager Database
Control:
C:\> ORACLE_BASE\ORACLE_HOME\bin\emctl stop dbconsole
Note:
Before you shut down all services that are monitored by Oracle
Enterprise Manager Grid Control, set a blackout in Grid Control for the
services that you intend to shut down. This is necessary so that the
availability records for these services indicate that the shutdown was
planned downtime rather than an unplanned system outage.
Shut down all Oracle RAC instances on the node on which you intend to
perform the rolling upgrade. To shut down Oracle RAC instances on
individual nodes in the database, enter the following command where db_name is the name of the database:
C:\> ORACLE_BASE\ORACLE_HOME\bin\srvctl stop instance -d db_name -i inst_name
If an Automatic Storage Management instance is present, then shut
down the Automatic Storage Management instance on the node on which you
intend to perform the rolling upgrade. To shut down an Automatic Storage
Management instance, enter the following command where node is the name of the node where the Automatic Storage Management instance is running:
C:\> ORACLE_BASE\ORACLE_HOME\bin\srvctl stop asm -n node
Stop all node applications running on the node. Enter the following command, where node is the name of the node where the applications are running:
C:\> CRS_home\bin\srvctl stop nodeapps -n node
Stop the Oracle Clusterware on the node on which you intend to perform the rolling upgrade:
C:\> CRS_home\bin\crsctl stop crs
Use the Service window to stop the following services if they are running:
OracleDBConsoleSID
OracleServiceSIDOracleJobSchedulerSID
OracleASMServiceASMSIDOracleHOME_NAMETNSListenerLISTENER_nodenameOracle Object Service
OracleClusterVolumeService
OracleCRService
OracleCSService
OracleEVMService
OracleRemExecService
OracleHOME_NAMEConfigurationManager
Oracle SID VSS Writer Service
Complete the steps mentioned in Section 8, "Installation Tasks".
Note:
The following instructions are displayed on the Oracle Universal Installer screen:
To complete the installation of this patch set, perform the following tasks on each node:
Shut down the following Oracle Clusterware Services:
OracleCRService
OracleEVMService
OracleCSService
Oracle Object Service
OracleClusterVolumeService
Run patch111.bat to automatically start the Oracle Clusterware services on the patched node:
C:\> CRS_home\install\patch111.bat
After completing this procedure, proceed to the next node and repeat.
To upgrade the rest of the nodes, go to the next node and perform Steps 1 to 6 and then enter the following command:
C:\> CRS_home\install\patch111.bat
7.6.2.2 Non Rolling Upgrade
For non rolling upgrade, Oracle Clusterware needs to be shut down completely.
Complete the following steps:
Shut down all services in the Oracle home on each node that might be
accessing a database, for example Oracle Enterprise Manager Database
Control:
C:\> ORACLE_BASE\ORACLE_HOME\bin\emctl stop dbconsole
Note:
Before you shut down all services that are monitored by Oracle
Enterprise Manager Grid Control, set a blackout in Grid Control for the
services that you intend to shut down. This is necessary so that the
availability records for these services indicate that the shutdown was
planned downtime rather than an unplanned system outage.
Shut down all Oracle RAC instances on all cluster nodes by entering the following command where db_name is the name of the database:
C:\> ORACLE_BASE\ORACLE_HOME\bin\srvctl stop database -d db_name
If Automatic Storage Management instance is present in the home to
which the patch is being applied, then shut down Automatic Storage
Management instances on all cluster nodes by entering the following
command where node is the name of the node where the Automatic Storage Management instance is running:
C:\> ORACLE_BASE\ORACLE_HOME\bin\srvctl stop asm -n node
Stop all node applications on all cluster nodes by entering the following command, where node is the name of the node where the applications are running:
C:\> ORACLE_BASE\ORACLE_HOME\bin\srvctl stop nodeapps -n node
Shut down the Oracle Clusterware services on each node by entering the following command:
C:\> CRS_home\bin\crsctl stop crs
Use Service Manager to stop the following services if any of them is running:
OracleDBConsoleSID
OracleServiceSIDOracleJobSchedulerSID
OracleASMServiceASMSIDOracleHOME_NAMETNSListenerLISTENER_nodenameOracle Object Service
OracleClusterVolumeService
OracleCRService
OracleCSService
OracleEVMService
OracleRemExecService
OracleHOME_NAMEConfigurationManager
Oracle SID VSS Writer Service
Complete the steps mentioned in Section 8, "Installation Tasks".
Run patch111.bat to upgrade the current node, and to automatically start the Oracle Clusterware services:
C:\> CRS_home\install\patch102.bat
To upgrade the rest of the nodes, go to the next node and enter the following command:
C:\> CRS_home\install\patch111.bat
7.6.3 Stopping All Processes for an Oracle RAC Installation
Shut down the following Oracle Database 11g services before installing the patch set:
C:\> ORACLE_BASE\ORACLE_HOME\bin\emctl stop dbconsole
Note:
Before you shut down all services that are monitored by Oracle
Enterprise Manager Grid Control, set a blackout in Grid Control for the
services that you intend to shut down. This is necessary so that the
availability records for these services indicate that the shutdown was
planned downtime rather than an unplanned system outage.
Shut down all Oracle RAC instances on the nodes, which run from the
Oracle home on which you are going to apply the patch set. To shut down
all Oracle RAC instances for a database, enter the following command
where db_name is the name of the database:
C:\> ORACLE_BASE\ORACLE_HOME\bin\srvctl stop database -d db_name
If Automatic Storage Management instance is present, then shut down
Automatic Storage Management instances on all nodes by entering the
following command where node is the name of the node where the Automatic Storage Management instance is running:
C:\> ORACLE_BASE\ORACLE_HOME\bin\srvctl stop asm -n node
Stop any listeners that are running from the Oracle home that you are
patching on all nodes. To stop the listener running on a node, enter
the following command, where node is the name of the node where the listener is running:
C:\> ORACLE_BASE\ORACLE_HOME\bin\srvctl stop listener -n node [-l listenername]
Use Service Manager to stop the following services if any of them is running:
OracleDBConsoleSID
OracleServiceSIDOracleASMServiceASMSIDOracleRemExecService
OracleHOME_NAMETNSListenerLISTENER_nodename
Note:
Using a logical standby database, you can upgrade Oracle Database
software and patch sets with almost no downtime. Using Data Guard SQL
Apply, you can perform a rolling upgrade of the Oracle Database software
from release 11.1.0.6 to the current patch set release. During a
rolling upgrade, you can run different releases of Oracle Database on
the primary and logical standby databases, while you upgrade them, one
at a time, incurring minimal downtime on the primary database.
See also:
Chapter 11, "Using SQL Apply to Upgrade the Oracle Database" of Oracle Data Guard Concepts and Administration
7.6.4 Stopping the Oracle Warehouse Builder (OWB) Control Center
If you are a user of Oracle Warehouse Builder 11.1 (Release
11.1.0.6), that is, you set up the OWB repository and workspaces, and
you are using OWB functionality, then you need to perform the following
steps prior to installing the Oracle Database 11.1.0.7 patch:
Exit all Oracle Warehouse Builder applications.
Stop the OWB Control Center service.
To stop the Control Center service, run the stop_service.sql script:
$ sqlplus OWBSYS
Enter password: OWBSYS_password@ ORACLE_BASE\ORACLE_HOME\owb\rtp\sql\stop_service.sql
A return value of Not Available appears, indicating that you successfully stopped the service.
After installing the Oracle Database 11.1.0.7 patch, you can find
late-breaking information about Oracle Warehouse Builder in the OWB
readme. See Locating the Oracle Warehouse Builder Readme.
7.7 Back Up the System
Oracle recommends that you create a backup of the Oracle Inventory, Oracle 11g home and Oracle 11g
Database before you install the patch set. If you are planning to apply
this patch to Oracle RAC, ensure that you create a backup of these
components on all nodes before applying the patch.
See also:
Oracle Database Backup and Recovery User's Guide for more information
Note:
In order to downgrade Oracle Enterprise Manager Database Control after
upgrading, save your Database Control files and data before applying the
patchset. Refer to Oracle Database Upgrade Guide for details.
8 Installation Tasks
You can install the patch set either interactively or
noninteractively. See one of the following sections for information
about how to complete the installation:
Note:
If you also plan to apply this patch to Oracle Clusterware, ensure that
you apply the patch to Oracle Clusterware before applying it to Oracle
Database. This is because Oracle Clusterware should always be at the
same or later version as the database.
Installing the Oracle Database 11g Patch Set Interactively
Installing the Oracle Database 11g Patch Set Noninteractively
8.1 Installing the Oracle Database 11g Patch Set Interactively
To install the Oracle Database 11g patch set interactively:
Note:
If you attempt to install this patch set in an Oracle home directory that does not contain an Oracle Database 11g
release 11.1.0.6 installation, Oracle Universal Installer displays a
warning dialog and does not allow the installation to proceed. The
warning dialog displays the following error:
OUI-10091: There are no patches that need to be applied from the patch set Oracle Database 11g Release 1 Patch Set 1
11.1.0.7
To locate the correct Oracle home for the installation, choose Installed Products in Oracle Universal Installer. If Oracle Database 11g
release 11.1.0.6 is installed, its home directory will be included in
the list of Oracle home directories. Select the correct Oracle home and
proceed with the installation.
Log on as a member of the Administrators group to the computer on
which you are going to install Oracle components. If you are installing
on a Primary Domain Controller or a Backup Domain Controller, log on as a
member of the Domain Administrators group.
Start Oracle Universal Installer located in the unzipped area of the patch set. For example, Oracle_patch\setup.exe.
On the Welcome screen, click Next.
In the Specify Home Details screen, select the name of the Oracle home that you want to update, or select the Path that you want to update from the list, then click Next.
Enter a valid email ID with password to configure Oracle Configuration manager.
Note:
If the page is left blank, then Oracle Configuration Manager can still be configured manually using ORACLE_BASE\ORACLE_HOME\ccr\bin\setupCCR after patchset installation.
If Oracle Configuration Manager was configured in 11.1.0.6, then this
page will not be displayed. In this case, Oracle Configuration Manager
would get upgraded to 10.3.0.1.0.
Click Next.
If you are installing the patch set on an Oracle RAC cluster, the
Selected Nodes screen appears. The patch set will be installed on these
nodes. Click Next.
Check for errors, if any, in the Product-Specific Prerequisite Checks and click Next.
On the Summary screen, click Install.
This screen lists all of the patches available for installation.
Note:
If you are applying this patch set to an Oracle Clusterware
installation, then complete all the steps displayed by the Oracle
Universal Installer.
Oracle Clusterware installation instructions are also available in CRS_home\install\readme.txt.
On the End of Installation screen, click Exit, then click Yes to exit from Oracle Universal Installer.
8.2 Installing the Oracle Database 11g Patch Set Noninteractively
To install the Oracle Database 11g patch set noninteractively:
Copy the response file template provided in the response directory where you unpacked the patch set archive file.
Edit the values for all fields labeled as <Value Required> as described by the comments and examples in the template.
To run Oracle Universal Installer, enter a command similar to the following, where response_file_path is the full path to the response file that you edited:
C:\Oracle_patch> setup.exe -silent -responseFile response_file_path
Note:
If you are applying this patch set to an Oracle Clusterware home, then complete all the steps in the CRS_home\install\readme.txt file.
9 Postinstallation Tasks
Review the information in this section before using the upgraded
software. This section lists required and optional postinstallation
tasks, depending on the installation type and the products that you want
to use.
Upgrading Earlier Oracle Database to Oracle Database 11g Release 1 (11.1.0.7)
Upgrading Oracle Database 11g Release 11.1.0.6 to Oracle Database 11g Release 11.1.0.7
Updating Oracle Time Zone Definitions
Oracle Database Extensions for .NET
Configuring Oracle Configuration Manager in a Cloned Oracle Home
Oracle Configuration Manager Behavior in Shared RAC Home
Locating the Oracle Warehouse Builder Readme
Upgrading the Oracle Warehouse Builder Version
Downloading Analytic Workspace Manager and Upgrading OLAP Client Applications
Configuring a User for Oracle Data Mining
Installing 11.1.0.6 Components In an 11.1.0.7 Oracle Home
9.1 Upgrading Earlier Oracle Database to Oracle Database 11g Release 1 (11.1.0.7)
For information about upgrading Oracle Databases from an earlier Oracle Database (Oracle8i, Oracle9i, Oracle Database 10g) or Oracle Database 11g) see Oracle Database Upgrade Guide.
If you are upgrading an Oracle RAC database, refer to Oracle Real Application Clusters Administration Guide as well.
9.2 Upgrading Oracle Database 11g Release 11.1.0.6 to Oracle Database 11g Release 11.1.0.7
See one of the following sections for upgrading an Oracle Database 11g release 11.1.0.6 to Oracle Database 11g release 11.1.0.7:
Upgrading a Release 11.1 Database using Oracle Database Upgrade Assistant
Manually Upgrading a Release 11.1 Database
9.2.1 Upgrading a Release 11.1 Database using Oracle Database Upgrade Assistant
After you install the patch set, you must perform the following steps
on every database associated with the upgraded Oracle home:
Note:
If you do not run the Oracle Database Upgrade Assistant as described in this section, then the following errors are displayed:
ORA-01092: ORACLE instance terminated.
ORA-39700: database must be opened with UPGRADE option.
Log in with administrator privileges.
Set the values for the environment variables ORACLE_HOME, ORACLE_SID and PATH.
For single-instance installations, if you are using Automatic Storage
Management, start the Automatic Storage Management instance.
For Oracle single-instance installations, start the listener as follows:
C:\> lsnrctl start [listener_name]
Note:
If the database has Database Vault configured, then disable Database Vault by following these steps before upgrading:
C:\> cd ORACLE_BASE\ORACLE_HOME\bin
C:\> move oradv11.dll oradv11_backup.dll
For RAC installations, disable Database Vault on each node.
If you are using Automatic Storage Management with RAC, start the ASM
instance on all the nodes before starting Database Upgrade Assistant.
ORACLE_BASE\ORACLE_HOME\bin\srvctl start asm -n node
Ensure that Database Control service is stopped and service control
panel is closed on all the nodes before running Oracle Database Upgrade
Assistant.
Run Oracle Database Upgrade Assistant either in the interactive or noninteractive mode:
Interactive mode:
Start the Oracle Database Upgrade Assistant:
From the Start menu, select Programs, then Oracle - HOME_NAME, then Configuration and Migration Tools and then Database Upgrade Assistant to start the Oracle Database Upgrade Assistant.
Complete the following steps displayed in the Oracle Database Upgrade Assistant screen:
Note:
If you are upgrading a database that has Database Control configured in
non-secure mode, Database Control will run in secure mode after upgrade.
Noninteractive mode:
Enter the following command to upgrade Oracle Database using Oracle Database Upgrade Assistant in noninteractive mode:
C:\> ORACLE_BASE\ORACLE_HOME\bin\dbua -silent -dbname ORACLE_SID
-oracleHome ORACLE_HOME -sysDBAUserName UserName
-sysDBAPassword SYS_password -recompile_invalid_objects true
On the Welcome screen, click Next.
On the Databases screen, select the name of the Oracle Database that you want to update, then click Next.
On the Recompile Invalid Objects screen, select the Recompile the invalid objects at the end of upgrade option, then click Next.
If you did not backup the database earlier, select I would like to take this tool to backup the database on the Backup screen, stipulate the Path, then click Next.
On the Summary screen, check the summary, then click Finish.
On the End of Database Upgrade Assistant's Upgrade Results screen, click Close to exit from Oracle Database Upgrade Assistant.
If you are using the Oracle Recovery Manager catalog, enter the following command:
C:\> rman catalog username/password@aliasRMAN> UPGRADE CATALOG;
Note:
If the database had Database Vault configured before the upgrade, then re-enable Database Vault by following these steps:
C:\> srvctl stop database -d dbnameC:\> cd ORACLE_BASE\ORACLE_HOME\bin
C:\> move oradv11_backup.dll oradv11.dll
C:\> srvctl start database -d dbname
For RAC installations, re-enable Database Vault on each node.
9.2.2 Manually Upgrading a Release 11.1 Database
Complete the following sections to upgrade an Oracle Database 11g release 11.1.0.x to Oracle Database 11g release 11.1.0.7:
Run the Pre-Upgrade Information Tool
Upgrading a Release 11.1 Database
Missing Components When Upgrading
9.2.2.1 Run the Pre-Upgrade Information Tool
If you are upgrading the database manually, then you should analyze it by running the Pre-Upgrade Information Tool.
The Pre-Upgrade Information Tool is a SQL script that ships with
Oracle Database 11.1. Complete the following procedure to run the
Pre-Upgrade Information Tool:
Start the database, either in normal mode or in upgrade mode:
SQL> STARTUP
or
SQL> STARTUP UPGRADE
Set the system to spool results to a log file for later analysis:
SQL> SPOOL upgrade_info.log
Run the Pre-Upgrade Information Tool:
SQL> @ORACLE_BASE\ORACLE_HOME\rdbms\admin\utlu111i.sql
Turn off the spooling of script results to the log file:
SQL> SPOOL OFF
Check the output of the Pre-Upgrade Information Tool in the upgrade_info.log file. The following is an example of the output generated by the Pre-Upgrade Information Tool:
Oracle Database 11.1 Pre-Upgrade Information Tool 06-15-2007 09:14:02
.
**********************************************************************
Database:
**********************************************************************
--> name: ORCL
--> version: 10.2.0.1.0
--> compatible: 10.2.0.1
--> blocksize: 8192
--> timezone file: V2
.
**********************************************************************
Tablespaces: [make adjustments in the current environment]
**********************************************************************
WARNING: --> SYSTEM tablespace is not large enough for the upgrade.
.... currently allocated size: 560 MB
.... minimum required size: 910 MB
.... increase current size by: 350 MB
.... tablespace is NOT AUTOEXTEND ENABLED.
--> UNDOTBS1 tablespace is adequate for the upgrade.
.... minimum required size: 457 MB
.... AUTOEXTEND additional space required: 352 MB
--> SYSAUX tablespace is adequate for the upgrade.
.... minimum required size: 617 MB
.... AUTOEXTEND additional space required: 287 MB
--> TEMP tablespace is adequate for the upgrade.
.... minimum required size: 61 MB
.... AUTOEXTEND additional space required: 41 MB
--> EXAMPLE tablespace is adequate for the upgrade.
.... minimum required size: 69 MB
.
**********************************************************************
Update Parameters: [Update Oracle Database 11.1 init.ora or spfile]
**********************************************************************
WARNING: --> "sga_target" needs to be increased to at least 388 MB
.
**********************************************************************
Renamed Parameters: [Update Oracle Database 11.1 init.ora or spfile]
**********************************************************************
WARNING: --> "plsql_compiler_flags" old value was "INTERPRETED";
new name is "plsql_code_type" new value is "INTERPRETED"
.
**********************************************************************
Obsolete/Deprecated Parameters: [Update Oracle Database 11.1 init.ora or spfile]
**********************************************************************
--> "max_enabled_roles"
--> "remote_os_authent"
--> "background_dump_dest" replaced by "diagnostic_dest"
--> "user_dump_dest" replaced by "diagnostic_dest"
--> "core_dump_dest" replaced by "diagnostic_dest"
.
**********************************************************************
Components: [The following database components will be upgraded or installed]
**********************************************************************
--> Oracle Catalog Views [upgrade] VALID
--> Oracle Packages and Types [upgrade] VALID
--> JServer JAVA Virtual Machine [upgrade] VALID
--> Oracle XDK for Java [upgrade] VALID
--> Oracle Workspace Manager [upgrade] VALID
--> Messaging Gateway [upgrade] VALID
--> OLAP Analytic Workspace [upgrade] VALID
--> OLAP Catalog [upgrade] VALID
--> Oracle Label Security [upgrade] VALID
--> EM Repository [upgrade] VALID
--> Oracle Text [upgrade] VALID
--> Oracle XML Database [upgrade] VALID
--> Oracle Java Packages [upgrade] VALID
--> Oracle interMedia [upgrade] VALID
--> Spatial [upgrade] VALID
--> Data Mining [upgrade] VALID
--> Oracle Ultra Search [upgrade] VALID
--> Expression Filter [upgrade] VALID
--> Rule Manager [upgrade] VALID
--> Oracle Application Express [upgrade] VALID
--> Oracle OLAP API [upgrade] VALID
.
**********************************************************************
Miscellaneous Warnings
**********************************************************************
WARNING: --> Database is using an old timezone file version.
.... Patch the 10.2.0.1.0 database to timezone file version 4
.... BEFORE upgrading the database. Re-run utlu111i.sql after
.... patching the database to record the new timezone file version.
WARNING: --> Database contains stale optimizer statistics.
.... Refer to the 11g Upgrade Guide for instructions to update
.... statistics prior to upgrading the database.
.... Component Schemas with stale statistics:
.... SYS
.... WMSYS
.... CTXSYS
WARNING: --> Database contains INVALID objects prior to upgrade.
.... USER PUBLIC has 7 INVALID objects.
.... USER FLOWS_010600 has 1 INVALID objects.
.... USER SYS has 1 INVALID objects.
WARNING: --> Database contains schemas with objects dependent on network packages.
.... Refer to the 11g Upgrade Guide for instructions to configure Network ACLs.
.... USER WKSYS has dependent objects.
.... USER SYSMAN has dependent objects.
WARNING: --> EM Database Control Repository exists in the database.
.... Direct downgrade of EM Database Control is not supported. Refer to the
.... 11g Upgrade Guide for instructions to save the EM data prior to upgrade.
The following sections describe the output of the Pre-Upgrade Information Tool.
Database
This section displays global database information about the current
database, such as the database name and release number before the
database is upgraded.
Tablespaces
This section displays a list of tablespaces in the current database.
For each tablespace, the tablespace name and minimum required size is
displayed. In addition, a message is displayed if the tablespace is
adequate for the upgrade. If the tablespace does not have enough free
space, then space must be added to the tablespace in the current
database. Tablespace adjustments must be made before the database is
upgraded.
Update/Obsolete/Deprecated Parameters
These sections display a list of initialization parameters in the
parameter file of the current database that should be adjusted before
the database is upgraded. The adjustments must be made to the Oracle
Database 11.1 init.ora or spfile.
Components
This section displays a list of database components that are upgraded or installed when the current database is upgraded.
9.2.2.2 Upgrading a Release 11.1 Database
After you install the patch set, you must perform these steps on every database associated with the upgraded Oracle home.
Note:
If you do not run the catupgrd.sql script as described in this section and you start up a database for normal operation, then the following error will occur:
ORA-01092: ORACLE instance terminated. Disconnection forced
Also, the following error will be in the alert log:
ORA-39700: database must be opened with UPGRADE option .
Note:
If the database has Database Vault configured, then disable Database Vault by following these steps before upgrading:
C:\> cd ORACLE_BASE\ORACLE_HOME\bin
C:\> move oradv11.dll oradv11_backup.dll
For RAC installations, disable Database Vault on each node.
Log in with administrator privileges.
For Oracle RAC installations, start the listener on each node of the cluster as follows:
C:\> ORACLE_BASE\ORACLE_HOME\bin\srvctl start listener -n node
If you are using Automatic Storage Management, start the Automatic Storage Management instance.
For single-instance installations, start the listener as follows:
C:\> lsnrctl start [listener_name]
For single-instance installations, use SQL*Plus to log in to the database as the SYS user with SYSDBA privileges:
C:\> sqlplus /NOLOG
SQL> CONNECT SYS AS SYSDBA
Enter password:SYS_password
Users of single-instance installations now proceed to step 7.
For Oracle RAC installations:
Use SQL*Plus to log in to the database as the SYS user with SYSDBA privileges:
C:\> sqlplus /NOLOG
SQL> CONNECT SYS AS SYSDBA
Enter password: SYS_passwordSQL> STARTUP NOMOUNT
Set the CLUSTER_DATABASE initialization parameter to FALSE:
SQL> ALTER SYSTEM SET CLUSTER_DATABASE=FALSE SCOPE=spfile;
Shut down the database:
SQL> SHUTDOWN
Enter the following SQL*Plus commands:
SQL> STARTUP UPGRADE
SQL> SPOOL patch.log
SQL> @ORACLE_BASE\ORACLE_HOME\rdbms\admin\catupgrd.sql
SQL> SPOOL OFF
Review the patch.log file for errors and inspect the list of components that is displayed at the end of catupgrd.sql script.
This list provides the version and status of each SERVER component in the database.
If necessary, rerun the catupgrd.sql script after correcting any problems.
Restart the database:
SQL> SHUTDOWN IMMEDIATE
SQL> STARTUP
Run the utlrp.sql script to recompile all invalid PL/SQL
packages now instead of when the packages are accessed for the first
time. This step is optional but recommended.
SQL> @ORACLE_BASE\ORACLE_HOME\rdbms\admin\utlrp.sql
Note:
When the 11.1.0.7 patch set is applied to an Oracle Database 11g Standard Edition database, there may be 53 invalid objects after the utlrp.sql script runs. These objects belong to the unsupported components and do not affect the database operation.
Ignore any messages indicating that the database contains invalid recycle bin objects similar to the following:
BIN$4lzljWIt9gfgMFeM2hVSoA==$0
Run the following command to check the status of all the components after the upgrade:
SQL> SELECT COMP_NAME, VERSION, STATUS FROM SYS.DBA_REGISTRY;
In the output of the preceding command, the status of all the components should be VALID for a successful upgrade.
If you are using the Oracle Recovery Manager catalog, enter the following command:
C:\> rman catalog username/password@alias RMAN> UPGRADE CATALOG;
For Oracle RAC installations:
Set the CLUSTER_DATABASE initialization parameter to TRUE:
SQL> ALTER SYSTEM SET CLUSTER_DATABASE=TRUE SCOPE=spfile;
Restart the database:
SQL> SHUTDOWN IMMEDIATE
SQL> STARTUP
Start the database as follows:
C:\> ORACLE_BASE\ORACLE_HOME\bin\srvctl start database -d dbname
To configure and secure Enterprise Manager follow these steps:
Note:
If you are upgrading a database that has Database Control configured in
non-secure mode, Database Control will run in secure mode after the
upgrade.
Note:
If the database had Database Vault configured before the upgrade, then re-enable Database Vault by following these steps:
C:\> cd ORACLE_BASE\ORACLE_HOME\bin
C:\> move oradv11_backup.dll oradv11.dll
For RAC installations, re-enable Database Vault on each node.
Make sure that the database and the listener are operational.
In the case of a single instance, execute:
emca -upgrade db
In the case of Oracle Real Application Clusters (RAC), execute:
emca -upgrade db -cluster
9.2.2.3 Missing Components When Upgrading
When you upgrade Oracle Database 10g Release 2 (10.2.0.4) to Oracle Database 11g Release 1 (11.1.0.7), the diagnostics of the pre-upgrade utility script utlu111.sql may indicate that some database components on the 11g Examples media should be installed. You should install these components from the Oracle Database 11g Release 1 (11.1) Examples media before applying this patch set. If the catupgrd.sql
script cannot upgrade a SERVER component because it was not installed
from the Examples media, then the status of the SERVER component in the patch.log file is reported as NO SCRIPT.
Note:
If the pre-upgrade script indicates the Server JAVA Virtual Machine's
JAccelerator (NCOMP) or Oracle Multimedia Image Accelerator should be
installed, but they are not installed before applying the patch set,
then the patch.log file contains the status of their parent components as successfully upgraded to Oracle Database 11g Release 1 (11.1.0.7) even though these components are still missing.
If you find any component, which was identified as missing by the
pre-upgrade utility script, was not installed before running the catupgrd.sql script, then install the missing component from the Examples media and run the catupgrd.sql script again.
9.3 Updating Oracle Time Zone Definitions
Based on the result you had in Section 7.5, "Update Oracle Time Zone Definitions" regarding the DST (Oracle time zone definitions):
If the DST version was 4, no action is required.
If the DST version was higher than 4, reapply the version of DST patches as described in OracleMetaLink document 568125.1, Actions for the DSTv4 update in the 11.1.0.7 patchset.
If the DST version was lower than 4, restore TSTZ data from backup
(if any) after performing the Postinstallation Tasks. For more
information, see OracleMetaLink document 568125.1, Actions for the DSTv4 update in the 11.1.0.7 patchset.
9.4 Oracle Database Extensions for .NET
If you use Oracle Database Extensions for .NET, then complete the following steps and start the OracleORACLE_HOMEClrAgent service:
Use SQL*Plus to deploy the DBMSClr.plb package:
C:\> sqlplus /NOLOG
SQL> CONNECT SYS AS SYSDBA
Enter password:SYS_PasswordSQL> @ORACLE_BASE\ORACLE_HOME\rdbms\admin\DBMSClr.plb
Start the OracleORACLE_HOMEClrAgent service:
From the Start menu, select Programs, then Administrative Tools and then Services to open the Services control panel then select OracleORACLE_HOMEClrAgent and click Start.
9.5 Configuring Oracle Configuration Manager in a Cloned Oracle Home
If Oracle Configuration Manager was configured using Oracle Universal
Installer 11.1.0.7.0 and if 11.1.0.7.0 is cloned, then follow these
steps in the cloned Oracle home:
Run the following command from ORACLE_BASE\ORACLE_HOME\ccr\state.
Run the following command from ORACLE_BASE\ORACLE_HOME\ccr\state.
Run these commands from ORACLE_BASE\ORACLE_HOME\ccr\bin.
Run this command from ORACLE_BASE\ORACLE_HOME\ccr\bin, and provide the proper credentials.
If Oracle Configuration Manager was manually configured in 11.1.0.7 using setupCCR, and if 11.1.0.7 is cloned, then follow these steps in the cloned Oracle home:
Delete all the subdirectories of the ORACLE_BASE\ORACLE_HOME\ccr\hosts directory to remove the previously configured hosts.
Run the following command from ORACLE_BASE\ORACLE_HOME\ccr\bin:
> configCCR -a
If you have installed Oracle Configuration Manager in the original
Oracle home but have not configured it, then run the following command
in the cloned Oracle home to configure it:
> setupCCR
9.6 Oracle Configuration Manager Behavior in Shared RAC Home
If Oracle Configuration Manager was configured in 11.1.0.6, and the
11.1.0.7 patchset is applied from any of the nodes belonging to the
cluster, Oracle Configuration Manager will be configured only on the
first node. You should not run ORACLE_BASE\ORACLE_HOME\ccr\bin\emCCRstatus on any of the remaining nodes of the cluster where RAC is installed in shared mode.
If Oracle Configuration Manager is configured using 11.1.0.7 Oracle
Universal Installer, then it only gets configured on the nodes from
where the patchset is applied.
9.7 Locating the Oracle Warehouse Builder Readme
For late-breaking information about Oracle Warehouse Builder, see the
Oracle Warehouse Builder Readme, which is installed with the database
software under ORACLE_BASE\ORACLE_HOME\owb\doc\ReadMe.htm.
9.8 Upgrading the Oracle Warehouse Builder Version
After upgrade to 11.1.0.7.0, DBA_REGISTRY continues to show version 11.1.0.6.0 for Oracle Warehouse Builder. Follow the steps described in $ORACLE_HOME/owb/doc/Readme.htm to manually upgrade the Oracle Warehouse Builder version from 11.1.0.6.0 to 11.1.0.7.0.
9.9 Downloading Analytic Workspace Manager and Upgrading OLAP Client Applications
Analytic Workspace Manager 11.1.0.7 is available for download on the OracleMetaLink website:
http://metalink.oracle.com
To download Analytic Workspace Manager 11.1.0.7:
Log on to OracleMetaLink.
Click Advanced at the top of the OracleMetaLink page.
Enter 7420490.1 in the Document ID field, then click Submit.
Follow the instructions in Document 7420490.1.
With AWM 11.1.0.7, you can create standard 11.1 analytic workspaces
or 10.2 style analytic workspaces. To create a 10.2 style analytic
workspace, choose the 10.2 cube type when creating a new analytic
workspace.
If you wish to use existing OLAP 11.1.0.6.0 or 11.1.0.6.0A client
applications with the 11.1.0.7 database, you must upgrade the run-time
OLAP API JAVA code to 11.1.0.7. After installing the 11.1.0.7.0 RDBMS
patch, locate the olap_api.jar file in ORACLE_BASE\ORACLE_HOME\olap\api\lib
. Insert this newer 11.1.0.7 jar file in your application's JAVA class
path, and omit any previous pointers to the 11.1.0.6.0 or 11.1.0.6.0A
jar file.
9.10 Configuring a User for Oracle Data Mining
Demo programs that illustrate the Data Mining APIs (PL/SQL and Java) are installed with Oracle Database Examples. Two scripts, dmsh.sql and dmshgrants.sql, must be run prior to using the demo programs.
dmshgrants.sql assigns the privileges needed to use the demo programs. After upgrade to 11.1.0.7.0, the syntax for invoking dmshgrants.sql is:
@ ORACLE_BASE\ORACLE_HOME\RDBMS\demo\dmshgrants dmuser_name
See Oracle Data Mining Administrator's Guide for details about dmsh.sql, dmshgrants.sql, and the Oracle Data Mining demo programs.
9.11 Installing 11.1.0.6 Components In an 11.1.0.7 Oracle Home
If you want to install or reinstall additional components from
11.1.0.6 (for example, Oracle Spatial) into an 11.1.0.7 Oracle Home, use
the 11.1.0.7 Oracle Universal Installer found in ORACLE_BASE\ORACLE_HOME\oui\bin.
10 Removing the Patch Set Software
The catdwgrd.sql script restores the Oracle Database release 11.1 installation that you backed up before applying the patch set. The catdwgrd.sql script is run in the 11.1.0.7 Oracle home to perform the necessary downgrade actions. After the 11.1.0.x release is restored, the catrelod.sql script is run from 11.1.0.x Oracle home to reload the 11.1.0.x release packages and views.
See one of the following sections for information about how to remove
the patch set software based on the Oracle Database installation type:
Removing the Patch Set Software for Single Instance Installation
Removing the Patch Set Software for Oracle RAC Installation
Note:
Oracle Clusterware downgrade is not supported.
You can run a higher version of Oracle Clusterware software with a lower version of Oracle Database.
10.1 Removing the Patch Set Software for Single Instance Installation
Perform the following steps for removing the 11.1.0.7 patch set:
Use SQL*Plus to log in to the database as the SYS user with SYSDBA privileges:
C:\> sqlplus /NOLOG
SQL> CONNECT SYS AS SYSDBA
Enter password: SYS_passwordSQL> SHUTDOWN IMMEDIATE
SQL> EXIT
Take a backup of the following files in the Oracle home directory:
ORACLE_BASE\ORACLE_HOME\rdbms\admin\catrelod.sqlORACLE_BASE\ORACLE_HOME\network\admin\tnsnames.ora
Note:
If the database has Database Vault configured, then disable Database Vault by following these steps before running catdwgrd.sql:
C:\> cd ORACLE_BASE\ORACLE_HOME\bin
C:\> move oradv11.dll oradv11_backup.dll
Enter the following SQL*Plus commands:
C:\> cd ORACLE_BASE\ORACLE_HOMEC:\> sqlplus /NOLOG
SQL> CONNECT SYS AS SYSDBA
Enter password:SYS_passwordSQL> STARTUP DOWNGRADE
SQL> DROP USER SYSMAN CASCADE;
SQL> SPOOL downgrade.out
SQL> @ORACLE_BASE\ORACLE_HOME\rdbms\admin\catdwgrd.sql
SQL> SPOOL OFF
SQL> SHUTDOWN IMMEDIATE
SQL> EXIT
Review the downgrade.out file for errors.
Remove Oracle Configuration Manager if it was configured with
11.1.0.7. If it was configured with 11.1.0.6, do not remove Oracle
Configuration Manager.
Follow these steps to remove the 11.1.0.7-configured Oracle Configuration Manager.
Stop the OraclehomenameConfigurationManager service. You can do this by executing the following command:
C:\>ORACLE_BASE\ORACLE_HOME\ccr\bin\emCCR stop
or you can stop the service from the Service window of Windows Control Panel.
After stopping the OraclehomenameConfigurationManager service, run the following commands:
C:\>ORACLE_BASE\ORACLE_HOME\ccr\bin\deployPackages -d
ORACLE_BASE\ORACLE_HOME\ccr\inventory\core.jar
C:\>rmdir /s/q ORACLE_BASE\ORACLE_HOME\ccr
Restore the Oracle 11g installation and central inventory that you backed up before applying the patch set.
Note:
If the database that you backed up had Database Vault configured, then
follow these steps to disable Database Vault before running catrelod.sql:
C:\> cd ORACLE_BASE\ORACLE_HOME\bin
C:\> move oradv11.dll oradv11_backup.dll
After restoring the original Oracle home, copy the saved version of catrelod.sql into the restored ORACLE_BASE\ORACLE_HOME\rdbms\admin directory and the saved version of tnsnames.ora into the restored ORACLE_BASE\ORACLE_HOME\network\admin\tnsnames.ora file.
Perform the following steps:
Start the service OracleServiceSID from the Control Panel by selecting Administrative Tools and then Services.
Enter the following SQL*Plus commands:
C:\> sqlplus /NOLOG
SQL> CONNECT SYS AS SYSDBA
Enter password:SYS_PasswordSQL> STARTUP DOWNGRADE
SQL> SPOOL catrelod.out
SQL> @ORACLE_BASE\ORACLE_HOME\rdbms\admin\catrelod.sql
SQL> SPOOL OFF
SQL> SHUTDOWN IMMEDIATE
Review the catrelod.out file for errors.
Note:
After reloading the 11.1.0.6 release, the version number for Oracle OLAP
Analytic Workspace remains at 11.1.0.7, although the downgrade process
is successful. This issue is tracked with Oracle bug 6975997.
Note:
If the database had Database Vault configured prior to the upgrade, then re-enable Database Vault by following these steps:
C:\> cd ORACLE_BASE\ORACLE_HOME\bin
C:\> move oradv11_backup.dll oradv11.dll
For RAC installations, re-enable Database Vault on each node.
Start the database and recompile the remaining invalid objects:
SQL> STARTUP
SQL> @ORACLE_BASE\ORACLE_HOME\rdbms\admin\utlrp.sql
Cross-check the status of installed components with the following script:
SQL> SELECT COMP_NAME, VERSION, STATUS FROM SYS.DBA_REGISTRY;
Restore the original Enterprise Manager Database Control. Refer to Oracle Database Upgrade Guide for details.
10.2 Removing the Patch Set Software for Oracle RAC Installation
Perform the following steps for removing the patch set from the 11.1.0.7 patch release:
Use SQL*Plus to log in to the database as the SYS user with SYSDBA privileges:
C:\> sqlplus /NOLOG
SQL> CONNECT SYS AS SYSDBA
Enter password:SYS_password
Set the CLUSTER_DATABASE initialization parameter to FALSE:
Note:
If the system uses an initialization parameter file, change the value of the CLUSTER_DATABASE initialization parameters to TRUE in the initialization parameter file (initsid.ora).
SQL> ALTER SYSTEM SET CLUSTER_DATABASE=FALSE SCOPE=spfile;
Exit SQL*Plus and shut down the database:
C:\> ORACLE_BASE\ORACLE_HOME\bin\srvctl stop database -d db_name
Take a backup of the following files in 11.1.0.7 Oracle home directory:
\ORACLE_BASE\ORACLE_HOME\rdbms\admin\catrelod.sql
\ORACLE_BASE\ORACLE_HOME\network\admin\tnsnames.ora
Note:
If the database has Database Vault configured, then disable Database Vault by following these steps before running catdwgrd.sql:
C:\> cd ORACLE_BASE\ORACLE_HOME\bin
C:\> move oradv11.dll oradv11_backup.dll
Disable Database Vault on each node.
Enter the following SQL*Plus commands:
C:\> sqlplus /NOLOG
SQL> CONNECT SYS AS SYSDBA
Enter password:SYS_passwordSQL> STARTUP DOWNGRADE
SQL> DROP USER SYSMAN CASCADE;
SQL> SPOOL catdwgrd.out
SQL> @ORACLE_BASE\ORACLE_HOME\rdbms\admin\catdwgrd.sql
SQL> SPOOL OFF
SQL> SHUTDOWN IMMEDIATE
SQL> EXIT
Complete the following steps to stop all Oracle Database services:
Stop all node applications running on the node. Enter the following command, where node is the name of the node where the applications are running:
C:\> ORACLE_BASE\ORACLE_HOME\bin\srvctl stop nodeapps -n node
For Automatic Storage Management instances, perform the following step:
C:\> ORACLE_BASE\ORACLE_HOME\bin\srvctl stop asm -n node
Stop the services OracleServiceinst_name and OracleDBConsoleinst_name from the Control Panel by selecting Administrative Tools and then Services.
Remove Oracle Configuration Manager if it was configured with
11.1.0.7. If it was configured with 11.1.0.6, do not remove Oracle
Configuration Manager.
Follow these steps to remove the 11.1.0.7-configured Oracle Configuration Manager.
Stop the OraclehomenameConfigurationManager service. You can do this by executing the following command:
C:\>ORACLE_BASE\ORACLE_HOME\ccr\bin\emCCR stop
or you can stop the service from the Service window of Windows Control Panel.
After stopping the OraclehomenameConfigurationManager service, run the following commands:
C:\>ORACLE_BASE\ORACLE_HOME\ccr\bin\deployPackages -d
ORACLE_BASE\ORACLE_HOME\ccr\inventory\core.jar
C:\>rmdir /s/q ORACLE_BASE\ORACLE_HOME\ccr
Restore the Oracle 11g installation and central inventory that you backed up before applying the patch set.
Note:
If the database that you backed up had Database Vault configured, then
follow these steps to disable Database Vault before running catrelod.sql:
C:\> cd ORACLE_BASE\ORACLE_HOME\bin
C:\> move oradv11.dll oradv11_backup.dll
Disable Database Vault on each node.
After restoring the original Oracle home, copy the saved version of catrelod.sql into the restored ORACLE_HOME\rdbms\admin directory and the saved version of tnsnames.ora into the restored ORACLE_HOME\network\admin\tnsnames.ora file.
Start the OracleServiceSID service from the Control Panel by selecting Administrative Tools and then Services.
Enter the following SQL*Plus commands:
C:\> sqlplus /NOLOG
SQL> CONNECT SYS AS SYSDBA
Enter password:SYS_PasswordSQL> STARTUP DOWNGRADE
SQL> SPOOL catrelod.out
SQL> @ORACLE_BASE\ORACLE_HOME\rdbms\admin\catrelod.sql
SQL> SPOOL OFF
SQL> SHUTDOWN IMMEDIATE
Start the listener, gsd and ons processes:
Start the node applications by entering the following command, where node is the name of the node where the applications are running:
C:\> ORACLE_BASE\ORACLE_HOME\bin\srvctl start nodeapps -n node
For Automatic Storage Management instances, perform the following step:
C:\> ORACLE_BASE\ORACLE_HOME\bin\srvctl start asm -n node
Start the service OracleServiceinst_name from the Control Panel by selecting Administrative Tools and then Services.
Review the catrelod.out file for errors.
Note:
After reloading the 11.1.0.6 release, the version number for Oracle OLAP
Analytic Workspace remains at 11.1.0.7, although the downgrade process
is successful. This issue is tracked with Oracle bug 6975997.
Start the database and recompile the remaining invalid objects:
SQL> STARTUP
SQL> @ORACLE_BASE\ORACLE_HOME\rdbms\admin\utlrp.sql
Cross-check the status of installed components with the following script:
SQL> SELECT COMP_NAME, VERSION, STATUS FROM SYS.DBA_REGISTRY;
Set the CLUSTER_DATABASE initialization parameter to TRUE:
Note:
If the system uses an initialization parameter file, change the value of the CLUSTER_DATABASE initialization parameters to TRUE in the initialization parameter file (initsid.ora).
SQL> ALTER SYSTEM SET CLUSTER_DATABASE=TRUE SCOPE=spfile;
SQL> SHUTDOWN
SQL> EXIT
Start the database:
Start the service OracleServiceinst_name from the Control Panel by selecting Administrative Tools and then Services.
Start the database by entering the following command:
C:\> ORACLE_BASE\ORACLE_HOME\bin\srvctl start database -d ORACLE_SID
Restore the original Enterprise Manager Database Control. Refer to Oracle Database Upgrade Guide for details.
Note:
If the database had Database Vault configured prior to the upgrade, then re-enable Database Vault by following these steps:
C:\> cd ORACLE_BASE\ORACLE_HOME\bin
C:\> move oradv11_backup.dll oradv11.dll
Re-enable Database Vault on each node.
Note:
Option for removing Oracle Clusterware patch set is not available in 11.1.0.7. This issue is tracked with Oracle bug 5598010.
11 Reinstalling the Patch Set Software
If necessary, you can reinstall a patch set that has been applied to an Oracle Database 11g installation. You must reinstall the patch set interactively.
To reinstall the patch set:
Make sure you complete the same set of preinstallation tasks that you performed when you installed the patch set initially:
Log on as a member of the Administrators group to the computer on
which to install Oracle components. Log on as a member of the Domain
Administrators group if you are installing on a Primary Domain
Controller or a Backup Domain Controller.
Unzip the downloaded patch set file into a new directory.
Shut down the existing Oracle server instance with normal or immediate priority. For example, shut down all instances cleanly.
Stop all listener, agent, and other services running in or against the Oracle home in which you are installing.
Start Oracle Universal Installer in the same manner that you did when
installing the patch set initially. You may only reinstall a patch set
by running Oracle Universal Installer in interactive mode.
The Welcome screen appears. If you are not sure of the name of the Oracle home, click Installed Products to determine the name of the Oracle home that you want to upgrade. Click Next.
In the Specify Home Details screen, select the name of the Oracle home that you want to update, or select the Path that you want to update from the list, then click Next.
If you are installing the patch set on an Oracle RAC cluster, click Next when the Selected Nodes screen appears.
The Available Product Component screen appears. This screen contains a
list of all components that have been patched by the original patch set
installation. These components are grayed out, indicating they cannot
be selected for installation.
Expand the nodes for each component listed in the tree to display the patch that corresponds to each component.
Select the patches that you want to install. To select all the patches, click Select All.
When you select a patch, the Install Status column changes to Reinstall.
Repeat the process for each patch bundled in the patch set, then click Next.
On the Summary screen, verify the list of patches to be reinstalled, then click Install.
On the End of Installation screen, click Exit, then click Yes to exit from Oracle Universal Installer.转载于:https://my.oschina.net/u/1412027/blog/353399
512
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
