My Global Init Script doesn't run with the new(er) LTS version 13.3. It runs great on 12.2LTS

[Benedetta]

Hey Databricks,

     Seems like you changed the way Global Init Scripts work.  How come you changed it? My Global Init Script runs great on 12.2LTS but not on the new(er) LTS version 13.3. We don't have Unity Catalog turned on. What's up with that? Are Global Init scripts going away for good?

Thank you

Benedetta

[Benedetta]

Hi Kaniz,

     Thanks for your reply. I still don't understand if my pyodbc global init script is supposed to run on LTS 13.3. If so.....it doesn't. The connection to the server fails. In the past when upgrading to the latest LTS runtime, I don't recall the init scripts failing.  Could you please confirm if my init script should run on the newer 13.3 LTS version, as it does on the LTS 12.2 version?

Thank you!

Benedetta

[ChloeBors · Accepted solution]

Hello Benedetta,

I had the same issue with an odbc init script.

Within the global script it was using an ubuntu version (16.04).
After I upgraded this version in the script to 22.04 it worked! (that 22.04 version also shows on Databricks Runtime 13.3 LTS | Databricks on AWS under System Environment)

I hope this will help you!

[Benedetta]

Thank you ChloeBors - I tried upgrading the ubuntu version per your suggestion but got a new error "Can t open lib ODBC Driver 17 for SQL Server file not found 0 SQLDriverConnect". I tried modifying this line to 18:  ACCEPT_EULA=Y apt-get install msodbcsql17 but I got the same error about 17. Not sure what to do next.