Professional Documents
Culture Documents
Upgrading 1 1.5.8 Application and 9.2.0 Database in 24 Hours
Upgrading 1 1.5.8 Application and 9.2.0 Database in 24 Hours
0 Database in 24 Hours
Presented by:
JPL
Introductions
JPL
Agenda
JPL
+ + + +
JPL
JPL
Upgrade Timing
Normal Upgrade Duration 4 days (24x7) Totally Unacceptable Innovative Method using Private Regions
24 hours
Reduction of 7 5 O / 0 downtime
Jet Propulsion Laboratory California Institute of Technology
JPL
System Configuration
Hardware
Sun EIOK 16b 4gbx4cpu
Solaris 8 Veritas File System EMC Symmetrix 8830
JPL
AS
cn
S
m -
a ,
a ,
m -
cn cn
C
3 2n
H
S E m S 0 w L
\ \ \ \ \
cn a,
\ \ \ \ \
0 a . .- 0 U m a,
v)
.
0
W L
cn
c .a , (31
L
c a .v) m m > .- L a u
0 0 c c v) , c c, CL 0 L a a & , L 0 3 >
L
v)
(31
>
v)
>
m 23 In
v)
a ,
S
v)
I -
S
I n I n rl
S
v)
U
I
>
73
a ,
CD
Q
m -
t
I
&
a ,
0
m
U
0
n
m m U m
v)
S
, a a , , a 3
U
rl
0;
0 z a
. m a a, W a . I - a n v) a . U a . W
. I . I
~
0 W
- >
. I
v) 0 0 U U 73 L aL E , v)
m E n
r" 2 a,
L I
2 3
3
1 . [5) n
. I
00 O
I-
73 0
rl
c U v) 3 3 Iu
IBS Team
.Database Administrators .System Administrators .Data Security .Management .Sponsors .Developers .Functional Analysts .Configuration Management .Communication .Change Management
Jet Propulsion Laboratory California Institute of Technology
JPL
Challenges
+ + + + + +
JPL
Allowable downtime - Weekend Database Upgrade One-off patches Custom code migrations Bring current Tech Stack to 11.5.8 9.2.x RMAN upgrade
Upgrade Methods
+ +
Traditional follow the doc upgrade Off the wall upgrade method
JPL
Traditional Upgrade
installation instruction + Apply one off patches + Follow 9.2.0.2 database upgrade instructions + Migrate Custom Codes + Validation All Modules
Jet Propulsion Laboratory California Institute of Technology
JPL
JPL
Clone
JPL
Creating an 1l i Instance
+ + +
Clone all l l i components (DB+Tech Stack) t o the private domains. Fresh install 11.5.8 on new 1158 volume. Merge 11.5.5 and 11.5.8 t o final-volume:
- Get the current database Tech Stack: Copy 9i $ORACLEWHOMEfrom 11.5.5
Source to final-volume - Get the existing 11.5.5 Application: Copy $APPLTOP, $OA-HTML & $JAVA-TOP from 11.5.5 Source to final-volume - Get the new 11.5.8 Tech Stack: copy apps csid>ora & c s i d x o m n (exclude $OA-HTML & $JAVA-TOP) from 11.5.8 source to final-volume
JPL
JPL
JPL
Instance validation
+ +
+
Get functional users to validate the instance. Developers verify custom codes still work after the upgrade. Verify Third party software are not affected after the upgrade. Test out new 11.5.8 new functionalities.
JPL
I 0 (3 0
0 .c ,
a ,
U
>
S .v)
W S
3 73
I a ,
c U
L
a a
0 L
L
v)
a , t LL
3 0
Q
a
S
> 3
c ,
E?
c11
t
4
m cu
Go Live
+ + + +
+ + +
Split mirrors. Swap current Tech-Stack volumes with the final volumes from the Private regions (11.5.8). Bring up Oracle Database (11.5.5 & 9.0.1). Apply 11.5.8 d-drivers & all one-off d-drivers to upgrade database t o 11.5.8. Shutdown instance again. Switch $ORACLE-HOME 9.0.1 to 9.2.0.2 Upgrade Oracle Database t o 9.2.0.2
JPL
Ground Rules
2 hours before estimated task start time + Each team to have on site support and alternate during all shifts of the project regardless of the task + All communications to quarterback. + Have management contact of Oracle to get a point of contact for TAR escalation.
JPL
Final Thoughts
+ This method does take up some resources up front. + Reduce the stress and mistakes. + This method reduced 75% production downtime. + You can do it too!
JPL