Re: Enterprise Manager / RMAN

Your setup sounds very similar to mine. I have a management database on its own server which handles OEM, RMAN, and when I was testing it, Oracle Names. Since none of these systems are very heavily used at any one time, the hardware doesn't even need to be that brawny; I just used an old test server. Keeping these "management" systems on their own server separate from the production instances is another protection against failure.

By the way, you don't HAVE to use a recovery catalog for RMAN. The backup info can be stored in the database's control file; it's just more limiting.

-Jason Heinrich

"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.
>
> --
> John Bossert
>
> In what concerns you much, do not think that you
> have companions: know that you are alone in the world.
>
> -- Henry David Thoreau
>
Received on Tue Jan 22 2002 - 05:18:31 CET