Tuesday, May 26, 2026

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

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:

Public Subnet
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

Saturday, May 9, 2026

OCI Cost Optimization Guide for Database Workloads

Cloud adoption is growing rapidly, but many organizations migrating Oracle databases to Oracle Cloud Infrastructure (OCI) often face an unexpected challenge: rising monthly cloud bills.

In most environments, database workloads consume a major share of cloud resources through:

Compute instances
Block volumes
Backup storage
Data transfer
Monitoring and logging services

This guide explains practical cost optimization methods specifically for Oracle database workloads on OCI.

Why OCI Database Costs Increase

The most common reasons for high OCI bills are:

1. Oversized Compute Instances

Many teams migrate on-premises workloads to OCI using the same sizing assumptions.

Example:

Production database requires 8 OCPUs
Team provisions 32 OCPUs “for safety”

Result:

4x unnecessary compute cost

Recommendation:
Monitor:

CPU utilization
Memory usage
Load trends

Target:

CPU average utilization between 40–70%

2. Idle Non-Production Databases

Development, UAT, and testing databases often run 24/7 unnecessarily.

Typical issue:

Dev DB active only during office hours
Still billed for full month

Cost Optimization Strategy

Schedule automatic shutdown/startup.

Example schedule:

Start: 8 AM
Stop: 8 PM
Weekends off

Potential savings:

50–65% on non-prod compute costs

3. Storage Overprovisioning

Many OCI environments allocate excessive block storage.

Common pattern:

2 TB allocated
500 GB actually used

Best Practice

Review:


SELECT tablespace_name,
       ROUND(SUM(bytes)/1024/1024/1024,2) size_gb
FROM dba_data_files
GROUP BY tablespace_name;

Actions:

Resize unused volumes
Archive old data
Move historical backups to cheaper storage tiers

4. Backup Storage Cost Explosion

RMAN backups accumulate quickly.

Typical issue:

Daily full backups retained for 90+ days

This increases:

Object storage usage
Archive costs

Recommended Backup Policy

Production:

Weekly full backup
Daily incremental backup
Archive log backup every 30 mins

Retention:

14–30 days online
Older backups archived

Example RMAN:


CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 14 DAYS;
DELETE OBSOLETE;

5. Unused Block Volumes and Snapshots

After migrations or server rebuilds:

Old block volumes remain attached
Snapshots never deleted

Monthly hidden cost source.

Audit Checklist

Review:

Unattached block volumes
Old boot volumes
Snapshot age > 30 days

Delete if unused.

6. High Logging and Monitoring Costs

OCI Logging and Monitoring can grow silently.

Common issue:

Debug logs retained indefinitely

Best Practices

Reduce retention:

Dev logs: 7 days
Test logs: 14 days
Prod logs: 30–60 days

Disable unnecessary verbose logging.

7. Wrong Database Deployment Model

Many organizations use expensive deployment types unnecessarily.

Compare:

Workload	Recommended Option
Small dev DB	Compute VM + Standard DB
Enterprise HA	Exadata / RAC
Variable workload	Autonomous DB
Archive/reporting	Lower compute shape

Choose based on actual workload.

8. Network Egress Charges

Cross-region traffic increases costs.

Examples:

Backup replication
Data Guard sync
Application traffic

Reduce Cost By

Keeping workloads in same region
Reviewing outbound traffic
Compressing backup transfers

9. License Cost Optimization

For BYOL environments:

Review:

Actual processor usage
Edition requirements

Sometimes Enterprise Edition is used where Standard Edition is sufficient.

Potential savings can be significant.

10. Monthly OCI Cost Governance Framework

Implement monthly review.

Checklist:

Compute

Idle instances
CPU utilization
Shape right-sizing

Storage

Unused block volumes
Snapshot cleanup
Backup growth

Database

License review
Storage growth trend
DR cost validation

Monitoring

Log retention
Alert efficiency

Sample Monthly Cost Review Script

Track storage growth:


SELECT owner,
       segment_type,
       ROUND(SUM(bytes)/1024/1024/1024,2) gb
FROM dba_segments
GROUP BY owner, segment_type
ORDER BY gb DESC;

Top space consumers can be archived or optimized.

Estimated Savings by Optimization Area

Optimization Area	Savings Potential
Auto shutdown non-prod	50–65%
Right sizing compute	20–40%
Backup retention cleanup	15–30%
Storage optimization	10–25%
Logging optimization	5–15%

Final Thoughts

OCI offers strong pricing flexibility, but cloud costs increase quickly without governance.

A DBA should monitor not only database health but also:

Resource efficiency
Backup growth
Storage utilization
Compute sizing
DR cost impact

Cost optimization is now a critical DBA responsibility in cloud environments.

Keywords for SEO

OCI cost optimization
Oracle cloud cost reduction
OCI database cost management
Oracle DBA cloud optimization
OCI storage optimization