Lesson 4	Oracle interMedia: Historical Reference
Objective	Describe Oracle interMedia's historical role, its evolution into Oracle Multimedia, and why its multimedia APIs are not used in Oracle AI Database 26ai.

Oracle interMedia: Historical Multimedia Architecture

This lesson describes legacy technology. Oracle interMedia's multimedia features became Oracle Multimedia, which was deprecated in Oracle Database 18c and desupported in 19c. These multimedia processing APIs are not a supported solution for Oracle AI Database 26ai.

In the Oracle8i era, interMedia helped applications work with rich content, including images, audio, video, and text. Its object-relational approach connected media content with database-managed attributes and methods. Understanding that design explains references to interMedia in older schemas and documentation without treating it as a current implementation choice.

From interMedia to Oracle Multimedia

Key stages in the product's history
Release or era	Historical significance
Oracle8i	The interMedia branding covered rich-content capabilities, including multimedia handling and interMedia Text.
Oracle9i	Oracle documentation used the name Oracle Text, formerly interMedia Text. Text search followed a separate product path.
Oracle Database 11g Release 1	The multimedia feature was renamed Oracle Multimedia.
Oracle Database 18c	Oracle Multimedia was deprecated.
Oracle Database 19c	Oracle Multimedia was desupported and its implementation removed.
Oracle AI Database 26ai	Current applications use supported storage, processing, and search components instead of the old multimedia APIs.

Deprecation signaled that applications should move away from the feature. Desupport in 19c went further: the implementation was removed. Legacy objects and packages could remain in a database, but attempts to use the removed functionality raised exceptions. The presence of an old type or package therefore did not establish that multimedia processing was still available.

How the Historical Architecture Worked

The diagram illustrates a client retrieving media, editing a local copy, and returning updated content. It is a conceptual view of the legacy workflow.

Historical interMedia workflow: a Java client retrieves and returns edited media; database multimedia services access object-table data defined by ORDAudio, ORDVideo, and ORDImage types. — Figure 1: Historical Oracle interMedia architecture. A Java client retrieved a media copy for local editing and returned the updated content to the database. The diagram depicts legacy multimedia services and object types, not an Oracle 26ai deployment.

Java client: Retrieved a media copy, edited it locally, and submitted the updated content.
interMedia server: Represents database-side multimedia services that retrieved media and managed its attributes using database transaction and locking mechanisms. The label does not identify a separate mandatory server process or imply that a lock remained held throughout desktop editing.
Object table: Illustrates an object-relational arrangement in which a LOB attribute stored binary media. Multimedia types could also appear as columns in relational tables; an object table was not mandatory.
Object types: Types such as ORDAudio, ORDVideo, and ORDImage supplied media attributes and methods. The diagram shows type definitions, not an inheritance hierarchy.

What Continues in Oracle 26ai?

Media storage and retrieval remain useful, but there is no single drop-in replacement for the historical multimedia API collection. Current applications separate these responsibilities:

Current approaches to media storage and search
Requirement	Current approach
Store binary media in the database	SecureFiles `BLOB` columns.
Store media externally	Object storage or another managed repository, with identifiers and metadata in Oracle tables.
Resize images or transcode audio and video	Suitable application libraries or external media services.
Manage descriptions and attributes	Relational columns or JSON documents.
Search document text	Oracle Text, using supported indexing and query facilities.
Retrieve similar content	Compatible embedding models and AI Vector Search when similarity retrieval is required.

Oracle Text was not removed with Oracle Multimedia. It remains a separate text-search capability. Likewise, vector similarity search does not automatically replace image conversion, video processing, or the old multimedia methods. Applications still need components appropriate to each task.

Recognizing Legacy Dependencies

When maintaining an older application, identify tables and program units that depend on multimedia types and methods. Preserve the original media and metadata, and replace processing calls with supported components before relying on a newer release. Renaming a type is not a migration strategy, and removing legacy objects without examining their dependencies can damage the application.

interMedia belongs to Oracle's history, while media storage and search remain current application requirements. With that distinction established, continue to the next lesson.

Oracle References