Share via

Azure Data Factory Oracle 2.0 Connector CLR error with SDO_GEOMETRY data type

Evan Morgoch 1 Reputation point
2025-10-22T18:01:26.6933333+00:00

We're testing data loading after updating our Oracle Linked Service connection from 1.0 to 2.0, and are running into an issue with columns that use the Oracle SDO_GEOMETRY data type.

With the 1.0 connector, queries that pulled these columns in executed fine, and converted the data into Strings. However, when using the 2.0 connector, we're getting the following error:

ErrorCode=DataTypeNotSupported,'Type=Microsoft.DataTransfer.Common.Shared.HybridDeliveryException,Message=Not supported clr type: Object.,Source=,'

We're using the supportV1DataTypes = true property as we also have a ton of NUMBER columns that are getting pulled in that use various precision and scale amounts and are saving the data to parquet, and we can't hardcode a fixed set of precision and scale values that would work for all columns.

The source data is in an Oracle 19c database if that makes any difference.

Azure Data Factory
Azure Data Factory
An Azure service for ingesting, preparing, and transforming data at scale.

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Vinodh247 39,201 Reputation points MVP Volunteer Moderator
    2025-10-23T01:32:56.96+00:00

    The adf Oracle 2.0 connector does not support complex oracle object types like SDO_GEOMETRY. In Oracle1.0, these were implicitly converted to strings, but in 2.0 the new .NET CLR-based driver enforces strict type mapping and fails with Not supported clr type: Object for unsupported data types.

    Workarounds that you can try:

    1. Explicitly cast SDO_GEOMETRY to VARCHAR in your source query, for example: SELECT SDO_UTIL.TO_WKTGEOMETRY(geom) AS geom_wkt, col1, col2 FROM table_name
    2. Keep using supportV1DataTypes: True, but this does not override unsupported complex types.
    3. If you must process geometry data, consider using a staging layer (synapse or databricks) that can handle spatial data before moving it into Parquet.

    so SDO_GEOMETRY is not supported in Oracle 2.0 connector, and you must convert it to a supported scalar type (VARCHAR) in your query.

    Please 'Upvote'(Thumbs-up) and 'Accept' as answer if the reply was helpful. This will be benefitting other community members who face the same issue.

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.