What would you do if you knew? Teradata Viewpoint Installation, Configuration, and Upgrade Guide for Customers Release B K May 2015

Transcription

1 What would you do if you knew? Teradata Viewpoint Installation, Configuration, and Upgrade Guide for Customers Release B K May 2015

2 The product or products described in this book are licensed products of Teradata Corporation or its affiliates. Teradata, Active Data Warehousing, Active Enterprise Intelligence, Applications-Within, Aprimo Marketing Studio, Aster, BYNET, Claraview, DecisionCast, Gridscale, MyCommerce, QueryGrid, SQL-MapReduce, Teradata Decision Experts, "Teradata Labs" logo, Teradata ServiceConnect, Teradata Source Experts, WebAnalyst, and Xkoto are trademarks or registered trademarks of Teradata Corporation or its affiliates in the United States and other countries. Adaptec and SCSISelect are trademarks or registered trademarks of Adaptec, Inc. AMD Opteron and Opteron are trademarks of Advanced Micro Devices, Inc. Apache, Apache Avro, Apache Hadoop, Apache Hive, Hadoop, and the yellow elephant logo are either registered trademarks or trademarks of the Apache Software Foundation in the United States and/or other countries. Apple, Mac, and OS X all are registered trademarks of Apple Inc. Axeda is a registered trademark of Axeda Corporation. Axeda Agents, Axeda Applications, Axeda Policy Manager, Axeda Enterprise, Axeda Access, Axeda Software Management, Axeda Service, Axeda ServiceLink, and Firewall-Friendly are trademarks and Maximum Results and Maximum Support are servicemarks of Axeda Corporation. Data Domain, EMC, PowerPath, SRDF, and Symmetrix are registered trademarks of EMC Corporation. GoldenGate is a trademark of Oracle. Hewlett-Packard and HP are registered trademarks of Hewlett-Packard Company. Hortonworks, the Hortonworks logo and other Hortonworks trademarks are trademarks of Hortonworks Inc. in the United States and other countries. Intel, Pentium, and XEON are registered trademarks of Intel Corporation. IBM, CICS, RACF, Tivoli, and z/os are registered trademarks of International Business Machines Corporation. Linux is a registered trademark of Linus Torvalds. LSI is a registered trademark of LSI Corporation. Microsoft, Active Directory, Windows, Windows NT, and Windows Server are registered trademarks of Microsoft Corporation in the United States and other countries. NetVault is a trademark or registered trademark of Dell Inc. in the United States and/or other countries. Novell and SUSE are registered trademarks of Novell, Inc., in the United States and other countries. Oracle, Java, and Solaris are registered trademarks of Oracle and/or its affiliates. QLogic and SANbox are trademarks or registered trademarks of QLogic Corporation. Quantum and the Quantum logo are trademarks of Quantum Corporation, registered in the U.S.A. and other countries. Red Hat is a trademark of Red Hat, Inc., registered in the U.S. and other countries. Used under license. SAP is the trademark or registered trademark of SAP AG in Germany and in several other countries. SAS and SAS/C are trademarks or registered trademarks of SAS Institute Inc. SPARC is a registered trademark of SPARC International, Inc. Symantec, NetBackup, and VERITAS are trademarks or registered trademarks of Symantec Corporation or its affiliates in the United States and other countries. Unicode is a registered trademark of Unicode, Inc. in the United States and other countries. UNIX is a registered trademark of The Open Group in the United States and other countries. Other product and company names mentioned herein may be the trademarks of their respective owners. The information contained in this document is provided on an "as-is" basis, without warranty of any kind, either express or implied, including the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. Some jurisdictions do not allow the exclusion of implied warranties, so the above exclusion may not apply to you. In no event will Teradata Corporation be liable for any indirect, direct, special, incidental, or consequential damages, including lost profits or lost savings, even if expressly advised of the possibility of such damages. The information contained in this document may contain references or cross-references to features, functions, products, or services that are not announced or available in your country. Such references do not imply that Teradata Corporation intends to announce such features, functions, products, or services in your country. Please consult your local Teradata Corporation representative for those features, functions, products, or services available in your country. Information contained in this document may contain technical inaccuracies or typographical errors. Information may be changed or updated without notice. Teradata Corporation may also make improvements or changes in the products or services described in this information at any time without notice. To maintain the quality of our products and services, we would like your comments on the accuracy, clarity, organization, and value of this document. Please teradata-books@lists.teradata.com Any comments or materials (collectively referred to as "Feedback") sent to Teradata Corporation will be deemed non-confidential. Teradata Corporation will have no obligation of any kind with respect to Feedback and will be free to use, reproduce, disclose, exhibit, display, transform, create derivative works of, and distribute the Feedback and derivative works thereof without limitation on a royalty-free basis. Further, Teradata Corporation will be free to use any ideas, concepts, know-how, or techniques contained in such Feedback for any purpose whatsoever, including developing, manufacturing, or marketing products or services incorporating Feedback. Copyright by Teradata. All Rights Reserved.

