Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

To celebrate FabCon Vienna, we are offering 50% off select exams. Ends October 3rd. Request your discount now.

Reply
TimoW
Frequent Visitor

IBM DB2 - PackageCollection bug in Fabric Pipeline

To connect to our IBM DB2 database, we need to set a custom "packageCollection" value as an additional connection property in a copy activity.

 

TimoW_0-1758617191307.png

 

However, when inspecting the pipeline's JSON, we noticed that "packageCollection" is added with a trailing space ("packageCollection "). This causes issues, as the DB2 database doesn’t recognize the property correctly.

TimoW_2-1758617281964.png

 

Manually removing the space in the JSON makes the pipeline work again, so for anyone facing the same issue, that’s a temporary fix. But ideally, this bug should be resolved at the source.

 

Is this the right place to report such a bug? As it stands, fixing it manually means the property can’t be configured through the UI anymore.

TimoW_3-1758618709436.png

 

1 ACCEPTED SOLUTION
v-veshwara-msft
Community Support
Community Support

Hi @TimoW ,

Thanks for posting in Microsoft Fabric Community.

Based on your findings it does look like the property is being written with a trailing space in the JSON, which explains why DB2 does not recognize it. Editing the JSON manually is a valid workaround for now, but as you mentioned, it prevents further changes through the UI.

 

Since this is product-side behavior, the right next step is to log it in the Fabric Issues forum here: Issues - Microsoft Fabric Community 

That way it can be tracked by the product team. If this is blocking for your environment, you may also consider opening a support ticket so it can be investigated directly.

 

Please reach out for further assistance.

Thank you.

View solution in original post

1 REPLY 1
v-veshwara-msft
Community Support
Community Support

Hi @TimoW ,

Thanks for posting in Microsoft Fabric Community.

Based on your findings it does look like the property is being written with a trailing space in the JSON, which explains why DB2 does not recognize it. Editing the JSON manually is a valid workaround for now, but as you mentioned, it prevents further changes through the UI.

 

Since this is product-side behavior, the right next step is to log it in the Fabric Issues forum here: Issues - Microsoft Fabric Community 

That way it can be tracked by the product team. If this is blocking for your environment, you may also consider opening a support ticket so it can be investigated directly.

 

Please reach out for further assistance.

Thank you.

Helpful resources

Announcements
September Fabric Update Carousel

Fabric Monthly Update - September 2025

Check out the September 2025 Fabric update to learn about new features.

August 2025 community update carousel

Fabric Community Update - August 2025

Find out what's new and trending in the Fabric community.