I’m not a Cloud Control expert but I use the tool from time to time – and most of my customers are heavy users of it, especially in larger deployments.
If you use Oracle Enterprise Manager Cloud Control 12c (18.104.22.168, 22.214.171.124 or 126.96.36.199) and would like to evaluate your options to upgrade to Oracle Enterprise Manager Cloud Control 13c then please consult the following very useful documentation:
- MOS Note:2095192.1
EM 13c: Checklist for Upgrading Enterprise Manager Cloud Control from Version 188.8.131.52/4/5 to 13c
- Oracle Enterprise Manager Cloud Control 13.1 – Upgrade Guide
If you are searching for the software please find it here:
Just be aware:
As of July 15, 2016 I received several emails and comments by customers about issues with the migration to OEM 13c, e.g.:
- bug 23017970 – – 12c-13c upg failed at repos config “invalid LOB locator specified: ORA-22275”
- bug 23542135 – OMS Upgrade failed during plugin pre-req
Tried upgrade but hit the bug:
Bug 23017970 : 12c-13c upg failed at repos config "invalid LOB locator specified: ORA-22275"
Had to rollback to 184.108.40.206 since there is no resolution to the bug.
Thanks Arun – I have updated the blog post as others have contacted me as well with EM migration issues …
Hello Mike, I am Facundo from Argentina.
I would like to add, that exists a new Note: EM 13c: Checklist for Upgrading Enterprise Manager Cloud Control from Version 220.127.116.11/5/13.1 to 13.2 (Doc ID 2199855.1).
Thanks a lot!!!!
I have an EM12c running OMS and repository on one machine with windows 2008 R2.
I want to upgrade to version 13.2 with separate machines for repository and OMS. Both on new server running windows 2012R2.
To bring the repository to the new server, I would use datapump.
But how can I upgrade / configure the OMS on a new machine.
Is there a way to do this?
Can you provide a step by step guide?
you can’t expdp/impdp the OEM repository database. It’s one of the most complex things ever build within an Oracle database.
You’ll have to copy the database over.
As far as I understand the procedure:
Shutdown the repository database with shutdown immediate.
Then copy it over to the new server.
Start it up (which includes creating the services necessary on Windows).
Then install the new OEM software – and I silently hope/assume that you can tell the install where your repository is located at.
In case this is not the case you may please open an SR unless you can’t find a guideline in the documentation or on MOS.
A few of my clients currently have OEMCC 13.4 installed, and notice that Premier Support for 13.4 ends after April 2023 (just 2 months away)! Also noticing 13.5 Premier Support ends after this December 2023, so there’s no point in us upgrading to 13.5 from 13.4 with such a short timeframe to end-of-life for 13.5.
Oracle calls their 13c Cloud Control product one of their “Flagship products”, but they have no further direction announced that we can find for what is the upgrade path/direction for when 13.5 is out of support! I recall reading somewhere (but can’t find where now!) that Oracle’s direction for OEMCC might be to have customers move their Enterprise Management to PaaS in the Oracle Cloud, but that would require secure VPN between the OCI and on-premises databases.
Do you have an insights on Oracle’s intended direction for upgrade-path after OEMCC 13c ?!?
I will try to find out something about it.
But I see your concern – and page 10 of https://www.oracle.com/us/assets/lifetime-support-technology-069183.pdf confirms your finding.
No problem, Mike!
ACTUALLY! Oracle Corp just announced on Friday (Feb 24) that the Extended Support for OEMcc 13.5 will be free of charge for all 3 years until 2026 !!
See the MOS note here:
Lifetime Support and Support Policies – Oracle Enterprise Manager Overview (Doc ID 1595197.1)
Oracle Development is working on the next OEMCC release >13. While the release date is not available yet, the intention is to overlap it with the Premier Support of 13.5 so it should be before 31-Dec-2023.
And if they do not make it by Dec 2023 we will have at least the Extended Support with the security updates as usual.
Awesome – thanks for the update, Ernst – and this way I learned something as well!