Why Oracle Is Moving Toward Self-Managing Databases: The Future of Database Administration

 

Introduction

For decades, Oracle Database Administration has relied heavily on manual intervention. DBAs have been responsible for performance tuning, index management, memory optimization, statistics collection, SQL execution plans, patching, backup strategies, and troubleshooting. While these tasks remain critical, the growing complexity of enterprise environments has made manual administration increasingly difficult.

Today's organizations expect databases to deliver high performance, continuous availability, and stronger security while supporting cloud-native applications, AI workloads, and ever-increasing data volumes. Managing these demands manually is becoming impractical.

Oracle's answer is a gradual shift toward self-managing databases—systems that continuously monitor themselves, identify optimization opportunities, and apply improvements automatically whenever it is safe to do so.

This evolution does not eliminate the DBA. Instead, it transforms the DBA from an operator performing repetitive maintenance into an engineer focused on architecture, automation, security, governance, and business continuity.

The Challenges of Traditional Database Administration

Enterprise databases generate thousands of internal events every second. A DBA must constantly monitor:

• SQL performance

• Memory utilization

• Wait events

• Blocking sessions

• Storage growth

• Optimizer statistics

• Backup validation

• Security compliance

• Patch management

As environments scale to hundreds of databases, these routine administrative activities consume significant time and increase the risk of human error.

Organizations are therefore looking for databases that can optimize themselves while allowing DBAs to concentrate on strategic responsibilities.

Why Oracle Is Investing in Autonomous Database Intelligence

Oracle's vision extends beyond adding new features to each database release. The company is redesigning the database engine to make intelligent decisions based on workload behavior and historical execution patterns.

The primary objectives include:

• Reducing manual tuning effort

• Improving application response time

• Preventing performance regressions

• Increasing database availability

• Lowering operational costs

• Delivering consistent performance at scale

• Simplifying cloud database management

Rather than relying on reactive troubleshooting, Oracle aims to detect and address performance issues before users notice them.

Automatic SQL Optimization

One of the most significant advancements is Oracle's ability to analyze SQL execution continuously.

Instead of requiring a DBA to manually identify expensive queries, Oracle evaluates execution statistics, identifies inefficient plans, and recommends or applies better execution strategies where appropriate.

This enables:

• Reduced execution time

• Lower CPU utilization

• Better optimizer decisions

• Improved workload stability

Smarter Statistics Collection

Accurate optimizer statistics are essential for generating efficient execution plans.

Older database environments often required DBAs to schedule statistics collection manually or investigate poor plans caused by outdated statistics.

Oracle now improves this process by:

• Monitoring table modifications

• Collecting statistics when needed

• Using Real-Time Statistics for changing objects

• Reducing stale statistics problems

The optimizer therefore has better information when selecting execution plans.

Intelligent Memory Management

Memory configuration has traditionally required continuous monitoring.

DBAs previously adjusted:

• SGA size

• PGA allocation

• Shared Pool

• Buffer Cache

Oracle now dynamically adjusts memory allocation according to workload requirements, reducing unnecessary tuning while maintaining consistent performance.

Automatic Index Management

Applications often accumulate unused indexes while missing indexes needed for new workloads.

Oracle's automatic indexing capabilities help by:

• Detecting repetitive SQL patterns

• Creating candidate indexes

• Validating performance improvements

• Monitoring index usage

• Removing ineffective automatic indexes

This creates a continuously optimized indexing strategy with minimal manual effort.

Performance Stability Through SQL Plan Management

A common production issue occurs after upgrades or statistics changes, where SQL begins using inefficient execution plans.

Oracle addresses this through SQL Plan Management by:

• Preserving known-good execution plans

• Testing alternative plans safely

• Preventing unexpected regressions

• Gradually accepting better plans

This helps maintain predictable application performance.

AI-Assisted Query Processing

Oracle Database 23ai introduces capabilities designed to support AI-driven workloads while also enhancing traditional database operations.

Examples include:

• AI Vector Search

• Intelligent optimizer enhancements

• Better execution decisions for mixed workloads

• Improved handling of modern application architectures

