Upgrade Rel 10.2.0.3 – 12.0.4 Oracle Applications database to version 10.2.0.4

Upgrade Rel 10.2.0.3 – 12.0.4 Oracle Applications database to version 10.2.0.4


1.) Install Oracle database patch 10.2.0.4 (Time: 1 hour)

a. Create 10.2 stage directory, cd to Disk1 directory and execute ./runInstaller.

2.) Apply database patches to 10.2.0.4 home (Time: 1 hour)

a. 4247037
b. 6870937
c. 7014646
d. 8362683
e. 7411865
f. 7038750 --- only available for 64 bit OS
g. 5386204
h. 7197637
i. 7496435 – all the patches in this bundle patch are covered by 8362683
( Please check the below patches are not covered in 8362683 if not pl apply)

Note: - patch #7278117 which is a part of 8362683 was giving a following error while applying. It has a conflict with the patch 7014646. As patch #7014646 is mentioned in the interop doc 454750.1, I chose to install 7014646 over 7278117.

Error:-
The following warnings have occurred during OPatch execution:
1) OUI-67301:
Following patches have conflicts. Please contact Oracle Support and get the merged patch of the patches :
7014646 7278117

4) Prepare DB for Upgrade (Time: 20 minutes)

a. Shutdown all application services
b. Verify that 10.2.0.3 database is defined in /var/opt/oracle/oratab file.


Upgrade database {Time: 2 Hrs)

c. Run dbua from 10.2.0 Oracle Home/bin directory.
i. Choose database to be upgraded
ii. Choose not to backup database.
Used catupgrd.sql to upgrade the database because DBUA screen was dead slow and not responding. After that I executed utlrp.sql for compiling the components.

Post Upgrade {Time: 2Hr}

d. Add 10gR3 release specific parameters to the init.ora file and remove obsolete parameters follow the doc 216205.1 -- None required
e. Run changeperm.sh from $ORACLE_HOME/install.
f. Select comp_name,version,status from dba_registry;
In the out put ,status of all components should be Valid. If there is any invalid check the note 565600.1
g. Run autoconfig on db.
h. Copy $APPL_TOP/admin/adstats.sql to $ORACLE_HOME/appsutil/admin directory.
i. Shutdown database and startup in restricted mode and run adstats.sql as sysdba. Then shutdown database again and startup in normal mode.(make sure we have atleast 1.5GB)
j. Start the new database listener.
k. select owner, table_name, stattype_locked from dba_tab_statistics
where stattype_locked is not null
If there are any schemas (which has tables with locked statistics)
other than SYS, SYSTEM execute
the following command:
exec dbms_stats.unlock_schema_stats('');
or exec dbms_stats.unlock_schema_stats ('&name');
l. Run Gather statistics on fixed tables using the below sql
exec dbms_stats.gather_fixed_objects_stats;
m. Run adadmin and run program “recreate grants and synonyms”.
n. Startup application services and test login.
o. Run Gather Schema Stats (timings are exclusive of this step )

References: Metalink Doc. 454750.1 and For issues 555579.1