Oracle License Management Training Part 1 - Database Licensing Basics

Oracle License Management
Training Part 1 - Oracle Licensing

Before we start…
Mute sounds from chat
If issues with video/view ppt – refresh browser

Test and Diploma (digital badge)
• Available for all attendees who have been on the live training sessions or watched 90% of the recordings.
• Test will be issued 1st week of October after last training session, which ends in September.
• Test is multiple-choice.
• Test is “live” for 2 weeks.
• You will can take the test 3 times.
• Diploma will be issues 3-4 weeks after successful completion of test.
• Diploma is a digital badge you can attached to email and linkedin profile.

Oracle Licensing
Before we start… some help
• Oracle has thousands of software lines, but database, middleware is more than 50% of
the install base. Our advise: Learn technology first and when you have a grasp of how to
license these products – then you learn something new
• Very few people has the knowledge, it’s 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 can’t find the licensing agreement.

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

About Audit org / Licensing
GLAS = Oracle in-
house audit org.
Mostly managed from
Romania since 2018
Most common products lines and metrics:
v Oracle Database | NUPs and Processor
v Weblogic | NUPs and Processor
v E Business Suite | Application User/ Enterprise
Metrics
SIA = 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)

Oracle Database Licensing
The basics.
• Enterprise and Standard Versions.
• Enterprise has 18 different “database options” functionality that requires additional licensing.
• Enterprise has core licensing.
• Standard Edition has CPU/Socket Licensing.
• There are Oracle DB versions 1-19. If you have a license you can use any version!
• No need to purchase a new license when upgrading to a new version.
As long as you are paying the annual support renewal, you have the right to update the
software without paying any uplift or upgrade fees.
• You can “migrate/upgrade” Standard Edition licenses towards Enterprise Edition for a fee.
• If you look in a SAM tool, it can be confusing to identify the version you have.

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

• 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.
Can only be resold by the ISV – limited to 1 application/solution
• ASFU/ESL Licenses – should always be excluded from an Oracle license
audit.
• Renewal of support is usually treated as an auto-renewal when there are
possibilities to negotiate.
Licensing Metrics and other licensing types

Oracle Database Licensing
What do you need to license?
You need to
license
production
environments
You need to
license test and
development
environments
You often need
to license
disaster
recovery
environments
Standard
licensing is the
same for all
types of usage
(FULL USE)

Example from Oracle Licensing Agreement
(Ordering Document)

Question
How do you calculate licensing for EE DB?
Answer A:
ü Socket licensing
Answer B:
ü Core licensing

Question
What is an ASFU License?
Answer A:
ü It is a license model only sold by ISV and it’s
limited for one application
Answer B:
ü It’s unlimited licensing agreement

Question
Can you sign a 2-year license agreement?
Answer A:
ü No, it is not possible
Answer B:
ü Yes, you have perpetual or 1-5 year licensing
options

Question
You have 15 test and dev env. running Oracle DB
Do you need to license these env.?
Answer A:
ü No, test and dev is free of charge
Answer B:
ü No, you need to license test and dev same way
as production

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…

* If non-human operated devices such as sensors are connecting to the Oracle Database, then all devices need to be licensed.
When licensing the Oracle Database by Named
User Plus…
all users who are using the Oracle Database, as well as all non-human
operated devices that are accessing the Oracle Database must be licensed.
If non-human operated devices
and human-operated devices
are connecting to the Oracle
Database and are mutually
exclusive, then all non-human
devices and all humans operating
devices need to be licensed.
If human-operated devices
such as bar code scanners are
connecting to the Oracle
Database, then all humans
operating these devices need to
be licensed.

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

Processor
Processor
This metric is used in environments where
users cannot be identified and counted.
REASON 1
The Internet is a
typical environment
where it is often
difficult to count
users.
REASON 2
This metric can also be
used when the Named
User Plus population is
very high and it is more
cost effective for the
customer to license the
Database using the
Processor metric

Processor Metric – Processor Core Factor Table
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

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

• Used in environments where users can
be counted
• Based on users and non-human
operated devices accessing the
database
CPU AND NAMED USER PLUS
Named
User Plus
Per Processor
BREAK-EVEN:
1 processor license =
50 NUP licenses (same license fees)
• 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

How to calculate licensing:
Oracle Database
Enterprise Edition:
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
For example deploying Oracle
Database Enterprise Edition 4 core
server intel cores you would require
to license 4x0,5 = 2 Oracle Database
Enterprise Edition Processors.
Oracle Database Standard
Edition:
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.

