Common omissions of SAM tooling and how to capture them.

 

 

1. Lack of Detection of Oracle Database Options & Management Packs

What are some common omissions of SAM tooling and how to capture them, when it comes to Oracle licensing and compliance? Most SAM tools fail to detect usage of features like:

 

• • Advanced Compression
  • Diagnostics Pack
  • Tuning Pack
  • Partitioning

They can check it, but are your tools seeing the difference between what needs licenses, and what comes pre-installed for free?

Oracle LMS checks v$option and dba_feature_usage_statistics, which Flexera and iQuate cannot access.

 

2. Virtualization (VMware)

Oracle wants you to license the entire VMware farm (and your neighbours), but SAM tools only scan active nodes, leading to the risk of under-licensing. What, non measurable , precautions did you took that limits your license need?

 

3. Oracle Java SE Tracking

Not every Java installation requires a, company wide Oracle Java subscription.

Many tools miss:

 

• • Java Commercial Features
  • Java versions in Docker containers
  • Java usage in development environments

4. Oracle Middleware (WebLogic / SOA Suite)

Flexera fails to detect WebLogic feature usage. Oracle LMS relies on the WebLogic Diagnostic Framework (WLDF) for this. License Consulting and ITAA have their own proprietary tools to let you know before Oracle knows.

 

5. Historical Usage Data

Some SAM tools lack a 12-month audit trail, which Oracle LMS requires to assess peak usage. Not only for the old Concurrent Device metric but also for Cloud deployments (not being OCI). You might need to have the evidence, because you’re guilty unless proven otherwise..

 

6. Cloud & BYOL Usage

Some SAM tooling is limited in tracking for:

 

• • Oracle Database on AWS RDS and Azure
  • Oracle Java in Kubernetes and Docker
  • Oracle Cloud Infrastructure (OCI)
  • Google Cloud

 

7. Incorrect Metric Calculation

Many tools miscalculate:

 

• • Processor Core Factor
  • The minimum of Named User Plus (NUP) licenses
  • High Availability (Active/Passive) nodes
  • Other measurements you have taken to mitigate your license need

 

Summary of Oracle LMS Perceived Omissions

 

Area of Omission	Oracle LMS’s Perception	SAM Tool Limitation
Database Options & Packs	High Risk	Cannot track v$ views
VMware & Virtualization	Critical Non-Compliance	Only scans active nodes
Java SE Subscription	High Risk	No visibility on commercial features
Middleware (WebLogic)	High Risk	No access to WLDF
Historical Usage Data	Mandatory	No 12-month audit trail
Cloud (AWS/Azure/OCI)	High Risk	BYOL tracking failure
Metric Calculation	High Risk	Incorrect core factor calculation

 

✅ Best Practice to Pass an Oracle LMS Audit:

 

• • Use Flexera/Snow or iQuate for data collection.
  • Use Collection Scripts (from Oracle LMS or ours (available for free)) for accurate compliance data. But DO NOT SHARE THE DATA with Oracle before you’ve contacted us.
  • Verify results with an independent Oracle Licensing Expert (e.g., ITAA , ITAM Japan or License Consulting).
  • This is the best way to find the omissions of your SAM tooling and we love to help you capture them.