Forum Discussion

DKHUghes55's avatar
DKHUghes55
Icon for Resolver II rankResolver II
2 months ago
Solved

Power BI Desktop Oracle Connection Error ORS-50122

Hi Power BI Community,

We have started seeing from Power BI Desktop users

Oracle: ORA-50122: The following configuration parameter is not allowed to be set : Community.

This is recent, nothing on our end has changed.

The entries in the TNSnames.ora file have this tag.  Community=tcp.world.

Is there a setting we need to change or add in either the Power BI desktop app or the oracle client on the users machine?

 

Any help will be greatly appreciated.

DKHughes

 

Need Help
  • DKHUghes55's avatar
    DKHUghes55
    2 months ago

    Hi Omkar!

    Thanks for response.  The Oracle client is the latest version on the users computer.  What we did find that fixed the issue is setting in the Power BI Desktop client.  It is called "Enable using Bundled oracle Managed ODP Provider for Import Mode"

    The user is not longer getting the Error and everything is working as expected.

     

    Thanks,

    DKHughes55

3 Replies

  • Omkar_1712's avatar
    Omkar_1712
    Icon for Solution Specialist rankSolution Specialist
    2 months ago

    Hello DKHUghes55,

    The error appears to originate from the Oracle client rather than Power BI Desktop.


    ORA-50122 indicates that the Oracle client doesn't allow the COMMUNITY parameter in the tnsnames.ora entry. If this started recently without any changes to Power BI, it's possible that the Oracle client was updated and is now enforcing stricter validation.


    A few things to check:

    • Verify whether the Oracle Client or ODAC version has recently changed.

    • Review the tnsnames.ora file and, if possible, remove or comment out the COMMUNITY=tcp.world parameter, as it is no longer supported by newer Oracle clients.

    • Ensure that Power BI Desktop is using the expected Oracle Client (especially if multiple Oracle homes are installed).

    If removing the COMMUNITY parameter isn't an option, you may also want to check with your DBA to confirm whether the tnsnames.ora file needs to be updated for compatibility with the current Oracle client version.


    Best regards,
    Omkar Shinde
    Microsoft Fabric Enthusiast | Power BI Consultant

    💡 If you found this response helpful, please consider giving it a Kudos.
    ✅ If this resolves your question, please mark it as the Accepted Solution to help others in the community.

    • DKHUghes55's avatar
      DKHUghes55
      Icon for Resolver II rankResolver II
      2 months ago

      Hi Omkar!

      Thanks for response.  The Oracle client is the latest version on the users computer.  What we did find that fixed the issue is setting in the Power BI Desktop client.  It is called "Enable using Bundled oracle Managed ODP Provider for Import Mode"

      The user is not longer getting the Error and everything is working as expected.

       

      Thanks,

      DKHughes55

  • Kagiyama_yutaka's avatar
    Kagiyama_yutaka
    Icon for Continued Contributor rankContinued Contributor
    2 months ago

    ORA‑50122 comes from the Oracle client, and Power BI Desktop has no setting for the COMMUNITY entry, so the change needs to be done on the Oracle side.