Study guide

13.3 Operating Autonomous AI Database: Scaling, Cloning, Backups, Patching & Self-Tuning

OCI 2026 Architect Professional 1Z0-997-26

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Exam Overview & Architecture Foundations

1.1 Exam Logistics, the 2026 Blueprint & How to Use This Guide 1.2 The OCI Well-Architected Framework & Architectural Tradeoffs

2 Chapter 2: High Availability & Resilient Design

2.1 Availability Domains, Fault Domains, Instance Pools & Load Balancers 2.2 OCI DNS Traffic Steering, Geolocation & Health Checks 2.3 Block Volume Replication, Volume Groups & Backup Policies 2.4 Object Storage Replication, Versioning & Retention Rules (WORM)

3 Chapter 3: Full Stack Disaster Recovery

3.1 Full Stack Disaster Recovery: Protection Groups, Members & Permissions 3.2 DR Plans: Switchover, Failover, Prechecks & Plan Execution 3.3 DR Drills, Plan Customization & Operational Readiness

4 Chapter 4: Container Instances, OCIR & OCI DevOps

4.1 Containerization, Microservices & OCI Container Instances 4.2 OCI Container Registry: Repositories, Push & Pull, and Image Management 4.3 OCI DevOps: Code Repositories, Build Pipelines & Deployment Strategies

5 Chapter 5: OCI Kubernetes Engine (OKE)

5.1 OKE Cluster Types, Node Options & Cluster Creation 5.2 OKE Networking: VCN-Native Pod Networking vs. Flannel, Subnet Sizing & Load Balancers 5.3 OKE Workload Identity, Secrets & Persistent Storage

6 Chapter 6: Serverless Functions & API Gateway

6.1 OCI Functions: Concepts, Invocation Modes, Integrations & Image Security 6.2 API Gateway: Authentication, JWT Validation, Rate Limiting & Usage Plans

7 Chapter 7: Messaging & Event-Driven Design

7.1 OCI Streaming, OCI Queue & Messaging Patterns for Microservices 7.2 OCI Events, Event Rules & OCI Notifications Fan-Out

8 Chapter 8: Infrastructure as Code with Terraform & Resource Manager

8.1 Infrastructure as Code with Terraform and the OCI Provider 8.2 OCI Resource Manager: Stacks, Jobs, Drift Detection & Private Endpoints

9 Chapter 9: Identity & Multi-Tenancy Governance

9.1 IAM Policy Design: Verbs, Conditions, Dynamic Groups & Principals 9.2 Organizations Management, Governance Rules & Compartment Quotas

10 Chapter 10: Security Posture with Cloud Guard & Security Zones

10.1 Cloud Guard: Detector Recipes, Problems, Scores & Responders 10.2 Security Zones & Vulnerability Scanning

11 Chapter 11: Secure Access & Network Protection

11.1 Layered Network Security: Security Lists, NSGs & Private Access to Services 11.2 OCI Bastion: Managed SSH, Port Forwarding & SOCKS5 Sessions 11.3 Zero Trust Packet Routing (ZPR): Security Attributes & Intent-Based Policy 11.4 OCI Network Firewall: Policies, Inspection Routing, Tunnel Inspection & Private NAT

12 Chapter 12: Application & Data Protection: WAF, Certificates & Vault

12.1 OCI Web Application Firewall: Policies, Modules, Actions & Enforcement Points 12.2 OCI Certificates: Private CAs, TLS Certificates, Renewal & Integrations 12.3 OCI Vault Key Management: Vault Types, Protection Modes, Dedicated KMS & External KMS 12.4 Vault Secrets: Versions, Rotation States, Automatic Generation & Rotation

13 Chapter 13: Base Database Service & Autonomous AI Database

13.1 Base Database Service: DB Systems, RAC, Data Guard, Cloning & Maintenance 13.2 Autonomous AI Database: Workload Types, Deployment Options, Services & Connectivity 13.3 Operating Autonomous AI Database: Scaling, Cloning, Backups, Patching & Self-Tuning 13.4 Autonomous Data Guard & Backup-Based Disaster Recovery for Autonomous AI Database

14 Chapter 14: Recovery Service, Global Distribution & OCI Cache

14.1 Autonomous Recovery Service: Protection Policies, Real-Time Protection & Retention Lock 14.2 Globally Distributed Autonomous AI Database: Sharding, Data Placement & Replication 14.3 OCI Cache: Valkey and Redis Clusters, Sharding, Security & Cross-Region Replication

15 Chapter 15: Monitoring, Alarms & Notifications

15.1 OCI Monitoring: Metrics, Namespaces, Custom Metrics & Monitoring Query Language 15.2 Alarms & Notifications: Trigger Rules, Absence Alarms, Split Messages, Suppression & Delivery

16 Chapter 16: Logging, Audit, Connector Hub & Search

16.1 OCI Logging: Log Groups, Service Logs, Custom Logs & the Unified Monitoring Agent 16.2 Logging Search, the Logging Query Language & OCI Audit 16.3 Connector Hub: Moving Logs, Metrics, Queue Messages & Streams Between Services 16.4 OCI Search with OpenSearch & Resource Search for Observability

