Upgrading Oracle Database 10g Release 10.2.0.

x to Oracle Database 10g Release

10.2.0.4
Reference:
1) Oracle Patch Set Notes Please follow this Document
Oracle Database Patch Set Notes
10g Release 2 (10.2.0.4) Patch Set 3 for Linux x86


2) Vincent Chan (vkchan99@yahoo.com) is a Senior Consultant at MSD Inc. He is an Oracle Certified
Master DBA with more than ten years of experience architecting and implementing Oracle solutions for
various clients.
http://www.oracle.com/technology/tech/linux/install/index.html

Doubts, Comments and suggestions: Please feel free to contact me @ prakash.dba@gmail.com

Versions Used:
Oracle Clusterware: 10.2.0.1
Oracle Database 10g: 10.2.0.1
Operating System: Oracle Enterprise Linux 4.0
VM Ware: 1.06
** This specific patch is for Oracle Binaries but not for the Clusterware, which I will update
soon.

7.7.3 Stopping All Processes for an Oracle RAC Installation
Shut down the following Oracle Database 10g processes before installing the patch set:
1. 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:
2. $ emct l st op dbconsol e
3. $ i sql pl usct l st op

HOST 1


HOST 2



l ogi n as: or acl e
or acl e@192. 168. 2. 131' s passwor d:
Last l ogi n: Thu J ul 10 12: 31: 29 2008
r ac1- > host name
r ac1. mycor pdomai n. com
r ac1- > emct l st op dbconsol e
TZ set t o US/ East er n
Or acl e Ent er pr i se Manager 10g Dat abase Cont r ol Rel ease 10. 2. 0. 1. 0
Copyr i ght ( c) 1996, 2005 Or acl e Cor por at i on. Al l r i ght s r eser ved.
ht t p: / / r ac1. mycor pdomai n. com: 1158/ em/ consol e/ about Appl i cat i on
St oppi ng Or acl e Ent er pr i se Manager 10g Dat abase Cont r ol . . .
. . . St opped.
r ac1- > i sql pl usct l st op
i SQL*Pl us 10. 2. 0. 1. 0
Copyr i ght ( c) 2003, 2005, Or acl e. Al l r i ght s r eser ved.
i SQL*Pl us i nst ance on por t 5560 i s not r unni ng . . .

1. Shut down all services in the Oracle home on each node that might be
accessing a database:
$ sr vct l st op ser vi ce - d db_name [ - s
service_name_list [ - i inst_name] ]


r ac1- > cr s_st at - t
Name Type Tar get St at e Host
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
or a. devdb. db appl i cat i on ONLI NE ONLI NE r ac1
or a. . . . b1. i nst appl i cat i on ONLI NE ONLI NE r ac1
or a. . . . b2. i nst appl i cat i on ONLI NE ONLI NE r ac2
or a. . . . SM1. asmappl i cat i on ONLI NE ONLI NE r ac1
or a. . . . C1. l snr appl i cat i on ONLI NE ONLI NE r ac1
or a. r ac1. gsd appl i cat i on ONLI NE ONLI NE r ac1
or a. r ac1. ons appl i cat i on ONLI NE ONLI NE r ac1
or a. r ac1. vi p appl i cat i on ONLI NE ONLI NE r ac1
or a. . . . SM2. asmappl i cat i on ONLI NE ONLI NE r ac2
or a. . . . C2. l snr appl i cat i on ONLI NE ONLI NE r ac2
or a. r ac2. gsd appl i cat i on ONLI NE ONLI NE r ac2
or a. r ac2. ons appl i cat i on ONLI NE ONLI NE r ac2
or a. r ac2. vi p appl i cat i on ONLI NE ONLI NE r ac2

*** No Ser vi ces r unni ng as I di d not conf i gur e any
ski ppi ng t hi s st ep.

1. 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:
$ sr vct l st op dat abase - d db_name

r ac1- > host name
r ac1. mycor pdomai n. com
r a

c1- >
rac1-> srvctl stop database -d devdb

r ac1- > ps - ef | gr ep devdb
or acl e 5735 1452 0 16: 24 pt s/ 4 00: 00: 00 gr ep devdb

