Azure Data Factory pipeline failing on sink side: Job failed due to reason: at Sink 'sink1': Invalid object name '[Table_Name]'.

Thomaz Suzuki 5

I have the following workflow: User's image

It fails on the sink step with: Job failed due to reason: at Sink 'sink1': Invalid object name '[table_name]'.

The thing is that this table_name that shows up in the warning, I'm not using it nowhere in the whole data workflow.

I even tried deleting the dataset and creating again, but no luck.

I'm able to preview the dataset (table the should be updated by the sink step).

Any clues on what is happening?

Thank you on advance.

Thomaz Suzuki 5 Reputation points

2023-10-17T14:06:06.1866667+00:00

As far as I know the name of the table is static.

Here are some prints of the configuration:

SINK:

DATASET

I even tried re-creating the dataset, but it still reach-out for the wrong table name.

I'm clueless.

Thank you!
Subashri Vasudevan 11,206 Reputation points

2023-10-17T15:33:22.36+00:00

Hmm. Thanks for sharing the additional details. That looks weird. Probably, change name of the sink from sink1 to a different name, and do a publish and retry? May be some caching issues, that causes this. Please try this and let us know.
Thomaz Suzuki 5 Reputation points

2023-10-17T15:48:28.5966667+00:00

Changed the name published and still having the same issue.

Is strange because the dataset used in Sink is also used on one of the Sources and in Source it pulls from the correct table, in sink it tries to reach out for a table that no longer exists in database.
Thomaz Suzuki 5 Reputation points

2023-10-17T15:51:28.0133333+00:00

In Sink I'm using just 2 columns for the update, the key column and the columns that I want to update, but there are more columns in the table, this can cause any issues ?
Subashri Vasudevan 11,206 Reputation points

2023-10-18T03:45:49.0533333+00:00

No, it wont cause a problem.

@Nandan Hegde @KranthiPakala-MSFT any thoughts ??
AnnuKumari-MSFT 33,986 Reputation points Microsoft Employee

2023-10-23T06:16:53.69+00:00

Thomaz Suzuki ,

Kindly go to the schema tab in your sink dataset and clear the schema and re-run the pipeline once. In case, that doesn't work , kindly try creating a new sink dataset altogether and let us know if issue still persists after the above approach. Thankyou
AnnuKumari-MSFT 33,986 Reputation points Microsoft Employee

2023-10-26T10:01:16.4033333+00:00

Hi Thomaz Suzuki ,

Did you try the above approach. Kindly provide update on the issue whether it's resolved or you are still facing the issue . Thankyou

1 answer

Subashri Vasudevan 11,206 Reputation points

2023-10-17T04:49:59.1966667+00:00

Hi Thomaz Suzuki

This error might be due to value being passed to the table field in data set during run time. Can you please tell us if you decide the name of the table dynamically or it is static?

Also please share us the data set configuration being used in sink.

This would help us isolate the issue,

Thanks
Please sign in to rate this answer.
Sudha Achuthan 20 Reputation points

2024-06-25T09:26:32.06+00:00

i had similar error.

because i copied a string name from spreadsheet to create the objects in ADF. Looks like they had special character and hence this error.

i deleted and recreated all the mappings. it went OK.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Azure Data Factory pipeline failing on sink side: Job failed due to reason: at Sink 'sink1': Invalid object name '[Table_Name]'.

1 answer

Your answer