No question at this time
DBA Top 10
1 M. Cadot 7200
2 B. Vroman 3100
3 J. PĂ©ran 2100
4 A. Kavsek 1400
5 P. Tsongayinwe 1300
6 P. Wisse 600
7 D. Walgude 400
7 J. Schnackenberg 400
9 J. Alcroft 200
10 A. Hudspith 100
10 D. Johnson 100
10 B. B 100
About
DBA-Village
The DBA-Village forum
Forum as RSS
as RSS feed
Site Statistics
Ever registered users48684
Total active users1329
Act. users last 24h2
Act. users last hour0
Registered user hits last week44
Registered user hits last month235
Go up

Out-of-place patching for RAC - official documentation
Next thread: File system size is 100%
Prev thread: opatch error 255 in Azure (Azure is here important)

Message Score Author Date
Hello Gurus, are you able to point me to to off...... Matej Pagac Aug 01, 2022, 14:42
Hi Matej, in general you just have to do this: ...... Score: 400 PtsScore: 400 PtsScore: 400 PtsScore: 400 PtsScore: 400 Pts Jan Schnackenberg Aug 02, 2022, 08:53
Hello Jan, thanks for the reply and confirmatio...... Matej Pagac Aug 02, 2022, 12:55
Well, you're somewhat right. But this method re...... Jan Schnackenberg Aug 13, 2022, 22:20

Follow up by mail Click here


Subject: Out-of-place patching for RAC - official documentation
Author: Matej Pagac, Slovakia
Date: Aug 01, 2022, 14:42, 16 days ago
Os info: any
Oracle info: 19.14
Message: Hello Gurus,

are you able to point me to to official documentation/metalink on how to perform out-of-place patching for 19c RAC database (apart from Oracle Fleet Patching)?

So far I was able to find only this (mentioned in GI patch README as):
https://docs.oracle.com/en/enterprise-manager/cloud-control/enterprise-manager-cloud-control/13.4/optch/place-patching.html#GUID-10EF5AF2-BB81-488B-8F5A-362C04E4E6BE

Grid Infrastructure Out of Place ( OOP ) Patching using opatchauto (Doc ID 2419319.1)


Problem is that currently I do not have a test environment to test it, but given a task to perform such operation.
2419319.1 - Scenario proceed to switch and patch all databases running from the specified Oracle home (which is not our case, as we want to patch unly subset of databases running from single OH).
There seems to be "-database" option, however when asked Oracle Support for confirmation, their response was that it is not possible to limit number of database to be switched/patched using opatchauto.
And since I cannot test it nor did I find any example on the net, I just have to believe them :)

As home cloning using clone.pl is also deprecated, oracle stated that recommended approach is to install new home(either new-new or created as gold image from existing one) and apply the patches:
19.x:Clone.pl script is deprecated and how to clone using gold-image (Doc ID 2565006.1)


So safer way seems to be to create gold image fom existing home, do the SW installation, apply patches, copy dbs/tns (read only home not used), adjust crs, start DB from new home and apply the datapatch.

As I do not want to miss some steps, I'm asking for your advice, as I would like to avoid similiar problems:
https://mikedietrichde.com/2021/08/12/dbms_optim_bundle-and-out-of-place-patching/

datapatch -verbose Fails with Error :" Patch xxxxxx: Archived Patch Directory Is Empty" (Doc ID 2235541.1)


Or any document describing at least best practices for such scenario?


Thanks,
mTj
Goto: Reply - Top of page 
If you think this item violates copyrights, please click here

Subject: Re: Out-of-place patching for RAC - official documentation
Author: Jan Schnackenberg, Germany
Date: Aug 02, 2022, 08:53, 15 days ago
Score:   Score: 400 PtsScore: 400 PtsScore: 400 PtsScore: 400 PtsScore: 400 Pts
Message: Hi Matej,

in general you just have to do this:

1. Install new ORACLE_HOME. Either simply reinstall and directly patch to the desired version or clone the existing ORACLE_HOME and install the patch there. The "Golden Image" installation is basically a clone, so that is the same for me. Cloning also would include your TNS-information, so you wouldn't have to do that, again.

2. Shutdown your database

3. Change the ORACLE_HOME using "srvctl modify database"

4. Start database

5. Run datapatch in the new ORACLE_HOME


The pitfall from Mike Dietrichs blog is just a minor issue (I am the Jan he mentions there. ;) ). Apart from that, everything worked smoothly.

Regards,
Jan
Your rating?: This reply is Good Excellent
Goto: Reply - Top of page 
If you think this item violates copyrights, please click here

Subject: Re: Out-of-place patching for RAC - official documentation
Author: Matej Pagac, Slovakia
Date: Aug 02, 2022, 12:55, 15 days ago
Message: Hello Jan,

thanks for the reply and confirmation.

I just found it really puzzling that Mike used stated that OOP is clearly our recommendation, but yet I'm unable to find any official documentation on how to achieve this on per database basis (not on oracle_home basis).

Anyway, even though the patches should be cumulative, I would most likely bring the new home to the current version, and then patch to new desired version.
As such operation takes just few more commands and does not require downtime, but insure more mental peace for myself :)

In case I find something interesting, will update this post :)

Thanks,
mTj
Your rating?: This reply is Good Excellent
Goto: Reply - Top of page 
If you think this item violates copyrights, please click here

Subject: Re: Out-of-place patching for RAC - official documentation
Author: Jan Schnackenberg, Germany
Date: Aug 13, 2022, 22:20, 4 days ago
Message: Well, you're somewhat right.

But this method really just boils down to what I wrote. It's much easier, and the fallback much safer, than doing an inplace update.

So they probably just didn't think that this needs to be written down. You know, being too familiar with a problem causes you loose sight of the complexity of the issue.

Regards,
Jan
Your rating?: This reply is Good Excellent
Goto: Reply - Top of page 
If you think this item violates copyrights, please click here