r ac1- > cr s_st at - t
Name Type Tar get St at e Host
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ora.devdb.db application OFFLINE OFFLINE
ora....b1.inst application OFFLINE OFFLINE
ora....b2.inst application OFFLINE OFFLINE
or a. . . . SM1. asmappl i cat i on ONLI NE ONLI NE r ac1
or a. . . . C1. l snr appl i cat i on ONLI NE ONLI NE r ac1
or a. r ac1. gsd appl i cat i on ONLI NE ONLI NE r ac1
or a. r ac1. ons appl i cat i on ONLI NE ONLI NE r ac1
or a. r ac1. vi p appl i cat i on ONLI NE ONLI NE r ac1
or a. . . . SM2. asmappl i cat i on ONLI NE ONLI NE r ac2
or a. . . . C2. l snr appl i cat i on ONLI NE ONLI NE r ac2
or a. r ac2. gsd appl i cat i on ONLI NE ONLI NE r ac2
or a. r ac2. ons appl i cat i on ONLI NE ONLI NE r ac2
or a. r ac2. vi p appl i cat i on ONLI NE ONLI NE r ac2



2. 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:
$ sr vct l st op asm- n node
** Make sure that we stop on each node.



This needs to be done only when patching the home from where ASM runs. It
is recommended that ASM run from a different ORACLE_HOME than the database.
3. 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:
$ sr vct l st op l i st ener - n node [ - l listenername]

r ac1- > sr vct l st op l i st ener - n r ac1 - l LI STENER_RAC1





7.8 Back Up the System
Oracle recommends that you create a backup of the Oracle Inventory, Oracle 10g home and
Oracle 10g Database before you install the patch set. If you are planning to apply this patch to
Oracle RAC, ensure that you create a backup of these components on all nodes before applying
the patch
I di d not as have a backup of whol e VM Pool .

8 Installation Tasks

8.1 Installing the Oracle Database 10g Patch Set Interactively
To install the Oracle Database 10g patch set interactively:
1. Log in as the oracle user. (Please note that I am doing it from the Server Console, so
no X-Windows software).

1. 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/ Di sk1
%. / r unI nst al l er




2. On the Welcome screen, click Next.
3. On 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.

4. If you are installing the patch set on an Oracle RAC cluster, click Next when the
Selected Nodes screen appears.

5. On the Product-specific Prerequisite Checks screen, correct any reported
errors, and click Next.


6. Enter details regarding the CSI Number, OracleMetaLink Account user
name and Country code on the Oracle Configuration Manager Registration
screen and click Next.

Note:
The registration and configuration can also be done manually after patchset
installation.
The OCM registration page appears only while applying 10.2.0.4 patch over
existing DB instances alone. ( New Feature of Oracle 10.2.0.4)
7. On the Summary screen, click Install.

This screen lists all of the patches available for installation.
8. When prompted, run the $ORACLE_HOME/ r oot . sh script as the r oot user. If you are
applying the patch set to an Oracle RAC installation, then run the r oot . 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 CRS_home/ i nst al l / r eadme. t xt file.
o When applying this patch set on an Oracle Clusterware home, Oracle Universal
Installer prompts you to run the r oot 102. sh script from $ORACLE_HOME/ i nst al l . You must
run this script as the r oot user on all nodes.
o Before you add a new node, ensure that you run r oot pr e. sh script as the r oot
user on the new node.
9. On the End of Installation screen, click Exit, then click Yes to exit from
Oracle Universal Installer.

[ r oot @r ac1 ~] # / u01/ app/ or acl e/ pr oduct / 10. 2. 0/ db_1/ r oot . sh
Runni ng Or acl e10 r oot . sh scr i pt . . .

The f ol l owi ng envi r onment var i abl es ar e set as:
ORACLE_OWNER= or acl e
ORACLE_HOME= / u01/ app/ or acl e/ pr oduct / 10. 2. 0/ db_1

