RE: RMAN Duplicate from lower patchset to higher patchsets
Date: Thu, 23 Apr 2009 11:16:52 -0400
I know this is a hassle and a pain but if you're stuck with that:
- what would you do if the patch was no good and you needed to resort to previous version(i'm assuming you took 10.2.0.3 and patched in place to 10.2.0.4)
- why not keep the 10.2.0.3 and add a 10.2.0.4 tree, realizing 2 oracle homes BUT it takes care of #1 above and doing the clone of production, startup the db in production version and do the upgrade to 10.2.0.4.
Or am I missing something here?
Joe Testa, Oracle Certified Professional Senior Consultant
Data Engineering and Administration
Interested in helping out your marriage?
Ask me about "Weekend to Remember"
Dec 11-13, 2009 here in Columbus.
"Vishal Gupta" <vishal_at_vishalgupta.com> To:
04/23/2009 11:06 AM
RE: RMAN Duplicate from lower patchset to higher patchsets Sent by:
Anyone got any ideas ?
From: oracle-l-bounce_at_freelists.org on behalf of Vishal Gupta
Sent: Wed 22/04/2009 23:25
Subject: RMAN Duplicate from lower patchset to higher patchsets
I am sure lot of people might have faced this problem. From what i have researched so far, RMAN does not support duplication (i am not talking restore here, but duplicate clone) between different version of oracle.
So if you have a very critical system, then obvious thing to do would be upgrade dev, then test , then production. But let's throw another complication into the picture, if lot of your dev and test instances are refreshed from production RMAN backup on a daily basis. Then you can't really upgrade dev/test first and leave production, until your testing is finished. RMAN does not allow duplicating a database from older version to newer version.
Though there is a procedure to restore database and then upgrade/downgrade
alter database open resetlogs upgrade/downgrade; now follow the downgrade/upgrade steps;
As anyone found any way of duplicating database using RMAN from say 10.2.0.3 to 10.2.0.4?