This content has been marked as final. Show 3 replies
220.127.116.11 is a patch that can only be applied to a 18.104.22.168 install. Since this version is out of support, you will need to create a SR with Support, and they will provide a link to the 22.214.171.124 software, assuming you have paid for Extended Support for 11gR1.
How big is the database ? How much downtime can you afford ? One option may be to perform a full export from existing hardware, create a new empty 126.96.36.199 database on the new hardware and performing an import - this will bypass the requirement of installing 11gR1 on the target hardware
I am guessing the options I used back in December 2011 and January 2012 are no longer available, nolonger supported. No we do not have extended suppport for 11gR1.
Current database 188.8.131.52.0 is 15.9 GB. Currently available space on oracle directory is 28.6 GB. Flash_recovery_area is at 114 GB so there is room to for an upgrade on this OS by cleaning up the flass recovery area, it will be slow. By the way the OS is Windows Server 2003 x64 AMD 64 x2 Standard Edition, not the 32-bit.
I can do an export (datapump or export?) and bring over just the schemas from the 184.108.40.206.0 database, to get it into a new 11.2.0.X.0 database? Is this your recommended approach to getting over to another non-conectable network (Widows Server 2008 R2 that will be running? Can we go to 11.2.0.X.0 the lastest release this way? Is there a document with this option?
Most of Oracle's documentation now shows upgrading to 11.2.0.X.0 on the same box. We do have to get off thie node and its network though, and so not have tha luxurary of closning or using RMAN 'duplicate database' options.
Will using a 220.127.116.11.0 backup now be out of the question?
Yes, you can upgrade using expdp and impdp - 16G is peanuts ;-)