RE: Architecture for Grid Control Production vs. Non-production

RE: Architecture for Grid Control Production vs. Non-production

 

  

Hi,

I run with a single repository, with multiple users who all view their own
targets. For example I have a prod user and a test user. I only report stats
for our prod targets.

Michael Peel
-----Original Message-----
From: ron [mailto:oracledba-ezmlmshield-x60657216.[Email address protected]
Sent: 03 April 2007 19:18
To: LazyDBA Discussion
Subject: Architecture for Grid Control Production vs. Non-production

DBA architects
We are going to deploy OEM Grid control and want to put agents on all
boxes, both production and non-production (QA, Test, etc).

Would I setup a separate OMS and repository for non-production or put it
into one repository?

If I put it all in one repository, won't the reporting get polluted by
non-production data? i.e. It will show a lot of downtime due to
non-production being down.

Thanks for the guidance.


---------------------------------------------------------------------
TO REPLY TO EVERYBODY , PLEASE CLICK REPLY-ALL, NOT JUST REPLY
To post a dba job: http://jobs.lazydba.com
To Subscribe : http://www.LazyDBA.com
To unsubscribe: http://www.lazydba.com/unsubscribe.html


**********************************************************************
This e-mail is confidential and may be privileged.
It may only be read, copied and used by the intended recipient.
If you have received it in error please contact the sender immediately
by return e-mail. Please then delete the e-mail and any copies of it
and do not use or disclose its contents to any person.
**********************************************************************
Registered Office: Farncombe House, Broadway, Worcestershire, WR12 7LJ

AccuRead Limited Registered Number: 3076187 England
GSL UK Limited Registered Number: 3333860 England
Global Solutions Limited Registered Number: 3189802 England
**********************************************************************


Oracle LazyDBA home page