To connect to our IBM DB2 database, we need to set a custom "packageCollection" value as an additional connection property in a copy activity.
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.
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.
As it stands, fixing it manually means the property can’t be configured through the UI anymore.
2 Comments
- We’re experiencing the same issue on our tenant as well, the “packageCollection” property is being saved with a trailing space (“packageCollection ”), causing DB2 connection errors. Manually editing the JSON works as a temporary fix for us too. Hopefully this can be addressed in an upcoming patch.
- Same issue here aswell. We can't use the pipeline activity without manually fixing the JSON. Microsoft pls fix, it's just a blank space 🙂