3 Table of Contents Preface...7 Purpose... 7 Audience... 7 Revision History... 7 Additional Information...7 Related Links...7 Related Documentation...8 Customer Education... 8 Product Safety Information...8 Chapter 1: Overview...9 Dependencies... 9 Supported Web Browsers...9 Supported Teradata Viewpoint Appliances... 9 Supported Teradata Database Versions... 9 Ports Used by Teradata Viewpoint Teradata Manager Feature Equivalence...10 Teradata Viewpoint Services Starting and Stopping Teradata Viewpoint Services Interaction between Teradata Alerts and Teradata Database...12 Notification Server Requirements...12 Linux Server Requirements...12 Windows Server Requirements...13 Starting and Stopping the Teradata Notification Service (Windows)...13 Starting and Stopping the Teradata Notification Service (Linux)...14 Chapter 2: Upgrading Viewpoint Software About Upgrading Viewpoint Software...15 Upgrading from Teradata Viewpoint xx.xx, xx.xx, or xx.xx Upgrading Teradata Viewpoint or Later...15 Teradata Viewpoint Installation, Configuration, and Upgrade Guide for Customers, Release

4 Table of Contents Creating an Incident...16 Finding the PUT Version Running on the System...16 Determining the Latest PUT Release...16 Downloading New PUT Packages...17 Installing and Upgrading PUT...18 Installing PUT...18 Upgrading PUT Checking for Space on the Node Creating a Target Directory...19 Software Package Downloads...20 Downloading Software Packages...20 Verifying the Previous Database Backup...21 Upgrading a Teradata Viewpoint Server...21 Creating a Teradata User for Data Collection...22 Upgrading a Teradata Viewpoint Cluster Troubleshooting a Failed Upgrade Chapter 3: Installing Notification Services...25 Downloading the Teradata Alerts Notification Software...25 Installing Teradata Notification Service for Windows...25 Preparing for Installation of Notification Service...25 Installing Notification Service Software on a Windows Server...26 Configuring the Teradata Viewpoint Server Location...27 Setting Up the BTEQ Scripts and Run Program Executables...27 Installing Teradata Notification Service for Linux...28 Preparing for Installation of Notification Service for Linux...28 Installing Software on a Linux Server...28 Installing Teradata Notification Service Interactively Service User...29 Configuring the Teradata Viewpoint Server Location...30 Setting Up the BTEQ Scripts and Run Program Executables...30 Uninstalling the Teradata Notification Service...31 Chapter 4: Advanced Configuration Tasks...33 Configuring NTP Time Synchronization Configuring LDAP for Teradata Viewpoint Prerequisites Teradata Viewpoint Installation, Configuration, and Upgrade Guide for Customers, Release 15.10

5 Table of Contents Definitions...34 Before You Begin LDAP Configuration Determining LDAP Configuration Mode...35 Is the Username in DN? Determining the Number of Bind Patterns LDAP Servers About Auto-Provisioning and Role Mapping...38 Adding an LDAP Server LDAP Configuration Options...39 Basic Configuration DN Pattern Bind...40 User Search...40 Key User Information Auto-Provisioning...41 Role Mapping Global Settings Role Mapping Individual Settings...41 Changing a Teradata Viewpoint System Name...41 Resetting the Admin User Password...42 Portlets Enabled Under Special Circumstances Installing Teradata Data Lab Configuring Teradata Data Lab Notifications...43 Configuring Teradata Viewpoint to Monitor a Managed Server...43 About Configuring Stats Manager...44 Before You Begin Configuring Stats Manager Configuring Teradata Database to Collect and Analyze Statistics...45 Collecting Statistics Analyzing Statistics Cleaning Up the TDStats Database...45 Teradata Viewpoint Server Clustering Configurations...46 High Availability Configuration: Two Teradata Viewpoint Servers High Usage Configuration: Three or More Teradata Viewpoint Servers Advanced Configuration: Three or More Teradata Viewpoint Servers With Dedicated Cache Database Server Teradata Alerts Cluster Configurations Failure Scenarios...49 Teradata Viewpoint Failure Scenarios Data Collection Server Failure...49 Cache Database Failure...49 Active Teradata Viewpoint Server Failure Teradata Alerts Failure Scenarios...51 Alert Service Failure (Scenario 1)...51 Messaging Service Failure (Scenario 2) Teradata Viewpoint Installation, Configuration, and Upgrade Guide for Customers, Release

6 Table of Contents DCS Failure (Scenario 3) Cache Database Failure (Scenario 4)...52 Server Failure (Scenario 5) Clustering Considerations...54 LAN or WAN Load Balancing Setting Disk Capacity for the Standby Cache Database...54 Setting Up Notifications of Failures and Promotions...54 Creating a Teradata Viewpoint Cluster...55 Adding Teradata Viewpoint Servers to a Cluster Configuring Automatic Promotions Disabling a Teradata Viewpoint Cluster Promoting the Standby Cache Database to Active Recreating a Standby Cache Database After a Promotion...57 Teradata Notification Service Cluster Configuration Cluster Enabling Cluster Disabling About Replacing a Viewpoint Server Backup for Teradata Viewpoint Databases...59 Backup...59 About Backup Errors...59 Scheduling Viewpoint Backups...59 Backing Up Third-Party Applications Uninstalling a Teradata Data Lab Package Manually Uninstalling Teradata Manager About Restoring a Teradata Viewpoint Database...61 Restoring a Teradata Viewpoint Database...62 Migrating Teradata Viewpoint to a New Server Backing Down to a Previous Teradata Viewpoint Version...63 Backing Down to a Previous Teradata Alerts Version...63 Manually Uninstalling Teradata Alerts Packages Teradata Viewpoint Installation, Configuration, and Upgrade Guide for Customers, Release 15.10

