Backing Down to a Previous Teradata Viewpoint Version - 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
If an upgrade of Teradata Viewpoint does not complete successfully, the following steps allow you to back down to the previously installed version of Teradata Viewpoint.

The only supported mechanism to backdown Teradata Viewpoint is to use VM&F during the upgrade.

  1. Reboot back into the alternate boot environment that contains the copy of the root partition prior to the upgrade.
  2. Stop all of the Teradata Viewpoint services on all Teradata Viewpoint servers by typing:
    /opt/teradata/viewpoint/bin/vp-control.sh stop
  3. Stop Postgres service by using service postgresql stop.
  4. If the Teradata Notification Service is running on a Windows server, stop this service.
  5. If the /data/db-backup directory exists and the creation time matches the time of last upgrade, do the following:
    1. Move the existing /data/viewpointdb directory to another location.
    2. Replace it with the /data/db-backup directory.
  6. If the /data/db-backup directory does not exist or is not recent, restore the last successful backup of the Teradata Viewpoint databases.
    The duration of this process varies depending on the size of the databases. If the Teradata Viewpoint databases are in a clustered environment, perform the restore against the primary database server.
  7. Restore the Viewpoint portal.
    1. Uninstall the Viewpoint package:
      rpm -e --nodeps viewpoint
    2. Reinstall the version of the Viewpoint package that was uninstalled:
      rpm -ivh viewpoint*.rpm
    3. Force Install other viewpoint related rpms:
      • 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

      For Viewpoint 22.10 and later:

      • rpm -Uvh --force postgresql10-devel*.rpm
      • rpm -Uvh –force standardconfig*.rpm
      If there are external portlets like bar and dm are installed, re-install:
      • rpm -Uvh --force barportlets*.rpm
      • rpm -Uvh --force tdmportlets*.rpm
    4. Run the Postgres service using service postgresql start.
    5. Run changedbpasswd.sh:
      /opt/teradata/viewpoint/dcs/bin/changedbpasswd.sh
    6. Run the post-upgrade setup scripts:
      If setupDb.sh is available, then run /opt/teradata/viewpoint/dcs/bin/setupDb.sh, or else run:
      • /opt/teradata/viewpoint/portal/bin/setup.sh
      • /opt/teradata/viewpoint/dcs/bin/setup.sh
      • /opt/teradata/cam/alert/bin/setupdb.sh
    7. 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

    8. Start all services:
      /opt/teradata/viewpoint/bin/vp-control.sh start