continuation of last post upgradation from 10.2.0.1 to 10.2.0.2 in E-Business Suit

Introduction

We need to install the 10.2.0.2 software only follow my last post , the process remain same.

Up gradation  of Oracle Database  on Sun OS using catupgrd.sql  is same as like other catupgrd.sql on other platforms. The only difference lies in setting operating system parameters like kernel configuration, checking memory, disks and other resources.

 Objective

The objective of this document is to detail out the Upgradation steps of Oracle 10.2.0.1 to  10.2.0.2 on Sun OS .

Creating Staging Area on the Server

Staging Area is an area from where you will stage the Oracle 10.2.0.2 Patch  Software and run the installation programme. Staging area for Oracle 10.2.0.2  requires around 1-2  GB of disk space. Download  patch p4547817_10202_SOLARIS64.zip  from oracle.metalink.com Create directories named as the stage and unzip the patch  

Stage No.  of  Patch Patch Contents
Oracle10.2.0.2 Software 1 Disk1 /d33/stage 

<h2

Starting Oracle 10G Software Installation.

Follow the same process as my last post
After Sucessfull Installation , Follow the below steps to accomplish the task

Post Install Checks

Check the log file for any errors .

Before you Begin Up gradation in Source Database

a. MANDATORY Patch Release for 10.2.0.2 RDBMS on Sun Sparc Solaris 64-bit Patch 5117016

b. Check before applying the patch . If $ORACLE_HOME/rdbms/lib/libserver10.a exists, the mandatory patch has probably not been installed.

c. Read readme.txt and follow the instruction to apply patch.

Required Pre-upgrade Checks

a. 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
b. Check SYSAUX Tablespace Size, ensure that there is at least 50 MB of free space allocated to the XDB tablespace.
c. Check 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:

d. Start the database:
SQL> STARTUP NOMOUNT
e.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.
f.Determine the current values of these parameters:
SQL> SHOW PARAMETER SHARED_POOL_SIZE
SQL> SHOW PARAMETER JAVA_POOL_SIZE
g.If the system is using a server parameter file:
i)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;
ii)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;
h.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).
i. 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 the SGA_TARGET parameter depends on your 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.

f.Shut down the database:
SQL> SHUTDOWN

Database Up gradation
$lsncrtl
$ start
$ sqlplus /nolog
SQL> CONNECT / AS SYSDBA
SQL> STARTUP UPGRADE
SQL> SPOOL patch.log
SQL> @?/rdbms/admin/catupgrd.sql
SQL> SPOOL OFF
Check patch.log after completion .
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

Check the invalid objects after completion using the following qyery :-
spool invalid_pre.lst
select substr(owner,1,12) owner,
substr(object_name,1,30) object,
substr(object_type,1,30) type, status from
dba_objects where status ‘VALID’;
spool off
Compile all the invalid objects using
Run the following script and then requery invalid objects:
This script must be run as a user with SYSDBA privs using SQL*Plus:
$ cd $ORACLE_HOME/rdbms/admin
$ sqlplus ‘/as sysdba’

Even compile all the objects using Adamin utility of Oracle E –Business Suit .

Summary
In this document we have covered:
1. Preparing the Sun Solaris system for Oracle 10.2.0.2 Up gradation .
2. Creating Staging Area of Oracle 10.2.0.2 patch
3. Installing Oracle 10.2.0.2 on Sun Solaris Server.
4. Upgrading Oracle Database from 10.2.0.1 to 10.2.0.2
References
Oracle Metlink: https://metalink.oracle.com.

Share This Post with Your Friends over Social Media!

About the Author Rajat

I am Rajat Dey and I have more than decade of Oracle experience from all major regions throughout the globe. I am well versed in most facets of Oracle, supporting database, fusion middleware and the eBusiness suite across many operating system platforms.Currently I am located in Sydney  Oracle Financials 11i and Release 12,12.2  Oracle RDBMS 7x,8i , 9i,10g and 11g  Amazon cloud .  Oracle RAC 10g and 11g  Oracle Applications Server  Oracle Web logic Server  OBIEE  Hyperion  SSO  Oracle Portal  PL/SQL  UNIX  SQL  MS-SQL 2008.  OEM 12c .  Data Guard .  Essbase .  Database backup and recovery.  Performance Tunning.  TimeSten

Leave a Comment:

[i]
[i]
[i]
[i]
[index]
[index]
[523.251,1046.50]
[523.251,1046.50]
[523.251,1046.50]
[523.251,1046.50]
[index]
[index]
[523.251,1046.50]
[523.251,1046.50]
[523.251,1046.50]
[523.251,1046.50]