{"id":878,"date":"2026-04-16T12:51:49","date_gmt":"2026-04-16T12:51:49","guid":{"rendered":"https:\/\/www.devopsschool.com\/tutorials\/oracle-cloud-autonomous-ai-database-on-dedicated-exadata-infrastructure-tutorial-architecture-pricing-use-cases-and-hands-on-guide-for-data-management\/"},"modified":"2026-04-16T12:51:49","modified_gmt":"2026-04-16T12:51:49","slug":"oracle-cloud-autonomous-ai-database-on-dedicated-exadata-infrastructure-tutorial-architecture-pricing-use-cases-and-hands-on-guide-for-data-management","status":"publish","type":"post","link":"https:\/\/www.devopsschool.com\/tutorials\/oracle-cloud-autonomous-ai-database-on-dedicated-exadata-infrastructure-tutorial-architecture-pricing-use-cases-and-hands-on-guide-for-data-management\/","title":{"rendered":"Oracle Cloud Autonomous AI Database on Dedicated Exadata Infrastructure Tutorial: Architecture, Pricing, Use Cases, and Hands-On Guide for Data Management"},"content":{"rendered":"\n<h2 class=\"wp-block-heading\">Category<\/h2>\n\n\n\n<p>Data Management<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">1. Introduction<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">What this service is<\/h3>\n\n\n\n<p><strong>Autonomous AI Database on Dedicated Exadata Infrastructure<\/strong> is an Oracle Cloud (OCI) managed Oracle Database service that runs on <strong>dedicated Exadata infrastructure<\/strong> (not shared with other customers). It delivers Oracle\u2019s autonomous operations (automated provisioning, tuning, patching, backups) with the performance characteristics of Exadata, and infrastructure isolation that many enterprises require.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">One-paragraph simple explanation<\/h3>\n\n\n\n<p>Think of it as <strong>Oracle Autonomous Database<\/strong>, but instead of running on shared hardware, it runs on <strong>your own dedicated Exadata environment<\/strong> in Oracle Cloud. Oracle manages the database operations, while you get stronger isolation, predictable performance, and governance alignment for regulated or high-scale workloads.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">One-paragraph technical explanation<\/h3>\n\n\n\n<p>Technically, you provision (or use an existing) <strong>Autonomous Exadata Infrastructure<\/strong> in an OCI region\/availability domain, create an <strong>Autonomous Container Database<\/strong>, and then create one or more <strong>Autonomous Database<\/strong> instances (workload types like transaction processing or data warehouse) inside that container. Connectivity can be public or private, authentication and authorization integrate with OCI IAM and database-native controls, and monitoring integrates with OCI Observability services.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">What problem it solves<\/h3>\n\n\n\n<p>It solves the common enterprise problem of needing:\n&#8211; <strong>Autonomous operations<\/strong> (reduced DBA toil, consistent patching, automated backups, automated tuning),\n&#8211; <strong>Dedicated, isolated infrastructure<\/strong> (compliance, noisy-neighbor avoidance, predictable performance),\n&#8211; <strong>Exadata performance<\/strong> (high throughput and low latency),\n&#8211; While staying within OCI\u2019s managed service model.<\/p>\n\n\n\n<blockquote>\n<p>Naming note (verify in official docs): Oracle\u2019s primary documentation commonly uses <strong>\u201cOracle Autonomous Database on Dedicated Exadata Infrastructure\u201d<\/strong> and related resources like <strong>Autonomous Exadata Infrastructure<\/strong> and <strong>Autonomous Container Database<\/strong>. The term <strong>\u201cAutonomous AI Database\u201d<\/strong> is used in some Oracle messaging to emphasize built-in AI\/ML and newer database capabilities. In the OCI Console and most docs you may still see <strong>Autonomous Database<\/strong> as the service name. Always confirm the exact service labels in your OCI region and tenancy.<\/p>\n<\/blockquote>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">2. What is Autonomous AI Database on Dedicated Exadata Infrastructure?<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Official purpose<\/h3>\n\n\n\n<p>The official purpose is to provide <strong>Oracle Autonomous Database<\/strong> capabilities\u2014automated lifecycle management, security hardening defaults, elastic scaling (within constraints), high availability, and performance optimization\u2014on <strong>dedicated Exadata infrastructure<\/strong> in Oracle Cloud, enabling secure and predictable operation for mission-critical workloads.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Core capabilities (what you can do)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Provision Autonomous Database instances on dedicated Exadata capacity.<\/li>\n<li>Choose database workload type (commonly Autonomous Transaction Processing and Autonomous Data Warehouse; exact options vary\u2014verify in your region).<\/li>\n<li>Scale CPU resources and storage within the boundaries of your dedicated environment.<\/li>\n<li>Enable automated backups, point-in-time recovery, and operational automation.<\/li>\n<li>Integrate with OCI IAM, Vault (for customer-managed keys where supported), Monitoring, Logging, and Audit.<\/li>\n<li>Use Oracle-provided database tools (Database Actions, SQL tooling, APIs) to manage schemas, load data, and operate applications.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Major components<\/h3>\n\n\n\n<p>In OCI dedicated autonomous deployments, you typically work with:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>\n<p><strong>Autonomous Exadata Infrastructure<\/strong>\n   &#8211; The dedicated Exadata environment in OCI.\n   &#8211; Represents the physical\/virtual Exadata resources reserved for your tenancy.<\/p>\n<\/li>\n<li>\n<p><strong>Autonomous Container Database (ACD)<\/strong>\n   &#8211; A container layer that hosts multiple Autonomous Database instances.\n   &#8211; Supports separation and management of autonomous databases.<\/p>\n<\/li>\n<li>\n<p><strong>Autonomous Database<\/strong>\n   &#8211; The database instance you connect to (schemas, users, tables, queries).\n   &#8211; Created within an Autonomous Container Database.<\/p>\n<\/li>\n<li>\n<p><strong>Networking constructs (optional but common)<\/strong>\n   &#8211; VCN, subnets, NSGs, route tables.\n   &#8211; Public endpoint (with IP allowlisting) or private endpoint for database access.<\/p>\n<\/li>\n<li>\n<p><strong>Operations &amp; security services<\/strong>\n   &#8211; <strong>OCI Monitoring<\/strong> for metrics.\n   &#8211; <strong>OCI Audit<\/strong> for control-plane events.\n   &#8211; <strong>OCI Logging<\/strong> (where applicable).\n   &#8211; <strong>OCI Vault<\/strong> for key management (where supported).\n   &#8211; <strong>OCI Bastion<\/strong> for secure admin access to private networks (common pattern).<\/p>\n<\/li>\n<\/ol>\n\n\n\n<h3 class=\"wp-block-heading\">Service type<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Managed database service (PaaS)<\/strong> on <strong>dedicated infrastructure<\/strong>.<\/li>\n<li>Oracle manages many operational tasks; you manage schema design, access controls, data modeling, and application integration.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Scope (regional\/global, project\/tenancy)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Typically <strong>regional<\/strong> (resources exist in a specific OCI region).<\/li>\n<li>The underlying infrastructure is placed in a specific <strong>availability domain<\/strong> where applicable.<\/li>\n<li>Resources are <strong>tenancy-scoped<\/strong> and organized by <strong>compartments<\/strong> (OCI\u2019s logical isolation and policy boundary).<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">How it fits into the Oracle Cloud ecosystem<\/h3>\n\n\n\n<p>Autonomous AI Database on Dedicated Exadata Infrastructure sits in OCI\u2019s <strong>Data Management<\/strong> portfolio alongside:\n&#8211; Autonomous Database (including serverless\/shared deployment options),\n&#8211; Exadata Database Service (more DBA control, less autonomous),\n&#8211; Base Database Service and MySQL offerings,\n&#8211; Data integration, analytics, and governance services.<\/p>\n\n\n\n<p>It is often selected when teams want:\n&#8211; A managed database with autonomous features,\n&#8211; But also need dedicated compute\/storage isolation and Exadata performance.<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">3. Why use Autonomous AI Database on Dedicated Exadata Infrastructure?<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Business reasons<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Faster time to value<\/strong>: Provision databases quickly without building\/operating Exadata yourself.<\/li>\n<li><strong>Reduced operational overhead<\/strong>: Autonomous automation can reduce repetitive DBA tasks.<\/li>\n<li><strong>Risk reduction<\/strong>: Consistent patching and backups help meet operational and audit requirements.<\/li>\n<li><strong>Predictable capacity planning<\/strong>: Dedicated infrastructure helps align costs and performance with business-critical workloads.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Technical reasons<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Exadata platform benefits<\/strong>: Designed for high-throughput, mixed workloads (OLTP + analytics) with optimized storage and database integration.<\/li>\n<li><strong>Isolation<\/strong>: Avoid \u201cnoisy neighbor\u201d concerns inherent in shared environments.<\/li>\n<li><strong>Elastic database provisioning inside a dedicated envelope<\/strong>: Create multiple autonomous databases for different apps\/teams while retaining centralized infrastructure control.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Operational reasons<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Standardized automation<\/strong>: Provisioning, backups, patching, and many tuning actions are automated.<\/li>\n<li><strong>Fleet model<\/strong>: Multiple autonomous databases can live under a common dedicated platform, simplifying governance and operations.<\/li>\n<li><strong>Clear separation of duties<\/strong>: Infrastructure admins manage Exadata capacity; application teams manage schemas and users.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Security\/compliance reasons<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Dedicated environment<\/strong>: Helps with regulated workloads and internal policies that require tenant isolation.<\/li>\n<li><strong>Encryption by default<\/strong>: Autonomous Database encrypts data at rest; network encryption is supported; key management integrations may be available (verify).<\/li>\n<li><strong>Auditability<\/strong>: Control-plane actions are captured in OCI Audit; database auditing is available via database features and supporting services.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Scalability\/performance reasons<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>High concurrency<\/strong>: Suitable for many parallel sessions and heavy analytics.<\/li>\n<li><strong>Multiple databases<\/strong>: Scale by deploying multiple autonomous databases across teams\/applications while keeping centralized capacity.<\/li>\n<li><strong>DR patterns<\/strong>: Options like standby\/replication features may be available (verify exact capabilities and prerequisites).<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">When teams should choose it<\/h3>\n\n\n\n<p>Choose Autonomous AI Database on Dedicated Exadata Infrastructure when you need:\n&#8211; Autonomous operations + Exadata performance,\n&#8211; Dedicated isolation,\n&#8211; Multiple mission-critical databases under one governed environment,\n&#8211; Strong compliance posture and predictable performance.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">When they should not choose it<\/h3>\n\n\n\n<p>Avoid (or reconsider) if:\n&#8211; You need <strong>lowest-cost entry<\/strong> or very small workloads \u2192 serverless\/shared Autonomous Database is typically simpler and cheaper.\n&#8211; You require <strong>full OS and database host-level control<\/strong> \u2192 Exadata Database Service or self-managed Oracle Database may fit better.\n&#8211; Your organization cannot commit to dedicated capacity and governance (approvals, quotas, cost controls).\n&#8211; You only need a simple relational database for a small app \u2192 OCI Base Database or other managed databases might be more appropriate.<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">4. Where is Autonomous AI Database on Dedicated Exadata Infrastructure used?<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Industries<\/h3>\n\n\n\n<p>Common in industries with strict governance and performance needs:\n&#8211; Financial services and insurance\n&#8211; Telecommunications\n&#8211; Healthcare and life sciences\n&#8211; Government and public sector\n&#8211; Large-scale retail and logistics\n&#8211; Manufacturing and energy<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Team types<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Central platform\/DBaaS teams offering databases to internal application teams<\/li>\n<li>Enterprise data platform teams<\/li>\n<li>Security-focused operations teams<\/li>\n<li>SRE\/operations groups supporting mission-critical systems<\/li>\n<li>Application teams needing reliable SLAs and performance without heavy DBA involvement<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Workloads<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>High-volume OLTP (payments, orders, account systems)<\/li>\n<li>Mixed workloads (transaction + reporting)<\/li>\n<li>Data warehousing and analytics<\/li>\n<li>Consolidated multi-tenant internal database platforms (many apps, many schemas\/dbs)<\/li>\n<li>Batch processing and near-real-time reporting<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Architectures<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Hub-and-spoke network with private endpoints<\/li>\n<li>Multi-tier applications (web\/app\/db) within OCI<\/li>\n<li>Hybrid connectivity (FastConnect\/VPN) from on-prem to OCI<\/li>\n<li>Multi-region DR designs (where supported and approved)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Real-world deployment contexts<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Production mission-critical databases for ERP\/CRM\/custom apps<\/li>\n<li>Central \u201cdatabase factory\u201d for multiple product teams<\/li>\n<li>Consolidation of legacy Oracle databases into a managed OCI platform<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Production vs dev\/test usage<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Production<\/strong>: Very common due to isolation, governance, and performance.<\/li>\n<li><strong>Dev\/test<\/strong>: Possible, but cost governance matters; teams often use serverless\/shared Autonomous Database for dev\/test and reserve dedicated for staging\/production, or run smaller dedicated environments for pre-prod validation.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">5. Top Use Cases and Scenarios<\/h2>\n\n\n\n<p>Below are realistic scenarios where Autonomous AI Database on Dedicated Exadata Infrastructure is a strong fit.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">1) Regulated OLTP core banking-style workload<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem<\/strong>: High transaction volume with strict compliance and audit requirements.<\/li>\n<li><strong>Why this fits<\/strong>: Dedicated isolation + autonomous patching\/backups + Exadata performance.<\/li>\n<li><strong>Example<\/strong>: A payments platform needs consistent latency and a dedicated environment for regulatory controls.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">2) Consolidated enterprise DBaaS platform<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem<\/strong>: Many teams need databases, but central IT must standardize operations and security.<\/li>\n<li><strong>Why this fits<\/strong>: One dedicated Exadata environment can host many autonomous databases with consistent guardrails.<\/li>\n<li><strong>Example<\/strong>: A shared services team offers separate autonomous databases per department with tagging, cost tracking, and policy controls.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">3) High-concurrency SaaS application (enterprise tier)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem<\/strong>: SaaS requires predictable performance and isolation for large customers.<\/li>\n<li><strong>Why this fits<\/strong>: Dedicated capacity reduces variability; autonomous features reduce operational effort.<\/li>\n<li><strong>Example<\/strong>: A SaaS vendor runs \u201centerprise-tier\u201d tenants on dedicated autonomous databases for guaranteed performance.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">4) Large-scale analytics \/ warehouse with governance controls<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem<\/strong>: Analytics queries compete with other tenants in shared environments; data access must be tightly governed.<\/li>\n<li><strong>Why this fits<\/strong>: Dedicated resources + autonomous tuning + strong database security features.<\/li>\n<li><strong>Example<\/strong>: A retailer runs daily sales analytics and forecasting on a dedicated autonomous data warehouse.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">5) Mission-critical ERP database modernization<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem<\/strong>: Legacy Oracle databases require patching, backups, and performance tuning; operations are costly.<\/li>\n<li><strong>Why this fits<\/strong>: Managed autonomous operations reduce DBA toil; Exadata supports high performance.<\/li>\n<li><strong>Example<\/strong>: Migrate an on-prem Oracle database supporting finance and procurement into OCI dedicated autonomous.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">6) Mixed workload consolidation (reduce database sprawl)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem<\/strong>: Too many standalone databases increase cost and operational risk.<\/li>\n<li><strong>Why this fits<\/strong>: Consolidate into fewer autonomous databases on a dedicated platform with centralized controls.<\/li>\n<li><strong>Example<\/strong>: Consolidate dozens of departmental databases into governed compartments with consistent policies.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">7) Secure data processing for PII\/PHI<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem<\/strong>: Sensitive data requires encryption, restricted access, and audited operations.<\/li>\n<li><strong>Why this fits<\/strong>: Encryption by default, strong IAM integration, private networking options, and audit trails.<\/li>\n<li><strong>Example<\/strong>: A healthcare provider stores patient data and requires strict network isolation and controlled access.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">8) Performance-sensitive batch + real-time reporting<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem<\/strong>: Nightly batches and morning reporting strain the system.<\/li>\n<li><strong>Why this fits<\/strong>: Exadata throughput + autonomous optimization; can scale resources to meet windows (within capacity).<\/li>\n<li><strong>Example<\/strong>: A logistics company processes overnight route optimization and serves morning dashboards.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">9) Hybrid cloud migration landing zone<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem<\/strong>: Need a controlled, performant landing zone in OCI while migrating from on-prem.<\/li>\n<li><strong>Why this fits<\/strong>: Dedicated environment can mirror enterprise controls; private connectivity works well with FastConnect\/VPN.<\/li>\n<li><strong>Example<\/strong>: Stage migrations by moving apps to OCI while keeping some dependencies on-prem.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">10) Environment requiring strict separation from other tenants<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem<\/strong>: Internal policy prohibits shared cloud database hardware.<\/li>\n<li><strong>Why this fits<\/strong>: Dedicated Exadata infrastructure meets isolation requirements.<\/li>\n<li><strong>Example<\/strong>: A government agency mandates dedicated hardware allocation for sensitive workloads.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">6. Core Features<\/h2>\n\n\n\n<blockquote>\n<p>Feature availability can vary by OCI region, database version, and service updates. For anything you plan to standardize on, <strong>verify in official docs<\/strong> for your tenancy\/region.<\/p>\n<\/blockquote>\n\n\n\n<h3 class=\"wp-block-heading\">1) Dedicated Exadata isolation<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does<\/strong>: Runs autonomous databases on Exadata capacity dedicated to your tenancy.<\/li>\n<li><strong>Why it matters<\/strong>: Stronger isolation and more predictable performance.<\/li>\n<li><strong>Practical benefit<\/strong>: Reduced risk from other tenants\u2019 workloads and clearer compliance alignment.<\/li>\n<li><strong>Caveats<\/strong>: Requires capacity planning and budget approval; not a \u201csmall spend\u201d entry point.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">2) Autonomous operations (patching, backups, tuning)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does<\/strong>: Automates key operational tasks.<\/li>\n<li><strong>Why it matters<\/strong>: Reduces human error and ongoing operational workload.<\/li>\n<li><strong>Practical benefit<\/strong>: Faster provisioning and consistent maintenance posture.<\/li>\n<li><strong>Caveats<\/strong>: You don\u2019t get the same level of host\/OS control as self-managed Oracle Database.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">3) Multi-database platform under Autonomous Container Database<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does<\/strong>: Allows multiple autonomous databases within the container on the same dedicated platform.<\/li>\n<li><strong>Why it matters<\/strong>: Enables internal DBaaS models and centralized governance.<\/li>\n<li><strong>Practical benefit<\/strong>: Standardized deployment patterns and easier consolidation.<\/li>\n<li><strong>Caveats<\/strong>: Requires clear compartment design, tagging, and capacity management.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">4) Workload types (transaction processing \/ data warehouse)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does<\/strong>: Lets you select a workload profile optimized for OLTP or analytics (naming varies by console and release).<\/li>\n<li><strong>Why it matters<\/strong>: Different workloads benefit from different defaults and resource patterns.<\/li>\n<li><strong>Practical benefit<\/strong>: Better performance outcomes with less manual tuning.<\/li>\n<li><strong>Caveats<\/strong>: Confirm supported workload choices in your region.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">5) Network access models: public endpoint and private endpoint<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does<\/strong>: Controls how clients connect to the database.<\/li>\n<li><strong>Why it matters<\/strong>: Network exposure is a primary security decision.<\/li>\n<li><strong>Practical benefit<\/strong>:<\/li>\n<li>Public endpoint can simplify initial setup (with IP allowlisting and mTLS).<\/li>\n<li>Private endpoint enables private-only access via VCN, VPN, or FastConnect.<\/li>\n<li><strong>Caveats<\/strong>: Public endpoints require strict allowlists; private endpoints require more network setup.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">6) Always-on encryption and secure connectivity<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does<\/strong>: Encrypts data at rest; supports TLS for data in transit.<\/li>\n<li><strong>Why it matters<\/strong>: Foundational control for compliance and risk reduction.<\/li>\n<li><strong>Practical benefit<\/strong>: Strong defaults reduce the chance of insecure deployments.<\/li>\n<li><strong>Caveats<\/strong>: Customer-managed key options and specific encryption behaviors should be verified in docs for your deployment type.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">7) Built-in tooling (Database Actions \/ SQL tools)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does<\/strong>: Provides web-based database administration and development tools.<\/li>\n<li><strong>Why it matters<\/strong>: Lowers the barrier for developers and operators.<\/li>\n<li><strong>Practical benefit<\/strong>: Run SQL, manage users, load data, and review performance without installing heavy clients.<\/li>\n<li><strong>Caveats<\/strong>: Network access to the database (public\/private) affects tool accessibility.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">8) Monitoring and metrics integration (OCI Observability)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does<\/strong>: Exposes performance and operational metrics.<\/li>\n<li><strong>Why it matters<\/strong>: You need visibility for SRE-style operations.<\/li>\n<li><strong>Practical benefit<\/strong>: Alarms, dashboards, and incident workflows can be standardized.<\/li>\n<li><strong>Caveats<\/strong>: Some advanced monitoring may require enabling additional services (verify).<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">9) IAM integration and compartment governance<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does<\/strong>: Uses OCI IAM policies to control who can create, update, and delete resources.<\/li>\n<li><strong>Why it matters<\/strong>: Prevents uncontrolled provisioning and helps enforce least privilege.<\/li>\n<li><strong>Practical benefit<\/strong>: Centralized access control with audit trails.<\/li>\n<li><strong>Caveats<\/strong>: IAM controls the OCI resources; database users\/roles still need separate governance.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">10) High availability design (platform-level)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does<\/strong>: Uses Oracle\u2019s managed architecture to provide HA characteristics (implementation details depend on service).<\/li>\n<li><strong>Why it matters<\/strong>: Reduces downtime risk for mission-critical systems.<\/li>\n<li><strong>Practical benefit<\/strong>: HA without building complex clusters yourself.<\/li>\n<li><strong>Caveats<\/strong>: Confirm exact HA\/SLA characteristics and DR options for your deployment type.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">7. Architecture and How It Works<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">High-level service architecture<\/h3>\n\n\n\n<p>At a high level:\n&#8211; You allocate <strong>dedicated Exadata<\/strong> capacity in OCI.\n&#8211; You create an <strong>Autonomous Container Database<\/strong> on that infrastructure.\n&#8211; You provision <strong>Autonomous Database<\/strong> instances inside the container.\n&#8211; Clients connect via:\n  &#8211; Public endpoint (secured with TLS + IP allowlisting), or\n  &#8211; Private endpoint (via VCN private IP, often through VPN\/FastConnect).<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Request\/data\/control flow<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Control plane<\/strong> (OCI APIs\/Console):<\/li>\n<li>Create\/update\/delete the Exadata infrastructure objects and autonomous databases.<\/li>\n<li>Governed via OCI IAM policies.<\/li>\n<li>\n<p>Logged via OCI Audit.<\/p>\n<\/li>\n<li>\n<p><strong>Data plane<\/strong> (SQL\/DB connections):<\/p>\n<\/li>\n<li>Application connects to the autonomous database endpoint.<\/li>\n<li>Data operations occur within the database.<\/li>\n<li>Backups\/maintenance are orchestrated by the service.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Integrations with related services<\/h3>\n\n\n\n<p>Common integrations in Oracle Cloud:\n&#8211; <strong>OCI Vault<\/strong>: key management (where supported) and secret storage for application credentials (usually store app secrets in Vault, not in code).\n&#8211; <strong>OCI Bastion<\/strong>: controlled administrative access to private networks (for private endpoint databases).\n&#8211; <strong>OCI Monitoring &amp; Alarms<\/strong>: metrics-based alerting.\n&#8211; <strong>OCI Logging \/ Audit<\/strong>: auditing of control-plane actions; database auditing via Oracle Database features and supporting services.\n&#8211; <strong>Networking (VCN, NSG, Security Lists, DRG)<\/strong>: private access patterns, hybrid connectivity.\n&#8211; <strong>OCI Resource Manager (Terraform)<\/strong>: infrastructure-as-code for repeatability (verify provider resources and fields).<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Dependency services<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>OCI IAM (users, groups, policies)<\/li>\n<li>OCI Networking (VCN, subnet) for private endpoint use<\/li>\n<li>OCI Key Management (optional)<\/li>\n<li>OCI Object Storage (commonly used for data staging and backups in cloud patterns; specifics vary\u2014verify)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Security\/authentication model<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>OCI IAM<\/strong> controls who can manage the OCI resources (create DBs, download wallets, rotate keys, etc.).<\/li>\n<li><strong>Database authentication<\/strong> uses database-native users\/roles; typically password auth + TLS\/mTLS depending on setup.<\/li>\n<li>Some organizations integrate enterprise identity patterns at the application tier (SSO to apps) while maintaining strict database credential handling.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Networking model<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Public endpoint model<\/strong>:<\/li>\n<li>Database has a public endpoint.<\/li>\n<li>Restrict with <strong>IP allowlists<\/strong> and enforce TLS\/mTLS as per service requirements.<\/li>\n<li><strong>Private endpoint model<\/strong>:<\/li>\n<li>Database gets a private IP in a customer subnet.<\/li>\n<li>Access from applications in the VCN, peered VCNs, or via VPN\/FastConnect.<\/li>\n<li>Most production enterprises prefer this model.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Monitoring\/logging\/governance considerations<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Use <strong>compartments<\/strong> per environment (dev\/test\/prod) and per business unit.<\/li>\n<li>Apply <strong>tags<\/strong> for cost and ownership.<\/li>\n<li>Enable <strong>alarms<\/strong> for CPU, storage, session counts, and service-specific health metrics (verify metric names in your tenancy).<\/li>\n<li>Use <strong>OCI Audit<\/strong> for change tracking and incident review.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Simple architecture diagram (Mermaid)<\/h3>\n\n\n\n<pre><code class=\"language-mermaid\">flowchart LR\n  Dev[Developer\/DBA] --&gt;|OCI Console \/ API| OCI[Oracle Cloud Control Plane]\n  OCI --&gt;|Provision| AEI[Autonomous Exadata Infrastructure (Dedicated)]\n  AEI --&gt; ACD[Autonomous Container Database]\n  ACD --&gt; ADB[Autonomous Database]\n\n  App[Application] --&gt;|SQL\/TLS| ADB\n<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">Production-style architecture diagram (Mermaid)<\/h3>\n\n\n\n<pre><code class=\"language-mermaid\">flowchart TB\n  subgraph OnPrem[On-Prem \/ Corporate Network]\n    Users[Users]\n    Apps[App Services]\n  end\n\n  subgraph OCI[Oracle Cloud (Region)]\n    subgraph Net[VCN]\n      WAF[Edge\/WAF (optional)]\n      LB[Load Balancer]\n      AppTier[Compute \/ OKE App Tier]\n      Bastion[OCI Bastion]\n      subgraph DataSubnet[Private Data Subnet]\n        ADBpriv[Autonomous Database (Private Endpoint)]\n      end\n    end\n\n    subgraph Exa[Dedicated Exadata Platform]\n      AEI[Autonomous Exadata Infrastructure]\n      ACD[Autonomous Container Database]\n    end\n\n    Mon[OCI Monitoring\/Alarms]\n    Audit[OCI Audit]\n    Vault[OCI Vault]\n  end\n\n  Users --&gt; WAF --&gt; LB --&gt; AppTier --&gt;|SQL\/TLS| ADBpriv\n  Apps --&gt;|FastConnect\/VPN via DRG| AppTier\n  Bastion --&gt; AppTier\n\n  AEI --&gt; ACD --&gt; ADBpriv\n\n  AppTier --&gt; Mon\n  ADBpriv --&gt; Mon\n  OCI --&gt; Audit\n  AppTier --&gt; Vault\n<\/code><\/pre>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">8. Prerequisites<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Tenancy and account requirements<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>An active <strong>Oracle Cloud<\/strong> tenancy with billing enabled.<\/li>\n<li>A compartment strategy (at minimum: a compartment where database resources can be created).<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Permissions \/ IAM roles<\/h3>\n\n\n\n<p>You need OCI IAM permissions to manage:\n&#8211; Autonomous Database resources\n&#8211; Autonomous Exadata Infrastructure resources (or at least to use existing ones)\n&#8211; Networking resources (if using private endpoints)\n&#8211; Wallet download permissions (if required by your access model)<\/p>\n\n\n\n<p>OCI permissions are defined via policies. Exact policy statements depend on your org structure. Use the official IAM documentation to craft least-privilege policies:\n&#8211; https:\/\/docs.oracle.com\/en-us\/iaas\/Content\/Identity\/Concepts\/overview.htm<\/p>\n\n\n\n<blockquote>\n<p>Practical note: In many enterprises, <strong>platform admins<\/strong> manage the Autonomous Exadata Infrastructure and Autonomous Container Database, while app teams are allowed to create autonomous databases inside approved containers.<\/p>\n<\/blockquote>\n\n\n\n<h3 class=\"wp-block-heading\">Billing requirements<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Dedicated Exadata infrastructure is typically a significant spend compared to serverless\/shared services.<\/li>\n<li>Ensure your tenancy has appropriate limits and budget approval.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">CLI\/SDK\/tools needed<\/h3>\n\n\n\n<p>For this tutorial, you can complete the lab using:\n&#8211; OCI Console (recommended)\n&#8211; A browser for Database Actions\nOptional tools for advanced validation:\n&#8211; SQLcl or SQL<em>Plus (if allowed)\n&#8211; Oracle Instant Client (if needed for SQL<\/em>Plus)\n&#8211; OCI CLI (optional)<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Region availability<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Dedicated autonomous on Exadata is not available in every OCI region.<\/li>\n<li>Verify availability in the OCI Console region selector and official docs:<\/li>\n<li>https:\/\/docs.oracle.com\/en-us\/iaas\/autonomous-database\/<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Quotas\/limits<\/h3>\n\n\n\n<p>Expect quota checks for:\n&#8211; Autonomous Exadata Infrastructure\n&#8211; Autonomous Container Database\n&#8211; Autonomous Databases (count and total OCPUs)\n&#8211; Networking limits (VCNs, subnets, NSGs)<\/p>\n\n\n\n<p>If you hit quota errors, request increases through OCI support processes (your org\u2019s standard path).<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Prerequisite services<\/h3>\n\n\n\n<p>Depending on your chosen connectivity pattern:\n&#8211; VCN\/subnets\/NSGs (for private endpoint)\n&#8211; Bastion (for secure access to private networks)\n&#8211; Vault (if using customer-managed keys or storing secrets)<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">9. Pricing \/ Cost<\/h2>\n\n\n\n<blockquote>\n<p>Do not rely on blog posts for pricing. OCI pricing changes and varies by region and contract. Always confirm using official sources.<\/p>\n<\/blockquote>\n\n\n\n<h3 class=\"wp-block-heading\">Current pricing model (how you are charged)<\/h3>\n\n\n\n<p>Autonomous AI Database on Dedicated Exadata Infrastructure generally has <strong>capacity-based cost drivers<\/strong> that may include:\n&#8211; <strong>Dedicated Exadata infrastructure capacity<\/strong> (the reserved Exadata environment)\n&#8211; <strong>Database compute consumption<\/strong> (OCPU-based, depending on configuration and scaling model)\n&#8211; <strong>Storage<\/strong> allocated\/consumed\n&#8211; <strong>Optional features<\/strong> (for example, DR\/standby capabilities, specialized monitoring, or add-on services\u2014verify)<\/p>\n\n\n\n<p>The exact billing dimensions can differ based on:\n&#8211; Region\n&#8211; Service deployment model (dedicated vs serverless\/shared)\n&#8211; Contract type (Pay As You Go vs Universal Credits)\n&#8211; Any negotiated enterprise terms<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Free tier<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>OCI Free Tier generally applies to select services and limited always-free resources.<\/li>\n<li>Dedicated Exadata infrastructure typically is <strong>not<\/strong> a free-tier service. Verify current Free Tier offerings:<\/li>\n<li>https:\/\/www.oracle.com\/cloud\/free\/<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Cost drivers (what increases spend)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Provisioning <strong>Autonomous Exadata Infrastructure<\/strong> (baseline ongoing cost)<\/li>\n<li>Higher OCPU allocation or autoscaling configuration (if enabled)<\/li>\n<li>Higher allocated storage, data growth, and backup retention requirements<\/li>\n<li>Network architecture (e.g., data egress to the internet, inter-region replication)<\/li>\n<li>Enabling DR\/standby (often doubles some compute\/storage footprint)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Hidden or indirect costs<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Environment duplication<\/strong>: separate dedicated platforms for dev\/test\/prod can multiply cost.<\/li>\n<li><strong>Data movement<\/strong>: exporting large datasets out of OCI can add egress charges.<\/li>\n<li><strong>Operational tooling<\/strong>: logging retention, monitoring data, and third-party tooling can add cost.<\/li>\n<li><strong>Backups and retention<\/strong>: longer retention often means more storage.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Network\/data transfer implications<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Intra-VCN traffic is generally not charged the same way as internet egress, but OCI network pricing has specifics\u2014verify:<\/li>\n<li>https:\/\/www.oracle.com\/cloud\/pricing\/<\/li>\n<li><strong>Internet egress<\/strong> (data leaving OCI to the public internet) can be a meaningful cost driver.<\/li>\n<li><strong>Inter-region<\/strong> replication\/DR can incur additional charges and bandwidth costs.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">How to optimize cost (practical guidance)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Right-size the dedicated environment: start with the smallest viable dedicated footprint that meets requirements.<\/li>\n<li>Consolidate: host multiple databases in one dedicated platform where governance allows.<\/li>\n<li>Use non-production cost controls:<\/li>\n<li>Shorter retention in dev\/test<\/li>\n<li>Schedule scale-down for predictable off-hours (if your model supports it\u2014verify)<\/li>\n<li>Tag everything and use budgets\/cost reports.<\/li>\n<li>Prefer private connectivity to reduce security risk; cost impact depends on architecture (FastConnect, VPN, etc.).<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Example low-cost starter estimate (without fabricating prices)<\/h3>\n\n\n\n<p>A \u201cstarter\u201d dedicated model is still typically a <strong>significant monthly commitment<\/strong> compared to serverless\/shared. A realistic approach to estimate:\n1. In OCI Pricing pages, locate <strong>Autonomous Database \u2013 Dedicated<\/strong> and <strong>Exadata Infrastructure<\/strong> pricing entries for your region.\n2. Use the <strong>OCI Cost Estimator<\/strong> \/ calculator:\n   &#8211; https:\/\/www.oracle.com\/cloud\/costestimator.html (verify current URL in Oracle docs)\n3. Model:\n   &#8211; 1 dedicated Exadata infrastructure\n   &#8211; 1 container database\n   &#8211; 1 small autonomous database for a lab schema\n   &#8211; Minimal storage\n4. Add expected hours (always-on unless you have a stop\/start capability\u2014verify for your exact deployment model)<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Example production cost considerations<\/h3>\n\n\n\n<p>For production, plan for:\n&#8211; Dedicated platform sized for peak workloads and growth\n&#8211; At least one standby\/DR environment if required\n&#8211; Separate non-prod environments (or strong workload isolation)\n&#8211; Monitoring, audit retention, and security services\n&#8211; Change management windows and operational staffing (even \u201cautonomous\u201d requires governance)<\/p>\n\n\n\n<p>Official pricing starting points:\n&#8211; OCI pricing overview: https:\/\/www.oracle.com\/cloud\/pricing\/\n&#8211; OCI cost estimation: https:\/\/www.oracle.com\/cloud\/costestimator.html (verify)\n&#8211; Autonomous Database docs (for deployment model specifics): https:\/\/docs.oracle.com\/en-us\/iaas\/autonomous-database\/<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">10. Step-by-Step Hands-On Tutorial<\/h2>\n\n\n\n<p>This lab is designed to be <strong>realistic and executable<\/strong>, but there is one important constraint:<\/p>\n\n\n\n<blockquote>\n<p>Dedicated Exadata infrastructure is usually provisioned by a platform team and is not \u201ccheap to spin up for a tutorial.\u201d This lab assumes your tenancy already has:\n&#8211; An <strong>Autonomous Exadata Infrastructure<\/strong>\n&#8211; An <strong>Autonomous Container Database<\/strong><\/p>\n<p>If you do not have these, coordinate with your OCI administrators. For learning-only practice without dedicated capacity, Oracle\u2019s serverless\/shared Autonomous Database is typically used instead\u2014but that is a different deployment model.<\/p>\n<\/blockquote>\n\n\n\n<h3 class=\"wp-block-heading\">Objective<\/h3>\n\n\n\n<p>Create an <strong>Autonomous Database<\/strong> on <strong>Dedicated Exadata Infrastructure<\/strong>, connect using <strong>Database Actions<\/strong>, create a schema, load sample data, and validate basic operations.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Lab Overview<\/h3>\n\n\n\n<p>You will:\n1. Confirm prerequisites (compartment, dedicated resources, IAM access).\n2. Create an Autonomous Database in the existing Autonomous Container Database.\n3. Configure secure access (public endpoint with IP allowlist for simplicity).\n4. Connect via Database Actions and run SQL to create objects and insert data.\n5. Validate metrics and basic health.\n6. Clean up the database (and optionally keep it if you need it).<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Step 1: Verify you have access to dedicated autonomous resources<\/h3>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Log in to the <strong>Oracle Cloud Console<\/strong>.<\/li>\n<li>Select the correct <strong>Region<\/strong> (top right).<\/li>\n<li>Navigate to <strong>Oracle Database<\/strong> \/ <strong>Autonomous Database<\/strong> area (menu names vary slightly by console updates).<\/li>\n<li>Confirm you can see:\n   &#8211; <strong>Autonomous Exadata Infrastructure<\/strong> (existing)\n   &#8211; <strong>Autonomous Container Database<\/strong> (existing)<\/li>\n<\/ol>\n\n\n\n<p><strong>Expected outcome<\/strong>\n&#8211; You can identify the name\/OCID of the Autonomous Container Database you are allowed to use.<\/p>\n\n\n\n<p><strong>Verification<\/strong>\n&#8211; Open the Autonomous Container Database details page and confirm its lifecycle state is <strong>Available<\/strong> (or equivalent healthy state).<\/p>\n\n\n\n<p><strong>Common issue<\/strong>\n&#8211; You don\u2019t see any dedicated resources.\n  &#8211; <strong>Fix<\/strong>: You likely lack IAM permissions or the resources do not exist in this region\/compartment. Ask your platform admin.<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Step 2: Create an Autonomous Database on the dedicated platform<\/h3>\n\n\n\n<ol class=\"wp-block-list\">\n<li>In the OCI Console, go to <strong>Autonomous Database<\/strong> and click <strong>Create Autonomous Database<\/strong>.<\/li>\n<li>Choose the <strong>Compartment<\/strong> for the database.<\/li>\n<li>Enter:\n   &#8211; <strong>Display name<\/strong>: <code>adb-dedicated-lab<\/code>\n   &#8211; <strong>Database name<\/strong>: follow naming rules shown in the console<\/li>\n<li>Under <strong>Deployment type<\/strong> (wording may vary), select <strong>Dedicated Exadata Infrastructure<\/strong> (or the dedicated option presented).<\/li>\n<li>Select the target:\n   &#8211; <strong>Autonomous Container Database<\/strong> (the one verified in Step 1)<\/li>\n<li>Choose <strong>Workload type<\/strong> appropriate for a simple lab:\n   &#8211; Transaction processing or Data warehouse (choose what your org allows; either works for basic SQL)<\/li>\n<li>\n<p>Configure compute and storage:\n   &#8211; Choose small values appropriate for a lab <strong>within your platform\u2019s allowed minimums<\/strong>.\n   &#8211; If there is an autoscaling option, keep it <strong>off<\/strong> for cost control unless your admin recommends otherwise.<\/p>\n<\/li>\n<li>\n<p>Set the <strong>ADMIN password<\/strong>:\n   &#8211; Follow the complexity rules shown.\n   &#8211; Store it securely (password manager or OCI Vault; do not paste into tickets or chat).<\/p>\n<\/li>\n<li>\n<p>Network access (for beginner-friendly connectivity):\n   &#8211; Select <strong>Public endpoint<\/strong> (if your organization allows it).\n   &#8211; Add your current public IP in the <strong>IP allowlist<\/strong>.\n   &#8211; If your org requires private endpoints only, skip public and coordinate network access (private endpoint requires VCN\/subnet and a path to it).<\/p>\n<\/li>\n<li>\n<p>Create the database.<\/p>\n<\/li>\n<\/ol>\n\n\n\n<p><strong>Expected outcome<\/strong>\n&#8211; The Autonomous Database enters a <strong>Provisioning<\/strong> state, then becomes <strong>Available<\/strong>.<\/p>\n\n\n\n<p><strong>Verification<\/strong>\n&#8211; Open the database details page and confirm:\n  &#8211; Lifecycle state: <strong>Available<\/strong>\n  &#8211; The database has a connect endpoint (public or private)\n  &#8211; Database Actions is enabled\/available (if shown)<\/p>\n\n\n\n<p><strong>Common errors and fixes<\/strong>\n&#8211; <strong>Quota exceeded \/ limit reached<\/strong>\n  &#8211; Fix: Request quota increase or use a different compartment\/region with capacity.\n&#8211; <strong>No dedicated capacity available<\/strong>\n  &#8211; Fix: Your Autonomous Container Database may not have available resources. Ask platform admin to scale capacity.<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Step 3: Connect using Database Actions (SQL Worksheet)<\/h3>\n\n\n\n<p>This step avoids installing clients and is typically the fastest way to validate.<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>From the Autonomous Database details page, click <strong>Database Actions<\/strong> (or <strong>Open Database Actions<\/strong>).<\/li>\n<li>\n<p>Log in:\n   &#8211; Username: <code>ADMIN<\/code> (or another database user if your org disallows ADMIN for interactive access)\n   &#8211; Password: the password you set<\/p>\n<\/li>\n<li>\n<p>Open <strong>SQL<\/strong> \/ <strong>SQL Worksheet<\/strong> (menu labels vary).<\/p>\n<\/li>\n<\/ol>\n\n\n\n<p><strong>Expected outcome<\/strong>\n&#8211; You can run SQL queries successfully.<\/p>\n\n\n\n<p><strong>Verification<\/strong>\nRun:<\/p>\n\n\n\n<pre><code class=\"language-sql\">SELECT sys_context('USERENV','DB_NAME') AS db_name FROM dual;\n<\/code><\/pre>\n\n\n\n<p>You should see your database name.<\/p>\n\n\n\n<p><strong>Common issues<\/strong>\n&#8211; <strong>Cannot access Database Actions<\/strong>\n  &#8211; Fix: If you used private endpoint only, you may need private network access (VPN\/FastConnect\/Bastion). For the lab, use a public endpoint if policy allows.<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Step 4: Create a lab user and schema objects<\/h3>\n\n\n\n<p>In SQL Worksheet, run:<\/p>\n\n\n\n<pre><code class=\"language-sql\">-- Create a dedicated lab user\nCREATE USER lab_user IDENTIFIED BY \"Use-A-Strong-Passw0rd!\";\n\n-- Grant minimal privileges for a simple lab\nGRANT CREATE SESSION, CREATE TABLE, CREATE SEQUENCE, CREATE VIEW TO lab_user;\n\n-- Optional: if you want the user to create procedures in the lab\n-- GRANT CREATE PROCEDURE TO lab_user;\n<\/code><\/pre>\n\n\n\n<p>Now create a simple table and load data:<\/p>\n\n\n\n<pre><code class=\"language-sql\">ALTER SESSION SET current_schema = lab_user;\n\nCREATE TABLE customers (\n  customer_id NUMBER GENERATED BY DEFAULT AS IDENTITY PRIMARY KEY,\n  email       VARCHAR2(320) NOT NULL,\n  full_name   VARCHAR2(200) NOT NULL,\n  created_at  TIMESTAMP DEFAULT SYSTIMESTAMP NOT NULL\n);\n\nCREATE UNIQUE INDEX customers_email_uq ON customers(email);\n\nINSERT INTO customers (email, full_name) VALUES ('ana@example.com', 'Ana Gomez');\nINSERT INTO customers (email, full_name) VALUES ('dev@example.com', 'Dev Patel');\nINSERT INTO customers (email, full_name) VALUES ('mei@example.com', 'Mei Chen');\n\nCOMMIT;\n\nSELECT customer_id, email, full_name, created_at\nFROM customers\nORDER BY customer_id;\n<\/code><\/pre>\n\n\n\n<p><strong>Expected outcome<\/strong>\n&#8211; A <code>LAB_USER.CUSTOMERS<\/code> table exists and returns 3 rows.<\/p>\n\n\n\n<p><strong>Verification<\/strong>\nRun:<\/p>\n\n\n\n<pre><code class=\"language-sql\">SELECT COUNT(*) AS customer_count FROM lab_user.customers;\n<\/code><\/pre>\n\n\n\n<p>Result should be <code>3<\/code>.<\/p>\n\n\n\n<p><strong>Common issues<\/strong>\n&#8211; <strong>ORA-01031 insufficient privileges<\/strong>\n  &#8211; Fix: Ensure you are running the <code>GRANT<\/code> statements as <code>ADMIN<\/code> (or a privileged admin user).\n&#8211; <strong>Password complexity errors<\/strong>\n  &#8211; Fix: Adjust the password to meet the shown requirements.<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Step 5: Validate basic observability and governance signals<\/h3>\n\n\n\n<ol class=\"wp-block-list\">\n<li>In OCI Console, open the Autonomous Database details page.<\/li>\n<li>Check:\n   &#8211; Metrics charts (CPU, storage, sessions\u2014exact charts vary)\n   &#8211; Work requests\/events for provisioning\n   &#8211; Tags (add cost-center and owner tags if your org uses them)<\/li>\n<\/ol>\n\n\n\n<p><strong>Expected outcome<\/strong>\n&#8211; You can see the database health and basic metrics.<\/p>\n\n\n\n<p><strong>Verification<\/strong>\n&#8211; Create a simple alarm (optional) if you have access:\n  &#8211; Alarm on storage utilization threshold (verify metric names in your tenancy).<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Validation<\/h3>\n\n\n\n<p>Use this checklist:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>[ ] Autonomous Database state is <strong>Available<\/strong><\/li>\n<li>[ ] You can open <strong>Database Actions<\/strong><\/li>\n<li>[ ] <code>lab_user<\/code> exists<\/li>\n<li>[ ] <code>lab_user.customers<\/code> contains 3 rows<\/li>\n<li>[ ] OCI Console shows basic metrics and no active errors<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Troubleshooting<\/h3>\n\n\n\n<p><strong>Issue: \u201cNotAuthorizedOrNotFound\u201d when creating the database<\/strong>\n&#8211; Likely cause: IAM policies do not allow creation in this compartment or dedicated model.\n&#8211; Fix: Ask admin for a policy update or use the correct compartment.<\/p>\n\n\n\n<p><strong>Issue: Database stuck in provisioning<\/strong>\n&#8211; Likely cause: capacity constraints or service issues.\n&#8211; Fix: Check Work Requests, confirm capacity in the Autonomous Container Database, and review OCI service status.<\/p>\n\n\n\n<p><strong>Issue: Can\u2019t connect from your network<\/strong>\n&#8211; Public endpoint: confirm your IP allowlist is correct and your IP did not change.\n&#8211; Private endpoint: confirm you have private network path (VPN\/FastConnect\/peering) and correct DNS\/security rules.<\/p>\n\n\n\n<p><strong>Issue: You need client tools<\/strong>\n&#8211; Prefer Database Actions for learning.\n&#8211; If you must use SQL tools and wallets, follow the official \u201cConnect to Autonomous Database\u201d documentation (wallet download and TLS settings vary by configuration):\n  &#8211; https:\/\/docs.oracle.com\/en-us\/iaas\/autonomous-database\/<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Cleanup<\/h3>\n\n\n\n<p>To avoid ongoing cost and clutter:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>\n<p>In SQL Worksheet (optional), drop objects:\n   <code>sql\n   DROP TABLE lab_user.customers PURGE;\n   DROP USER lab_user CASCADE;<\/code><\/p>\n<\/li>\n<li>\n<p>In OCI Console:\n   &#8211; Navigate to your Autonomous Database <code>adb-dedicated-lab<\/code>\n   &#8211; Click <strong>Terminate<\/strong> (or <strong>Delete<\/strong>) and confirm<\/p>\n<\/li>\n<\/ol>\n\n\n\n<p><strong>Expected outcome<\/strong>\n&#8211; The autonomous database is deleted and no longer billable as a running database instance (note: dedicated infrastructure may still incur costs).<\/p>\n\n\n\n<blockquote>\n<p>Important: Deleting the Autonomous Database does <strong>not<\/strong> delete the <strong>Autonomous Exadata Infrastructure<\/strong>. The dedicated platform continues to incur cost until terminated (and termination is usually tightly controlled).<\/p>\n<\/blockquote>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">11. Best Practices<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Architecture best practices<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Prefer <strong>private endpoints<\/strong> for production; use public endpoints only with strict allowlists and strong governance.<\/li>\n<li>Use <strong>separate compartments<\/strong> for dev\/test\/prod, and separate policies.<\/li>\n<li>Consolidate multiple databases under a governed dedicated platform to improve utilization and simplify operations.<\/li>\n<li>Plan DR early: define RPO\/RTO and verify supported options (e.g., standby\/replication features).<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">IAM\/security best practices<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Enforce least privilege:<\/li>\n<li>Separate roles for infrastructure admins (Exadata\/container management) and application DB creators.<\/li>\n<li>Restrict wallet download permissions and admin user usage.<\/li>\n<li>Require MFA\/SSO for OCI Console access via your identity provider (where applicable).<\/li>\n<li>Tag resources with owner, environment, and cost center.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Cost best practices<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Right-size and consolidate: dedicated platforms are cost-effective when well-utilized.<\/li>\n<li>Set budgets and cost alerts at compartment level.<\/li>\n<li>Keep non-production lean (smaller databases, shorter retention, fewer add-ons).<\/li>\n<li>Track growth: storage and backups grow over time\u2014measure and forecast.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Performance best practices<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Use appropriate workload type selection (OLTP vs warehouse).<\/li>\n<li>Design schemas properly:<\/li>\n<li>Correct indexing strategy<\/li>\n<li>Partitioning where appropriate (verify included features and constraints)<\/li>\n<li>Avoid anti-patterns:<\/li>\n<li>Unbounded result sets<\/li>\n<li>Missing predicates<\/li>\n<li>Excessive commits in loops<\/li>\n<li>Load test before production and baseline metrics.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Reliability best practices<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Define maintenance windows and change processes (verify what scheduling control the service offers).<\/li>\n<li>Use application-level retries and connection pooling.<\/li>\n<li>Validate backup\/restore and DR procedures at least quarterly.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Operations best practices<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Standardize dashboards and alarms (CPU, sessions, storage, error events).<\/li>\n<li>Use OCI Audit logs to track changes to databases, network settings, and IAM.<\/li>\n<li>Maintain a runbook for:<\/li>\n<li>Provisioning<\/li>\n<li>Scaling<\/li>\n<li>Credential rotation<\/li>\n<li>Incident response<\/li>\n<li>Restore procedures<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Governance\/tagging\/naming best practices<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Naming conventions:<\/li>\n<li><code>env-app-purpose<\/code> (e.g., <code>prod-billing-atp<\/code>)<\/li>\n<li>Mandatory tags:<\/li>\n<li><code>Environment<\/code>, <code>Owner<\/code>, <code>CostCenter<\/code>, <code>DataClassification<\/code><\/li>\n<li>Use compartments as policy boundaries, not just folders.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">12. Security Considerations<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Identity and access model<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>OCI IAM<\/strong> controls management actions (create DBs, change network settings, delete resources).<\/li>\n<li><strong>Database users\/roles<\/strong> control data-plane access (schemas, tables, SQL execution).<\/li>\n<li>Implement separation of duties:<\/li>\n<li>OCI admins manage infrastructure.<\/li>\n<li>DB security admins manage privileged database accounts.<\/li>\n<li>App teams get least-privileged schema accounts.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Encryption<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Autonomous Database encrypts data at rest by default (TDE-based architecture in Oracle Database).<\/li>\n<li>Data in transit is protected with TLS; some connection models rely on wallets and mTLS.<\/li>\n<li>Customer-managed keys may be supported in some configurations\u2014verify in OCI docs and your region.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Network exposure<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Prefer private endpoint for production.<\/li>\n<li>If using public endpoint:<\/li>\n<li>Strict IP allowlists<\/li>\n<li>Review and rotate credentials regularly<\/li>\n<li>Monitor access patterns and failed logins<\/li>\n<li>Use NSGs and route controls in VCN designs for private access.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Secrets handling<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Do not store database passwords in source code or CI logs.<\/li>\n<li>Use a secrets manager pattern (often OCI Vault) and rotate credentials.<\/li>\n<li>Prefer per-application schema users; avoid shared \u201cglobal\u201d credentials.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Audit\/logging<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Use <strong>OCI Audit<\/strong> for control-plane actions.<\/li>\n<li>Enable database auditing appropriate to your compliance needs (database-native auditing configuration is a database design topic; verify best practices for your database version).<\/li>\n<li>Retain logs according to policy and protect audit logs from tampering.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Compliance considerations<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Dedicated infrastructure can help meet isolation requirements.<\/li>\n<li>Still validate:<\/li>\n<li>Data residency (region choice)<\/li>\n<li>Encryption requirements<\/li>\n<li>Access logging and retention<\/li>\n<li>DR location requirements (cross-region constraints)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Common security mistakes<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Leaving public endpoints open to broad IP ranges.<\/li>\n<li>Overusing <code>ADMIN<\/code> credentials for day-to-day access.<\/li>\n<li>Not separating dev\/test\/prod compartments.<\/li>\n<li>Not monitoring for unusual login activity or privilege escalation.<\/li>\n<li>Failing to rotate secrets and revoke access for departed staff.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Secure deployment recommendations<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Production: private endpoints + DR + strict IAM + Vault + budgets.<\/li>\n<li>Enforce tagging and compartment controls.<\/li>\n<li>Establish a privileged access management process for ADMIN-level access.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">13. Limitations and Gotchas<\/h2>\n\n\n\n<blockquote>\n<p>These are common realities for dedicated autonomous deployments. Always verify exact constraints in official docs and your tenancy policies.<\/p>\n<\/blockquote>\n\n\n\n<h3 class=\"wp-block-heading\">Known limitations \/ realities<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Dedicated is not \u201cquick and cheap\u201d<\/strong>: Requires dedicated platform provisioning and capacity planning.<\/li>\n<li><strong>Not full control<\/strong>: You do not manage the underlying host OS; Oracle manages many aspects.<\/li>\n<li><strong>Feature variance<\/strong>: Some database features\/options depend on database version, service policies, and region.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Quotas and capacity<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Provisioning can fail due to:<\/li>\n<li>Insufficient dedicated capacity<\/li>\n<li>Service limits in your region<\/li>\n<li>Compartment quota restrictions (org policy)<\/li>\n<li>Your team may need platform admin coordination for scaling.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Regional constraints<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Not all OCI regions offer the same dedicated autonomous capabilities.<\/li>\n<li>Cross-region DR options may be limited by region pair availability.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Pricing surprises<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>The biggest \u201csurprise\u201d is that <strong>dedicated infrastructure continues costing money<\/strong> even if you delete individual autonomous databases.<\/li>\n<li>DR\/standby architectures can significantly increase spend.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Compatibility issues<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Some legacy application behaviors may require:<\/li>\n<li>Specific connection methods<\/li>\n<li>Specific database parameters (which may be locked down in managed services)<\/li>\n<li>Migration tooling and compatibility should be assessed per workload.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Operational gotchas<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>IP allowlist issues for public endpoints when your ISP changes IP.<\/li>\n<li>Private endpoint access requires network planning (DNS, routes, NSGs).<\/li>\n<li>Overlapping responsibilities: OCI IAM vs database privileges can cause confusion unless documented.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Migration challenges<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Data migration needs planning:<\/li>\n<li>Data pump, replication, or migration services (tool choice depends on downtime constraints\u2014verify current OCI migration options).<\/li>\n<li>Performance tuning may shift due to Exadata behavior; load test and baseline.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Vendor-specific nuances<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Terminology includes \u201cAutonomous Exadata Infrastructure\u201d and \u201cAutonomous Container Database\u201d\u2014this is different from serverless\/shared Autonomous Database.<\/li>\n<li>Many operations are \u201cmanaged,\u201d which is a benefit, but also a constraint for teams used to OS-level access.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">14. Comparison with Alternatives<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Nearest services in Oracle Cloud<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Autonomous Database (serverless\/shared)<\/strong>: lower entry cost, faster provisioning; less isolation.<\/li>\n<li><strong>Exadata Database Service (Exadata Cloud Service)<\/strong>: more DBA control; less \u201cautonomous\u201d operational model.<\/li>\n<li><strong>Exadata Cloud@Customer<\/strong>: Exadata managed by Oracle but deployed in your data center (hybrid); different procurement and ops model.<\/li>\n<li><strong>OCI Base Database Service<\/strong>: more control, typically lower cost for smaller workloads, but more admin effort.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Nearest services in other clouds<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>AWS<\/strong>: Amazon Aurora, Amazon RDS for Oracle (managed Oracle), self-managed Oracle on EC2.<\/li>\n<li><strong>Azure<\/strong>: Azure SQL Database\/Managed Instance (different engine), Oracle on Azure VMs, Oracle Database@Azure (service offerings evolve\u2014verify).<\/li>\n<li><strong>Google Cloud<\/strong>: Cloud SQL (different engine), AlloyDB (PostgreSQL), Oracle on Compute Engine.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Open-source\/self-managed alternatives<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>PostgreSQL (managed or self-managed)<\/li>\n<li>MySQL (managed or self-managed)<\/li>\n<li>Self-managed Oracle Database on IaaS (full control, higher ops)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Comparison table<\/h3>\n\n\n\n<figure class=\"wp-block-table\"><table>\n<thead>\n<tr>\n<th>Option<\/th>\n<th>Best For<\/th>\n<th>Strengths<\/th>\n<th>Weaknesses<\/th>\n<th>When to Choose<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td><strong>Autonomous AI Database on Dedicated Exadata Infrastructure<\/strong> (Oracle Cloud)<\/td>\n<td>Regulated, mission-critical Oracle workloads needing dedicated isolation<\/td>\n<td>Dedicated Exadata performance, autonomous operations, strong governance model<\/td>\n<td>Higher baseline cost, less host-level control, requires capacity planning<\/td>\n<td>When you need autonomous + dedicated + Exadata and can justify dedicated spend<\/td>\n<\/tr>\n<tr>\n<td>Autonomous Database (serverless\/shared) (Oracle Cloud)<\/td>\n<td>Small-to-medium workloads, dev\/test, fast starts<\/td>\n<td>Lower entry cost, easy provisioning<\/td>\n<td>Shared infrastructure, less isolation<\/td>\n<td>When cost and simplicity matter more than dedicated isolation<\/td>\n<\/tr>\n<tr>\n<td>Exadata Database Service (Oracle Cloud)<\/td>\n<td>Teams needing Exadata but more DBA control<\/td>\n<td>High performance, more configuration control<\/td>\n<td>More operational burden vs autonomous<\/td>\n<td>When you need Exadata and DBAs want deeper control<\/td>\n<\/tr>\n<tr>\n<td>Base Database Service (Oracle Cloud)<\/td>\n<td>Traditional VM-based Oracle DB management<\/td>\n<td>Flexibility, familiar ops model<\/td>\n<td>More patching\/tuning responsibility<\/td>\n<td>When you need control and accept ops overhead<\/td>\n<\/tr>\n<tr>\n<td>Amazon Aurora \/ Azure SQL \/ AlloyDB<\/td>\n<td>Cloud-native apps not tied to Oracle<\/td>\n<td>Managed scale, simpler app patterns (depending)<\/td>\n<td>Not Oracle-compatible (migrations required)<\/td>\n<td>When you can move off Oracle and want managed open engines<\/td>\n<\/tr>\n<tr>\n<td>Self-managed Oracle on IaaS<\/td>\n<td>Specialized requirements<\/td>\n<td>Maximum control<\/td>\n<td>Maximum ops complexity<\/td>\n<td>When managed constraints block your requirements<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/figure>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">15. Real-World Example<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Enterprise example: regulated financial services consolidation<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem<\/strong><\/li>\n<li>Dozens of Oracle databases across business units with inconsistent patching, backups, and access controls.<\/li>\n<li>Compliance requires tenant isolation and strong auditability.<\/li>\n<li><strong>Proposed architecture<\/strong><\/li>\n<li>One or more <strong>Autonomous Exadata Infrastructure<\/strong> environments per regulatory boundary (e.g., prod vs non-prod).<\/li>\n<li>Multiple <strong>Autonomous Container Databases<\/strong> to segment workloads (as required).<\/li>\n<li>Autonomous databases provisioned per application domain.<\/li>\n<li>Private endpoints connected via VPN\/FastConnect to on-prem apps.<\/li>\n<li>Centralized monitoring and IAM governance, cost tagging, and budgets.<\/li>\n<li><strong>Why this service was chosen<\/strong><\/li>\n<li>Dedicated isolation for compliance.<\/li>\n<li>Autonomous operations reduce operational risk and inconsistent maintenance.<\/li>\n<li>Exadata performance supports mixed OLTP + reporting workloads.<\/li>\n<li><strong>Expected outcomes<\/strong><\/li>\n<li>Standardized patching\/backups, improved audit readiness.<\/li>\n<li>Reduced DBA toil and improved reliability.<\/li>\n<li>Better cost attribution via tagging and consolidated platform utilization.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Startup\/small-team example: enterprise-tier SaaS offering<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem<\/strong><\/li>\n<li>A SaaS company serves smaller customers on shared infrastructure, but new enterprise customers demand predictable performance and isolation.<\/li>\n<li><strong>Proposed architecture<\/strong><\/li>\n<li>Dedicated autonomous platform for \u201centerprise tier.\u201d<\/li>\n<li>Separate autonomous database per enterprise tenant (or per group of tenants) depending on data isolation requirements.<\/li>\n<li>Strict IAM controls; private endpoint access from application tier.<\/li>\n<li><strong>Why this service was chosen<\/strong><\/li>\n<li>Faster than building\/operating Exadata; still meets enterprise isolation expectations.<\/li>\n<li>Autonomous ops fits a small ops team.<\/li>\n<li><strong>Expected outcomes<\/strong><\/li>\n<li>Stronger enterprise posture, easier compliance discussions.<\/li>\n<li>Reduced performance variability.<\/li>\n<li>Clear segmentation between standard tier and enterprise tier.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">16. FAQ<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">1) Is \u201cAutonomous AI Database on Dedicated Exadata Infrastructure\u201d the same as Autonomous Database?<\/h3>\n\n\n\n<p>It refers to <strong>Autonomous Database<\/strong> deployed on <strong>Dedicated Exadata Infrastructure<\/strong>. In the console and many docs, you may primarily see \u201cAutonomous Database,\u201d with dedicated vs serverless\/shared as deployment choices. Verify the exact labels in your region.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">2) What is the difference between dedicated and serverless\/shared Autonomous Database?<\/h3>\n\n\n\n<p>Dedicated uses <strong>your reserved Exadata capacity<\/strong> (isolation and predictability). Serverless\/shared typically runs on shared infrastructure with lower entry cost and less isolation.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">3) Do I need to provision Exadata infrastructure before creating the database?<\/h3>\n\n\n\n<p>Yes, in the dedicated model you typically need <strong>Autonomous Exadata Infrastructure<\/strong> and an <strong>Autonomous Container Database<\/strong> available first (often provisioned by a platform team).<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">4) Can I use private networking only?<\/h3>\n\n\n\n<p>Yes, private endpoints are a common production pattern. You\u2019ll need VCN\/subnet planning and a connectivity path (VCN-local apps, VPN, FastConnect, etc.).<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">5) Can I use a public endpoint?<\/h3>\n\n\n\n<p>Often yes, with IP allowlisting and TLS\/mTLS requirements, but many enterprises restrict or forbid it. Follow your security policy.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">6) Who manages patching and backups?<\/h3>\n\n\n\n<p>Oracle manages key operational tasks under the autonomous model. You still manage schema design, users\/roles, and application behavior.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">7) Can I get OS-level access to the database host?<\/h3>\n\n\n\n<p>No, this is a managed service. If you require OS-level access, consider other Oracle database offerings.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">8) How do I control who can create or delete databases?<\/h3>\n\n\n\n<p>Use <strong>OCI IAM policies<\/strong> and compartments. Keep \u201cdelete\u201d permissions limited and require approvals.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">9) What tools can I use to connect?<\/h3>\n\n\n\n<p>Database Actions (web), SQL Developer\/SQLcl\/SQL*Plus depending on your organization\u2019s allowed tools and your connection model. Follow official connection docs.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">10) Does it support high availability?<\/h3>\n\n\n\n<p>Autonomous Database is designed with managed HA characteristics, but exact details and SLAs depend on the specific service and configuration. Verify HA\/DR documentation for dedicated deployments.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">11) Does it support disaster recovery across regions?<\/h3>\n\n\n\n<p>DR features and options vary. Check whether your deployment supports standby\/replication, region pairing constraints, and cost implications.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">12) How do I estimate cost accurately?<\/h3>\n\n\n\n<p>Use official OCI pricing pages and the OCI cost estimator for your region and contract model. Dedicated pricing is capacity-driven; avoid guessing.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">13) What is an Autonomous Container Database?<\/h3>\n\n\n\n<p>A container layer that hosts one or more autonomous databases on the dedicated platform. It\u2019s part of the dedicated deployment architecture.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">14) Can I run multiple application databases on one dedicated platform?<\/h3>\n\n\n\n<p>Yes. That\u2019s a major advantage: consolidate multiple autonomous databases under one governed dedicated environment (with careful capacity and security controls).<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">15) What is the most common beginner mistake?<\/h3>\n\n\n\n<p>Trying to learn dedicated autonomous without realizing that <strong>dedicated infrastructure is required first<\/strong> and continues to cost money even if you delete the individual database.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">16) How do I keep it secure for production?<\/h3>\n\n\n\n<p>Use private endpoints, least privilege IAM, secret management (Vault), strict database roles, and strong auditing\/logging with retention policies.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">17) Can I practice this without dedicated infrastructure?<\/h3>\n\n\n\n<p>You can learn many Autonomous Database concepts on serverless\/shared Autonomous Database, but dedicated-specific components (Exadata Infrastructure, Container Database) require dedicated capacity.<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">17. Top Online Resources to Learn Autonomous AI Database on Dedicated Exadata Infrastructure<\/h2>\n\n\n\n<figure class=\"wp-block-table\"><table>\n<thead>\n<tr>\n<th>Resource Type<\/th>\n<th>Name<\/th>\n<th>Why It Is Useful<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Official documentation<\/td>\n<td>OCI Autonomous Database Documentation<\/td>\n<td>Primary reference for provisioning, networking, security, and operations: https:\/\/docs.oracle.com\/en-us\/iaas\/autonomous-database\/<\/td>\n<\/tr>\n<tr>\n<td>Official documentation<\/td>\n<td>OCI Identity and Access Management (IAM) Documentation<\/td>\n<td>Required for correct policies and least privilege: https:\/\/docs.oracle.com\/en-us\/iaas\/Content\/Identity\/Concepts\/overview.htm<\/td>\n<\/tr>\n<tr>\n<td>Official pricing<\/td>\n<td>Oracle Cloud Pricing<\/td>\n<td>Official pricing entry point (region and SKU vary): https:\/\/www.oracle.com\/cloud\/pricing\/<\/td>\n<\/tr>\n<tr>\n<td>Official cost estimator<\/td>\n<td>OCI Cost Estimator<\/td>\n<td>Model dedicated vs non-dedicated costs (verify current URL): https:\/\/www.oracle.com\/cloud\/costestimator.html<\/td>\n<\/tr>\n<tr>\n<td>Official tutorials\/labs<\/td>\n<td>Oracle LiveLabs (search for Autonomous Database and Exadata labs)<\/td>\n<td>Hands-on labs maintained by Oracle (availability varies): https:\/\/livelabs.oracle.com\/<\/td>\n<\/tr>\n<tr>\n<td>Official architecture center<\/td>\n<td>Oracle Architecture Center<\/td>\n<td>Reference architectures and best practices: https:\/\/docs.oracle.com\/solutions\/<\/td>\n<\/tr>\n<tr>\n<td>Official videos<\/td>\n<td>Oracle Database \/ OCI YouTube channels (search Autonomous Database dedicated)<\/td>\n<td>Product walkthroughs and updates; confirm relevance to your release: https:\/\/www.youtube.com\/@Oracle<\/td>\n<\/tr>\n<tr>\n<td>Official service docs<\/td>\n<td>OCI Networking Documentation<\/td>\n<td>Private endpoints and VCN design depend on networking fundamentals: https:\/\/docs.oracle.com\/en-us\/iaas\/Content\/Network\/Concepts\/overview.htm<\/td>\n<\/tr>\n<tr>\n<td>Terraform provider docs<\/td>\n<td>OCI Terraform Provider Documentation<\/td>\n<td>Automate provisioning (verify exact resource fields for dedicated autonomous): https:\/\/registry.terraform.io\/providers\/oracle\/oci\/latest\/docs<\/td>\n<\/tr>\n<tr>\n<td>Community learning<\/td>\n<td>Oracle ACE \/ community blogs (select carefully)<\/td>\n<td>Can provide practical troubleshooting; validate against official docs before adopting in production<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/figure>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">18. Training and Certification Providers<\/h2>\n\n\n\n<figure class=\"wp-block-table\"><table>\n<thead>\n<tr>\n<th>Institute<\/th>\n<th>Suitable Audience<\/th>\n<th>Likely Learning Focus<\/th>\n<th>Mode<\/th>\n<th>Website<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>DevOpsSchool.com<\/td>\n<td>DevOps engineers, platform teams, cloud engineers<\/td>\n<td>OCI + DevOps practices, automation, operational readiness<\/td>\n<td>Check website<\/td>\n<td>https:\/\/www.devopsschool.com\/<\/td>\n<\/tr>\n<tr>\n<td>ScmGalaxy.com<\/td>\n<td>Beginners to intermediate IT professionals<\/td>\n<td>DevOps fundamentals, tooling, and process<\/td>\n<td>Check website<\/td>\n<td>https:\/\/www.scmgalaxy.com\/<\/td>\n<\/tr>\n<tr>\n<td>CLoudOpsNow.in<\/td>\n<td>Cloud ops and operations teams<\/td>\n<td>Cloud operations, monitoring, reliability practices<\/td>\n<td>Check website<\/td>\n<td>https:\/\/www.cloudopsnow.in\/<\/td>\n<\/tr>\n<tr>\n<td>SreSchool.com<\/td>\n<td>SREs, reliability engineers, ops leaders<\/td>\n<td>SRE practices, observability, incident response<\/td>\n<td>Check website<\/td>\n<td>https:\/\/www.sreschool.com\/<\/td>\n<\/tr>\n<tr>\n<td>AiOpsSchool.com<\/td>\n<td>Ops teams adopting automation<\/td>\n<td>AIOps concepts, monitoring automation<\/td>\n<td>Check website<\/td>\n<td>https:\/\/www.aiopsschool.com\/<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/figure>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">19. Top Trainers<\/h2>\n\n\n\n<figure class=\"wp-block-table\"><table>\n<thead>\n<tr>\n<th>Platform\/Site<\/th>\n<th>Likely Specialization<\/th>\n<th>Suitable Audience<\/th>\n<th>Website<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>RajeshKumar.xyz<\/td>\n<td>DevOps\/cloud training and guidance (verify offerings)<\/td>\n<td>Beginners to practitioners seeking guided learning<\/td>\n<td>https:\/\/rajeshkumar.xyz\/<\/td>\n<\/tr>\n<tr>\n<td>devopstrainer.in<\/td>\n<td>DevOps training and mentoring (verify offerings)<\/td>\n<td>Engineers seeking hands-on DevOps coaching<\/td>\n<td>https:\/\/www.devopstrainer.in\/<\/td>\n<\/tr>\n<tr>\n<td>devopsfreelancer.com<\/td>\n<td>Independent DevOps services\/training (verify offerings)<\/td>\n<td>Teams needing short-term help or coaching<\/td>\n<td>https:\/\/www.devopsfreelancer.com\/<\/td>\n<\/tr>\n<tr>\n<td>devopssupport.in<\/td>\n<td>DevOps support and enablement (verify offerings)<\/td>\n<td>Ops\/DevOps teams needing practical support<\/td>\n<td>https:\/\/www.devopssupport.in\/<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/figure>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">20. Top Consulting Companies<\/h2>\n\n\n\n<figure class=\"wp-block-table\"><table>\n<thead>\n<tr>\n<th>Company<\/th>\n<th>Likely Service Area<\/th>\n<th>Where They May Help<\/th>\n<th>Consulting Use Case Examples<\/th>\n<th>Website<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>cotocus.com<\/td>\n<td>Cloud\/DevOps consulting (verify specific OCI offerings)<\/td>\n<td>Architecture reviews, automation, operational processes<\/td>\n<td>Landing zone setup, IAM governance patterns, IaC pipelines<\/td>\n<td>https:\/\/cotocus.com\/<\/td>\n<\/tr>\n<tr>\n<td>DevOpsSchool.com<\/td>\n<td>DevOps consulting and enablement (verify offerings)<\/td>\n<td>Training + consulting for DevOps adoption<\/td>\n<td>CI\/CD design, platform runbooks, operational maturity<\/td>\n<td>https:\/\/www.devopsschool.com\/<\/td>\n<\/tr>\n<tr>\n<td>DEVOPSCONSULTING.IN<\/td>\n<td>DevOps consulting (verify offerings)<\/td>\n<td>Tooling, pipelines, reliability practices<\/td>\n<td>Observability stack setup, deployment automation, operational handover<\/td>\n<td>https:\/\/www.devopsconsulting.in\/<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/figure>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">21. Career and Learning Roadmap<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">What to learn before this service<\/h3>\n\n\n\n<p>To be effective with Autonomous AI Database on Dedicated Exadata Infrastructure, learn:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>OCI fundamentals<\/strong>\n   &#8211; Tenancy, compartments, IAM policies, tagging<\/li>\n<li><strong>Networking<\/strong>\n   &#8211; VCNs, subnets, NSGs, routing, private connectivity (VPN\/FastConnect concepts)<\/li>\n<li><strong>Oracle Database fundamentals<\/strong>\n   &#8211; Users\/roles, tablespaces concepts (as applicable), indexing, SQL performance basics<\/li>\n<li><strong>Security basics<\/strong>\n   &#8211; Least privilege, secret management, audit logging, encryption concepts<\/li>\n<li><strong>Operations basics<\/strong>\n   &#8211; Monitoring\/alerting, incident response, backup\/restore concepts<\/li>\n<\/ol>\n\n\n\n<h3 class=\"wp-block-heading\">What to learn after this service<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>DR and business continuity patterns for Oracle workloads (verify service-specific DR capabilities)<\/li>\n<li>Terraform automation for OCI database provisioning and governance<\/li>\n<li>Observability at scale (dashboards, alarms, SLOs)<\/li>\n<li>Data governance tooling (classification, masking, auditing) aligned to your org\u2019s compliance requirements<\/li>\n<li>Application modernization patterns (connection pooling, retry logic, zero-downtime migrations)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Job roles that use it<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Cloud Solution Architect (OCI)<\/li>\n<li>Database Platform Engineer<\/li>\n<li>Cloud\/DevOps Engineer supporting data platforms<\/li>\n<li>SRE (data platform reliability)<\/li>\n<li>Security Engineer focusing on cloud data stores<\/li>\n<li>Data Platform Product Owner \/ Technical Program Manager<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Certification path (if available)<\/h3>\n\n\n\n<p>Oracle certification offerings change over time. Start here and select OCI and database tracks relevant to Autonomous Database:\n&#8211; https:\/\/education.oracle.com\/ (verify current OCI certification paths and names)<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Project ideas for practice<\/h3>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Build a \u201cdatabase factory\u201d design:\n   &#8211; compartments, policies, tags, naming<\/li>\n<li>Create a standardized onboarding runbook:\n   &#8211; request \u2192 approve \u2192 provision \u2192 monitor \u2192 rotate secrets<\/li>\n<li>Implement private endpoint connectivity pattern:\n   &#8211; VCN + app tier + ADB private endpoint + Bastion<\/li>\n<li>Create cost governance:\n   &#8211; budgets, tag enforcement (where available), monthly reporting<\/li>\n<li>Create performance baseline:\n   &#8211; run representative queries, capture metrics, define alarms<\/li>\n<\/ol>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">22. Glossary<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>ADB (Autonomous Database)<\/strong>: Oracle-managed database service with automation for provisioning, tuning, backups, and patching.<\/li>\n<li><strong>Autonomous Exadata Infrastructure<\/strong>: Dedicated Exadata capacity in OCI reserved for your tenancy.<\/li>\n<li><strong>Autonomous Container Database (ACD)<\/strong>: Container layer that hosts autonomous databases on dedicated infrastructure.<\/li>\n<li><strong>Compartment<\/strong>: OCI logical container used for organizing resources and applying IAM policies.<\/li>\n<li><strong>Dedicated Exadata Infrastructure<\/strong>: Exadata resources isolated for a single customer tenancy.<\/li>\n<li><strong>IAM Policy<\/strong>: OCI authorization rule defining who can manage which resources in which compartments.<\/li>\n<li><strong>IP Allowlist<\/strong>: Network control restricting inbound connections to specific public IP addresses.<\/li>\n<li><strong>mTLS<\/strong>: Mutual TLS; both client and server authenticate using certificates (common in some database secure connection models).<\/li>\n<li><strong>NSG (Network Security Group)<\/strong>: Virtual firewall for VNICs\/resources in OCI VCNs.<\/li>\n<li><strong>OCPU<\/strong>: Oracle CPU unit used for OCI compute\/database billing dimensions.<\/li>\n<li><strong>OCI Audit<\/strong>: Service that records OCI control-plane API calls and actions.<\/li>\n<li><strong>Private Endpoint<\/strong>: Database endpoint with private IP in a subnet, reachable only via private networking paths.<\/li>\n<li><strong>Public Endpoint<\/strong>: Database endpoint reachable over the public internet (secured by TLS and allowlists).<\/li>\n<li><strong>VCN<\/strong>: Virtual Cloud Network; OCI\u2019s private network construct.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">23. Summary<\/h2>\n\n\n\n<p>Autonomous AI Database on Dedicated Exadata Infrastructure (Oracle Cloud, Data Management) is <strong>Oracle Autonomous Database deployed on dedicated Exadata capacity<\/strong>, designed for organizations that need <strong>autonomous operations plus dedicated isolation and predictable performance<\/strong>.<\/p>\n\n\n\n<p>It fits best for <strong>mission-critical, regulated, and high-scale<\/strong> Oracle workloads where shared infrastructure is not acceptable. The key cost reality is that <strong>dedicated infrastructure introduces a baseline commitment<\/strong>, so strong consolidation, tagging, and budgeting practices matter. From a security standpoint, prefer <strong>private endpoints<\/strong>, enforce least privilege with OCI IAM, manage secrets properly, and build audit\/monitoring into your standard operating model.<\/p>\n\n\n\n<p>Next step: review the official Autonomous Database documentation and run an Oracle LiveLabs lab focused on Autonomous Database connectivity and operations, then align your deployment model (public\/private endpoint, DR requirements, and governance) with your organization\u2019s policies:\n&#8211; https:\/\/docs.oracle.com\/en-us\/iaas\/autonomous-database\/\n&#8211; https:\/\/livelabs.oracle.com\/<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Data Management<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[68,62],"tags":[],"class_list":["post-878","post","type-post","status-publish","format-standard","hentry","category-data-management","category-oracle-cloud"],"_links":{"self":[{"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/posts\/878","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/comments?post=878"}],"version-history":[{"count":0,"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/posts\/878\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/media?parent=878"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/categories?post=878"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/tags?post=878"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}