<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Databricks App Error libodbc.so.2: cannot open shared object file: No such file or directory in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/databricks-app-error-libodbc-so-2-cannot-open-shared-object-file/m-p/112715#M44307</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;How are you doing today?, As per my understanding,&amp;nbsp;It looks like your init script is correctly installing the ODBC driver for Notebooks, but Apps might not be picking it up because they run in a different context. Have you checked if the Apps are using the same cluster and environment? Sometimes, environment variables or library paths don’t carry over. You could try explicitly setting the LD_LIBRARY_PATH in your init script to make sure the driver is linked properly. Also, running print(pyodbc.drivers()) inside an App can help confirm if the driver is available. If it’s missing, you might need to check permissions or try a different installation approach. Let me know what you find!&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Brahma&lt;/P&gt;</description>
    <pubDate>Sun, 16 Mar 2025 03:37:55 GMT</pubDate>
    <dc:creator>Brahmareddy</dc:creator>
    <dc:date>2025-03-16T03:37:55Z</dc:date>
    <item>
      <title>Databricks App Error libodbc.so.2: cannot open shared object file: No such file or directory</title>
      <link>https://community.databricks.com/t5/data-engineering/databricks-app-error-libodbc-so-2-cannot-open-shared-object-file/m-p/112583#M44260</link>
      <description>&lt;P&gt;How do I solve this error in my Databricks Apps when using the pyodbc library? I have used an init script to install the library in my cluster, which has resolved the issue in Notebooks. However, the problem persists in Apps. I have used the following commands in my init script:&lt;BR /&gt;&lt;FONT face="terminal,monaco" color="#993300"&gt;sudo apt-get update &lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="terminal,monaco" color="#993300"&gt;sudo apt-get install -y libodbc2&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="terminal,monaco" color="#993300"&gt;sudo ACCEPT_EULA=Y apt-get install -y msodbcsql18&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 14 Mar 2025 13:17:49 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/databricks-app-error-libodbc-so-2-cannot-open-shared-object-file/m-p/112583#M44260</guid>
      <dc:creator>SObiero</dc:creator>
      <dc:date>2025-03-14T13:17:49Z</dc:date>
    </item>
    <item>
      <title>Re: Databricks App Error libodbc.so.2: cannot open shared object file: No such file or directory</title>
      <link>https://community.databricks.com/t5/data-engineering/databricks-app-error-libodbc-so-2-cannot-open-shared-object-file/m-p/112715#M44307</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;How are you doing today?, As per my understanding,&amp;nbsp;It looks like your init script is correctly installing the ODBC driver for Notebooks, but Apps might not be picking it up because they run in a different context. Have you checked if the Apps are using the same cluster and environment? Sometimes, environment variables or library paths don’t carry over. You could try explicitly setting the LD_LIBRARY_PATH in your init script to make sure the driver is linked properly. Also, running print(pyodbc.drivers()) inside an App can help confirm if the driver is available. If it’s missing, you might need to check permissions or try a different installation approach. Let me know what you find!&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Brahma&lt;/P&gt;</description>
      <pubDate>Sun, 16 Mar 2025 03:37:55 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/databricks-app-error-libodbc-so-2-cannot-open-shared-object-file/m-p/112715#M44307</guid>
      <dc:creator>Brahmareddy</dc:creator>
      <dc:date>2025-03-16T03:37:55Z</dc:date>
    </item>
    <item>
      <title>Re: Databricks App Error libodbc.so.2: cannot open shared object file: No such file or directory</title>
      <link>https://community.databricks.com/t5/data-engineering/databricks-app-error-libodbc-so-2-cannot-open-shared-object-file/m-p/112717#M44308</link>
      <description>&lt;P&gt;Your analysis is spot on! The issue likely stems from environment differences between Notebooks and Apps. Checking cluster consistency, verifying and setting should help. Also, reviewing permissions and alternative installations might be necessary. Let me know what you find—I’d be happy to troubleshoot further!&lt;/P&gt;</description>
      <pubDate>Sun, 16 Mar 2025 03:41:49 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/databricks-app-error-libodbc-so-2-cannot-open-shared-object-file/m-p/112717#M44308</guid>
      <dc:creator>mourinseoexpart</dc:creator>
      <dc:date>2025-03-16T03:41:49Z</dc:date>
    </item>
  </channel>
</rss>