These capabilities demonstrate Oracle's strategy of integrating AI directly into the database engine rather than treating it as a separate platform.

Reduced Human Error

Many production incidents originate from manual mistakes such as:

• Incorrect initialization parameters

• Missing optimizer statistics

• Incomplete index maintenance

• Delayed monitoring

• Configuration inconsistencies

By automating repetitive administrative activities, Oracle reduces the likelihood of these common operational errors.

Better Cloud Operations

Modern enterprises often manage databases across multiple regions and cloud environments.

Automation provides:

• Consistent configurations

• Standardized maintenance

• Faster provisioning

• Predictable performance

• Easier lifecycle management

This is especially valuable for organizations operating hundreds of databases simultaneously.

Does Automation Replace the DBA?

A common misconception is that self-managing databases make DBAs unnecessary.

In practice, the DBA's responsibilities evolve rather than disappear.

Future-focused DBAs will increasingly concentrate on:

• Database architecture

• High availability and disaster recovery

• Security and compliance

• Capacity planning

• Performance engineering

• Automation using scripting and Infrastructure as Code

• Cloud database services

• Cost optimization

• AI-enabled database solutions

Routine operational work decreases, while strategic responsibilities become more important.

What This Means for Oracle DBAs

To remain competitive, Oracle DBAs should strengthen skills in areas such as:

• Oracle Database 23ai

• Oracle Cloud Infrastructure (OCI)

• Autonomous Database

• Performance engineering

• Data Guard

• RAC

• Backup and recovery

• Shell scripting

• Python automation

• Infrastructure as Code

• Database observability and monitoring

The most valuable DBAs of the future will combine traditional database expertise with cloud, automation, and AI knowledge.

Final Thoughts

Oracle's move toward self-managing databases reflects a broader shift in enterprise IT. As systems grow larger and more complex, automation becomes essential for maintaining reliability, performance, and operational efficiency.

The objective is not to remove the DBA but to reduce repetitive maintenance and allow database professionals to focus on higher-value engineering tasks. Oracle Database 23ai continues this journey by introducing intelligent automation that helps databases optimize themselves while giving administrators greater visibility and control.

For Oracle DBAs, embracing these technologies is an opportunity to expand their role, deliver greater business value, and stay relevant in an increasingly automated world.

OCI Control Center Console Enhancements – A DBA's Perspective (2026)

 

Introduction

Oracle Cloud Infrastructure (OCI) continues to evolve with new console enhancements aimed at simplifying cloud administration and improving operational efficiency. The latest OCI Control Center updates focus on better visibility, faster navigation, centralized resource management, and an improved user experience.

As Oracle DBAs and Cloud Administrators manage hundreds of cloud resources across compartments and regions, these enhancements help reduce administration effort and improve productivity.

In this article, I will discuss the key benefits of the OCI Control Center enhancements and how they can help database administrators in day-to-day operations.

Why OCI Control Center Matters

The OCI Console is the primary interface used to manage:

• Compute Instances
• Oracle Databases
• Autonomous Databases
• Networking Components
• Storage Services
• Monitoring and Alarms
• Identity and Access Management

For large environments, navigating multiple services can become challenging. Oracle's latest enhancements are designed to provide a more streamlined management experience.

Key Enhancements in OCI Control Center

1. Improved Resource Visibility

One of the major improvements is better visibility across cloud resources.

Administrators can now:

• Quickly identify critical resources
• Monitor resource health
• View service status at a glance
• Access frequently used services faster

This reduces the time spent searching for resources across multiple compartments.

DBA Benefit

A DBA managing multiple Oracle databases can quickly locate:

• Production databases
• Standby databases
• Backup resources
• Monitoring dashboards

without excessive navigation.

2. Enhanced Dashboard Experience

The dashboard now provides a more centralized operational view.

Important metrics are easier to access, including:

• Resource utilization
• Service health
• Alerts and notifications
• Database-related events

DBA Benefit

Instead of opening multiple pages, administrators can monitor important infrastructure components from a single location.

3. Faster Navigation

Oracle has improved console responsiveness and navigation.

Enhancements include:

