Oracle has licensed their software by many different metrics over the years., and some customers remain licensed by those retired metrics. In some cases, an old metric may be outdated when compared to current hardware standards. Examples of this are the Named User Multi Server and Named User Single Server metrics, which had minimum license requirements tied to the number of MHz of a server. While the metric may have served the customer’s purposes 15 years ago, state-of-the-art hardware may be creating a compliance violation by inflating the minimum number of licenses required.
Many Oracle customers are licensed by a concurrent metric. While there are advantages to remaining on concurrent licenses, Oracle knows all too well that adherence to concurrency as it has historically been defined by Oracle is difficult.
Some old metrics did not include the allowance for automatic batching that customers enjoy today through the Named User Plus metric. For customers using these old metrics, they must license the front-end user population for any third party database that batches to Oracle. Oracle knows this presents a compliance pitfall for customers as well.
For these reasons, customers that remain licensed with legacy metrics may be at greater risk of audit.