Symptom
- You performed a takeover to a secondary site, and run into an SDA connection error from the new primary site(old secondary site).
- SAP DBTech JDBC: [403]: internal error: Cannot get remote source objects: Unable to load driver manager
- MSSQL drivers were not installed on this new primary site prior to this takeover, and this ODBC driver got copied from the old primary site.
- ODBC driver can be seen in the library directory, and it's correctly specified in .odbc.ini
- ODBC driver
- myhanahost:/opt/microsoft/msodbcsql17/lib64 # ls -ltr total 2024
-rwxr-xr-x 1 root root 2071864 Jan 31 2024 libmsodbcsql-17.10.so.6.1
- myhanahost:/opt/microsoft/msodbcsql17/lib64 # ls -ltr total 2024
- .odbc.ini
- hanadm@myhanahost:/usr/sap/HAN/home> cat odbc.ini
[MSSQL]
Driver=/opt/microsoft/msodbcsql17/lib64/libmsodbcsql-17.10.so.6.1
Server=10.100.10.xxx,1433
Database=HAN
"Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental."
- hanadm@myhanahost:/usr/sap/HAN/home> cat odbc.ini
- ODBC driver
Read more...
Environment
- SAP HANA 2.0, Platform edition
- MSSQL Server
Product
SAP HANA, platform edition 2.0
Keywords
HANA SDA connection issue, failover, MSSQL drivers, SAP DBTech JDBC 403, remote source objects, driver manager, LD_LIBRARY_PATH, ODBC driver, SAP HANA Smart Data Access , KBA , HAN-DB-SDA , SAP HANA Smart Data Access , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.
SAP Knowledge Base Article - Preview