RE: OEM Licenses
Date: Wed, 26 Aug 2015 23:32:11 +0100
Message-ID: <DUB113-W10171CE90E739D7A576D87D85600_at_phx.gbl>
Pete,
I have worked with clients who have just one OEM and clients who have several, usually a PROD/TEST split. However, section 1.5 of the license doc says:
"Additional database options or additional servers for disaster recovery require separate licensing." suggest if you don't use DR or RAC the DB's are free
but
"Customers receive one single-instance database with the Cloud Control", suggests you're only allowed a single repository no matter how big/diverse/segmented your estate.
Has anyone who has had the Oracle audit recently been picked up on multiple OEM repositories? Neil
1.5 Enterprise Manager Restricted-use LicenseEnterprise Manager includes a restricted-use license of the Oracle Database for use only with the Oracle Management Repository or other complementary repositories included with Enterprise Manager (such as, AWR Warehouse, Ops Center, Real User Experience Insight, Load Testing, and Test Manager). Additional database options or additional servers for disaster recovery require separate licensing. Customers receive one single-instance database with the Cloud Control, or RMAN, repository. To protect the repository with Data Guard, customers need to purchase a license for the standby site. To protect the repository with Oracle Real Application Clusters, customers must license the second node for the database, and both nodes require an Oracle Real Application Clusters license.
Date: Wed, 26 Aug 2015 13:09:35 -0700
From: pete.sharman_at_oracle.com
To: neil_chandler_at_hotmail.com; Oracle-L_at_freelists.org
Subject: RE: OEM Licenses
Neil We have many customers that have multiple EM installations in their environments. The reasons for that might include: · Having a dev/test environment so they can test patches· Having separate environments for separate business units – this one is a more political decision than technical, as you can control access with privileges instead but some customers have been forced down this route by business rules not technical ones.· Network separations that mean one EM environment cannot reach all targets – generally this one can be addressed by proxy settings but not all the time. Having said that, there is no reason (other than those just mentioned) that I can think of for multiple EM environments, and certainly no reason for per instance environments at all. That is the arena of EM Database Express, not EM Cloud Control. From a licensing perspective, providing you are following the guidelines in section 1.5 of the doc, you should be good to go with multiple environments. BUT keep in mind my comments above. J
-- http://www.freelists.org/webpage/oracle-lReceived on Thu Aug 27 2015 - 00:32:11 CEST