• Simplified menu structures
• Improved search functionality
• Better service categorization
• Faster page loading

DBA Benefit

During critical incidents, administrators can access required services quickly and reduce response times.

4. Better Monitoring Integration

Monitoring and observability continue to be important areas within OCI.

The latest enhancements improve access to:

• OCI Monitoring
• Alarms
• Logging
• Events

DBA Benefit

Database administrators can identify issues earlier and respond before they affect business operations.

Examples include:

• High CPU utilization
• Storage consumption alerts
• Backup failures
• Network latency issues

5. Improved Resource Organization

Organizations often maintain:

• Development environments
• Test environments
• UAT environments
• Production environments

OCI Control Center enhancements help administrators organize resources more efficiently.

DBA Benefit

Resources can be located and managed faster, reducing operational complexity.

Real-World DBA Scenario

Imagine an organization running:

• Oracle Database 19c
• Data Guard
• OCI Compute
• OCI Block Storage
• OCI Monitoring

When an alert is generated for high CPU utilization on a production database server:

Previous Approach

• Open Monitoring Service
• Find Alarm
• Identify Instance
• Open Compute Console
• Verify Database Status

Enhanced Experience

Using the improved OCI Control Center:

• Alert visibility is improved
• Resource identification is quicker
• Navigation is faster
• Root cause investigation starts immediately

This can significantly reduce Mean Time To Resolution (MTTR).

Benefits for Oracle DBAs

Operational Efficiency

Less time spent navigating the console.

Improved Visibility

Critical resources are easier to monitor.

Faster Troubleshooting

Quicker access to monitoring and diagnostic information.

Better User Experience

Simplified workflows improve productivity.

Centralized Management

Multiple OCI services can be managed more effectively.

Best Practices

To maximize the benefits of the OCI Control Center:

Use Compartments Properly

Separate:

• Production
• Development
• Testing

resources into dedicated compartments.

Configure Monitoring Alarms

Create alarms for:

• CPU utilization
• Memory usage
• Storage thresholds
• Backup failures

Use Resource Tagging

Implement consistent tagging standards for:

• Databases
• Compute instances
• Storage resources

Regularly Review Dashboards

Monitor dashboard metrics daily to identify trends before issues occur.

Conclusion

The latest OCI Control Center enhancements are focused on improving usability, visibility, and operational efficiency. While these updates may appear minor at first glance, they provide significant value for Oracle DBAs managing complex cloud environments.

The improved dashboard experience, faster navigation, better monitoring integration, and enhanced resource visibility help administrators spend less time searching for information and more time optimizing database performance and availability.

For Oracle professionals working with OCI, these enhancements contribute to a smoother cloud management experience and support faster operational decision-making.

Oracle Database Security Checklist for 2026

 

Introduction

For many organizations, database security is still associated with passwords and firewall rules. In reality, modern Oracle database security extends far beyond authentication.

In 2026, Oracle DBAs must secure databases against:

• Ransomware attacks
• Credential theft
• Privilege abuse
• SQL injection
• Insider threats
• Cloud misconfigurations
• AI-assisted cyberattacks

This article presents a practical security checklist based on real-world Oracle DBA operations and Oracle 23ai best practices.

Security Philosophy Every DBA Should Follow

I use a simple principle:

Assume the database will be attacked and design controls accordingly.

Security should not depend on a single layer.

A secure Oracle environment combines:

• Identity Security
• Network Security
• Data Security
• Monitoring
• Auditing
• Backup Protection
• Disaster Recovery

Layer 1 – User and Account Security

Review Default Accounts

Many environments still contain unused accounts.

Check:

SELECT username,
       account_status
FROM dba_users
ORDER BY username;

Review:

• ANONYMOUS
• APEX_PUBLIC_USER
• DBSNMP
• OUTLN
• SYSTEM

Lock unused accounts.

ALTER USER username ACCOUNT LOCK;

DBA Recommendation

Perform quarterly user-account reviews.

Enforce Strong Password Policies

Use Oracle Profiles.

Example:

CREATE PROFILE SECURE_PROFILE
LIMIT
FAILED_LOGIN_ATTEMPTS 5
PASSWORD_LIFE_TIME 90
PASSWORD_REUSE_TIME 365;

