Oracle permits customers to run their database on an unlicensed spare server for up to 10 separate calendar days per year. This article explains exactly how it works, how Oracle counts the days, practical examples, common misconceptions, and best practices for compliance.
Understanding Oracle licensing for failover environments is critical. Especially given the complexities surrounding compliance and potential audit penalties. Before explaining the 10-day rule, it is important to clarify Oracle's licensing context for failover scenarios.
A failover environment is a backup system that automatically activates if the primary production system fails. A standby environment typically uses Oracle technologies such as Data Guard or third-party clustering solutions to replicate and quickly recover data.
Oracle typically requires licensing for all servers running Oracle software, including failover or standby environments. If Oracle software is installed on a server, it must be licensed. Regardless of whether it is actively running. The 10-Day Rule is a limited exception to this principle, offering restricted flexibility for genuine failover scenarios only.
Oracle's 10-Day Rule refers explicitly to their failover licensing policy. In simple terms: you can use an unlicensed spare/failover server for 10 calendar days per year. Usage beyond this period requires the spare server to be fully licensed.
This rule is strictly defined and explicitly limited. It applies only to passive spare nodes in clustered configurations that share a disk array and are used exclusively during genuine failover events.
The 10-day rule is one of Oracle's most misunderstood policies. Many organisations assume it provides broad DR coverage. It does not. It applies only to passive failover nodes in clustered setups with shared storage. A cloud DR site in a different data centre or region is generally treated as a separate environment and does not qualify for the 10-day exception. Active Data Guard usage is also explicitly excluded.
| Counting Rule | Detail |
|---|---|
| Unit of measurement | One calendar day (24-hour period, midnight to midnight). |
| Partial-day activation | Even 15 minutes of activation counts as one full day toward the 10-day limit. |
| Multiple activations per day | Multiple brief activations within the same calendar day count as one day only. |
| Consecutive requirement | Days do not need to be consecutive. Each separate day of activation is counted individually. |
| Annual reset | The 10-day counter resets on January 1st every calendar year. |
| Reset trigger | Resets on January 1st. Not on licence renewal dates or fiscal year-ends. |
Primary Oracle database on Server A fails on January 15. Failover to standby Server B is activated for 6 hours that day.
Oracle counts one full day of the 10-day allowance. 9 remaining failover days for the calendar year.
Server A experiences brief outages on three occasions. March 5: failover activated for 30 minutes. June 10: failover activated for 2 hours. July 20: failover activated for 15 minutes.
Oracle counts three separate calendar days. 7 remaining failover days for the year. Duration does not matter. Each calendar day where the failover server was active counts as one full day.
Primary Oracle server experiences severe issues. Failover server activated continuously from August 1 through August 15 (15 calendar days).
Days 1 to 10 (August 1 to 10) are covered under the 10-day allowance. Days 11 to 15 (August 11 to 15) require full licensing immediately. Oracle expects licences to be in place immediately upon exceeding the 10-day limit. Not after the fact. If your failover server runs Oracle for an 11th day without a licence, you are non-compliant from that moment. Oracle auditors will request logs or documentation of every failover event and duration.
| Consideration | Detail |
|---|---|
| Monitoring and documentation | Accurately track every failover event, date, and duration. Oracle auditors frequently request these records. |
| Calendar-year limit | The 10-day count resets annually on January 1st, providing a fresh allowance each year. |
| Passive only | The failover server must remain completely passive. No reporting, backups, queries, or testing outside actual failover scenarios. |
| Virtualisation complexity | Oracle requires licensing for all physical hosts potentially running Oracle workloads if virtualised. The 10-day rule can apply, but only clearly defined usage qualifies. |
| Cloud DR sites | The 10-day rule does not automatically apply to cloud DR setups. A cloud DR site in a different data centre/region is generally treated as a separate environment requiring its own licences. |
| Active Data Guard | Active Data Guard usage is explicitly excluded from the 10-day rule. Any read-only queries on a standby require full ADG licensing regardless of duration. |
Oracle's Software Investment Guide contains the definitive language on this policy. The official wording states that in failover configurations, nodes are configured in clustered configurations and share one disk array. Oracle permits licensed Oracle customers to run Oracle programs on an unlicensed spare computer for up to a total of ten separate days in any given calendar year. Any other use requires the environment to be fully licensed.
This official wording clarifies three critical constraints. First, the rule applies strictly to passive spare nodes in clustered configurations. Second, the nodes must share one disk array, meaning shared storage in the same cluster. Third, the limit is 10 separate days in any given calendar year. A cloud DR site in a different data centre, a remote standby using Data Guard replication over a WAN, or any server performing active duties such as read-only queries does not qualify under this exception.
| Misconception | Reality |
|---|---|
| Multiple brief activations in one day count as multiple days. | Oracle counts calendar days, not occurrences. Multiple activations within the same day count as one day. |
| The 10-day rule resets after a licence renewal. | The counter resets annually on January 1st. Not with licence renewals or fiscal year-ends. |
| The failover node can be used for occasional reporting or testing. | Oracle strictly prohibits active usage. Reporting, testing, and queries require full licensing immediately regardless of duration. |
| If the DR server is powered off, I do not need a licence. | If Oracle software is installed on a server, it must be licensed regardless of whether it is running. The mere presence of Oracle binaries can trigger a licence requirement. |
| I can use my production licences on the DR server during failover. | Only partially true. The 10-day rule provides temporary coverage. Beyond that, you cannot simply reassign licences without proper contractual provisions. |
| The 10-day rule covers cloud-based DR sites. | The rule is intended for spare servers in the same on-premise cluster. Cloud DR sites in different data centres/regions are generally treated as separate environments. |
Maintain detailed records including dates, exact durations, and reasons for activation. This evidence is critical during Oracle audits. Without documentation, Oracle's default position is to count all days as failover days, potentially pushing you over the 10-day limit.
Any query, reporting, backup, or testing on the standby server invalidates the 10-day rule and triggers immediate licensing requirements. This is the single most common violation we see in audit engagements. Even a single ad-hoc query against the standby database changes its status from passive failover to active usage.
If your environment regularly approaches or exceeds 10 days annually, licence the failover server to ensure compliance. The cost of licensing a standby server is significantly less than the audit penalty for non-compliance. If you have used 7 or more days by mid-year, treat the remaining allowance as a buffer, not a target.
Database and infrastructure teams must understand the licensing limits. Accidental activation for maintenance or patching counts against the 10-day allowance. We have seen organisations burn through their entire 10-day allowance on planned maintenance windows because the infrastructure team was unaware that each planned failover consumed a day.
Oracle's hard partitioning rules interact with failover licensing. Ensure your virtualisation architecture is clearly defined and that the failover configuration meets Oracle's clustered-with-shared-storage requirement. In VMware environments, vMotion and DRS can move Oracle workloads to unlicensed hosts automatically, creating compliance exposure.
OCI allows you to keep DR instances dormant (stopped) and only consume licences when running. This is potentially more cost-effective than on-premise standby licensing. However, this operates under OCI's cloud licensing rules, not the traditional 10-day rule. The mechanisms are different.
When negotiating Oracle agreements, explicitly address DR/failover licensing terms. Some customers negotiate more favourable provisions than the standard 10-day rule. Options include extended failover allowances (20 or 30 days), DR site licensing at reduced rates, or explicit provisions covering cloud-based DR environments.
Yes. Oracle always counts calendar days, regardless of duration. Even 15 minutes of activation counts as a full day toward the 10-day limit.
Oracle typically applies the rule per failover configuration. If multiple standby servers exist, verify with Oracle or an independent licensing expert to avoid unintended non-compliance. Each configuration may have its own 10-day allowance, but this depends on the specific clustered setup.
No. The 10-day rule strictly applies to passive failover scenarios only. Any active use including queries, reporting, backups, or testing invalidates the rule and requires immediate full licensing of the server.
Oracle immediately requires full licensing of the standby server for all additional days used beyond the initial 10. Licences must be in place from the 11th day onward, not retroactively. Exceeding the limit without licences constitutes non-compliance and can result in significant audit penalties.
No. Active Data Guard is a separately licensed option that enables read-only queries on the standby. Because the standby is actively processing data, it requires full licensing at all times. The 10-day failover exception does not apply.
The 10-day rule is intended for spare servers in the same on-premise cluster with shared storage. Cloud DR sites (AWS, Azure, or even OCI in a different region) are generally treated as separate environments requiring their own licences. Oracle Cloud Infrastructure does offer specific advantages such as keeping DR instances stopped and only consuming licences when running, but this is a different mechanism from the 10-day rule.
Yes. Any activation of the Oracle database on the standby server counts toward the 10-day limit. This includes planned maintenance windows, patching activities, and testing. Infrastructure teams must be trained to understand that these planned activities consume the same limited allowance as unplanned failovers.
Yes. When negotiating Oracle agreements, you can request extended failover allowances such as 20 or 30 days, DR site licensing at reduced rates, or explicit provisions covering cloud-based DR environments. These concessions are negotiable and Oracle will consider them as part of a broader commercial discussion. The key is to raise DR licensing explicitly during contract negotiations, not during an audit.
Independent Oracle advisory helping enterprises navigate failover licensing, audit defence, and DR compliance. Share your environment details and we will provide an independent compliance assessment.