A ULA count is not just production. Test, development, and disaster recovery instances of the named products all count toward your certification if they were deployed within the term and you can evidence them. Leaving non production out of the count is one of the most common ways organisations lose entitlement.
Every environment running a named Oracle product is a candidate for your certified count, not only production. Test, development, disaster recovery, and standby instances deployed within the term qualify in most agreements, because a ULA does not generally grant a free non production allowance. The instances exist whether or not you count them, so the only question is whether you capture and evidence them before the cutoff.
Under standard Oracle licensing, a test or development database running the licensed software is a licensed deployment like any other. A ULA does not change that principle; it simply makes the deployment unlimited during the term and converts it to a perpetual entitlement at certification. So when you certify, the test and development estate you built during the term is legitimate entitlement to capture, not a grey area to avoid. Teams that certify only their production footprint hand back the perpetual value of everything else they were running, and they often discover later that the non production estate was a large share of the total.
Yes. Test and development instances of the named products, deployed and running within the term, count toward the certified quantity in most agreements. Oracle does not generally provide a free non production tier under a ULA, which means those environments are licensed deployments that belong in your count. The practical task is finding them all, because test and development estates are often sprawling, informally provisioned, and poorly inventoried. A thorough discovery across the estate, not just the production data centre, is what turns these instances into counted entitlement.
In most cases yes. An installed and configured disaster recovery instance is a deployment of the product, and a deployment counts. The important caveat is that the detail depends on your contract and on how the standby is run, because some Oracle policies treat particular failover and backup configurations differently from a fully installed standby. A passive standby that has the software installed is generally a deployment; a configuration that Oracle policy treats as failover may be handled differently. Because this is contract specific, the disaster recovery position should be confirmed against your agreement before you rely on it in the count, and the way the standby is configured during the term can be planned with the certification in mind.
Count everything you are genuinely entitled to count, across production and non production, and evidence each instance. A complete, defensible count is worth far more than a cautious one, because support stays flat regardless of the number.
A counted instance is only as good as the record behind it. For each one you should be able to show that it was installed and running before the deployment cutoff, on what hardware, and running which product and options. That means server and instance inventories, build or change records that establish the install date, and measurement output that captures the cores and the products in use. This evidence does double duty: it justifies the count at certification, and it defends the position if Oracle examines it in the first two years afterward, when audit risk is highest. Evidence cannot be created after the fact, so it is gathered while the environments are live.
Consider an anonymized financial services firm certifying a database ULA. Its first internal estimate counted only the production clusters. A full discovery added a substantial test and development estate and a disaster recovery site that mirrored production, each installed within the term and each evidenced with inventories and build records. The certified count rose well above the production only figure. The numbers here are indicative and the outcome depended on that specific estate and contract, but the pattern is consistent: production is usually a fraction of the defensible total once non production is properly counted.
| Environment | Counts toward certification? | Evidence to hold |
|---|---|---|
| Production | Yes, if deployed in term | Inventories, measurement output |
| Test and development | Yes, in most agreements | Discovery records, install dates |
| Disaster recovery, installed standby | Usually, contract specific | Build records, configuration detail |
| Failover per Oracle policy | Depends on configuration and contract | Policy mapping, configuration evidence |
Counting well raises a tooling question and a risk question. Read Oracle LMS scripts, run them or not for how to gather measurement output on your terms, and the overcount risk and its cost for the discipline that keeps a maximized count defensible. For the full mechanics, the Oracle ULA certification guide sets out how the count fits the certification.
Yes. Test and development instances of the named products, deployed and running within the term, count toward the certified quantity in most agreements. Oracle does not generally grant a free non production allowance under a ULA, so these environments are legitimate licensed deployments that belong in the count, provided you can evidence them.
In most cases yes, because an installed and configured disaster recovery instance is a deployment. The detail depends on your contract and on how the standby is run, since some Oracle policies treat certain failover configurations differently. Because it is contract specific, the disaster recovery position should be checked against your agreement before you rely on it.
Each counted instance should be supported by records showing it was installed and running before the deployment cutoff: server inventories, build or change records, and measurement output showing the cores and product in use. The evidence is what converts a claimed deployment into a defensible one if Oracle questions the count.
Book a confidential assessment and we will discover your full estate, count production and non production correctly, and evidence each instance for a defensible certification.