SAS Viya Oracle and ODBS db as preassigned libraries in SAS Studio.

[val_nikolajevs]

How to configure library as a Connection to Oralce and/or MS SQL database ins SAS Viya 4 similar to SAS 9.4 (nice and clear way to manage connections and users/groups).

I am not interested in CAS.

found these sources:

https://documentation.sas.com/api/collections/sasadmincdc/v_044/docsets/evfun/content/evfun.pdf?loca...

https://communities.sas.com/t5/SAS-Communities-Library/Where-to-define-your-SAS-libraries-in-SAS-Viy...

Able to connect to Oracle DB using libname statement and able to add resource in the SAS Studio session, see this as a resource in  environment manager contexts, SAS Studio compute context , so the library populates when user (that configured connection) starts SAS Studio Session.

I am trying to configure access using identities option in the Edit Compute Context and add/assign libraries and grant access to these based on  user/groups . I need to have an alias way to give users access to data sources, so the users do not see any DBs login data and manage users access based on groups.

Able to connect as the user that have access to the library in context configuration, but now all other users have SAS Studio compute context failing.

What I am missing; is this "normal" for this environment to be so unstable all this "close/open different browsers" business is a new standard or deployment is bad ?

Thank you.

[gwootton]

If I understand your description correctly, after adding a pre-assigned resource in your context definition, users who do not have a credential in the referenced authentication domain are unable to start a compute session with that context, is that correct?

You may wish to engage SAS Technical Support on this, I don't think that's expected behavior.

[val_nikolajevs]

Yes, that is the issue; contacted SAS--first feedback--it should not be this way.
Also is this normal, when one data source is not configured correctly or let say oracle client failed none of the libraries will be loaded? For example, in SAS 9.4 even if there is issue with connection to the one of db's other still get loaded.

[ravikumar901]

Hi ,

Is issue resolved? If yes can  you please say how to resolve.
Thanks in advance.

regards,
Ravi

[val_nikolajevs]

Hi Ravi,

No, Issue was not resolved.  Had to "scrap" deployment, still in the process just to do basic deployment and configuration.

I will let you know when/if we get to this. Would Appreciate if you can share solution, if you find it before.

Thank you,
Val

[gwootton]

@val_nikolajevs @ravikumar901 I believe this behavior was fixed with an update.

[JuanS_OCS]

This is a strange behavior in many ways indeed.

@gwootton could you pin point to the version and the applied fix? I think that would help.

The way I see it, when a pod starts with a fatal error, that could lead to the pod no starting at all. However what you indicate is that the pod started well, but it completely crashes after a failed connection with the driver/data connector. This seems indeed something for SAS Tech Support.

Where you able to test the connection with the same driver but outside from SAS, from the NodePool host?

Is the Authentication Domain and permissions sets working with other libraries?

[gwootton]

@JuanS_OCS The fix for the issue of a compute context failing to start when a user does not have access to a credential in the authentication domain specified for a library assigned to a context was made at Stable 2024.08, and released as a patch update to the supported releases containing the issue.

At LTS 2024.03, this was made available at sas-programming-environment image version 1.53.32
At Stable 2024.07, this was made available at sas-programming-environment image version 1.58.25

You can run this command to confirm the version of the sas-programming-environment image in use in your environment:

$ k get podtemplate sas-compute-job-config -o jsonpath='{.template.spec.containers[0].image}{"\n"}'

Instructions for applying a patch update to get this version can be found here:

Applying a Patch Update
https://go.documentation.sas.com/doc/en/sasadmincdc/v_057/k8sag/p0954mgxmsddrmn1klrphsbnqasm.htm

[ravikumar901]

My issue is when trying to create and connect a Spark library in the studio. The user's studio context closes and doesn't restart. This behavior only occurs when a user attempts to create and connect a library in the studio."

If i got solution i will share it you.

[ravikumar901]

Yes , Issue resolved after applying patch.

Thanks!

[JuanS_OCS]

Thanks for the confirmation @ravikumar901  and special thanks to you @gwootton for pointing out the relevant patch 😉