10 Question Oracle License Audit Thermometer

Oracle Audit Temperature Madora


Take the 10 Question Oracle License Audit Thermometer

Have you got a temperature?


Answer Yes or No to each of these 10 questions and add up your scores to find just how Audit Hot you are.

It is no secret that Oracle LMS now routinely roll through customers on a periodic basis. You are particularly at risk of winning the LMS lottery if you have not bought anything for the last 2 years and if you have not been audited in the last 5 years.   Now you may be approached by Oracle via the Sales Rep, the COLS team, a JPE Partner or even Oracle LMS to fill in a server worksheet. Remember this is not a formal audit – but could turn into one. Below is a list of  a number of items that Oracle particularly look for, and may ask you about when they hold that initial first meeting.  So be prepared and run through these items to check your temperature.

  1. Have you undergone a hardware consolidation or infrastructure modernisation in the last 18 months?
  2. Are you using virtualisation software  such as VMware in your Oracle data centres?
  3. Do you have multiple production clones, staging areas and  other test/development environment?
  4. Do you use a third party outsourcer to manage your IT or that provides remote Database Administration services?
  5. Do you have any Oracle based Disaster Recovery environments?
  6. Do you have Named User Licences (NUPS)?

User minimums are often misunderstood. See blog article for more detail on this http://madora.co.uk/oracle-licensing-user-minimums-how-much-is-your-organisation-exposed-part-1/

  1. Do you have any old license metrics? – check your support renewals and contracts to see if you are using old UPU metrics for Oracle Database
  2. Have you made any acquisitions, divestments or been involved in any mergers since your last purchase of Oracle products?
  3. Do you provide a chargeable service for customers that is powered by applications underpinned by Oracle products?

Check you have the correct licence type. E.g. standard contracts are for internal use only.  Hosting or embedded licences are different. So your contracts, even a ULA may not cover some of your customer facing applications.  We are seeing more of this so will be writing a future article on this topic. Let us know if of interest.


  1. Do you have multiplexing scenarios?

See definition. ” Multiplexing is when a large number of end users and/or devices access a system via an interface, such as a transaction processing monitor or a web server product, so that the apparent number of users and/or devices accessing the system is much smaller than the actual number of users and/or devices. If Oracle software is part of an environment in which multiplexing hardware or software is used, then all users and/or devices must be licensed at the multiplexing front end.”

See http://www.oracle.com/corporate/pricing/sig.pdf

Please note multiplexing is particularly an issue when running Oracle products to underpin vendor applications; what Oracle calls ISVs. These have been a target for Oracle COLS/LMS in the past as more often than not they are incorrectly licensed due to a lack of understanding of the multiplexing rule.

Remember every interface to an Oracle database counts as a user. See NUPS definition. We have seen this as a major issue in the financial services sector in particular.

Frankly if you answered ‘yes’ to any of these questions then you have some potential risk.

If you answered ‘yes’ to more than 6 contact Madora Consulting today.

(3) comments

Add Your Reply