Oracle Support Rewards and OCI

Oracle Support Rewards and OCI

Oracle Support Rewards offer financial credits to customers who consume Oracle Cloud Infrastructure (OCI). In simple terms, it’s a program that ties OCI cloud spending to Oracle support cost reduction. Organizations earn credits from their OCI usage, which can be used to offset Oracle software support fees.

This guide breaks down how the program works, how credits accumulate, which OCI services qualify, and how to plan your cloud strategy around these rewards.

The goal is to help CIOs, CTOs, finance teams, and cloud architects clearly understand this OCI financial incentive and use it to lower Oracle support bills.

For more information, read our ultimate guide, Oracle OCI (Cloud Infrastructure) Licensing.

Step 1 – Understanding the Support Rewards Program

The Oracle Support Rewards program provides a straightforward deal: use OCI services and get rewarded with credits that reduce your Oracle support costs. It’s Oracle’s way of encouraging cloud adoption by giving back a portion of your spend as savings on support.

The program is available to most Oracle customers with on-premises software support contracts who start using OCI under a Universal Credits subscription.

In essence, your cloud infrastructure budget can directly subsidize your database and middleware support bills. This foundation is key to planning any OCI move because it links cloud spend to support savings predictably.

Checklist: Support Reward Basics

• ✔ Earn credits from OCI spend – Your OCI usage generates reward credits.
• ✔ Apply credits to Oracle support invoices – Credits can be used as payment toward eligible support fees.
• ✔ Credits reduce annual support bills – Over time, your yearly support costs go down thanks to the applied credits.
• ✔ Available to many Oracle Cloud customers – Most customers with Oracle software support and an OCI Universal Credits plan can enroll.
• ✔ Requires active OCI usage – You must consume OCI services to accrue rewards (idle accounts or free trials don’t count).

Table: Program Overview

In summary, Oracle Support Rewards links your OCI cloud spend directly to savings on your Oracle support costs. It’s a simple concept with powerful implications: the more you invest in OCI, the more you get back in support value.

Step 2 – How Support Credits Accumulate

Support Reward credits accumulate based on your OCI consumption, following a clear formula. For every dollar you spend on OCI services, you earn a percentage back as credit (generally 25%).

Customers with certain agreements, such as an Unlimited License Agreement (ULA), accrue at a higher rate (33%). Oracle tallies your eligible OCI usage at the end of each month and deposits the corresponding credits into your rewards account. These credits can then be applied to upcoming support invoices.

The system is dynamic: higher OCI usage means more credits, with no upper limit on how much you can earn. However, there are rules to keep in mind – notably, credits expire 12 months after they’re earned, so timing and usage are important to ensure you don’t lose any value.

The key takeaway is that credits grow in line with your OCI usage, turning cloud spend into a growing pool of support savings.

Checklist: Credit Accumulation

• ✔ Earn credits based on OCI consumption – e.g. $0.25 credit per $1 of OCI spend (or $0.33 for ULA customers).
• ✔ Higher spend increases total credits – The more you use OCI, the more credits you rack up (no fixed cap).
• ✔ Credits accumulate monthly – Rewards are calculated and added at the end of each month’s usage.
• ✔ Credits apply to future invoices – You can apply earned credits toward upcoming Oracle support bill payments.
• ✔ Unused credits have rules – Credits expire 12 months after issuance if not used, so plan to utilize them before expiry.

Table: Credit Accumulation Logic

In essence, the program rewards you based on your cloud usage. The accumulation is predictable and transparent: as your OCI usage grows, so do your support credits. Just remember to use those credits within a year – this ensures your OCI support rewards continually reduce your costs rather than expiring unused.

Read about pricing on OCI, OCI Pricing and Oracle Licensing.

Step 3 – Eligible OCI Services and Spend Categories

Not every cloud service is equal in the Support Rewards program, but almost all core OCI services count toward earning credits. Oracle has broadened the program so that typical cloud workloads will qualify for rewards. Compute instances, storage volumes, Oracle database services, networking bandwidth, and many platform services are all eligible.

