Drop Down MenusCSS Drop Down MenuPure CSS Dropdown Menu

vertica Database installation

-
Installing Vertica is fairly simple. With the following steps, we will try to understand a two-node cluster:
  1. Download the Vertica installation package from http://my.vertica.com/ according to the Linux OS that you are going to use.
  2. Now log in as root or use the sudo command.
  3. After downloading the installation package, install the package using the standard command:
    • For .rpm (CentOS/RedHat) packages, the command will be:
      rpm -Uvh vertica-x.x.x-x.x.rpm
    • For .deb (Ubuntu) packages, the command will be:
      dpkg -i vertica-x.x.x-x.x.deb
    Refer to the following screenshot for more details:

    Running the Vertica package
  4. In the previous step, we installed the package on only one machine. Note that Vertica is installed under /opt/vertica. Now, we will set up Vertica on other nodes as well. For that, run the following command on the same node:
    /opt/vertica/sbin/install_vertica -s host_list -r rpm_package -u dba_username
    Here, –s is the hostname/IP of all the nodes of the cluster, including the one on which Vertica is already installed. –r is the path of the Vertica package and –u is the username that we wish to create for working on Vertica. This user has sudo privileges. If prompted, provide a password for the new user. If we do not specify any username, then Vertica creates dbadmin as the user, as shown in the following example:
    [impetus@centos64a setups]$ sudo /opt/vertica/sbin/install_vertica -s 192.168.56.101,192.168.56.101,192.168.56.102 -r "/ilabs/setups/vertica-6.1.3-0.x86_64.RHEL5.rpm" -u dbadmin


Vertica Analytic Database 6.1.3-0 Installation Tool
Upgrading admintools meta data format..
scanning /opt/vertica/config/users
Starting installation tasks...
Getting system information for cluster (this may take a while)....

Enter password for impetus@192.168.56.102 (2 attempts left):
backing up admintools.conf on 192.168.56.101
Default shell on nodes:
192.168.56.101 /bin/bash
192.168.56.102 /bin/bash

Installing rpm on 1 hosts....
installing node....  192.168.56.102

NTP service not synchronized on the hosts: ['192.168.56.101', '192.168.56.102']

Check your NTP configuration for valid NTP servers.


Vertica recommends that you keep the system clock synchronized using NTP or some other time synchronization mechanism to keep all hosts synchronized. Time variances can cause (inconsistent) query results when using Date/Time Functions. For instructions, see:
  * http://kbase.redhat.com/faq/FAQ_43_755.shtm
  * http://kbase.redhat.com/faq/FAQ_43_2790.shtm

Info: the package 'pstack' is useful during troubleshooting.  Vertica recommends this package is installed.

Checking/fixing OS parameters.....
Setting vm.min_free_kbytes to 37872 ...
Info! The maximum number of open file descriptors is less than 65536
Setting open filehandle limit to 65536 ...
Info! The session setting of pam_limits.so is not set in /etc/pam.d/su
Setting session of pam_limits.so in /etc/pam.d/su ...
Detected cpufreq module loaded on 192.168.56.101
Detected cpufreq module loaded on 192.168.56.102
CPU frequency scaling is enabled.  This may adversely affect the performance of your database.
Vertica recommends that cpu frequency scaling be turned off or set to 'performance'

Creating/Checking Vertica DBA group

Creating/Checking Vertica DBA user

Password for dbadmin:
Installing/Repairing SSH keys for dbadmin

Creating Vertica Data Directory...

Testing N-way network test.  (this may take a while)
 All hosts are available                            ...  
Verifying system requirements on cluster.
 IP configuration                                   ...  
 IP configuration                                   ...  
Testing hosts (1 of 2)....

Running Consistency Tests
 LANG and TZ environment variables                  ...  
Running Network Connectivity and Throughput Tests...
Waiting for 1 of 2 sites...                         ...  

  Test of host 192.168.56.101 (ok)  
====================================

    Enough RAM per CPUs (ok)  
  --------------------------------
  

  Test of host 192.168.56.102 (ok)  
====================================

    Enough RAM per CPUs (FAILED)  
  --------------------------------
    Vertica requires at least 1 GB per CPU (you have 0.71 GB/CPU)
    See the Vertica Installation Guide for more information.
  

  Consistency Test (ok)  
=========================

  Info: The $TZ environment variable is not set on  192.168.56.101
  Info: The $TZ environment variable is not set on  192.168.56.102

Updating spread configuration...
Verifying spread configuration on whole cluster.
Creating node node0001 definition for host 192.168.56.101
... Done
Creating node node0002 definition for host 192.168.56.102
... Done
Error Monitor  0 errors  4 warnings
Installation completed with warnings.  
Installation complete.

To create a database:
1. Logout and login as dbadmin.**
2. Run /opt/vertica/bin/adminTools as dbadmin
3. Select Create Database from the Configuration Menu

** The installation modified the group privileges for dbadmin.
   If you used sudo to install vertica as dbadmin, you will
   need to logout and login again before the privileges are applied.
  5. After we have installed Vertica on all the desired nodes, it is time to create a database. Log in as a new user (dbadmin in default scenarios) and connect to the admin panel. For that, we have to run the following command:
    /opt/vertica/bin/adminTools
  6. If you are connecting to admin tools for the first time, you will be prompted for a license key. If you have the license file, then enter its path; if you want to use the community edition, then just click on OK.

    License key prompt
  7. After the previous step, you will be asked to review and accept the End-user License Agreement (EULA).

    Prompt for EULA
    After reviewing and accepting the EULA, you will be presented with the main menu of the admin tools of Vertica.

    Admin tools main menu
  8. Now, to create a database, navigate to Administration Tools | Configuration Menu | Create Database.

    The Create Database option in the configuration menu
  9. Now, you will be asked to enter a database name and a comment that you would like to associate with the database.

    Database name and comments
  10. After entering the name and comment, you will be prompted to enter a password for this database.

    Password for the new database
  11. After entering and re-entering (for confirmation) the password, you need to provide pathnames where the files related to user data and catalog data will be stored.

    Catalog and data pathnames
    After providing all the necessary information related to the database, you will be asked to select hosts on which the database needs to be deployed. Once all the desired hosts are selected, Vertica will ask for one final check.

    Final confirmation for database creation
  12. Now, Vertica will create and deploy the database.

    Database creation
  13. Once the database is created, we can connect to it using the VSQL tool or perform admin tasks.

