By Franck Pachot
You want the amazing features of Oracle SQL and PL/SQL with minimal cost. Your database is too large for Oracle XE edition, but not big enough to require the cost of Enterprise Edition. You accept to do things manually, have maintenance windows. You are ok with a RTO of 5 minutes (time to switchover with Dbvisit standby), RPO of 10 minutes (archive_lag_target=600). Your servers have no more than 2 sockets.
So you opted for Standard Edition One.
But now, you have heard that Standard Edition One is stopped. What are your alternatives?
This information comes from what we can find in oracle.com documents about Standard Edition Two.
Big thanks to Dominic Giles, Mike Dietrich, Tammy Bednar that helped a lot to understand the rules and how to apply them on real customer situations.
Standard Edition Two
If you want to upgrade to 184.108.40.206 (12c patchet 1) then you have to go to Standard Edition Two.
From the price list, the SE2 costs x3 the price of SE1:
Upgrade from Standard Edition One
The price list shows the public price when you buy Standard Edition Two.
However, from Oracle Brief DB SE2 you don’t have to pay the difference when going from SE1 to SE2:
It’s clear: if you are in SE1, it’s free to go to SE2 and the maintenance annual cost is only 20% higher.
So, if you are in SE1 the annual cost increases by 20% and:
- you can upgrade to latest versions with full support
- you can put your database in HA with RAC if you want to
- each database load can have up to 16 sessions running concurrently in CPU
- you can still have older versions if you need to, without this new limitation
It’s always difficult to accept changes that are imposed, but when you think that you have bought SE1 at a price that has been set at a time where sockets had 4 cores, then it is easier to accept the new limitations. They make the Standard Edition model sustainable after all.
A lot of customers I know have bought SE1 because they we consolidating their IT on VMWare. Enterprise Edition was a no-go because of the cost to licence all the cores of all servers. And having a dedicated ESX for oracle database is the opposite of consolidation if you have only few databases.
But the price of SE1 is still acceptable when you licence all sockets. And, as long as each server has no more than 2 sockets, SE1 was possible there. Don’t worry, it’s the same rule for SE2. The 2 socket limit is per server.
Yes. Now you can have RAC in SE2 which was not possible in SE1. This brings service high availability to your database: two instances are running on two nodes. One can fail and the service is still there on the other node with access to all data.
But if you have two sockets in your server, you can’t run another instance on another node because of the two sockets limitations. In RAC, SE2 is limited to 2 mono-socket nodes. Here is what you can do:
- You can change hardware to mono-socket servers
- You can remove one processor (physically – not BIOS disabled). The 2 sockets limitation is only for occupied sockets.
- You can virtualize with OVM to use only one socket for oracle. The other one can be used for your application server.
Don’t forget, the goal is to have at least 8 cores to run the 8 user sessions. More cores (or hyper-threading) will keep-up with background processes, OEM agents, etc. Having two 1s8c16t (1 socket 8 cores 16 threads) servers is a good minimal configuration to use the full power of SE2 RAC.
Note that if you are on VMWare with 2-socket servers, then you can’t use RAC in SE2. RAC in SE2 is limited to one socket per server.
Note that RAC is only for service protection. Data protection is achieved with a standby database. There is no Data Guard in Standard Edition, but there are smart alternatives such as Dbvisit Standby
Less good news for customers that bought the minimum NUP which was 5 in SE1 independently of the number of servers. When you go to SE2 you have a limit of 10 NUP, and it’s per server. It can make a difference if you are on VMWare as you have to count all servers.
The cost for extended support is additional 20% after 7 years of initial release. 11gR2 was released on Sept. 2009 which means that the extended support for 220.127.116.11 will be 20% in Sept. 2016 – the same price as the SE2 support.
Conclusion: better to go to SE2 before Sept. 2016 than keep SE1. You have same support for 18.104.22.168 databases and in addition to that you will be able to install and upgrade to latest release. We expect 12.2 to be available in Sept. 2016.
Added Oct. 16th, 2015:
Today Oracle announced that the waived support has been extended to May 2017.
See more info in a new blog post
Did you already upgrade to 12c? Then you are in 22.214.171.124 which is the latest available for SE1.
It’s different case than 126.96.36.199 because there will be no extended support for it. In September 2016, you will have no PSU anymore. You can stay with sustaining support at no additional cost. But if you want more support you can downgrade to 188.8.131.52 and pay extended support, or upgrade to SE2 and upgrade to 184.108.40.206 or 12.2 if it is available at that time. Of course, as we have seen previously, there is no point to stay in SE1 and pay the additional 20% because it’s the same cost to go to SE2.
Conclusion: If you are in 12c SE1, stay in sustaining support (no PSU) or pay additional 20% to get full support and features of new versions through SE2.
If you look at it, except if you don’t want support, you should upgrade to SE2 in 2016.
Think positive: you can run oracle with all SE features on 16 cores dedicated to your users with a reasonable cost, even on VMware. And you can also think to get HA with RAC if you are on physical servers (1 socket) or virtualized with OVM. That was probably unexpected if you bought SE1 several years ago.
SE features are all oracle features that can be seen from application development point of view. EE has lot of features for administration, protection, performance, etc. But the lower cost of SE leaves time and money to find workarounds if you want to do it yourself. SE is a very good product affordable for small companies.
An additional remark. If you plan to buy Standard Edition before the end of the year, then it seems that you have the following choices (prices from public price list) :
- Buy SE2 at 17500$ per socket and support for 3500$ per year
- Buy SE1 at 5800$ per socket and upgrade to SE2 – support will be 1392$ per year then
Of course, the second solution seems to be the more attractive one, but don’t wait: SE1 will not be available anymore in December 2015.
SQL> select date'2015-12-01' - sysdate "SE1 COUNTDOWN (days)" from dual;
SE1 COUNTDOWN (days)