Problem Note 71046: JDBC Connections to Oracle fail after applying oracle DR RU 19.24
 |  |  |  |  |
Your version of a DataDirect driver that is used by SAS® Visual Investigator might be one that results in Oracle JDBC connections failing. you can find details of the specific driver version at JDBC connections to Oracle fail after Oracle database update.
In your datahub log, an error similar to the following occurs:
createPoolProperties(ALERT_STORE): ConnectionPool[defaultAutoCommit=null; defaultReadOnly=null; defaultTransactionIsolation=-1; defaultCatalog=null; driverClassName=org.postgresql.Driver; maxActive=100; maxIdle=0; minIdle=0; initialSize=0; maxWait=30000; testOnBorrow=true; testOnReturn
Oracle_SASFDEU: exception: Could not determine auto-commit behaviour: [SAS][Oracle JDBC Driver]null
Oracle_FD_SAP: exception: Could not determine auto-commit behaviour: [SAS][Oracle JDBC Driver]null
Oracle_SASFDEU: exception: Could not determine auto-commit behaviour: [SAS][Oracle JDBC Driver]null
Oracle_FD_SAP: exception: Could not determine auto-commit behaviour: [SAS][Oracle JDBC Driver]null
To circumvent this issue, it is necessary to update your version to SAS® Visual Investigator 10.8 Hot Fix 11.1.
Click the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
| Product Family | Product | System | Product Release | SAS Release | ||
| Reported | Fixed* | Reported | Fixed* | |||
| SAS System | SAS Visual Investigator (on SAS Viya 3.x) | Linux for x64 | 10.8 | Viya | ||
An update for this issue is available for SAS Visual Investigator 10.8. For instructions on how to access and apply these software updates, see the documentation links at the top of
https://tshf.sas.com/techsup/download/hotfix/HF2/Viya_VI_10_8_home.html#71046| Type: | Problem Note |
| Priority: | high |
| Date Modified: | 2024-11-13 09:46:02 |
| Date Created: | 2024-11-12 14:41:14 |