7 Preface Purpose This guide provides customer information and procedures for configuring and maintaining the Teradata Viewpoint server, as well as upgrading from and backing down to a previous Teradata Viewpoint software version. Audience This guide is intended for use by: System administrators Database administrators and relational database developers Customers Teradata Customer Support Revision History Date Release Description May Corrected "Creating a Teradata Viewpoint Cluster" topic April Added Data Lab installation instructions March Initial release Additional Information Related Links URL Description Use Teradata At Your Service to access Orange Books, technical alerts, and knowledge repositories, view and join forums, and download software packages. Teradata Viewpoint Installation, Configuration, and Upgrade Guide for Customers, Release

8 Preface Product Safety Information URL Description External site for product, service, resource, support, and other customer information. Related Documentation Documents are located at Title Parallel Upgrade Tool (PUT) Reference Publication ID B Describes how to install application software using PUT. Teradata Viewpoint User Guide B Describes the Teradata Viewpoint portal, portlets, and system administration features. Electronic Software Distribution Guide BCD Customer Education Teradata Customer Education designs, develops and delivers education that builds adept skills and capabilities for our data warehousing technology customers, enabling them to maximize their Teradata investment. Teradata offers a variety of delivery formats to suit your needs. The combination of web technology through the Teradata Education Network, along with hands-on classroom training, provides each user level with a wide range of opportunities to gain knowledge about our data warehousing tools. Our flexible education options build upon and complement one another to give you a cost effective, robust education offering. On this website, you can view and enroll in any Teradata Customer Education training offering. As the premier on-line learning environment for Teradata users, Teradata Education Network (TEN) is a membership-based learning community that allows you to harness the power of the internet and expand your knowledge of Teradata data warehousing tools at your own pace... anytime, anywhere. If you do not have a membership that includes web-based training courses, you can purchase courses at or Teradata University. Product Safety Information This document may contain information addressing product safety practices related to data or property damage, identified by the word Notice. A notice indicates a situation which, if not avoided, could result in damage to property, such as equipment or data, but not related to personal injury. Example Notice: Improper use of the Reconfiguration utility can result in data loss. 8 Teradata Viewpoint Installation, Configuration, and Upgrade Guide for Customers, Release 15.10

9 CHAPTER 1 Overview Dependencies Supported Web Browsers Browser Version Mozilla Firefox 35 Internet Explorer 10 or 11 Google Chrome 40 Safari 8 Recommended Hardware At least 1.8 GHz Pentium M, 3 GHz Pentium 4, or equivalent CPU At least 1 GB of RAM Monitor or display supporting at least 1024x768 resolution Supported Teradata Viewpoint Appliances Teradata Viewpoint Appliance Model Number Description Storage Capacity 415 Dell 2950 with 20 GB total RAM upgrade 4 x 300 GB drives (RAID 5) 617 Dell R710 4 x 450 GB drives (RAID 5) 819 Dell R720 6 x 900 GB drives (RAID 10) Supported Teradata Database Versions Teradata Viewpoint Installation, Configuration, and Upgrade Guide for Customers, Release

10 Chapter 1 Overview Teradata Manager Feature Equivalence Ports Used by Teradata Viewpoint Following is a list of ports used by Teradata Viewpoint and Alerts. Additional ports are required for Teradata Viewpoint Clustering. Incoming 22 (SSH) 80 (HTTP) 443 (HTTPS) 5432 (Cache Database) 8888 (Optional for monitoring Teradata Viewpoint server - tmsmonitor) (Teradata Alerting) Outgoing 22 (SSH) For clustering and Elastic Performance uploads 80 (HTTP) For monitoring Teradata Aster systems 389 Optional for LDAP authentication 636 Optional for LDAPS authentication 1025 (JDBC) 5432 (Cache Database) When clustering is enabled 8081(HTTP) for monitoring Teradata Hadoop systems 8888 Optional for monitoring Teradata Managed Servers - tmsmonitor Alerts 25 SMTP (default)* 465 SMPT over SSL (default)* 162 SNMP Trap *You can change the outgoing Teradata Alerts SMTP ports by selecting Delivery Settings > in the Alert Setup portlet. Teradata Manager Feature Equivalence Teradata Viewpoint supports all features of Teradata Manager except the following. Teradata Manager Feature Scheduling Priority Scheduler Administrator Option Most operating systems provide scheduling features. In Microsoft Windows, use the Microsoft Task Scheduler. You can use the Workload Designer portlet instead. Teradata Viewpoint Services Teradata Viewpoint includes the following separate services. Service camalert Description Teradata Alert Service that processes events and alerts 10 Teradata Viewpoint Installation, Configuration, and Upgrade Guide for Customers, Release 15.10

11 Chapter 1 Overview Starting and Stopping Teradata Viewpoint Services Service dcs postgresql tdnotification tdactivemq tmsmonitor viewpoint Description Data Collection Service that monitors and collects data from Teradata systems Internal database used to store all Viewpoint configuration and collected data Teradata Notification Service used to run BTEQ and Run Program alert actions. Messaging service that allows message exchanges between the Teradata Alerts components Teradata Managed Server Monitor that monitors performance of the Teradata Viewpoint server Teradata Viewpoint portal that provides web browser access Starting and Stopping Teradata Viewpoint Services The /etc/init.d directory on the Teradata Viewpoint server contains scripts that allow you to manage Teradata Viewpoint services using the following commands. Command start stop restart status Description Starts the service. If the service is already running, a new instance is not started. Stops the service. The script completes successfully even when the service is not running. Stops and starts the service. Checks if the service is running. The Teradata Viewpoint services that can use these commands are: camalert dcs postgresql tdactivemq tmsmonitor viewpoint The following are examples of using the commands. Action Starting the Teradata Alert service Stopping the Teradata Viewpoint service Restarting the PostgreSQL service Example /etc/init.d/camalert start /etc/init.d/viewpoint stop /etc/init.d/postgresql restart Teradata Viewpoint Installation, Configuration, and Upgrade Guide for Customers, Release

