After you upgrade to SAS^® Viya^® Stable 2025.11 or later, the table.loadDataSource action is unable to load any SAS^® Data Connectors. The sas-cas-server-default-control pod logs an error message:

{"level":"error","message":"Extension Load Failure: OS Error: -1 (libclntsh.so.12.1: cannot
open shared object file: No such file or directory)","messageKey":"TKS_OS_LOAD_FAILURE",
"properties":{"caller":"sklstoj.c:118","pod":"sas-cas-server-default-
controller","sessionIndex":"20","sessionPid":"3227","sessionUser":
"sas.planning","thread":"00000007"},"source":"cas-shared-default","timeStamp":
"2026-01-07T17:26:30.436000+00:00","version":1}

Due to this error, other processes and pods fail:

• CASLIBs using a dataSource fail to be created, which causes the MRM Reporting Library to be missing. 
• The sas-planning pod fails to start successfully. The sas-planning pod log contains messages similar to the following:
  DBMS Precondition failed: expected oracle, got postgresql\n","properties":{"logger":"liquibase.changelog","thread":"main"}}
  
  "version":1,"timeStamp":"2026-01-07T20:37:16.918Z","level":"warn","source":"sas-planning","message":"failed to create and cache initial CAS connection\ncom.sas.cas.CASException: The specified datasource could not be loaded 
  
  "level":"error","source":"sas-planning","message":"Cannot read field \"applicationContext\" because \"com.sas.solutions.services.util.StaticContextAccessor.instance\" is null\njava.lang.NullPointerException: Cannot read field \"applicationContext\" because \"com.sas.solutions.services.util.StaticContextAccessor.instance\" is null","properties":{"logger":"com.sas.solutions.util.AutomaticNumberFactory","thread":"main"}}

Cause

Since SAS^® Viya^® Stable 2024.05, the Oracle Instant Client libraries are included with the SAS Viya deployment. With Stable 2025.11, SAS Cloud Analytic Services uses a library linked to the Oracle Instant Client library, libclntsh.so.12.1. An environment variable, ORACLE, points to the shipped location of the libclntsh.so.12.1 library in the default deployment assets. When you deploy SAS/ACCESS^® Interface for Oracle, you can change the deployment to point to a different version of the Oracle Instant Client libraries. The sas-access.properties file is updated to set the ORACLE environment variable to the location of the Oracle Client libraries. If this location does not have the libclntsh.so.12.1 library, SAS Cloud Analytic Services is unable to load the SAS Data Connectors library.

Resolution

• If you do not need the Oracle Instant Client library or if it is not provided in your deployment, remove the setting of the ORACLE environment variable from the sas-access.properties file. 
• If the provided libraries do not include the libclntsh.so.12.1 library, update the ORACLE environment variable in the sas-access.properties file to include the shipped location(/opt/sas/viya/home/lib64/accessclients/oracle/19.22/client64/lib) at the end. 
  
  Here is an example:

   ORACLE=/data-drivers/access-clients/oracle:/opt/sas/viya/home/lib64/accessclients/oracle/19.22/client64/lib

Note: Update the deployment after changing the sas-access.properties file and restart the CAS deployment.