dbTalk Databases Forums  

Patching in an environment used for dataguard

comp.databases.oracle.server comp.databases.oracle.server


Discuss Patching in an environment used for dataguard in the comp.databases.oracle.server forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
dba cjb
 
Posts: n/a

Default Patching in an environment used for dataguard - 09-27-2010 , 10:14 AM






9777078 Patch Number 38

Oracle 10.2.0.4 Enterprise / windows 2003 server

I am looking to plan a patch to production and then a patch to
dataguard environment

My general ( simplified ! ) plan for dataguard / following production
patch will be as follows

* Stop database
* Apply software
* Re-start database ...with the hope that continued application of
archive logs will apply the patch database changes already applied to
production



cheers
Chris B

Reply With Quote
  #2  
Old   
Steve Howard
 
Posts: n/a

Default Re: Patching in an environment used for dataguard - 09-27-2010 , 02:24 PM






On Sep 27, 11:14*am, dba cjb <chris.br... (AT) providentinsurance (DOT) co.uk>
wrote:
Quote:
9777078 Patch Number 38

Oracle 10.2.0.4 Enterprise / windows 2003 server

I am looking to plan *a patch to production and then a patch to
dataguard environment

My general ( simplified ! ) plan for dataguard / following production
patch will be as follows

* Stop database
* Apply software
* Re-start database ...with the hope that continued application of
archive logs will apply the patch database changes already applied to
production

cheers
Chris B
Hi Chris,

It's always safer to ask Oracle, but we have used the steps in your
plan several times with no issues, so this should work. The database
script changes run on the production database will be propagated to
the standby via the redo stream. If you are *really* concerned, you
can try to tie the application of the patch as close as possible to
when you stop applying redo on the standby, so they "mostly" match.

However, as noted, we have never had an issue when doing this.

Regards,

Steve

Reply With Quote
  #3  
Old   
joel garry
 
Posts: n/a

Default Re: Patching in an environment used for dataguard - 09-27-2010 , 04:13 PM



On Sep 27, 12:24*pm, Steve Howard <stevedhow... (AT) gmail (DOT) com> wrote:
Quote:
On Sep 27, 11:14*am, dba cjb <chris.br... (AT) providentinsurance (DOT) co.uk
wrote:



9777078 Patch Number 38

Oracle 10.2.0.4 Enterprise / windows 2003 server

I am looking to plan *a patch to production and then a patch to
dataguard environment

My general ( simplified ! ) plan for dataguard / following production
patch will be as follows

* Stop database
* Apply software
* Re-start database ...with the hope that continued application of
archive logs will apply the patch database changes already applied to
production

cheers
Chris B

Hi Chris,

It's always safer to ask Oracle, but we have used the steps in your
plan several times with no issues, so this should work. *The database
script changes run on the production database will be propagated to
the standby via the redo stream. *If you are *really* concerned, you
can try to tie the application of the patch as close as possible to
when you stop applying redo on the standby, so they "mostly" match.

However, as noted, we have never had an issue when doing this.

Regards,

Steve
Interesting tidbit from Tanel about standby binaries I happened to
notice this morning while looking for something else:
http://www.freelists.org/post/oracle...AFILE-HEADER,4

jg
--
@home.com is bogus.
"ASM adds another layer of distraction in that it creates and manages
the files internally so that from an OS point of view you may have
very few files (assign whole disks to ASM and let if parcel out the
space to the databases)." - Mark Powell
I agree, and not in the abstract! :-)

Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.