12 Chapter 1 Overview Interaction between Teradata Alerts and Teradata Database Action Example Checking the Teradata Managed Server monitor status /etc/init.d/tmsmonitor status The vp-control.sh script, located in the same directory, allows you to run the start, stop, restart and status commands. When running start, stop, or restart, the script performs the specified action on the tdactivemq, camalert, tmsmonitor, dcs, and viewpoint services. When running status, you receive the status of all commands for all the services including postgresql. /opt/teradata/viewpoint/bin/vp-control.sh command Where command is the command you want to perform using the script. This script supports the same command arguments as the individual init.d scripts. Interaction between Teradata Alerts and Teradata Database Teradata Alerts has limited interaction with Teradata Database. The three components that interact with the Teradata Database are: BTEQ alert actions SQL alert actions Alerts processed by the Teradata Viewpoint alert request data collector Teradata Notification Service for Windows and Teradata Notification Service for Linux can execute BTEQ scripts. The version of BTEQ that is installed on the Windows Server or Linux Server must be compatible with the version of the Teradata Database that the BTEQ scripts are executing against. Teradata Alerts running on the Viewpoint Server executes SQL alert actions using the Teradata JDBC driver. The queries entered by the administrator must be compatible with the Teradata Database where the queries will be executed. Teradata Viewpoint alert request data collector monitors the dbcmngr.alertrequest and dbcmngr.monitorrequest tables for alert requests. Teradata Alerts supports the same versions of the Teradata Database that Viewpoint monitoring supports. Notification Server Requirements Linux Server Requirements Teradata Notification Service for Linux is needed to run the BTEQ scripts and executable programs on a Linux server and must be installed on a customer provided Linux server. If the BTEQ and Run Program alert actions are not needed on Linux, Teradata Notification Service for Linux is not required. 12 Teradata Viewpoint Installation, Configuration, and Upgrade Guide for Customers, Release 15.10

13 Chapter 1 Overview Starting and Stopping the Teradata Notification Service (Windows) Software Dependencies Other Requirements One of the following SuSE Linux Enterprise operating systems: SuSE Linux Enterprise 10, Service Pack 3 or later version SuSE Linux Enterprise 11 The following Java SE Runtime Environment: Java SE Runtime Environment 7 or greater BTEQ and related dependencies: TTU versions are dependent on the targeted Teradata Database and should be installed using the TTU Client Main Install so all required dependencies are installed. The Linux system clock must be synchronized with the clock on the Viewpoint server. Windows Server Requirements Teradata Notification Service for Windows is needed to run the BTEQ scripts and executable programs on a Windows server, and must be installed on the Windows Server. If the BTEQ and Run Program alert actions are not needed on Windows, Teradata Notification Service for Windows is not required. Software Dependencies Other Requirements One of the following Microsoft Windows operating systems: Windows XP Windows Server 2003 Windows Vista Windows Server 2008 Windows Server 2008 R2 Windows 7 The following Java SE Runtime Environment: 32-bit Java SE Runtime Environment 7 or greater BTEQ and related dependencies: TTU versions are dependent on the targeted Teradata Database and should be installed using the TTU Client Main Install so all required dependencies are installed. The Windows system clock must be synchronized with the clock on the Viewpoint server. Starting and Stopping the Teradata Notification Service (Windows) The Teradata Notification Service is installed as a Windows Service named Teradata Notification Service. The default installation procedure configures the service to automatically start when the system reboots. Teradata Viewpoint Installation, Configuration, and Upgrade Guide for Customers, Release

14 Chapter 1 Overview Starting and Stopping the Teradata Notification Service (Linux) You can start, stop, pause, resume, or restart a service using the Services Administration tool in Windows, which can be opened from a command prompt window by typing services.msc. Starting and Stopping the Teradata Notification Service (Linux) The Teradata Notification Service is installed as a Linux service named tdnotification. The default installation procedure configures the service to automatically start when the system reboots. The Teradata Notification Service for Linux has an init script called tdnotification, located in the /etc/init.d directory. The init script supports the following commands. Command Description Example start Starts the service. If the service is already running, a new instance is not started. To start the tdnotification service, type: /etc/init.d/tdnotification start stop Stops the service. To stop the tdnotification service, type: /etc/init.d/tdnotification stop restart Stops and restarts the service. To restart the tdnotification service, type: /etc/init.d/tdnotification restart status Checks if the service is currently running. To check if the tdnotification service is running, type: /etc/init.d/tdnotification status 14 Teradata Viewpoint Installation, Configuration, and Upgrade Guide for Customers, Release 15.10

