Installing Oracle AI Database 26ai on Oracle Linux 10

Starting with Oracle AI Database 26ai Release Update 23.26.2, the Linux x86–64 operating system is supported with the following minimum supported versions:

Oracle Linux 10 with the Unbreakable Enterprise Kernel 8: 6.12.0–104.43.4.2.el10uek.x86_64 or later
Oracle Linux 10 with the Red Hat Compatible Kernel: 6.12.0–55.40.1.0.1.el10_0.x86_64 or later

In this article, we will walk through the installation of Oracle AI Database 26ai on Oracle Linux 10.2.

The installation process can be divided into two main parts. First, we prepare the operating system for Oracle Database by configuring the hostname, local package repository, required packages, Oracle user and groups, kernel parameters, resource limits, directories, and environment variables.

In the second part, we install the Oracle Database software, apply the required Release Update (RU), execute the required root scripts, and finally create a database using Database Configuration Assistant (DBCA).

1. Preparing Oracle Linux 10 for Oracle Database Installation

Before installing Oracle AI Database 26ai, we need to prepare the operating system.

The following sections describe the main preparation steps.

Step 1: Configure the Hostname

The first step is to configure the hostname of the Oracle Linux server.

the hostname is set to OL10.

First, edit /etc/hostname:

[root@localhost ~]# vi /etc/hostname
OL10

We also configure /etc/hosts:

[root@localhost ~]# vi /etc/hosts
# Loopback entries; do not change.
# For historical reasons, localhost precedes localhost.localdomain:
127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4
::1         localhost localhost.localdomain localhost6 localhost6.localdomain6
# See hosts(5) for proper format and other examples:
# 192.168.1.10 foo.example.org foo
# 192.168.1.13 bar.example.org bar

192.168.1.40 OL10

The hostname can be changed immediately without rebooting:

[root@localhost ~]# hostname OL10
[root@localhost ~]# su -
Last login: Sat Aug 22 15:36:26 EDT 2026 from 192.168.1.35 on pts/1
[root@OL10 ~]#

Step 2: Configure a Local Oracle Linux 10 Repository

The next step is to make the Oracle Linux installation media available as a local package repository.

This is particularly useful in environments where the server does not have direct Internet access.

First, create a mount point:

[root@OL10 ~]# mkdir /dvd

Then mount the Oracle Linux installation media:

[root@OL10 ~]# mount /dev/sr0 /dvd
mount: /dvd: WARNING: source write-protected, mounted read-only.

Now, we can configure YUM/DNF to use it.

First, remove the existing repository definitions:

[root@OL10 ~]# rm -rf /etc/yum.repos.d/*

Create a new repository file:

[root@OL10 ~]# vi /etc/yum.repos.d/OEL10.repo
[InstallMedia-BaseOS]
name=OEL10 - BaseOS
metadata_expire=-1
gpgcheck=0
enabled=1
baseurl=file:///dvd/BaseOS/

[InstallMedia-AppStream]
name=OEL10 - AppStream
metadata_expire=-1
gpgcheck=0
enabled=1
baseurl=file:///dvd/AppStream/

Step 3: Install the Oracle AI Database Preinstallation Package

Oracle provides a preinstallation RPM for Oracle AI Database 26ai. This package performs the OS-level preparation required by Oracle, including:

Installing the required RPM dependencies.
Configuring the required kernel parameters.
Configuring the required user limits.
Creating and configuring the required Oracle groups and users.
Applying other OS settings required for Oracle AI Database 26ai.

In this lab, the following package is used:

oracle-ai-database-preinstall-26ai-1.0-1.el10.x86_64.rpm

We install it using:

[root@OL10 source]# yum -y localinstall oracle-ai-database-preinstall-26ai-1.0-1.el10.x86_64.rpm

The package automatically identifies and installs many of the packages required by Oracle Database 26ai.

For example, the installation pulls packages such as:

bc
binutils
elfutils-libelf
fontconfig
glibc
glibc-devel
glibc-headers
ksh
libaio
libgcc
libibverbs
libstdc++
libvirt-libs
libxcb
libX11
libXau
libXi
libXrender
libXtst
libxcrypt-compat
make
policycoreutils
policycoreutils-python-utils
smartmontools
sysstat

and their required dependencies.

