Does the dradmin user require verticadba as it's primary group?

book

Article ID: 225420

calendar_today

Updated On:

Products

CA Performance Management - Usage and Administration DX NetOps

Issue/Introduction

Our environment requires non-local dradmin user through Active Directory.

Our environment does not allow for special primary groups set for the users so won't allow the verticadba group to be used as a primary group.

Due to this the install or upgrade of Vertica fails. Is there a way around this?

Cause

Environmental limitations prevent verticadba from being set as primary group.

Environment

All supported DX NetOps Performance Management releases

Resolution

There are a few locations we will need to change in order to allow the use of a different group than verticadba.

  1. Modify the default set in the dr_install.sh script VERTICA_DBA_GROUP variablle.
    1. Open the (default path) /opt/CA/IMDataRepository_vertica<version>/dr_install.sh script for editing.
    2. Change the VERTICA_DBA_GROUP value from verticadba to the group set as the dradmin users primary group.
  2. Add the --dba-group argument and value to the install_vertica command run in the dr_install.sh script.
    1. Change this entry.
      printTitle "Invoking install_vertica..."
      /opt/vertica/sbin/install_vertica -s $DB_HOST_NAMES -u $DB_ADMIN_LINUX_USER -l $DB_ADMIN_LINUX_USER_HOME -d $DB_DATA_DIR -L ./resources/$VLICENSE -Y -r ./resources/$VERTICA_RPM_FILE $POINT_TO_POINT_SPREAD_OPTION $failure_threshold 2>&1 | tee -a $LOG_FILE
    2. Edit the install_vertica line in the script.
      1. Add this to the command: --dba-group <groupName>
      2. Example: Using a group named verticadba_prd? It would be: --dba-group verticadba_prd
    3. The full edited line would be:
      printTitle "Invoking install_vertica..."
      /opt/vertica/sbin/install_vertica -s $DB_HOST_NAMES -u $DB_ADMIN_LINUX_USER -l $DB_ADMIN_LINUX_USER_HOME -d $DB_DATA_DIR --dba-group <groupName> -L ./resources/$VLICENSE -Y -r ./resources/$VERTICA_RPM_FILE $POINT_TO_POINT_SPREAD_OPTION $failure_threshold 2>&1 | tee -a $LOG_FILE