Whether you’re running virtual machines, storing data, using Oracle Autonomous Database, or leveraging integration and analytics services on OCI, the money you spend on those services will translate into support credits.

Only a few exceptions exist – for example, third-party offerings through the Oracle Cloud Marketplace or specialized partner services (like VMware solutions or Microsoft licensing components) do not earn rewards.

Also, spending on Oracle SaaS applications (Cloud Applications) doesn’t count, since those are separate from OCI infrastructure. The important point is that most OCI consumption qualifies, especially the fundamental infrastructure and platform services that enterprises commonly use.

Checklist: Eligible Spend

• ✔ Compute services – VMs, bare metal, container services, etc.
• ✔ Storage services – Block storage, object storage, file storage.
• ✔ Database services – Autonomous Database, Exadata Cloud Service, DB systems.
• ✔ Networking spend – Data egress, load balancing, VPN, and related network resources.
• ✔ Platform and integration tools – Native OCI platform services (integration, monitoring, analytics, etc.) on the Universal Credits model.

Table: Eligible Categories

Virtually all primary OCI services will earn Support Rewards, meaning your typical cloud infrastructure spending is covered.

By focusing on OCI’s core offerings, you ensure that every dollar spent on those services is coming back to you as a credit against your Oracle support bills. (Just avoid assuming spending on third-party marketplace items or Oracle SaaS products will count – stick to OCI infrastructure and platform usage for rewards.)

Step 4 – Which Support Bills Can Be Reduced

Support Rewards are designed to offset the maintenance fees for Oracle technology products. In practice, this means you can apply the credits to your on-premises software support contracts for databases, middleware, and other Oracle technology licenses.

For example, if you pay annual support for Oracle Database or Oracle WebLogic Server licenses, those invoices can be reduced by the OCI credits you’ve earned. Even support costs for Oracle [email protected] (Oracle’s cloud-at-customer offering) are eligible, since it’s essentially an on-premises subscription to Oracle technology.

The program targets recurring support fees – the yearly “Software Update License & Support” costs that IT budgets struggle with. It’s important to note what’s not covered: you cannot use these rewards to pay for Oracle application support (such as Oracle E-Business Suite or other SaaS/ERP support contracts), and they won’t apply to services like Oracle consulting fees or any non-support costs.

The focus is purely on technical software support for Oracle products. By using Support Rewards, companies can significantly lower these recurring support bills, directly reducing operating expenses for Oracle software.

Checklist: Support Offset Rules

• ✔ On-premises license support – Yes, apply credits to support fees for Oracle database, middleware, and other technology licenses.
• ✔ Oracle [email protected] support – Yes, support charges under the Cloud@Customer model (UCM portion) can be offset with credits.
• ✔ Support for DB and middleware – Yes, core tech support contracts (Oracle Database, Middleware, etc.) are eligible for reduction.
• ✔ Excludes Oracle applications & consulting – No, credits cannot reduce support for Oracle enterprise apps (e.g. ERP) or pay for consulting/services engagements.
• ✔ Reduces recurring support totals – The program is intended to chip away at the annual support renewal costs for Oracle technology products.

Table: Support Offset Targets

Oracle Support Rewards are specifically designed to offset your ongoing technical support fees. This means each year (or each billing period), you can apply the credits to lower what you owe for database and middleware support.

By contrast, contracts outside standard support – such as cloud application subscriptions or consulting projects – must be paid for in the normal way. The net effect is a reduction in your recurring Oracle support spend, easing the burden of those yearly maintenance bills.

Step 5 – Comparing Support Rewards to Traditional Discounts

It’s useful to compare Oracle’s Support Rewards with traditional discounting methods. In the past, if you wanted to lower your Oracle support costs, you’d typically negotiate a discount or concession with Oracle (often tied to a large purchase or a strategic deal). Those traditional discounts are upfront and static – for example, Oracle might give you a 10% support discount on a certain contract, and that fixed percentage stays the same each year.

