Oracle Support Rewards is an incentive program offered by Oracle to customers who use Oracle OCI and have on-premise technology contracts under active support.
- If you have an active support contract for on-premise software licenses (technology)
- If you have an OCI contract (annual-flex)
- You can claim 25% of every dollar you spend on Oracle OCI after 12 months.
- It is important to note that you need to consume the OCI spend, and this is not an automatic process.
What Are Oracle Support Rewards?
Oracle Support Rewards is an incentive program launched by Oracle in 2021 to help customers reduce their on-premises Oracle support costs using Oracle Cloud Infrastructure (OCI).
In simple terms, for every dollar you spend on OCI services, you earn credits (Oracle Support Rewards) that can offset your Oracle software support bills. Oracle’s leadership introduced this program to encourage cloud adoption: as you migrate workloads to OCI, you “get paid back” through support cost reductions.
Why it matters:
Many enterprises pay hefty annual fees for Oracle Software Update License & Support (databases, middleware, etc.). Support Rewards allow those customers to reduce their support costs if they also invest in Oracle’s cloud.
This can translate into tangible savings in IT budgets. For example, if your company spends $100,000 on OCI this quarter, you could earn $25,000 credits to apply against your next Oracle support invoice.
Over a year, such savings add up and can even reduce certain support bills to $0 in the right scenarios.
(Real-world context: A global firm with a $1M yearly Oracle database support bill moved a few applications to OCI, spending about $2M on cloud services.
As a result, they earned roughly $500k in Support Rewards – effectively cutting that year’s Oracle support bill in half.
In another case, a company doubled its cloud spend to $4 million, earning about $1 million in rewards and fully eliminating its $1 million support fee for the year.
How Rewards Are Earned (Accrual Mechanics)
Oracle Support Rewards accrue at a fixed reward rate based on your OCI consumption.
For most customers, you earn 25% of each dollar spent on OCI as credit toward support fees. If your organization has an Unlimited License Agreement (ULA) for Oracle software, the reward rate is even higher – 33% of each OCI dollar.
In other words:
- Standard customers: Spend $1.00 on OCI, earn $0.25 in Support Rewards.
- ULA customers: Spend $1.00 on OCI, earn $0.33 in Support Rewards.
There is no complex tiering or tricky formula – it’s a straightforward rebate-like system. Oracle set a 33% higher rate to incentivize its ULA customers (who typically have large fixed support costs) to use OCI.
If you have any active ULA for Oracle technology, your entire OCI usage is charged at a 33% rate. (This is significant: even if not all your products are under the ULA, as long as you have one, Oracle will credit all OCI spend at the higher rate.)
What counts toward OCI spend?
Almost all OCI services qualify. Whether using core compute and storage, Oracle Autonomous Database, networking, analytics cloud services, or even an OCI Dedicated Region at your own data center, all those usage charges will accrue rewards.
It does not matter what workloads you run; you could be running an Oracle database, a third-party application, or a custom app on OCI – as long as you’re consuming eligible OCI services, you earn rewards.
Oracle intentionally made it broad: “Any workload on OCI can accrue rewards.”
This means you don’t have to run only Oracle software in the cloud to get the benefit; even moving non-Oracle workloads to OCI helps generate credits (which you can then use to pay Oracle support bills for the Oracle software you use elsewhere).
However, there are a few exclusions on OCI spending for accrual:
- Third-Party Marketplace offerings: OCI services that resell third-party solutions are not rewarded. For example, the Oracle Cloud VMware Solution (which bundles VMware licenses on OCI) or any application purchased through the Oracle Cloud Marketplace would be excluded. The rule of thumb is that if the service fee is largely passed through to a third party (such as VMware or Microsoft licensing for Windows), Oracle won’t count it for rewards.
- Oracle Cloud Apps (SaaS): Using Oracle’s SaaS application suites, such as Oracle Fusion Cloud ERP and HCM, does not accrue Support Rewards. Those are separate subscriptions, and Oracle offers other incentives for migrating from on-premises apps to cloud apps, such as the Customer 2 Cloud program, but they are outside the scope of this program.
- OCI Free or Trial usage: Naturally, any free credits, free tier usage, or promotional trial usage of OCI does not earn rewards. You only accrue rewards on paid consumption of OCI services.
- Base fees for Cloud@Customer: If you deploy Oracle Cloud@Customer (similar to a Dedicated Region in your data center), the metered usage charges for that environment accrue rewards (since they’re part of Universal Credits), but certain one-time or base infrastructure fees may not. (For instance, the base rack subscription for a Dedicated Region is not eligible, but the ongoing usage of that region’s resources is eligible.)
Oracle imposes no maximum cap on how much you can accrue. In a given month or year, the more you use OCI, the more credits pile up. Theoretically, you could earn millions in rewards if your cloud usage is high enough.
This is essentially Oracle’s saying: “We won’t limit your savings; if you migrate more, we reward more.” In practice, the limit is what you can practically use, which ties into your actual support costs and the 12-month expiration, covered later.
Accrual timing: Support Rewards are calculated monthly in arrears. At the end of each month, Oracle totals your eligible OCI spend and applies the 25% or 33% rate to determine the reward amount.
Those credits are then deposited into your Support Rewards account, which is visible in the OCI console. If you ramp up your OCI usage mid-year, you’ll start seeing rewards accrue by the end of that month.
Conversely, reducing OCI usage means you earn fewer new credits that month. There’s no averaging over a year – it’s based on actual usage month-to-month.
(Example scenario: Suppose your company spent $100,000 on OCI services in March.) By early April, Oracle will post $25,000 worth of Support Rewards to your account (assuming standard 25% rate). In April, you ramp up further and spend $200,000 on OCI – by May, you’ll get an additional $50,000 credit. You now have $75,000 in rewards accrued over those two months. You can keep accumulating like this until you can use them on a support bill.
You can monitor these accruals in real time – Oracle’s OCI Console has a “Support Rewards” dashboard under Billing, where you can see the balance of accrued rewards and expiration dates. This transparency helps your team track the amount of credit available at any given time.
Using and Redeeming Your Rewards
Earning rewards is only half the story; the value comes when you redeem those credits to reduce costs on your Oracle support invoices.
Here’s how redemption works and important rules to know:
- What support bills can be paid? Oracle Support Rewards can be applied only to invoices for Oracle Technology program support fees. This means the annual (or periodic) support renewal fees for Oracle database, Oracle middleware, and other core technology licenses you own. It includes Oracle Database, Oracle WebLogic, and the Oracle Middleware suite, among others. Essentially, it qualifies as an on-premises software product under the “Software Update License & Support” contract. It does not include support for Oracle applications (such as E-Business Suite, PeopleSoft, JD Edwards, etc.), and it also doesn’t cover support for Oracle hardware or appliances, or any cloud subscription fees. For example, you cannot use these credits to pay for an Oracle Fusion SaaS or an Oracle Linux support subscription – those are different models. (Oracle Linux support and Java SE subscriptions are explicitly ruled out because those subscriptions bundle license and support together.) The program intends to offset traditional license support bills for technology products.
- How to redeem: When you have an upcoming support invoice, you can use your accrued rewards as a payment method on that invoice. Oracle allows you to apply the credits to any eligible open support invoice. Typically, your organization’s Oracle support renewals come up annually. If you’ve accrued rewards, you would inform Oracle (or simply apply via the OCI console billing system) that you want to use $X of your rewards balance to pay (or partially pay) that invoice. The mechanics may involve your Oracle account manager or billing coordinator, but Oracle’s system will deduct the reward balance, rather than you having to pay that portion in cash. Important: you can’t use credits to cover taxes on the invoice – only the pre-tax support amount can be offset. So, you might still pay a small amount for out-of-pocket taxes if applicable, even if rewards fully cover the support fee.
- Timing matters: You can only use rewards you have already accrued when the invoice is due. You cannot delay paying a support invoice, hoping to earn more credits in the coming months to cover it. For example, suppose your support renewal is due in July, and you will only accrue significant rewards from July to the end of the year. In that case, you can’t postpone the July payment, so try to apply those later credits. Instead, you’d use whatever rewards you have up to that point for the July bill, and any new credits earned afterwards could go toward next year’s renewal. You should align your cloud usage and accrual plan ahead of your support billing cycle. Many firms plan cloud projects the year before a major support renewal, so that by the time the support fee is due, a healthy stack of credits is ready to help soften or eliminate that bill.
- Expiration of rewards: One of the most crucial points to manage – Support Rewards credits expire 12 months after they are earned. Each month’s credits have a “use by” date one year from now. For instance, rewards earned at the end of October 2024 will expire at the end of October 2025 if not used. Oracle will automatically apply the oldest credits first (first-in, first-out) when you redeem them, to help avoid expiration, but it’s ultimately up to the customer to keep track. There is no extension or reactivation for expired rewards – once a credit reaches its 12-month expiration, it is lost if unused. In practice, you can’t just hoard credits for many years to cover a huge future purchase – you need to use them within a year of earning them. The program is designed to encourage continuous cloud usage and regular application of the credits to support renewals.
- Actionable insight: Align your reward usage with your support renewal calendar. If your support renewals are annual, you’ll likely accrue credits throughout the year and apply as much as possible when the renewal invoice arrives. If you have multiple support renewal dates (for different products that renew at different times), you can use credits several times a year. The key is to plan so that no large block of credits expires unused. Many companies set internal reminders 2-3 months before each reward tranche expires, to ensure they either apply it to any outstanding eligible invoice or confirm none will be wasted.
- Using across the company: Oracle allows flexibility for large enterprises with multiple legal entities or divisions. If you have, for example, two subsidiaries, each with their support contracts, the parent company can pool and apply rewards to any eligible invoice within the corporate family. The OCI console allows an admin to authorize other entities within your company to use the rewards. This is helpful if, for example, one business unit drives most of the OCI usage (accumulating rewards). In contrast, another business unit has a big Oracle DB support bill – you can apply the first unit’s earned rewards to the second unit’s support invoice. The program’s terms typically tie the rewards to the “Sold To” party on the cloud order. Still, Oracle permits internal transfers as long as the entities are linked in your corporate hierarchy. From a SAM manager’s perspective, ensure you have internal agreements on allocating rewards if business units operate with separate budgets. You want to maximize the company-wide benefit.
- No cash value & other limitations: Support Rewards can’t be converted to any other currency or used. You either apply them to support invoices or they expire – you can’t, for instance, use them to buy new licenses or pay for cloud services, and Oracle won’t cut you a refund check if you somehow accrue more credits than you have support to spend on. They strictly offset support fees and nothing else.
(Real-world example: A retail company found themselves with more rewards than their current support bill because they aggressively moved workloads to OCI. They coordinated with Oracle to apply what they could to the present invoice and saved the remainder for the next cycle.
Since the credits would expire in 12 months, they timed their next support renewal (for another product) a bit earlier, within that window, to utilize the remaining credits. Internally, this required the SAM team to negotiate a one-month extension of the renewal date – a small but worthwhile adjustment to avoid losing credits. The lesson: stay proactive in managing and scheduling your support renewals and reward usage.)
Maximizing the Benefits (Strategies for Customers)
To get the most out of Oracle Support Rewards, organizations should approach it strategically.
Here are some actionable strategies and considerations:
- Identify Workloads Suitable for OCI: Review your IT portfolio for systems that can run on Oracle Cloud Infrastructure, especially those linked to your Oracle technology stack. Oracle databases, middleware-based applications, and high I/O workloads typically run well on OCI due to Oracle’s optimized infrastructure, such as Exadata Cloud Service for databases. By moving these, you can gain performance benefits and generate rewards to offset their support costs. Even non-Oracle workloads are candidates if OCI makes sense technically and financially. The key is to choose cloud migration projects that align with your IT roadmap – don’t migrate something solely for the reward credits if it doesn’t otherwise add value or if OCI isn’t a good fit for that system.
- Calculate Potential Savings Beforehand: Work with your licensing and finance team to estimate how much support savings you can achieve at various OCI spend levels. For example, if you currently pay $500,000/year in Oracle support, you know that every $1 of OCI yields $0.25 in credit. To offset the full $ 500,000, you must spend $2 million on OCI over the year (assuming a 25% rate). That might or might not be realistic. Perhaps you project $1 million of OCI usage for certain new projects – that would yield $ 250,000 in credits, cutting support costs by 50%. Laying out these scenarios helps justify cloud projects: the more you spend on OCI for genuine business needs, the more you save in support, effectively improving the ROI of moving to the cloud. Present these numbers to IT leadership and CFOs as part of the business case for migrating to OCI. This also ensures everyone has realistic expectations (e.g., you won’t eliminate a $10M support bill unless you plan a large OCI adoption).
- ULA Customers – Leverage the 33% Rate: If your company is under an Oracle Unlimited License Agreement, the higher accrual rate means OCI spending has an even bigger payoff. For instance, a ULA customer spending $3 million on OCI would earn roughly $1 million in rewards (33%), nearly enough to offset a $1 million support bill (just short by a small amount). If you’re nearing the end of a ULA period and considering certifying or renewing it, factor in Support Rewards: moving workloads to OCI while under the ULA not only helps utilize those “unlimited” licenses in the cloud, but also dramatically cuts the support costs you’ll continue to pay. ULA situations can be complex, so involve your license experts. However, Oracle essentially gives ULA holders a strong nudge to use OCI. Many ULA customers use this to reduce the total cost of ownership of their Oracle investments by shifting some capacity to OCI and reaping the 33% reward.
- Combine BYOL and Rewards for Maximum Benefit: Most OCI services allow you to Bring Your Own License (BYOL), meaning you use your existing Oracle software licenses on the cloud and pay a lower rate for the cloud service. BYOL can save you money on cloud subscription costs since you’re not paying Oracle again for a license you already own. The good news is that BYOL usage on OCI still earns Support Rewards (as confirmed by Oracle’s program FAQ). So, a savvy strategy is using BYOL to save on cloud costs and still accumulate rewards on that cloud spend to save on support costs. You’re double-dipping legitimately. For example, if you deploy an Oracle Database on OCI via BYOL, you avoid new license fees in the cloud, yet the compute and storage you pay for generate rewards. This approach requires you to maintain your licenses with active support, which you likely do if you’re concerned about support costs.
- Plan Cloud Spend to Align with Support Cycles: Schedule OCI projects in sync with your support billing calendar to avoid losing credits to expiration. If your big support renewal is every December, ramp up OCI usage earlier in the year so that you have plenty of credits by December. If you plan a major OCI deployment right after your support renewal has been paid, you’ll accrue many credits that might sit unused for many months and risk expiring before the next cycle. It might even be worth discussing the alignment of billing cycles with Oracle. Oracle is generally not going to change your support renewal dates frequently. Still, there might be some flexibility, as in the real-world example where a renewal was pulled in slightly earlier. At a minimum, ensure internal budgeting accounts for using the credits within one year.
- Monitor and Adjust: Treat Support Rewards as an asset that needs management. Assign someone, such as a SAM manager or financial analyst, to monitor the OCI reward balance monthly. Oracle’s tooling will show accruals and expirations; use that to forecast how much will be available at each upcoming renewal. If you see that you’re on track to have more credits than needed for the next support payment, you might decide to slow down paid OCI usage if it’s purely driven by this incentive (not common, but in case you’re over-provisioning). Conversely, if you want to maximize offset, you might accelerate some cloud usage or expansion if feasible. The idea is to continuously align your cloud consumption to reduce support costs without overshooting. Regular reviews, such as quarterly, of cloud spend versus support rewards earned should be part of your IT finance governance.
- Beware of Overspending for the Sake of Rewards: While Support Rewards are attractive, remember that spending $4 to save $1 (in the case of a 25% rate) only makes sense if that $4 of cloud spend is providing real value to your business. Do not let the tail wag the dog – the primary reason to use OCI should be that it meets your technical and business requirements. The support savings are a bonus that improves the financial equation. It might be tempting for some organizations to consider moving marginal workloads or keeping instances running on OCI just to accrue credits. Always weigh the actual cloud costs against the benefits. For example, if an OCI service would cost you more than an alternative cloud or on-premises solution by $ 100,000, getting $ 25,000 back in support credit still means you’re out $ 75,000 net. However, if OCI is cost-competitive (or better) for the workload, the $ 25,000 reward truly reduces your overall costs. In short, using Support Rewards as a sweetener for OCI adoption is not the sole reason.
- Internal Communication and Buy-In: Ensure your finance department and procurement team understand the program. It’s relatively new and unique to Oracle. When they see a support invoice “paid” by cloud credits, they should know what that is. Similarly, if different teams handle cloud spending versus license support, bring them together to plan how the cloud budget can reduce the support budget. Some organizations create an internal charging mechanism; for instance, the team running OCI gets “credit” in their budget for the support savings they generate, which encourages collaboration. No matter how you do it, treat Oracle as a single vendor across cloud and on-prem in this context, and aim to optimize the total relationship cost. Oracle designed these rewards to increase loyalty to OCI; as a customer, you can take advantage of that to lower your net spend with Oracle, but it requires breaking down silos between cloud ops and license management internally.
Potential Pitfalls and Cautions
While Oracle Support Rewards can yield significant benefits, be aware of a few pitfalls so you can avoid any unwelcome surprises:
- Expiry Risk: The 12-month expiration is why customers might miss the full value. It’s easy to get caught up in cloud migration and forget to apply credits in time. Oracle will not remind you individually when credits are nearing expiration. They consider it the customer’s responsibility to manage. Mitigation: As mentioned, assign owners to track this and set up alerts. Treat expiring credits like expiring budgets – use them or lose them.
- Not Applicable to All Spend/All Support: Double-check your Oracle support portfolio. If most of your Oracle spend is on things like Oracle E-Business Suite support, note that this program won’t reduce those costs (since application support is excluded). Support Rewards might have limited impact if you’re primarily an Oracle applications customer (with relatively little database or middleware licensing). Conversely, that’s the sweet spot if you mainly pay for database and middleware support. Also, if you use Oracle Linux or Java SE subscriptions, note that these fees cannot be offset. In short, ensure you have eligible support expenses (Oracle tech licenses) to offset, and plan your OCI usage accordingly. Otherwise, you might accrue credits that you find you cannot use.
- Contractual Commitment: Remember that you likely signed up for a Universal Credits cloud contract to get the rewards. That might have a certain spending commitment or at least an expectation of ongoing usage. Failing to meet those could have other implications, such as not getting discounts or, if you had a committed spend, potentially wasting your budget. Make sure the cloud commitment you make aligns with your IT plans. The Support Rewards do not require a minimum cloud spend – no limit or minimum is imposed to earn credits. However, large enterprises often negotiate a volume discount in OCI by committing to spend a certain amount over a specified term. Don’t over-commit just because of support savings; forecast realistically.
- Oracle Ecosystem Lock-In: It’s worth noting the bigger picture: Oracle offers these rewards to keep you within their ecosystem (on-prem software + Oracle Cloud). This isn’t necessarily bad – if Oracle’s solutions work well for you, it can create a virtuous cycle of cost savings. But be mindful of your overall cloud strategy. If multi-cloud or best-of-breed is important to your organization, weigh the value of Support Rewards against any benefits you’d get from running certain workloads on other clouds. For example, you may use OCI for Oracle databases to gain rewards and technical synergy, but still use AWS or Azure for other services where they excel. That can be a sensible balance. Avoid getting so caught up in chasing Oracle credits that you neglect a better solution elsewhere. Keep technical and business requirements first; use the financial perk to tip close decisions in OCI’s favor, not to override well-founded architecture choices.
- Operational Considerations: You might have to coordinate with Oracle’s billing support when redeeming rewards. Ensure you understand the process well. Oracle has guides and even videos on redeeming via the OCI console. It’s usually straightforward, but make sure your accounts payable team doesn’t accidentally pay an invoice in full if you intended to use credits – communicate internally when you plan to use rewards for a given invoice. Hence, the payment process accounts for it. Also, partial payments with rewards are possible. If you don’t have enough credits to cover the whole bill, you can apply what you have and pay the remainder. Align this with your budgeting – for example, if you expected a $ 200,000 support invoice but have $ 150,000 in rewards, you’ll only need $ 50,000 in cash this time; account for that difference.
- Staying Informed: Oracle may update programs and policies. So far, Support Rewards has been consistent since launch, but always review your contract terms and Oracle’s official FAQ for any changes. For example, if Oracle were to adjust the accrual rates or extend the program to new services, those are things to note. The contractual guarantee typically ensures that your terms (such as the 25%/33% rate) won’t change during your cloud contract period. If you renew your cloud contract, double-check if any terms have changed. Being on top of Oracle’s announcements (or working with an Oracle licensing advisor) will ensure you continue to maximize benefits.
Recommendations
In summary, here are practical recommendations for SAM managers, licensing professionals, and IT leaders to make the most of Oracle Support Rewards:
- Enroll Proactively: If you have significant Oracle support costs, consider discussing Support Rewards with Oracle when starting or renewing an OCI contract. Ensure the program is included in your cloud agreement so you don’t miss out.
- Map Out Workloads: Identify which projects or systems you can move to OCI in the next 12-24 months. Prioritize those aligning with Oracle’s strengths (e.g., databases, Oracle apps) to maximize technical benefits and reward accrual.
- Estimate and Track Savings: Calculate potential support savings from anticipated OCI usage. Use Oracle’s 25% (or 33%) rate to forecast credits and incorporate those savings into your IT budget plans. Monitor the OCI Console monthly to track accrued rewards and adjust your plans if needed.
- Align with Renewal Dates: Time your reward redemption to coincide with when support invoices are due. Set internal reminders well ahead of support renewal deadlines and reward expiration dates. This ensures you apply credits optimally and avoid expiration.
- Communicate Internally: Educate finance and relevant IT teams about how Support Rewards work. When using credits to pay an invoice, coordinate with your accounting department so they apply the credit correctly. Make the rewards part of your overall Oracle vendor management strategy.
- Use Holistically, not in Isolation: Include support rewards in cloud vs. on-premises cost comparisons. However, don’t base decisions solely on the reward—ensure OCI meets your needs on technical merits and total cost. Use the rewards as a bonus to inform tipping decisions while also considering architecture and vendor risk.
- Review and Revise: Periodically review your experience with the program. Are you realizing the expected savings? Are any credits at risk of expiring? Adjust your cloud usage or support contract accordingly. For example, if you consistently have leftover credits, you might consolidate some support contracts or plan additional OCI usage to utilize them, or vice versa.
By taking these steps, organizations can wisely leverage Oracle Support Rewards to save money on support, while advancing their cloud adoption in a balanced way.
This program can significantly improve the economics of running Oracle software for those invested in OCI, but it works best when approached with careful planning and oversight.
Ultimately, the goal is to transform what was once considered rigid support fees into opportunities for reinvesting in modern cloud infrastructure without increasing overall costs.
Eligibility and Enrollment
Not every Oracle customer automatically gets to use Support Rewards – you need to meet certain conditions and actively enroll.
Key points on eligibility include:
Compatibility with Other Oracle Programs: Oracle Support Rewards is meant to complement other Oracle programs rather than replace them.
For example, if you have a Bring Your Own License (BYOL) arrangement to use your existing licenses on OCI, you can still earn Support Rewards based on your cloud usage.
It’s also available alongside Oracle’s standard volume discounts on cloud or programs like Oracle’s “Customer 2 Cloud” (which helps convert on-prem application support into cloud subscriptions for Oracle’s SaaS apps).
However, note for Unlimited License Agreement (ULA) customers: If your Oracle ULA included a special clause called “ULA2PaaS” (an option that allowed using your ULA licenses on Oracle Cloud with no new license cost), you cannot use both that and Support Rewards simultaneously.
In such cases, you’d need to amend the ULA to drop the ULA2PaaS option to enroll in Support Rewards. This mainly affects a subset of ULA customers. Your licensing team should review the ULA contract details with Oracle to make the right choice.
Oracle Support Customer:
You must have existing Oracle on-premises software with an active support contract. The program is aimed at organizations paying for Oracle technology support (e.g., databases and middleware). If you don’t pay for Oracle support (for instance, if you use a third-party support provider or only use Oracle SaaS products), this program won’t apply.
OCI Universal Credits Contract:
You become eligible once you sign or renew an OCI Universal Credits order and start consuming OCI services under that agreement. This means working with Oracle (or a partner) to establish a Universal Cloud Credits contract – even if it’s a flexible “pay-as-you-go” style agreement.
Importantly, simply having an OCI account and using some services on a credit card (the classic pay-as-you-go, no-contract option) is not enough to qualify. Oracle currently requires a formal enrollment in Universal Credit to activate Support Rewards. So, if you’re planning to leverage this benefit, involve your Oracle representative to ensure the proper contract terms are in place.
Geography and Sector:
The program is available to commercial customers globally (in all Oracle Cloud regions) except in a few cases, like mainland China or the U.S. federal public sector, where different rules or restrictions apply. Most typical enterprise customers worldwide can participate without issue.
Enrollment Process:
Enrolling in Support Rewards is straightforward once you’re eligible. You usually request that your Oracle cloud sales rep include Support Rewards terms in your OCI contract. This often means signing an addendum or an ordering document that spells out your participation in the program.
Once that’s done, the program is tied to your cloud tenancy for the duration of your contract, unless you opt out. All future OCI usage under that tenancy will then automatically start accruing rewards. (Practical tip: If negotiating a new OCI agreement or renewal, explicitly ask about adding Oracle Support Rewards. Don’t assume it’s automatic – make sure the contract mentions it so you don’t leave money on the table.)
Read more about our Oracle License Management Services.
