3. Oracle Licensing
how to approach Oracle Licensing (our advice)
ā¢ Oracle has thousands of software lines, but database, middleware is more than 50% of
the install base. Learn technology first and when you have a grasp of how to license
these products ā then you learn something new.
ā¢ We have helped more than 100 companies with Oracle Licensing an estimate is that 70%
of all the work is about Oracle Technology (Db and MW)
ā¢ Very few people has the knowledg, its mostly important to understand the basics and then
understanding where you can research and find out the answers as you do the work.
ā¢ Oracle licensing and contracts can be highly customized, not standard licensing.
ā¢ Always start with reviewing your contracts ā never assume customers have standard
licensing unless you cant find the licensing agreement.
4. About the Products / Acquisitions
6000+
Product Lines
25000+
Global Partners
120+ Acquisitions up to 2016
Some of the most well known
acquisitions:
Siebel | Peoplesoft/JDE | BEA | Hyperion | Sun
Microsystems
5. About LMS / Licensing
LMS = Oracle in-
house audit org.
Mostly managed from
Romania since 2018
Most common products lines and metrics:
ļ¶ Oracle Database | NUPs and Processor
ļ¶ Weblogic | NUPs and Processor
ļ¶ E Business Suite | Application User/ Enterprise
Metrics
SIA = ānewā
advisory team at
Oracle
Thousands of Metrics
(Legacy and New)
Orders have Terms and
Conditions each one can
be different
Master Agreement also
has Terms and Conditions
*(NUP = Named User Plus)
6. Licensing Licensing
The basics.
ā¢ Start with learning Oracle Database
ā¢ Enterprise and Standard Versions.
ā¢ Enterprise has 26 different ādatabase optionsā functionality that requires additional licensing.
ā¢ Enterprise has core licensing.
ā¢ Standard Edition has CPU/Socket Licensing.
ā¢ There are Oracle DB versions 1-18. If you have a license you can use any version! No need to
purchase a new license for a new version. As long as you are paying the annual support
renewal an Oracle customer have the right to update the software without paying any uplift or
upgrade fees.
ā¢ You can āmigrateā exchange Standard Edition licenses towards Enterprise Edition for a fee.
7. Oracle Database Licensing Basics
Licensing is not just a priceā¦
METRIC TYPE
TERM SUPPORT
Processor
Named User Plus (NUP)
Perpetual (most common)
1,2,3,4,5 years
Full Use
Application specific (ASFU) (partner)
Embedded (partner/OEM)
Prop application hosting
(Partner/Hosting)
Software Update
License & Support
Requires renewal every year
8. ā¢ Perpetual = 90% + of all licenses we come across.
ā¢ 1,2,3,4,5 year Licensing are discounted (term licenses).
ā¢ Term licenses are usually used for time limited projects, migration or resolve
under licensing during an audit.
ā¢ ASFU/ESL Licenses ā compliance is the partner/application vendor.
ā¢ ASFU/ESL Licenses ā any audit of those environments must go thru the
application vendor. (contractually)
ā¢ Renewal of support is usually treated as a auto-renewal when there are
possibilities to negotiate.
Summary
10. ā¢ Used in environments where users can
be counted
ā¢ Based on users and non-human
operated devices accessing the
database
Licensing Models
Named
User Plus
Per Processor
BREAK-EVEN:
1 processor license =
50 NUP licenses
ā¢ Used in environments where users cannot be counted
e.g. internet users
ā¢ Based on the number of processors, cores (EE) or
sockets (SE and SE1) in the server on which the
Database is installed
12. Licensing Technology Products:
Named User Plus
Named User Plus (NUP licenses)
ā¦.is defined as an individual authorized by you to use the programs which are installed on a
single server or multiple servers, regardless of whether the individual is actively using the
programs at any given time. All of the remaining provisions of this definition apply only with
respect to Named User Plus licenses, and not to Named User licenses.
A non human operated device will be counted as a named user plus in addition to all individuals
authorized to use the programs, if such devices can access the programs. If multiplexing
hardware or software (e.g., a TP monitor or a web server product) is used, this number must be
measured at the multiplexing front end.
Automated batching of data from computer to computer is permitted. You are responsible for
ensuring that the named user plus per processor minimums are maintained for the programs
contained in the user minimum table in the licensing rules section; the minimums table provides
for the minimum number of named users plus required and all actual users must be licensedā¦
13. PROCESSOR
...shall be defined as all processors where the Oracle programs are installed and/or running.
Programs licensed on a processor basis may be accessed by your internal users (including agents
and contractors) and by your third party users.
The number of required licenses shall be determined by multiplying the total number of cores
of the processor by a core processor licensing factor specified on the Oracle Processor Core
Factor Table which can be accessed at http://oracle.com/contracts. All cores on all multicore chips
for each licensed program are to be aggregated before multiplying by the appropriate core
processor licensing factor and all fractions of a number are to be rounded up to the next whole
number.
When licensing Oracle programs with Standard Edition One or Standard Edition in the product
name, a processor is counted equivalent to an occupied socket; however, in the case of multi-chip
modules, each chip in the multi-chip module is counted as one occupied socket.....
Licensing Technology Products:
Processor
14. How many processor licenses are required for Database EE?
ā¢ Single core processors: A license for each CPU used to run Oracle DB EE
ā¢ Multi-core processors: # CPU x # cores x Processor factor
How many NUP licenses are required for Database EE?
The license minimium for Oracle Database Enterprise Edition is 25 Named User Plus per processor (Taking
into account Oracleās processor definition)
When licensing an environment by Named User Plus check the license minimum and the actual # of users.
Whichever is greater needs to be licensed!
Licensing Database Enterprise Edition
15. Oracle Database
Oracle Database restrictions
ā¢ Oracle Database Standard Edition Two may only be licensed on servers that have a maximum
capacity of 2 sockets and 16 threads.
ā¢ Oracle Database Standard Edition One may only be licensed on servers that have a maximum
capacity of 2 sockets.
ā¢ Oracle Database Standard Edition may only be licensed on servers that have a maximum
capacity of 4 sockets.
ā¢ Oracle Database Enterprise Edition has NO license restrictions (hw)
16. Licensing Database Standard Edition, One and 2
How many processor licenses are required?
ā¢ Oracle Database Standard Edition 2 : 1 Processor License per occupied socket (max 2 sockets, 16 threads)
ā¢ Oracle Database Standard Edition: 1 Processor License per occupied socket (max 4 sockets)
ā¢ Oracle Database Standard Edition One: 1 Processor License per occupied socket (max 2 Sockets)
How many Named User Plus Licenses are required?
ā¢ The License minimum for Oracle Database Standard Edition 2 is 10 Named User Plus (per server)
ā¢ The License minimum for Oracle Database Standard Edition is 5 Named User Plus
ā¢ The License minimum for Oracle Database Standard Edition One is 5 Named User Plus
(When licensing Oracle programs with Standard Edition One, Standard Edition 2 or Standard Edition in the product name, a processor is counted
equivalent to a socket; however, in the case of multi-chip modules, each chip in the multi-chip module is counted as one occupied socket.)
17. Product Selection: Exercise
Which database version can be installed?
EE
Hardware:
ProLiant DL 380
2 CPU Dual-Core Intel
2 sockets
Hardware:
IBM P 550Q
2 CPU Quad-Core Risc
4 sockets
18. Licensing Technology Products:
Exercise
Company A ā 460 employees all have access to Database
Runs Oracle Database Enterprise Edition on 2 servers
with 2 Quad Core Processors (Intel) each
(Total of 2 servers x 2 processors)
How many Named User Plus Licenses are required?
19. Licensing Technology Products:
ANSWER:
ā¢ 2 servers x 2 processors each with 4 cores ( 8 cores per server)
ā¢ Total cores 16 cores (16x 0,5= 8 CPU Licenses)
ā¢ Oracle Licensing minimum NUP per CPU = 25
ā¢ Minimum nup per server = 100 (4 Oracle CPU per server)
Minimum NUP 2 servers = 200.
ā¢ But here there are 460 users so we need to license this with 460 NUP.
Alternatively you license this with 8x CPU Licenses.
21. Oracle Licensing Basics
Database Recovery ā Backup (Definition)
BACKUP: In this method, a copy of the physical
database structures of the database is made. When the original
data is lost, the backup files can be used to reconstruct the lost
information that constitutes the Oracle Database.
This backup copy includes important parts of the databaseās
physical structures such as control files, redo logs and data
files. These physical files can be stored on a server., storage
array, disk drive, or Compact Disc.
Source: Licensing Data Recovery Environments
22. Oracle Licensing Basics
Database Recovery ā Backup (Example)
ā¢ Staging, test and production
environments are installed on
server 1, which has 6 processors
ā¢ Backup of the production
environment is done on tapes
every night by 1 DBA. These tapes
are stored in the tape storage unit
ā¢ 10 Developers are working on
staging, test and production
environments
ā¢ 500 traders are using the Web site
that resides on production
environment
Source: Oracle Software Investment Guide (SIG)
Illustration #: Backup
10 Developers
500 Traders
Production
Test
Staging
Database EE
6 Processors
Storage Unit
Website
23. Oracle Licensing Basics
Database Recovery ā Failover (Definition)
FAILOVER: In this method, nodes are configured in āclustersā with the first installed node acting as a
primary node. If the primary node fails, one of the surviving nodes in the cluster acts as the primary node. In
this type of environment, Oracle permits its licensed Technology customers to run the Technology Programs
(listed on the Technology Price List) on an unlicensed spare computer for up to a total of ten separate days in
any given calendar year.
The above right only applies when a number of machines are arranged in a cluster and share one disk array.
Once the primary node is repaired, you must switch back to the primary node. Only one failover node per
clustered environment is at no charge for up to ten separate days even if multiple nodes are configured as
failover nodes. When licensing options on a failover environment, the options must match the number of
licenses of the associated database. Additionally, when licensing by Named User Plus, the user minimums
are waived on one failover node only. Any use beyond the right granted in this section must be licensed
separately. In a failover environment, the same license metric must be used for the production and failover
nodes when licensing a given clustered configuration.
Source: Licensing Data Recovery Environments
24. Oracle Licensing Basics
Database Recovery ā Failover (Example)
ā¢ Failsafe included with Oracle
Database EE is installed on
nodes 1 and 2; it is running on
node 1 only
ā¢ If node 1 fails, node 2 takes over
(there is always an idle node with
Failsafe or other vendor cluster
solutions)
Illustration #4: Failover
1000 Traders
Apps 1- 4
6 Processors 4 Processors
SAN
Disk Array
Node 1
FS
DB EE Instance DB EE Instance
DB
26. Multi-Core Licensing Oracle
Database Enterprise Edition
To determine the total number of processor
licenses required when counting multi-core
chips, the total number of processors (chips) in
the server should be multiplied by the number
of cores then multiplied by the Processor
Factor.
Processor
Type
Processor
Factor
UltraSPARC T1 0.25
UltraSPARC with 1.4 GHz 0.50
AMD/Intel 0.50
All Other Multi-core chips 1.00
Single Core Servers 1.00# CPU x # CORE x Processor factor
Oracle Core Factor Table
Multi-core Processors
27. Processor factor has been changed as of March 16, 2009
Old situation:
Processor licenses that have been purchased before March 16, 2009 can be
allocated using the rules that applied at the time of purchase
Processor Type Processor Factor
UltraSPARC T1 Processors 0.25
Ultrasparc with 1.4 GHz processors 0.50
AMD/Intel processors 0.50
All Other Multi-core processors 0.75
Single Core Processors 1.00
Multi-core Processors
28. Oracle Licensing Basics
Processor Metric ā Processor Core Factor Table (1/3)
Source: http://www.oracle.com/us/corporate/contracts/processor-core-factor-table-070634.pdf
Vendor and Processor
Core Processor
Licensing Factor
Sun and Fujitsu UltraSPARC T1 processor (1.0 or 1.2 GHz)
Only named servers including:
Sun Fire T1000 Server, SPARC Enterprise T1000 Server*, with 6 or 8-core 1.0 GHz UltraSPARC T1 processor
Sun Fire T2000 Server, SPARC Enterprise T2000 Server*, with 4, 6, or 8-core
1.0 GHz, or 8 core 1.2 GHz UltraSPARC T1 processor
0.25
Sun Netra T2000, 1.0 or 1.2 GHz UltraSPARC T1 processor 0.25
SPARC T3 processor 0.25
Sun and Fujitsu UltraSPARC T1 1.4 GHz
Only named servers including:
Sun Fire T2000 Server and SPARC Enterprise T2000 Server*, with 8-core, 1.4 GHz UltraSPARC T1 processor 0.5
Sun T6300, 1.4 GHz UltraSPARC T1 processor 0.5
AMD EPYCā¢ 7XX1 and AMD Opteronā¢ Models 13XX, 23XX, 24XX, 32XX, 41XX, 42XX, 43XX, 61XX, 62XX, 63XX, 83XX, 84XX or earlier Multicore chips 0.5
IntelĀ® XeonĀ® Platinum 92XX, IntelĀ® XeonĀ® Platinum 82XX, IntelĀ® XeonĀ® Platinum 81XX, IntelĀ® XeonĀ® Gold 62XX, IntelĀ® XeonĀ® Gold 61XX, IntelĀ® XeonĀ® Gold 52XX, IntelĀ®
XeonĀ® Gold 51XX, IntelĀ® XeonĀ® Silver 42XX, IntelĀ® XeonĀ® Silver 41XX, IntelĀ® XeonĀ® Bronze 32XX, IntelĀ® XeonĀ® Bronze 31XX, Intel Xeon Series 56XX, Series 65XX, Series 75XX,
Series E7-28XX, E7-28XX v2, Series E7-48XX, E7-48XX v2, E7-48XX v3, E7-48XX v4, Series E7-88XX, E7-88XX v2, E7-88XX v3, E7-88XX v4, Series E5-24XX, E5-24XX v2, E5-24XX
v3, Series E5-26XX, E5-26XX v2, E5-26XX v3, E5ā26XX v4, Series E5-46XX, E5-46XX v2, E5-46XX v3, E5-46XX v4, E3-15XX v5, E3-15XX v6, Series E3- 12XX, E3-12XX v2, E3-12XX
v3, E3-12XX v4, E3ā12XX v5, E3-12XX v6, E5-
14XX v3, E5-14XX v2,, E5-16XX v4, E5-16XX v3, E5-16XX v2, and E5-16XX or
earlier Multicore chips 0.5
Intel Itanium Series 93XX or earlier Multicore chips (For servers purchased prior to Dec 1st, 2010) 0.5
Intel or AMD Desktop, Laptop/Notebook, or Netbook Multicore chips 0.5
Sun UltraSPARC T2+ 0.5
29. Oracle Licensing Basics
Processor Metric ā Processor Core Factor Table (2/3)
Source: http://www.oracle.com/us/corporate/contracts/processor-core-factor-table-070634.pdf
Vendor and Processor
Core Processor
Licensing Factor
Sun UltraSPARC T2+ 0.5
SPARC64 VII+ 0.5
SPARC64 X, SPARC64 X+, SPARC64 XII 0.5
SPARC T4 processor 0.5
SPARC T5 0.5
SPARC M5, SPARC M6, SPARC M7, SPARC M8 0.5
SPARC S7 0.5
Sun and Fujitsu SPARC64 VI, VII 0.75
Sun UltraSPARC IV, IV+, or earlier Multicore chips 0.75
Sun UltraSPARC T2 0.75
HP PA-RISC 0.75
IBM POWER5+ or earlier Multicore chips 0.75
All Single Core Chips 1.0
Intel Itanium Series 93XX (For servers purchased on or after Dec 1st, 2010) 1.0
Intel Itanium Series 95XX 1.0
IBM POWER6 1.0
IBM POWER7, IBM POWER7+ 1.0
IBM POWER8, POWER9 1.0
IBM Z (z14, z13, z(EC)12, z196, z11, z10 and earlier) 1.0
All Other Multicore chips 1.0
* SPARC Enterprise T1000 and SPARC Enterprise T2000 Servers may be sold and branded by Oracle, Sun Microsystems, Fujitsu or Fujitsu Siemens.
30. What does this mean?
ā¢ Many customers look at which server/hw spec is most efficient when licensing Oracle SW.
ā¢ Usually if you pick the right hardware you can cut down the license need In half.
ā¢ If you replace/refresh a server running Oracle Software and you want to reduce costs start by
looking at finding the most āoptimalā hardware.
33. What does this mean?
ā¢ Oracle state in their āOracle Partitioning Policyā available at
http://www.oracle.com/us/corporate/pricing/partitioning-070609.pdf:
ā¢ The partitioning policy is not part of any licensing agreement:
34. What does this mean?
ā¢ Oracle LMS references the following clause, in your OMA Schedule P:
ā¢ āOracle partitioning policy is not at all referenced in the OMA Schedule P.
ā¢ Just because Oracle has decided that VMware is a āsoft partitioningā does that give them
the right to assume that all processors within a vcentre has used to install and or run
Oracle programs?
35. VMWare impact on Oracle licensing
The use of vSphere has impacts that vary depending on the version that has been implemented, but which
are confirmed by the general Oracle guideline:
Any hardware which could be used theoretically by the software during a given runtime must be
licensed
Version Features Licensing Impact
Up to and including 5.0
Version 5.1 and version
5.5
Version 6.0
The virtual machines (VMs)
can only be migrated within
a cluster
Virtual machines (VMs) can
be migrated between
clusters (within one
vCenter)
Virtual machines (VMs) can
be migrated from one
vCenter to another
The whole cluster must
be licensed
All severs within the
vCenter must be
licensed
All servers in all
vCenters in the server
farm must be licensed
36. Starting Point: ESXi 5.0
Let us assume that a customer has Oracle Database Enterprise Edition software deployed on two virtual
machines (Vmware of course).
1
These two virtual machines are running in ESXi 5.0 cluster composed of four physical severs with one shared
storage (not accessible to any other cluster or server).
2
The setup is managed via a vCenter 5.0, which has multiple other clusters, however they are not sharing the
same storage. Each physical server consists of two quad-core Intel Xeon CPUs.
3
So the licensing requirement for Oracle (based on Processor license metric) is:
4 servers x 2 Intel Xeon CPUs x 4 cores/CPU x 0.5=
16 Processor licenses
Financial license cost (license list price +1 year
support): $927, 200.00 USD
Live migration between clusters not having the same shared storage is not possible in this situation.4
37. Migration to vCenter 6 and ESXi 5.5
The customerās VMware system managers decide it would be more efficient to use vCenter 6 and ESXi 5.5
to manage the environment. This greatly increases the flexibility of the VMs and its management and would
bring the company a lot of benefits. The two Oracle deployments keep running on the cluster with four
servers and the shared storage.
1
The increased functionality of vCenter 6 allows for VMs to migrate across vCenter instances (Cross vCenter
functionality) and the vSphere ESXi 5.5 version allows for live migration across the clusters in a vCenter
without the shared storage requirement.
2
In order to correctly calculate the license for the Oracle deployments in this setup, this customer would now
need to:
ā¢ License all physical severs in the vCenter where Oracle is deployed (so no longer only the four physical
servers, but all severs in all clusters)
ā¢ License all instances of vCenter, if multiple are present, due to the Cross vCenter functionality
3
If we assume that this customer has two identical vCenter instances, each comprised of three
clusters of four physical severs according to the setup above, this will have the following impact
on license requirement and financial cost:
2 vCenters x 3 clusters x 4 servers x 2 Intel Xeon
CPUs x 4 cores/CPU x 0.5= 96 Processor licenses
Financial license cost (license list price +1 year
support): $5, 563, 200.00 USD
40. ā¢ Diagnostics Pack (troubleshooting, monitoring tool) ā Very common
ā¢ Tuning Pack ā Very common
ā¢ Database Lifecycle Management Pack (not used often)
ā¢ Configuration Management Pack for Database
ā¢ Provisioning and Patch automation Pack for Database (not used often)
ā¢ Change Management Pack (not used often)
ā¢ Data Masking and Subsetting Pack
ā¢ Cloud Management Pack for Oracle Database
Database Oracle Enterprise Management Packs:
Overview
41. ā¢ Real Application Clusters (One Node)
ā¢ Partitioning
ā¢ OLAP
ā¢ Spatial and Graph
ā¢ Active Data Guard (11g)
ā¢ Real Application Testing (11g)
ā¢ Advanced Compression (11g)
Oracle Database Enterprise Edition Options:
Overview
ā¢ Database In-Memory
ā¢ Advanced Security
ā¢ Label Security
ā¢ Database Vault
ā¢ Multitenant
ā¢ Advanced Analytics
ā¢ Data Model (Retail, Airline, Utilities &
Communications)
42. ā¢ Database Options can only be used in addition to Oracle Database Enterprise
Edition
ā¢ Enterprise Edition Options must match the number of licenses and the license
model of the associated Oracle Database Enterprise Edition
ā¢ In addition, a minimum of 25 Named User Plus licenses per Processor must be
met.
ā¢ When licensing Active Data Guard, both the primary and the standby servers
must be licensed.
ā¢ The use of Tuning Pack requires the licensing of Diagnostics Pack
Database Enterprise Edition Options:
Licensing Rules
43. Prod
50 NUP
Prod
90 NUP
Application 1 Application 2 Application 3
Prod
20 NUP
Tuning Pack
Diagnostics Pack
Change
Management
Pack
PARTITIONING (USER)
IBM P5 550Q
4 CPU Quad Core
RISC
8 Sockets
Enterprise
Edition
Licensing Technology Products:
Exercise
Which products and how many licenses are required to license the architecture below?
ORACLE
Enterprise Edition
44. ā¢ Use a SAM Tool (can help, up to 90% - dont trust any SAM tool 100% as they
make mistakes such as saying you need to license something when you dont.
Or dont pick it up at all. (A tool, not a compliance tool)
ā¢ Work with a Oracle Consultant who can analyze the Oracle audit scripts.
Then they can tell you what will Oracle detect/interpret/view. (Recommended)
ā¢ Manual, work with DBAs/System owners (Risk as someone might not provide
the correct information = not recommended)
ā¢ Home/Made scripts. DBA/Technical staff might be able to write something that
can be used as a substitute to a SAM Tool. A tool, not a compliance tool)
How to detect / find out database options usage
45. Top 7 most common compliance issues
Usage of management
packs
(diagnostics/tuning)
1 Usage of advanced
compression or other options
(adv compression most
common)
2
Usage of management
packs on standard
edition. (not allowed)
3
Usage of management
packs (historical usage,
not uncommon to see
years of usage)
4 Not having full use licenses
under EBS applications.
(common reason for being
audited)
5 Oracle virtualization
policies, vmware,
solaris, ibm lpar
(controversial topic)
6
Installing the wrong version
or refreshing hardware not
buying new licenses
7
46. Preventive recommendations:
ā¢ Educate DBAs/Technicians about what licenses you own.
ā¢ Perform a 18 month check up on database options usage (LMS scripts)
ā¢ If you pass the next Oracle audit with no issues you might not face another audit
in 10 years! (They rarely audit customers who have a track record of being
compliant)
ā¢ Have a SAM tool to manage Oracle environments
How can you prevent future non-compliance?
48. Licensing Middleware Products:
Exercise
ā¢ Most common products are
ā¢ Oracle Internet Application Server
ā¢ Oracle Weblogic Server & Suite.
ā¢ Licensing is almost identical to database licensing.
ā¢ Focus should be more on making sure you have deployed it correctly.
ā¢ SAM tools are usually only able to license these products and not any of the other 50+ Oracle
Middleware products that Oracle has.
49. Licensing Weblogic Server
License minimums Weblogic Server
Weblogic Server
Standard Edition: 10
Named User Plus per
processor
Weblogic Server
Enterprise Edition:
10 Named User Plus
per processor
Core licensing is the
same as Oracle
Database.
Weblogic Suite:
10 Named User
Plus per
processor
S E Su
50. Weblogic Server restrictions
Weblogic Server
Weblogic Server
Enterprise
Edtion has NO
license
restrictions
Weblogic Suite
has NO license
restrictions
Weblogic Server
Standard Edition
has NO license
restrictions
S E Su
51. License minimums Internet Application Server
Licensing Internet Application Server
Internet Application
Server Java Edition:
10 Named User
Plus per
processor
Internet Application
Server Standard
Edition: 10 Named
User Plus per
processor
Core licensing is the
same as Oracle
Database
Internet Application
Server Enterprise
Edition: 10 Named
User Plus per
processor
J S E
52. Internet Application Server
Internet Application
Server Standard
Edition has NO
license HW
restrictions
Internet Application
Server Enterprise
Edition has NO
license HW
restrictions
S E
54. ā¢ A SAM tool is a must if you have a large Oracle estate.
ā¢ SAM tool will help you making sure Oracle does not go completely āout of
controlā
ā¢ SAM tools are not to be trusted for a compliance position.
ā¢ SAM tools have been sold to many companies, and those companies are still
facing huge audit fines when Oracle are auditing them...
ā¢ Use a SAM tool as a second data source, if you want to resolve Oracle
compliance issues you should use Oracle āLMSā style scripts to analyze.
How to approach Oracle Licensing (sam tool)
55. SAM tool Overall description Pro Cons Our Grade
Lime Software
Only Oracle Tool, that scans IP adresses for
Oracle Databases and Middleware. Then it
runs the Oracle LMS Scripts.
ļ± Easy to deploy
ļ± Low pricing
ļ± Has good Oracle analysis built into it
DB/MW
ļ± Little documentation on how to manage
it, use the tool.
ļ± Small company (less than 5 employees)
ļ± No support for Oracle Apps.
3
Aspera
Comprehensive tool, much investments into
Oracle License management.
Their attitude towards Oracle License
management is serious shown by
acquisitions and their employees.
Oracle provides LMS scripts.
ļ± When we have reviewed/verified aspera
results ā they have been very good.
ļ± Does not āover-sellā its tool and are
transparent about usage.
ļ± Possible to customize rules - which
suits Oracle licensing well.
ļ± Oracle DB and MW capabilities.
ļ± Few partners who can help you with it.
ļ± You might end up buying everything
from the tool vendor (consultancy and
tool) and that can lead too over-
reliance on the tool and not objective
advise.
5
Snow Software
Primarily a tool to manage MS and desktop
SAMā great for some vendors. (SAP)
We dont have a good experience of using
Snow for Oracle. They were very late to the
Oracle SAM. Stronger in marketing than
Oracle Licensing.
ļ± Nice graphic interface.
ļ± Large customer installbase in EMEA,
less so in US.
ļ± Easy to use, and lower cost than
Aspera and Flexera.
ļ± Oracle DB capabilities.
ļ± Their marketing and sales are not
educating, arguably harmful to Oracle
SAM. Many license managers have
bought into the hype that the tool will
solve it all.
ļ± Too many false positives that cause you
to investigate āfalse alarmsā
ļ± No support for MW, Apps.
2
Flexera
Comprehensive tool, many major companies
use Flexera for all vendors.
By far the most āexperiencedā and serious
Oracle License managers we come across
use Flexera or Aspera.
Oracle provides LMS scripts.
ļ± If you spent time on configuring it and
managing it ā it can be the best tool in
the market.
ļ± Offers you to pull out scripts (raw) and
do the analysis outside of the tool.
ļ± Oracle DB and MW capabilities.
ļ± Expensive and requires a lot of time to
implement.
ļ± Cannot do Oracle Applications (as
everyone else) 4
Oracle āaudit scriptsā
We recommend it to be used at any time you
want a compliance position that is close to
100%. Never use only a tool when there is
an audit or āsharpā scenario with Oracle.
ļ± Very accurate
ļ± Copy of Oracle LMS methodologies
ļ± Must use external consultancy
ļ± Requires some work to run them on all
your Oracle Servers
ļ± Not a discovery tool.
N/A
58. Licensing Technology Products
Exercise ā Optimization ā how to license most effective?
Production DBs (total 50 cores intel 0,5) Test DBs (20 cores intel 0,5)
59. Savings 237 500 $ in license fees. (+22% support fees)
Licensing Optimization
Scenario 1 (License both production
and test with CPU Licenses)
70 cores of Intel (0,5) 70x0,5 = 35 CPU
Licenses
Equals 35x Proc Enterprise Edition
Licenses 1,662 500 $ in license fees..
Scenario 2 (License production with
CPU and test with NUP Licenses
Licensing production (50 cores) equals
= 25 processor licenses.
Licensing Test (20 cores) equals = 250
Named User Plus (25 per CPU)
25 processor licenses + 250 NUP
licenses Enterprise Edition = 1,425 000
$ in license fees.
60. 1. Compare CPU and Named User Plus
Licensing.
2. Consolidate your Oracle Database to less
servers, (usually utilization for an Oracle DB
server is very low as low as (10-20%)
3. Consider the most license effective
hardware to run the software on. Can
reduce licensing by 50%.
4. You can negotiate contract terms allowing
you to license Oracle differently than the
standard way (for example license test and
development with 10 user instead of 25 ā
will give you a 60% reduction)
7 ways of āoptimizingā Oracle Licenses.
5. Look at downgrading to Standard Edition
versions (many times the application can
use standard edition and there is no
requirement for using enterprise edition)
6. Question the need of DB management
packs, if they are used once a year ā should
you consider terminating the licenses?
7. Test and development environments that
are used very rarely, consider moving to a
Oracle cloud / or any other cloud platform
and use per the hour the tests are being
delivered.
61. Support
Renewals
License
Agreement,
audit reports
Find
entitlements
Which products
do you have?
ā¢ Technology?
ā¢ Apps?
On which
metrics?
ā¢ CPU/Users?
ā¢ Revenue?
ā¢ ASFU? (exclude)
Inventory
ā¢ SAM tools & Inventory
ā¢ Application owners
Method
ā¢ SAM tool
ā¢ LMS Scripts
Analyze results
ā¢ Risk Reduction
ā¢ Why is it being
used?
Optimisation
ā¢ Downgrade
ā¢ Consolidate
ā¢ License model
ā¢ Migrate
Negotiation
ā¢ Understand
discount levels
possible.
ā¢ Negotiate contract
terms
Reviewing Oracle Licensing ā Road map
62. Production Production usage licensing CPU % Depends on discount
targets
Test and
Development
Test and development can be lowered to much
lower user minimums than product today. Today
most customers are licensing this by 25 for DB
which can be cut by 60%
NUP % Easy to negotiate
Disaster Recovery You can ask Oracle for a specific DR licensing. CPU % Easy to negotiate
Archieving,
other use
Ask Oracle for a specific license for any archieving
or any other purpose.
NUP % Easy to negotiate
Application users
variations (EBS an
others)
Oracle can negotiate away from full users on
applications and not pay full price for users who
ābarelyā touches application.
User % Customer specific
Non standard
licensing
Hotel rooms, oil barrels, airplanes, number of
customers
Not Applicable Not Applicable Difficult, large deals
only
Cloud Test, development, production OCPU NA Difficult
License & Contract Optimization
DifficultyDiscounting
License
Metrics
DescriptionUSAGE
All versions can be installed on the top one, as long as the 16 thread count is met.
Only SE and EE can be installed on the bottom one, SE must have been purchased prior to SE2 and not migrated!
There are a couple of options which may be included with certain applications or as part of a standard database install ie Partioning system user and on Ebusiness Suite sometimes Spatial locator and OLAP these have to be analysed when looking at scripts and with follow up questions to the customer.
Answer minimums required = 4 * 4 * 0.75 = 12 Processors or 300 NUP (12 * 25) 160 Actual Users.
Minimums are greater than actual users so minimums must be met!
DBEE = 300, Tuning Pack = 300 (options and packs must match database) 300 Diagnostics Pack, 300 Database Lifecycle Mangement, 300 Partioning.