Database metrics:
Oracle Database Enterprise Edition
The Enterprise Edition requires a
minimum of 25 Named User Plus
per processor licenses or the total
number of actual users, whichever
is greater.
John
Ken
Klaus
Kate
Alex
25 Named User
Example: A customer who wants to license the Database
Enterprise Edition on a 4-way box (assuming single core
chips) will be required to license a minimum of 4 processors *
25 Named User Plus, which is equal to 100 Named User Plus.

Database metrics:
Oracle Database Standard Edition 2
The Oracle Standard Edition 2 and
Enterprise Edition of the database can
be licensed using the Named User Plus
metric or the Processor metric
Named User Plus
This metric can be used in all environments. Different
minimums apply depending on the Database edition:
* Oracle Database Standard Edition 2 may only be licensed on
servers that have a maximum capacity of 2 sockets
* The minimums when licensing by Named User Plus (NUP)
metric are 10 NUP licenses per server.
John
Ken
Klaus
Kate
Alex

Exercise
Which database version is allowed to be deployed on this
server?
EE
Hardware:
HP Intel
4 CPU – Quadcore Intel
4 sockets
Answer A:
ü Only Enterprise Edition
Answer B:
ü Enterprise and Standard Edition 2

Exercise
Licensing Enterprise Edition DB, how many CPUs are required?
EE
Hardware:
HP Intel servers
4 sockets
Answer A:
ü 4 x 1 = 4 processors
Answer B:
ü 4 x cpu = 4 cores = 16 cores
ü 16 x 0,5 = 8 processor licenses.

Exercise
Licensing Enterprise Edition DB, how many NUPs are required?
You also have 550 users
EE
Hardware:
HP Intel servers
4 sockets
Answer A:
ü 550 user licenses
Answer B:
ü 4 x cpu = 4 cores = 16 cores
ü 16 x 0,5 = 8 processor licenses.
ü 8 x 25 user minimums = 200 user licenses

Exercise
Licensing SE2 DB, how many CPUs are required?
EE
Hardware:
HP Intel
1 socket
Answer A:
ü 4 cores x 1 = 4 processors
Answer B:
ü 1 CPU Oracle DB SE2.

Product Selection: Exercise
What information do we need to find out the licensing (DB)?
EE
Hardware:
A server running Oracle Database

Check List to review Database Licensing
1. Review your
licensing agreement
a support renewal
Why: You want to
understand which
licensing metric that you
have.
A contract can also tell
you if there are limitations
to the licensing.
2. Find out which
version of Database
that is running,
DB SE or DB EE?
3. Gather data about the
server
your database is running
on:
What type of processor
Intel/AMD etc.
* How many processors
are in the server
* How many cores in each
processor
* Is the server virtual or
physical ?
ü ü ü

By asking these questions you will be able to
understand:
- Do we have the correct version of database installed?
(match with entitlement)
- Do we have the quantity of licenses?
What you will not know is:
What database options are in use or have been in use?
How to find out: You need to analyse the database in detail and it
can almost be impossible
to find out if you lack the knowledge to analyse Oracle LMS scripts.
Oracle LMS scripts will detect not only what is in use today, but also
what has been used in the past.

Example of Oracle Server Worksheet

…
Enterprise Edition Options
Licensing

Oracle Database
What should you know?
• Different features that requires extra licensing
• They are only allowed to be used on Enterprise Edition DB.
• Common compliance issue is that companies have used EE options on SE DB.
• Oracle Enterprise Edition – must have same license metric and quantity as the database.
• Most options can be used by DBA or IT staff without any alert about licensing requirements.
• Usage of DB EE options is by default often saved in the database (historical).
• Oracle LMS/Audit scripts will detect this usage and require licensing.

• Diagnostics Pack (troubleshooting, monitoring tool) – Common compliance issues
• Tuning Pack – Common compliance issues.
• Database Lifecycle Management Pack (not used often)
• Data Masking and Subsetting Pack
• Cloud Management Pack for Oracle Database
Database Oracle Enterprise Management Packs:
Overview

• Real Application Clusters (& One Node)
• Partitioning
• OLAP
• Spatial and Graph (now free)
• Active Data Guard
• Real Application Testing
• Advanced Compression (compliance
issues)
Oracle Database Enterprise Edition Options:
Overview
• Database In-Memory
• Advanced Security
• Label Security
• Database Vault
• Multitenant
• Advanced Analytics (now free)

