Consequences of stopping Oracle support

Job Oprel 10
0 0
Read Time:4 Minute, 24 Second

When buying licenses for Oracle, the first year support is mostly part of the deal. After that, a Customer may decide to stop paying for the yearly technical support of the Oracle licenses. The consequences of that decision is not always clear to customers. Most OLSA’s will contain the sentence   “If you decide not to purchase technical support, you may not update any unsupported program licenses with new versions of the program.”

This is correct, but there is more to think of.  This post will cover the elements that should be considered when deciding on stopping the support.

Unsupported actions

The Technical Support Policy of Oracle clarifies a bit more of what actions a customer is not entitled to do when stopping the support:

Customers with unsupported programs are not entitled to download, receive, or apply updates, maintenance  releases, patches, telephone assistance, or any other technical support services for unsupported programs.

This means the software instantly become legacy, AND a substantial risk. The Oracle software will not be upgraded or patched, the environment  (O.S., client software, middleware, other connected software) does. With the possible effect the application might not work in the future.


However Oracle claims that the departments Support, Accountmanagement and LMS acts more or less seperated and will not share this kind of information, it is naive to assume that the decision of stopping support of (part of) the Oracle licenses has no consequences regarding the rank of the customer on LMS’s list for submitting an audit.


Matching Service Levels

The support of the license to be stopped could be part of a socalled ‘subset’. Then the following rule applies according to the Support Policy:

You may desupport a subset of licenses in a license set only if you agree to terminate that subset of licenses.

The definition of a license subset is quite a definition, but here are two examples:

Oracle Database Enterprise Edition with RAC, Diagnostic and Tuning Pack.

Weblogic Suite with SOA Suite

So stopping support of the options is a ‘Matching Service Level’ – thing, what LMS will translate as incompliancy, and the chance that My Oracle Support is not willing to help when submitting a Service Request.


Afbeeldingsresultaat voor oracle reinstatement fee


Support of Oracle software is related to CSI-numbers, and there may be several CSI-numbers in one contract. And a customer may have more contracts, all with ther own negotiated discounts. The following line in the Support Policy is important when stopping support of a line-item :

Pricing for support is based upon the level of support and the volume of licenses for which support is ordered. In the event that a subset of licenses on a single order is terminated or if the level of support is reduced, support for the remaining licenses on that license order will be priced at Oracle’s list price for support in effect at the time of termination or reduction minus the applicable standard discount.

This is ‘Repricing’, also called ‘Pricing following Reduction ‘. So, the updated support renewal, then, would be recalculated at a less optimal discount. Ending up being no savings – just less product on support for the same costs.

This is mostly the case of terminating a license and not for terminating support (however this is a ‘reduced level of support’), but it’s important to know.

Terminating a license within a CSI-number – in stead of stopping support – is in some cases by the way not a reason for repricing. E.g. when there has been a reorganisation of contracts in the past.


When a customer decides – for what reason – to reinstate the support, there will be a reinstatement-fee.

The reinstatement fee is computed as follows:

a) if technical support lapsed, then the reinstatement fee is 150% of the last annual technical support fee you paid for the relevant program;

b) if you never acquired technical support for the relevant programs, then the reinstatement fee is 150% of the net technical support fee that would have been charged

Engineered Systems

Stopping support of a productline also has a peculiar effect on products, running on engineered systems.

The lifecycle managment of engineered systems are maintained by so-called  ‘bundle-patches’. These bundle-patches contains patches of storage-firmware, bios-updates, o.s-updates, and .. Oracle software patches.

So, when stopping Oracle support you still receive the database and middleware-patches through the bundle-patches, which is not allowed. And however it could be possible to not use these patches, it will break the life cycle managment of the engineered system. I don’t think this is advisable.


The prerequisites of making such a decision:

  • An overview of all the Oracle contracts at your firm, what seems pretty obvious, but takes quite an effort sometimes.
  • An overview of what licences you are actually using, compared to what you are entitled to.


