Re: Simple OEM Deployment Advice needed

If your OEM users are going to be looking at the same databases, you might prefer a central management server. That way everything that gets stored in the management server repository will be the same for every user. Otherwise things will get out of sync quickly. If each DBA is responsible for a non-overlapping set of databases you could have separate repositories, although it's a waste of resources.

Van

"Michael J. Moore" <hicamel_at_home.com> wrote in message news:dzRA5.260885$i5.3592107_at_news1.frmt1.sfba.home.com...
> Sorry, I guess my question was not very clear. Obviously, only the DBA
 types
> of people will be allowed to use OEM.
> If I understand correctly, there are 2 ways that OEM can be deployed, 1)
> full install on each client, 2) OEM Server on a server box, and thin OEM
> client on each client machine.
>
> So, Is my understanding correct? And if so...
> is there any advantage to option 2, other than client side resources?
> thanks,
> Mike
>
> "Sybrand Bakker" <postbus_at_sybrandb.demon.nl> wrote in message
> news:970177971.14345.2.pluto.d4ee154e_at_news.demon.nl...
> > If you want to have every user to be able to shutdown the database, yes,
> > please install it on every pc you can find.
> > OEM is a console/DBA product, it is not an end-users product. If they
 have
> > it they really can creat havoc.
> >
> > Regards,
> >
> > Sybrand Bakker, Oracle DBA
> >
> > "Michael J. Moore" <mNiOcShPaAeMl.j.moore_at_wcom.com> wrote in message
> > news:qBNA5.20$Xw.744_at_pm01news.wcom.com...
> > > Is there any advantage to having a centeralized OEM server, over
 having
 each
> > > user with a complete OEM on his machine? I mean OTHER than the
 resources
> > > required for each individual machine.
> > >
> > > Thanks,
> > > Mike
> > >
> > >
> >
> >
>
>
Received on Fri Sep 29 2000 - 20:57:44 CEST