Recommended:

Setting	Value
Minimum Length	14+
Expiration	90 Days
Failed Attempts	5
Complexity	Enabled

Layer 2 – Privilege Security

Identify Powerful Users

Check privileged accounts:

SELECT *
FROM dba_role_privs
WHERE granted_role IN
('DBA',
 'SYSDBA',
 'SYSOPER');

Questions every DBA should ask:

• Does the user still need access?
• Is access temporary?
• Is access documented?

Avoid Granting DBA Role

Many organizations grant DBA role unnecessarily.

Instead:

Grant only required privileges.

Example:

GRANT CREATE SESSION TO app_user;

GRANT CREATE TABLE TO app_user;

Principle:

Least Privilege Access

Layer 3 – Network Security

Restrict Listener Access

Check listener configuration.

Review:

lsnrctl status

Ensure:

• Listener not exposed publicly
• Only application servers can connect
• Admin access restricted

Enable SQL*Net Encryption

Verify encryption settings.

SQLNET.ENCRYPTION_SERVER = REQUIRED
SQLNET.CRYPTO_CHECKSUM_SERVER = REQUIRED

Benefits:

• Data protection in transit
• Protection from packet sniffing
• Regulatory compliance

Layer 4 – Data Encryption

Verify Transparent Data Encryption (TDE)

TDE should be standard in 2026.

Check wallet:

SELECT wallet_type,
       status
FROM v$encryption_wallet;

Expected:

OPEN

Benefits:

• Datafile encryption
• Backup encryption
• Regulatory compliance

Encrypt Sensitive Columns

Examples:

• Aadhaar numbers
• PAN numbers
• Credit card data
• Banking details

Implement column-level encryption where required.

Layer 5 – Auditing

Enable Unified Auditing

Verify:

SELECT value
FROM v$option
WHERE parameter='Unified Auditing';

Monitor:

• Login activity
• Failed logins
• Privilege grants
• Sensitive table access

Audit SYS Activities

Many breaches involve privileged accounts.

Example:

AUDIT ALL BY SYS;

Review regularly.

Layer 6 – Oracle 23ai SQL Firewall

Why SQL Firewall Matters

One of the most important security features introduced in recent Oracle releases.

SQL Firewall:

• Learns approved SQL patterns
• Blocks unauthorized SQL
• Protects against injection attacks

Ideal for:

• Banking applications
• ERP systems
• Customer portals

Layer 7 – Backup Security

Encrypt RMAN Backups

Example:

CONFIGURE ENCRYPTION FOR DATABASE ON;

Benefits:

• Backup theft protection
• Cloud storage security
• Compliance readiness

Validate Backup Recoverability

Never assume backups are usable.

Perform:

RESTORE VALIDATE DATABASE;

Monthly validation is recommended.

Layer 8 – Patch Management

Track Oracle Release Updates

Check version:

SELECT banner_full
FROM v$version;

Maintain:

• Quarterly RUs
• Security patches
• One-off critical fixes

My Patching Rule

If a patch fixes:

• Security vulnerability
• Data corruption issue
• RAC stability issue

It should be prioritized.

Layer 9 – Monitoring and Threat Detection

Monitor Failed Logins

Example:

SELECT username,
       timestamp
FROM dba_audit_session
WHERE returncode <> 0;

Look for:

• Brute-force attacks
• Password guessing
• Service account misuse

Monitor Privilege Escalation

Track:

GRANT DBA;
GRANT SYSDBA;
GRANT ANY PRIVILEGE;

Unexpected grants should trigger alerts.

Layer 10 – Cloud Security (OCI)

For OCI-hosted databases:

Review:

IAM Policies

Follow least-privilege principles.

NSG Rules

Allow only required ports.

Common:

Port	Purpose
22	SSH
1521	Listener
5500	EM Express

Restrict source IPs.

OCI Vault

Store:

• TDE Keys
• Secrets
• API Keys
• Wallet Passwords

Never store secrets in scripts.

Layer 11 – Disaster Recovery Security

