Back Down to a Previous Teradata Alerts Version | Teradata Viewpoint - Backing Down to a Previous Teradata Alerts 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 Alerts does not complete successfully, the following steps allow you to back the system down to the previously installed version. Note that xx represents the specific version of the software.

This procedure is only for backing down from Teradata Alerts 16.20.00.xx to release 16.10.00.xx, 16.00.00.xx, 15.11.00.xx, 15.10.00.xx, 15.00.00.xx, or 14.10.00.xx.

If backing down to an earlier version of Teradata Alerts, make sure that any applications that require the version being removed are also backed down.
  1. If the Teradata Notification Service is running on a Windows Server, stop the service.
  2. If the Teradata Notification Service is running on a Linux Server, stop the tdnotification service:
    /etc/init.d/tdnotification stop
  3. Stop all of the Teradata Alerts services on all Teradata Viewpoint servers. Also stop the Teradata Viewpoint services:
    • /etc/init.d/dcs stop
    • /etc/init.d/tmsmonitor stop
    • /etc/init.d/viewpoint stop
    • /etc/init.d/camalert stop
    • /etc/init.d/tdactivemq stop
  4. Restore the last successful backup of the previous version of the Teradata Alerts database.
    The duration of this process varies and is based on the size of the database. If you have a clustered environment, perform the restore against the primary database server.
  5. If the Teradata Notification Service is running on a Windows Server, uninstall the Teradata Notification Service.
  6. If the Teradata Notification Service for Linux is running on a Linux Server, uninstall the tdnotification package.
  7. Uninstall the Teradata Alerts RPMs on all Teradata Viewpoint servers.
  8. Reinstall the previous version of Teradata Alerts RPMs on all Teradata Viewpoint servers.
  9. If the Teradata Notification Service was installed on a Windows Server, install and configure the previous version of the Teradata Notification Service for Windows.
    1. Move the programs from the usrcmd folder of the current version to the usrcmd folder of the previous version.
      The current usrcmd folder is located at:
      installation folder\Teradata\Client\version\Teradata Notification Service\usrcmd
    2. Move the BTEQ scripts from the sql folder of the current version to the sql folder of the previous version.
      The sql folder is located at:
      installation folder\Teradata\Client\version\Teradata Notification Service\sql
    3. Start the previous version of the Teradata Notification Service on the Windows Server.
  10. If the Teradata Notification Service for Linux was installed on a Linux Server, install the previous version of the Teradata Notification Service for Linux.
    1. If tdnotification is already installed, it is now the current package. If it is not installed, install the prior version manually.
    2. Start the previous version of the Teradata Notification Service on the Linux Server:
      /etc/init.d/tdnotification start
  11. Start the previous version of the Teradata Alerts services on all Teradata Viewpoint servers. Also start the Teradata Viewpoint services:
    • /etc/init.d/tdactivemq start
    • /etc/init.d/camalert start
    • /etc/init.d/dcs start
    • /etc/init.d/tmsmonitor start
    • /etc/init.d/viewpoint start