Re: Upgrade OEM repository from 12c to 13c

Thanks Rich,

I think that this covers moving both the OMS and the repo, but I don't want to move OMS at all. I'd rather create a fresh 13c installation from scratch, but using (a copy of) the old repo as the existing repo, which then must be upgraded.

The goal is to leave all the crud that has built up over the years behind and start over with a relatively clean installation, whilst retaining the targets and their history.

That is

1. install RDBMS 12.2.0.1 on the new VM
2. create a clone from the old 11g repo DB and upgrade to 12.2
3. install fresh OMS 13.2 on the new VM, with cloned database as "pre-existing repository"
4. upgrade the 12.1.0.5 OMS repo to 13.2

I wonder if step 4 is so automatic that it just did not occur to the OEM maintainers to mention it?

RHEL7 (and friends) is simply the one that will be supported for longest. Even with this version, upgrading the OS is still discouraged (although apparently supported)... going to 7 just gives us the most joy out of this upgrade :)

We install all our Linux servers without windowing system, that's the easiest. How often do you need the console anyway... I only ever use it to follow system reboots.

Cheers,
Tony

On 23/03/17 22:40, Rich J wrote:
>
> On 2017/03/23 06:46, De DBA wrote:
>
>> I'm hoping to upgrade our OEM 12c in the near future to the latest & greatest. Since the physical server is well and truly end-of-life, as is the RHEL5 that runs it, we have decided to take advantage of the situation to create a new VM with RHEL7 on it and install OEM13c from scratch, with a gleaming new 12cR2 database to put it's repository in.
>>
>> Here is the catch - I'm sure it's possible to migrate the 12c repository to the new server and upgrade it, but in all my googling I've only been able to find posts from people in the same situation as I. There's plenty of doco on how to start from scratch, and also on how to upgrade an existing installation, but none whatsoever on migrating the repository to a beautiful new installation.
>>
>> If you've got any experience with this scenario, or know of some documentation, please share?
> It seems like there's been a lot of chatter about this very topic lately:
> http://www.freelists.org/post/oracle-l/OMS-move-to-new-Hardware,1
> I'm in about the same situation as you. From what I've found, to move to RHEL7 will require an intermediate jump to RHEL6, if you follow the certifications of EM versions to OS versions. Here's a very abbreviated table of the EM version support matrix:
> OMS Linux x86-64 Repo DB Target Oracle DB
> 13.2 OL6, OL7 12.1.0.2 11.2.0.3, 12.1.0.2
> 12.1.0.5 OL5, OL6 11.2.0.3, 12.1.0.2 11.2.0.3, 12.1.0.2
>
> I have yet to see any value in moving to OL7 in my situation, so I'll likely stick with OL6 for now (I hate Gnome3 anyway), saving the intermediate jump.
>
> HTH! GL! And don't forget to share the fun you'll be having with your move!
>
> Rich
>
> p.s. For the sake of this and most other messes, I treat RHEL versions to be the same as OL (Oracle Linux) versions.
>
>

--
http://www.freelists.org/webpage/oracle-l