The OPEX (Operational of Operating Expenditures) can be decreased, in some cases substantially, but before jumping into action and conclusions, contact someone who understands the risks, and is able to look further ahead in the future, together with you.


Example OLSA:

Oracle Software Technical Support Policies :

About Post Author

Job Oprel

Until February 2019, Job worked as a solution architect at AMIS Services with a special interest in Oracle licensing, High Availability architectures and managing complex (Oracle) environments, which includes Cloud environments.With a background as Oracle developer, DBA, team-manager and license-consultant he is able to utilize the Oracle technologies to a cost-efficient architecture for his customers.He is regularly involved in consultancy regarding: - Unlimited License Agreements (ULA). - License compliancy-checks and advice regarding optimizing the environment. - Second opinions. - Education / presentations about licensing and managing your infrastructure in the most cost-efficient manner.Twitter: @jobaclenl
0 %
0 %
0 %
0 %
0 %
0 %

Average Rating

5 Star
4 Star
3 Star
2 Star
1 Star

10 thoughts on “Consequences of stopping Oracle support

  1. HI we have taken licences for incremental increase and added few other new products. Let us say we have 5 ordering documents. One of the document we would like to stop renewing as the products are covered in other documents. We are on 12.1.3 version. If I stop renewing the document do we have any support issues or any?

    I appreciate helping this forum.


  2. Hi Job

    Firts of all Thanks for the valuable article , I have below qustions and appreciate your suggestions

    1. I want to stop any kind of Application Support with Oracle like EBS, Oracle Retail, Siebel e.t.c
    2. We do not have any plans of upgrade
    3. If there is any issues , We will fix ourself or hire any vendor to do it
    4. Can we get all Source code from Oracle , like we have for some applications but not for all

    We need to get rid of this additional expence as we are not using their support


    1. Hi, I’ve got no experience in stopping Application support of EBS, Siebel etc., but it should work the same. Take care that you continue to be the owner of the licenses when stopping support. Check if your contract points out something different. Oracle is not likely to hand-over their source-code, I think this will not happen. Regardz

  3. a quick question, after ending support, can I still log on to and have access to anything that is available prior to termination of support?

    1. Good question, but I haven’t experienced it yet. According to the support policy only states ‘you are not entitled to… etc’.
      When you are in the posession of 1 CSI which is out of support, you will likely receive the message ‘Error: Your access to My Oracle Support is restricted because you currently do not have any active SI in your profile’. So it’s a no unfortunately, but not 100% sure. When in posession of multiple CSI’s and anly one is active, you have access to anything in My Oracle Support.

  4. Hi,
    I was still confused by some information. I appreciate if you can help with that.

    Let’s assume that I have some licenses of type Enterprise Edition with partition, RAC, Diagnostic/tuning pack enable but all of type PERPETUAL (Licenses and options) and I resolve not to pay more for the support and annual update.

    Can I continue to use licenses without problems because they are “perpetual” type? (Yes, I know I could not open SR, update the products and etc). Let’s say the environment will only be for legacy / historical access.

    Thank you

    1. Hello,

      When you decide not to pay support anymore, you are still the owner of the licenses, but you can’t indeed use support, upgrade etc. Just don’t sign any agreement where you waive your license-rights (sometimes Oracle tries to persuade you to do this). En elegant way is to get in contact with the Oracle representative to get this done. Regardz.

    1. Laurent, thank you for your comment. I don’t know what link you are referring to, but I think you are right. In any case for the perpetual licenses. Corrected this in the blogpost. In rare cases there could be indeed a license buy without buying support, but then the rest of the blogpost applies :-).

Comments are closed.

Next Post

Oracle SOA Suite: Two-way SSL with TLS1.2 made easy (slightly less complicated)

Transport layer security (TLS) is not an easy topic. Many blogs have been written about this already. Surprisingly though, I did not find a single blog which was more or less complete and provided me with everything I needed to know to get this working on SOA Suite 12.2.1. In […]
%d bloggers like this: