Applying a cpu patch in Oracle 10.2.0.4 RAC environment c/w dataguard standby database
From: dba cjb <chris.brown_at_providentinsurance.co.uk>
Date: Mon, 21 Feb 2011 07:16:03 -0800 (PST)
Message-ID: <f3a93363-2303-4abf-b1a7-49694a9c050f_at_x18g2000yqe.googlegroups.com>
I am applying a patch ( 38 ) on production at the week-end on 3 node cluster on oracle 10.2.0.4 / this will also be applied to dataguard standby database on seperate 3 node cluster.
Date: Mon, 21 Feb 2011 07:16:03 -0800 (PST)
Message-ID: <f3a93363-2303-4abf-b1a7-49694a9c050f_at_x18g2000yqe.googlegroups.com>
I am applying a patch ( 38 ) on production at the week-end on 3 node cluster on oracle 10.2.0.4 / this will also be applied to dataguard standby database on seperate 3 node cluster.
os is windows 2003 sp 2
I have practised patch apply on copy production many times and have confidence this will work.
The general order of events will be:-
- Stop production
- Stop Standy
- apply binaries part of patch on production
- apply binarries part of patch on Standby
- Start standby
- Start production
- Apply database scripts to production
I will be unable to test until the week-end
My main concern is that standby can apply archivelogs that were generated from redo before patch / database upgrade as well as logs resulting from upgrade and after
/ especially in rac environment wher application of standby logs generated from independant nodes is not independant
If anyone can allay my fears or point to hints/documentation I would be gratefull
cheers
Chris B
Received on Mon Feb 21 2011 - 09:16:03 CST