Using the dradmin OS user as both install owner and DB admin user
search cancel

Using the dradmin OS user as both install owner and DB admin user

book

Article ID: 384825

calendar_today

Updated On:

Products

Network Observability CA Performance Management

Issue/Introduction

Can the dradmin DB admin user configured for DX NetOps Performance Management Data Repository Vertica database administration be used for installs and upgrades?

Can we use one user for DR DB installs, upgrades and database administration?

Do we have to use a root or sudo root user that is different from the dradmin database administrator user for DR DB installs or upgrades?

Environment

All supported DX NetOps Performance Management releases

Resolution

Ensure the dradmin user /etc/sudoers configuration contains all required commands specified in the Prepare to Install the Data Repository documentation. With the config set for the same user to allow but installs/upgrades, and database administration a second user isn't needed.

  • The sudoers file config for the dradmin user needs to have command access specified in the documentation for both install and admin user.
  • When using a sudo user that has passwordless SSH keys set up, when we know the password for that OS user, we must do one of the following.
    • Set the password in drinstall.properties SudoPassword field.
    • Enter it on the CLI when prompted.
  • When running the dr_validate, dr_install or other commands, the new features allow us to run them without the "sudo" command preceding it.
    • The new features are able to ID the fact that it's a sudo user and precedes commands that require it with the 'sudo' command where needed.
    • Instead of running this as the dradmin sudo user.
      • [dradmin@Node0001 IMDataRepository_vertica23]$ sudo ./dr_validate.sh -p drinstall.properties
    • Run this, minus the 'sudo' part of the command.
      • [dradmin@Node0001 IMDataRepository_vertica23]$ ./dr_validate.sh -p drinstall.properties

Once the /etc/sudoers file configuration is correct on all nodes the commands should be successful. If not successful review the resulting log for additional information or open a new Support case for additional assistance.