Support Rewards, on the other hand, are dynamic and earned, not given outright. Instead of negotiating money off, you’re generating credits by using OCI. The savings materialize as you consume cloud services, essentially functioning like an ongoing rebate.

Another difference is timing and scalability: a negotiated discount applies regardless of what you do (and usually won’t increase without another negotiation), whereas Support Rewards will scale with your cloud usage – the more you migrate to OCI, the larger your effective support discount becomes.

Also, traditional support discounts can be hard to get and often require long negotiations or commitments. Support Rewards require no haggling once you’re enrolled; they automatically accrue with consumption.

In essence, Oracle has shifted the model from one-time negotiated savings to continuous, usage-based savings, directly incentivizing cloud adoption through tangible support cost relief.

Checklist: Comparison Points

• ✔ Support Rewards reduce future bills – Credits earned now lower the support invoices you’ll pay going forward.
• ✔ Traditional discounts reduce upfront cost – Negotiated support or license discounts give an initial reduction, but typically fixed in value.
• ✔ Rewards apply every billing cycle – Each support billing period, you can use new credits (earned from ongoing OCI usage) to cut costs.
• ✔ Rewards scale with cloud growth – As your OCI usage grows, your support savings grow in tandem (no need to renegotiate to save more).
• ✔ Discounts require negotiation – Conventional discounts or concessions usually involve deals and contracts, whereas rewards are automatic via program participation.

Table: Discount Comparison

Support Rewards clearly incentivize cloud adoption in a way traditional discounts do not. Instead of giving you a one-time break, Oracle set up a system where your ongoing behavior (moving workloads to OCI) is rewarded continuously. This means customers have a financial reason to keep shifting appropriate workloads to Oracle Cloud – the more you use OCI, the less you effectively pay in support. In contrast, a traditional discount might save some money but won’t encourage further cloud usage after the deal is signed. Support Rewards align your cost savings with Oracle’s cloud usage goals, creating a win-win: you reduce expenses, and Oracle gains a cloud workload.

Step 6 – Support Rewards Impact on Total Cost of Ownership

When evaluating the total cost of ownership (TCO) of Oracle systems, Support Rewards add a new dimension. Oracle software TCO traditionally includes license costs (often one-time), annual support, and the infrastructure costs to run the software (hardware or cloud).

By moving workloads to OCI and leveraging Support Rewards, you effectively create a feedback loop that lowers part of that TCO.

Here’s how it breaks down: you will incur OCI cloud costs (which might be new if you were on-premises before), but you’ll simultaneously reduce your Oracle support costs by applying the earned credits. The annual support reduction can be significant, translating into much lower operating costs for those Oracle systems over multi-year periods.

This means the ROI for migrating to OCI improves – some of the cloud spending is “returned” via support savings, offsetting the overall expense.

Additionally, the pattern of these offsets can be forecasted. If you know how much you plan to spend on OCI, you can predict how much support credit you’ll earn each year, bringing predictable offset patterns into your financial planning.

Over time, organizations might find they are less reliant on special discounts or extreme cost-cutting measures to manage Oracle costs, as the Support Rewards program automatically covers a portion of them.

The net effect: a lower total cost of ownership over the long run, making the business case for OCI more attractive when considering all factors.

Checklist: TCO Factors

• ✔ Annual support reduction – Year after year, support fees go down by the value of OCI-earned credits.
• ✔ Lower long-term operating cost – Over the long haul, the cost to run Oracle software (licenses + support + cloud) decreases thanks to support savings.
• ✔ Higher ROI for OCI migrations – Projects to move Oracle workloads to OCI see better returns because part of the cloud spend comes back as support credit.
• ✔ Predictable offset patterns – Support savings can be forecast based on planned OCI usage, aiding in budget planning and TCO calculations.
• ✔ Reduced dependency on discounts – Less need to negotiate special deals or concessions on support, since the program continuously offsets costs.

Table: TCO Impact

