Oracle Exadata Database Service offers flexible billing and licensing models designed to meet diverse organizational needs. Understanding these options is crucial for optimizing costs while ensuring compliance and performance for your database workloads.

Cost-Effective Software Licensing Models

Oracle provides two primary licensing approaches for Exadata Database Service, each tailored to different organizational scenarios and usage patterns.

License Included Pricing

A license-included consumption model includes Oracle Database Enterprise Edition plus all advanced database options and management packs. This model is ideal for:

Organizations with new workloads requiring immediate database capabilities
Dynamic utilization patterns where database usage varies significantly
Simplified procurement without complex license management
Rapid deployment scenarios where time-to-market is critical

Key benefits of License Included pricing:

All-inclusive pricing with no separate license costs
Access to all Oracle Database features including Advanced Security, Partitioning, and Management Packs
Simplified billing with single line-item charges
No license compliance concerns as everything is handled by Oracle

Bring Your Own License (BYOL)

Oracle BYOL is short for "Bring your own license". It allows you to bring your own license to any public cloud platform. This model offers significant cost advantages for qualifying organizations.

BYOL is ideal for:

Organizations migrating existing workloads with consistent usage patterns
Enterprises with existing Oracle license investments
Predictable workloads where usage patterns are well-established
Cost optimization scenarios where license portability provides savings

Cost Comparison: In Autonomous Database scenarios, Oracle notes that BYOL can lower the database compute costs by around 76%. Similarly, on Exadata Cloud@Customer, the Oracle Database software portion costs about $0.336 per CPU hour with License Included vs $0.0807 with BYOL.

Elastic OCPU Scaling and Pay-As-You-Use

One of the most compelling aspects of Exadata Database Service is its elastic OCPU scaling model where you pay for what you use. This approach offers several advantages:

Flexible Resource Allocation

Scale OCPUs up or down based on actual demand
No upfront capacity planning required
Automatic scaling capabilities for dynamic workloads
Real-time resource adjustments without service interruption

Cost Optimization

Pay only for consumed compute resources
No charges for unused capacity
Predictable pricing model based on actual usage
Optimal cost-performance ratio for variable workloads

Integrated Security Framework

Exadata Database Service provides comprehensive security from data to identity, implementing multiple layers of protection:

Operator Access Control

The service includes robust operator access control to prevent, detect, and respond to security threats:

Prevention: Multi-factor authentication, role-based access control, and network isolation
Detection: Continuous monitoring, audit logging, and anomaly detection
Response: Automated threat response, incident management, and forensic capabilities

Built-in Security Features

Transparent Data Encryption (TDE) for data at rest
Network encryption for data in transit
Database Vault for privileged user access control
Data Masking and Subsetting for development environments
Advanced Security features included in all service tiers

Exadata Database Service Lifecycle Management

Managing databases on Exadata Database Service follows a structured lifecycle approach that ensures optimal performance and reliability.

1. Create Custom Software Image (Grid Infrastructure Image)

The first step involves creating a custom software image that includes:

Oracle Grid Infrastructure components
Specific patches and updates required for your environment
Custom configurations and settings
Security hardening parameters

This image serves as the foundation for all database deployments and ensures consistency across your infrastructure.

2. Create Database Home

After establishing the software image, you create a database home which:

Defines the Oracle Database software installation
Specifies version and patch levels
Establishes the runtime environment for databases
Provides isolation between different database versions

3. Create Database

The database creation process involves:

Defining database parameters and configuration
Setting up storage allocation and management
Configuring memory and compute resources
Establishing backup and recovery settings

4. Create and Manage Pluggable Database (PDB)

Pluggable Database (PDB) management includes:

Creating multiple PDBs within a single container database
Resource allocation and isolation between PDBs
Independent backup and recovery for each PDB
Simplified database consolidation and management

5. Enable Data Guard Association / Active Data Replication

For high availability and disaster recovery, you can enable Data Guard association which provides:

Real-time data replication to standby databases
Automatic failover capabilities
Zero data loss protection (with synchronous replication)
Active Data Guard for read-only workload offloading

Oracle Data Guard Configuration

Oracle Database supports two role transition operations: switchover and failover.

Switchover

Planned role transition between primary and standby databases
Zero data loss during the transition
Reversible operation that can be switched back
Used for maintenance windows or load balancing

Failover

Unplanned role transition due to primary database failure
Automatic activation of standby database
Minimal downtime for critical applications
Ensures business continuity during disasters

Data Guard Requirements

Both the DB systems must be in the same compartment and must meet specific configuration requirements:

Infrastructure Requirements

Both DB systems must be in the same compartment
Both Exadata Cloud Service instances must use the same VCN for single-region deployments
The DB systems must be the same shape type
Network connectivity between primary and standby systems

Database Requirements

The database versions and editions must be identical
Each database must have a unique name to avoid conflicts
Compatible character sets and database parameters
Sufficient storage capacity on both systems

Additional Considerations

By Default Exadata comes with Extreme Performance, so you can configure Active Data Guard
Proper network bandwidth for data replication
Security configurations must be consistent
Backup strategies should be coordinated

Best Practices for Cost Management

License Optimization

Assess existing licenses before choosing between License Included and BYOL
Consider usage patterns when selecting licensing models
Monitor actual consumption to optimize OCPU allocation
Plan for growth to avoid licensing constraints

Resource Management

Implement automated scaling to match demand patterns
Use PDB consolidation to maximize resource utilization
Monitor performance metrics to right-size deployments
Schedule non-critical workloads during off-peak hours

Conclusion

Exadata Database Service's flexible billing and licensing models provide organizations with options to optimize both costs and performance. Whether you choose License Included for simplicity or BYOL for cost savings, the elastic scaling capabilities ensure you only pay for what you use while maintaining enterprise-grade performance and security.

The comprehensive lifecycle management capabilities, combined with robust Data Guard integration, make Exadata Database Service an ideal platform for mission-critical database workloads requiring high availability, security, and cost optimization.

Ready to optimize your database costs with Exadata Database Service? Evaluate your current licensing position and usage patterns to determine the most cost-effective approach for your organization.

Billing and Licensing in Exadata Database Service

Table of contents