topic Pipeline Data Copy Error 2200 in Pipelines

Pipeline Data Copy Error 2200

rje_gaiaherbs — Tue, 11 Jun 2024 11:14:56 GMT

I am attempting to copy data from an on prem oracle table to Fabric (tried both wh and lh). This is requiring the use of Azure Data Lake Storage Gen2 for staging. When running the action, the following error is received. I have done this in the past without issue. Not sure why there is a problem now. The table I'm attempting to copy is a customer DIM table. It only contains text and date fields, nothing extravegant.

{ "errorCode": 2200, "message": "ErrorCode=ParquetInvalidDecimalPrecisionScale,'Type=Microsoft.DataTransfer.Common.Shared.HybridDeliveryException,Message=Invalid Decimal Precision or Scale. Precision: 38 Scale: 127.,Source=Microsoft.DataTransfer.Richfile.ParquetTransferPlugin,'", "details": [] }

Re: Pipeline Data Copy Error 2200

Anonymous — Tue, 11 Jun 2024 11:26:06 GMT

Hi rje_gaiaherbs ,

Thanks for using Fabric Community. Apologize for the issue you are facing.
This is identified as a bug and Product team is working on the fix.
I will let you know once there is an update.
Appreciate your patience.

Re: Pipeline Data Copy Error 2200

rje_gaiaherbs — Tue, 11 Jun 2024 11:30:20 GMT

Thank you for the quick response!

Re: Pipeline Data Copy Error 2200

Anonymous — Wed, 04 Sep 2024 14:37:38 GMT

I have also faced same issue. May I know when this will be resolved. Do we have any alternate solution?

Re: Pipeline Data Copy Error 2200

data_power — Mon, 09 Sep 2024 13:42:32 GMT

Unfortunately I join to club too, Any news how this bug will be handled or any workaround?
Thanks in advance for all answers.

Re: Pipeline Data Copy Error 2200

FabianSchut — Fri, 01 Nov 2024 16:49:18 GMT

This has been a struggle for me for a few weeks too. I've created my own workaround for this problem. It took some time to finetune, but it works for me. Hope it helps you too.
First, I created a lookup that retrieves all the column names from the table in Oracle. The table and schema are pipeline parameters in my case, but can be hardcoded or retrieved in another way too.

The Query for the lookup is (I use XMLAGG instead of other options to mitigate the problem that the returned string was too long) :

@concat('SELECT RTRIM(XMLAGG(XMLELEMENT(E,CASE WHEN DATA_TYPE = ''NUMBER'' AND (CAST (DATA_SCALE AS NUMBER(5,0)) >= CAST (DATA_PRECISION AS NUMBER(5,0)) OR DATA_SCALE IS NULL OR DATA_PRECISION IS NULL) THEN ''CAST('' || COLUMN_NAME || '' AS NUMBER(38,18)) AS '' || COLUMN_NAME ELSE COLUMN_NAME END,'', '').EXTRACT(''//text()'') ORDER BY COLUMN_NAME).GetClobVal(),'', '') AS query_string
 FROM ALL_TAB_COLUMNS
 WHERE TABLE_NAME = ''', pipeline().parameters.table_name, '''
 AND OWNER = ''', pipeline().parameters.schema, '''')

Then I use these retrieved columns in my copy data:

And the query for the source is:

@concat('SELECT ',activity('lookup_columns_from_table').output.firstRow.QUERY_STRING, ' FROM ', pipeline().parameters.schema, '.', pipeline().parameters.table_name)

Re: Pipeline Data Copy Error 2200

grisensko — Thu, 19 Dec 2024 14:12:30 GMT

Is this fixed? I don't see this issues in fabric known Bugs Lists.

As usual the list seem incomplete, but it would help to track when it get resolved

Re: Pipeline Data Copy Error 2200

jenyfer_duran — Tue, 22 Apr 2025 09:17:07 GMT

Thank you! Works for me too