Backing Down from an OS Migration | Teradata Viewpoint - Backing Down from an OS Migration - Teradata Viewpoint

Teradata® Viewpoint Installation, Configuration, and Upgrade Guide for Customers - 24.04

Deployment
VantageCloud
VantageCore
Edition
Enterprise
IntelliFlex
Lake
VMware
Product
Teradata Viewpoint
Release Number
24.04
Published
April 2024
Language
English (United States)
Last Update
2024-04-29
dita:mapPath
ohm1711972149764.ditamap
dita:ditavalPath
acl1501004736403.ditaval
dita:id
ulq1467244577135
Product Category
Analytical Ecosystem

When an OS migration of Teradata Viewpoint does not complete successfully, you need to back down the OS. After backing down the OS, perform the following steps to restart the Viewpoint services.

  1. Bring down all services:
    /opt/teradata/viewpoint/bin/vp-control.sh stop
  2. Re-install all Viewpoint rpms:
    • rpm -Uvh --force viewpoint*.rpm
    • rpm -Uvh --force dcs*.rpm
    • rpm -Uvh --force camalert*.rpm
    • rpm -Uvh --force camportlets*.rpm
    • rpm -Uvh --force querygridportlet*.rpm
    • rpm -Uvh --force tasmportlets*.rpm
    • rpm -Uvh --force tddatalabsportlets*.rpm
    • rpm -Uvh --force tdmgmtportlets*.rpm
    • rpm -Uvh --force tmsmonitor*.rpm
  3. Run changedbpasswd.sh:
    /opt/teradata/viewpoint/dcs/bin/changedbpasswd.sh
  4. Run setupDb.sh
    /opt/teradata/viewpoint/dcs/bin/setupDb.sh
  5. Run rpm -qa | grep viewpointlog4j to check if log4j remediation was applied. If yes, then:
    1. Delete the remediation trace files:
      rm /etc/opt/teradata/log4j-*viewpoint
    2. Re-install the log4j remediation:
      rpm -Uvh --force viewpointlog4j*.rpm
  6. Restart all services:
    /opt/teradata/viewpoint/bin/vp-control.sh restart