I haven't installed the console yet, but I am guessing that you can use it to manage a 5.0 databases. I can't find anywhere in the documentation that states otherwise. To install the console you need a whole new server! You can't use one of the nodes in the cluster for the console. Now that I'm thin...

The Vertica search_path works just like the the PATH variable in Linux or DOS. If a table with the same name exists in more than one schema, Vertica will simply use the first of those schemas listed in your search_path variable. Example: dbadmin=> create schema test1; CREATE SCHEMA dbadmin=> create ...

You can add a database schema to your search_path variable so that when you log in you won't have to prefix table names with that schema. For instance, if I log into Vertica as the user dbadmin and I want to query the employee_zip_dim table in the cognos schema, normally I would have to write the fo...

What is the error that you are getting? For one thing, you can't have spaces after the commas that separate the IP addresses. Try this: /opt/vertica/sbin/install_vertica -s 10.255.11.130,10.255.11.140,10.255.11.150 -r vertica-5.0.11-0.x86_64.RHEL5.rpm -u vadmin Everything else looks good. How come y...

Here are a few links to very interesting discussions about Vertica:

http://www.dbms2.com/2011/09/05/zynga-l ... #more-5159
http://www.dbms2.com/2011/06/20/columna ... r-metrics/

Vertica does not support the CLOB or BLOB data types. It does support the data types CHARACTER ( CHAR ) and CHARACTER VARYING ( VARCHAR ). Each of these data types has a maximum length of 65000 bytes which is unfortunately a tad bit smaller than the 4 GB you can store in a CLOB in Oracle. Maybe you ...