15 CHAPTER 2 Upgrading Viewpoint Software About Upgrading Viewpoint Software Depending on your currently installed release, you may have to perform incremental upgrades to upgrade to the latest release. Installed Release xx.xx xx.xx, or xx.xx Action Upgrade from Teradata Viewpoint xx.xx, xx.xx, or xx.xx or later Upgrade from Teradata Viewpoint or later Upgrading from Teradata Viewpoint xx.xx, xx.xx, or xx.xx When upgrading from a release earlier than , perform the following upgrades concurrently in the same single PUT session: Teradata Alerts to release PostgreSQL database to PostgreSQL Perform an incremental backup to reduce the upgrade time. Determine the approximate duration of the Teradata Viewpoint upgrade: a. Determine the duration of the last backup by subtracting the finish time from the configured start time. b. Multiply this value by 2. 2 Verify the previous database backup. 3 Upgrade the software based on your configuration: Teradata Viewpoint Server Teradata Viewpoint Cluster Upgrading Teradata Viewpoint or Later 1 Verify the previous database backup. 2 Upgrade the software based on your configuration: Teradata Viewpoint Server Teradata Viewpoint Installation, Configuration, and Upgrade Guide for Customers, Release

16 Chapter 2 Upgrading Viewpoint Software Creating an Incident Teradata Viewpoint Cluster Creating an Incident You must obtain an Incident number from Teradata at Your Service prior to performing any software upgrades. 1 On your Windows PC, open a web browser and go to Teradata At Your Service at tays.teradata.com and log in. 2 Under the Product banner click Incident. 3 Click the Create tab. 4 Make the following selections as appropriate: Note: Click the green arrows to move forward or back in the selection screens. Option Site Priority Product Area Description The site where the activity will be performed. The Priority of the issue. The area of the system where the issue is located or where work will be performed. Problem Type A list of Problem Types. Synopsis Description 5 Click Submit the Incident. A short Synopsis of the activity being performed. A short description of the activity being performed. 6 Click OK to confirm the submission of the incident. The incident is added to the list of Incidents. The Status shows Pending (a blue circle) until Customer Services accepts the incident, at which time the Status becomes Active (a green circle). Finding the PUT Version Running on the System 1 From your PC, open a communication window to any server in the system. 2 Issue the following command on all nodes: rpm -qa TDput 3 Record the latest PUT version number. Determining the Latest PUT Release PUT is updated periodically. You must always use the latest version of PUT. 16 Teradata Viewpoint Installation, Configuration, and Upgrade Guide for Customers, Release 15.10

17 Chapter 2 Upgrading Viewpoint Software Downloading New PUT Packages 1 Check for the latest version of PUT in the Certification List section of Teradata At Your Service at Downloading New PUT Packages This task needs to be performed only if your version of PUT needs to be updated. 1 On your Windows PC, open a web browser and go to Teradata At Your Service at tays.teradata.com and log in. 2 Click Software Downloads > Certified Configs. 3 On the Certified Configuration Help screen, click Parallel Upgrade Tool (PUT) under Software Patches in the left pane. 4 In the Specify the type for PUT Packages section, select the following: Field Platform Current Selection The operating system Current 5 Click Submit. 6 On the Teradata PUT screen, select PUTSRC, PUTTools, and TDput for download and write the version number in the following space: TDput PUTSRC PUTTools_(Version not required; download is) 7 Complete the download request with the following choices: Field Download Type Download Readme Files? User Name Site ID Change Control Number Selection/Entry Windows No The name on your account The address on your account The site ID for your site The Change Control Number previously obtained Note: The Change Control Number entered must be valid for your site ID. 8 Click Submit. 9 Click Download. 10 Save the downloaded files and transfer them to the PUT Master Node: Teradata Viewpoint Installation, Configuration, and Upgrade Guide for Customers, Release

18 Chapter 2 Upgrading Viewpoint Software Installing and Upgrading PUT a b c d When asked to click the button to download, click Download. In the File Download dialog box, click Save. In the Save As dialog box, go to the target directory for the downloaded packages and click Save. The package files are compressed into a single Windows.zip file. Extract or unzip the downloaded.zip file. Notice: The unzipped files are Linux files in the.gz or.rpm format. Never uncompress a Linux.gz file on a Windows computer. Windows might corrupt the file. e Use the Secure File Transfer Protocol (SFTP) utility to transfer the.gz or.rpm files to the Master Node download directory and then uncompress the.rpm files (the.gz files do not need to be uncompressed). Note: Make sure you transfer the files using the binary mode, not the ASCII mode. The.zip files are not needed on the Master Node and can be deleted from the Windows system after the upgrade. Installing and Upgrading PUT If PUT is not installed on your system, use the instructions for Installing PUT. If you are upgrading an existing version of PUT, use the instructions for Upgrading PUT. Installing PUT 1 To install PUT, follow the instructions in the Parallel Upgrade Tool (PUT) Reference. Note: Make sure the version of PUT is the same on all nodes, including TMS servers. Always use the latest version of PUT. Upgrading PUT This procedure copies PUT from the Master Node to all other nodes that need a new version of PUT installed. Notice: Do not choose any PUT operation other than the operation specified. Choosing any of the PUT operations that are not specified in your task could result in severe damage to user data. 1 Start PUT on the Master Node (if it is not already started). 2 In the main screen, select Install/Upgrade PUT and click Next. 3 In the Network Subnet Selection screen, select byn1 and click Next. 4 In the Select Nodes screen: 18 Teradata Viewpoint Installation, Configuration, and Upgrade Guide for Customers, Release 15.10

