{"id":879,"date":"2026-04-16T12:57:36","date_gmt":"2026-04-16T12:57:36","guid":{"rendered":"https:\/\/www.devopsschool.com\/tutorials\/oracle-cloud-autonomous-ai-database-on-exadata-cloud-customer-tutorial-architecture-pricing-use-cases-and-hands-on-guide-for-data-management\/"},"modified":"2026-04-16T12:57:36","modified_gmt":"2026-04-16T12:57:36","slug":"oracle-cloud-autonomous-ai-database-on-exadata-cloud-customer-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-exadata-cloud-customer-tutorial-architecture-pricing-use-cases-and-hands-on-guide-for-data-management\/","title":{"rendered":"Oracle Cloud Autonomous AI Database on Exadata Cloud@Customer 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>Autonomous AI Database on Exadata Cloud@Customer is an Oracle Cloud <strong>Data Management<\/strong> service that delivers Oracle Autonomous Database capabilities on <strong>Exadata Cloud@Customer infrastructure deployed in your data center<\/strong> (or a customer-controlled facility), while still being managed and metered through Oracle Cloud Infrastructure (OCI).<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Simple explanation (one paragraph)<\/h3>\n\n\n\n<p>It is a managed Oracle database service that runs on Exadata hardware in your own environment. You get many of the automation benefits associated with Autonomous Database (provisioning workflows, patching\/maintenance automation, backups, scaling options, and OCI integration) while keeping the database physically on-premises for latency, residency, or regulatory reasons.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Technical explanation (one paragraph)<\/h3>\n\n\n\n<p>Conceptually, this service combines: (1) <strong>Exadata Cloud@Customer<\/strong> (Exadata infrastructure installed in your data center and managed as a cloud service) with (2) <strong>Autonomous Database (Dedicated)<\/strong> style constructs (such as Exadata infrastructure resources, VM clusters, Autonomous Container Databases, and Autonomous Databases) managed via OCI control plane APIs and the OCI Console. Data plane traffic (SQL*Net\/TCPS) stays within your network, while the control plane (provisioning, lifecycle, metering) integrates with OCI tenancy, compartments, IAM, audit, and monitoring.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">What problem it solves<\/h3>\n\n\n\n<p>Many organizations want the automation, patching discipline, and operational consistency of a managed database service, but cannot place sensitive databases in a public cloud region due to <strong>data sovereignty<\/strong>, <strong>low-latency<\/strong>, <strong>legacy connectivity<\/strong>, or <strong>regulatory<\/strong> requirements. Autonomous AI Database on Exadata Cloud@Customer addresses this by bringing the service to your environment while retaining cloud management patterns.<\/p>\n\n\n\n<blockquote>\n<p>Naming note (verify in official docs): Oracle documentation commonly uses terms like <strong>\u201cAutonomous Database on Exadata Cloud@Customer\u201d<\/strong> and <strong>\u201cAutonomous Database Dedicated\u201d<\/strong> for the underlying architecture and APIs. The phrase <strong>\u201cAutonomous AI Database\u201d<\/strong> is used in Oracle marketing to highlight AI-era database capabilities (for example, Oracle Database releases branded with \u201cAI\u201d). Always verify the exact OCI Console labels and API resource names in your tenancy and current Oracle docs.<\/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 Exadata Cloud@Customer?<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Official purpose<\/h3>\n\n\n\n<p>Autonomous AI Database on Exadata Cloud@Customer is intended to provide a <strong>managed, automated Oracle database service<\/strong> on Exadata infrastructure that resides <strong>at the customer site<\/strong>, with centralized governance and metering through <strong>Oracle Cloud<\/strong>.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Core capabilities (what you should expect)<\/h3>\n\n\n\n<p>While exact capabilities depend on your contract, deployment configuration, and database version (verify in official docs), the service is designed around:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Autonomous provisioning workflows<\/strong> for databases on dedicated Exadata capacity.<\/li>\n<li><strong>Automation for database lifecycle operations<\/strong> (patching\/maintenance orchestration, backups, scaling\/config changes based on allowed parameters).<\/li>\n<li><strong>Performance and consolidation<\/strong> benefits of Exadata (optimized storage, high throughput, offload capabilities\u2014exact features depend on Exadata generation and configuration).<\/li>\n<li><strong>OCI-native governance<\/strong>: compartments, IAM policies, audit trails, tagging, and integrations with OCI monitoring\/logging patterns.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Major components (typical resource model)<\/h3>\n\n\n\n<p>In many deployments, the resource hierarchy aligns with Autonomous Database Dedicated patterns:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Tenancy \/ Compartments<\/strong> (OCI governance boundary)<\/li>\n<li><strong>Exadata Cloud@Customer Infrastructure<\/strong> (physical Exadata system deployed on-prem)<\/li>\n<li><strong>(Autonomous) Exadata VM Cluster<\/strong> (compute virtualization layer on Exadata)<\/li>\n<li><strong>Autonomous Container Database (ACD)<\/strong> (container for Autonomous Databases)<\/li>\n<li><strong>Autonomous Database<\/strong> (the database instance you connect to; workload type depends on what\u2019s enabled)<\/li>\n<\/ul>\n\n\n\n<blockquote>\n<p>Verify in official docs: Oracle uses specific naming in the OCI Console and APIs (for example \u201cAutonomous Exadata VM Cluster\u201d and \u201cAutonomous Container Database\u201d). These names and availability may vary by service generation.<\/p>\n<\/blockquote>\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<\/strong> (Oracle-managed control plane + customer-site data plane)<\/li>\n<li><strong>Dedicated infrastructure<\/strong> model (built on Exadata Cloud@Customer rather than shared\/serverless multi-tenant infrastructure)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Scope (regional\/global\/zonal)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Control plane scope:<\/strong> Managed through an OCI tenancy and compartments (account\/tenancy-scoped governance).<\/li>\n<li><strong>Data plane location:<\/strong> Runs on Exadata systems deployed in your facility (customer site).<\/li>\n<li><strong>\u201cRegion\u201d behavior:<\/strong> Your Exadata Cloud@Customer deployment is still associated with an OCI region\/tenancy for management, identity, billing, and APIs. Exact region mapping and availability should be confirmed in the Exadata Cloud@Customer documentation and your Oracle order form.<\/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 Exadata Cloud@Customer sits within Oracle Cloud\u2019s database portfolio alongside:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Autonomous Database (shared\/serverless in OCI public regions)<\/strong><\/li>\n<li><strong>Autonomous Database Dedicated (OCI public regions on dedicated Exadata)<\/strong><\/li>\n<li><strong>Exadata Database Service<\/strong> (Oracle databases managed on Exadata, typically more DBA-controlled than Autonomous)<\/li>\n<li><strong>Base Database Service \/ Oracle Database on Compute<\/strong> (more self-managed)<\/li>\n<\/ul>\n\n\n\n<p>It is particularly relevant when you want OCI-style IAM, auditing, tagging, automation, and API-driven operations while meeting on-prem requirements.<\/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 Exadata Cloud@Customer?<\/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>Data residency and sovereignty:<\/strong> Keep sensitive datasets physically in your environment.<\/li>\n<li><strong>Reduce operational burden:<\/strong> Shift routine operations (patching orchestration, backups, lifecycle tasks) to managed service workflows.<\/li>\n<li><strong>Standardize governance:<\/strong> Use OCI IAM, compartments, and audit for centralized control.<\/li>\n<li><strong>Support modernization without forcing a full cloud move:<\/strong> Adopt cloud operating model while maintaining on-prem footprint.<\/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>Low-latency access to on-prem applications:<\/strong> Particularly for ERP\/legacy systems or manufacturing systems that cannot tolerate WAN latency.<\/li>\n<li><strong>Exadata-optimized performance:<\/strong> High throughput storage, database-aware optimizations, and consolidation on engineered systems (specific features depend on configuration).<\/li>\n<li><strong>API-driven provisioning and management:<\/strong> Automate via OCI Console\/CLI\/SDK\/Terraform (availability depends on your environment and permissions).<\/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>Consistent lifecycle management:<\/strong> Repeatable provisioning, standardized backup\/restore patterns, predictable maintenance scheduling (subject to your configuration).<\/li>\n<li><strong>Centralized monitoring and auditing:<\/strong> Integrate with OCI Monitoring, Events, and Audit.<\/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>Private network access:<\/strong> Databases can be reachable only over private networks (recommended).<\/li>\n<li><strong>Separation of duties:<\/strong> IAM policies can separate \u201cdatabase provisioning admins\u201d from \u201cdatabase users\u201d.<\/li>\n<li><strong>Auditability:<\/strong> OCI Audit records many control plane actions.<\/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>Scale within the dedicated Exadata capacity:<\/strong> Increase database compute\/storage (within service limits and hardware capacity).<\/li>\n<li><strong>Consolidate multiple databases:<\/strong> Use one engineered system to host multiple Autonomous Databases with consistent policies.<\/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 Exadata Cloud@Customer when:\n&#8211; You need <strong>on-prem data location<\/strong> but want <strong>managed database automation<\/strong>.\n&#8211; You already standardized on Oracle Database and require <strong>Exadata-class performance<\/strong>.\n&#8211; You have strict regulatory constraints preventing public cloud database hosting.\n&#8211; You want OCI governance (IAM\/compartments\/audit) for on-prem databases.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">When teams should not choose it<\/h3>\n\n\n\n<p>Avoid (or reconsider) if:\n&#8211; You want a <strong>low-cost entry<\/strong> or quick dev\/test without enterprise procurement\u2014Cloud@Customer requires dedicated infrastructure and commercial commitments.\n&#8211; You do not need Oracle Database\u2013specific capabilities and can use a simpler managed database (PostgreSQL\/MySQL) in a public cloud.\n&#8211; Your organization cannot support the on-prem requirements (space, power, cooling, network, change management) of Exadata hardware deployment.\n&#8211; You need full OS-level control and bespoke database configurations that conflict with the Autonomous managed model (verify the allowed customization boundaries).<\/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 Exadata Cloud@Customer used?<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Industries<\/h3>\n\n\n\n<p>Commonly adopted in industries with strong governance and data locality requirements:\n&#8211; Financial services (banking, payments, trading)\n&#8211; Healthcare and life sciences\n&#8211; Government and public sector\n&#8211; Telecommunications\n&#8211; Manufacturing and industrial IoT\n&#8211; Retail (especially where point-of-sale or supply chain is on-prem)\n&#8211; Energy and utilities<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Team types<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Platform engineering teams building internal database platforms<\/li>\n<li>Central DBA teams modernizing operations<\/li>\n<li>Security and compliance teams enforcing data locality<\/li>\n<li>SRE\/operations teams standardizing monitoring and lifecycle<\/li>\n<li>Application teams needing managed Oracle databases near on-prem apps<\/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>OLTP and line-of-business applications (ERP\/CRM\/billing)<\/li>\n<li>Data warehousing and analytics close to on-prem data sources<\/li>\n<li>Mixed workloads where separation is needed (verify supported workload types)<\/li>\n<li>Regulated workloads requiring strict audit trails<\/li>\n<li>Migration staging platforms (on-prem to OCI public regions, or hybrid)<\/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>Hybrid application stacks: on-prem app tier + on-prem database managed via OCI<\/li>\n<li>Data hub architectures: consolidating multiple Oracle databases onto Exadata<\/li>\n<li>Disaster recovery designs using on-prem + OCI region (DR approach depends on your licensing and service support\u2014verify)<\/li>\n<li>Secure zones with no internet-exposed database endpoints<\/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>Customer data center deployments with dedicated network links to OCI (VPN\/FastConnect, depending on design)<\/li>\n<li>Customer-controlled colocation sites<\/li>\n<li>Dedicated secure facilities for regulated workloads<\/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> Common, because the value proposition is strongest for mission-critical databases.<\/li>\n<li><strong>Dev\/test:<\/strong> Possible, but many teams use smaller Autonomous Databases on OCI public regions for dev\/test and reserve Cloud@Customer for prod due to cost and operational overhead.<\/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 Exadata Cloud@Customer fits well.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">1) Regulated customer data platform on-prem<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> Regulations require sensitive customer PII to remain on-premises.<\/li>\n<li><strong>Why this service fits:<\/strong> Keeps data local while adopting managed database operations and governance via Oracle Cloud.<\/li>\n<li><strong>Example:<\/strong> A bank stores customer profiles and transaction metadata on Exadata Cloud@Customer and uses OCI IAM\/audit for centralized control.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">2) Low-latency ERP database for on-prem ERP application<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> ERP application servers are on-prem and latency to a public region is unacceptable.<\/li>\n<li><strong>Why this service fits:<\/strong> Database stays on-prem with engineered performance and automated operations.<\/li>\n<li><strong>Example:<\/strong> Manufacturing ERP runs in an on-prem VMware cluster, connects to Autonomous Database on the local Exadata Cloud@Customer.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">3) Database consolidation and standardization<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> Hundreds of Oracle databases spread across servers cause patching drift and high operational cost.<\/li>\n<li><strong>Why this service fits:<\/strong> Consolidate onto Exadata and manage provisioning and lifecycle consistently.<\/li>\n<li><strong>Example:<\/strong> A telecom consolidates departmental Oracle databases into a governed set of Autonomous Databases with standardized backup policies.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">4) Secure analytics hub for on-prem data sources<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> Data sources are on-prem and cannot be moved; analytics needs fast ingestion.<\/li>\n<li><strong>Why this service fits:<\/strong> Exadata performance and proximity reduce data movement; managed operations reduce DBA toil.<\/li>\n<li><strong>Example:<\/strong> Utility company ingests smart meter data into an on-prem Autonomous data warehouse environment (verify supported workload type).<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">5) Hybrid modernization with phased migration<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> You want to migrate to cloud gradually without a \u201cbig bang\u201d cutover.<\/li>\n<li><strong>Why this service fits:<\/strong> Establish OCI-style governance and APIs now, keep data on-prem, later replicate\/migrate to OCI region.<\/li>\n<li><strong>Example:<\/strong> Retailer runs the database on Exadata Cloud@Customer while modernizing app tier; later moves read replicas\/reporting to OCI (verify supported replication options).<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">6) High-performance batch processing close to on-prem systems<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> Nightly batch jobs depend on local systems and large data volumes.<\/li>\n<li><strong>Why this service fits:<\/strong> High throughput and reduced network dependency.<\/li>\n<li><strong>Example:<\/strong> Insurance firm runs premium recalculation batches on the on-prem Autonomous Database environment.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">7) Security-controlled enclave deployment<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> Security policy prohibits database endpoints from being internet-accessible.<\/li>\n<li><strong>Why this service fits:<\/strong> Private networking model; integrate with strict segmentation and on-prem security controls.<\/li>\n<li><strong>Example:<\/strong> Government agency uses a segmented network zone; only application subnets can reach the database over private IPs.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">8) DR \/ business continuity with strict RTO\/RPO targets<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> Need high availability and disaster recovery with predictable targets.<\/li>\n<li><strong>Why this service fits:<\/strong> Exadata capabilities + managed backups and structured operations can support BC designs.<\/li>\n<li><strong>Example:<\/strong> A financial institution keeps primary databases on Exadata Cloud@Customer and designs DR to another site\/region (exact DR patterns must be verified).<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">9) Internal database platform (DBaaS) for multiple teams<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> Teams need fast database provisioning without granting broad DBA privileges.<\/li>\n<li><strong>Why this service fits:<\/strong> Use OCI compartments, policies, and resource quotas to create a governed self-service model.<\/li>\n<li><strong>Example:<\/strong> Platform team offers \u201cdatabase request\u201d workflows using OCI APIs; teams receive isolated Autonomous Databases.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">10) Data sovereignty for multinational deployments<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> Data must remain within a country or facility boundary, but operations must be centralized.<\/li>\n<li><strong>Why this service fits:<\/strong> On-prem location + centralized cloud control plane.<\/li>\n<li><strong>Example:<\/strong> Multinational firm deploys Exadata Cloud@Customer in-country and manages it under a central OCI tenancy.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">11) Performance-sensitive OLTP with predictable cost envelope<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> OLTP workload requires consistent performance and capacity planning.<\/li>\n<li><strong>Why this service fits:<\/strong> Dedicated Exadata capacity; scaling and consolidation with governance.<\/li>\n<li><strong>Example:<\/strong> Payments processor runs core OLTP on on-prem Exadata with Autonomous operations.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">12) Legacy Oracle ecosystem integration<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> Many Oracle-dependent integrations (tools, drivers, stored procedures) must remain intact.<\/li>\n<li><strong>Why this service fits:<\/strong> Minimal app rewrites; managed lifecycle reduces operational risk.<\/li>\n<li><strong>Example:<\/strong> Existing Oracle-based applications migrate from self-managed Oracle DB servers to Autonomous on Exadata Cloud@Customer.<\/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>Important: Feature availability can vary by deployment and service configuration. Always verify in the official Oracle docs and in your OCI Console for the exact options available for <strong>Autonomous AI Database on Exadata Cloud@Customer<\/strong>.<\/p>\n<\/blockquote>\n\n\n\n<h3 class=\"wp-block-heading\">1) Dedicated Exadata Cloud@Customer deployment (customer-site)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does:<\/strong> Runs the database on Exadata hardware installed at your location.<\/li>\n<li><strong>Why it matters:<\/strong> Meets data residency and low-latency requirements.<\/li>\n<li><strong>Practical benefit:<\/strong> Keep sensitive data in your facility while adopting cloud-style operations.<\/li>\n<li><strong>Caveats:<\/strong> Requires on-prem readiness (space, power, cooling, network) and commercial agreement.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">2) OCI Console \/ API-driven lifecycle management<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does:<\/strong> Enables create\/update\/scale\/terminate operations using OCI Console, CLI, SDKs, and (often) Terraform.<\/li>\n<li><strong>Why it matters:<\/strong> Makes operations repeatable and automatable.<\/li>\n<li><strong>Practical benefit:<\/strong> Integrate provisioning into CI\/CD or platform workflows.<\/li>\n<li><strong>Caveats:<\/strong> Some deep configuration changes may be restricted compared with self-managed databases.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">3) Compartment-based governance and tagging<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does:<\/strong> Uses OCI compartments for isolation and IAM scoping; tags for cost allocation and governance.<\/li>\n<li><strong>Why it matters:<\/strong> Prevents uncontrolled sprawl and supports multi-team operations.<\/li>\n<li><strong>Practical benefit:<\/strong> Chargeback\/showback, policy enforcement, and clean ownership boundaries.<\/li>\n<li><strong>Caveats:<\/strong> Requires disciplined tenancy design (naming, tagging, and policy standards).<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">4) IAM-based access control (control plane)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does:<\/strong> Controls who can manage infrastructure and databases through OCI IAM policies.<\/li>\n<li><strong>Why it matters:<\/strong> Enables separation of duties and least privilege.<\/li>\n<li><strong>Practical benefit:<\/strong> Different roles for infra admins, DB lifecycle operators, and auditors.<\/li>\n<li><strong>Caveats:<\/strong> IAM controls the OCI resource actions; database user privileges still apply inside the database.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">5) Automated backups (service-managed patterns)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does:<\/strong> Provides managed backup scheduling and retention options (exact choices vary).<\/li>\n<li><strong>Why it matters:<\/strong> Backups are non-negotiable for recovery readiness.<\/li>\n<li><strong>Practical benefit:<\/strong> Standardized backups without bespoke scripting.<\/li>\n<li><strong>Caveats:<\/strong> Understand restore boundaries, retention, and where backups are stored (local vs OCI\/Object Storage) \u2014 verify in docs and your environment.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">6) Patching and maintenance orchestration<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does:<\/strong> Orchestrates patching\/maintenance as part of the managed service model.<\/li>\n<li><strong>Why it matters:<\/strong> Reduces security exposure from patch lag and configuration drift.<\/li>\n<li><strong>Practical benefit:<\/strong> More predictable, governed patch cycles.<\/li>\n<li><strong>Caveats:<\/strong> Maintenance windows and scheduling options vary; confirm operational expectations and blackout procedures in your service terms.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">7) Scaling within available Exadata capacity<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does:<\/strong> Allows scaling of database resources (compute and\/or storage) within configured limits and available capacity.<\/li>\n<li><strong>Why it matters:<\/strong> Handles growth without forklift migrations.<\/li>\n<li><strong>Practical benefit:<\/strong> Faster response to workload changes.<\/li>\n<li><strong>Caveats:<\/strong> Scaling is bounded by hardware capacity, service quotas, and enabled features.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">8) Private endpoint connectivity (recommended)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does:<\/strong> Supports private network connectivity to databases (common for Cloud@Customer designs).<\/li>\n<li><strong>Why it matters:<\/strong> Reduces attack surface by avoiding public exposure.<\/li>\n<li><strong>Practical benefit:<\/strong> Databases are reachable only from approved subnets\/segments.<\/li>\n<li><strong>Caveats:<\/strong> Requires correct DNS, routing, and firewall policies; client connectivity must be planned.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">9) Exadata performance characteristics<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does:<\/strong> Leverages Exadata\u2019s engineered system architecture for database workloads.<\/li>\n<li><strong>Why it matters:<\/strong> Supports demanding workloads and consolidation with predictable performance.<\/li>\n<li><strong>Practical benefit:<\/strong> High throughput, optimized IO paths, and database-aware optimizations (exact capabilities depend on configuration).<\/li>\n<li><strong>Caveats:<\/strong> Don\u2019t assume every Exadata feature is automatically enabled for every workload; verify.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">10) Observability via OCI (metrics, audit, events)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>What it does:<\/strong> Uses OCI Monitoring for metrics, OCI Audit for control plane logs, OCI Events for automation triggers (availability varies).<\/li>\n<li><strong>Why it matters:<\/strong> Enables SRE-grade operations and traceability.<\/li>\n<li><strong>Practical benefit:<\/strong> Alerts on health and capacity signals; audit who changed what.<\/li>\n<li><strong>Caveats:<\/strong> Database-level logs\/diagnostics may require additional configuration or services (verify).<\/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 architecture<\/h3>\n\n\n\n<p>Autonomous AI Database on Exadata Cloud@Customer is best understood as <strong>two planes<\/strong>:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Data plane:<\/strong> SQL client connections from your applications\/tools to the database endpoints in your on-prem network (often over TCPS with wallets\/certificates).<\/li>\n<li><strong>Control plane:<\/strong> OCI-managed APIs and Console operations that create, patch, backup, and govern the database resources using OCI IAM, compartments, and audit logs.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Request\/data\/control flow (typical)<\/h3>\n\n\n\n<ol class=\"wp-block-list\">\n<li>An admin uses OCI Console\/CLI to create or manage an Autonomous Database resource.<\/li>\n<li>OCI control plane validates permissions via IAM policy and records actions in Audit logs.<\/li>\n<li>The service orchestrates changes on Exadata Cloud@Customer infrastructure (VM clusters, ACDs, ADBs).<\/li>\n<li>Application clients connect to the database using private networking and Oracle Net services (typically TCPS with a wallet).<\/li>\n<li>Monitoring systems query OCI metrics and logs for operational visibility.<\/li>\n<\/ol>\n\n\n\n<h3 class=\"wp-block-heading\">Integrations with related Oracle Cloud services (common patterns)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>OCI Identity and Access Management (IAM):<\/strong> policies, groups, dynamic groups (where applicable)<\/li>\n<li><strong>OCI Audit:<\/strong> records control plane calls<\/li>\n<li><strong>OCI Monitoring &amp; Alarms:<\/strong> metrics + alerting<\/li>\n<li><strong>OCI Events:<\/strong> event-driven automation (verify event types for your resources)<\/li>\n<li><strong>OCI Vault:<\/strong> key management and secrets (where integrated\/required)<\/li>\n<li><strong>OCI Networking:<\/strong> VCNs\/subnets\/route tables\/security lists\/NSGs<\/li>\n<li><strong>Oracle Cloud Observability &amp; Management services:<\/strong> such as Database Management \/ Operations Insights (availability depends on licensing and service enablement\u2014verify)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Dependency services<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>OCI tenancy and compartments<\/li>\n<li>Exadata Cloud@Customer infrastructure installed and onboarded to tenancy<\/li>\n<li>Networking (on-prem and OCI management connectivity per Oracle requirements)<\/li>\n<li>DNS and certificate\/wallet distribution for client connectivity<\/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>Control plane auth:<\/strong> OCI IAM (users, groups, policies; optionally federation).<\/li>\n<li><strong>Database auth:<\/strong> Oracle database users\/roles (and potentially integration with enterprise identity via supported mechanisms\u2014verify).<\/li>\n<li><strong>Network security:<\/strong> private subnets, NSGs\/security lists, firewalls, segmentation.<\/li>\n<li><strong>Encryption:<\/strong> typically at-rest and in-transit, with details depending on configuration and key management choices (verify).<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Networking model (typical)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Application subnets in your data center route to the database private IPs on Exadata Cloud@Customer.<\/li>\n<li>Management\/control connectivity exists between your environment and OCI control plane per Oracle Cloud@Customer design.<\/li>\n<li>Public exposure is generally avoided; use bastions\/jump hosts if needed.<\/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 compartments to separate environments (prod\/dev\/test).<\/li>\n<li>Use tags for cost center and owner.<\/li>\n<li>Use alarms on capacity and availability signals.<\/li>\n<li>Integrate Audit logs into your SIEM.<\/li>\n<\/ul>\n\n\n\n<h4 class=\"wp-block-heading\">Simple architecture diagram (Mermaid)<\/h4>\n\n\n\n<pre><code class=\"language-mermaid\">flowchart LR\n  Admin[Admin \/ Platform Engineer] --&gt;|OCI Console \/ CLI| OCI[OCI Control Plane\\n(IAM, Audit, APIs)]\n  OCI --&gt;|Provision \/ Lifecycle| ExaCC[Exadata Cloud@Customer\\n(on-prem)]\n  App[On-prem App Tier] --&gt;|TCPS\/SQL*Net| ADB[Autonomous AI Database\\non Exadata Cloud@Customer]\n  ADB --- ExaCC\n  OCI --&gt; Mon[OCI Monitoring \/ Alarms]\n  OCI --&gt; Audit[OCI Audit Logs]\n<\/code><\/pre>\n\n\n\n<h4 class=\"wp-block-heading\">Production-style architecture diagram (Mermaid)<\/h4>\n\n\n\n<pre><code class=\"language-mermaid\">flowchart TB\n  subgraph OnPrem[\"Customer Data Center \/ Customer-Controlled Facility\"]\n    subgraph Net[\"Network Segments\"]\n      AppSub[\"App Subnet(s)\"]\n      ToolsSub[\"Admin\/Tools Subnet\"]\n      Jump[\"Bastion \/ Jump Host\\n(optional)\"]\n    end\n\n    subgraph Exa[\"Exadata Cloud@Customer\"]\n      VMClus[\"Autonomous VM Cluster\"]\n      ACD[\"Autonomous Container Database\"]\n      ADB1[\"Autonomous Database (Prod)\"]\n      ADB2[\"Autonomous Database (Analytics)\"]\n      VMClus --&gt; ACD --&gt; ADB1\n      ACD --&gt; ADB2\n    end\n\n    App[\"Application Services\"] --&gt;|Private TCPS| ADB1\n    Tools[\"SQL Clients \/ Automation\"] --&gt; Jump --&gt;|Private TCPS| ADB1\n    Tools --&gt; Jump --&gt;|Private TCPS| ADB2\n  end\n\n  subgraph OCI[\"Oracle Cloud (OCI Tenancy)\"]\n    IAM[\"IAM (Users, Groups, Policies)\"]\n    Audit[\"Audit\"]\n    Mon[\"Monitoring &amp; Alarms\"]\n    Events[\"Events (optional)\"]\n    Vault[\"Vault (keys\/secrets, if used)\"]\n  end\n\n  Tools --&gt;|API calls| IAM\n  IAM --&gt; Audit\n  IAM --&gt; Mon\n  IAM --&gt; Events\n  Vault -. keys\/policies .- IAM\n\n  OCI --&gt;|Control plane orchestration| Exa\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<p>Because this is a Cloud@Customer service, the \u201cprerequisites\u201d are more substantial than a typical public-cloud tutorial.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Account\/tenancy requirements<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>An <strong>OCI tenancy<\/strong> with billing enabled.<\/li>\n<li>Exadata Cloud@Customer infrastructure already <strong>ordered, delivered, installed, and onboarded<\/strong> to your tenancy (this typically involves Oracle-managed processes).<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Permissions \/ IAM roles<\/h3>\n\n\n\n<p>You need IAM permissions to manage database resources in the relevant compartment(s). Exact policy statements vary, but you typically need permissions covering resources such as:\n&#8211; Exadata Cloud@Customer infrastructure resources\n&#8211; Autonomous VM clusters\n&#8211; Autonomous Container Databases\n&#8211; Autonomous Databases<\/p>\n\n\n\n<blockquote>\n<p>Verify in official docs: Oracle provides IAM policy examples per service. Use the official policy reference for the precise resource types and verbs.<\/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>A paid subscription\/contract. This service is not a typical \u201cclick-to-start free tier\u201d offering.<\/li>\n<li>Ensure your tenancy is configured for the correct billing model and that Cloud@Customer metering is enabled as per your Oracle agreement.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Tools you may need<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>OCI Console access (browser)<\/li>\n<li>OCI CLI (optional, for automation): https:\/\/docs.oracle.com\/en-us\/iaas\/Content\/API\/SDKDocs\/cliinstall.htm<\/li>\n<li>A SQL client:<\/li>\n<li>SQLcl (Oracle SQL Developer Command Line) or SQL*Plus (if available in your environment)<\/li>\n<li>SQL Developer (GUI), if desired<\/li>\n<li>Network tools: <code>nslookup<\/code>, <code>openssl s_client<\/code>, <code>tnsping<\/code> (where available)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Region availability<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Exadata Cloud@Customer is available only in certain commercial arrangements and locations. Availability is not the same as \u201cOCI regions list\u201d.<\/li>\n<li>Confirm your service\u2019s region association and availability in official docs and your order form.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Quotas \/ limits<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>OCI tenancy quotas and service limits apply to control-plane resources.<\/li>\n<li>Physical Exadata capacity (CPU\/storage) is the ultimate limit on how many and how large databases can be created.<\/li>\n<li>Verify limits for:<\/li>\n<li>Max number of Autonomous Databases per ACD\/VM cluster<\/li>\n<li>Compute scaling bounds<\/li>\n<li>Storage bounds<\/li>\n<li>Concurrent operations, if any<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Prerequisite services (common)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>OCI Networking components (VCN\/subnets) as required by your deployment design<\/li>\n<li>OCI Vault (if customer-managed keys are part of your security requirements\u2014verify)<\/li>\n<li>Logging\/Monitoring services enabled in the tenancy<\/li>\n<\/ul>\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<h3 class=\"wp-block-heading\">Current pricing model (how to think about it)<\/h3>\n\n\n\n<p>Autonomous AI Database on Exadata Cloud@Customer pricing is typically <strong>not<\/strong> a simple \u201cpublic price per hour in a region\u201d experience like serverless databases. It often combines:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Exadata Cloud@Customer infrastructure subscription costs<\/strong> (the engineered system capacity at your site)<\/li>\n<li><strong>Database service consumption charges<\/strong> (compute and storage for Autonomous Databases), metered through OCI<\/li>\n<\/ul>\n\n\n\n<p>The exact dimensions can vary by:\n&#8211; Contract terms\n&#8211; License model (<strong>License Included<\/strong> vs <strong>BYOL<\/strong>)\n&#8211; Hardware generation and configuration\n&#8211; Enabled options and support levels<\/p>\n\n\n\n<p>Because of this variability, you should treat published list prices (if available) as directional and confirm with:\n&#8211; Official Oracle pricing pages\n&#8211; Your Oracle order documents \/ cloud contract\n&#8211; OCI Cost Analysis and your billing reports<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Pricing dimensions (typical)<\/h3>\n\n\n\n<blockquote>\n<p>Verify exact meters in official pricing docs for your service.<\/p>\n<\/blockquote>\n\n\n\n<p>Common pricing dimensions to evaluate:\n&#8211; <strong>Compute<\/strong>: OCPU\/ECPU allocation for Autonomous Databases (and whether auto-scaling is enabled)\n&#8211; <strong>Storage<\/strong>: allocated storage for Autonomous Databases (and backup storage behavior)\n&#8211; <strong>Infrastructure subscription<\/strong>: Exadata Cloud@Customer base cost (often the primary cost driver)\n&#8211; <strong>Data transfer<\/strong>: Usually minimal for local on-prem traffic; any replication to OCI services or remote sites may incur networking costs depending on design<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Free tier<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Not typically applicable<\/strong> to Exadata Cloud@Customer-based services. Free Tier generally targets shared public-cloud services.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Cost drivers (direct)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Size of Exadata Cloud@Customer footprint (capacity\/subscription)<\/li>\n<li>Number of Autonomous Databases and their compute allocations<\/li>\n<li>Auto-scaling settings (can raise monthly cost if left unconstrained)<\/li>\n<li>Storage allocations and growth<\/li>\n<li>Backup retention and where backups are stored (confirm details)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Hidden\/indirect costs<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Data center costs: rack space, power, cooling<\/li>\n<li>Network connectivity and security appliances<\/li>\n<li>Operational processes: change management, incident response, access governance<\/li>\n<li>Client tooling and integration work (wallet distribution, certificate rotation processes)<\/li>\n<li>DR\/BC design costs (secondary site, replication, backup export)<\/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>Local app-to-db traffic in the data center does not incur \u201ccloud egress\u201d fees as in public cloud; it\u2019s your internal network.<\/li>\n<li>If you replicate data to OCI Object Storage, OCI regions, or other clouds, standard data transfer pricing may apply (verify in Oracle pricing docs).<\/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 initial database compute and storage; increase after observing real utilization.<\/li>\n<li>Use compartments and tagging to attribute costs to teams and environments.<\/li>\n<li>Prefer turning off non-essential dev\/test databases when not in use (if your service supports stop\/start patterns\u2014verify; Cloud@Customer may differ from serverless ADB behavior).<\/li>\n<li>Define policy guardrails: who can create databases, max allowed compute, required tags.<\/li>\n<li>Regularly review allocations vs actual usage with OCI billing\/cost tooling.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Example low-cost starter estimate (directional, no fabricated numbers)<\/h3>\n\n\n\n<p>A \u201cstarter\u201d setup is still enterprise-grade:\n&#8211; You need an Exadata Cloud@Customer subscription in place.\n&#8211; Create <strong>one small Autonomous Database<\/strong> for a sandbox workload.\n&#8211; Costs will primarily be:\n  1) the underlying Exadata Cloud@Customer subscription, and\n  2) the metered database compute\/storage you allocate.<\/p>\n\n\n\n<p>Because list prices and contracts vary, use:\n&#8211; Oracle Cloud pricing pages: https:\/\/www.oracle.com\/cloud\/pricing\/\n&#8211; Oracle price list: https:\/\/www.oracle.com\/cloud\/price-list\/\n&#8211; Oracle Cloud Cost Estimator: https:\/\/www.oracle.com\/cloud\/costestimator.html\n&#8211; OCI Console Cost Analysis (in your tenancy)<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Example production cost considerations<\/h3>\n\n\n\n<p>For production, account for:\n&#8211; Multiple databases (prod + staging + reporting)\n&#8211; HA\/BC requirements (secondary systems, replication, backups)\n&#8211; Larger storage footprints and retention policies\n&#8211; Monitoring and management tooling\n&#8211; Operational staffing and controls<\/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 assumes you already have Exadata Cloud@Customer installed and visible in your OCI tenancy. The tutorial focuses on a realistic \u201cday-1\u201d workflow: create an Autonomous Database on the existing dedicated environment, connect securely from a client, validate with SQL, and then clean up.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Objective<\/h3>\n\n\n\n<p>Provision an <strong>Autonomous Database<\/strong> under <strong>Autonomous AI Database on Exadata Cloud@Customer<\/strong>, connect using a secure wallet, run validation SQL, and then safely remove the database.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Lab Overview<\/h3>\n\n\n\n<p>You will:\n1. Validate prerequisites (compartment, IAM, existing Exadata Cloud@Customer resources).\n2. Create (or reuse) an Autonomous Container Database (ACD) and then create an Autonomous Database.\n3. Configure secure connectivity and download the client wallet.\n4. Connect with SQLcl (or another Oracle SQL client) and run basic SQL checks.\n5. Clean up by terminating the Autonomous Database.<\/p>\n\n\n\n<blockquote>\n<p>Note: Exact Console labels and resource names may differ by release. If a UI field is not present, follow the closest equivalent and <strong>verify in official docs<\/strong>.<\/p>\n<\/blockquote>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Step 1: Confirm access, compartments, and existing Exadata Cloud@Customer resources<\/h3>\n\n\n\n<h4 class=\"wp-block-heading\">1.1 Confirm you can see the Cloud@Customer infrastructure<\/h4>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Sign in to the <strong>Oracle Cloud Console<\/strong>.<\/li>\n<li>Select the correct <strong>region<\/strong> associated with your Cloud@Customer deployment (as configured by your org).<\/li>\n<li>Navigate to the Exadata Cloud@Customer section (naming varies; you may find it under <strong>Databases<\/strong> or <strong>Oracle Database<\/strong>).<\/li>\n<li>Confirm you can see the <strong>Exadata Cloud@Customer infrastructure<\/strong> resource and that its lifecycle state is healthy\/available.<\/li>\n<\/ol>\n\n\n\n<p><strong>Expected outcome:<\/strong> You can view the infrastructure resource and its basic details.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\">1.2 Verify the compartment strategy<\/h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Ensure you have (or create) a compartment like:<\/li>\n<li><code>cmp-prod-data<\/code><\/li>\n<li><code>cmp-nonprod-data<\/code><\/li>\n<li><code>cmp-lab-data<\/code><\/li>\n<\/ul>\n\n\n\n<p>If you need to create one:\n1. Go to <strong>Identity &amp; Security \u2192 Compartments<\/strong>\n2. Create compartment <code>cmp-lab-data<\/code>.<\/p>\n\n\n\n<p><strong>Expected outcome:<\/strong> A compartment exists where you will create the database resources.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\">1.3 Verify IAM permissions<\/h4>\n\n\n\n<p>You should be able to:\n&#8211; Create and manage Autonomous Databases in the target compartment\n&#8211; View\/use the underlying Cloud@Customer resources<\/p>\n\n\n\n<p>If you get authorization errors later, stop and request the required IAM policy updates.<\/p>\n\n\n\n<p><strong>Verification tip:<\/strong> Try opening the \u201cCreate Autonomous Database\u201d screen and confirm you can proceed far enough to see deployment options.<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Step 2: Confirm (or create) an Autonomous VM Cluster and Autonomous Container Database<\/h3>\n\n\n\n<p>In many Autonomous Database Dedicated-style environments, you create databases inside an <strong>Autonomous Container Database (ACD)<\/strong> running on an <strong>Autonomous VM Cluster<\/strong>.<\/p>\n\n\n\n<blockquote>\n<p>If your environment already has an Autonomous VM Cluster and ACD configured, reuse them and proceed to Step 3.<\/p>\n<\/blockquote>\n\n\n\n<h4 class=\"wp-block-heading\">2.1 Check for an existing Autonomous VM Cluster<\/h4>\n\n\n\n<ol class=\"wp-block-list\">\n<li>In OCI Console, go to <strong>Autonomous Database (Dedicated)<\/strong> or equivalent section used for Cloud@Customer.<\/li>\n<li>Locate <strong>Autonomous VM Clusters<\/strong> in your compartment.<\/li>\n<li>Confirm an Autonomous VM Cluster exists and is in an available state.<\/li>\n<\/ol>\n\n\n\n<p><strong>Expected outcome:<\/strong> You have an Autonomous VM Cluster to host databases.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\">2.2 Check for an existing Autonomous Container Database (ACD)<\/h4>\n\n\n\n<ol class=\"wp-block-list\">\n<li>In the same area, locate <strong>Autonomous Container Databases<\/strong>.<\/li>\n<li>Confirm an ACD exists and is available.<\/li>\n<\/ol>\n\n\n\n<p><strong>Expected outcome:<\/strong> You have an ACD that can host an Autonomous Database.<\/p>\n\n\n\n<blockquote>\n<p>If you need to create these resources, follow Oracle\u2019s official step-by-step for Autonomous Database Dedicated \/ Cloud@Customer for your release. The workflow includes selecting the Exadata infrastructure, network, CPU allocation, and maintenance settings. Because Cloud@Customer environments differ, <strong>verify in official docs<\/strong> before creation.<\/p>\n<\/blockquote>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Step 3: Create an Autonomous Database (the actual database you will connect to)<\/h3>\n\n\n\n<h4 class=\"wp-block-heading\">3.1 Start creation in the Console<\/h4>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Navigate to <strong>Autonomous Databases<\/strong> in the appropriate service area.<\/li>\n<li>Click <strong>Create Autonomous Database<\/strong>.<\/li>\n<li>Choose the compartment: <code>cmp-lab-data<\/code>.<\/li>\n<li>For <strong>Deployment type<\/strong>, select the option corresponding to <strong>Exadata Cloud@Customer<\/strong> \/ <strong>Dedicated<\/strong> (naming varies).<\/li>\n<li>Select your <strong>Autonomous Container Database<\/strong> (ACD).<\/li>\n<\/ol>\n\n\n\n<h4 class=\"wp-block-heading\">3.2 Provide database basics<\/h4>\n\n\n\n<p>Fill in:\n&#8211; <strong>Display name:<\/strong> <code>adb-lab-ai-customer<\/code>\n&#8211; <strong>Database name:<\/strong> <code>ADBLAB1<\/code> (must meet naming rules)\n&#8211; <strong>Workload type:<\/strong> Choose what your service supports (often ATP or ADW in Autonomous Database families).<br\/>\n<strong>Verify<\/strong> which workload types are enabled in your environment.\n&#8211; <strong>Compute model \/ compute count:<\/strong> Choose a small starting point that fits your lab policies.\n&#8211; <strong>Storage:<\/strong> Choose minimal storage that meets requirements.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\">3.3 Networking and access<\/h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Prefer <strong>private endpoint<\/strong> connectivity.<\/li>\n<li>Select the correct network\/subnet options as required by your Cloud@Customer design.<\/li>\n<\/ul>\n\n\n\n<h4 class=\"wp-block-heading\">3.4 Set admin credentials<\/h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Set the <strong>ADMIN<\/strong> password per Oracle\u2019s complexity rules.<\/li>\n<li>Store it in a secure password manager (do not paste into chat\/tools).<\/li>\n<\/ul>\n\n\n\n<h4 class=\"wp-block-heading\">3.5 Create<\/h4>\n\n\n\n<p>Click <strong>Create Autonomous Database<\/strong> and wait for it to become <strong>Available<\/strong>.<\/p>\n\n\n\n<p><strong>Expected outcome:<\/strong> The Autonomous Database resource is created and in \u201cAvailable\u201d state.<\/p>\n\n\n\n<p><strong>Verification:<\/strong> Open the database details page and confirm:\n&#8211; Lifecycle state: Available\n&#8211; Connection endpoints are present (private)\n&#8211; Database OCID and details are visible<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Step 4: Download the client credentials (wallet) and connect securely<\/h3>\n\n\n\n<p>Autonomous Database connectivity often uses a wallet or client credentials bundle for TLS connections (TCPS). The exact mechanism can vary; follow what the Console offers.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\">4.1 Download wallet from Console<\/h4>\n\n\n\n<ol class=\"wp-block-list\">\n<li>In the database details page, click <strong>DB Connection<\/strong>.<\/li>\n<li>Choose <strong>Download Wallet<\/strong> (or equivalent).<\/li>\n<li>Set a wallet password when prompted.<\/li>\n<li>Download the ZIP file to your admin workstation or jump host.<\/li>\n<\/ol>\n\n\n\n<p><strong>Expected outcome:<\/strong> You have a wallet ZIP file and the wallet password stored securely.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\">4.2 Install SQLcl (example)<\/h4>\n\n\n\n<p>If you don\u2019t already have SQLcl:\n&#8211; Get SQLcl from official Oracle sources (verify latest): https:\/\/www.oracle.com\/database\/sqldeveloper\/technologies\/sqlcl\/\n&#8211; Ensure Java is installed if required by your SQLcl version.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\">4.3 Unzip wallet and configure environment<\/h4>\n\n\n\n<p>On a Linux jump host or workstation:<\/p>\n\n\n\n<pre><code class=\"language-bash\">mkdir -p ~\/adb_wallet\/ADBLAB1\nunzip Wallet_ADBLAB1.zip -d ~\/adb_wallet\/ADBLAB1\nls -l ~\/adb_wallet\/ADBLAB1\n<\/code><\/pre>\n\n\n\n<p>You should see files like <code>tnsnames.ora<\/code>, <code>sqlnet.ora<\/code>, and wallet files.<\/p>\n\n\n\n<p>Set <code>TNS_ADMIN<\/code> so the client uses the wallet directory:<\/p>\n\n\n\n<pre><code class=\"language-bash\">export TNS_ADMIN=~\/adb_wallet\/ADBLAB1\n<\/code><\/pre>\n\n\n\n<p><strong>Expected outcome:<\/strong> Your client environment is pointing to the wallet directory.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\">4.4 Connect using SQLcl<\/h4>\n\n\n\n<p>Pick a service name from <code>tnsnames.ora<\/code> (for example, a \u201chigh\/medium\/low\u201d service). The actual entries depend on your database configuration.<\/p>\n\n\n\n<pre><code class=\"language-bash\">sql admin@ADBLAB1_high\n<\/code><\/pre>\n\n\n\n<p>When prompted, enter the ADMIN password you set at creation time.<\/p>\n\n\n\n<p><strong>Expected outcome:<\/strong> You get a SQL prompt connected over TCPS.<\/p>\n\n\n\n<p><strong>Verification SQL:<\/strong><\/p>\n\n\n\n<pre><code class=\"language-sql\">SELECT sysdate FROM dual;\n\nSELECT\n  user,\n  sys_context('USERENV','DB_NAME') AS db_name,\n  sys_context('USERENV','HOST') AS host\nFROM dual;\n\nSELECT name, open_mode FROM v$database;\n<\/code><\/pre>\n\n\n\n<blockquote>\n<p>If access to <code>v$database<\/code> is restricted in your configuration, that\u2019s not necessarily an error\u2014verify your privileges and Autonomous restrictions in the docs.<\/p>\n<\/blockquote>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Step 5: Create a sample schema object and run a quick workload check<\/h3>\n\n\n\n<p>Run:<\/p>\n\n\n\n<pre><code class=\"language-sql\">CREATE TABLE lab_events (\n  id NUMBER GENERATED BY DEFAULT AS IDENTITY,\n  event_time TIMESTAMP DEFAULT SYSTIMESTAMP,\n  message VARCHAR2(200)\n);\n\nINSERT INTO lab_events(message) VALUES ('hello from Autonomous AI Database on Exadata Cloud@Customer');\nCOMMIT;\n\nSELECT * FROM lab_events ORDER BY id DESC FETCH FIRST 5 ROWS ONLY;\n<\/code><\/pre>\n\n\n\n<p><strong>Expected outcome:<\/strong> Table created, one row inserted and returned.<\/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>[ ] Database shows <strong>Available<\/strong> in OCI Console<\/li>\n<li>[ ] Wallet downloaded and stored securely<\/li>\n<li>[ ] SQLcl connects successfully using <code>TNS_ADMIN<\/code><\/li>\n<li>[ ] Basic SQL queries succeed<\/li>\n<li>[ ] Sample table insert\/select works<\/li>\n<\/ul>\n\n\n\n<p>Optional validation:\n&#8211; Confirm audit entries exist for database creation in <strong>OCI Audit<\/strong>.\n&#8211; Confirm metrics appear in <strong>OCI Monitoring<\/strong> for the database resource (availability depends on service setup).<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h3 class=\"wp-block-heading\">Troubleshooting<\/h3>\n\n\n\n<h4 class=\"wp-block-heading\">Error: \u201cORA-28759: failure to open file\u201d (wallet\/TLS issues)<\/h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Confirm <code>TNS_ADMIN<\/code> points to the correct wallet folder.<\/li>\n<li>Confirm the wallet ZIP was fully extracted.<\/li>\n<li>Confirm file permissions allow your user to read the wallet files.<\/li>\n<\/ul>\n\n\n\n<h4 class=\"wp-block-heading\">Error: Cannot resolve host \/ cannot reach private endpoint<\/h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Validate DNS resolution from your client host.<\/li>\n<li>Confirm routing between your client subnet and the Exadata Cloud@Customer subnet.<\/li>\n<li>Check firewalls and security rules (NSGs\/security lists\/on-prem firewalls).<\/li>\n<li>Ensure you are connecting from an allowed network location (often requires a jump host).<\/li>\n<\/ul>\n\n\n\n<h4 class=\"wp-block-heading\">Error: Authorization failure in Console<\/h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Your IAM policies may not allow <code>create autonomous-database<\/code> or related operations.<\/li>\n<li>Work with your OCI tenancy admin to apply least-privilege policies based on Oracle\u2019s service documentation.<\/li>\n<\/ul>\n\n\n\n<h4 class=\"wp-block-heading\">Error: Database stuck in provisioning<\/h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Check the database work requests \/ activity logs in the Console.<\/li>\n<li>Confirm the underlying VM cluster\/ACD have sufficient capacity and are healthy.<\/li>\n<li>Escalate to Oracle support if the work request indicates infrastructure-level issues.<\/li>\n<\/ul>\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 consumption and clutter:<\/p>\n\n\n\n<h4 class=\"wp-block-heading\">1) Delete lab objects (optional)<\/h4>\n\n\n\n<pre><code class=\"language-sql\">DROP TABLE lab_events PURGE;\n<\/code><\/pre>\n\n\n\n<h4 class=\"wp-block-heading\">2) Terminate the Autonomous Database<\/h4>\n\n\n\n<ol class=\"wp-block-list\">\n<li>In OCI Console, open the database resource: <code>adb-lab-ai-customer<\/code>.<\/li>\n<li>Click <strong>Terminate<\/strong>.<\/li>\n<li>Confirm termination (type the database name if prompted).<\/li>\n<\/ol>\n\n\n\n<p><strong>Expected outcome:<\/strong> Database lifecycle state becomes \u201cTerminating\u201d and then it disappears or becomes \u201cTerminated\u201d depending on Console behavior.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\">3) Remove wallet files from shared hosts<\/h4>\n\n\n\n<p>If the wallet was placed on a shared jump host, remove it to prevent credential leakage:<\/p>\n\n\n\n<pre><code class=\"language-bash\">rm -rf ~\/adb_wallet\/ADBLAB1\nunset TNS_ADMIN\n<\/code><\/pre>\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>Design for <strong>private connectivity<\/strong> to the database. Avoid public endpoints unless you have a strong justification and compensating controls.<\/li>\n<li>Separate environments by <strong>compartment<\/strong> (prod vs non-prod) and by network segmentation.<\/li>\n<li>Use a layered model: application subnets \u2192 controlled jump hosts \u2192 database endpoints.<\/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 <strong>least privilege<\/strong> with compartment-scoped policies.<\/li>\n<li>Use separate groups for:<\/li>\n<li>Infrastructure admins (VM cluster\/ACD)<\/li>\n<li>Database lifecycle operators (create\/scale\/terminate ADBs)<\/li>\n<li>Read-only auditors (view-only + audit access)<\/li>\n<li>Require <strong>tags<\/strong> on database resources (owner, cost center, data classification).<\/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>Treat Exadata Cloud@Customer capacity as a shared platform: plan consolidation and avoid over-provisioning.<\/li>\n<li>Define guardrails:<\/li>\n<li>Max compute per database for non-prod<\/li>\n<li>Approval workflows for production database creation<\/li>\n<li>Review cost allocation using tags and compartments.<\/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 the correct service level\/service name from <code>tnsnames.ora<\/code> for workload type (for example, high vs low service).<\/li>\n<li>Keep application connections efficient:<\/li>\n<li>Use connection pooling<\/li>\n<li>Avoid excessive connect\/disconnect loops<\/li>\n<li>Size storage and compute based on measured workload, not guesses.<\/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 backup\/restore objectives (RPO\/RTO) and test restores.<\/li>\n<li>Use change windows for maintenance and patching where configurable.<\/li>\n<li>Document runbooks for provisioning, scaling, and incident response.<\/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>Enable monitoring and alarms for:<\/li>\n<li>Storage thresholds<\/li>\n<li>CPU\/utilization signals (if available)<\/li>\n<li>Availability and failed work requests<\/li>\n<li>Centralize logs and audit in a SIEM.<\/li>\n<li>Track configuration drift by treating OCI resources as code where possible (Terraform).<\/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: include environment, owner\/team, and purpose.<\/li>\n<li>Example: <code>adb-prod-payments-core<\/code><\/li>\n<li>Tagging:<\/li>\n<li><code>CostCenter<\/code><\/li>\n<li><code>Owner<\/code><\/li>\n<li><code>DataClassification<\/code><\/li>\n<li><code>Environment<\/code><\/li>\n<li>Enforce via policy where possible.<\/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> governs who can create\/modify\/delete database resources.<\/li>\n<li><strong>Database users\/roles<\/strong> govern who can access schemas and data.<\/li>\n<li>Design for separation of duties:<\/li>\n<li>OCI admins should not automatically have database data access.<\/li>\n<li>DB admins should not automatically have broad OCI tenancy permissions.<\/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><strong>In transit:<\/strong> Use TLS\/TCPS for client connections; wallets help manage certificates.<\/li>\n<li><strong>At rest:<\/strong> Autonomous Database environments generally encrypt data at rest by default, but key management options (Oracle-managed vs customer-managed keys) vary\u2014<strong>verify in official docs<\/strong> for Cloud@Customer specifics.<\/li>\n<li>If customer-managed keys are required, integrate with <strong>OCI Vault<\/strong> per Oracle guidance (verify supported configurations).<\/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 IPs and keep database endpoints off the public internet.<\/li>\n<li>Use strict segmentation:<\/li>\n<li>Only app subnets and controlled admin subnets can reach the database listener ports.<\/li>\n<li>Use bastion\/jump hosts with session logging for administrative 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>Treat wallets and ADMIN credentials as secrets:<\/li>\n<li>Store in a secrets manager or vault<\/li>\n<li>Rotate regularly<\/li>\n<li>Never store in source code repos<\/li>\n<li>Limit wallet distribution to only hosts\/users who must connect.<\/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 (create, update, delete).<\/li>\n<li>Capture database audit trails inside the database as required by compliance (verify available auditing features).<\/li>\n<li>Forward logs to centralized logging\/SIEM.<\/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>Validate how Cloud@Customer meets your regulatory requirements (data residency, access controls, auditability).<\/li>\n<li>Document shared responsibility:<\/li>\n<li>Oracle manages specific layers (service-defined)<\/li>\n<li>Customer manages network perimeter, endpoint security, identity governance, and application security<\/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 wallets on shared jump hosts without access controls<\/li>\n<li>Overly permissive IAM policies (tenancy-wide instead of compartment-scoped)<\/li>\n<li>No tagging\/data classification (hard to enforce governance)<\/li>\n<li>No restore testing (security includes resilience)<\/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>Use compartment isolation + network segmentation + least privilege IAM together.<\/li>\n<li>Implement a controlled \u201cdatabase request\u201d process (ticket + approval + IaC).<\/li>\n<li>Enforce MFA and federation for privileged OCI users.<\/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>Treat these as common patterns; confirm exact limitations for your release and contract.<\/p>\n<\/blockquote>\n\n\n\n<h3 class=\"wp-block-heading\">Known limitations (common to Cloud@Customer-style services)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Not instant to start:<\/strong> Requires physical infrastructure provisioning and onboarding.<\/li>\n<li><strong>Not free tier:<\/strong> Designed for enterprise workloads and contracts.<\/li>\n<li><strong>Customization boundaries:<\/strong> Autonomous-managed services often restrict OS-level access and some database-level parameters (compared to self-managed Oracle DB).<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Quotas and capacity constraints<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Physical Exadata limits: total CPU\/storage capacity.<\/li>\n<li>Service limits: number of databases, maximum sizes, concurrent operations\u2014verify in OCI limits docs for your service.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Regional\/availability constraints<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Exadata Cloud@Customer availability depends on commercial availability and deployment in your facility, not the public region catalog.<\/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>Underestimating the fixed portion (infrastructure subscription) vs variable database allocations.<\/li>\n<li>Enabling auto-scaling without guardrails can raise monthly costs.<\/li>\n<li>DR\/replication and backup exports can add network and storage costs.<\/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>Application connectivity: wallets, TLS, and DNS must be planned.<\/li>\n<li>Legacy clients may need updates to support modern TLS settings (verify).<\/li>\n<li>Some database features and options may be limited in Autonomous-managed environments.<\/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>Maintenance windows: ensure business stakeholders understand patching schedules.<\/li>\n<li>Change management: database creation\/termination is easy via Console; enforce governance so production isn\u2019t changed ad-hoc.<\/li>\n<li>Wallet rotation and distribution: plan this as an operational process.<\/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>Migrating from self-managed Oracle to Autonomous may require:<\/li>\n<li>Privilege model changes<\/li>\n<li>Feature compatibility checks<\/li>\n<li>Performance testing with service-level differences<\/li>\n<li>Use Oracle migration guidance and tools appropriate to your scenario (verify official recommendations).<\/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>Cloud@Customer blends on-prem operations with cloud control plane governance; align your teams (DBA + infra + security) early.<\/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<p>Autonomous AI Database on Exadata Cloud@Customer is a specialized solution. Compare it against other Oracle Cloud options and non-Oracle alternatives.<\/p>\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 Exadata Cloud@Customer<\/strong><\/td>\n<td>Regulated\/on-prem, low latency, Oracle DB standardization<\/td>\n<td>On-prem data location + OCI governance + Exadata performance<\/td>\n<td>Requires dedicated infrastructure and enterprise commitment; more complex prerequisites<\/td>\n<td>When data must stay on-prem but you want managed Autonomous operations<\/td>\n<\/tr>\n<tr>\n<td><strong>Autonomous Database (Serverless\/shared in OCI public region)<\/strong><\/td>\n<td>Fast start, elastic dev\/test, cloud-native apps<\/td>\n<td>Simple provisioning, pay-as-you-go, minimal infra<\/td>\n<td>Data is in OCI region; may not meet strict residency\/latency needs<\/td>\n<td>When public cloud is acceptable and you want simplest operations<\/td>\n<\/tr>\n<tr>\n<td><strong>Autonomous Database Dedicated (OCI region)<\/strong><\/td>\n<td>Dedicated capacity in OCI for isolation\/performance<\/td>\n<td>Dedicated Exadata in OCI, strong governance<\/td>\n<td>Still in OCI region; not on-prem<\/td>\n<td>When you need dedicated capacity but can host in OCI<\/td>\n<\/tr>\n<tr>\n<td><strong>Exadata Database Service on Cloud@Customer<\/strong><\/td>\n<td>More DBA control on Exadata on-prem<\/td>\n<td>Exadata on-prem + managed infrastructure; supports traditional Oracle DB operations<\/td>\n<td>More operational responsibility than Autonomous<\/td>\n<td>When you need more control than Autonomous model allows<\/td>\n<\/tr>\n<tr>\n<td><strong>Self-managed Oracle Database on Exadata (customer-owned)<\/strong><\/td>\n<td>Maximum control, custom configurations<\/td>\n<td>Full control, can meet niche requirements<\/td>\n<td>Highest operational burden; patching and backups are on you<\/td>\n<td>When managed service boundaries are too restrictive<\/td>\n<\/tr>\n<tr>\n<td><strong>AWS RDS for Oracle<\/strong><\/td>\n<td>Oracle DB in AWS managed service<\/td>\n<td>Managed backups\/patching (service-level), AWS ecosystem<\/td>\n<td>Oracle licensing constraints; not Exadata; not on-prem<\/td>\n<td>When you are standardized on AWS and want managed Oracle DB in AWS<\/td>\n<\/tr>\n<tr>\n<td><strong>Azure Oracle Database offerings (varies)<\/strong><\/td>\n<td>Oracle in Azure ecosystem<\/td>\n<td>Integration with Azure services<\/td>\n<td>Service scope varies; verify product specifics<\/td>\n<td>When workloads are Azure-native and Oracle DB is required<\/td>\n<\/tr>\n<tr>\n<td><strong>PostgreSQL\/MySQL managed databases<\/strong><\/td>\n<td>Cost-effective general-purpose apps<\/td>\n<td>Open-source, broad tooling, lower cost<\/td>\n<td>Not Oracle; migration effort; feature differences<\/td>\n<td>When Oracle-specific features are not required<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/figure>\n\n\n\n<blockquote>\n<p>Cross-cloud note: Oracle Database offerings in other clouds vary and may be partner-delivered. Always verify current service scope and support boundaries in the vendor\u2019s official docs.<\/p>\n<\/blockquote>\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 core systems<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> A financial institution runs core transaction systems on-prem due to strict regulatory and latency requirements. They also struggle with patch compliance and operational consistency across many Oracle databases.<\/li>\n<li><strong>Proposed architecture:<\/strong><\/li>\n<li>Exadata Cloud@Customer deployed in primary data center<\/li>\n<li>Autonomous AI Database on Exadata Cloud@Customer hosts multiple Autonomous Databases:<ul>\n<li><code>adb-prod-core-transactions<\/code><\/li>\n<li><code>adb-prod-customer-profile<\/code><\/li>\n<li><code>adb-prod-reporting<\/code><\/li>\n<\/ul>\n<\/li>\n<li>OCI IAM compartments separate prod\/non-prod; strict tagging and policies<\/li>\n<li>Private network connectivity from app clusters to database endpoints<\/li>\n<li>Centralized monitoring\/alarms and OCI Audit forwarded to SIEM<\/li>\n<li><strong>Why this service was chosen:<\/strong><\/li>\n<li>Keeps data on-prem while adopting managed automation and governance.<\/li>\n<li>Consolidation on Exadata improves performance and simplifies platform operations.<\/li>\n<li><strong>Expected outcomes:<\/strong><\/li>\n<li>Reduced patch drift and improved security posture<\/li>\n<li>Faster provisioning and standardized backup policies<\/li>\n<li>Better auditability for compliance<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Startup\/small-team example: local-data requirement for a regional SaaS<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem:<\/strong> A small SaaS provider serving government-adjacent clients must keep data in a customer-controlled facility and provide audited change control, but the team is small and cannot run a large DBA operation.<\/li>\n<li><strong>Proposed architecture:<\/strong><\/li>\n<li>Single Exadata Cloud@Customer deployment (customer-controlled facility)<\/li>\n<li>One production Autonomous Database plus one staging database<\/li>\n<li>IaC for provisioning (where supported) + strict IAM and tagging<\/li>\n<li>A controlled bastion host for admin access; private endpoints only<\/li>\n<li><strong>Why this service was chosen:<\/strong><\/li>\n<li>Operational model reduces DBA workload and improves reliability.<\/li>\n<li>Meets customer contract requirements for data location.<\/li>\n<li><strong>Expected outcomes:<\/strong><\/li>\n<li>Faster onboarding of new customers (new schemas\/databases)<\/li>\n<li>Better operational discipline without expanding headcount<\/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 Autonomous AI Database on Exadata Cloud@Customer the same as Autonomous Database?<\/h3>\n\n\n\n<p>It is part of the Autonomous Database family, but specifically deployed on <strong>Exadata Cloud@Customer<\/strong> infrastructure in your environment. The control plane is in OCI; the data plane is on-prem.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">2) Does this mean Oracle manages the database for me?<\/h3>\n\n\n\n<p>Oracle provides a managed service model for lifecycle operations defined by the service. Your team still owns application schema design, data modeling, access governance, and operational processes like incident response and change approvals.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">3) Where does the data actually live?<\/h3>\n\n\n\n<p>The database runs on Exadata hardware located in your data center or customer-controlled facility. Confirm the exact deployment boundary in your Cloud@Customer documentation and contract.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">4) Do I need an OCI tenancy even though it\u2019s on-prem?<\/h3>\n\n\n\n<p>Yes. OCI tenancy, IAM, compartments, and billing are typically used to manage the service.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">5) Can I connect without a wallet?<\/h3>\n\n\n\n<p>Autonomous Database connectivity commonly uses wallets\/certificates for TLS. Some environments may support alternative mechanisms, but you should follow the connectivity method shown in your Console and official docs.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">6) Can I expose the database publicly?<\/h3>\n\n\n\n<p>Best practice is private-only connectivity. Public exposure is usually discouraged, and may be constrained by design. Verify what is supported and approved in your security architecture.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">7) What are the main resources I will manage?<\/h3>\n\n\n\n<p>Common constructs include Exadata infrastructure, VM clusters, Autonomous Container Databases, and Autonomous Databases (exact names may differ). Most users primarily interact with the Autonomous Database resource.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">8) How is access controlled?<\/h3>\n\n\n\n<p>Control plane actions are controlled by OCI IAM. Data access is controlled by database users\/roles inside the database.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">9) How do patches and updates work?<\/h3>\n\n\n\n<p>The service includes managed patching\/maintenance orchestration. Maintenance timing controls vary\u2014verify available maintenance window controls in the official docs for your environment.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">10) Can I use Terraform?<\/h3>\n\n\n\n<p>Often yes for OCI resources, but Cloud@Customer and Dedicated Autonomous constructs may require specific providers and permissions. Verify Terraform support for your exact resource types.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">11) Is it suitable for dev\/test?<\/h3>\n\n\n\n<p>It can be, but Cloud@Customer is typically optimized for production\/regulated needs. Many teams use OCI public-region Autonomous Database for dev\/test due to lower barrier to entry.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">12) How do backups work?<\/h3>\n\n\n\n<p>Autonomous services typically provide automated backups with configurable retention. On Cloud@Customer, backup storage location and recovery workflows must be confirmed in documentation and your deployment design.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">13) Can I replicate to OCI public regions?<\/h3>\n\n\n\n<p>Hybrid DR\/replication patterns may be possible depending on tooling, network, and service support, but specifics must be verified for Cloud@Customer deployments.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">14) What\u2019s the biggest \u201cgotcha\u201d new teams hit?<\/h3>\n\n\n\n<p>Networking and connectivity planning: DNS, routing, firewalls, and wallet distribution often cause the most friction in early adoption.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">15) How do I estimate costs accurately?<\/h3>\n\n\n\n<p>Use a combination of Oracle\u2019s official pricing resources, your contract\/order form, and OCI cost tools. Cloud@Customer pricing is often contract-specific, so avoid relying on generic per-hour estimates alone.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">16) Can I use existing Oracle licenses (BYOL)?<\/h3>\n\n\n\n<p>Many Oracle services offer BYOL vs License Included. Availability depends on your contract and service configuration\u2014verify in Oracle pricing and your agreement.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">17) Is this \u201cserverless\u201d?<\/h3>\n\n\n\n<p>Not in the same way as shared Autonomous Database in OCI public regions. This is a <strong>dedicated capacity<\/strong> model running on your Exadata Cloud@Customer infrastructure.<\/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 Exadata Cloud@Customer<\/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>Oracle Autonomous Database docs: https:\/\/docs.oracle.com\/en\/cloud\/paas\/autonomous-database\/<\/td>\n<td>Core concepts, operations, connectivity, security for Autonomous Database<\/td>\n<\/tr>\n<tr>\n<td>Official documentation<\/td>\n<td>Autonomous Database Dedicated docs (verify Cloud@Customer alignment): https:\/\/docs.oracle.com\/en\/cloud\/paas\/autonomous-database\/dedicated\/<\/td>\n<td>Resource model (VM clusters\/ACDs), dedicated deployment workflows<\/td>\n<\/tr>\n<tr>\n<td>Official documentation<\/td>\n<td>Exadata Cloud@Customer docs (service overview and operations): https:\/\/docs.oracle.com\/en\/cloud\/paas\/exadata-cloud-at-customer\/<\/td>\n<td>Cloud@Customer architecture, prerequisites, and operational guidance<\/td>\n<\/tr>\n<tr>\n<td>Official pricing<\/td>\n<td>Oracle Cloud Pricing overview: https:\/\/www.oracle.com\/cloud\/pricing\/<\/td>\n<td>Entry point to OCI pricing models and services<\/td>\n<\/tr>\n<tr>\n<td>Official pricing<\/td>\n<td>Oracle Cloud Price List: https:\/\/www.oracle.com\/cloud\/price-list\/<\/td>\n<td>Detailed SKUs\/meters (where published); confirm service-specific items<\/td>\n<\/tr>\n<tr>\n<td>Cost calculator<\/td>\n<td>Oracle Cloud Cost Estimator: https:\/\/www.oracle.com\/cloud\/costestimator.html<\/td>\n<td>Build scenarios; validate against contract where applicable<\/td>\n<\/tr>\n<tr>\n<td>Official labs<\/td>\n<td>Oracle LiveLabs: https:\/\/livelabs.oracle.com\/<\/td>\n<td>Hands-on labs; search for Autonomous Database and Exadata topics<\/td>\n<\/tr>\n<tr>\n<td>Official architecture<\/td>\n<td>Oracle Architecture Center: https:\/\/docs.oracle.com\/en\/solutions\/<\/td>\n<td>Reference architectures; useful for hybrid and database designs<\/td>\n<\/tr>\n<tr>\n<td>Official CLI docs<\/td>\n<td>OCI CLI installation and usage: https:\/\/docs.oracle.com\/en-us\/iaas\/Content\/API\/SDKDocs\/cliinstall.htm<\/td>\n<td>Automate provisioning and lifecycle steps<\/td>\n<\/tr>\n<tr>\n<td>Official tool<\/td>\n<td>SQLcl: https:\/\/www.oracle.com\/database\/sqldeveloper\/technologies\/sqlcl\/<\/td>\n<td>Lightweight client for connecting to Autonomous Database<\/td>\n<\/tr>\n<tr>\n<td>Official videos<\/td>\n<td>Oracle YouTube channel: https:\/\/www.youtube.com\/user\/Oracle<\/td>\n<td>Webinars, product explainers (verify playlists for Autonomous\/Exadata)<\/td>\n<\/tr>\n<tr>\n<td>Community learning<\/td>\n<td>Oracle Cloud community forums: https:\/\/community.oracle.com\/<\/td>\n<td>Practical Q&amp;A validate answers against official docs<\/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 URL<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>DevOpsSchool.com<\/td>\n<td>Cloud engineers, DevOps\/SRE, platform teams<\/td>\n<td>OCI fundamentals, automation, DevOps practices around cloud services<\/td>\n<td>Check website<\/td>\n<td>https:\/\/www.devopsschool.com\/<\/td>\n<\/tr>\n<tr>\n<td>ScmGalaxy.com<\/td>\n<td>DevOps beginners to intermediate<\/td>\n<td>SCM\/CI\/CD foundations that can support IaC and database automation<\/td>\n<td>Check website<\/td>\n<td>https:\/\/www.scmgalaxy.com\/<\/td>\n<\/tr>\n<tr>\n<td>CLoudOpsNow.in<\/td>\n<td>Operations and cloud ops teams<\/td>\n<td>Cloud operations practices, monitoring, reliability, governance<\/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, operations leads<\/td>\n<td>SRE principles, observability, incident management for cloud platforms<\/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, automation, monitoring-driven operations<\/td>\n<td>Check website<\/td>\n<td>https:\/\/www.aiopsschool.com\/<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/figure>\n\n\n\n<blockquote>\n<p>Note: Always verify course syllabi specifically for Oracle Cloud and Cloud@Customer coverage, as these are specialized topics.<\/p>\n<\/blockquote>\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 URL<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>RajeshKumar.xyz<\/td>\n<td>DevOps\/cloud training and mentorship (verify offerings)<\/td>\n<td>Individuals and teams seeking guided coaching<\/td>\n<td>https:\/\/rajeshkumar.xyz\/<\/td>\n<\/tr>\n<tr>\n<td>devopstrainer.in<\/td>\n<td>DevOps training services (verify OCI coverage)<\/td>\n<td>Beginners to working professionals<\/td>\n<td>https:\/\/www.devopstrainer.in\/<\/td>\n<\/tr>\n<tr>\n<td>devopsfreelancer.com<\/td>\n<td>Freelance DevOps consulting\/training platform (verify scope)<\/td>\n<td>Teams needing short-term help or project-based guidance<\/td>\n<td>https:\/\/www.devopsfreelancer.com\/<\/td>\n<\/tr>\n<tr>\n<td>devopssupport.in<\/td>\n<td>DevOps support\/training (verify offerings)<\/td>\n<td>Ops teams needing hands-on 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 URL<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>cotocus.com<\/td>\n<td>Cloud\/DevOps consulting (verify Oracle Cloud experience)<\/td>\n<td>Platform engineering, automation, cloud operations<\/td>\n<td>OCI landing zone + database provisioning automation patterns<\/td>\n<td>https:\/\/cotocus.com\/<\/td>\n<\/tr>\n<tr>\n<td>DevOpsSchool.com<\/td>\n<td>DevOps and cloud consulting\/training<\/td>\n<td>IaC pipelines, governance, operational best practices<\/td>\n<td>Build CI\/CD + Terraform workflows for OCI database environments<\/td>\n<td>https:\/\/www.devopsschool.com\/<\/td>\n<\/tr>\n<tr>\n<td>DEVOPSCONSULTING.IN<\/td>\n<td>DevOps consulting services (verify service catalog)<\/td>\n<td>DevOps transformation, tooling, reliability practices<\/td>\n<td>Monitoring\/alerting integration and runbook standardization<\/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 Exadata Cloud@Customer, build these foundations:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>\n<p><strong>OCI fundamentals<\/strong>\n   &#8211; Tenancy, compartments, IAM policies\n   &#8211; VCNs, subnets, routing, NSGs\/security lists\n   &#8211; Audit, Monitoring, Events<\/p>\n<\/li>\n<li>\n<p><strong>Oracle Database fundamentals<\/strong>\n   &#8211; Users\/roles, tablespaces, basic SQL performance concepts\n   &#8211; Backup\/restore concepts (even if automated)\n   &#8211; Connectivity (SQL*Net, TCPS, wallets)<\/p>\n<\/li>\n<li>\n<p><strong>Security fundamentals<\/strong>\n   &#8211; Least privilege, secrets management, TLS concepts\n   &#8211; Network segmentation and firewalling<\/p>\n<\/li>\n<li>\n<p><strong>Automation<\/strong>\n   &#8211; OCI CLI basics\n   &#8211; Terraform basics (if your org uses IaC)\n   &#8211; Git and CI\/CD<\/p>\n<\/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>Advanced operational practices:<\/li>\n<li>SLOs\/SLIs for database platforms<\/li>\n<li>Capacity planning on dedicated infrastructure<\/li>\n<li>Incident response for database-backed systems<\/li>\n<li>Hybrid architecture patterns:<\/li>\n<li>DR strategies and recovery testing<\/li>\n<li>Data replication approaches (verify supported technologies)<\/li>\n<li>Governance at scale:<\/li>\n<li>Policy-as-code, tagging enforcement, cost allocation<\/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 (Oracle Cloud\/hybrid)<\/li>\n<li>Database platform engineer<\/li>\n<li>Oracle DBA (transitioning to managed service operations)<\/li>\n<li>SRE \/ reliability engineer (database platforms)<\/li>\n<li>Security engineer (cloud governance and regulated environments)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Certification path (if available)<\/h3>\n\n\n\n<p>Oracle certifications change over time. Start by checking Oracle University and OCI certification tracks, then map to database specialties.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Oracle University: https:\/\/education.oracle.com\/  <\/li>\n<li>OCI training\/certification entry points are commonly linked from Oracle University (verify latest tracks).<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Project ideas for practice<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Build a \u201cdatabase vending machine\u201d:<\/li>\n<li>A request form + Terraform\/CLI automation that creates an Autonomous Database in the right compartment with mandatory tags.<\/li>\n<li>Implement audit + alerting:<\/li>\n<li>Alert when a database is created without required tags.<\/li>\n<li>Create a secure connectivity pattern:<\/li>\n<li>Bastion-only admin access, private endpoints, wallet distribution via a secure pipeline.<\/li>\n<\/ul>\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>Autonomous Database:<\/strong> Oracle-managed database service emphasizing automation in provisioning, tuning, patching, and backups (capabilities vary by deployment model).<\/li>\n<li><strong>Exadata Cloud@Customer:<\/strong> Exadata infrastructure deployed at a customer site but delivered\/managed as a cloud service with OCI integration.<\/li>\n<li><strong>OCI (Oracle Cloud Infrastructure):<\/strong> Oracle Cloud platform providing IAM, networking, monitoring, audit, and database services.<\/li>\n<li><strong>Compartment:<\/strong> OCI governance container used to organize and isolate resources and apply IAM policies.<\/li>\n<li><strong>IAM Policy:<\/strong> Rules that define who can do what actions on which OCI resources.<\/li>\n<li><strong>OCID:<\/strong> Oracle Cloud Identifier; unique ID for OCI resources.<\/li>\n<li><strong>Control plane:<\/strong> Management layer (APIs\/Console) used to provision and manage resources.<\/li>\n<li><strong>Data plane:<\/strong> The path where application data flows (SQL connections, queries, transactions).<\/li>\n<li><strong>Wallet:<\/strong> Credential bundle used by Oracle clients to establish secure TLS connections to Autonomous Database endpoints.<\/li>\n<li><strong>TCPS:<\/strong> Oracle Net over TLS; encrypted transport commonly used for Autonomous Database connections.<\/li>\n<li><strong>Autonomous VM Cluster:<\/strong> A virtualized compute cluster on Exadata used to host Autonomous database containers (naming may vary).<\/li>\n<li><strong>Autonomous Container Database (ACD):<\/strong> A container that hosts one or more Autonomous Databases in dedicated environments (verify exact usage).<\/li>\n<li><strong>NSG (Network Security Group):<\/strong> OCI virtual firewall construct for controlling traffic to\/from resources.<\/li>\n<li><strong>RPO\/RTO:<\/strong> Recovery Point Objective \/ Recovery Time Objective for disaster recovery planning.<\/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 Exadata Cloud@Customer (Oracle Cloud, <strong>Data Management<\/strong>) brings Autonomous Database-style managed operations to <strong>Exadata hardware located in your environment<\/strong>, while retaining OCI governance, IAM, auditing, and API-driven lifecycle management. It matters most for organizations that need <strong>on-prem data residency<\/strong>, <strong>low-latency access<\/strong>, and <strong>enterprise-grade performance<\/strong>, but still want to reduce DBA toil and standardize operations.<\/p>\n\n\n\n<p>Cost-wise, plan for a combination of <strong>Cloud@Customer infrastructure subscription<\/strong> plus <strong>database compute\/storage consumption<\/strong>, and use official Oracle pricing tools and your contract for accuracy. Security-wise, design around <strong>private connectivity<\/strong>, strict <strong>IAM least privilege<\/strong>, careful <strong>wallet\/secret handling<\/strong>, and centralized <strong>audit\/monitoring<\/strong>.<\/p>\n\n\n\n<p>Use this service when on-prem location is required and you want a managed Oracle database platform. If you don\u2019t need on-prem residency or dedicated infrastructure, consider Autonomous Database in OCI public regions for a simpler and faster start.<\/p>\n\n\n\n<p>Next step: read the official Autonomous Database Dedicated and Exadata Cloud@Customer documentation, then run the hands-on lab steps in a controlled compartment to validate connectivity, IAM, and operational readiness before production adoption.<\/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-879","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\/879","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=879"}],"version-history":[{"count":0,"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/posts\/879\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/media?parent=879"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/categories?post=879"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.devopsschool.com\/tutorials\/wp-json\/wp\/v2\/tags?post=879"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}