The preinstallation package also performs important Oracle operating-system preparation tasks.

For example, after installing it, the following files are available:

[root@OL10 ~]# ls -l /etc/security/limits.d
total 4
-rw-r--r--. 1 root root 1245 Aug 22 15:48 oracle-ai-database-preinstall-26ai.conf

The corresponding sysctl configuration file is also created:

[root@OL10 ~]# ls -lh /etc/sysctl.d/99-oracle-ai-database-preinstall-26ai-sysctl.conf
-rw-r--r--. 1 root root 2.4K Aug 22 15:48 /etc/sysctl.d/99-oracle-ai-database-preinstall-26ai-sysctl.conf

Step 4: Configure Firewall and SELinux

The next step concerns the operating-system security services.

Whether these services should be disabled depends on the environment and security requirements.

Firewall

In a test or lab environment, the firewall can be stopped and disabled:

 [root@OL10 ~]# systemctl stop firewalld
 [root@OL10 ~]# systemctl disable firewalld
Removed '/etc/systemd/system/multi-user.target.wants/firewalld.service'.
Removed '/etc/systemd/system/dbus-org.fedoraproject.FirewallD1.service'.

The Oracle Database software does not inherently require the firewall to be disabled.

In a production environment, it is generally preferable to keep the firewall enabled and allow only the required Oracle Database and listener ports.

SELinux

The lab configuration also sets SELinux to disabled:

[root@OL10 ~]# vi /etc/sysconfig/selinux
SELINUX=disabled

Again, disabling SELinux is not inherently required simply to install Oracle Database 26ai. The appropriate configuration depends on the organization’s security policies and the Oracle software components being deployed.

Step 5: Create the Oracle Directories

Next, we create the directories that will be used for the Oracle software and Oracle base.

[root@OL10 ~]# mkdir /oracle/26.2 /oracle/base /oraInventory -p

Then change their ownership:

[root@OL10 ~]# chown -R oracle:oinstall /oracle /oraInventory

The /oraInventory directory stores information about installed Oracle products and their configuration.

Step 6: Configure Oracle Environment Variables

The Oracle environment variables are configured in the Oracle user’s login profile.

[oracle@OL10 ~]$ vi .bash_profile
export ORACLE_SID=db26ai
export ORACLE_BASE=/oracle/base
export ORACLE_HOME=/oracle/26.2
export PATH=${PATH}:$HOME/bin:$ORACLE_HOME/bin:/oracle/26.2/bin/
export LD_LIBRARY_PATH=$ORACLE_HOME/lib:/lib:/usr/lib
export CLASSPATH=$ORACLE_HOME/jlib:$ORACLE_HOME/rdbms/jlib
export TMP=/tmp
export TMPDIR=$TMP

2. Installing Oracle AI Database 26ai

After completing the operating-system preparation, we can start installing the Oracle Database software.

Extract the Oracle Database Software and Patches

First, extract the Oracle AI Database 26ai software into the Oracle Home directory:

 [oracle@OL10 ~]$ unzip /source/LINUX.X64_2326100_db_home.zip -d /oracle/26.2/

The Oracle Home is now ready for the installation.

Next, extract the required OPatch utility for 23.26.2:

[oracle@OL10 ~]$ unzip /source/p6880880_236R2_Linux-x86-64.zip -d /oracle/26.2/

Then, extract the 23.26.2 Release Update patch into a separate directory:

[oracle@OL10 ~]$ unzip /source/p39088031_230000_26R2_Linux-x86-64.zip -d /patch26.2/

Applying the Release Update and Launching the Installer

Before starting the Oracle Database installation, apply the 23.26.2 Release Update (RU) to the Oracle Home.

[oracle@OL10 ~]$ cd /oracle/26.2/
[oracle@OL10 26.2]$ ./runInstaller -applyRU /patch26.2/39088031/39093711/

Two operations will be performed: first the home will be patched, and then the installer will be launched.

Operation 1:

Preparing the home to patch...
Applying the patch /patch26.2/39088031/39093711/...
Successfully applied the patch.
The log can be found at: /tmp/InstallActions2026-08-22_04-02-40PM/installerPatchActions_2026-08-22_04-02-40PM.log

Operation 2:

Launching Oracle AI Database Setup Wizard...