19 Chapter 2 Upgrading Viewpoint Software Checking for Space on the Node a b Verify that all the nodes in the system are listed. If any nodes are missing, you will not be able to continue with this upgrade and should open an incident. Select and move the desired nodes from the Available column to the Selected column using the >> button. c Click Next. 5 In the Choose Software Location screen, enter the source directory for the downloaded PUT package and click Next. PUT proceeds through the Gather PUT Package Info, Spool & Distribute PUT Package, and Upgrade PUT Package screens which may take several minutes. No user interaction is required here. When PUT reaches the Overall Package Install Results screen, the package name and installation results are displayed. 6 Check the results of the installation and report any failures. 7 Click Next. 8 In the Finished! screen, click Finish. PUT will complete the operation and return you to the main screen. Checking for Space on the Node 1 Prior to downloading any software packages, check the nodes in your system to make sure you have enough space: df -k Example output: Filesystem 1K-blocks Used Available Use% Mounted on /dev/sda % / udev % /dev /dev/sda % /var /dev/sda % /var/opt/teradata In this example, the / drive has no available space. Contact your system administrator to remove old files and free up space for the new packages. Teradata recommends that you double the total the space required by the packages you are downloading. Creating a Target Directory 1 Set up a target directory on the server to hold the downloaded packages with the following command: mkdir -p /var/opt/teradata/ccnumber/pkgs where the ccnumber is the Teradata Change Control Number, as shown in the following example: Teradata Viewpoint Installation, Configuration, and Upgrade Guide for Customers, Release

20 Chapter 2 Upgrading Viewpoint Software Software Package Downloads /var/opt/teradata/vecd2rq9b/pkgs Software Package Downloads Software packages must be downloaded from Teradata At Your Service at tays.teradata.com. Downloading Software Packages 1 Navigate to the software repository in one of the following ways: Option Customer access: Teradata internal access: /TSFS/ Description a. Click Software Downloads. b. Click Certified Configs. a. Click Teradata. b. Click Combined Certification List. 2 In the Certification List section of the left pane, click Current List. 3 In the Certification List area, make the appropriate selections as follows: Field Node Type Target OSs Application Version Teradata Releases BusType Would you like to compare lists? Selection/Entry The application package to be installed. The operating system on the node. The release number for the application. N/A SM3G Select Yes or No If two additional fields appear, make the appropriate selections as follows: Field External Storage Type TESA Type Selection/Entry The type of external storage if any exists. The type of Teradata Enterprise Service Architecture (TESA) that applies to the Node Type selected. The TESA type identifies CMIC and node components for Server Management. 4 Click Submit. 5 Select all packages. 6 Complete the download request with the following choices: 20 Teradata Viewpoint Installation, Configuration, and Upgrade Guide for Customers, Release 15.10

21 Chapter 2 Upgrading Viewpoint Software Verifying the Previous Database Backup Field Download Type Download Readme Files? User Name Site ID Change Control Number Selection/Entry Windows No The name on your account The address on your account The site ID for your site The Change Control Number previously obtained Note: The Change Control Number entered must be valid for your site ID. 7 Click Submit. 8 When the.zip package is ready to download, click the Download button. Optionally, you can save the patch for future use by selecting the Save the Patch for future use box. 9 In the File Download dialog, click Save, navigate to the target directory, and click Save again. 10 Extract or unzip the file in the target directory. Verifying the Previous Database Backup If providing a back down procedure is a concern, verify that a current database backup has completed successfully. Backups are automatically performed during upgrades from versions xx.xx and earlier to xx.xx or later as part of the PostgreSQL 9.1 upgrade procedure. Using VM&F for these upgrades is recommended, because booting to an alternate boot environment is the only supported back down procedure. 1 From the Teradata Viewpoint portal page, click. 2 Do one of the following to access the Backup portlet: Select Backup from the Viewpoint Administration menu. Select the Backup portlet on the page. 3 Review the details of the last backup, including the time it was completed and whether or not it was successful. Upgrading a Teradata Viewpoint Server Note: If a backdown procedure is required, see Verify the Previous Database Backup. 1 Start PUT. Teradata Viewpoint Installation, Configuration, and Upgrade Guide for Customers, Release

22 Chapter 2 Upgrading Viewpoint Software Creating a Teradata User for Data Collection 2 In the main screen, select Install/Upgrade Software and click Next. 3 In the System Information Warning screen, click Next. 4 If the System Check Found Problems screen appears, verify that there are no issues that need attention (or correct any issues that need correcting), and click Ignore. 5 Accept the default selection in the Select Spool Area for Linux Nodes screen and click Next. 6 In the Enter Source for New Packages screen, enter or select the path /var/opt/ teradata/packages/viewpoint/linux and click Next. 7 In the Media Source Confirmation screen, accept the default selections and click Next. 8 In the Group Nodes screen verify that the node displayed in the right panel has the following settings and click Next: System - System0 Group - Group0 Node Type - VP If these settings need to be changed, do the following: a. Select the item listed in the right panel. b. Click Modify Group. c. Make the necessary changes. d. Click Submit Changes e. Click Next. 9 Accept the default options for all subsequent steps. 10 In Select Teradata Startup Option, select Automatically Start Teradata after a system reboot and click Next to finish the installation. Creating a Teradata User for Data Collection To monitor a Teradata Database system, Teradata Viewpoint requires a Teradata Database system user account with specific permissions. You can use SQL commands to create a user account and grant permissions, or the user can be an existing user with specific permission. The Teradata Viewpoint user account must have sufficient spool space to allow Teradata Viewpoint to issue monitoring queries. Also, permanent (perm) space is required by the Lock Info collector that is used by the Lock Viewer portlet. 1 Determine the amount of perm space and spool space to allocate to the Teradata user. These values vary based on several factors, including the size of the Teradata Database system, the level of activity on the Teradata Database system, and the amount of data retained in the data dictionary tables queried by Teradata Viewpoint. For Teradata systems of 50 nodes or fewer, the suggested allocations are 2 GB of perm space and 500 GB of spool space. For Teradata Database systems larger than 50 nodes, additional perm and spool space might be required. 22 Teradata Viewpoint Installation, Configuration, and Upgrade Guide for Customers, Release 15.10

