Exadata and Base Database Service – Page-by-Page Notes
3.1 Oracle Base Database Service Overview (Part 1)
What It Is
- A co-managed service on Oracle Cloud Infrastructure (OCI).
- Oracle manages infrastructure → you manage the DB contents.
- Runs Oracle DB Standard Edition & Enterprise workloads.
- VM-based DB systems available worldwide.
Key Features
- Database lifecycle automation: provisioning, patching, scaling, backup/recovery, HA/DR.
- Security by default: Always-on encryption, Defense-in-Depth model.
- Supports DB versions: .
- Deployment options:
- Single-instance VM DB system
- 2-node RAC VM DB system
Licensing Models
- License Included (LI)
- Includes DB Enterprise Edition + management packs.
- Ideal for customers without licenses or wanting advanced features.
- Supports innovation by removing cost barriers.
- Bring Your Own License (BYOL)
- Use existing Oracle DB licenses in the cloud.
- Includes rights to TDE, Diagnostic Pack, Tuning Pack, Data Masking & Subsetting, RAT.
- Support Rewards Program → of cloud spend credited against on-premise support bills.
Licensing Tiers
- Standard Edition 2 → Multitenant (≤), ML, Spatial, Graph.
- Enterprise Edition (EE) → Adds Data Guard, EM Packs (Masking, Subsetting, Tuning, Diagnostics).
- Enterprise Edition High Performance (EE-HP) → Adds lifecycle/cloud mgmt. packs, partitioning, compression, advanced security.
Required if > PDBs. - Enterprise Edition Extreme Performance (EE-EP) → Adds Active Data Guard, RAC, In-Memory.
- RAC & Exadata with License Included require Extreme Performance licensing tier.
Deployment Details
- Choose DB Edition, version, OCPUs, memory.
- Billed per second based on OCPU & license tier.
- Storage:
- Block volumes for DB storage.
- Backups → Recovery Service (default) or Object Storage.
- Recovery Service offers better RTO/RPO at same cost.
- Compute Shapes:
- : Most economical, single-node only, no SE2. ().
- : single-node or RAC.
- : single-node or RAC.
- : Older, . Must switch shape to scale.
3.2 Storage, Availability, and Security (Part 2)
Storage Architecture
- LVM (Logical Volume Manager) → for fast provisioning (single node).
- ASM (Automatic Storage Management) → default; required for 2-node RAC.
- Default: .
- Provides triple mirroring of data.
- Storage scaling: online up to .
- Cloning supported with both LVM and ASM.
Availability Concepts
- Region → Geographical OCI deployment.
- Availability Domain (AD) → Independent data centers in a region.
- Fault Domain (FD) → Hardware/infrastructure grouping within an AD.
High Availability (HA) & Disaster Recovery (DR)
- RAC (2-node) → Instances deployed in separate Fault Domains.
- Data Guard → For HA (within AD) and DR (cross-region).
- Maximum Availability Architecture (MAA) supported.
HA Features by Licensing Tier
- Flashback + Backup & Recovery → all editions.
- Multitenant → all editions (≤3 PDBs); unlimited PDBs in HP/EP tiers.
- Data Guard → All EE editions.
- Active Data Guard → Extreme Performance only.
- RAC → Extreme Performance only.
- Application Continuity → Extreme Performance only (needs ADG or RAC).
- Security: Defense in Depth
- Database Security:
- Transparent Data Encryption (TDE).
- Data Redaction, Masking, Subsetting.
- Key Vault for encryption key separation.
- Database Vault (control DBA access).
- Database Firewall (SQL statement control).
- Data Safe (sensitive data detection + risk assessment).
- System Security:
- Hardened Oracle Linux 7 images.
- Only required packages, disabled unused services.
- Network Security:
- OCI VCNs & VLANs for isolation.
- Native Network Encryption for client–DB traffic.
- Compliance:
- PCI, HIPAA, ISO 27001.
- Antivirus, vulnerability scans, automated alerts.
Takeaway
- Oracle Base Database Service = full-featured DB in the cloud with automation, flexibility in licensing, enterprise HA/DR, and strong security built in.
3.3 Exadata Database Service Overview
What It Is
- Oracle Exadata Database Service = Oracle DB Enterprise with all features, all options, and all management packs.
- Runs on Exadata Database Machine → fault-tolerant, scale-out servers, high-performance RoCE network fabric.
- Ideal for high-performance, HA workloads.
Key Features
- All DB Enterprise features included: RAC, In-Memory, Multitenant, Partitioning, ADG, etc.
- Exadata Innovations: SQL offload, Smart Flash Cache, Storage Index, Hybrid Columnar Compression.
- Latest add-ons: XRMEM accelerators, 100Gb/s RoCE.
- 100% app-compatible with on-premise Oracle DB and Exadata.
Subscription & Licensing
- Pay monthly subscription based on Exadata shape + .
- No upfront CapEx, no datacenter overhead.
- Flexible: License Included (LI) or Bring Your Own License (BYOL).
- Scale up/down elastically → only pay for what you use.
Service Management
- Oracle operations team → Manages infrastructure (network, firmware, servers, storage, RoCE fabric).
- Customer → Manages DB VMs, data, schema, encryption keys.
- Full automation (UI + APIs): provisioning, patching, scaling, backup/restore, HA/DR setup.
- Root access to DB VMs → you can customize + install 3rd-party agents.
Deployment Options
- Exadata Cloud Infrastructure (OCI Public Cloud)
- Dedicated infrastructure managed by Oracle.
- Best for enterprise DBaaS.
- Exadata Cloud@Customer
- Same Exadata & automation but runs in your data center.
- Data residency & compliance guaranteed.
- 4-year minimum subscription for infra.
- On-Premise Exadata (CapEx model)
- You own/manage the hardware.
- Multi-Cloud
- Connect via FastConnect or run Oracle Database@Azure.
All deployments = 100% feature consistent → smooth portability + zero downtime migration.
3.4 Cloud Management Responsibilities
Responsibility Split
- Oracle (Cloud Ops) manages up to hypervisor:
- DB servers, storage servers, firmware, RoCE internal network.
- Infra patching, security scans, OS updates.
- Customer can schedule maintenance windows.
- Customer manages everything above hypervisor:
- Guest VMs, Grid Infrastructure, DB software, schema, data, encryption keys.
- Full automation for lifecycle tasks (via UI or APIs).
- You can install & manage 3rd-party software in DB VMs.
- Oracle staff cannot access your guest VMs.
Lifecycle Management (with Automation)
- Provisioning new DBs.
- Patching DB/Grid Infra.
- Scaling OCPUs/storage.
- Backups & Recovery.
- HA/DR with Data Guard.
- Security (built-in at all layers).
3.5 Billing and Licensing
Licensing Models
- License Included (LI)
- Oracle DB EE + all options + all management packs included.
- Best for customers without existing licenses or needing full DB feature set.
- Bring Your Own License (BYOL)
- Customers use existing EE licenses + DB options.
- Still includes:
- TDE
- Data Safe
- Diagnostics Pack
- Tuning Pack
- Data Masking & Subsetting
- Real Application Testing
- Exadata Storage Server Software (no license needed)
- Oracle Standard Edition not supported on Exadata Database Service.
Cost Optimization with Vertical Scaling
- Billing is based on OCPUs (cores) in use.
- Exadata allows online scaling up/down of → no disruption.
- On-prem systems must be sized for peak workload → overspending on underutilized CPUs.
- Cloud scaling = pay only for what you use.
Security: Defense in Depth
- Database Security
- TDE → Encrypts data at rest.
- Data Redaction, Masking, Subsetting → Users only see relevant data.
- Key Vault → Separates encryption key control.
- Database Vault → Restricts DBA access to user data.
- Database Firewall → Controls which SQL statements are allowed.
- Data Safe → Detects sensitive data, assesses risks.
- System & Compute Security
- Secure implementation guidelines.
- Minimal packages → reduces attack surface.
- Token-based SSH access for admins.
- Network Security
- OCI VCNs/VLANs → Isolate DB access.
- Oracle Native Network Encryption → Protects client–DB connections.
- Dedicated client & backup networks → Separation of traffic.
- Compliance
- Meets FedRAMP, HIPAA, PCI, and other certifications.
- IAM, MFA, policy-based access, groups/compartments for governance.
Operator Access Control (OAC)
- Limits Oracle Ops staff access to your infrastructure.
- Operators must request access → customer approves.
- Customers control:
- Which component is accessed.
- Duration of access.
- Privileges granted.
- Customers can observe & record keystrokes in real time.
- If needed, terminate operator sessions immediately.
- Highly attractive to regulated industries needing strict control + auditability.
Key Takeaways from 3.5
- Two licensing models: License Included vs. BYOL.
- BYOL customers get TDE, Packs, RAT, Exadata Storage Software included.
- Vertical scaling of OCPUs = major cost savings.
- Defense in Depth security model: database, system, network, compliance, operator access control.
- Exadata DB Service is secure, compliant, and gives customers full visibility & control over data access.
3.6 Exadata Database Lifecycle Management – Use Managed Maintenance Tasks (Part 2)
Core Functions
- Update Database Home, Grid Infrastructure, OS, and DB software via rolling patches.
- Custom images and standard images supported for standardization.
- Enable Data Guard for disaster recovery.
- Perform user-managed updates and upgrades.
- Accessible via Console, API, CLI, or SDK.
Custom Software Images
- Purpose: Standardization via approved "gold images."
- Types: Database or Grid Infrastructure images.
- Contents:
- Database/Grid versions.
- Release updates, bundle patches, one-off patches.
- Oracle Home or Grid Home inventory.
- Storage: Oracle-managed Object Storage.
- Created via Console or API.
Database Home & Database Creation
- Database Home:
- Created in Exadata VM Cluster.
- Can use Oracle-provided or custom software image.
- Database Creation:
- Specify name, version, optional PDB name.
- Choose Database Home (existing or new).
- Configure CIS user credentials.
- Backup options: destination + schedule.
- Encryption keys: Oracle-managed or customer-managed (Vault/OKV).
- OKV (Oracle Key Vault) integration: for Cloud@Customer. Centralized key management for TDE, wallets, and keystores.
Pluggable Database (PDB) Lifecycle
- Default: One CDB with one PDB created per database.
- Management:
- Create new PDBs in existing CDBs.
- Direct connection to PDBs with unique connection strings.
- Use Performance Hub for monitoring.
- Cloning PDBs:
- Local clone (same CDB).
- Remote clone (different CDB, same AD).
- Refreshable clone (keeps data synced with source PDB).
- Other Actions: Start/Stop, Relocate, Restore, Delete.
Data Guard for Disaster Recovery
- Purpose: High availability and disaster recovery.
- Capabilities:
- Protect against site or DB failure.
- Minimize downtime during maintenance.
- Supports switchover, failover, and reinstate operations.
- Active Data Guard: adds offloading for reporting, backups, advanced features.
- Setup: Enable via API or console.
- Requirements:
- Primary and standby DBs must be in the same compartment.
- Same DB version required.
- Each DB must have a unique DB name.
- If in same region → share the same VCN.
- If cross-region → VCN peering required.
- Network rules:
- Enable TCP traffic (default SCAN listener port 1521).
- Role Transitions:
- Switchover → planned role reversal.
- Failover → unplanned, promotes standby DB.
- Fast-Start Failover → automatic failover to pre-chosen standby.
- Reinstate → bring failed DB back as standby.
Key Takeaways
- Lifecycle tasks (images, DBs, PDBs, Data Guard) can be done through Console, API, CLI, SDK.
- Custom software images = consistency + easier patching.
- Data Guard provides both planned (switchover) and unplanned (failover) recovery.
- Active Data Guard adds performance and backup benefits, but must be licensed for hybrid use.
- Networking and compartment requirements must be satisfied for Data Guard.
3.7 Exadata Database Lifecycle Management – Use Managed Maintenance Tasks (Part 1)
Maintenance Responsibility
- Oracle Managed Infrastructure Maintenance
- Oracle applies quarterly infrastructure updates to:
- Physical compute servers, Root VM
- Exadata storage servers
- Internal switches (RDMA fabric)
- PDUs, ILOM interfaces, firmware
- Control plane components
- User Managed Maintenance (done quarterly, max )
- Patching Oracle Grid Infrastructure software
- Patching Oracle Database software (VM level)
- Updating Exadata Database VM operating system
Best Practices Before Updates
- Always backup databases.
- Prefer creating a new Database Home instead of updating existing.
- Update Grid Infrastructure before Database Home.
- Run precheck before maintenance.
- Ensure all DB servers are up.
- Free space requirements:
- \/u01\; (Grid Infra Home) \geq 15\;\text{GB}
- \/u02\; (Database Home) \geq 15\;\text{GB}
Finding Patch Levels & Updates
- VM Cluster Details page shows current patch levels.
- Updates page shows available updates for:
- OS (Exadata image updates)
- Grid Infrastructure
- Database Home (Oracle/custom images)
- Update History page shows past patch attempts & outcomes.
OS Image Updates (Exadata Image)
- Updates OS image of VM nodes automatically via Console/API.
- Precheck required before applying.
- Rollback available if issues occur.
- Only latest minor versions are available in console.
Grid Infrastructure Patching
- Updates found on Updates page.
- Options: Run Precheck or Apply Patch.
- Patching is rolling (one node at a time).
- DB instances on node unavailable during update.
3.8 Exadata Database Lifecycle Management – Use Managed Maintenance Tasks (Part 2)
Updating Database Home
- Two paths:
- Update existing DB Home → affects all DBs in it.
- Create new DB Home → move DB(s) to new DB Home (preferred).
- Precheck required before applying.
- Updates applied in rolling manner across RAC instances.
- Moving DB to new DB Home = faster patching, less downtime.
Custom Database Images
- Options:
- Create DB Home with custom image → move DBs individually.
- Update existing DB Home with custom image → updates all DBs.
Impact of Updates
- Zero downtime possible with RAC rolling updates.
- Temporary reduction in compute performance & throughput during updates.
Upgrading Grid Infrastructure
- Upgrades GI software on all compute nodes.
- Rolling upgrade (one node at a time).
- Precheck required.
- Restrictions during upgrade:
- Cannot enable Data Guard
- Cannot perform switchover/failover
- Cannot manage DB Homes, restore DB, or change IORM settings
- Cannot scale CPUs or provision new DBs
Upgrading a Database
- Preparation:
- Backup DB & test version beforehand.
- Run upgrade precheck.
- Create a target DB Home with desired version.
- Ensure all PDBs can open.
- Disable auto backups & take on-demand backup.
- Upgrade Process:
- Automatic precheck
- Create guaranteed restore point
- Move DB to target DB Home
- Upgrade performed by Database Upgrade Assistant (DBUA)
- Data Guard Consideration:
- Upgrade standby first (recommended).
- Redo apply disabled during upgrade.
- Validate redo apply & open mode after upgrade.
Key Takeaways from 3.7/3.8
- Exadata Lifecycle Management supports structured, managed maintenance with options for updating DB Homes, custom images, and Data Guard-aware upgrade flows.
- Rolling upgrades enable near-zero downtime with RAC.
- Data Guard considerations are essential during upgrades; ensure compatibility and testing.
- OKV integration and security controls carry through upgrades; plan for key management during migrations.