13.3 Operating Autonomous AI Database: Scaling, Cloning, Backups, Patching & Self-Tuning

Key Takeaways Explain This Topic AI

Compute auto scaling is enabled by default and lets an Autonomous AI Database use up to three times its ECPU count, billed for the extra CPU actually used.

Storage auto scaling is disabled by default and lets the database grow to three times its reserved base storage.

Autonomous AI Database offers full clones, refreshable clones, metadata clones, and refreshable metadata clones.

Automatic backups are retained for 60 days by default (configurable from 1 to 60 days), and long-term backups can be kept from 3 months to 10 years.

With the Early patch level, maintenance is applied one week before databases on the default Regular patch level.

Last updated: October 2026

  • Scaling
  • Compute Auto Scaling

When compute auto scaling is enabled, which is the default for new databases, the database can use up to three times more CPU and I/O resources than its ECPU count. For example, a database with 512 ECPUs can use up to 1,536 ECPUs. You are billed for the additional CPU the workload actually consumes. The number of ECPUs allocated can be checked on the Database Dashboard in Database Actions. Enabling auto scaling also changes the concurrency and parallelism settings of the predefined services.

Storage Auto Scaling

Storage auto scaling is disabled by default . When you enable it, the database can expand to use up to three times the reserved base storage . You can also change the base storage manually at any time through Manage resource allocation .

Manual Scaling

You can change the ECPU count and storage online , without downtime. A common pattern is a modest base ECPU count with auto scaling for peaks, plus scheduled manual scaling for known month-end loads.

Cloning

Clones create new databases from an existing one, for testing, development, analytics, or recovery.

  • Clone type What it contains Updates
  • Full clone Data and metadata Independent copy
  • Refreshable clone Read-only full copy Can be refreshed with data from the source
  • Metadata clone Schema metadata only, no data Independent copy
  • Refreshable metadata clone Read-only metadata copy Can be refreshed with changes from the source

For full and metadata clones you also choose the source :

Clone from a database instance : a copy of the running database.

Clone from a backup : a copy at a selected backup or point in time.

Clone from the latest backup : a copy using the most recent backup data.

Additional options include cross-region cloning , cross-tenancy cloning , cloning to change the workload type , cloning when the source is unavailable (to replace a failed database from its backup), and cloning to a preview of an upcoming release when one is available. Refreshable clones are a popular way to give reporting teams a read-only, periodically refreshed copy without affecting production.

Backups and Recovery

Autonomous AI Database backs itself up automatically:

Automatic backups : retained for 60 days by default ; you can set the retention from 1 to 60 days . You can restore or clone to any point in time within the retention period.

Long-term backups : created once or on a weekly, monthly, or yearly schedule, with retention from 3 months to 10 years , for compliance and archival needs.

Restore operations replace the database contents with an earlier point in time, while cloning from a backup creates a separate database and leaves the original untouched, which is usually safer when investigating a data error.

Patching and Maintenance

Oracle applies patches automatically during maintenance windows shown in the Console:

Patch level : Regular (default when provisioning) or Early . Early-level databases receive maintenance one week before Regular ones, so you can test patches in non-production databases before they reach production. A clone inherits the source's patch level by default.

Patches are applied in a rolling fashion within the scheduled maintenance window to minimize disruption, and the Console shows the next scheduled maintenance.

On dedicated Exadata infrastructure , you set maintenance preferences at the Autonomous Container Database level, so groups of databases share schedules you control.

Self-Tuning: Auto Configuration and Optimizer Statistics

Autonomous AI Database configures memory, parallelism, and many database settings automatically based on the workload type and size. It also maintains optimizer statistics for you:

High-frequency automatic optimizer statistics collection is enabled by default and runs every 15 minutes , so statistics are less likely to be stale.

Real-time statistics are gathered during conventional DML, helping the optimizer between collection jobs.

Automatic indexing , once you enable it with the DBMS_AUTO_INDEX package (it is disabled by default), creates and validates indexes based on the workload.

SQL quarantine can stop repeatedly runaway statements (automatic quarantine based on Resource Manager limits is disabled by default, but manually quarantined statements are honored).

Settings such as OPTIMIZER_IGNORE_HINTS and OPTIMIZER_IGNORE_PARALLEL_HINTS control whether the optimizer follows hints in application SQL, which matters when migrating applications that contain old hints.

Initialization Parameters

Unlike Base Database Service, you cannot change most initialization parameters . Oracle publishes a list of parameters that you can modify, such as NLS formatting parameters, OPTIMIZER_IGNORE_HINTS , OPTIMIZER_IGNORE_PARALLEL_HINTS , OPTIMIZER_MODE , OPTIMIZER_REAL_TIME_STATISTICS , and RESULT_CACHE_INTEGRITY , using ALTER SESSION or ALTER SYSTEM as documented for each parameter. If an application depends on parameters outside that list, Base Database Service may be a better fit.

Stopping and Starting

You can stop an Autonomous AI Database when it is not needed, such as a development database at night. Compute billing stops while it is stopped, but storage is still billed . Combine start and stop actions with the Resource Scheduler or a scheduled function to automate this.

Loading diagram... Operational Levers for Autonomous AI Database