RE: Enterprise Manager Restricted Use License

  • From: "Pete Sharman" <pete.sharman@xxxxxxxxxx>
  • To: <mark.brinsmead@xxxxxxxxx>
  • Date: Fri, 10 Apr 2015 02:33:14 +1000

I can’t disagree with that, Mark. :)



Pete



Pete Sharman
Database Architect, DBaaS
Enterprise Manager Product Suite
33 Benson Crescent CALWELL ACT 2905 AUSTRALIA

Phone: <tel:+61262924095> +61262924095 | | Fax: <fax:+61262925183>
+61262925183 | | Mobile: +61414443449

_____

"Controlling developers is like herding cats."

Kevin Loney, Oracle DBA Handbook



"Oh no, it's not, it's much harder than that!"

Bruce Pihlamae, long term Oracle DBA

_____



From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On
Behalf Of MARK BRINSMEAD
Sent: Friday, April 10, 2015 2:28 AM
To: pete.sharman@xxxxxxxxxx
Cc: dmarc-noreply@xxxxxxxxxxxxx; ORACLE-L
Subject: Re: Enterprise Manager Restricted Use License



At the very least, the two may require different availability.

In a lot of places, you might only need the RMAN repository to be available for
an hour or two each day, while if you rely on OEM for monitoring you probably
need it to be available all the time.

On the flip side of that, though, if you have gone to the time and expense of
building an HA infrastructure for OEM, is probably not a really bad idea to
"drop" your RMAN catalog into the same database so you can leverage the HA
features there, too. Loss of an RMAN catalog is not usually a "disaster", but
it can sure be a pain.

As with almost all things "oracle", both alternatives are valid and which
choice is best will depend a lot on your particular needs and preferences.



On Thu, Apr 9, 2015 at 12:08 PM, Pete Sharman <pete.sharman@xxxxxxxxxx
<mailto:pete.sharman@xxxxxxxxxx> > wrote:

You’re reading more into my example than what I meant, Mladen. I’m not saying
either of them are OLTP or DW. Just they have different use cases and may
require different tuning, which is simply easier when things are separated.
Same as it is for OLTP and DW.



Pete



Pete Sharman
Database Architect, DBaaS
Enterprise Manager Product Suite
33 Benson Crescent CALWELL ACT 2905 AUSTRALIA

Phone: <tel:+61262924095> +61262924095 | | Fax: +61262925183 | | Mobile:
+61414443449 <tel:%2B61414443449>


_____


"Controlling developers is like herding cats."

Kevin Loney, Oracle DBA Handbook



"Oh no, it's not, it's much harder than that!"

Bruce Pihlamae, long term Oracle DBA


_____




From: oracle-l-bounce@xxxxxxxxxxxxx <mailto:oracle-l-bounce@xxxxxxxxxxxxx>
[mailto:oracle-l-bounce@xxxxxxxxxxxxx <mailto:oracle-l-bounce@xxxxxxxxxxxxx> ]
On Behalf Of Mladen Gogala (Redacted sender "mgogala@xxxxxxxxx
<mailto:mgogala@xxxxxxxxx> " for DMARC)
Sent: Friday, April 10, 2015 1:53 AM
To: oracle-l@xxxxxxxxxxxxx <mailto:oracle-l@xxxxxxxxxxxxx>
Subject: Re: Enterprise Manager Restricted Use License



On 04/09/2015 11:29 AM, Pete Sharman wrote:

One other point – while you CAN use the same database for your RMAN catalog and
the OMR, I would not recommend that unless you’re short of hardware. The
usages of the two are completely different. Think of it in a similar manner
(though not to the same extent of course) as putting together an OLTP and a DW
database. You would tune them differently – exactly the same as you would for
the RMAN catalog and the OMR.

Which one of the two is OLTP? RMAN catalog is usually very low traffic, almost
no demands. I've even housed my private one on Oracle Express Edition, and it
worked just fine.



--
Mladen Gogala
Oracle DBA
http://mgogala.freehostia.com



JPEG image

Other related posts:

  1. Home
  2. oracle-l
  3. Archive
  4. 04-2015