Changes in Oracle AI Database Globalization Support Guide for Oracle AI Database 26ai

The following are changes in Oracle AI Database Globalization Support Guide for Oracle AI Database 26ai.

New Features

New Features in Oracle AI Database 26ai, Release Update 23.26.3

  • Support for Unicode 17.0, keeping Oracle Database current with the latest Unicode Standard and expanding multilingual coverage for newly encoded scripts, characters, and symbols.

    Unicode 17.0 includes a new currency symbol, the SAUDI RIYAL SIGN (Unicode code point U+20C1), that the Saudi Central Bank introduced in 2025 to represent the currency of Saudi Arabia. The new symbol can be used by configuring the NLS_CURRENCY parameter through the client environment, database session, application-specific logon configuration, or individual SQL formatting functions. To display the symbol correctly, the client character set and application font must support Unicode code point U+20C1.

    Saudi Riyal Symbol

    See "Unicode Support".

New Features in Oracle AI Database 26ai, Release Update 23.26.2

New Features in Oracle AI Database 26ai

  • Support for Unicode 15.0, a major version of the Unicode Standard that supersedes all its previous versions.

    See "Unicode Support".

  • Enhanced Ideographic Variation Sequence (IVS) support:

  • A new territory TURKIYE, which supports the official name of the country of Türkiye.

    See "Territories".

  • A new linguistic sort ICELANDIC_IST, which implements the Icelandic Standard IST 130:2004.

    See "Linguistic Collations".

  • The implementation of the Oracle client character set ZHS32GB18030 is updated to support the latest GB18030-2022 standard.

    See "Client-Only Character Sets".

  • The UTL_I18N package provides three new procedures that detect the most likely Oracle character sets and Oracle languages for a given data sample.

    See DETECT_CHARSET, DETECT_LANGUAGE, and DETECT_LANGUAGE_CHARSET in Oracle AI Database PL/SQL Packages and Types Reference.

  • The process of upgrading time zone data using the DBMS_DST package has been enhanced as follows:

    • The upgrade is optimized to take the actual data contents of a table into account. Only tables impacted by a daylight saving time rule change will undergo a data change. See "Upgrade Window".

    • You can monitor the actions performed on tables during the upgrade process by viewing the upgrade history table. See "About the Upgrade History Table".

  • The new TIME_AT_DBTIMEZONE initialization parameter allows you to specify whether time-dependent database operations use the time zone of the database host system or the time zone of the PDB.

    See Oracle AI Database Reference.