IMHO, installing OEM 12c along Oracle VMM on the same machine will greatly increase the resource usage of your server.
OEM 12c requires a lot of RAM: on the same server you'll have Oracle DB, Oracle WebLogic and, if you need it, Oracle BI.
About your questions:
1. there are no official documents stating the contrary but, if a problem arises, I think Oracle will suggest you to keep the two separated
2. OEM 12c is installed under /u01/app/oracle/Middleware and shares nothing from your DB installation
3. when installing OEM you can point the installer to an existing Oracle DB instance; it will create its own schema without harming the Oracle VMM schema.
From my 2+ year experience with our Oracle VM production cluster, I had to reinstall Oracle VMM a few times to resolve some bugs (i.e. running tasks never ending), sometimes deleting the Oracle DB instance. I would'nt do that with OEM.
A final note: Oracle VMM 3.2 uses MySQL as its default database.
Thank you for your reply!
The irony with my OEM and OVM on the same box question is that the Oracle Sales & Support teams as well as public Marketecture has been recommending collocating OEM & OVM!
I agree with you 100% about resource consumption, and considering how often we must restore/reset Oracle VM Manager I am curious how supportable an OEM & OVM install is on the same box. 99% of my customers are not interested in supporting MySQL, i.e. the DBAs know Oracle not MySQL. As long as Oracle VM Manager resets (DB deletes) and UUID restores (uninstalls and re-installs) will not damage OEM its all good.
Thanks again for your support!
I see no problem co-locating on the same server. The Oracle VM manager really doesn't take that many resources and is rather small compared to a OEM 12c installation. I would plan for a standard OEM installation and then throw in a little extra for OVM.
OEM has a few known memory issues that have work arounds or have been fixed in recent versions. If you're having memory issues, then search for the fixes. Instead of doing a UUID restore, you should try doing a database restore or a schema restore. A simple periodic export of the OVM schema should give you the ability to restore the OVM schema without touching the entire database. Never tried it, but it should be fine. I can't think of reason it wouldn't work.
There is a VM template for the latest version of OEM. With the complexity associated with setting up a proper OEM environment, I would just build a VM guest from the template... but I don't think you would run into a lot of problems running the VM manager and OEM products against the same database or on the same servers. The only issue I can see is possible port conflicts.
Thank you for your reply!
Regarding the latest OEM template, can you confirm that it does indeed work? I gave up on the OEM R2 template due to the following issue, (ironically the OEM R1 template worked):
- Enter the passwords and email address for Oracle Enterprise Manager The passwords and email address for Oracle Enterprise Manager are mandatory. Unfortunately, there is a VERY short timeout value before the installer moves forward with a NULL entry, i.e. if your not paying attention, the installer times out and defaults to "null", and the setup will continue without installing the middleware home. If the passwords and email address are not entered the setup completes without installing the Middleware home. When this happens, kill the virtual machine, delete it, and start over.
If it works, I'll give it a whirl again!
Sorry. Can't confirm the newest template works. I've only used R1. Haven't had the chance to check out release 2. Seems like there is always something else to do . Hopefully I'll get a change to do it soon. I'd really like to use R2. R1 is really flaky at times.