The MySQL Client Library Driver for Oracle, liboramysql, was a drop-in replacement for the MySQL C client library. Applications written against the MySQL C API could be relinked to it and connect to Oracle Database instead, with the driver translating calls onto Oracle Call Interface. It shipped as a 12c-era client add-on; the introduction release recorded here is a best-effort value.

Migrations care because an application using this shim is really a MySQL-API application that happens to talk to Oracle. Moving it to Azure is not a straightforward Oracle-to-target mapping: the choice is between rewriting for the target's native driver or choosing a MySQL-compatible destination. The library is easy to miss because it lives in application deployments, not in the database.

Oracle's 21c Upgrade Guide deprecates the driver, and the 26ai guide desupports it (notice dated April 2023) with no replacement offered.

The MySQL client library driver, liboramysql, arrived in Oracle Database 12.1. In life, it let applications written against the MySQL client library talk to Oracle Database.

Deprecated in 21c, it was desupported in 26ai. Its passage to Azure was blocked because Azure SQL Database uses SQL Server connection libraries and offers no MySQL-protocol endpoint, requiring applications to change drivers and SQL dialect.

It is survived by Azure SQL Database, where it lives on not at all. Applications may instead use Microsoft drivers and connection libraries for Python, Java, Node.js, PHP, Ruby, or .NET—or target Azure Database for MySQL when MySQL compatibility is the requirement.