Review Data Guard configuration.

Verify:

SELECT protection_mode
FROM v$database;

Ensure:

• Standby database encrypted
• Backups encrypted
• DR access controlled

Security Health Scorecard

Every quarter I recommend reviewing:

Control	Status
Default Accounts Reviewed	✓
Password Policy Verified	✓
TDE Enabled	✓
Unified Auditing Enabled	✓
RMAN Encryption Enabled	✓
SQL Firewall Enabled	✓
Listener Restricted	✓
Patching Current	✓
Backup Validation Tested	✓
DR Security Reviewed	✓

Security Trends DBAs Must Watch in 2026

AI-Assisted Attacks

Attackers increasingly use AI tools to:

• Generate malicious SQL
• Automate vulnerability discovery
• Accelerate credential attacks

Zero Trust Database Security

Trust no user by default.

Continuously verify:

• Identity
• Device
• Access pattern
• Location

Security Automation

Future-ready DBAs automate:

• User reviews
• Privilege reviews
• Audit analysis
• Patch compliance
• Backup validation

Final Thoughts

Database security is no longer a yearly audit activity. It is an everyday operational responsibility.

A modern Oracle DBA must think like a security engineer, continuously reviewing access, encryption, auditing, backups, and cloud configurations.

In my experience, the strongest Oracle environments are not the ones with the most tools—they are the ones where security reviews are performed consistently and operational discipline is maintained.

Designing an AI-Powered Oracle DBA Copilot Using OCI Generative AI and Oracle Database 23ai

 

Introduction

Artificial Intelligence is rapidly transforming how IT operations are managed. Database Administration is no exception. Traditionally, Oracle DBAs spend a significant amount of time monitoring databases, reviewing alerts, troubleshooting incidents, analyzing performance reports, and supporting application teams.

As Oracle Database 23ai introduces AI-native capabilities and Oracle Cloud Infrastructure (OCI) expands its Generative AI services, a new possibility emerges: an AI-powered DBA Copilot.

This article explores a conceptual architecture for building an Oracle DBA Copilot using Oracle Database 23ai and OCI Generative AI. The objective is not to replace DBAs but to enhance productivity, accelerate troubleshooting, and simplify database operations.

---

What Is a DBA Copilot?

A DBA Copilot is an intelligent assistant that helps database administrators perform daily operational tasks through natural language interactions.

Instead of manually reviewing reports, logs, and monitoring dashboards, a DBA could ask questions such as:

• Why is my database slow today?
• Are my backups healthy?
• Is Data Guard synchronized?
• Which tablespace is growing fastest?
• What caused yesterday’s ORA error?

The copilot would analyze available database information and provide meaningful responses along with recommended actions.

---

Why Do DBAs Need an AI Copilot?

Modern database environments generate a massive amount of operational data.

Examples include:

• Alert logs
• AWR reports
• ASH reports
• RMAN backup logs
• Data Guard statistics
• OEM alerts
• Application performance metrics
• Incident tickets

Although monitoring tools can identify issues, DBAs often spend considerable time investigating root causes and correlating information from multiple sources.

An AI-powered copilot can assist by:

• Reducing investigation time
• Providing contextual recommendations
• Identifying recurring issues
• Improving operational efficiency
• Helping junior DBAs learn faster

---

Oracle Technologies That Make This Possible

Oracle Database 23ai

Oracle Database 23ai introduces capabilities that support AI-driven applications, including:

• AI Vector Search
• Select AI
• Enhanced developer productivity features
• Improved integration with AI services

These features allow database information and operational knowledge to be stored and searched intelligently.

OCI Generative AI

OCI Generative AI provides large language models that can:

• Understand natural language
• Summarize complex information
• Generate recommendations
• Explain incidents in simple terms

When combined with database telemetry, these capabilities create the foundation for a DBA Copilot.

---

Conceptual Architecture

The proposed solution consists of four logical layers.

Layer 1 – Operational Data Collection

The copilot gathers information from various sources:

• Oracle Database
• AWR Reports
• Alert Logs
• RMAN Backup Logs
• Data Guard Statistics
• Monitoring Alerts
• Internal Runbooks
• Incident Management Systems

