Share via

error with numeric columns in a PostgreSQL connection via ADF integration runtime 5.55.9315.1

Wilfred Vonk 20 Reputation points
2025-11-18T14:19:21.2833333+00:00

Since November 15 (likely coinciding with the update of the self-hosted integration runtime to version 5.55.9315.1), numeric columns in our PostgreSQL tables have been displaying incorrect values when decimals are involved—the numbers appear to be multiplied by 10,000.

As far as I can tell, downgrading isn't an option. Is there any alternative solution to resolve this issue?

Azure Data Factory
Azure Data Factory
An Azure service for ingesting, preparing, and transforming data at scale.
0 comments
Answer accepted by question author
  1. Swapnesh Panchal 1,365 Reputation points Microsoft External Staff Moderator
    2025-11-27T18:51:38.3833333+00:00

    Hi @Wilfred Vonk ,
    Welcome to the Microsoft Q&A and thank you for posting your questions here.
    Thank you for coming back and sharing the solution!

    This behavior is caused by a bug in Self-hosted Integration Runtime (SHIR) version 5.55.9315.1. As you confirmed, reverting to an earlier stable release (for example, the April 2025 version) resolves the numeric column error for PostgreSQL connections.

    This insight is very helpful for others who might run into the same problem until an official fix is released.

    Workaround – Roll Back SHIR Version

    1. Uninstall the current SHIR version 5.55.9315.1 from the machine (Do not delete the IR configuration from Azure Data Factory.)
    2. Download an earlier stable version from the Microsoft Download Center: https://www.microsoft.com/en-us/download/details.aspx?id=39717
    3. Install the older SHIR and reconnect it using the same authentication key.
    4. In Azure Data Factory, go to Manage → Integration runtimes and confirm that the Self-hosted IR is online and linked correctly.
    5. Re-run the pipeline / activity to validate that the numeric column error is resolved.

    Useful References

    SHIR – Create & configure:
    https://learn.microsoft.com/azure/data-factory/create-self-hosted-integration-runtime

    SHIR – Upgrade / manage versions:
    https://learn.microsoft.com/azure/data-factory/self-hosted-integration-runtime-upgrade

    Expired SHIR version list (GitHub):
    https://github.com/Azure/Azure-DataFactory/blob/main/Self-hosted%20Integration%20Runtime%20Expired%20Version.md

    0 comments

2 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Q&A Assist
    2025-11-18T14:19:55.2233333+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    It seems that the issue you are experiencing with numeric columns in PostgreSQL when using Azure Data Factory (ADF) integration runtime version 5.55.9315.1 could be related to how the integration runtime handles decimal precision or data type conversions. Here are some steps you can take to troubleshoot and potentially resolve the issue:

    1. Check Data Types: Ensure that the data types of the numeric columns in PostgreSQL are compatible with what ADF expects. Sometimes, ADF may misinterpret the data type, leading to incorrect values.
    2. Adjust Decimal Precision: If the decimal precision of the numeric columns is too high, it might cause issues when ADF processes the data. Consider adjusting the precision in your PostgreSQL table definitions or in the ADF mapping.
    3. Review ADF Mapping Settings: Check the mapping settings in your ADF pipeline to ensure that the numeric columns are being handled correctly. You may need to explicitly define how ADF should treat these columns.
    4. Use Data Flow Transformations: If the issue persists, consider using data flow transformations to manipulate the data before it is written to the sink. This can help you adjust the values as needed to correct the multiplication issue.
    5. Monitor Updates and Issues: Keep an eye on any updates or known issues related to the integration runtime version you are using. Sometimes, issues are resolved in subsequent updates, so staying informed can help you find a solution.

    If these steps do not resolve the issue, you may want to reach out to Microsoft support for further assistance specific to your integration runtime version and configuration.

    References:

    0 comments
  2. Wilfred Vonk 20 Reputation points
    2025-11-19T08:34:48.1166667+00:00

    i installed a older version of the Self Hosted Integration Runtime (april 2025) and now the problem is gone. It's clearly a bug in version 5.55.9315.1

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.