The installer first patches the Oracle Home and, after successfully applying the RU, automatically launches the Oracle AI Database Setup Wizard to continue the installation.

Step 1: Choose the Installation Option

The first step determines whether the Oracle software should be installed only or whether a database should also be created as part of the installation.

For a software-only installation, select the option that installs the database software without creating a database.

In this lab, the Oracle software is installed first and the database is created afterward using DBCA.

Step 2: Select Single Instance Database Installation

“Single instance database installation” is appropriate when Oracle Database is being installed on a standalone server rather than an Oracle RAC environment.

Oracle RAC requires additional Grid Infrastructure and cluster configuration, while a single-instance installation does not.

Step 3: Specify Oracle Base

The Oracle Home is already determined by the location from which the installer is launched.

The Oracle Base can be reviewed or changed during installation.

Step 4: Specify the Oracle Inventory

The installer asks for the location of the Oracle Inventory. The Oracle Inventory contains information about Oracle products installed on the server.

Step 5: Operating System Groups

The installer automatically identifies the operating-system groups created for Oracle. These groups provide different levels of administrative privileges for Oracle software and database administration.

The preinstallation package prepares the required operating-system configuration automatically.

Step 6: Root Script Configuration

At the end of the installation, Oracle requires root-level scripts to be executed.

The installer can either request the root password and execute the scripts automatically or allow the DBA to execute them manually.

Step 7: Prerequisite Checks

The installer performs a series of prerequisite checks before starting the installation.

These checks can identify problems with:

Operating-system packages
Memory
Swap
Disk space
Kernel configuration
Resource limits
Operating-system configuration

Step 8: Installation Summary

The installer displays a summary of the selected configuration.

Review the settings carefully before starting the installation.

Step 9: Install the Oracle Software

After confirming the configuration, the installer begins copying and configuring the Oracle software.

At this point, the Oracle Home is populated and the required Oracle components are installed.

Executing the Root Scripts

After the Oracle software installation finishes, two root scripts must be executed.

[root@OL10 ~]# /oraInventory/orainstRoot.sh
Changing permissions of /oraInventory.
Adding read,write permissions for group.
Removing read,write,execute permissions for world.
Changing groupname of /oraInventory to oinstall.
The execution of the script is complete.

[root@OL10 ~]# /oracle/26.2/root.sh
Performing root user operation.
The following environment variables are set as:
ORACLE_OWNER= oracle
ORACLE_HOME= /oracle/26.2
Enter the full pathname of the local bin directory: [/usr/local/bin]:
Copying dbhome to /usr/local/bin …
Copying oraenv to /usr/local/bin …
Copying coraenv to /usr/local/bin …
Creating /etc/oratab file…
Entries will be added to the /etc/oratab file as needed by
Database Configuration Assistant when a database is created
Finished running generic part of root script.
Now product-specific root actions will be performed.

Verifying the Oracle Software Installation

After the installation is complete, we can test SQL*Plus.

[oracle@OL10 ~]$ sqlplus "/as sysdba"
SQL*Plus: Release 23.26.2.0.0 - Production
Version 23.26.2.0.0

This confirms that the Oracle AI Database 26ai software has been installed successfully.

At this stage, however, the software installation and database creation are separate tasks. The next step is to create the database.

3. Creating the Database with DBCA

Oracle Database Configuration Assistant (DBCA) is used to create and configure the database.

[oracle@OL10 ~]$ dbca

Step 1: Create Database

DBCA can also be used to manage existing databases, but in this section our objective is to create a new database.

Step 2: Configuration Mode

DBCA provides different configuration modes.

If detailed control over the database configuration is required, select:

Advanced Configuration

For a straightforward installation, the typical configuration can be sufficient.

Advanced configuration is useful when the DBA needs to explicitly configure items such as storage, memory, database components, character set, connection mode, or other database properties.

Step 3: Database Type and Template

The next screen determines the database type and template.

For a standalone database, select:

Single Instance Database

For an Oracle RAC environment, the corresponding RAC option should be selected.

The template determines the initial database configuration.

Common templates include:

Custom Database
General Purpose or Transaction Processing
Data Warehouse

A Custom Database provides the greatest control over database configuration.

For a typical OLTP environment, General Purpose or Transaction Processing is normally an appropriate starting point.

