What causes ArgumentOutOfRangeException?

Oracle table contains BC-era dates (year < 1) which cannot be represented in .NET DateTime. Oracle stores second or minute values greater than 59 (valid in Oracle, invalid in .NET). Source table has historical data loaded from legacy systems with non-standard date representations. DateTime columns were not validated when data was loaded into Oracle

How do I fix ArgumentOutOfRangeException?

Run `SELECT dump( ) FROM WHERE > DATE '9999-12-31'` in Oracle SQL Developer to locate rows with out-of-range DateTime values.. In the Fabric copy activity, add a WHERE clause filter on the Oracle source query to exclude rows with invalid dates before they reach the .NET runtime.. For columns with BC-era dates, add a transformation in the copy activity mapping to replace them with a sentinel value such as '1900-01-01' or NULL.. If the column contains second values above 59 (Oracle allows leap seconds in some configurations), cast the column using TO_CHAR and then re-parse as a string in the sink.. After filtering out the bad rows, decide whether to write them to a rejected-rows table using the copy activity's fault tolerance settings (skipIncompatibleRow) for audit purposes.

Medium severityfabricMicrosoft Fabric →

Microsoft Fabric Error:
ArgumentOutOfRangeException

Q: How do I fix ArgumentOutOfRangeException?

Run `SELECT dump( ) FROM WHERE > DATE '9999-12-31'` in Oracle SQL Developer to locate rows with out-of-range DateTime values.. In the Fabric copy activity, add a WHERE clause filter on the Oracle source query to exclude rows with invalid dates before they reach the .NET runtime.. For columns with BC-era dates, add a transformation in the copy activity mapping to replace them with a sentinel value such as '1900-01-01' or NULL.. If the column contains second values above 59 (Oracle allows leap seconds in some configurations), cast the column using TO_CHAR and then re-parse as a string in the sink.. After filtering out the bad rows, decide whether to write them to a rejected-rows table using the copy activity's fault tolerance settings (skipIncompatibleRow) for audit purposes.

What does this error mean?

A copy pipeline reading from Oracle via Fabric Data Factory failed because an Oracle DateTime value is outside the range supported by Azure Data Factory and Synapse (0001-01-01 to 9999-12-31). Oracle supports BC-era dates and second values above 59 which have no equivalent in .NET DateTime.

Common causes

1Oracle table contains BC-era dates (year < 1) which cannot be represented in .NET DateTime
2Oracle stores second or minute values greater than 59 (valid in Oracle, invalid in .NET)
3Source table has historical data loaded from legacy systems with non-standard date representations
4DateTime columns were not validated when data was loaded into Oracle

How to fix it

1Run `SELECT dump(<column_name>) FROM <table> WHERE <column_name> < DATE '0001-01-01' OR <column_name> > DATE '9999-12-31'` in Oracle SQL Developer to locate rows with out-of-range DateTime values.
2In the Fabric copy activity, add a WHERE clause filter on the Oracle source query to exclude rows with invalid dates before they reach the .NET runtime.
3For columns with BC-era dates, add a transformation in the copy activity mapping to replace them with a sentinel value such as '1900-01-01' or NULL.
4If the column contains second values above 59 (Oracle allows leap seconds in some configurations), cast the column using TO_CHAR and then re-parse as a string in the sink.
5After filtering out the bad rows, decide whether to write them to a rejected-rows table using the copy activity's fault tolerance settings (skipIncompatibleRow) for audit purposes.

Beyond the docs

Common practitioner solutions not covered in the official documentation.

1Identify rows with out-of-range dates using: SELECT * FROM <table> WHERE <date_col> < DATE '0001-01-01'
2Cast the Oracle DateTime column to VARCHAR in the copy source query to bypass the conversion: TO_CHAR(<col>, 'YYYY-MM-DD HH24:MI:SS')
3Filter out or replace known out-of-range values at the source query level before they reach the copy sink
4If BC dates are business-critical, consider a custom transformation step before loading into the target

Frequently asked questions

Does this error affect Power BI reports in the same workspace?

Depends on the error type. Semantic model failures affect report freshness directly. Dataflow or pipeline failures may cascade into downstream semantic model failures.

How is debugging Fabric errors different from classic Power BI errors?

Fabric errors often require checking capacity utilization alongside the item-level error. The Fabric admin portal shows capacity pressure that Power BI Service doesn't expose.

Can Fabric errors be caused by capacity limits?

Yes — Fabric capacities have concurrent operation limits. An undersized capacity causes failures during peak usage.

Does this error appear in Power BI Desktop?

No — Fabric items are cloud-native. Desktop can connect to Fabric semantic models but cannot trigger or observe Fabric-specific errors.

Source · learn.microsoft.com/en-us/fabric/data-factory/connector-troubleshoot-oracle