The myth of the free dev environment.
The single most expensive assumption in Oracle licensing is that test and development environments are free. They are not. Oracle licenses the software, not the environment, and the license metric applies to every installed and running copy regardless of whether the environment is labelled production, test, development, quality assurance, staging, training, or disaster recovery. The belief that non production environments carry no cost is the source of a large share of the audit findings we defend. The belief usually traces back to the Oracle Technology Network download. The download is free. The right to use what you downloaded is not.
What the OTN licence actually permits.
When an engineer downloads Oracle Database or any other Oracle technology product from the Oracle Technology Network, the download is governed by the OTN Developer License. That license permits the use of the software for the purpose of developing, testing, prototyping, and demonstrating an application. It is a narrow grant. It does not permit use of the software for internal data processing, for any commercial or production purpose, or for any environment that supports a production system. The moment a test environment is used to validate production data, to support a production release, or to process real business information, the OTN license no longer applies and a full commercial license is required.
The practical problem is that the boundary between development and production use is crossed silently. An engineer downloads the database under the OTN license, builds a development environment, and over time that environment starts holding a copy of production data for realistic testing. At that point the environment requires a full license and the customer almost never realises it. The buyer side discipline is to treat every OTN installation as a license liability waiting to mature.
The full use rule.
Oracle's licensing position on non production environments is straightforward and unforgiving. Every environment that runs licensed Oracle software requires a full license at the same metric and the same quantity as a production environment of the same size. A four processor test database requires four processor licenses. A development environment running the Partitioning option requires Partitioning licenses. There is no discount for non production use and no concept of a reduced rate test license in the standard Oracle price list. The licensing footprint of a non production environment is identical to the footprint of a production environment with the same hardware and the same feature usage.
This rule surprises buyers because most other enterprise software vendors offer reduced or free non production licensing. Oracle does not. The buyer side discipline is to count non production environments in the license model from the start and to challenge the assumption that they are cost free. We cover the broader entitlement counting method in our licensing compliance pillar guide.
Test and dev compliance checklist
- Inventory of every non production environment running Oracle software.
- Identification of the license basis for each environment, OTN or full commercial.
- Documentation of the data held in each environment, synthetic or production copy.
- Confirmation of the options and packs installed in each non production environment.
- Verification that disaster recovery environments are licensed under the correct rule.
- Reconciliation of non production footprint against the total entitlement.
- Documentation of the license basis decision for audit defence.
The disaster recovery trap.
Disaster recovery environments deserve specific attention because Oracle's rules are precise and widely misunderstood. Oracle permits a limited use of a backup environment under the ten day rule. The ten day rule allows a customer to run production workload on an unlicensed failover node for up to ten separate days in a calendar year, where the failover node is in the same cluster and uses the same storage as the primary. The rule is narrow. A warm standby that is mounted and applying redo does not qualify because it is considered installed and running. A cold backup that is never started does not require a license. The buyer side discipline is to classify every disaster recovery environment as cold standby, warm standby, or active standby and to apply the correct rule for each.
Active Data Guard environments are the most common disaster recovery finding because Active Data Guard is a separately licensed option and the standby must be licensed for both the database and the option. We cover this specific exposure in our Active Data Guard pricing article.
Options and packs in non production.
The options and packs exposure is amplified in non production environments because engineers enable features for testing without realising the features are separately licensed. The Diagnostics Pack and Tuning Pack are enabled by default in many Enterprise Edition installations and are heavily used in development and performance testing. Partitioning is used in test environments that mirror production schemas. Advanced Compression is enabled to reduce test storage. Each of these features requires a license in the non production environment exactly as it does in production. The buyer side discipline is to audit the feature usage of every non production environment using the same scripts that Oracle uses, and to disable any feature that is not licensed and not required.
The named user alternative.
For non production environments the Named User Plus metric is sometimes a more economical license basis than the Processor metric. A development environment typically has a small and identifiable population of developers and database administrators. If that population is below the Processor to Named User Plus conversion ratio, licensing the environment by named user is cheaper. Oracle's minimum named user counts per processor still apply, so the calculation is not automatic, but for small development teams the named user basis frequently reduces the non production license cost. The buyer side discipline is to model both metrics for every non production environment and to select the lower cost basis before the environment is licensed.
The negotiation opportunity.
Non production licensing is a strong negotiation lever because it is a cost the buyer can often eliminate or reduce without affecting production. The buyer side opportunities are to decommission redundant non production environments, to revert environments to genuine synthetic data under the OTN license, to consolidate development databases onto fewer servers, and to negotiate a non production licensing concession at a renewal or a license purchase. Some customers negotiate a defined non production allowance into the contract that permits a stated quantity of development and test usage without additional license. This is a contract drafting exercise and should be reviewed in a formal contract review. The audit defence side of non production exposure is handled through our audit defense service.
Related resources.
- Licensing Compliance pillar guide
- Audit Defense service
- Contract Review service
- Database Licensing deal type page
- Oracle Database product page
- Oracle Audit Defense Handbook 52 page reference paper.
- Database Options and Pack Compliance related sub article.