This information forms the operational knowledge base.

---

Layer 2 – Knowledge Repository

Historical incidents and operational documentation are stored in Oracle Database 23ai.

Examples include:

• ORA error resolutions
• Backup troubleshooting procedures
• Data Guard recovery steps
• Performance tuning recommendations
• Standard operating procedures

This repository becomes the memory of the copilot.

---

Layer 3 – AI Intelligence Layer

OCI Generative AI processes user questions and retrieves relevant information from the knowledge repository.

The AI engine can:

• Understand intent
• Search historical incidents
• Correlate operational data
• Generate contextual responses

Rather than displaying raw metrics, the system explains what the data means.

---

Layer 4 – DBA Interaction Layer

DBAs interact with the copilot using natural language.

Potential interfaces include:

• Oracle APEX
• Web Portals
• Collaboration Platforms
• Mobile Applications

The focus is on simplicity and accessibility.

---

Example Use Cases

Use Case 1 – Database Health Assessment

DBA Question

"Is my database healthy?"

Possible Copilot Response

Database health is currently stable.

• CPU utilization within normal range
• No blocking sessions detected
• Backup completed successfully
• Data Guard synchronization healthy

No immediate action required.

Instead of checking multiple dashboards, the DBA receives a consolidated status summary.

---

Use Case 2 – Tablespace Growth Prediction

DBA Question

"Which tablespace is likely to become full first?"

Possible Copilot Response

The USERS tablespace is currently 89% utilized.

Based on historical growth patterns, it may reach capacity within the next two weeks.

Recommended Action:
Review storage allocation and consider adding additional space.

This allows proactive capacity planning.

---

Use Case 3 – ORA Error Analysis

DBA Question

"What caused ORA-01653?"

Possible Copilot Response

The error occurred because the target tablespace did not have sufficient free space available.

Similar incidents were observed previously during month-end processing.

Recommended Action:
Add a datafile or enable autoextend for the affected tablespace.

The copilot provides both diagnosis and guidance.

---

Use Case 4 – Backup Validation

DBA Question

"Are my backups healthy?"

Possible Copilot Response

All scheduled RMAN backups completed successfully.

Backup duration increased by 18% compared to last month, likely due to database growth.

Recommendation:
Review backup retention policies and parallelism settings.

This goes beyond simple success or failure reporting.

---

Use Case 5 – Performance Troubleshooting

DBA Question

"Why was application performance slow yesterday?"

Possible Copilot Response

Database response time increased during peak business hours.

Primary contributing factors:

• High CPU utilization
• Increased reporting workload
• Elevated I/O activity

The most resource-intensive SQL statement accounted for approximately 40% of total database activity during the affected period.

This helps DBAs focus their investigation quickly.

---

Benefits of an AI DBA Copilot

Organizations could realize several advantages from such a solution.

Faster Incident Resolution

AI-assisted analysis can significantly reduce investigation time.

Improved Knowledge Retention

Operational knowledge remains available even when team members change.

Better Operational Visibility

The copilot can present information in a simple and understandable format.

Increased Productivity

DBAs can spend less time gathering information and more time solving business problems.

Faster Onboarding

Junior DBAs can learn from AI-generated explanations and recommendations.

---

Challenges to Consider

While the concept is promising, organizations should also consider:

• Data security requirements
• Access controls
• Sensitive information handling
• Accuracy of AI-generated responses
• Governance and auditing requirements

AI should assist decision-making, but final operational actions should remain under DBA control.

---

Looking Ahead

As Oracle continues to expand AI capabilities across its database and cloud platforms, the role of the DBA is evolving.

Future DBA copilots may provide:

• Automated incident summaries
• Predictive capacity planning
• Intelligent SQL tuning recommendations
• Self-healing operational workflows
• Voice-enabled database administration

The combination of Oracle Database 23ai and OCI Generative AI creates exciting opportunities for organizations seeking more intelligent database operations.

---

Conclusion

The future of database administration is becoming increasingly intelligent. By combining Oracle Database 23ai with OCI Generative AI, organizations can envision a DBA Copilot capable of transforming operational data into actionable insights.

