topic Re: validating connect and grid server from SMC and failing due to Oracle and odbc in Administration and Deployment

validating connect and grid server from SMC and failing due to Oracle and odbc

sathya66 — Tue, 20 May 2025 17:23:47 GMT

Hi All,

Trying to validate the grid and connect server from SMC but they are failing due to oracle and odbc libs. getting below ERROR

ERROR: Could not load opt/sas/home/SASFoundation/9.4/sasexe/sasodb (43 images loaded) [5/19/25, 5:13 PM] FINE: ERROR: libodbc.so: cannot open shared object file: No such file or directory [5/19/25, 5:13 PM] FINE: ERROR: Extension Load Failure: OS Error: -1 (/opt/oracle/19c/lib//libclntsh.so: cannot open shared object file: Permission denied) ERROR: Unable to load oracle client (libclntsh.so) ERROR: Libref xxxx failed to assign from logical server. ERROR: The SAS/ACCESS Interface to ODBC cannot be loaded. The SASODB code appendage could not be loaded. ERROR: Libref xxxxx failed to assign from logical server.

Re: validating connect and grid server from SMC and failing due to Oracle and odbc

EyalGonen — Mon, 26 May 2025 10:33:13 GMT

Check this out: https://communities.sas.com/t5/Administration-and-Deployment/SAS-Access-Oracle-Configuration/td-p/927516

Re: validating connect and grid server from SMC and failing due to Oracle and odbc

SASKiwi — Mon, 26 May 2025 20:06:41 GMT

Looks like you have AUTOEXEC programs running at server startup assigning Oracle and ODBC LIBNAMES. Do these work correctly when accessing your grid server via EG or SAS Studio when using the same account you use with SMC? If you get the same type of errors then you may have a configuration issue and @EyalGonen 's link should help. If it works OK in EG or SAS Studio then I suspect the validation process itself is missing the correct configuration.

Re: validating connect and grid server from SMC and failing due to Oracle and odbc

sathya66 — Wed, 28 May 2025 13:21:18 GMT

Oracle is sorted but
We are not getting below error for ODBC
ERROR: could not load /home/sas/SASFoundation/9.4/sasexe/sasodb(47 images loaded)
ERROR: libodbc.so: cannot open shared object file: No such file or directory.
Libname test odbc defer=yes datasrc=test schena=dbo user=test password=xxx;
ERROR: The SAS/ACCESS Interface to ODBC cannot be loaded. The SASODB code appendage could not be loaded.

Re: validating connect and grid server from SMC and failing due to Oracle and odbc

EyalGonen — Wed, 28 May 2025 14:24:05 GMT

Can you run this code below and verifyy SAS/Access to ODBC is installed?

proc product_status;run;

Re: validating connect and grid server from SMC and failing due to Oracle and odbc

sathya66 — Wed, 28 May 2025 14:51:26 GMT

Yes I can see you it.

For SAS/ACCESS Interface to ODBC …
Custom version information:9.4_M8

Re: validating connect and grid server from SMC and failing due to Oracle and odbc

EyalGonen — Wed, 28 May 2025 15:06:52 GMT

Did you follow the instructions at https://support.sas.com/documentation/installcenter/en/ikfdtnunxcg/66380/PDF/default/config.pdf pg. 59 for configuring SAS/Access to ODBC?

You need to set LD_LIBRARY_PATH to the ODBC Driver's lib directory.

Re: validating connect and grid server from SMC and failing due to Oracle and odbc

sathya66 — Thu, 29 May 2025 20:32:24 GMT

Thanks for this.
It is a permission issue . Odbc.ini has 660 so we made it to 664 and it worked but we are still getting the below errors. When validating grid server and connect server, I can see successful ping and connection message in the log but validation is failing due to below errors.
ERROR: Libref test2 failed to assign from logical server.

ERROR: Libref test failed to assign from logical server.

ERROR: Libref test1 failed to assign from logical server.

Workspace, pooled workspace, stored process are validating but grid server and connect servers are not validating .

Do we need to amend any config/ autoexec files in grid server and connect server? I know , user doesn’t have access to some libraries and it will give permission issue but how can we bypass this error to validate grid and connect server successfully.
If I run Workspaceserver.sh with nodms from the server, I can see the same libname errors as above but I can run a sas code successfully.