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

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

 

  

I'd like you to elaborate on that. I don't understand why multiple
repositories would impact downtime. ... as well as why you would need
multiple repositories.

I'm kind of new to the idea, and admit as of yet have not thought about
it really. But it seems so complex to have more than one repository.

The first thing that comes to mind is dual RMAN catalog databases. One
to back up the other, and vice versa, and maybe to split the backups
they do. But I don't see the analogy really with the repository.

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

-----Original Message-----
From: Amin Adatia
[mailto:oracledba-ezmlmshield-x98029160.[Email address protected]
Sent: Tuesday, April 03, 2007 9:11 PM
To: LazyDBA Discussion
Subject: Re: Architecture for Grid Control Production vs. Non-production

Sorry .. I was not clear in my statement. I agree with your point about
the
blackout. I was trying to say ... to have multiple OEM repositories
because
of the downtime statistics does not make any sense.

Regards
Amin Adatia ([Email address protected]
KnowTech Solutions Inc. (www.knowtech.ca)
(613) 226-8378 Mobile (613) 864-8378
----- Original Message -----
From: "Joel" <oracledba-ezmlmshield-x13570243.[Email address protected]
To: "LazyDBA Discussion" <[Email address protected]
Sent: Tuesday, April 03, 2007 6:16 PM
Subject: RE: Architecture for Grid Control Production vs. Non-production


>I didn't understand your comments. All I am saying if you run a cold
> backup that takes 2.4 hours, then your downtime is 10%. If you tell
OEM
> that those 2.4 hours is a blackout, your downtime will be 0.
>
> I could be wrong, as I have not seen it with my own two eyes. But
that
> is my understanding.
>
> Joel Patterson
> Database Administrator
> joel.[Email address protected]
> x72546
> 904 727-2546
>
> -----Original Message-----
> From: Amin Adatia
> [mailto:oracledba-ezmlmshield-x3583823.[Email address protected]
> Sent: Tuesday, April 03, 2007 5:23 PM
> To: LazyDBA Discussion
> Subject: Re: Architecture for Grid Control Production vs.
Non-production
>
> But maybe the focus is on the downtime -- like the quarterly results
--
> and
> not the management of all databases. If you can do the work with more
> than
> one -- why not have 6?
>
> Regards
> Amin Adatia ([Email address protected]
> KnowTech Solutions Inc. (www.knowtech.ca)
> (613) 226-8378 Mobile (613) 864-8378
> ----- Original Message -----
> From: "Joel" <oracledba-ezmlmshield-x98867803.[Email address
protected]
> To: "LazyDBA Discussion" <[Email address protected]
> Sent: Tuesday, April 03, 2007 2:30 PM
> Subject: RE: Architecture for Grid Control Production vs.
Non-production
>
>
>> 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
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> 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
>>
>>
>>
>
>
>
> ---------------------------------------------------------------------
> 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
>
>
>
>
> ---------------------------------------------------------------------
> 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
>
>
>



---------------------------------------------------------------------
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