DevOps让系统管理更轻松。
分类： Oracle
2009-11-15 16:19:28
10g Release 2 (10.2.0.3) Patch Set 2 for Linux x86
February 2007
These patch set notes accompany the Oracle Database release 10.2.0.3 patch set. This document contains the following sections:
This document may be updated after release. To check for updates to this document, see document 316900.1 on the OracleMetalink Web site:
To locate document 316900.1:
Log on to OracleMetalink.
Click Advanced at the top of the OracleMetalink page.
Enter 316900.1 in the Document ID field, then click Submit.
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 10.2.0.3 patch set to the following Oracle Database 10g release 2 installations:
Oracle Database
Oracle Real Application Clusters
Oracle Database Client
Oracle Database Companion CD
Oracle Clusterware
Oracle Database Vault 10.2.0.2
For a list of products included in this patch set, see the section.
This patch set includes Oracle Universal Installer release 10.2.0.3, which is also installed when you install this patch set. This is to ensure that your Oracle home can be patched in the future. You should not use the 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 10g (10.2.0.x) installation.
There are two documents related to this release of the Oracle Database patch set:
Oracle Database Patch Set Notes, 10g release 2 (10.2.0.3) Patch Set 2 for Linux x86 (this document)
Oracle Database List of Bugs Fixed, 10g release 2 (10.2.0.3) Patch Set 2
Both of these documents are included with the patch set. In addition, they are available from document 316900.1, ALERT: Oracle 10g release 2 (10.2) Support Status and Alerts on the OracleMetalink Web site:
To locate document 316900.1:
Log on to OracleMetalink.
Click Advanced at the top of the OracleMetalink page.
Enter 316900.1 in the Document ID field, then click Submit.
The following sections describe the contents of the Oracle Database Patch Set Notes and the Oracle Database List of Bugs Fixed.
Oracle Database Patch Set Notes, 10g Release 2 (10.2.0.3) Patch Set 2 for Linux x86
This document provides:
System requirements and information about how to install, reinstall or remove the patch set
A list of all bugs fixed to date that are specific to Oracle Database for Linux x86
A list of known issues relating to Oracle Database on Linux x86
Oracle Database List of Bugs Fixed, 10g Release 2 (10.2.0.3) Patch Set 2
The List of Bugs Fixed is a list of all generic bugs related to Oracle Database that have been fixed to date.
The following are the system requirements for this patch set:
Operating System
SUSE Linux Enterprise Server 9
Red Hat Enterprise Linux AS/ES 3
Red Hat Enterprise Linux AS/ES 4
Enterprise Linux 4
Asianux 2.0
Oracle Database 10g (10.2.0.1) or later
Complete the following preinstallation tasks before installing the patch set:
Review the information in the following sections. If any of the issues apply to your Oracle installation, follow the instructions before installing the patch set.
If you are an Oracle E-Business Suite customer and you want to upgrade your 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:
Before applying this patch set to an Oracle Database 10.2.0.x installation that uses one or more physical or logical standby databases, review the following OracleMetalink documents:
For information about physical standby databases, review document 278641.1.
For information about logical standby databases, review document 278643.1.
These documents are available on the OracleMetaLink Web site:
If any of the databases use Java Virtual Machine or Oracle interMedia, then install the Oracle Database 10g Products installation type from the Oracle Database 10g Companion CD before installing the 10.2.0.3 patch set. For information about installing the Oracle Database 10g Products installation type from the Companion CD, see the Oracle Database Companion CD Installation Guide for your platform. This installation type includes the Natively Compiled Java Library files to improve Java performance. If you do not install the Natively Compiled Java Library files, the ORA-29558:JAccelerator(NCOMP)not installed error occurs when a database that uses Java Virtual Machine is upgraded to the patch release.
The Oracle Clusterware software must be at the same or newer level as the Oracle software in the Oracle RAC Oracle home. Therefore, you should always upgrade Oracle Clusterware before you upgrade Oracle RAC.
Complete the steps in this section before upgrading Oracle Database Vault from 10.2.0.2 to 10.2.0.3 or downgrading Oracle Database Vault from 10.2.0.3 to 10.2.0.2:
Re-create and replace the password file, in order to log in to an Oracle Database Vault instance as a SYS user with SYSDBA privilege:
$ orapwd file=$ORACLE_HOME/dbs/orapwsid password=syspasswd force=y nosysdba=n
|
Note: TheSYS connection as SYSDBA is disabled in a default Oracle Database Vault installation. Without enabling SYSDBA, you cannot unlock DVSYS in Step that follows. |
Shut down the database:
For Oracle RAC:
$ srvctl stop database -d db_name -c "SYS/SYS_password as SYSDBA"
For Single Instance:
SQL> CONNECT SYS/ AS SYSOPER
Enter password: SYS_password
SQL> SHUTDOWN
Re-link the Oracle database software with dv_off:
|
Note: For Oracle RAC, you must run the following commands on all the nodes. |
$ cd $ORACLE_HOME/rdbms/lib $ make -f ins_rdbms.mk dv_off $ cd $ORACLE_HOME/bin $ relink oracle
Start the database:
For Oracle RAC:
$ srvctl start database -d db_name -c "SYS/SYS_password as SYSDBA"
For Single Instance:
$ sqlplus /nolog
SQL> CONNECT SYS/SYS_password AS SYSDBA
SQL> STARTUP
Unlock the DVSYS account and set the password:
SQL> ALTER USER DVSYS ACCOUNT UNLOCK; SQL> ALTER USER DVSYS IDENTIFIED BY DVSYS;
Disable the Oracle Database Vault triggers:
SQL> CONNECT DVSYS/DVSYS; SQL> ALTER TRIGGER DV_BEFORE_DDL_TRG DISABLE; SQL> ALTER TRIGGER DV_AFTER_DDL_TRG DISABLE;
To apply this patch set, Oracle OLAP users should ensure that the base release is the Enterprise Edition of 10.2.0.x 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 your 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:
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.
Oracle OLAP users upgrading the Oracle database to 10.2.0.3.0 must upgrade the Analytic Workspace Manager client as well. This new 10.2.0.3.0 Analytic Workspace Manager can be found on Oracle Technology Network and on OracleMetaLink by referencing Oracle OLAP patch 5581559.
This is not a complete software distribution. You must install it in an existing Oracle Database 10g Oracle home. To identify Oracle home directories, view the /etc/oratab file.
If you are installing this patch set on an existing Oracle Real Applications Cluster 10g release 10.2.0.x installation, you must run Oracle Universal Installer from the same node from which the Oracle Database software was installed.
Before installing this patch set in a production environment, review document 316900.1, ALERT: Oracle 10g release 2 (10.2) Support Status and Alerts, available on the OracleMetaLink Web site:
To locate this document:
Log on to OracleMetalink.
Click Advanced at the top of the OracleMetalink page.
Enter 316900.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.
To download and extract the patch set installation software:
Download the p5337014_10203_LINUX.zip patch set installation archive to a directory that is not the Oracle home directory or under the Oracle home directory.
Enter the following command to unzip and extract the installation files:
$ unzip p5337014_10203_LINUX.zip
The 10.2.0.3 patch set includes an update to the Oracle time zone definitions. The 10.2.0.3 patch set updates the standard version of the Oracle 10.2 time zone definitions version-2 to version-3. This version of the time zone definitions includes the changes to daylight saving time in the USA in 2007, and many other updates.
A list of updated time zones in version-3 of these definitions are available from document 412160.1 on the OracleMetalink Web site:
To locate document 412160.1:
Log on to OracleMetalink.
Click Advanced at the top of the OracleMetalink page.
Enter 412160.1 in the Document ID field, then click Submit.
Perform the following actions to ensure that time zone data affected by the changes in these time zones are updated appropriately:
Download the patch 5601428 from OracleMetalink.
Install the patch. The script utltzuv2.sql is installed into the $ORACLE_HOME/rdbms/admin directory.
Run utltzuv2.sql to check the data of datatype TIMESTAMP WITH TIME ZONE (TSTZ). The output of this script is a results table which highlights the affected columns.
Refer to the instructions in the utltzuv2.sql or OracleMetalink note 396671.1: Usage of utltzuv2.sql before updating time zone files in Oracle 10, to evaluate results and if required save the existing TSTZ data. If no data was found, no further actions are needed.
|
Note: If you saved the existingTSTZ data, you need to complete under the section to view the change. |
To locate document 396671.1 on the OracleMetalink Web site:
To locate document 396671.1:
Log on to OracleMetalink.
Click Advanced at the top of the OracleMetalink page.
Enter 396671.1 in the Document ID field, then click Submit.
|
Note: If you have previously installed a patch for bug 4689959, the database is already usingversion 3 of the Oracle time zone definitions. In this case, the script in step will display the following message: TIMEZONE data is consistent with the latest version 3 transition rules, No need to validate TIMEZONE data. In this case, no further action is needed and step can be skipped.
If you have previously installed a patch for bug 5632264, the database is already using |
Enter the following commands to set the ORACLE_HOME and ORACLE_SID environment variables:
Bourne, Bash, or Korn shell:
$ ORACLE_HOME=oracle_home $ ORACLE_SID=sid $ export ORACLE_HOME ORACLE_SID
C shell:
% setenv ORACLE_HOME oracle_home % setenv ORACLE_SID sid
In these examples, oracle_home is the Oracle home directory where the Oracle Database 10g installation that you want to upgrade is installed, and sid is the SID of the database that you want to upgrade.
Enter the following commands to set the ORACLE_HOME and ORACLE_SID environment variables:
Bourne, Bash, or Korn shell:
$ ORACLE_HOME=Oracle_home $ ORACLE_SID=sid $ export ORACLE_HOME ORACLE_SID
C shell:
% setenv ORACLE_HOME Oracle_home % setenv ORACLE_SID sid
In these examples, Oracle_home is the Oracle home directory where the Oracle Database 10g installation that you want to upgrade is installed, and sid is the system identifier of the database that you want to upgrade. For Oracle RAC installations, sid is generally the sid prefix and the instance number. For example, ORCL1.
Go to the following sections based on your Oracle Database installation type:
|
See also: Appendix F, "How to Stop Processes in an Existing Oracle Real Application Clusters Database, and How to Perform Oracle Clusterware Rolling Upgrades" of Oracle Database Oracle Real Application Clusters Installation Guide. |
Shut down the following Oracle Database 10g processes in the order specified before installing the patch set:
Shut down all processes in the Oracle home that might be accessing a database, for example Oracle Enterprise Manager Database Control or iSQL*Plus:
$ emctl stop dbconsole $ isqlplusctl stop
|
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 database instances running in the Oracle home directory, where you need to install the patch set.
Shut down all listeners running in the Oracle home directory, where you need to install the patch set.
If there is an Automatic Storage Management instance present, then enter the following command to set the values for the environment variables $ORACLE_HOME and $ORACLE_SID:
Bourne, Bash, or Korn shell:
$ export ORACLE_SID=+ASM $ export ORACLE_HOME=ASM_HOME
C shell:
% setenv ORACLE_SID +ASM % setenv ORACLE_HOME ASM_HOME
Enter the following command to shut down the Automatic Storage Management instance:
$ sqlplus /NOLOG
SQL> CONNECT SYS/SYS_password AS SYSDBA
SQL> SHUTDOWN IMMEDIATE
For Automatic Storage Management, to shut down the Oracle Cluster Synchronization Services daemon enter the following command as the root user:
# $ORACLE_HOME/bin/crsctl stop crs
This section contains the following information:
By default, Oracle supports rolling upgrade for Oracle Clusterware. Complete the following steps only on one node:
Shut down all processes in the Oracle home on the node that might be accessing a database, for example Oracle Enterprise Manager Database Control or iSQL*Plus:
$ emctl stop dbconsole $ isqlplusctl stop
|
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 services in the Oracle home on the node that might be accessing a database:
$ srvctl stop service -d db_name [-s service_name_list [-i inst_name]]
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:
$ 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:
$ srvctl stop asm -n node
Stop all node applications on the node on which you intend to perform the rolling upgrade. To stop node applications running on a node, log in as the root user and enter the following command, where node is the name of the node where the applications are running:
# srvctl stop nodeapps -n node
Perform the steps mentioned in .
|
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:
|
To upgrade the rest of the nodes, go to the next node and perform Steps to and then log in as the root user and perform the following steps:
Enter the following command to shut down the Oracle Clusterware:
# CRS_home/bin/crsctl stop crs
Run the root102.sh script to automatically start the Oracle Clusterware on the patched node:
# CRS_home/install/root102.sh
|
Note: Rolling upgrade is not supported on Shared Oracle home. |
For non rolling upgrade, Oracle Clusterware needs to be shut down completely.
Complete the following steps:
|
Note: You must perform these steps in the order listed. |
Shut down all processes in the Oracle home on each node that might be accessing a database, for example Oracle Enterprise Manager Database Control or iSQL*Plus:
$ emctl stop dbconsole $ isqlplusctl stop
|
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 services in the Oracle home on each node that might be accessing a database:
$ srvctl stop service -d db_name [-s service_name_list [-i inst_name]]
Shut down all Oracle RAC instances on all cluster nodes by entering the following command where db_name is the name of the database:
$ srvctl stop database -d db_name
If Automatic Storage Management instance is present, 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:
$ srvctl stop asm -n node
Stop all node applications on all cluster nodes by entering the following command as the root user, where node is the name of the node where the applications are running:
# srvctl stop nodeapps -n node
Shut down the Oracle Clusterware processes by entering the following command on all nodes as the root user:
# CRS_home/bin/crsctl stop crs
Complete the steps mentioned in .
|
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 Database 10g processes before installing the patch set:
Shut down all processes in the Oracle home on each node that might be accessing a database, for example Oracle Enterprise Manager Database Control or iSQL*Plus:
$ emctl stop dbconsole $ isqlplusctl stop
|
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 services in the Oracle home on each node that might be accessing a database:
$ srvctl stop service -d db_name [-s service_name_list [-i inst_name]]
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:
$ srvctl stop database -d db_name
If Automatic Storage Management instance is present, then shut down all Automatic Storage Management instances on all nodes. 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:
$ 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:
$ srvctl stop listener -n node [-l listenername]
|
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 10.2.0.1 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. |
Oracle recommends that you create a backup of the Oracle Database 10g installation before you install the patch set.
|
See also: Oracle Database Backup and Recovery User's Guide for more information. |
You can install the patch set either interactively or noninteractively. See one of the following sections for information about how to complete the installation:
To install the patch set interactively, see the section.
To install the patch set noninteractively, see the section.
To install the Oracle Database 10g patch set interactively:
|
Note: If you attempt to install this patch set in an Oracle home directory that does not contain an Oracle Database 10g release 10.2.0.1 or 10.2.0.2 installation, Oracle Universal Installer displays a warning dialog with the following error:OUI-10091: There are no patches that need to be applied from the patch set Oracle Database 10g Release 2 Patch Set 2
10.2.0.3
The Oracle Universal Installer does not allow the installation to proceed. Click OK, then click Cancel to end the installation. |
Log in as the oracle user.
If you are not installing the software on the local system then, run the following command on remote machine:
Bourne, Bash, or Korn shell:
$ export DISPLAY=localhost:0.0
C shell:
% setenv DISPLAY local_host:0.0
In this example, local_host is the host name or IP address of the system that you want to use to display Oracle Universal Installer (your workstation or PC).
Now to enable X applications, run the following command on the machine that you want to use to display Oracle Universal Installer (your workstation or PC):
$ xhost + [fully_qualified_remote_host_name]
Enter the following commands to start Oracle Universal Installer, where patchset_directory is the directory where you unpacked the patch set software:
% cd patchset_directory/Disk1
% ./runInstaller
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.
If you are installing the patch set on an Oracle RAC cluster, click Next when the Selected Nodes screen appears.
On the Summary screen, click Install.
This screen lists all of the patches available for installation.
When prompted, run the $ORACLE_HOME/root.sh script as the root user. If you are applying the patch set to an Oracle RAC installation, then run the root.sh script on each node of the cluster.
|
Note: If you are applying this patch set to an Oracle Clusterware installation, then complete all of the steps displayed on the Oracle Universal Installer screen.The Oracle Clusterware installation instructions displayed on the Oracle Universal Installer screen are also available in the When applying this patch set on an Oracle Clusterware home, Oracle Universal Installer prompts you to run the |
On the End of Installation screen, click Exit, then click Yes to exit from Oracle Universal Installer.
To install the Oracle Database 10g 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
|
Note: For Oracle RAC installations, make sure theCLUSTER_NODES variable specifies all of the nodes used in the original Oracle RAC installation. |
To run Oracle Universal Installer, enter a command similar to the following, where response_file is the full path to the response file that you edited:
$ ./runInstaller -silent -responseFile response_file
After the installation, run the $ORACLE_HOME/root.sh script as the root user. If you are applying the patch set to an Oracle RAC installation, then run the root.sh script on each node of the cluster.
|
Note: If you are applying this patch set to an Oracle Clusterware installation, then complete all the steps in theCRS_home/install/readme.txt file. You must run this script as the root user on all nodes. |
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.
Review the following sections before upgrading an earlier Database to Oracle Database 10g release 2 (10.2.0.3):
For information about upgrading Oracle databases from an earlier Oracle database (Oracle8i, Oracle9i, or Oracle Database 10g), see Oracle Database Upgrade Guide.
If you are upgrading an Oracle RAC database, refer to the Oracle Real Application Clusters Administration Guide as well.
If you want to upgrade an Oracle9i release 9.2 preconfigured database, and you are not using Oracle Label Security, complete the following steps to avoid errors during the upgrade:
Use Oracle Universal Installer release 9.2 to install Oracle Label Security using the Custom installation type.
Run the $ORACLE_HOME/rdbms/admin/catnools.sql script with the SYSDBA privilege to remove Oracle Label Security components from the database.
See one of the following sections for upgrading an Oracle Database 10g release 10.2.0.x to Oracle Database 10g release 10.2.0.3:
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:
|
Log in as the Oracle software owner user.
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:
$ lsnrctl start
Run Oracle Database Upgrade Assistant either in the interactive or noninteractive mode:
Interactive mode:
Enter the following command from the command prompt:
$ dbua
Complete the following steps displayed in the Oracle Database Upgrade Assistant screen:
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.
|
Note: For Oracle RAC, enter theSYS password to do the upgrade. |
On the Recompile invalid objects screen, select the Recompile the invalid objects at the end of upgrade option, then click Next.
If you have not taken the back up of the database earlier, on the Backup screen, select the I would like to take this tool to backup the database option, mention the Path, then click Next.
On the Summary screen, check the summary, then click Finish.
On the End of upgradation screen, click Exit, then click Yes to exit from Oracle Database Upgrade Assistant.
Noninteractive mode:
Enter the following command to upgrade Oracle Database using Oracle Database Upgrade Assistant in noninteractive mode
$ dbua -silent -dbname $ORACLE_SID -oracleHome $ORACLE_HOME -sysDBAUserName UserName -sysDBAPassword SYS_password -recompile_invalid_objects true
If you are using the Oracle Recovery Manager catalog, enter the following command:
$ rman catalog username/password@alias RMAN> UPGRADE CATALOG;
For Oracle RAC installations, start any database services that you want to use by entering the following command:
$ srvctl start service -d db_name -s service_name
Complete the following sections to upgrade an Oracle Database 10g release 10.2.0.x to Oracle Database 10g release 10.2.0.3:
Check the SYSTEM tablespace size and set the initialization parameters.
Check the SYSTEM Tablespace Size
If JServer is part of the installation, ensure that there is at least 50 MB of free space allocated to the SYSTEM tablespace or autoextend space in your SYSTEM tablespace prior to upgrading.
Set the SHARED_POOL_SIZE and JAVA_POOL_SIZE Initialization Parameters
Set the value of the SHARED_POOL_SIZE and the JAVA_POOL_SIZE initialization parameters as follows:
Start the database with the NOMOUNT option:
SQL> STARTUP NOMOUNT
If necessary, enter the following command to determine whether the system uses an initialization parameter file (initsid.ora) or a server parameter file (spfiledbname.ora):
SQL> SHOW PARAMETER PFILE;
This command displays the name and location of the server parameter file or the initialization parameter file.
Determine the current values of these parameters:
SQL> SHOW PARAMETER SHARED_POOL_SIZE SQL> SHOW PARAMETER JAVA_POOL_SIZE
If the system is using a server parameter file:
If necessary, set the value of the SHARED_POOL_SIZE initialization parameter to at least 150 MB:
SQL> ALTER SYSTEM SET SHARED_POOL_SIZE='150M' SCOPE=spfile;
If necessary, set the value of the JAVA_POOL_SIZE initialization parameter to at least 150 MB:
SQL> ALTER SYSTEM SET JAVA_POOL_SIZE='150M' SCOPE=spfile;
If the system uses an initialization parameter file, if necessary change the values of the SHARED_POOL_SIZE and the JAVA_POOL_SIZE initialization parameters to at least 150 MB in the initialization parameter file (initsid.ora).
If you use Automatic Shared Memory Management, ensure that the value of the SGA_TARGET initialization parameter size is at least 50 MB greater than the sum of the values of the SHARED_POOL_SIZE and the JAVA_POOL_SIZE initialization parameters.
|
Note: The value of theSGA_TARGET parameter depends on the environment. If you receive a system error when you restart the database, increase the value of the SGA_TARGET parameter to the value specified in the error. |
Shut down the database:
SQL> SHUTDOWN
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 thecatupgrd.sql script as described in this section and you start up a database for normal operation, then ORA-01092:ORACLE instance terminated. Disconnection forced errors will occur and the error ORA-39700:database must be opened with UPGRADE option will be in the alert log. |
Log in as the Oracle software owner user.
For Oracle RAC installations, start listener on each node of the cluster as follows:
$ 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:
$ lsnrctl start
For single-instance installations, use SQL*Plus to log in to the database as the SYS user with SYSDBA privileges:
$ sqlplus /nolog
SQL> CONNECT SYS/SYS_password AS SYSDBA
For Oracle RAC installations:
Use SQL*Plus to log in to the database as the SYS user with SYSDBA privileges:
$ sqlplus /nolog
SQL> CONNECT SYS/SYS_password AS SYSDBA
SQL> 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> @?/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 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> @?/rdbms/admin/utlrp.sql
|
Note: When the 10.2.0.3 patch set is applied to an Oracle Database 10g Standard Edition database, there may be 42 invalid objects after theutlrp.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 |
If you are using the Oracle Recovery Manager catalog, enter the following command:
$ 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 SQL> STARTUP
Start any processes that you want to use:
$ srvctl start service -d db_name -s service_name
|
Important: Oracle recommends using the most restrictive file permissions possible for your given implementation. Perform these optional steps only after considering all security ramifications and only if you need to share this installation. |
During patch set installation, all new files and directories are created with restricted access, by default. Users or third party applications with a different group identifier from that of the database, which try to access client-side utilities or libraries in the database home, will see permission errors when trying to access these files or directories. Perform the following steps to change the permissions:
Change to the install directory by using the following command:
$ cd $ORACLE_HOME/install
Run changePerm.sh and specify the patched server Oracle home location, before accessing client-side utilities or libraries in the database home.
|
Note: If you are patching Oracle RAC home, then you will need to run this script on all the nodes. |
For installations with Oracle Database Vault, complete the following steps:
Run the catmac.sql script:
SQL> @?/rdbms/admin/catmac.sql SYSTEM TEMP SYS_password
Turn off the recycle bin:
SQL> ALTER SYSTEM SET RECYCLEBIN=OFF SCOPE=BOTH;
|
Note: For Oracle RAC environments, run this command on all instances in the cluster. |
Enable the Oracle Database Vault triggers:
SQL> CONNECT DVSYS/DVSYS; SQL> ALTER TRIGGER DV_BEFORE_DDL_TRG ENABLE; SQL> ALTER TRIGGER DV_AFTER_DDL_TRG ENABLE;
Lock the DVSYS account:
$ sqlplus /NOLOG SQL> CONNECT SYS/SYS_password AS SYSDBA SQL> ALTER USER DVSYS IDENTIFIED BY new_password; SQL> ALTER USER DVSYS ACCOUNT LOCK;
Log in as SYS user and run the following command:
SQL> @?/rdbms/admin/utlrp.sql
Shut down the database:
For Oracle RAC:
$ srvctl stop database -d db_name
For Single Instance:
SQL> CONNECT SYS/ AS SYSOPER Enter password: SYS_password SQL> SHUTDOWN
Re-link Oracle database software with dv_on:
|
Note: For Oracle RAC, you must run the following commands on all the nodes. |
$ cd $ORACLE_HOME/rdbms/lib $ make -f ins_rdbms.mk dv_on $ cd $ORACLE_HOME/bin $ relink oracle
Restart the database:
For Oracle RAC:
$ srvctl start database -d db_name -c "SYS/SYS_password as SYSDBA"
For Single Instance:
SQL> CONNECT SYS/ AS SYSOPER
Enter password: SYS_password
SQL> STARTUP
Re-create and replace the password file, in order to disable log in to an Oracle Database Vault instance as SYS user with SYDDBA privilege:
$ orapwd file=$ORACLE_HOME/dbs/orapwsid password=syspassword force=y nosysdba=y
If you saved TSTZ data as mentioned in section under , you need to restore this data to the TSTZ columns where they originated from.
Refer to the instructions in the utltzuv2.sql script in step of or OracleMetalink note 396671.1: Usage of utltzuv2.sql before updating time zone files in Oracle 10.
To locate document 396671.1 on the OracleMetalink Web site:
To locate document 396671.1:
Log on to OracleMetalink.
Click Advanced at the top of the OracleMetalink page.
Enter 396671.1 in the Document ID field, then click Submit.
Downgrading Oracle Database Vault from 10.2.0.3 to 10.2.0.2 requires the following steps:
Follow the steps in section ""
Follow the steps in section ""
Follow the steps in section ""
The catdwgrd.sql script enables the user to restore the Oracle Database installation of the database back to the original 10.2 release that the user backed up before applying the patch set. The catdwgrd.sql script is run in the 10.2.0.3 Oracle home to perform necessary downgrade actions. After the 10.2.0.x release is restored, the catrelod.sql script is run from 10.2.0.x Oracle home to reload the 10.2.0.x release packages and views.
See one of the following sections for information about how to remove the patch set software based on your Oracle Database installation type:
|
Note:
|
Perform the following steps for backing out from the 10.2.0.3 patch release:
Use SQL*Plus to log in to the database as the SYS user with SYSDBA privileges:
$ sqlplus /NOLOG
SQL> CONNECT SYS/SYS_password AS SYSDBA
SQL> SHUTDOWN IMMEDIATE
SQL> EXIT
Take a backup of the following file in 10.2.0.3 Oracle home directory:
$ ORACLE_HOME/rdbms/admin/catrelod.sql $ ORACLE_HOME/network/admin/tnsnames.ora
Enter the following SQL*Plus commands:
$ cd $ORACLE_HOME
$ sqlplus /NOLOG
SQL> CONNECT SYS/SYS_password AS SYSDBA
SQL> STARTUP DOWNGRADE
SQL> SPOOL downgrade.out
SQL> @?/rdbms/admin/catdwgrd.sql
SQL> SPOOL OFF
SQL> SHUTDOWN IMMEDIATE
SQL> EXIT
Review the downgrade.out file for errors.
Restore the Oracle10g installation and Central Inventory (see /etc/oraInst.loc) that you backed up before applying the patch set.
After restoring the original Oracle home, copy the saved version of catrelod.sql script into the restored Oracle home rdbms/admin directory. Also copy the saved version of 10.2.0.3/network/admin/tnsnames.ora directory into the restored Oracle home /network/admin/tnsnames.ora directory, and then perform the following steps:
$ sqlplus /NOLOG
SQL> CONNECT SYS/SYS_password AS SYSDBA
SQL> STARTUP DOWNGRADE
SQL> SPOOL catrelod.out
SQL> @?/rdbms/admin/catrelod.sql
SQL> SPOOL OFF
SQL> SHUTDOWN IMMEDIATE
Review the catrelod.out file for errors.
|
Note: Ignore theORA-29844 and ORA-31085 errors found in the catrelod.out file. These errors are tracked with Oracle bugs 4758112 and 4425495 respectively.
After reloading the 10.2.0.2 release, the version numbers for Oracle Data Mining and Oracle OLAP Analytic Workspace remain at 10.2.0.3. These issues are tracked with Oracle bugs 4758695 and 4751917. |
Start the database and recompile the remaining invalid objects:
SQL> STARTUP SQL> @?/rdbms/admin/utlrp.sql
Perform the following steps for backing out from the 10.2.0.3 patch release:
Use SQL*Plus to log in to the database as the SYS user with SYSDBA privileges:
$ sqlplus /NOLOG
SQL> CONNECT SYS/SYS_password AS SYSDBA
Set the CLUSTER_DATABASE initialization parameter to FALSE:
|
Note: If the system uses an initialization parameter file, change the value of theCLUSTER_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:
$ srvctl stop database -d db_name
Take a backup of the following files in 10.2.0.3 Oracle home directory:
$ ORACLE_HOME/rdbms/admin/catrelod.sql $ ORACLE_HOME/network/admin/tnsnames.ora
Enter the following SQL*Plus commands:
$ sqlplus /NOLOG
SQL> CONNECT SYS/SYS_password AS SYSDBA
SQL> STARTUP DOWNGRADE
SQL> SPOOL catdwgrd.out
SQL> @?/rdbms/admin/catdwgrd.sql
SQL> SPOOL OFF
SQL> SHUTDOWN IMMEDIATE
SQL> EXIT
Restore the Oracle10g installation and Central Inventory (see /etc/oraInst.loc) that you backed up before applying the patch set on both the nodes.
After restoring the original Oracle home, copy the saved version of catrelod.sql script into the restored Oracle home rdbms/admin directory. Also copy the saved version of 10.2.0.3/network/admin/tnsnames.ora directory into the restored Oracle home /network/admin/tnsnames.ora directory, and then perform the following steps:
$ sqlplus /NOLOG
SQL> CONNECT SYS/SYS_password AS SYSDBA
SQL> STARTUP DOWNGRADE
SQL> SPOOL catrelod.out
SQL> @?/rdbms/admin/catrelod.sql
SQL> SPOOL OFF
SQL> SHUTDOWN IMMEDIATE
Review the catrelod.out file for errors.
|
Note: Ignore theORA-29844 and ORA-31085 errors found in the catrelod.out file. These errors are tracked with Oracle bugs 4758112 and 4425495 respectively.
After reloading the 10.2.0.2 release, the version numbers for Oracle Data Mining and Oracle OLAP Analytic Workspace remain at 10.2.0.3. These issues are tracked with Oracle bugs 4758695 and 4751917. |
Start the database and recompile the remaining invalid objects:
SQL> STARTUP SQL> @?/rdbms/admin/utlrp.sql
Set the CLUSTER_DATABASE initialization parameter to TRUE:
|
Note: If the system uses an initialization parameter file, change the value of theCLUSTER_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:
$ srvctl start database -d db_name
|
Note: Option for removing Oracle Clusterware patch set is not available in 10.2.0.3. This issue is tracked with Oracle bug 5598010. |
If necessary, you can reinstall a patch set that has been applied to an Oracle Database 10g installation. You must reinstall the patch set interactively.
To reinstall the patch set:
Log in as the oracle user.
If you are not installing the software on the local system, enter the following command to direct X applications to display on the local system:
Bourne, Bash, or Korn shell:
$ DISPLAY=local_host:0.0 ; export DISPLAY
C shell:
% setenv DISPLAY local_host:0.0
In this example, local_host is the host name or IP address of the system that you want to use to display Oracle Universal Installer (your workstation or PC).
Enter the following commands to start Oracle Universal Installer, where patchset_directory is the directory where you unpacked the patch set software:
$ cd patchset_directory/Disk1
$ ./runInstaller
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.
If you are installing the patch set on an Oracle RAC cluster, click Next when the Selected Nodes screen appears.
|
Note: 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. |
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.
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.
Review the following known issues after you apply the patch set:
If you use Oracle Scheduler, that is, (dbms_scheduler) external jobs on Linux, and have modified the owner or group of the extjob executable, then this patch set will reset these changes.
Beginning with Oracle Database release 10.2.0.3, the supported way to change the user or group that external jobs run as is to modify the externaljob.ora file in rdbms/admin. This file is owned by root user and only the root user can modify this file. Changes to this file take effect immediately and do not require restarting the database.
If you are using an Oracle Database release 10.2.0.2 preconfigured Standard Edition database, then the database contains the following components that are not supported by the Standard Edition:
Oracle Data Mining
Oracle OLAP Catalog
Oracle OLAP Analytic Workspace
Oracle OLAP API
The catupgrd.sql script does not run the patch scripts for these components. It sets the component STATUS to OPTION OFF in the DBA_REGISTRY view. The original versions of the dictionary objects for the components remain in the database but the catupgrd.sql script does not apply the patch to them.
When you start Oracle Database Upgrade Assistant to upgrade 10.2.0.1 database to 10.2.0.3 patch set, the following error occurs:
Inplace upgrade of Enterprise Manager is not supported for RAC databases is not supported in this release
Workaround:
Ignore warning.
This issue is tracked with Oracle bug 5531470.
Oracle Database Upgrade Assistant fails during postinstallation upgrade on a single node and displays the following error message:
ORA-32001: write SPFILE requested but no SPFILE specified at startup
Workaround:
Start the database with the NOMOUNT option:
$ sqlplus /NOLOG
SQL> CONNECT SYS/SYS_password AS SYSDBA
SQL> STARTUP NOMOUNT
Create SPFILE from PFILE by entering the following command where pfile_location is usually $ORACLE_BASE/admin/db_name/pfile for Optimal Felxible Architecture compliant database:
SQL> CREATE SPFILE=SHARED_LOCATION/SPFILE.ORA FROM PFILE=pfile_location/init.ora
Shut down the database:
SQL> SHUTDOWN IMMEDIATE SQL> EXIT
Clear the contents of PFILE located at $ORACLE_HOME/dbs/initsid.ora and set the value of SPFILE as SHARED_LOCATION/SPFILE.ORA.
Run Oracle Database Upgrade Assistant:
$ $ORACLE_HOME/bin/dbua
|
Note: This workaround will resolve the issue faced during add node operation from single node. This issue is tracked with Oracle bug 5585075. |
This issue is tracked with Oracle bug 5531643.
Oracle OLAP users will not be able to connect to Oracle Warehouse Builder immediately after upgrading their database to 10.2.0.3.0.
Workaround:
Download patch 5548282 from OracleMetalink or Oracle Technology Network.
This issue is tracked with Oracle bug 5548282.
When you use Oracle Database Upgrade Assistant to upgrade the Automatic Storage Management instance of the 10.2.0.1 or 10.2.0.2 database to 10.2.0.3 patch set, the pre-upgrade summary page and the upgrade results page display the earlier 10.2 version of the Automatic Storage Management instance even if the upgrade is successful.
This issue is tracked with Oracle bug 5510050.
In an Oracle RAC set up, if database instances are not running on the same node as Oracle Enterprise Manager Management Service, then monitoring in memory access mode does not display performance chart data.
This issue is tracked with Oracle bug 5559618.
Rolling upgrade or upgrade of Oracle Clusterware to 10.2.0.3 patch set may cause VIP to move to the last node.
Workaround:
Enter the following command to relocate the VIP to the preferred node:
crs_relocate VIP Resource