Ent er t he f ul l pat hname of t he l ocal bi n di r ect or y: [ / usr / l ocal / bi n] :
The f i l e " dbhome" al r eady exi st s i n / usr / l ocal / bi n. Over wr i t e i t ? ( y/ n)
[ n] : y
Copyi ng dbhome t o / usr / l ocal / bi n . . .
The f i l e " or aenv" al r eady exi st s i n / usr / l ocal / bi n. Over wr i t e i t ? ( y/ n)
[ n] : y
Copyi ng or aenv t o / usr / l ocal / bi n . . .
The f i l e " cor aenv" al r eady exi st s i n / usr / l ocal / bi n. Over wr i t e i t ? ( y/ n)
[ n] : y
Copyi ng cor aenv t o / usr / l ocal / bi n . . .

Ent r i es wi l l be added t o t he / et c/ or at ab f i l e as needed by
Dat abase Conf i gur at i on Assi st ant when a dat abase i s cr eat ed
Fi ni shed r unni ng gener i c par t of r oot . sh scr i pt .
Now pr oduct - speci f i c r oot act i ons wi l l be per f or med.

[ r oot @r ac2 ~] # / u01/ app/ or acl e/ pr oduct / 10. 2. 0/ db_1/ r oot . sh
Runni ng Or acl e10 r oot . sh scr i pt . . .

The f ol l owi ng envi r onment var i abl es ar e set as:
ORACLE_OWNER= or acl e
ORACLE_HOME= / u01/ app/ or acl e/ pr oduct / 10. 2. 0/ db_1

Ent er t he f ul l pat hname of t he l ocal bi n di r ect or y: [ / usr / l ocal / bi n] :
The f i l e " dbhome" al r eady exi st s i n / usr / l ocal / bi n. Over wr i t e i t ? ( y/ n)
[ n] : y
Copyi ng dbhome t o / usr / l ocal / bi n . . .
The f i l e " or aenv" al r eady exi st s i n / usr / l ocal / bi n. Over wr i t e i t ? ( y/ n)
[ n] : y
Copyi ng or aenv t o / usr / l ocal / bi n . . .
The f i l e " cor aenv" al r eady exi st s i n / usr / l ocal / bi n. Over wr i t e i t ? ( y/ n)
[ n] : y
Copyi ng cor aenv t o / usr / l ocal / bi n . . .

Ent r i es wi l l be added t o t he / et c/ or at ab f i l e as needed by
Dat abase Conf i gur at i on Assi st ant when a dat abase i s cr eat ed
Fi ni shed r unni ng gener i c par t of r oot . sh scr i pt .
Now pr oduct - speci f i c r oot act i ons wi l l be per f or med.





9.3.2.2 Upgrading a Release 10.2 Database

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 cat upgr d. sql script as described in this section and
you start up a database for normal operation, then ORA- 01092: ORACLE
i nst ance t er mi nat ed. Di sconnect i on f or ced errors will occur and
the error ORA- 39700: dat abase must be opened wi t h UPGRADE
opt i on will be in the alert log.

1. Log in as the Oracle software owner user.
2. For Oracle RAC installations, start listener on each node of the cluster as follows:
3. $ sr vct l st ar t l i st ener - n node
4. If you are using Automatic Storage Management, start the Automatic Storage
Management instance.
5. For single-instance installations, start the l i st ener as follows:
6. $ l snr ct l st ar t
7. For single-instance installations, use SQL*Plus to log in to the database as the SYS user
with SYSDBA privileges:
8. $ sql pl us / nol og
9. SQL> CONNECT SYS AS SYSDBA
10. Ent er passwor d: SYS_password
11. For Oracle RAC installations:
a. Use SQL*Plus to log in to the database as the SYS user with SYSDBA privileges:
b. $ sql pl us / nol og
c. SQL> CONNECT SYS AS SYSDBA
d. Ent er passwor d: SYS_password
e. SQL> STARTUP NOMOUNT
f. Set the CLUSTER_DATABASE initialization parameter to FALSE:
g. SQL> ALTER SYSTEM SET CLUSTER_DATABASE=FALSE
SCOPE=spf i l e;
h. Shut down the database:
i . SQL> SHUTDOWN
12. Enter the following SQL*Plus commands:
13. SQL> STARTUP UPGRADE
14. SQL> SPOOL pat ch. l og
15. SQL> @?/ r dbms/ admi n/ cat upgr d. sql
16. SQL> SPOOL OFF