While this remains a conceptual design, it demonstrates how Oracle's latest AI technologies can be leveraged to simplify database management, improve operational efficiency, and support faster decision-making.

As Oracle professionals, exploring these possibilities today can help us prepare for the next generation of database operations.

 

How to Deploy Oracle 23ai Database on OCI – Complete DBA Implementation Guide.

Introduction

Oracle 23ai is Oracle’s latest AI-enabled database release designed for modern enterprise workloads, AI applications, vector search, JSON-relational architecture, and autonomous operations. Deploying Oracle 23ai on Oracle Cloud Infrastructure (OCI) provides DBAs with high performance, scalability, and enterprise-grade security.

In this guide, we will deploy Oracle 23ai Database on OCI from scratch using:

• Virtual Cloud Network (VCN)

• Public and Private Subnets

• Network Security Groups (NSG)

• Oracle DB System

• SSH Access Configuration

This article is written from a real DBA operational perspective instead of a basic cloud tutorial.

Architecture Overview

Before deployment, let us understand the architecture.

Components Used

Component	Purpose
VCN	Private cloud network for OCI resources
Public Subnet	Used for Bastion / external access
Private Subnet	Used for Database deployment
NSG	Security-level traffic control
Internet Gateway	Internet connectivity
Route Table	Controls network routing
Oracle DB System	Hosts Oracle 23ai database
SSH Key Pair	Secure server access

Target Architecture

The deployment architecture follows enterprise security standards.

Laptop
   |
SSH
   |
Public IP
   |
OCI Bastion / Public Subnet
   |
Private Subnet
   |
Oracle 23ai DB System

Prerequisites

Before starting deployment ensure:

• OCI account is active

• User has Administrator privileges

• SSH client installed

• Oracle Cloud region selected

• OCI Compartment created

Step 1 – Login to OCI Console

Open OCI Console.

Navigate to:

Oracle Cloud Console → Identity & Security → Compartments

Create a new compartment.

Example:

Name: PROD-DBA-LAB
Description: Oracle 23ai Deployment Lab

Compartments help isolate cloud resources.

Step 2 – Create Virtual Cloud Network (VCN)

What is VCN?

VCN acts like a private data center network inside OCI.

Navigate:

Networking → Virtual Cloud Networks → Create VCN

VCN Configuration

Parameter	Value
Name	OCI-23AI-VCN
CIDR Block	10.0.0.0/16
DNS Resolution	Enabled

Click:

Create VCN

Step 3 – Create Internet Gateway

Navigate:

VCN → Internet Gateways → Create Internet Gateway

Configuration:

Parameter	Value
Name	OCI-IGW
Enabled	Yes

Purpose:

• Enables internet communication

• Required for package downloads and updates

Step 4 – Create Route Table

Navigate:

VCN → Route Tables → Create Route Table

Add route rule:

Destination	Target
0.0.0.0/0	Internet Gateway

This allows outbound internet access.

Step 5 – Create Subnets

We will create:

1. Public Subnet

2. Private Subnet

Step 5A – Create Public Subnet

Navigate:

VCN → Subnets → Create Subnet

Configuration:

Parameter	Value
Name	PUBLIC-SUBNET
CIDR	10.0.1.0/24
Type	Regional
Public IP	Enabled
Route Table	OCI-RT

Purpose:

• Bastion access

• SSH connectivity

• Jump server access

Step 5B – Create Private Subnet

Configuration:

Parameter	Value
Name	PRIVATE-DB-SUBNET
CIDR	10.0.2.0/24
Public IP	Disabled
Route Table	OCI-RT

Purpose:

• Secure Oracle Database deployment

• Internal traffic only

Step 6 – Create Network Security Group (NSG)

Why NSG?

NSG provides instance-level traffic filtering.

Navigate:

Networking → Network Security Groups

Create NSG:

Name: OCI-23AI-NSG

Step 7 – Configure NSG Rules

Ingress Rules

Source	Port	Protocol	Purpose
Your Public IP	22	TCP	SSH Access
Application Server	1521	TCP	Oracle Listener
Internal Network	5500	TCP	EM Express

