Re: Enterprise Manager / RMAN

I haven't set this up myself, but did perform an investigation on much the same thing (they didn't want to pay for the extra hardware).

Blue-sky thinking - a separate server for OEM, and one for RMAN, and one for the RMAN backup.

Realistically, I would push for a separate OEM server since, depending on what you are doing, it may need a bit of grunt. Also, although Oracle will tell you that OEM doesn't use many resources, try convincing your users that your database running OEM isn't affecting their performance.

For RMAN, I would recommend placing it on a Production server since it is effectively a Production instance, albeit yours (or the DBA group). Don't forget to have another one on another server backing this one up for redundancy. RMAN isn't resource hungry, and is only being used when the others are quiet by its nature.

If you are really paranoid, the RMAN and RMAN backup servers should be at different sites.

Hope that helps.

John Bossert <jbossert_at_usa.net> wrote in message news:<3C4B582A.5010608_at_usa.net>...
> For the management of a small but mission-critical production environment, how are people deploying
> RMAN (which requires its own database/instance for the catalog) and Enterprise Manager (which
> requires its own database/instance?)
>
> Is the best/simplest approach just a small(?) machine running an instance dedicated to these two tools?
>
> I'll have half a dozen production databases spread across slightly fewer machines and another 3-4
> development/test systems.
>
> The idea of piggy-backing "support" tools on the production systems seems awkward to me.
>
> I'm looking for any sort of guidelines and/or best practices. Thanks in advance.
Received on Mon Jan 21 2002 - 19:25:45 CST