23 Chapter 2 Upgrading Viewpoint Software Upgrading a Teradata Viewpoint Cluster 2 Type the following command, where perm space and spool space are the perm space and spool space to allocate to the user: create user username as perm=perm space, spool=spool space password=user password; 3 If the console user does not exist on the target Teradata Database system, run the following command to create the user: create user console as perm=50000, spool=50000, account='$h-remoteconsole-user', password=console, fallback; Upgrading a Teradata Viewpoint Cluster 1 Identify the primary cache database server by opening the following file from any server: /etc/opt/teradata/viewpoint/distributed.cluster.properties The IP address or server name of the primary cache database is listed after the active.database.host key. 2 Stop the Teradata Viewpoint services on all of the servers except the primary server: /opt/teradata/viewpoint/bin/vp-control.sh stop If there are more than two Teradata Viewpoint servers in the cluster, the order in which you stop the servers does not matter. 3 Upgrade the primary server. 4 Upgrade the remaining servers in the cluster. 5 If you upgraded from a version earlier than , use the cluster setup tool from the primary server to re-establish the cluster by following the instructions in Creating a Teradata Viewpoint Cluster. Troubleshooting a Failed Upgrade During a Teradata Viewpoint upgrade, modifications might be made to PostgreSQL database tables and data. The modifications are necessary to ensure that the database is synchronized with the version of the software you are upgrading. 1 When installing Teradata Viewpoint, read the reports from TDPut to ensure that the upgrade was successful. 2 If there are errors, contact your Customer Support Representative. 3 After you resolve the problem, run the TDPut operation again. This ensures that the software and PostgreSQL database are successfully upgraded. Teradata Viewpoint Installation, Configuration, and Upgrade Guide for Customers, Release

24 Chapter 2 Upgrading Viewpoint Software Troubleshooting a Failed Upgrade 24 Teradata Viewpoint Installation, Configuration, and Upgrade Guide for Customers, Release 15.10

25 CHAPTER 3 Installing Notification Services Downloading the Teradata Alerts Notification Software 1 Access the Teradata Software Server: 2 Select Certified Configs. 3 On the menu on the left, select Software Patches > Teradata Applications. 4 At Sub Category, select Common Alerting Mechanism. 5 At Release, select Click Submit. 7 Select the Notification Service package for Windows or Linux as needed. 8 At please enter the following information to download, enter your user name, address, site ID, and the change control number. 9 Click Submit. 10 Click Download. 11 Extract the files from the downloaded archive. 12 Copy the files to the servers where the installation or upgrade is to be performed. Installing Teradata Notification Service for Windows To use BTEQ and Run Program alert actions on Windows, first install the Teradata Notification Service. Install the service on a Windows server and configure the software with information specific to your Teradata Viewpoint server. Preparing for Installation of Notification Service Before installing Teradata Notification Service, ensure the following: Teradata Viewpoint server is set up and running. Teradata Viewpoint Installation, Configuration, and Upgrade Guide for Customers, Release

26 Chapter 3 Installing Notification Services Installing Teradata Notification Service for Windows Alert Services are running on the Viewpoint Server. You have the hostname or IP address of the Teradata Viewpoint server. You have installed a 32-bit Java Runtime Environment 7 or greater. The JAVA_HOME environment variable is defined at the System (not at the User) level. This is important because the Teradata Notification Service runs as a service. The process varies depending on the Windows operating system. You must log on as an administrator to change System-level environment variables. 1 Depending on your version of the Windows operating system, do the following: Option Windows operating systems prior to Windows 7 Windows 7 operating system Description a. From Control Panel, double-click the System icon to view and change system settings. b. Select the Advanced tab. a. From Control Panel, select System and Security. b. Select System. c. Select Advanced system settings. 2 Click Environment Variables. 3 Click New, located under System variables, to set the JAVA_HOME environment variable. Installing Notification Service Software on a Windows Server The following steps describe how to install or upgrade the Teradata Notification Service on a Windows Server. Note that xx represents the version of the software you are installing or upgrading. 1 Download the software from the Teradata Software Server, as explained in Downloading the Teradata Alerts Notification Software. 2 Copy the zip file teradatacam Windows_i xx.zip to the server where the installation or upgrade will be performed. 3 Navigate to the directory and folder containing the zip file. 4 Extract the zip file. This creates a folder called teradatacam Windows_i xx in the current directory. 5 Navigate to the teradatacam Windows_i xx\DISK1 folder. 6 Click setup.exe. 7 Select the setup language, and click OK. 8 Follow the Install Shield wizard instructions and do the following: a Accept the license agreement. 26 Teradata Viewpoint Installation, Configuration, and Upgrade Guide for Customers, Release 15.10

