Oracle AI Database Postinstallation Tasks

Complete configuration tasks after you install Oracle AI Database.

You are required to complete some configuration tasks after Oracle AI Database is installed. In addition, Oracle recommends that you complete additional tasks immediately after installation. You must also complete product-specific configuration tasks before you use those products.

This chapter describes basic configuration only. Refer to product-specific administration and tuning guides for more detailed configuration and tuning information.

Downloading Release Update Patches

Download and install Oracle Release Updates (RUs) and Monthly Recommended Patches (MRPs) after installation by searching My Oracle Support by patch, bug, product, release, platform, or language criteria. Review each patch’s README before applying it. For Oracle AI Database 26ai, Oracle recommends out-of-place patching with gold images; OPatch and OPatchAuto remain available for in-place patching, while RUs are not supported for the Free release.

Oracle AI Database Patching

Oracle AI Database 26ai Release Updates are delivered as gold images for out-of-place patching or binary patches for in-place application with OPatch or OPatchAuto. Out-of-place patching involves downloading and extracting the gold image, creating a new Oracle home with runInstaller -setupDBHomeAs, and moving the database with DBCA or Oracle FPP Local Mode; in clustered environments, FPP commands must be run from one node and retried from that same node if they fail.

Unlocking Accounts and Resetting Oracle AI Database User Passwords

Most administrative accounts are locked or have revoked passwords after installation, so required accounts must be explicitly unlocked and assigned secure passwords. Review predefined and Oracle-maintained accounts carefully, avoid modifying accounts marked as Oracle maintained, and use SQL*Plus as SYSDBA with ALTER USER to lock, unlock, or reset accounts. EM Express is desupported in Oracle AI Database 26ai; use supported database management tools instead.

About Installing Oracle Autonomous Health Framework

Oracle Autonomous Health Framework is preinstalled with Oracle AI Database and provides proactive health checks and diagnostic collection across database, Grid Infrastructure, RAC, GoldenGate, Exadata, SuperCluster, Recovery Appliance, and related deployments. Updates are included with database Release Updates or available through My Oracle Support, and Oracle recommends maintaining the latest version.

Enabling and Disabling Oracle AI Database Options After Installation

Use the postinstallation chopt utility in ORACLE_HOME/bin to enable or disable supported database options such as Partitioning and Real Application Testing. The database must be stopped before running the command and restarted afterward; cloned or image-based installations enable all options by default. Oracle Advanced Analytics cannot be disabled with chopt, and OLAP-related technologies are deprecated.

Creating a Fast Recovery Area

Create a fast recovery area to centralize RMAN backups, archived logs, control-file backups, and database copies, enabling faster recovery and automatic obsolete-file management. Configure it with DB_RECOVERY_FILE_DEST and DB_RECOVERY_FILE_DEST_SIZE, preferably on a separate ASM disk group sized for several days of recovery data or more. Use ASMCA to create and configure the disk group, selecting an appropriate name, redundancy level, and eligible disks.

About Changes in Default SGA Permissions for Oracle AI Database

Oracle AI Database restricts read and write access to the System Global Area to the installation owner by default, improving security but potentially limiting OSDBA administrators. The ALLOW_GROUP_ACCESS_TO_SGA parameter controls whether OSDBA group members can access the SGA; its default FALSE setting is recommended, although it can be changed to TRUE when group read access is required.

Setting Language and Locale Preferences for Client Connections

Configure client locale and character-set settings according to the application, operating system, and I/O device. OCI applications use NLS_LANG and related settings, with the character-set component matching the device encoding; an incorrect value can cause data loss. JDBC applications instead use the Java VM locale and Unicode internally, while three-tier deployments may define locale settings in application-server configuration.

Recompile Invalid Objects in the Database

After installation, patching, or upgrading, recompile invalid objects across the CDB and PDBs using Oracle scripts such as utlrp.sql, utlprp.sql, or utlprpom.sql, executed through catcon.pl. AutoUpgrade generally recompiles Oracle-maintained objects automatically, while administrators can choose serial or parallel recompilation, process Oracle-owned objects first, and control PDB concurrency and logging through command parameters.

About the oradism Utility in Oracle AI Database

The oradism utility enables Oracle AI Database to perform operations requiring privileged operating-system access on Linux. Oracle installs and configures it automatically as a root-owned binary in $ORACLE_HOME/bin; its background process, ora_dism_<sid>, starts with the database and stops during shutdown. Alert-log errors should prompt verification of the binary’s location and ownership.

Checking Installed Oracle AI Database Contents and Directory Location

To inspect installed Oracle AI Database products and their locations, launch Oracle Universal Installer from $ORACLE_HOME/oui/bin, open Installed Products, select the relevant product, and view its details. Close the inventory and exit the installer after reviewing the installation contents.

Setting the Oracle User Environment Variables

Configure the installation owner’s profile on every cluster node with ORACLE_BASE, ORACLE_HOME, and ORACLE_SID, and add $ORACLE_HOME/bin to PATH. Correctly setting these variables is required for SQL*Plus and other Oracle utilities to locate the database installation and instance.
Read More: Setting the Oracle User Environment Variables