Ref er Bel ow scr een upon compl et i on:
Or acl e Dat abase 10. 2 Upgr ade St at us Ut i l i t y 07- 10- 2008 19: 22: 56
.
Component St at us Ver si on HH: MM: SS
Or acl e Dat abase Ser ver VALI D 10. 2. 0. 4. 0 00: 19: 00
J Ser ver J AVA Vi r t ual Machi ne VALI D 10. 2. 0. 4. 0 00: 12: 34
Or acl e XDK VALI D 10. 2. 0. 4. 0 00: 02: 09
Or acl e Dat abase J ava Packages VALI D 10. 2. 0. 4. 0 00: 01: 10
Or acl e Text VALI D 10. 2. 0. 4. 0 00: 00: 58
Or acl e XML Dat abase VALI D 10. 2. 0. 4. 0 00: 03: 29
Or acl e Real Appl i cat i on Cl ust er s VALI D 10. 2. 0. 4. 0 00: 00: 03
Or acl e Wor kspace Manager VALI D 10. 2. 0. 4. 3 00: 01: 37
Or acl e Dat a Mi ni ng VALI D 10. 2. 0. 4. 0 00: 00: 48
OLAP Anal yt i c Wor kspace VALI D 10. 2. 0. 4. 0 00: 01: 18
OLAP Cat al og VALI D 10. 2. 0. 4. 0 00: 01: 58
Or acl e OLAP API VALI D 10. 2. 0. 4. 0 00: 01: 54
Or acl e i nt er Medi a VALI D 10. 2. 0. 4. 0 00: 08: 48
Spat i al VALI D 10. 2. 0. 4. 0 00: 05: 33
Or acl e Expr essi on Fi l t er VALI D 10. 2. 0. 4. 0 00: 00: 32
Or acl e Ent er pr i se Manager VALI D 10. 2. 0. 4. 0 00: 03: 31
Or acl e Rul e Manager VALI D 10. 2. 0. 4. 0 00: 00: 26


1. Review the pat ch. l og file for errors and inspect the list of components that is
displayed at the end of cat upgr d. sql script.
This list provides the version and status of each SERVER component in the database.
2. If necessary, rerun the cat upgr d. sql script after correcting any problems.
3. Restart the database:
4. SQL> SHUTDOWN I MMEDI ATE
5. SQL> STARTUP
6. Run the ut l r p. 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.
7. SQL> @?/ r dbms/ admi n/ ut l r p. sql


TI MESTAMP
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
COMP_TI MESTAMP UTLRP_END 2008- 07- 10 19: 56: 26
DOC> The f ol l owi ng quer y r epor t s t he number of obj ect s t hat have compi l ed
DOC> wi t h er r or s ( obj ect s t hat compi l e wi t h er r or s have st at us set t o 3 i n
DOC> obj $) . I f t he number i s hi gher t han expect ed, pl ease exami ne t he er r or
DOC> messages r epor t ed wi t h each obj ect ( usi ng SHOWERRORS) t o see i f t hey
DOC> poi nt t o syst emmi sconf i gur at i on or r esour ce const r ai nt s t hat must be
DOC> f i xed bef or e at t empt i ng t o r ecompi l e t hese obj ect s.
DOC>#

OBJ ECTS WI TH ERRORS
- - - - - - - - - - - - - - - - - - -
0
DOC> The f ol l owi ng quer y r epor t s t he number of er r or s caught dur i ng
DOC> r ecompi l at i on. I f t hi s number i s non- zer o, pl ease quer y t he er r or
DOC> messages i n t he t abl e UTL_RECOMP_ERRORS t o see i f any of t hese er r or s
DOC> ar e due t o mi sconf i gur at i on or r esour ce const r ai nt s t hat must be
DOC> f i xed bef or e obj ect s can compi l e successf ul l y.
DOC>#

ERRORS DURI NG RECOMPI LATI ON
- - - - - - - - - - - - - - - - - - - - - - - - - - -
0


SQL> ALTER SYSTEM SET CLUSTER_DATABASE=TRUE SCOPE=spf i l e;
SQL> shut down
Dat abase cl osed.
Dat abase di smount ed.
ORACLE i nst ance shut down.



Happy Endi ngs

Take a f ul l backup Reboot t he nodes, i f you want ! And Cl ose t he Change.

Cheer s
Ravi Pr akash