• 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:
RULES TO CONSIDER

Question
If you are using Tuning pack, which licenses are pre-req?
Answer A:
ü Oracle DB Enterprise Edition
Answer B:
ü Oracle DB Enterprise Edition + Diagnostics Pack

Question
Your Oracle DB EE is licensed on NUP basis, you want
to add diagnostic pack licensing, which metric should
you choose?
Answer A:
ü Diagnostics Pack – Named User Plus
Answer B:
ü Diagnostic Pack – Processor

• Use a SAM Tool (can help, up to 90% - don't trust any SAM tool 100% as they
make mistakes such as saying you need to license something when you
don't. Or don't 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

Oracle Database
Licensing Oracle Database – DR/High availability
• Oracle have different ways of licensing disaster recovery.
• You must find out what specific high availability/DR solution that you have/want.
• What is Oracle view on licensing, some require licensing and some does not.
• Common reason for companies being non compliant (misunderstanding the licensing
rules/policies)

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

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.
Oracle permits customers to store a back up copy of the
database physical files on storage devices, such as tapes,
without purchasing additional licenses
In an event of a failure, when the Oracle data is restored
from a tape or media, and the Oracle Database is installed
on the recovery sever, licensing is required

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

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.

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

STANDBY:
In this method, one or more copies of a primary database are maintained on a
standby server(s). The sites in a standby configuration may be dispersed
geographically and are connected by Oracle Net Services. As the primary database
is modified, log information generated by the changes are sent to the standby
database(s) and subsequently applied to the standby database. If the primary
database fails, a standby database can be activated to be the new primary
database. Solutions like Oracle Data Guard (included with Oracle Database EE) or
customer-generated scripts can be used.
In this environment, both the primary and the standby databases must be fully
licensed. Additionally, the same metric must be used to license both
databases

REMOTE MIRRORING:
This method involves the mirroring of the storage unit or shared disk arrays. Remotely mirrored
storage units may be geographically dispersed and not in the same location as the primary unit,
but they share the same disk array. To setup a remote mirroring environment, the Oracle data
files, executables, binaries, and DLLs are replicated to the mirrored storage unit. Solutions like
Veritas Volume Replicator, EMC SRDF, Legato Replistor, and EMS StoreEdge are used to mirror
the data stored on the disk arrays. In this environment, both the primary and the remote mirrored
databases must be fully licensed. Additionally, the same metric must be used to license both
databases.
If the Oracle Database is accessing the data from the primary disk array and it is not accessing
the mirrored disk array, but is installed on the mirrored network storage unit, then both databases
must be fully licensed and the same metric must be used.
If a failure occurs in the primary storage unit and the Oracle Database can no longer access the
data from the primary disk array, however it is still installed on the primary unit, the data can only
be accessed from the remote mirrored disk array, then both databases must still be fully licensed
and the same metric must be used. In this environment, Oracle must be fully licensed at the
primary site, and if it is ever installed and/or run at the secondary site, it must all be fully licensed
there. Additionally, the same metric (i.e. processor-based, or named user-based)

Question
You are using Oracle HA solution “Oracle Data Guard”
Do you need to license both primary and standby?
Answer A:
ü Yes, Oracle Data Guard is only included in Oracle DB EE
and is considered a active standby.
Answer B:
ü No, you can run it for free up to 10 days

Question
You are saving your Oracle DB backups to a tape every
evening, do you need to license a cold standby with
no binaries installed?
Answer A:
ü Yes, you must license both.
Answer B:
ü No, you do not need to license the backup
because the binaries are stored on a tape
backup.

…
Licensing Oracle in virtual
environments

“ABC” vCenter (vSphere 5.0):
In older versions of VMware’s vSphere ESXi, up to 5.0, shared
storage is required for the virtual machines running Oracle to move
throughout the VMware environment
Oracle software is installed on shared storage and the entire
cluster(s) connected to the shared storage have the ability to run
Oracle.
As a result of this, Oracle requires you to license all the physical
cores of the physical ESXi hosts that are part of the cluster that is
connected to shared storage within the VMWare environment.
Shared storage is no longer required to live migrate a running virtual
machine. A virtual machine running Oracle can move anywhere within
the vCenter Server Instance and shared storage no longer serves as
the install point for Oracle.
cores of all the physical ESXi hosts that are part of the same vCenter
Server Instance, including across datacenters within the vCenter
Server Instance, since the end user has the ability to move the virtual
machine running Oracle software to any server within the vCenter
Server Instance.
Total: 16 Processor Licenses
List Price = $3,800 000 List Price $11,400 000
Total: 80 Processor Licenses Total: 240 Processor Licenses
List Price = $ 760 000
With vCenter Server 6.0 or higher, a running virtual machine can
move across vCenter Server Instances which impacts licensing
across the entire environment
cores of all the physical ESXi hosts of all the vCenter Server
Instance(s) which have hosts with ESXi 5.1 or later hypervisors.
Virtualization impact on Oracle licensing

62
Step 1. - Oracle Partitioning Policy document
Source: https://www.oracle.com/assets/partitioning-070609.pdf

Approved Technologies + disclaimer
63

Step 2- Oracle Partitioning Policy document
Soft partitioning segments the operating system using OS resource managers. The operating system limits the number of CPUs
where an Oracle database is running by creating areas where
CPU resources are allocated to applications within the same operating system. This is a flexible way of managing data processing
resources since the CPU capacity can be changed fairly easily, as additional resource is needed.
Examples of such partitioning type include: Solaris 9 Resource Containers, AIX Workload Manager, HP Process Resource
Manager, Affinity Management, Oracle VM, and VMware.
Unless explicitly stated elsewhere in this document, soft partitioning (including features/functionality of any technologies
listed as examples above) is not permitted as a means to determine or limit the number of software licenses required for
any given server or cluster of servers.
SOFT Partitioning:

Step 3. We start reviewing Oracle Licensing Agreements, OMA, OLSA
All oracle
customer have
accepted Oracle
t&cs
Contracts don’t
reference
“partitioning”
policy document
Partitioning
policy document
is NOT part of
any contracts.
Contracts
reference other
policies such as
support

What does it say in Oracle contracts?
Review your Oracle Master Agreement (OMA)
2. RIGHTS GRANTED
2.1 Upon Oracle’s acceptance of Your order, You have the non-
exclusive, non-assignable, royalty free, perpetual (unless otherwise
specified in the order), limited right to use the Programs and receive
any Program-related Service Offerings You ordered solely for Your
internal business operations and subject to the terms of the Master
Agreement, including the definitions and rules set forth in the order and
the Program Documentation.
OMA

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
Installed and/or
running is not
defined in the
OMA.
But : It does
not reference
the partitioning
policy document.
NEXT.. PROCESSOR DEF.

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

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?

Licensing Middleware Products:
Most common products are:
• Oracle Internet Application Server
• Oracle Weblogic Server (Standard and Enterprise) & 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.

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

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

License minimums Internet Application Server
Licensing Internet Application Server
Internet Application
Server Java Edition:
10 Named User
Plus per
processor
Server Standard
Edition: 10 Named
User Plus per
processor
Core licensing is the
same as Oracle
Database
Server Enterprise
Edition: 10 Named
User Plus per
processor
J S E

Internet Application Server
Server Standard
Edition has NO
license HW
restrictions
Server Enterprise
Edition has NO
license HW
restrictions
S E

• Oracle Database Licensing https://www.oracle.com/assets/databaselicensing-070584.pdf
• Oracle Partitioning (virtualisation) https://www.oracle.com/assets/partitioning-070609.pdf
• Oracle Licensing Disaster Recovery https://www.oracle.com/assets/data-recovery-
licensing-070587.pdf
• Oracle Application Licensing https://www.oracle.com/assets/application-licensing-table-
070571.pdf
• Oracle Licensing in the Cloud https://www.oracle.com/assets/cloud-licensing-070579.pdf
Oracle Software investment guide:
ftp://public.dhe.ibm.com/software/websphere/oracle/sig.pdf.
• Oracle Database Licensing information:
https://docs.oracle.com/database/121/DBLIC/editions.htm#DBLIC109
Oracle Middleware Licensing information:
https://docs.oracle.com/cd/E24628_01/doc.121/e24474/toc.htm
Licensing sources (use it when reviewing
licensing)

Oracle License Management Training Part 1 - Database Licensing Basics

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to Oracle License Management Training Part 1 - Database Licensing Basics

Similar to Oracle License Management Training Part 1 - Database Licensing Basics (20)

Recently uploaded

Recently uploaded (20)

Oracle License Management Training Part 1 - Database Licensing Basics