Comments

Post a Comment

Popular posts from this blog

How to find the server is whether standby (slave) or primary(master) in Postgresql replication ?

-
Method 1 You can check the mode of the server using "pg_controldata". [pgsql@test~]$ pg_controldata /usr/local/pgsql/data84/ Database cluster state: in archive recovery --> This is Standby Database Database cluster state: in production --> This is Production Database [Master] Method 2 You can use pg_is_in_recovery() which returns True if recovery is still in progress(so the server is running in standby mode or slave) postgres=# select pg_is_in_recovery(); pg_is_in_recovery ------------------- t (1 row) If Return    false   so the server is running in primary mode or master postgres=# select pg_is_in_recovery(); pg_is_in_recovery ------------------- f (1 row)
Read more

7 Steps to configure BDR replication in postgresql

-
Image
 The  BDR  (Bi-Directional Replication) project adds multi-master replication to PostgreSQL 9.4.  Postgres-BDR has a lower impact on the masters(s) than trigger-based replication solutions. There is no write-amplification, as it does not require triggers to write to queue tables in order to replicate writes.   Here We are using  postgres version 9.4.12 and bdr version 1.0.2. for configuring  multi master replication . Simply Following 7 steps you can configure the multi master replication in postgresql. To download the bdr in below link. .   https://github.com/2ndQuadrant/bdr/archive/bdr-pg/REL9_4_12-1.tar.gz $ tar -xzvf REL9_4_12-1.tar.gz $ wget https://github.com/2ndQuadrant/bdr/archive/bdr-plugin/1.0.2.tar.gz $ tar -xzvf 1.0.2.tar.gz 1. To install BDR. $ cd ~/bdr-bdr-pg-REL9_4_12-1 $ ./configure --prefix=/usr/lib/postgresql/9.4 --enable-debug --with-openssl $ make -j4 -s install-world $ cd ~/bdr-bdr-plugin-1.0.2 $ PATH=/usr/lib/postgresql/9.4/bin:"$PATH" ./c
Read more

How to Get Table Size, Database Size, Indexes Size, schema Size, Tablespace Size, column Size in PostgreSQL Database

-
In this post, I am sharing few important function for finding the size of database, table and index in PostgreSQL. Finding object size in postgresql database is very important and common. Is it very useful to know the exact size occupied by the object at the tablespace. The object size in the following scripts is in GB. The scripts have been formatted to work very easily with PUTTY SQL Editor. 1. Checking table size excluding table dependency: SELECT pg_size_pretty(pg_relation_size('mhrordhu_shk.mut_kharedi_audit')); pg_size_pretty ---------------- 238 MB (1 row) 2. Checking table size including table dependency: SELECT pg_size_pretty(pg_total_relation_size('mhrordhu_shk.mut_kharedi_audit')); pg_size_pretty ---------------- 268 MB (1 row) 3. Finding individual postgresql database size SELECT pg_size_pretty(pg_database_size('db_name')); 4. Finding individual table size for postgresql database -including dependency index: SELECT pg_size_pretty(pg_total_rel
Read more

Ora2PG - Oracle/MySQL to Postgres DB migration Version 20.0

-
Ora2Pg is a free tool used to  migrate  an  Oracle  or MySQL database to a  PostgreSQL  compatible schema. It connects your  Oracle  database, scan it automatically and extracts its structure or data, it then generates SQL scripts that you can load into your  PostgreSQL  database. ora2pg version 20.0 software : ora2pg-20.0.tar ora2pg-20.0   https://github.com/darold/ora2pg/releases/tag/v20.0 Some Blogs about DB Migration : https://2ndquadrant.in/postgresmigration/oracle-to-postgresql-migration/ https://2ndquadrant.in/database-migration-from-oracle-to-postgres/ INSTALLATION All Perl modules can always be found at CPAN ( http://search.cpan.org/ ). Just type the full name of the module (ex: DBD::Oracle) into the search input box, it will brings you the page for download. Releases of Ora2Pg stay at SF.net ( https://sourceforge.net/projects/ora2pg/ ). Under Windows you should install Strawberry Perl ( http://strawberryperl.com/ ) and the OSes corresponding Oracle clients. I
Read more

PostgreSQL Introduction

-
PostgreSQL tutorial provides basic and advanced concepts of SQL. Our PostgreSQL tutorial is designed for beginners and professionals. PostgreSQL is an opens-source object-relational database management system (ORDBMS). Our PostgreSQL tutorial includes all topics of PostgreSQL language such as create database, create table, drop database, drop table, select database, select table, insert record, update record, delete record, triggers, functions, procedures, cursors etc. There are also given PostgreSQL interview questions and quizzes to help you better understand the PostgreSQL language. Prerequisite: Before you start doing practice with various types of examples given in this reference, I'm making an assumption that you are already aware about what is database, especially RDBMS and what is a computer programming language. you must have the basic knowledge of SQL Problem: We assure that you will not find any problem in this PostgreSQL tutorial. But if there is any mistake
Read more