Oracle Autonomous Database supports versioned shares through the open Delta Sharing protocol. Providers publish data from Autonomous Database, and recipients access shares using a JSON profile and query Parquet data for a selected version window. Oracle also provides a fully scriptable sharing workflow through the DBMS_SHARE package.

• ./change-data-feed/Oracle Delta Sharing CDF.ipynb — Python code that compares two versions of a Delta Share and prints the raw change rows returned for that version window.

This notebook demonstrates a file-based CDF-style workflow for versioned Delta Shares published by Oracle Autonomous Database.

The notebook:

• authenticates with a Delta Sharing profile
• requests changes between START_VERSION and END_VERSION
• downloads only the Parquet/action files returned for that version window
• displays raw rows together with _commit_version and _change_type

This makes it useful for validating what changed between two published versions of a share without scanning the full share.

This sample operates at file level.

When a file changes between two versions:

• rows from the previous file can appear as delete
• rows from the replacement file can appear as insert

As a result, unchanged rows inside a replaced file can appear as matching delete/insert pairs. The notebook intentionally shows the raw output so downstream logic can derive the net inserts, deletes, and updates.

In practice, this means that if a share is large but only a small incremental change was published, the notebook reads only the files returned for the requested version window rather than scanning the full share.

• Overview of the Data Share Tool
• Manage Shares with DBMS_SHARE
• DBMS_SHARE Constants
• High-Level Steps for Receiving Shares for Versioned Data
• Sharing Data from On-Premise Oracle Databases
• Seamless, Open Data Sharing Between Oracle Autonomous Database and Databricks