Oracle AI Database 26ai Offers EBCDIC Compatibility Features for Mainframe Re-Platforming

Oracle announced Oracle AI Database 26ai now includes EBCDIC compatibility capabilities that address two fundamental challenges of preserving EBCDIC compatibility: accurate character encoding conversion and preservation of EBCDIC binary ordering.

Together, these capabilities can help organizations re-platform IBM mainframe databases while preserving data integrity and application compatibility. The Oracle AI Database Globalization Support Guide (26ai) describes these capabilities in more detail.

At the heart of these capabilities is a family of IBM CDRA-compatible EBCDIC client character sets.

These client character sets implement IBM Character Data Representation Architecture (CDRA) code page definitions, providing source-to-target character mappings that are compatible with IBM’s published standards. This enables accurate and predictable character encoding conversion during data migration and subsequent database client/server communication, said Oracle.

Accurate character encoding conversion alone is not sufficient to preserve EBCDIC compatibility. Many legacy EBCDIC applications, such as those written in COBOL, implicitly rely on the EBCDIC binary ordering defined by IBM EBCDIC code pages. SQL predicates that compare character values, perform range searches, or sort query results often assume this ordering.

After migration to an ASCII-based Oracle AI Database character set, these same SQL statements can produce different results—not because the data changed, but because the database’s default binary ordering follows that of the ASCII-based database character set rather than the source EBCDIC code page.

Oracle AI Database now includes IBM CDRA-compatible EBCDIC client character sets with matching emulated EBCDIC binary collations. Each built-in emulated EBCDIC binary collation is generated specifically for its associated IBM EBCDIC code page, reproducing its binary ordering. As a result, SQL comparison and ordering operations can preserve the behavior expected by many legacy EBCDIC applications with minimal or no SQL changes after migration.

As built-in Oracle AI Database collations, these EBCDIC binary collations work with any supported Oracle AI Database character set and are supported across Oracle AI Database deployment models, such as Oracle Exadata, Oracle Autonomous Database on OCI, Exadata Cloud@Customer, and Multi-cloud deployments. This is particularly important for customers modernizing their workloads to Oracle Autonomous Database and other Exadata-based deployment models because customized locale data, including customized collations, is not supported on Oracle Exadata-based deployments.

Oracle AI Database includes the Data-Bound Collation feature, allowing collations to be associated directly with columns, tables, or schemas instead of relying on application logic or session settings. This existing Oracle AI Database capability makes deployment of the EBCDIC binary collations straightforward.

By making EBCDIC binary ordering part of the database definition, the Data-Bound Collation feature can help avoid the need to create separate linguistic indexes with customized collations. This can reduce deployment complexity and can help simplify long-term administration.

Oracle’s implementation is designed to preserve compatibility while helping to manage operational and performance overhead, Oracle said.

Although customized linguistic collations can reproduce EBCDIC binary ordering, they apply the complexity of linguistic ordering to what is fundamentally a binary ordering problem. As a result, they can generate significantly larger collation keys, which can lead to larger linguistic indexes and increased storage and processing overhead.

Successful mainframe re-platforming depends on preserving EBCDIC compatibility after migration—not only the integrity of migrated character data, but also the application semantics that existing applications depend on.

Oracle AI Database combines IBM CDRA-compatible EBCDIC client character sets, built-in emulated EBCDIC binary collations, the Data-Bound Collation feature, and migration guidance for EBCDIC compatibility on modern ASCII-based systems. Whether the destination is an on-premises deployment or one of Oracle AI Database’s cloud deployment models, organizations can modernize mission-critical workloads while preserving EBCDIC compatibility.