This can be caused by a variety of issues, but resources limitations usually being the common cause such as running out of storage in SASWORK or overreaching the memory limits for the sas-programming-environments container in the sas-compute-server pod. I would recommend to configure external strorage for SASWORK as described in the documentation so that the ephemeral storage on the compute node is not being utilized (emptyDir). You might want to check the describe of your compute node to ensure that the node is not having any disk pressure when this issue occurs.: Configure External Storage Class https://go.documentation.sas.com/doc/cn/sasadmincdc/v_059/calsrvpgm/n0k315nlna2awln119phkhua1na2.htm And/or increase the launcher memory limits: Manage Requests and Limits for CPU and Memory https://go.documentation.sas.com/doc/ja/itopscdc/v_058/itopssrv/p0wvl5nf1lvyzfn16pqdgf9tybuo.htm#n0u9kbsqdgyoean1ofbds3oe4wq5 If your program or job causes the sas-programming-environments container to exceed the memory limits (default is 2Gi) then kubernetes will terminate the sas-compute-server pod which you would then see the warning message in SAS Studio Viya stating that your session has encountered a problem and prompting you to reset the session. I would recommend testing with setting the launcher memory limits to something like 8Gi to see how things behave. ... View more

Hi Ravi, I don't think the CAS server itself runs a JVM, so this OOM is probably coming from one of the supporting services. I'd start by checking the log of the sas-data-explorer-app pod to see if you see the java.lang.OutofMemoryError in there and if so, increase the Xmx for the service SAS Data Explorer's jvm definition in Env Mgr > Configuration > All Services > SAS Data Explorer. ... View more

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

One can reference the details in $deploy/sas-bases/examples/data-access/README.md for your installation. The ODBC clients/drive need to be installed in a Persistent Volume storage.  One should typically be able to access with ssh. There must be a jump box to access this. I would prefer creating a separate folder for each ODBC driver Select a driver that could be extracted and used (tar.gz extension) rather that that needs installation (rpm) The video I referred to above and the readme file as above are helpful and the process pretty straight forward. ... View more