Incorporating Support Rewards into your financial analysis can shift your budget decisions in favor of Oracle Cloud. While you will spend on OCI, you’re simultaneously trimming your support expenses.

When added up, many organizations find the effective net cost of running Oracle software on OCI is lower than it would be otherwise.

This can be a tipping point when evaluating options – the support savings essentially subsidize your cloud investment, improving the total cost outlook for staying within the Oracle ecosystem.

Step 7 – Example Scenario: Support Rewards in Action

To see how this works in practice, let’s walk through a simple scenario. Imagine an organization that pays for Oracle database and middleware support annually and decides to migrate some systems to OCI.

We’ll use round numbers to illustrate the impact. By plugging in a few basic inputs – their OCI spend, the reward rate, and their support bill – we can calculate the rewards earned and the resulting support savings.

Checklist: Example Inputs

• ✔ Monthly OCI spend: $100,000 per month on OCI services (new cloud workloads)
• ✔ Applicable reward rate: 25% credit earned on OCI spend (standard rate for non-ULA customers)
• ✔ Annual support bill: $600,000 per year for existing Oracle software support
• ✔ Credit application: OCI spend generates credits applied to the next support invoice
• ✔ Net support reduction: Support bill is cut approximately in half after applying credits

Table: Example Walkthrough

In this scenario, the company’s moderate OCI usage (about $1.2 million annually) yields $300,000 in Support Rewards over the year. They apply those credits to their $600,000 support invoice, slashing the bill by half.

The result is meaningful savings: $300k less in support costs, achieved simply by utilizing OCI for part of their infrastructure needs. Even with these moderate workloads running on Oracle Cloud, the support rewards are substantial. For a ULA customer with the higher 33% rate, the savings would be even greater.

This example demonstrates how quickly the economics can shift – a relatively routine amount of cloud usage can translate into hundreds of thousands of dollars in savings on the support side. The takeaway is that even a modest OCI adoption can significantly reduce your Oracle support expenses.

Step 8 – Planning a Cloud Migration with Support Rewards in Mind

When planning a migration to OCI, it’s smart to factor Support Rewards into your strategy from the beginning. This ensures you maximize the benefits and time things correctly to get the most out of the program.

Start by identifying which Oracle support contracts are eligible for rewards redemption – typically, your database and middleware support bills. Knowing the dollar amounts and renewal dates of those contracts will help set targets for how much OCI spends (and credits) you’ll need to make a dent in those costs.

Next, map your workloads to OCI services with an eye on those that will generate significant OCI consumption.

For example, migrating an Oracle database to OCI not only shifts infrastructure but also directly contributes to rewards that offset that database’s support fees. It’s useful to estimate credit accrual over time as you migrate: create a forecast of OCI spend by month or quarter, and thus expected credits, to see how they align with your support renewal cycles.

Timing is important – try to align cutover with billing cycles. If your big support renewal is every January, plan migrations so that by the time the invoice arrives, you’ve accrued as many credits as possible to apply.

You don’t want to migrate right after paying a support bill, only to have credits sitting idle until the next cycle; it’s better to have them ready to reduce the upcoming bill. Finally, actively track cumulative savings once you begin migration.

This means keeping a running total of the dollars of support costs offset by Support Rewards. That information is powerful for demonstrating the value of the cloud move to stakeholders in finance and leadership. It also helps in adjusting your plan – if savings are falling short or exceeding expectations, you can tweak the migration pace or target additional systems to move.

Checklist: Migration Planning Actions

• ✔ Identify eligible support contracts – List which Oracle support invoices (databases, middleware, etc.) can be paid with rewards.
• ✔ Map workloads to OCI services – Plan which applications or databases to move to OCI, focusing on those that will both benefit from cloud and generate rewards.
• ✔ Estimate credit rate over time – Forecast your OCI spend and calculate expected monthly credits to see the trajectory of reward accrual.
• ✔ Align cutover with billing cycles – Schedule migrations so that accrued credits are available before major support renewal payments are due.
• ✔ Track cumulative savings – Monitor how much support cost you’ve offset as the migration progresses, to inform budgeting and demonstrate ROI.

