Licensing glossary
What is an Oracle ULA?
An Oracle Unlimited License Agreement (ULA) grants the right to deploy unlimited quantities of the Oracle programs it names for a fixed term, then you certify what you deployed.
How it works
During the term you deploy as much of the covered programs as you need without buying further licenses, and the core factor table does not apply. Oracle publishes no standard term; the length and the certification mechanics are in your contract.
At the end you certify usage, declaring what you have deployed of each covered program. The certified quantities become the licenses you keep. Anything beyond them, or any program the ULA never covered, needs licenses of its own. A Perpetual ULA (PULA) has no end date, but it does not end audits.
Worked example
Illustrative numbers. At the end of the term the covered database runs on 400 Processors, 150 of them on AWS:
- Deployed at term end
- 400 Processors
- On AWS, Azure or Google Cloud
- 150, excluded by Oracle's cloud policy
- Certified
- 250 Processors
- Cloud workloads after the ULA
- Need licenses of their own
Oracle's cloud policy lets you use ULA licenses in those clouds during the term, but they cannot be included in the certification.
What to watch
- Moving workloads to AWS, Azure or Google Cloud late in the term. Everything there drops out of the count you certify.
- Programs the agreement does not name. They need licenses whatever the ULA says.
- The certification date. Your license position needs it, with the products the ULA covers.
- Treating a PULA as audit-proof. The audit terms of your license agreement still apply.