Don't think so.
Shouldn't it report by database? And overall for the target/server.

Downtime due to scheduled outages is not counted towards the downtime
statistic. If you blackout the target before bringing it down, the
time will not count.

Joel Patterson
Database Administrator
joel.[Email address protected]
x72546
904 727-2546

-----Original Message-----
From: ron
[mailto:oracledba-ezmlmshield-x60657216.[Email address protected]
Sent: Tuesday, April 03, 2007 2:18 PM
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



Oracle LazyDBA home page