A side note on this topic...
When setting up the Vertica ODBC 5.1 driver initially, I also experienced the same error as Josh. Once I added the additional ODBC driver configuration settings in an /etc/vertica.ini file and set the VERTICAINI environment variable to point to the file, the connection to Vertica worked as expected.
Whats interesting is that afterwards I found that I could delete the /etc/vertica.ini file and set the VERTICAINI variable to nothing and my connection would still work.
Here are my current settings odbc.ini file contents:
Code: Select all
[root@CUBEBUILDER01 etc]# cat odbc.ini
[verticatst01]
Driver = /opt/vertica/lib/libverticaodbc.so
Servername = verticatst01
Database = vertica01
Port = 5433
UserName = cognos
Password = xxxxx
Note that /opt/vertica/lib/libverticaodbc.so links to libverticaodbc.so.5.1.5:
Code: Select all
[root@CUBEBUILDER01 etc]# ls -lrt /opt/vertica/lib/libverticaodbc.so
lrwxrwxrwx 1 root root 23 May 23 07:04 /opt/vertica/lib/libverticaodbc.so -> libverticaodbc.so.5.1.5
My VERTICAINI environment variable is now set to nothing:
Code: Select all
[root@CUBEBUILDER01 etc]# echo $VERTICAINI
[root@CUBEBUILDER01 etc]
But I can still connect:
Code: Select all
[root@CUBEBUILDER01 etc]# isql -v verticatst01
+---------------------------------------+
| Connected! |
| |
| sql-statement |
| help [tablename] |
| quit |
| |
+---------------------------------------+
SQL> select count(*) from tables;
+---------------------+
| count |
+---------------------+
| 214 |
+---------------------+
SQLRowCount returns 1
1 rows fetched
I found this to be interesting. I wonder if the setting were added to some underlying ODBC config file?