In this lab, the default template is used.

Step 4: Database Identification

The database name and SID are configured on this screen.

For example, the lab environment uses:

ORACLE_SID=db26ai

The database name identifies the database, while the SID identifies the instance.

DBCA also provides an option to specify the PDB name.

If multiple PDBs are created through the relevant DBCA option, the specified PDB name can be used as the basis for their names.

There is also an option to create an empty container database if no user PDB is required during database creation.

Step 5: Database Storage

This screen determines where the database files will be stored.

Database files include:

Data files
Control files
Online redo logs

Oracle Managed Files (OMF) can also be enabled.

The storage layout should be designed according to the workload and availability requirements of the database.

Step 6: Fast Recovery Area and ARCHIVELOG

DBCA provides the option to configure the Fast Recovery Area (FRA).

The FRA provides a managed location for files such as:

Archived redo logs
RMAN backup-related files
Flashback logs

The database can also be configured to operate in ARCHIVELOG mode.

For production databases, ARCHIVELOG mode is generally important when backup and recovery requirements include online backups, point-in-time recovery, or other recovery features.

Step 7: Listener Configuration

The listener configuration can be performed during database creation.

DBCA can create a new listener or use an existing listener.

The Oracle listener is responsible for accepting incoming client connection requests and directing them to the appropriate database service.

Step 8: Database Security

DBCA also provides options for additional database security components, such as:

Database Vault
Oracle Label Security

These features should be enabled according to the organization’s security requirements.

Step 9: Memory Configuration

DBCA provides several approaches for configuring database memory.

The main approaches are:

1. Manual Shared Memory Management

With manual shared memory management, the DBA explicitly configures the individual memory components.

2. Automatic Shared Memory Management

With Automatic Shared Memory Management, Oracle manages the sizes of individual SGA components based on the configured memory settings.

3. Automatic Memory Management

Automatic Memory Management uses MEMORY_TARGET and allows Oracle to manage the SGA and PGA within the configured memory target.

The appropriate memory-management method depends on the operating system, Oracle version, workload, and DBA requirements.

Step 10: Database Sizing

The Sizing section allows the DBA to configure parameters such as:

Database block size
PROCESSES

The block size is an important database-level decision. If a non-default block size is required, the database should be created using an appropriate custom configuration.

The PROCESSES parameter controls the maximum number of operating-system user processes that can connect to the database.

Step 11: Character Set

The character set determines how character data is stored and interpreted.

The appropriate character set should be selected based on the applications and languages that will use the database.

Step 12: Connection Mode

The connection mode determines how sessions are handled by the Oracle server.

For this installation, select:

Dedicated Server

With dedicated server architecture, each client session is associated with a dedicated server process.

Step 13: Cloud Control Registration

DBCA can also provide configuration options for registering the database with Oracle Enterprise Manager Cloud Control.

Step 14: Database Passwords

DBCA requires passwords for administrative database accounts such as:

SYS
SYSTEM
PDBADMIN

Step 15: Create the Database

After reviewing all configuration options, select:

Create Database

DBCA now begins creating the database using the configuration selected in the previous steps.

Step 16: Configuration Summary

Before or during the database creation process, DBCA provides a summary of the selected configuration.

Step 17: Database Creation in Progress

DBCA now creates the database.

During this stage, Oracle creates and configures the required database components, including the container database and the configured PDB.

The duration of this process depends on the server’s CPU, memory, and storage performance.

Step 18: Database Creation Completed

When DBCA completes successfully, the wizard displays a confirmation that the database has been created.

4. Verifying the Database

The final step is to verify the database from SQL*Plus.

[oracle@OL10 ~]$ sqlplus "/as sysdba"

SQL*Plus: Release 23.26.2.0.0 - Production

Version 23.26.2.0.0

Connected to:
Oracle AI Database 26ai Enterprise Edition Release 23.26.2.0.0 - Production
Version 23.26.2.0.0

Now check the PDBs:

SQL> show pdbs

CON_ID CON_NAME OPEN MODE RESTRICTED
 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 

2 PDB$SEED READ ONLY NO

3 VAHID READ WRITE NO

This confirms that:

PDB$SEED is available in READ ONLY mode.
The user PDB VAHID is open in READ WRITE mode.

Search This Blog

Relational Databases