APPLY ORACLE PATCH

APPLYING ORACLE PATCH

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 patch sets include only low impact fixes, we are not required to certify applications or tools against the server unless directed to by the operating system vendor. Also Patch sets are cumulative.

Procedure for applying Oracle patch sets:

Pre installation Tasks
a. Review Known Pre installation Issues.
b. Review Changes in Oracle Text Filtering Technology.
c. Pre installation Considerations for Oracle Real Application Clusters.
d. Identify the Oracle Installation.
e. Check Post release Updates.
f. Download and Extract the Installation Software.
g. Set the ORACLE_HOME and ORACLE_SID Environment Variables.
h. Shut Down Oracle Databases.
i. Stop All Processes.
j. Back Up the System.

Installation Tasks
The following procedure describes how to install the patch set interactively:

2.1. Log in as the Oracle software owner (typically oracle).

2.2. 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


2.3. Enter following commands to start Oracle Universal Installer, where patch set directory is the directory you unpacked the patch set software:

$ patchset_directory/Disk1
$ ./runInstaller


2.4. On the Welcome screen, click Next.

2.5. On the Specify File Locations screen, click Browse next to the Path field in the Source section.

2.6. Select the products.xml file from the stage directory where you unpacked the patch set files, then click Next. For example:

patchset_directory/Disk1/stage/products.xml


2.7. In the Name field in the Destination section, select the name of the Oracle home that you want to update from the drop down list, then click Next.

2.8. On the Summary screen, click Install.

This screen lists all of the patches available for installation.

2.9. 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.

2.10. On the End of Installation screen, click Exit, then click Yes to exit from Oracle Universal Installer.

Postinstallation tasks
Check Tablespace Sizes and Set Parameter Values.
3.1. Check SYSTEM Tablespace Size. If JServer is part of the installation ensure that there is at least 10 MB of free space allocated to the SYSTEM tablespace.
3.2. Check XDB Tablespace Size. For Oracle RAC installations, ensure that there is at least 50 MB of free space allocated to the XDB tablespace.
3.3. Set the SHARED_POOL_SIZE and JAVA_POOL_SIZE Initialization Parameters. Users who have JVM (Java enabled) or JVM and XDB installed on their 9.2.0.1 databases should make sure that the init.ora parameters SHARED_POOL_SIZE and JAVA_POOL_SIZE are each 150 MB or more before running the catpatch.sql upgrade script. Failure to do so could result in an unrecoverable memory failure while running of the script. Set the value of the SHARED_POOL_SIZE and the JAVA_POOL_SIZE initialization parameters as follows:
a. Use SQL*Plus to log in to the database as the SYS user with SYSDBA privileges: $ sqlplus /nolog
SQL> CONNECT / AS SYSDBA
b. Start the database:
SQL> STARTUP
c. 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.
d. Determine the current values of these parameters:
SQL> SHOW PARAMETER SHARED_POOL_SIZE
SQL> SHOW PARAMETER JAVA_POOL_SIZE
e. If the system is using a server parameter file:
1.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;
2..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;
f. 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).
g. Shut down the database:
SQL> SHUTDOWN IMMEDIATE;

4. Upgrade Database.
1. Log in as the Oracle software owner (typically oracle).
2.Start the Oracle Net listener as follows:
$ lsnrctl start
3.log in to the database as the SYS user with SYSDBA privileges.
$ sqlplus /nolog
SQL> CONNECT / AS SYSDBA
4.Enter the following SQL*Plus commands:
SQL> STARTUP MIGRATE
SQL> SPOOL patch.log
SQL> @?/rdbms/admin/catpatch.sql SQL> SPOOL OFF
5.Review the patch.log file for errors and inspect the list of components that is displayed at the end of catpatch.sql script.
6. If necessary, rerun the catpatch.sql script after correcting any problems.
7.Restart the database:
SQL> SHUTDOWN IMMEDIATE
SQL> STARTUP
8.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