Install: using existing database vs creating new database

Question

Which one do you recommend?

Answer 1

Hans has done a good job pointing out the pros and
cons but I reject some of his reasons for using the
default database:I also reject some of the reasons I state - but I state them as they need to be presented before they can be rejected. <g>
My point is simple - you gather all the reasons first and then accept or reject based on your specific environment. What works for me may not work for you.
>
- potentially tuned to EM needs;
==> Read the install notes for oracle recommended settings...not hardHow many people read any install manual? Especially these days ...
People will probably skim the internet to determine that it's possible to install on a separate database, and will often target a database that has sufficient space.
I doubt if 1 in 10 would even consider that the OMR will put a load on the CPU or would think to change the DBs settings based on a compination of "what si best for the applications in the DB" and "what is best for the OMR"
>
- on the same machine as OMS;
==> an existing database can also be on the same
machineIf the OMS load pushes the machine to require another CPU and that forces the purchase another CPU license, then I would consider getting the OMS the h*^l off the machine on to a separate server.
AFAIK, you pay for the DB license, but there is no per-cpu charge for the OMS. So, like any client, you can install the OMS anywhere you want. I'd appreciate any documentation to the contrary.
>
- specific DB version selected (that is known to work
woth OMR);
==> you should check metalink for the latest versions
and what is supported ANYWAY...Again - you assume person reads. <g>
/Hans