BookmarkSubscribeRSS Feed
🔒 This topic is solved and locked. Need further help from the community? Please sign in and ask a new question.
aarcad3100
Calcite | Level 5
Thank you so much @alexal.
That fixed it.
Do you know if that will impact the ability to connect to SQL Server?
Thanks again for your help.
alexal
SAS Employee

@aarcad3100 ,

 

No, you should be able to connect.

aarcad3100
Calcite | Level 5

Hi @alexal ,

Thanks again for your help with fixing the JVE issue. 

We lost the ability to connect to SQL server after modifying the sasenv file. 

we are getting the error below in EG when attempting to connect. We were able to connect prior to modifying the file using the same statement. Thanks in advance for your help.

 

ERROR: CLI error trying to establish connection: [unixODBC][Driver Manager]Data source name not found and no default driver

       specified

ERROR: Error in the LIBNAME statement.

alexal
SAS Employee

@aarcad3100 ,

 

This has nothing to do with LD_LIBRARY_PATH. Something is wrong with your library statement and/or your driver configuration.

Kurt_Bremser
Super User

@aarcad3100 wrote:

Hi @alexal ,

Thanks again for your help with fixing the JVE issue. 

We lost the ability to connect to SQL server after modifying the sasenv file. 

we are getting the error below in EG when attempting to connect. We were able to connect prior to modifying the file using the same statement. Thanks in advance for your help.

 

ERROR: CLI error trying to establish connection: [unixODBC][Driver Manager]Data source name not found and no default driver

       specified

ERROR: Error in the LIBNAME statement.


Looks like you overwrote some existing configuration when you made your change. Get the previous version from your backup and compare it.

aarcad3100
Calcite | Level 5

Thanks for your reply @Kurt_Bremser.

the original sasenv_local file was:

############################################################################

export ODBCHOME=/opt/microsoft/msodbcsql17
export ODBCSYSINI=/etc/
export ODBCINI=/etc/odbc.ini


export LD_LIBRARY_PATH=/usr/lib64/:/opt/sas/sashome/SASODBCDriversfortheWebInfrastructurePlatformDataServer/9.4/Driver/:$ODBCHOME/lib:/opt/sas/sashome/SASFoundation/9.4/sasexe

############################################################################

 

the new one is:

############################################################################

export ODBCHOME=/opt/microsoft/msodbcsql17
export ODBCSYSINI=/etc/
export ODBCINI=/etc/odbc.ini

 

export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:/usr/lib64/:$ODBCHOME/lib

############################################################################

 

Thanks again for your help. 

Kurt_Bremser
Super User

These are the crucial parts:

export LD_LIBRARY_PATH=/usr/lib64/:/opt/sas/sashome/SASODBCDriversfortheWebInfrastructurePlatformDataServer/9.4/Driver/:$ODBCHOME/lib:/opt/sas/sashome/SASFoundation/9.4/sasexe

here you create the complete LD_LIBRARY_PATH from scratch, without any reference to an existing one.

export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:/usr/lib64/:$ODBCHOME/lib

here you use the system-supplied variable and just add /usr/lib64/:$ODBCHOME/lib

I'd combine both, for safety's sake:

export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:/usr/lib64/:/opt/sas/sashome/SASODBCDriversfortheWebInfrastructurePlatformDataServer/9.4/Driver/:$ODBCHOME/lib:/opt/sas/sashome/SASFoundation/9.4/sasexe

You might end up with some duplicates, but you won't miss anything.

suga badge.PNGThe SAS Users Group for Administrators (SUGA) is open to all SAS administrators and architects who install, update, manage or maintain a SAS deployment. 

Join SUGA 

Get Started with SAS Information Catalog in SAS Viya

SAS technical trainer Erin Winters shows you how to explore assets, create new data discovery agents, schedule data discovery agents, and much more.

Find more tutorials on the SAS Users YouTube channel.

Discussion stats
  • 21 replies
  • 7541 views
  • 4 likes
  • 6 in conversation