Table: Migration Framework

By planning with Support Rewards in mind, you effectively build a migration business case that includes a rebate on the tail end. This can influence which systems you prioritize moving (perhaps the ones with high support costs first) and how you time the project.

The result is a cloud migration that not only delivers technical and business benefits, but also maximizes financial incentives – you’re not leaving any support savings on the table. Good planning ensures you hit the ground running, with OCI usage translating into support reductions from day one.

Step 9 – Governance for Support Rewards Tracking

Once you’re leveraging Support Rewards, governance and oversight become important to capture the full value. After all, you want to make sure every credit earned is actually used to save money. Establishing some internal processes will help your organization stay on top of this.

First, set up a monthly routine to track OCI spend. This can be as simple as reviewing the OCI billing reports or using Oracle’s cost management tools to verify how much you spent and that the corresponding reward credits were accrued correctly.

Next, track the credit accumulation itself. Oracle’s cloud console provides a Support Rewards dashboard – use it to check your current credit balance and note when credits will expire.

Expiration management is crucial: you might adjust plans to use expiring credits on the next available support invoice. It’s also wise to verify the credit application whenever you use rewards on an invoice. In practice, this means ensuring that when a support bill comes due, the credits are properly applied through Oracle’s billing system (often by obtaining a reward redemption code and applying it to the invoice).

Having someone double-check that the support invoice reflects the credit deduction prevents oversight that could lead you to pay cash for something that could have been credited. Coordination with your finance or procurement team is essential, so coordinate with finance teams early.

Finance will be paying the support bills, so they need visibility into the amount of available credit to reduce those payments. This avoids confusion and ensures the budget reflects the lowered costs. Finally, maintain documentation of all this – keep records of OCI usage, credits earned, credits applied, and resulting savings.

This helps audit the program’s success internally and for any discussions with Oracle. With these governance steps, you create a safety net around the program so that no savings slip through the cracks. Proper tracking and communication mean you realize the full potential of Support Rewards without administrative hiccups.

Checklist: Governance Actions

• ✔ Track OCI spend monthly – Monitor your OCI usage and costs each month to ensure expected credits are accruing.
• ✔ Track credit accumulation – Keep an eye on your reward balance and expiration dates; know how many credits are available at any time.
• ✔ Verify credit application – When paying support invoices, confirm that earned credits are applied correctly (no credits left unapplied).
• ✔ Coordinate with finance teams – Sync up with finance so they account for credits in budgeting and use them in invoice payments.
• ✔ Maintain documentation – Document rewards earned and used, to report savings and troubleshoot any issues with Oracle if needed.

Table: Governance Framework

Establishing this governance framework is essentially about protecting your savings.

The Support Rewards program is generous, but it only helps if you actively redeem your rewards.

By tracking and managing the process, you ensure no rewards go unused and no savings opportunities are missed. It’s a bit of ongoing homework that pays off in real dollars saved. In the end, proper oversight ensures that Oracle’s promised support reduction actually shows up in your financial results.

5 Expert Takeaways

• Oracle Support Rewards can significantly reduce Oracle support bills through OCI usage, directly converting cloud spend into support savings.
• Credits accrue in proportion to eligible cloud consumption (generally 25% of OCI spend, or 33% for ULA customers), so the more you use OCI, the more you save on support.
• Most OCI services qualify for rewards, meaning typical compute, storage, database, and networking usage all count – it’s broad coverage of core cloud spend.
• These rewards effectively shift the total cost of ownership in favor of Oracle Cloud, making OCI more financially attractive when you consider the offset to support expenses.
• To maximize savings, organizations should plan and govern their OCI adoption with Support Rewards in mind: track usage, align with billing cycles, and ensure all earned credits are used.

Read about our Oracle Advisory Services

Do you want to know more about our Oracle Advisory Services?

Please enable JavaScript in your browser to complete this form.

Name *

First

Last

Email *

Company

Message *

Submit