Thank you for your answer. I wish I could buy you a beer. 🙂 My solution was slightly different but starring me right in the face. Your answer provided the perfect clue. In my case, there was no "universal" directory. However, I noticed there was a CA bundle file. It DID NOT come preconfigured with the GeoTrust CA we have for the SSL certificate we purchased for our F5. It did have some other GeoTrust CA and many others, as well. I simply opened up the cacerts.pem file and added that GeoTrust CA to the end, saved the file, and ran my test query. It then worked! [mpetronic@vmwhnsqsrclnt01 ~]$ echo "show tables" | isql -d, -b -v f5 mpetronic $(cat ~/.pw.dat) cro_capacity_extract_tmp cro_capacity_ranked_tmp cro_capacity_report_final cro_efficiency_extract_tmp cro_efficiency_hourly_tmp cro_efficiency_report_final j1_total_user_counts san_data_2 test Here is what my directory structure looks like for the ODBC driver version I am using: [root@vmwhnsqsrclnt01 lib]# tree /usr/lib/hive/ hive └── lib └── native ├── hiveodbc │ ├── ErrorMessages │ │ └── en-US │ │ ├── DSMessages.xml │ │ ├── HiveODBCMessages.xml │ │ ├── ODBCMessages.xml │ │ ├── SQLEngineMessages.xml │ │ └── ThriftExtensionMessages.xml │ ├── EULA.txt │ ├── Hortonworks\ Hive\ ODBC\ Driver\ User\ Guide.pdf │ ├── Release\ Notes.txt │ └── Setup │ ├── odbc.ini │ └── odbcinst.ini └── Linux-amd64-64 ├── api.prod.quasar.nadops.net.pem ├── cacerts.pem <<< Added GeoTrust CA to end of this file ├── cacerts.pem.orig ├── HiveODBC.did ├── hortonworks.hiveodbc.ini └── libhortonworkshiveodbc64.so ... View more