27 Chapter 3 Installing Notification Services Installing Teradata Notification Service for Windows b c d e f [Optional] Change the destination folder. Specify the system name of the Teradata Viewpoint server. This can be the hostname defined by DNS or an IP address. Click Install. Select Start the Teradata Notification Service now. Click Finish. The software is installed at drive:\program Files (x86)\teradata\client \15.10\Teradata Notification Service Configuring the Teradata Viewpoint Server Location The previous installation procedure requested that you enter the name of the Teradata Viewpoint server. If you did not complete this step, manually configure the Teradata Notification Service to include the location of the Viewpoint server where Teradata Alerts is installed. 1 Create the following folder in the installation partition: drive:\etc\opt\teradata\cam 2 Change the directory to the installation folder to: drive:\program Files (x86)\teradata\client\15.10\teradata Notification Service 3 Copy config\cam.properties.template to drive:\etc\opt\teradata\cam\cam.properties 4 Edit cam.properties and locate the entry for cam.activemq.host: #cam.activemq.host=localhost 5 Remove the comment sign and assign cam.activemq.host to the Viewpoint server where you installed the Teradata Alerts packages: cam.activemq.host=servername 6 Save and close the file. 7 Restart the Teradata Notification Service. Setting Up the BTEQ Scripts and Run Program Executables The Teradata Notification Service executes the BTEQ and Run Program alert actions. The BTEQ scripts and program executables must be located in the specified folders. The directories where you placed the BTEQ scripts and programs are scanned periodically by the Teradata Notification Service while the service is running. If changes are detected to the directories, the updated directory contents are relayed to the alert service, which updates the Teradata Alerts repository on the Viewpoint server. The alert service must be running on the Viewpoint server in order for updates to be visible on the Viewpoint server. Teradata Viewpoint Installation, Configuration, and Upgrade Guide for Customers, Release

28 Chapter 3 Installing Notification Services Installing Teradata Notification Service for Linux 1 Place the BTEQ scripts in the following folder relative to the installation location: InstallFolder\Teradata\Client\15.10\Teradata Notification Service \sql 2 Place the programs you want to run in the following folder relative to the installation location: InstallFolder\Teradata\Client\15.10\Teradata Notification Service \usrcmd Installing Teradata Notification Service for Linux Preparing for Installation of Notification Service for Linux Before installing Teradata Notification Service, ensure the following: Teradata Viewpoint server is set up and running. Alert Services are running on the Viewpoint Server. You have the hostname or IP address of the Teradata Viewpoint server. You have installed a 64-bit Java Runtime Environment 7 or greater. The JAVA_HOME environment variable is defined in the default profile so that once the software is installed, the service is able to locate the Java Runtime Environment. Perform the steps below the change this system setting. 1 Log in as root. 2 Edit /etc/profile.local by adding a line to define JAVA_HOME where you have installed the JRE. For example, if you have installed the Java Runtime Environment in /home/jre7 type: export JAVA_HOME=/home/jre7 3 Source the updated file to pick up the JAVA_HOME definition.. /etc/profile.local Installing Software on a Linux Server Teradata Notification service for Linux can be installed using PUT. These instructions assume that the reader is familiar with the PUT installation process, and that the TDPut software is installed and available on the Linux server. 1 Download the software from the Teradata Software Server, as explained in Downloading the Teradata Alerts Notification Software. 2 Launch TDPut on the Linux server and install the tdnotification1500 package onto the server. 3 After the installation, manually configure the software with the location of the Viewpoint server. 28 Teradata Viewpoint Installation, Configuration, and Upgrade Guide for Customers, Release 15.10

29 Installing Teradata Notification Service Interactively Use these steps to perform an interactive installation or upgrade of Teradata Notification Service on a Linux server. This procedure is only used when PUT is not available. Note that xx represents the version of the software you are installing or upgrading. 1 Download the software from the Teradata Software Server: 2 Copy the rpm file tdnotification1510 SLES10-11_x xx-1.rpm to the server where the installation or upgrade is to be performed. 3 Log on to your Linux server as the root user. 4 Change to the directory containing the rpm file. 5 Verify that JAVA_HOME is defined: echo $JAVA_HOME 6 Set the CAM_INTERACTIVE_INSTALL environment variable to indicate the installation is interactive: export CAM_INTERACTIVE_INSTALL=1 7 Install the rpm: rpm -Uvh tdnotification1510 SLES10-11_x xx-1.rpm. 8 When prompted, enter the name of the Viewpoint server. 9 When prompted, enter the name of the service user, or accept the default of camuser. Service User The service runs with the user id of the service user account. See Service User for more information. The software is installed in the following location: /opt/teradata/client/15.10/cam/tdnotification A symbolic link is created to the installation directory: /opt/teradata/client/cam/tdnotification -> /opt/teradata/client/ 15.10/cam/tdnotification If you provided the name of the Viewpoint server, the software is now configured and ready to start: /etc/init.d/tdnotification start Chapter 3 Installing Notification Services Installing Teradata Notification Service for Linux The tdnotification installation process creates a new user which, as of release 14.10, can be custom-defined during installation. If no user is defined, the system creates a default user called camuser, with a default home account of /home/camuser. If the new user account cannot be created with a home account, it is created without one. The camuser account is a non-login account. The tdnotification service runs with the user ID--either custom-defined or camuser-- instead of running as the root user. Teradata Viewpoint Installation, Configuration, and Upgrade Guide for Customers, Release