| upgrading 11g to 12c on new windows server [message #663567] |
Thu, 08 June 2017 08:34  |
aviana
Messages: 106
Registered: July 2007
|
Senior Member |
|
|
Hi
My existing production LIVE is oracle 11.2.0.3 on windows server 2008(server A)
To be new LIVE is 12.2.0.1 on windows server 2012(server B)
In server, I installed the oracle 12.2.0.1 software only-did not use the create and configure database option this time but I usually always use that before.(Also have not created the database using DBCA yet
as I am not sure if this needs to be done first) and because I wish to use RMAN to copy the 11g database from existing server to this new server. Does the database creation using DBCA needs to be done on the 12c database first, before doing (backup of RMAN on serverA+ restore on serverBt +perform upgrade script on serverB)?
Have always used the datapump (impdp/expdp) before for upgrading oracle version to a new server but now want to document the RMAN upgrade procedure from 11g to 12c and want to try that method instead .
Looking for help in getting the correct links containing required steps or explain in detail ?I have been reading different documentation but not seeing one with the full detail.
Please kindly guide?
Thanks a lot
Aviana
[Updated on: Thu, 08 June 2017 08:47] Report message to a moderator |
|
|
|
|
|
| Re: upgrading 11g to 12c on new windows server [message #663570 is a reply to message #663568] |
Thu, 08 June 2017 10:05  |
aviana
Messages: 106
Registered: July 2007
|
Senior Member |
|
|
https://docs.oracle.com/database/121/BRADV/rcmdupdb.htm#BRADV010
The above has different methods of database duplication and I am planning to upgrade database from a backup after copying the RMAN
backups to a backup location on server B
But I would like to apply the alter database open resetlogs upgrade after this and What I am looking for is RMAN duplicate/clone procedure but at the end alter database open resetlogs upgrade option.
But RMAN duplicate procedure needs me to connect to the auxiliary instance but for this the database on server needs to have been created beforehand, that's why I asked about creating the database first on server B.
|
|
|
|
| Re: upgrading 11g to 12c on new windows server [message #663571 is a reply to message #663570] |
Thu, 08 June 2017 11:14 |
John Watson
Messages: 8960
Registered: January 2010
Location: Global Village
|
Senior Member |
|
|
Not quite. This is wrong,
Quote:But RMAN duplicate procedure needs me to connect to the auxiliary instance but for this the database on server needs to have been created beforehand, that's why I asked about creating the database first on server B. you cannot connect to a database because (as you say) the database does not exist. You create an instance, and connect to that. The docs do describe creating the auxiliary instance. When you duplicate the database to the auxiliary, use the NOOPEN clause to leave the database in mount mode. Then you can open resetlogs upgrade.
|
|
|
|
| Re: upgrading 11g to 12c on new windows server [message #663573 is a reply to message #663567] |
Thu, 08 June 2017 11:40 |
 |
EdStevens
Messages: 1376
Registered: September 2013
|
Senior Member |
|
|
|
John Watson gave you good advice. But to perhaps dispel some mis-conception, when you restore or duplicate a database from a backup, you are 'creating' a database. The database is really nothing but a bunch of data files (and I use the term broadly, it actually includes the control files, redo log files, spfile, and data files, but to the os they are all just "files"). When you restore or duplicate from backup, you a re-building those files - from scratch - from the backup pieces. So there is nothing to "pre-create", except in the case of a Windows system, when you need to pre-create the supporting windows service, using the oradim utility.
|
|
|
|
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
