What is the difference between term and perpetual licenses?
The difference is duration: an Oracle term license grants the right to use the software for a fixed period, often one to five years, while a perpetual license grants that right with no end date. Both are real licenses that permit deployment within the metrics and conditions of the agreement. What separates them is what happens at the end of the term. The perpetual license keeps granting the right indefinitely, with annual support as a separate renewable layer. The term license stops granting anything when the clock runs out.
That single difference drives everything else. A perpetual license is an asset the buyer holds for as long as the software is used, and the recurring cost is the support fee. A term license is a time boxed right, cheaper to acquire because it expires, that requires the buyer to either stop using the software, retire it, or buy again before the end date. Reading the agreement to know which kind of license covers each deployment is the first step in managing either one.
What happens when an Oracle term license expires?
When an Oracle term license expires the right to use the software ends, so any deployment still running on it becomes unlicensed at that moment. There is no grace built into the right itself: the software does not stop working, but the legal permission to run it does. A database, option or product that was fully compliant the day before expiry is exposed the day after, and that gap is exactly the kind of finding an audit is built to surface.
This makes expiry tracking a compliance task, not a procurement footnote. The buyer needs to know the end date of every term license, what it covers, and what the plan is at expiry: retire the deployment, migrate it onto a perpetual entitlement, or renew the term. Leaving the date untracked is how a term license becomes an unplanned liability, because the deployment keeps running on momentum while the right underneath it has lapsed. Oracle's preliminary findings arrive inflated at list price, and an expired term claim is straightforward for Oracle to assert and expensive to ignore.
| Attribute | Term license | Perpetual license |
|---|---|---|
| Right to use | Fixed period | Indefinite |
| Up front cost | Lower | Higher |
| End of term | Right ends | Right continues |
| Main buyer risk | Running past expiry | Support cost growth |
Which is cheaper, term or perpetual?
Term is cheaper up front and perpetual is cheaper over a long horizon, so the answer depends on how long the software will actually be used and is contract dependent. A term license carries a lower acquisition cost because the buyer is paying for a defined window rather than a permanent right. Over a short project, a fixed migration, or a use case with a known end date, that lower cost is genuine value. The right expires when the need does, and nothing is wasted.
Perpetual licensing wins when the software will run for many years, because the buyer pays once for the right and then only the annual support fee, which runs at roughly 22 percent of the license cost with annual escalation. Repeatedly renewing a term license for a long lived deployment can cost more than buying perpetual would have. The mistake to avoid is choosing term for short term reasons and then keeping the deployment for the long term, which combines the higher lifetime cost of repeated terms with the exposure of an expiry date that someone has to remember.
How do term and perpetual licenses show up in an audit?
In an audit, term licenses show up as a date check and perpetual licenses show up as a metric check, so the two demand different defenses. For a term license, the central question is whether the deployment is still inside its term, which makes the expiry date and the deployment date the evidence that matters. For a perpetual license, the term never lapses, so the audit focuses on whether usage stays within the licensed metric and quantity, the same processor and Named User Plus questions that apply to any Enterprise Edition deployment.
Because audits are a sales channel, an expired or expiring term license is an attractive lever for Oracle: it converts cleanly into a renewal or an upsell. The buyer move is to hold a current record of every term license and its end date inside the estate map, so an expiry claim can be met with the actual dates rather than reconstructed under a 30 to 45 day response window. An independent line by line review of findings typically cuts claims by 60 to 80 percent, and term license claims that rest on misread dates or already retired deployments are among the easiest lines to remove with good records.
How do you manage the choice between them?
You manage the choice by matching the license type to the lifespan of the deployment and then tracking the commitments you take on. Short, bounded needs suit term licensing because the lower cost matches the limited use and the expiry is a feature rather than a risk. Long lived production systems suit perpetual licensing because the right never lapses and the only recurring cost is support. Making that match deliberately, at the point of purchase, avoids the expensive accident of a long term deployment riding on a short term license.
The governance that follows is straightforward but easy to neglect. Record every term license end date, review the estate periodically so an approaching expiry is seen well before it arrives, and decide early whether each term deployment will be retired, migrated to perpetual, or renewed. The same discipline keeps perpetual licenses defensible by tracking their metrics and quantities. A buyer who knows which licenses expire, when, and what covers each deployment turns the term versus perpetual question from an audit risk into a managed commercial decision.
The next step
This article is part of our Database Licensing cluster. Read the pillar, the Oracle database licensing guide, for the full picture, and these related reads: SE2 socket rules and their limits, and Multitenant and pluggable database licensing. For the engagement, see our database licensing advisory service, or reach us through contact.