Introduction and scope:

This document is intended for those which are having 10.2.0.1 database installation and intended to upgrade the same to 10.2.0.2, by applying 10.2.0.2 patchset.

This document is based on Metalink note ID 316900.1. Follow the below procedure for upgrading the database from 10.2.0.1 to 10.2.0.2

Pre-Requiste:

We are assuming that you have already installed 10.2.0.1 Database. This patchset has to be applied over and above 10.2.0.1.

Pre Installation Steps:

1. Download patch p4547817_10202_LINUX.zip (download patch according to your operating system like windows, solaris..) and copy it to your linux machine
2. Unzip patch as “unzip p4547817_10202_LINUX.zip”
3. Set ORACLE_HOME and ORACLE_SID to your database (10.2.0.1) on which you are planning to apply this patchset .
   • ORACLE_HOME = /u01/app/oracle/OHome
   • ORACLE_SID = g9
   • export ORACLE_HOME ORACLE_SID
4. Stop database and database listener
5. Take a cold backup of your complete database.

Database 10.2.0.2 Patch Set Installation Steps:

Login as oracle user who installed 10.2.0.1 database make sure that DISPLAY variable is set correctly and check xclock command is opening a clock. Change directory to patchset unziped directory and run the following command

bash-2.05$ ./runInstaller -invPtrLoc /u01/app/oracle/OHome/oraInst.Loc

Choose the correct ORACLE_HOME name and location. Remember that you are upgrading the existing 10.2.0.1 ORACLE_HOME.

Other screens are simple and self explanatory.

Check opatch version after ORACLE_HOME is upgraded.

bash-2.05$ cd $ORACLE_HOME
bash-2.05$ cd OPatch/
bash-2.05$ opatch version
Invoking OPatch 10.2.0.2.0

OPatch Version: 10.2.0.2.0

OPatch succeeded.

Now we have upgraded the ORACLE_HOME to 10.2.0.2. Next thing is to upgrade the database from 10.2.0.1 to 10.2.0.2. For this you need to open the database in upgrade.

1. Mount the database and check the parameters first and check the parameters SHARED_POOL_SIZE and JAVA_POOL_SIZE. Values for these parameters should be atleast 150M. If not please set the values to atleast 150M.
2. shutdown and startup again in upgrade mode.

SQL> startup upgrade
ORACLE instance started.

Total System Global Area 427819008 bytes
Fixed Size 2029464 bytes
Variable Size 398461032 bytes
Database Buffers 25165824 bytes
Redo Buffers 2162688 bytes
Database mounted.
Database opened.
SQL> spool upgrade.log
SQL> @?/rdbms/admin/catupgrd.sql

SQL> spool off

Once the upgrade is done. Check any errors in the spooled file. If every thing is OK you can proceed to recompile the invalids using utlrp.sql script present in ORACLE_HOME/rdbms/admin directory.

After recompiling shutdown the database and startup for allowing access to the users.