Oracle Standard Edition RAC Licensing
- Major Change in Oracle 19c: Starting with Oracle version 19c, Oracle Standard Edition 2 (SE2) will no longer support Real Application Cluster (RAC).
- History and Changes in SE2: In December 2015, SE2 replaced the previous Standard Edition (SE) and Standard Edition One (SE1) releases. SE2 introduced limitations on the total number of CPU sockets and the maximum number of 16 CPU threads per database instance.
- Options for Companies: If an upgrade is imminent, companies using RAC today must evaluate their requirements and decide whether to switch to Oracle Enterprise Edition (EE) with the RAC option or to the public cloud.
Oracle Standard Edition RAC Licensing
The Introduction of SE2
In December 2015, Oracle introduced Standard Edition 2 (SE2), replacing the earlier versions of Standard Edition (SE) and Standard Edition One (SE1).
This transition was necessary for users running versions pre-12.1.0.2 to upgrade to SE2. The introduction of SE2 brought several changes and requirements that significantly impacted users of the earlier editions.
Mandatory Transition: Users of SE and SE1 were required to upgrade to SE2. This transition was not optional, as support for the older versions was phased out.
Support Fee Changes: One of the significant alterations introduced with SE2 was the change in support fees. This change was particularly impactful for SE1 customers, who saw a notable increase in support costs.
Significant Changes from SE to SE2
The transition from SE and SE1 to SE2 brought about several important changes, particularly regarding CPU socket and thread limitations and the implications for Real Application Clusters (RAC).
CPU Sockets and Threads Limitation
- CPU Sockets: SE2 introduced a new limitation on the number of CPU sockets. Under SE2, databases can have a maximum of two CPU sockets, a reduction from SE’s allowance of four and SE1’s allowance of two.
- CPU Threads: SE2 also capped the number of CPU threads per database instance at 16. This was a significant change from the previous editions, which did not impose a cap on CPU threads.
These limitations mean that organizations running SE2 must carefully consider their hardware configurations to comply with licensing terms.
Implications for RAC (Real Application Clusters)
- RAC Configuration: SE2 imposed restrictions on RAC configurations. Under SE2, RAC is limited to one CPU socket per server, and each database instance can only utilize up to 8 CPU threads. This is a considerable reduction compared to the previous configurations allowed under SE.
- Performance Impact: These limitations on CPU sockets and threads in RAC configurations may impact performance, particularly for organizations that rely heavily on RAC for high availability and load balancing.
Key Points to Consider
- Upgrade Requirements: To stay compliant and supported, all Oracle Database installations running versions pre-12.1.0.2 must be upgraded to SE2.
- Hardware Assessment: Organizations must assess their hardware configurations to meet the new SE2 CPU sockets and thread limitations.
- Budget for Increased Costs: Be prepared for increased support fees, particularly if transitioning from SE1 to SE2.
- Performance Planning: Plan for potential performance impacts due to CPU sockets and thread limitations, especially in RAC environments.
Understanding these changes and planning accordingly can help organizations manage the transition to SE2 smoothly, ensuring compliance with Oracle’s licensing requirements while optimizing their database performance and costs.
Oracle DB SE 19c and Future Versions
End of RAC in SE2
Discontinuation of RAC: Starting with Oracle Database version 19c, Real Application Clusters (RAC) are no longer permitted under Standard Edition 2 (SE2). This change is explicitly outlined in the “Database Licensing Information User Manual.”
Impact on Upgrades: Organizations planning to upgrade to version 19c or later must evaluate their reliance on RAC. Removing RAC from SE2 affects how businesses manage high availability and load balancing, making it crucial to reassess database strategies.
Importance of Evaluating RAC Usage
Assessing Business Requirements: Organizations need to carefully evaluate their current use of RAC, considering key business requirements such as:
- Zero Downtime: Ensuring continuous availability without interruptions.
- Online Patching: Applying updates and patches without taking the system offline.
- Load Balancing: Distributing workloads evenly across servers to optimize performance.
A thorough evaluation helps determine the best action and avoid disruptions during the transition.
Options Post-19c Release
Switching to Oracle Enterprise Edition (EE) with RAC
- Transition Considerations: Organizations heavily relying on RAC may need to move to Oracle Enterprise Edition (EE) with RAC. This transition involves understanding EE and RAC’s licensing requirements and costs.
- Consulting Experts: Engaging experts like Redress Compliance can provide valuable guidance on:
- The number of EE and RAC licenses needed.
- The most suitable licensing metrics for your organization.
- Upgrading existing SE, SE1, or SE2 licenses to EE, ensuring a smooth transition.
Adoption of Public Cloud Solutions
- Cloud Support for RAC: Public cloud solutions continue to support RAC, allowing organizations to maintain high availability and load balancing in a cloud environment.
- Licensing Requirements: When moving to the cloud, obtain all necessary licenses. This includes understanding the specific licensing terms and compliance requirements for cloud deployments.
- Benefits of Cloud Adoption:
- Cost Management: Spread costs over time and pay based on actual system usage duration.
- Flexibility: Scale resources up or down based on demand, optimizing cost and performance.
- Consulting Specialists: Working with certified Oracle licensing specialists can facilitate the transition to the cloud, ensure compliance, and maximize the benefits of cloud adoption.
Key Points to Consider
- Evaluate RAC Usage: Assess the current reliance on RAC and determine if upgrading to EE or adopting cloud solutions is necessary.
- Consult Experts: Seek advice from Oracle licensing experts to navigate the transition smoothly and ensure compliance.
- Plan for Costs: Understand the cost implications of moving to EE with RAC or adopting cloud solutions, including licensing and operational expenses.
- Optimize Performance: Ensure the chosen solution meets your organization’s performance and availability requirements.
By understanding these options and planning accordingly, organizations can effectively manage the transition from SE2 to Oracle Database 19c and future versions, maintaining compliance and optimizing their database infrastructure.
FAQs
What is Oracle Standard Edition 2 (SE2)?
Oracle Standard Edition 2 (SE2) is a version of Oracle Database introduced in December 2015. It replaces the previous Standard Edition (SE) and Standard Edition One (SE1).
What major change occurred in Oracle version 19c regarding SE2?
Starting with Oracle version 19c, using Real Application Clusters (RAC) is no longer permitted under SE2. This change is detailed in the “Database Licensing Information User Manual.”
Why was SE2 introduced?
SE2 was introduced to provide a more consistent licensing model and phase-out support for older versions, such as SE and SE1, which ran before 12.1.0.2.
What were the significant changes from SE to SE2?
SE2 introduced limitations on CPU sockets and threads, limiting the number of CPU sockets to two and the number of CPU threads to 16 per database instance.
How did the transition to SE2 affect RAC configurations?
In SE2, RAC configurations are limited to one CPU socket per server and only 8 CPU threads per database instance, significantly reducing the capacity compared to previous editions.
What should organizations consider regarding their current use of RAC?
Organizations should evaluate their reliance on RAC, considering factors such as zero downtime, online patching, and load balancing to determine the best strategy for future upgrades.
What options are available post-19c release for organizations using RAC?
Organizations can switch to Oracle Enterprise Edition (EE) with RAC or adopt public cloud solutions that support RAC, ensuring they obtain all necessary licenses.
What are the implications of switching to Oracle Enterprise Edition (EE) with RAC?
Switching to EE with RAC involves understanding the licensing requirements and costs and potentially consulting experts to determine the number of EE and RAC licenses needed and the best licensing metrics.
How can public cloud solutions benefit organizations using RAC?
Public cloud solutions support RAC, offering benefits like cost management through spreading costs over time and flexibility in scaling resources based on demand.
What are the cost implications of moving to EE with RAC or adopting cloud solutions?
Organizations need to plan for the increased costs associated with EE and RAC licenses or the operational expenses of cloud solutions, including understanding specific licensing terms.
How does SE2’s CPU socket and thread limitation impact performance?
The limitations may impact performance, particularly for organizations that rely heavily on RAC for high availability and load balancing. Therefore, careful performance planning is required.
What steps should organizations take to ensure compliance when upgrading to SE2?
Organizations should ensure all Oracle Database installations are upgraded to SE2, assess current hardware configurations, and budget for increased support fees.