Egress Rules

Allow all outbound traffic.

Step 8 – Generate SSH Key Pair

Linux / macOS

Run:

ssh-keygen -t rsa -b 4096

Windows (PowerShell)

ssh-keygen

Files generated:

File	Purpose
id_rsa	Private Key
id_rsa.pub	Public Key

Important:

Never share private keys.

Step 9 – Create Oracle 23ai DB System

Navigate:

Oracle Database → Base Database Service → Create DB System

Step 10 – Configure DB System

Basic Information

Parameter	Value
DB System Name	OCI23AI-DB
Compartment	PROD-DBA-LAB
Availability Domain	AD-1
Shape	VM.Standard.E5.Flex
OCPU	2
Memory	32 GB

Step 11 – Configure Networking

Parameter	Value
VCN	OCI-23AI-VCN
Subnet	PRIVATE-DB-SUBNET
NSG	OCI-23AI-NSG
Hostname	oci23ai-db

Step 12 – Database Configuration

Database Details

Parameter	Value
Database Version	Oracle 23ai
Database Name	ORCL23AI
PDB Name	ORCLPDB1
Character Set	AL32UTF8
Workload Type	OLTP

Step 13 – Upload SSH Public Key

Paste contents of:

id_rsa.pub

OCI injects this key into the server during provisioning.

Step 14 – Create the DB System

Click:

Create DB System

Provisioning typically takes:

20 to 40 minutes

Step 15 – Verify Deployment

After deployment verify:

Database Status

Available

Listener Status

lsnrctl status

Database Status

sqlplus / as sysdba

Then:

select name,open_mode from v$database;

Expected:

READ WRITE

Step 16 – SSH Access to Oracle Server

SSH Command

ssh -i id_rsa opc@<PUBLIC-IP>

Switch to Oracle user:

sudo su - oracle

Step 17 – Verify Oracle 23ai Features

Connect database:

sqlplus / as sysdba

Check version:

select banner_full from v$version;

Expected output:

Oracle Database 23ai Enterprise Edition

Step 18 – Configure Automatic Backups

Navigate:

DB System → Backup Configuration

Enable:

• Automatic backups

• Recovery window

• Object storage backup

Recommended:

Setting	Recommended Value
Backup Window	Night Time
Retention	30 Days
Incremental Backup	Enabled

Step 19 – Enable Monitoring and Alerts

OCI monitoring helps DBAs proactively identify issues.

Navigate:

Observability & Management → Monitoring

Create alerts for:

• CPU utilization

• Tablespace usage

• Memory pressure

• Backup failures

• Storage growth

Step 20 – Security Best Practices

Recommended Security Standards

1. Use Private Subnet for Databases

Never expose database servers directly to internet.

2. Restrict SSH Access

Allow SSH only from office or VPN IP.

3. Enable TDE

Transparent Data Encryption should remain enabled.

4. Rotate SSH Keys

Rotate keys periodically.

5. Enable Audit Policies

Monitor database login activities.

DBA Operational Validation Checklist

Validation	Status
Listener Running	Verified
Database Open	Verified
SSH Access	Verified
NSG Rules Applied	Verified
Backup Enabled	Verified
Monitoring Enabled	Verified

Common Deployment Issues

Issue 1 – SSH Timeout

Cause:

• NSG rule missing

• Port 22 blocked

Solution:

• Verify ingress rules

• Verify public IP

Issue 2 – Listener Not Reachable

Cause:

• Port 1521 blocked

Solution:

• Add NSG ingress rule

Issue 3 – Database Creation Failed

Cause:

• Insufficient quota

• Wrong shape

Solution:

• Verify tenancy limits

Real DBA Recommendations

Recommended Shapes

Environment	Shape Recommendation
Dev	VM.Standard.E4.Flex
Test	VM.Standard.E5.Flex
Production	Exadata / DenseIO

Why Oracle 23ai on OCI?

Key Benefits

• AI-ready database engine

• Integrated vector search

• High scalability

• Enterprise-grade HA

• Built-in security

• Automated patching

• Cloud-native architecture