Aster Database Installation and Upgrade Guide

Transcription

1 Aster Database Installation and Upgrade Guide Release Number 6.10 Product ID: B K December 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 Chapter 1: Introduction to Aster Database Early Planning For an Aster Database Installation Storage Preparation Network Preparation Aster Database Installation Overview Basic Aster Database Concepts Node Types Node States Tools for Configuring Aster Database AMC ncli Chapter 2: Preparing to Install Aster Database Hardware Requirements Supported Platforms and System Requirements Supported Operating Systems for Aster Database Supported Platforms for Drivers and Utilities Supported Web Browsers Removing Existing Data Remove Ghost Security Patch by Restoring Original glibc Package Deleting All Data to Re-Provision a Node Cluster Network Prerequisites Gather Network Settings TCP Ports Used by Aster Database Set Up Passwordless Authentication with SSH Set Up Passwordless Authentication for Root User Chapter 3: Installing Aster Database Prerequisites Supported Operating Systems Hardware and Storage Checklist Aster Database Installation and Upgrade Guide 3

4 Obtaining Installation Files Install Aster Database Preparation Procedure Chapter 4: Performing Post-Installation Steps Run Diagnostic Tests Security Configurations Disable Passwordless Root SSH Reinstall JCE to Support Kerberos Set Root Password on All Nodes in the Cluster Use Your Aster Database Set up Event Alerts Chapter 5: Installing Aster Backup Planning Your Aster Backup Installation Supported Platforms Node and Disk Requirements Storage Requirements and Recommendations Installing Aster Backup Preparing the Backup Cluster Machines Obtaining Installation File Installation Script Preparing to Install Setting Up Passwordless SSH Installation Procedure Other Installation Options Uninstalling Aster Backup Upgrading Aster Backup Chapter 6: Upgrading the Aster Database on an Aster Appliance Early Planning for Upgrading the Aster Database on an Aster Appliance Data/System Privilege/Authentication Preparation Data Redistribution Preparation Aster Database Installation and Upgrade Guide

5 Component Upgrade Matrix Upgrade Paths Supported Direct Upgrades Supported Indirect Upgrades Obtaining Installation Files Pre-Upgrade Procedures Remove Ghost Security Patch by Restoring Original glibc Package Check for These Blocker Conditions Check Cluster and OS Settings Back Up Data and Files Record Database State for Post-Upgrade Validation Save Custom Settings Quiesce the Aster Database Cluster Clear Prepared Transactions and Initiate Replication Run the ncli Pre-Upgrade Commands Upgrade Procedure Preparation Procedure Post-Upgrade Procedures Restore Pre-Upgrade Settings Recovering Custom SQL-MR Functions Restart Aster Database Activate Aster Database Test your Cluster Redistribute Preexisting Data on the Cluster Disable Passwordless Root SSH Add SQL-H Configurations Upgrade Backup Cluster and Aster Clients Upgrade the Aster Backup Cluster Upgrade ACT Upgrade ODBC and JDBC Drivers Upgrade Aster Loader Tool Re-Create TD Wallet Symbolic Link Upgrade Complete! Common Procedures View Row Counts for Each Table Block User Queries Re-enable User Queries Reinstall JCE to Support Kerberos Configure the Browser to Trust the AMC Certificate Configure Firefox to Trust the AMC Certificate Configure Internet Explorer to Trust the AMC Certificate Aster Database Installation and Upgrade Guide 5

6 Chapter 7: Upgrading the Aster Database on Commodity Hardware Early Planning for Upgrading the Aster Database on Commodity Hardware Data/System Privilege/Authentication Preparation Data Redistribution Preparation Component Upgrade Matrix Upgrade Paths Supported Direct Upgrades Supported Indirect Upgrades Download Required Software Pre-Upgrade Procedures Remove Ghost Security Patch by Restoring Original glibc Package Check for These Blocker Conditions Check Cluster and OS Settings Back Up Data and Files Record Database State for Post-Upgrade Validation Save Custom Settings Quiesce the Aster Database Cluster Clear Prepared Transactions and Initiate Replication Run the ncli Pre-Upgrade Commands Restart and Activate the Cluster Upgrade Procedure Preparation Procedure Post-Upgrade Procedures Restore Pre-Upgrade Settings Recovering Custom SQL-MR Functions Restart Aster Database Activate Aster Database Fix Each Access Control List (ACL) Test your Cluster Redistribute Preexisting Data on the Cluster Disable Passwordless Root SSH Add SQL-H Configurations Upgrade Backup Cluster and Aster Clients Upgrade the Aster Backup Cluster Upgrade ACT Upgrade ODBC and JDBC Drivers Upgrade Aster Loader Tool Re-Create TD Wallet Symbolic Link Aster Database Installation and Upgrade Guide

7 Upgrade Complete! Common Procedures View Row Counts for Each Table Install Kernel Patches on Red Hat Block User Queries Re-enable User Queries Reinstall JCE to Support Kerberos Configure the Browser to Trust the AMC Certificate Configure Firefox to Trust the AMC Certificate Configure Internet Explorer to Trust the AMC Certificate Chapter 8: Troubleshooting PUT Troubleshooting Reference Topics Installation and Expansion Issues Problems with Symbolic Links and Filesystem Setup Nodes stay as New or Preparing in SUSE install on HP ProLiant DL380 G Add node attempt stalls or fails Add node fails due to time clock mismatch Add node fails with user data directories are present message Node Comes Up as Failed After Upgrade, First COMMIT Takes a Long Time If steadystatechecks Continues to Detect Pending DROP DATABASE Operations Install Python Disable the YUM Repositories for Aster Database Components Unable to Connect to the Teradata System Hardware and Networking Problems on Workers Worker comes up as Failed or is missing in AMC Address Hardware Problems on Workers Backup Install Problems Operating System Not in /etc/issue Index Aster Database Installation and Upgrade Guide 7

8 8 Aster Database Installation and Upgrade Guide

9 CHAPTER 1 Introduction to Aster Database This section provides early planning information and introduces basic concepts related to installing Aster Database: Early Planning For an Aster Database Installation Aster Database Installation Overview Basic Aster Database Concepts Tools for Configuring Aster Database Early Planning For an Aster Database Installation Storage Preparation This section provides information on these topics, which should be considered as part of the initial planning and setup of a cluster for an Aster Database installation: Storage Preparation Network Preparation Aster Database software assumes that each node has directly attached storage devices. For ease of management and optimal I/O performance, the Aster Database software requires that all hard disks in a given node be bound together into one or more logical volumes using hardware RAID. Specifics on how to do this will differ based on the hardware RAID controllers and the BIOS of each of your nodes. Please refer to your hardware vendor s instructions on how to create a single logical volume of all the hard disks present on your nodes. Before installing Aster Database, read all sections that follow, unless the text directs otherwise. Recommended RAID Settings for SUSE For queen, worker and loader nodes, if you are using a physical machine, configure the RAID options to specify two RAID5 disks. Aster Database Installation and Upgrade Guide 9

10 Introduction to Aster Database Early Planning For an Aster Database Installation Table 1-1: Disk Partitioning Recommended RAID Settings for Red Hat and SLES RAID Levels: Summary Teradata Aster recommends the following RAID settings: Queen: Use RAID 5 or RAID 10. The queen is the central coordinating node for the Aster Database. The I/O activity on a queen node is typically of medium intensity. Disk usage on the queen is, typically, relatively low since the queen stores mainly metadata related to Aster Database. RAID 5 provides tolerance of disk failures in exchange for a small storage and I/O bandwidth penalty. RAID 10 provides faster rebuilds, but less capacity. Workers: Use RAID 5 if your cluster runs on Red Hat or SLES. Do not use RAID 10 for workers. Loaders: Use RAID 5. Loader nodes should use the same RAID settings as the worker nodes for consistency and ease of manageability. If loader nodes are configured identically to worker nodes at the hardware level, it is relatively simple to convert a loader node into a worker node, if you have an urgent need for a new worker node. Battery-Backed RAID Cache Teradata Aster strongly recommends using a RAID controller with a battery-backed cache. Most hardware RAID controllers have a battery-backed cache which is turned on by default. The battery-backed cache helps improve write performance by providing a write cache that can survive power failures. If the battery-backed cache is turned off on your hardware RAID controller, please turn it on. Disk Partitioning Partition the Disk to Support Aster Database You must partition the disks of the Aster Database queen and all nodes as shown in Table 1-1, Disk Partitioning. For additional information, including the impact when there is a change to the operating system, refer to the Aster Database 6.10 Release Notes. No Partition Name Size Partition Type File System Type Mount Path 1 boot 100 MB RAID1 ext3 on Red Hat and SLES /boot 2 active root 20 GB RAID1 ext4 on Red Hat, and ext 3 on SLES 4 active home 20 GB RAID1 ext4 on Red Hat, and ext 3 on SLES / /home 6 swap Allocate an amount equal to the RAM size plus 2 GB (across all disks). RAID0 swap swap 7 /data Rest of the disk space RAID5 ext4 on Red Hat, and xfs on SLES /data 10 Aster Database Installation and Upgrade Guide

11 Introduction to Aster Database Aster Database Installation Overview Network Preparation Before setting up any nodes in the cluster, you should consider not only how large your cluster will be to start, but potentially how large you will want it to grow eventually. Specifically, you must ensure that you reserve enough free IP addresses on the same network for the current and future needs of your Aster Database cluster. IP addresses need not be contiguous, but do need to be on the same network. Although Aster Database will not manage allocation of IP addresses, it is still best to keep all addresses as part of the same subnet. Also, it is best to limit the number of network devices between nodes and to keep the interconnect as balanced as possible. For example, placing all machines on the same VLAN but having a bridge or router between machines may cause bandwidth skew among nodes, and you may suffer undesirable performance as a result. Failure to make a large enough subnet may prohibit addition of new nodes in the future, and though it is possible to change network settings (including IP) of your nodes after installation, it is not recommended. Aster Database Installation Overview An Aster Database installation uses Teradata's Parallel Upgrade Tool (PUT) to install the Aster Database software. These instructions require that before installing the Aster Database software you have already installed and will manage the operating system on all nodes. See the Aster Database Platform/OS Support Matrix for a list of supported OS/hardware combinations. The process for installing the Aster Database is described in these sections: Preparing to Install Aster Database on page 15 Installing Aster Database on page 25 Performing Post-Installation Steps on page 45 Additional topics that describe backing up, upgrading and troubleshooting the Aster Database are described in these sections: Installing Aster Backup on page 49 Upgrading the Aster Database on an Aster Appliance on page 59 Upgrading the Aster Database on Commodity Hardware on page 101 Troubleshooting on page 145 Basic Aster Database Concepts Node Types There are three types of nodes in Aster Database: queen nodes, worker nodes, and loader nodes. For more information about the architecture of the Aster Database, refer to the Aster Database User Guide. For information the Aster Backup cluster, which is a separate cluster Aster Database Installation and Upgrade Guide 11

12 Introduction to Aster Database Basic Aster Database Concepts from the Aster Database cluster, refer to Installing Aster Backup on page 49 and the Aster Database User Guide. Queen Nodes The queen node (or coordinator) is the central node in the system and is represented in the Aster Management Console (AMC) by an icon with a Q. This is the node on which the Aster Database management software (including the AMC) is installed. It is the node responsible for all management of Aster Database, from node management to statement execution management. Worker Nodes Worker nodes are the workhorses of Aster Database they are the nodes where data resides and where query processing occurs. They are represented in the AMC by an icon with a W. In general, worker nodes represent the largest group of nodes in an Aster Database installation and are the focal point of management and administration. Loader Nodes Loader nodes are optional nodes that can be added to Aster Database in order to increase the load throughput of the system (the rate at which data can be loaded into the system). They are represented in the AMC by an icon with an L. By default, data is loaded into Aster Database through the queen node. However, if additional throughput is required, dedicated loader nodes can be added to the system. These nodes can also be used for bulk exporting of data from the system. Please contact Teradata if you need additional loading capacity, so that we may help you plan and configure your Aster Database optimally. Node States The node state or status indicates the operational health or condition of a physical node in Aster Database. In the AMC s Nodes > Node Overview tab, each node in the node list has a color indicating its status. The possible node statuses are: New When a node is first added to Aster Database, or registered, it is considered to be a New node. At this point, Aster Database is aware of the node s existence, but the node has not yet contacted the queen in order to be prepared, or loaded with the Aster Database software. Nodes are also shown as New immediately following a restart of Aster Database, before their state can be determined. Preparing After the node contacts the queen to be prepared, its status changes to Preparing. While in this status, it is loading the Aster Database software and preparing itself to become a participant in Aster Database. 12 Aster Database Installation and Upgrade Guide

13 Introduction to Aster Database Tools for Configuring Aster Database Prepared Once the node completes preparation, its status becomes Prepared. At this point, the node is ready to be incorporated into Aster Database so that it can host virtual workers (vworkers). Upgrading The Aster software on the node is being upgraded. Active Active and Passive are the acceptable states for nodes in a running cluster. Active nodes are nodes that are available immediately to process queries in Aster Database. Passive Active and Passive are the acceptable states for nodes in a running cluster. A Passive node is a standby that holds frequently updated copies of vworkers data and later can be made Active to take on query processing work as needed. Suspect Suspect nodes are nodes that have exhibited unusual behavior and are participating in the Aster Database in a limited capacity while being investigated for potential failures by the queen. Failed Failed nodes are nodes that are no longer participating in the Aster Database. Tools for Configuring Aster Database Some of the steps for installing and configuring Aster Database will be performed using the following tools: Aster Management Console (AMC) Aster Database Command Line Interface (ncli) AMC The Aster Management Console (AMC) is a browser-based management application that runs on the queen. You will be able to use the AMC after the Aster Database queen has been installed. Log in to the AMC 1 Open the Aster Database Management Console (AMC) in a browser window. To do this, navigate to address of the queen>. 2 In the login window, type the username db_superuser and the password db_superuser. Aster Database Installation and Upgrade Guide 13

14 Introduction to Aster Database Tools for Configuring Aster Database ncli The Aster Database command line interface (ncli) is a command line management tool for Aster Database. Many of the functions available in ncli can also be performed using the AMC. ncli provides the ability to manage the cluster when: A browser is not available, The queen is not running, or Network setup problems prevent you from accessing the AMC, but you can access a console window on the queen. You can find information on using ncli in the Aster Database User Guide. 14 Aster Database Installation and Upgrade Guide

15 CHAPTER 2 Preparing to Install Aster Database Before installing Aster Database, plan your installation using this information: Hardware Requirements Supported Platforms and System Requirements Removing Existing Data Cluster Network Prerequisites Set Up Passwordless Authentication with SSH Hardware Requirements Workers and Queens Worker nodes provide data storage in the Aster Database cluster. While the queen node stores only database metadata over the long term, its hardware requirements are otherwise identical to those of a worker, so Teradata recommends using the same type of hardware for workers and queens. Worker and queen nodes should conform to the hardware specifications provided in the Aster Database Platform/OS Support Matrix. To optimize system performance, Teradata recommends that the maximum number of worker nodes be 64 and the maximum number of vworkers per worker node be 6. Teradata recommends that all worker nodes have identical disk storage capacity. While the Aster Database software can handle nodes with differing storage capacity, it is designed to work best with worker nodes of the same storage capacity. Special Case: Running Aster Database on Virtual Machines If you wish to run a virtual machine-based Aster Database cluster as a development environment or to test out new features, you can download Aster Express. For the instructions and download, visit and search for Aster Express. Aster Database Installation and Upgrade Guide 15

16 Preparing to Install Aster Database Supported Platforms and System Requirements Notice! Running a very high number of vworkers on a node is not supported. Do not attempt to run more than 16 vworkers per physical worker node. Specifically, you can run the following number of vworkers per node, whichever is less: up to 16. However, Teradata recommends a maximum of six vworkers per physical worker node, or up to the number of physical cores per machine. Secondary Queen To enable your cluster to recover from a queen failure, you must install a secondary queen. The secondary queen should use hardware identical to the primary queen. Loaders Loaders store very little data and can have low disk storage capacity. For ease of manageability, disk storage on all loader nodes should be identical. If you would like to be able to quickly repurpose loader machines as replacements for failed worker machines, Teradata Aster recommends that you use the same hardware configuration for all worker and loader nodes. Loader nodes should conform to the hardware specifications provided in the Aster Database Platform/OS Support Matrix. Supported Platforms and System Requirements Supported Operating Systems for Aster Database Aster Database can be installed on Linux. See the Aster Database Platform/OS Support Matrix for details about the specific Linux versions supported. Supported Platforms for Drivers and Utilities Supported Web Browsers For a matrix of supported operating systems for the Aster Database drivers and utilities, see the Aster Database 6.10 Drivers and Utilities Guide. For a matrix of supported web browsers, see the Aster Database Platform/OS Support Matrix. Removing Existing Data Teradata's Parallel Upgrade Tool (PUT) will always upgrade an existing installation of the Aster Database. If performing a clean installation of the Aster Database, you must ensure that any existing Aster Database software and data on the machine is completely removed. Before performing a clean install: 16 Aster Database Installation and Upgrade Guide

17 Preparing to Install Aster Database Removing Existing Data 1 Back up any existing configurations, data and settings on the existing queen to another machine. All data within the Aster Database directory structure (/home/beehive and /data/ncluster) will be lost during a clean install. 2 Remove all data from the queen except the operating system. 3 Ensure that the worker and loader machines have the correct configuration: The operating system is installed, and nothing else. For machines that were previously used as worker and loader nodes, follow the steps in Deleting All Data to Re-Provision a Node on page 17. Remove Ghost Security Patch by Restoring Original glibc Package When performing a fresh installation of version 6.10.x of the Aster Database on a cluster that previously had the Ghost security patch installed, you must ensure that the Ghost security patch is removed before performing the Aster Database installation. The Ghost security patch is removed by restoring the original glibc package. To restore the original glibc package (in order to remove the Ghost security patch) when you are performing a fresh installation of version 6.10.x of the Aster Database on a cluster that previously had the Ghost security patch installed, follow this procedure: 1 (Optional) To verify that a cluster already has the Ghost security patch installed, run this command on the queen: # ncli node runonall 'rpm -qa grep aster-db-libc-patch-1-2' 2 Before performing a fresh installation of version 6.10.x of the Aster Database, run this command on every node in the cluster in order to restore the original glibc package, which will remove the Ghost security patch: # rpm -e aster-db-libc-patch-1-2 If, after running the command, this error message is returned, then the Ghost security patch is not installed and you can continue with the installation without taking further action to restore the original glibc package: error: package aster-db-libc-patch-1-2 is not installed Deleting All Data to Re-Provision a Node This section only applies if you need to re-provision a node that used to be part of an Aster Database cluster. Notice! If you wish to re-deploy a node that previously served as an Aster Database node, make sure the machine does not contain any data you need, since you must delete all its Aster-stored data before you re-deploy it. As a guideline, if your cluster is currently running at RF=2 (after removing the node that you will re-deploy), then it is probably safe to delete the node s data as explained below. Aster Database Installation and Upgrade Guide 17

18 Preparing to Install Aster Database Cluster Network Prerequisites 1 If the node you are re-provisioning is already part of the cluster, remove it from the cluster using the AMC or the ncli system removenode command. 2 Clean the node for reuse in the cluster by issuing these commands: cp -p home/beehive/bin/utils/init/nclusterdatacontroller.py /tmp /tmp/nclusterdatacontroller.py --uninstall rm /tmp/nclusterdatacontroller.py 3 Reboot the machine. Rebooting ensures that data clean-up is completed. 4 The machine is now ready to be re-added as a new worker or loader node in Aster Database. Cluster Network Prerequisites Gather Network Settings Collect the following information for each machine, and have it available during the installation. Collect queen information Make a note of the following settings for each network interface card (NIC) you will use on the machine that will be the Aster Database queen: Hostname and domain name IP address Collect worker, loader and backup node information Assemble a list of: IP addresses of all the worker and loader machines. IP addresses of the Backup Manager and all Backup nodes you will add. Multi-NIC Queen To set up the queen node if it has multiple NICs. Use this method to configure network traffic in the optimal way for your Aster Database installation: One NIC configured to a subnet dedicated to Aster Database and one or more other NICs configured on one or more externally visible subnets. TCP Ports Used by Aster Database This section is informational. You do not need to do any special configuration to enable Aster Database to function using these ports. These ports are set up automatically by the installer. 18 Aster Database Installation and Upgrade Guide

19 Preparing to Install Aster Database Cluster Network Prerequisites Core Components Table 2-2: TCP Ports Used by Aster Database: Core Components Port Service Used on Nodes 1711 Loader (queenexec) Loader 1850 Admission Control Monitor Queen 1860 Beehive State logger 1953 Stats Server Queen, Worker, Loader 1975 IWT Server Worker 1984 Shell server Queen, Worker, Loader, Backup 1985 Worker daemon Queen, Worker, Loader 1986 Replication daemon Queen, Worker, Backup 1987 Clone ID service Queen 1988 Progress Indicator daemon Queen 1989 Trashman Worker 1990 Process management master Queen 1991 Backup manager Backup 1995 IO Interceptor Queen, Worker 1996 Qos Slave Queen, Worker, Loader 2007 Mailman Queen 2008 Aster log server Queen, Worker, Loader, Backup 2009 Reliable State Saving Service Queen 2010 Registration Server Queen 2011 Qos Manager Queen, Worker 2012 Local Stats Collector 2105 Sysman Queen 2111 Replication Helper Queen, Worker, Backup 2113 File Stream Server Queen, Worker, Backup 2115 Ice Server Queen, Worker 2117 Ice Server Queen, Worker 2194 Platform Manager Queen, Worker, Loader 2199 Platform Database (reserved) Queen, Worker, Loader 2222 waspd Queen, Worker Aster Database Installation and Upgrade Guide 19

20 Preparing to Install Aster Database Cluster Network Prerequisites Table 2-2: TCP Ports Used by Aster Database: Core Components (continued) Port Service Used on Nodes 2304 Installer Daemon Queen 2305 Installer Client Queen, Worker, Loader 2345 Cleanup service 2406 Queen/Loader (queenexec) Queen, Loader 2407 Queen HTTP Queen 3211 Netcat Server Worker, Backup 4582 TxMan Queen 6543 HardwareStatCollector Queen, Worker, Loader 20 Aster Database Installation and Upgrade Guide

21 Preparing to Install Aster Database Cluster Network Prerequisites Local Database Instances Table 2-3: TCP Ports Used by Aster Database: Local Database Instances Port Service Used on Nodes 8000 local database instance at the queen 8001 Model worker (when activated) vworker database instances Note: TDput may use port 9000 during an installation or upgrade operation, but any use of the port by TDput occurs when the vworkers are down Backup database Transient Inter-node Data Transfer Ports Table 2-4: Ports Used by Aster Database: Transient Inter-node Data Transfer Ports Port Service Used on Nodes CreateWorkerViaCloning LogCollector Extensibility shared Java VM UI Web Servers Table 2-5: TCP Ports Used by Aster Database: UI Web Servers Port Service Used on Nodes 80 Apache HTTP Port Queen 443 Apache HTTPS Port Queen 8080 Tomcat HTTP Port Queen 8443 Tomcat HTTPS Port Queen 8005 Tomcat "Shutdown" Port Queen 8009 Tomcat AJP Integration Port Queen Non-Aster Services Table 2-6: TCP Ports Used by Aster Database: Non-Aster Services Port Service Used on Nodes 22 sshd All 8649 gmond Queen, Worker, Loader gmetad Queen Aster Database Installation and Upgrade Guide 21

22 Preparing to Install Aster Database Set Up Passwordless Authentication with SSH Set Up Passwordless Authentication with SSH Set Up Passwordless Authentication for Root User To install Aster Database, you need to create an SSH authorized key and set up passwordless root SSH. This section shows you the Aster-recommended way to set up passwordless root SSH. Depending on whether you already have an SSH key you want to use: If you already have a key, skip to Copy the SSH Key to the Queen on page 23. Otherwise, if you need to generate a new SSH key, proceed to Generate a New SSH Key on page 22. Generate a New SSH Key 1 Log in as root on the machine on which you wish to generate the SSH key. This could be the queen or another machine. 2 Generate a new key by running the following command: # ssh-keygen -t dsa 3 You will be prompted to enter the directory where the key should be saved. Press Enter to accept the default directory: Enter file in which to save the key (/root/.ssh/id_dsa): Press [Enter] key 4 Press the Enter key when prompted for a passphrase. If you create a passphrase the installation will fail: Enter passphrase (empty for no passphrase): Press [Enter] key Enter same passphrase again: Press [Enter] key Your identification has been saved in /root/.ssh/id_dsa. Your public key has been saved in /root/.ssh/id_dsa.pub. The key fingerprint is: 04:be:15:ca:1d:0a:1e:e2:a7:e5:de:98:4f:b1:a6:01 root@auser-queen 5 Change to the directory where your key file was created: # cd.ssh 6 Copy your DSA key file to authorized_keys to make it an SSH authorized key: # cat id_dsa.pub >> authorized_keys 7 Change the permissions on the authorized key file: # chmod 600 authorized_keys or # chmod og-rwx authorized_keys 8 Proceed to: If you generated the key on the queen, skip to Test the SSH Key on the Queen on page 23. If you generated the key on another machine, Copy the SSH Key to the Queen on page Aster Database Installation and Upgrade Guide

23 Preparing to Install Aster Database Set Up Passwordless Authentication with SSH Copy the SSH Key to the Queen 1 Log in as root on the machine that has the SSH key you want to use. 2 To make sure the key file works, issue an SSH command to localhost: # ssh localhost date If you are asked to confirm, type yes and press Enter. The command should then succeed without prompting for a password. 3 Make sure the queen is powered on and booted into its OS. 4 Change the working directory to your home directory on the machine with the SSH key: # cd 5 Copy the key file to the queen by running the following command, specifying the IP address of the queen to which you are copying the key: # scp -pr.ssh root@<queen-ip>: If you are asked to confirm, type yes and press Enter. If you are prompted for a password, enter it. 6 Verify that you can SSH to the queen without a password. # ssh <queen-ip> # exit 7 Proceed to Test the SSH Key on the Queen on page 23. Test the SSH Key on the Queen 1 Log in as root on the queen. 2 To make sure the key file works, issue an SSH command to localhost: # ssh localhost date If you are asked to confirm, type yes and press Enter. The command should then succeed without prompting for a password. 3 If you wish to do so, you may disable passwordless SSH for the root user after installation and addition of all nodes is completed. Enabling Passwordless Root SSH for All Nodes 1 Log in as root on the queen. 2 To make sure the key file works, open a SSH session to localhost: # ssh localhost If you are asked to confirm, type yes and press Enter. The login should then succeed without prompting for a password. 3 Exit the SSH session: # exit 4 Make sure the worker and loader nodes are powered on and booted into their OS. 5 Back on the queen, change the working directory to your home directory: # cd Aster Database Installation and Upgrade Guide 23

24 Preparing to Install Aster Database Set Up Passwordless Authentication with SSH 6 Copy the key file to each of the Aster Database nodes by running the following command, specifying the IP address of the node to which you are copying the key: # scp -pr.ssh root@<node-ip>: If you are asked to confirm, type yes and press Enter. If you are prompted for a password, enter it. 7 Verify that you can SSH to each worker and loader node without a password. # ssh <node-ip> # exit 8 Test the passwordless connections among all nodes by connecting via SSH from each of the nodes to all the other nodes. If you are asked to confirm, type yes and press Enter. 9 If you wish to do so, you may disable passwordless SSH when you no longer need it (for example, after adding a node, upgrading, and so on). Disabling Passwordless Root SSH for All Nodes After you ve completed the procedure that required passwordless root SSH, you may disable it for all nodes. 1 Log in as root on the queen. 2 Issue the command to disable passwordless SSH, providing the IP address of each worker and loader node in the cluster: # ncli sshkeys disable -n <IP1,IP2,...> Note that when specifying multiple node IP addresses using the -n option, they must be separated by a comma only, without spaces. 3 Whenever you need to re-enable passwordless SSH (i.e when adding a node, upgrading, etc.) the procedure will direct you to do so. Passwordless Authentication for Beehive User Setting up passwordless authentication for the Beehive user is performed after completing installation of the Aster Database. See Step 9 on page 40 for information on performing this procedure. 24 Aster Database Installation and Upgrade Guide

25 CHAPTER 3 Installing Aster Database This chapter explains how to perform an Aster Database installation on a supported system. See the Aster Database Platform/OS Support Matrix for a list of supported OS/hardware combinations. Perform all the steps unless the text directs you to skip a step for your particular environment. Prerequisites Supported Operating Systems These instructions require that you have already installed and will manage the operating system on all nodes in the cluster. See the Aster Database Platform/OS Support Matrix for a list of supported OS/hardware combinations. Notice! When you perform a fresh Aster Database install, the installation software expects a clean machine without old Aster Database data and settings. If you want to reprovision any Aster node, see Deleting All Data to Re-Provision a Node on page 17. Hardware and Storage Checklist Hardware and Storage Checklist Make sure you are ready to install Aster Database: 1 Review the information described in Early Planning For an Aster Database Installation on page 9 to ensure that storage and networking for your cluster is correctly setup for the installation of Aster Database. 2 These installation instructions assume that your queen, workers, and loaders contain no Aster data or configuration that you wish to keep. 3 Complete the steps in Preparing to Install Aster Database (page 15). The topics from that section include: Hardware Requirements: Do your processors and RAM meet requirements? Supported Platforms and System Requirements: Are you installing Aster Database on a supported OS/hardware combination? Aster Database Installation and Upgrade Guide 25

26 Installing Aster Database Prerequisites Removing Existing Data: Have you completely removed all existing Aster Database software and data from the machine? Cluster Network Prerequisites: Will you be using multi-nic machines? Have you collected the necessary information to have it available during the installation? Set Up Passwordless Authentication with SSH: Have you set up passwordless authentication with SSH for the root and beehive users? Next step: Go to the next section, Obtaining Installation Files. Obtaining Installation Files Work with your Account Team to order the new base version of the Aster software for either the Appliance or commodity hardware. The Aster software will contain the required base installation files, along with these dependency files, in order to perform the Aster Installation: cliv noarch.rpm tdicu noarch.rpm TeraGSS_linux_x noarch.rpm tptbase noarch.rpm The Teradata At Your Service website, is an additional resource that is available to customers and Teradata employees. This is a secure site from which you can access Orange Books, technical alerts, and knowledge repositories; view and join forums; and download software packages and documentation. The following files are required to perform this installation of the Aster Database. They should be put in the /var/opt/teradata directory on your cluster: Ensure that all required files for a specified version of an installation are located in a single directory and that a separate directory is used for each subsequent version of required installation files. NOTE: The ADE files will not be included beyond the AD6.10 release. They can be downloaded for free through the Teradata Developer Exchange website, Required files: ADE-linux.gtk.x86_64.tar.gz ADE-linux.gtk.x86.tar.gz ADE-macosx.cocoa.x86.tar.gz ADE-plugin-only.zip ADE-win32.win32.x86.zip aster-clients-linux r x86_64.rpm aster-db-common r x86_64.rpm aster-db-config-common r x86_64.rpm aster-db-config-redhat r x86_64.rpm aster-db-config-suse r x86_64.rpm 26 Aster Database Installation and Upgrade Guide

27 Installing Aster Database Install Aster Database aster-db-coordinator r x86_64.rpm aster-db-loader r x86_64.rpm aster-db-pkg r x86_64.rpm aster-db-toolchain r x86_64.rpm aster-db-worker r x86_64.rpm cliv noarch.rpm tdicu noarch.rpm TeraGSS_linux_x noarch.rpm tptbase noarch.rpm The TDput installer package compatible with your installed operating system. To install this release of the Aster Database, the minimum required version of TDput is: For Appliances running a supported version of the TD-SLES operating system: TDput or later sles11 build for appliance. For commodity hardware running a supported version of the Linux operating system (for example, SLES11 SP2 or Redhat 6.4 or 6.5): TDput or later non- Teradata OS build for commodity. The non-teradata OS build is for both Redhat and non-teradata SLES 11. Next Step: Proceed to Install Aster Database. Install Aster Database These instructions describe installing the Aster Database on a supported OS/hardware combination. See the Aster Database Platform/OS Support Matrix for a list of supported OS/hardware combinations. Preparation Synchronize the clocks on all of the nodes in the cluster. For systems running a version of the Teradata SLES operating system: Verify that these packages are installed: libasound libstdc++.so.6 net-snmp (requires installation of perl-snmp) For NEW Appliance installations only. Ensure that teradata-asterdb is not installed or the installation will fail. To determine if teradata-asterdb is installed, issue this command: rpm -qa grep teradata-asterdb To uninstall teradata-asterdb if it is installed, issue this command: rpm -erase teradata-asterdb For systems running a version of the Red Hat Enterprise Linux operating system, verify that net-snmp is installed on all nodes. Aster Database Installation and Upgrade Guide 27

28 Installing Aster Database Install Aster Database Ensure that all nodes to be included in the cluster contain the same /etc/hosts file with correct and complete information. PUT and ncli both use /etc/hosts files to group nodes and to add workers and loaders. The number of partitions should be an integral multiple of the number of workers in the.cluster_config file. Therefore, the value for NUM_PARTITIONS should be a multiple of the value of NUM_WORKERS. For example, if NUM_WORKERS = 3, the NUM_PARTITIONS should be 3, or 6, and so on. Verify that max open files is at least and is identical on all worker nodes. To do this, issue the following command on each node: ulimit -a If you change the OS configuration parameter that specifies the maximum number of open files, you do not need to restart the server or the cluster at this time. The cluster is restarted later in the procedure, so the configuration change will take effect at that time. Verify that version 1.6 or 1.7 of Java is installed on the computer that will be used to connect to PUT. PUT does not currently support a connection from a computer running Java version 1.8. Procedure Perform these steps to install or upgrade a cluster using the Parallel Upgrade Tool (PUT): Information on using Teradata's Parallel Upgrade Tool (PUT) is documented in the Parallel Upgrade Tool (PUT) Reference Guide. This guide is available on the Teradata Information Products website: 1 Select a machine to be the PUT master node. The master node: Is typically the coordinator of the cluster. Must be located on the same network as all machines in the cluster. Hosts the software RPM files to be installed on the cluster. 2 Install PUT on all nodes in the cluster including the secondary queen (optional depending on your configuration) and the PUT master node (if it is not a node in the cluster). a b Determine if PUT is installed on the node by issuing this command: rpm -qa grep TDput If TDput-xxxx is returned, PUT is installed on the node. Issue the /etc/init.d/tdput start command to start TDput services and then continue on to Step 3 or, if you want to upgrade the installed version of PUT, continue to Step b. If TDput-xxxx is not returned, PUT is not installed on the node. Continue on to Step b. To perform an initial installation of TDput on nodes enabled with root ssh: 28 Aster Database Installation and Upgrade Guide

29 Installing Aster Database Install Aster Database i ii iii Execute this command on the queen in the cluster: rpm -Uvh TDput*.rpm Open a supported web browser. Enter the URL for the system in the browser bar. Typically, this is or iv v vi When the PUT Logon screen appears: Enter the root ID and password for the node to which you are connecting. Select Teradata Support Mode (QuickLook ID). Enter a valid, active QuickLook ID. Run the PUT install and upgrade operation in order to install PUT on the remaining nodes in the cluster. Refer to the Parallel Upgrade Tool (PUT) Reference Guide for information about running the PUT install and upgrade operation. For nodes not enabled with root ssh: Copy the TDput package to all nodes in the cluster Execute this command on every node in the cluster: rpm -Uvh TDput*.rpm c To upgrade an existing installation of TDput, run the PUT install and upgrade operation in order to upgrade all the nodes at the same time. Refer to the Parallel Upgrade Tool (PUT) Reference Guide for information about running the PUT install and upgrade operation. 3 Once PUT is installed on the master node, you can connect to the master node using HTTP on port 8080 or HTTPS on port For example: Or 4 If there is an existing Aster Database installation on your cluster and you are performing a fresh installation of the Aster Database: a Issue this command on the coordinator to shut down the cluster: ncli system softshutdown b You will need to clean the cluster. To clean the cluster, execute the following sequence on each node in the cluster: cp /home/beehive/bin/utils/init/nclusterdatacontroller.py /tmp /tmp/nclusterdatacontroller.py --uninstall rm -f /tmp/nclusterdatacontroller.py 5 Specify the makeup of your cluster by creating a /home/beehive/.cluster_config file on the queen node. a For a commodity hardware installation, use this file to specify the cluster IP address for the queen (SYSMAN_IP), the number of workers in the cluster, the total number of vworkers (partitions), and the IP address of the NTP server (optional). The format of the file for a commodity hardware installation is: For the primary queen: Aster Database Installation and Upgrade Guide 29

30 Installing Aster Database Install Aster Database PRIMARY_IP=<ip addr> # cluster IP address of the primary queen NUM_WORKERS=<integer> # number of worker nodes NUM_PARTITIONS=<integer> # number of primary vworkers NTP_SERVER=<ip_address> # IP address of an NTP server (optional) For the secondary queen: PRIMARY_IP=<ip addr> # cluster IP address of the secondary queen NUM_WORKERS=<integer> # number of worker nodes NUM_PARTITIONS=<integer> # number of primary vworkers NTP_SERVER=<ip_address> # IP address of an NTP server (optional) b For an Aster appliance installation, use this file to specify the internal IP address for the queen using the IP address of the interface on the queen node that will be visible to the worker nodes (for example, the bynet interface IP address), the number of workers in the cluster, the total number of vworkers (partitions), and the IP address of the NTP server (optional). The format of the file for an Aster appliance installation is For the primary queen: PRIMARY_IP=<ip addr> # internal IP address of the primary queen NUM_WORKERS=<integer> # number of worker nodes NUM_PARTITIONS=<integer> # number of primary vworkers NTP_SERVER=<ip_address> # IP address of an NTP server (optional) For the secondary queen: PRIMARY_IP=<ip addr> # internal IP address of the secondary queen NUM_WORKERS=<integer> # number of worker nodes NUM_PARTITIONS=<integer> # number of primary vworkers NTP_SERVER=<ip_address> # IP address of an NTP server (optional) 6 Connect to PUT from a web browser. You can connect to PUT using either an HTTP or HTTPS connection. To start PUT from a web browser: a b c Open a supported web browser. Enter the URL for the system in the browser bar. Typically, this is the master node of the queen, or When the PUT Logon screen appears: i ii If a window opens asking if you want to run the TDput Loader application, click Run. Enter the root ID and password for the node to which you are connecting. iii If you have a valid, active Teradata QuickLook ID, select Teradata Support Mode (QuickLook ID), and enter a valid, active QuickLook ID. 7 Install the Aster Database software using PUT. For detailed information on using PUT to perform an installation, or to obtain information on common PUT install software steps, refer to the Install/Upgrade Software Section in the Parallel Upgrade Tool (PUT) Reference Guide. The subset of topics listed in this step are intended to supplement the detailed information available in the corresponding topics in Install/Upgrade Software Section in the Parallel 30 Aster Database Installation and Upgrade Guide

31 Installing Aster Database Install Aster Database Upgrade Tool (PUT) Reference Guide, and provide information specific to an Aster Database software installation. Detailed information on using Teradata's Parallel Upgrade Tool (PUT) is documented in the Parallel Upgrade Tool (PUT) Reference Guide. This guide is available on the Teradata Information Products website: a On the PUT interface screen, click Install/Upgrade Software. b Configuration Mode - Select Typical. Click Next. c Find All Subnets - Select the subnet that corresponds to the cluster s subnet. Click Next. This action can take several minutes to complete, and returns the IP address of all subnets where PUT daemons are running. Aster Database Installation and Upgrade Guide 31

32 Installing Aster Database Install Aster Database d Select Nodes - Select the IP address of the nodes (including the secondary queen IP address if applicable) in the cluster from the Available list. If all nodes in the cluster do not have a shared subnet, select the subnet on which the nodes you want to install are located; multiple runs of the TDput operation will be required. Click >> to move them to the Selected list. Click Next. 32 Aster Database Installation and Upgrade Guide

33 Installing Aster Database Install Aster Database e f g Key Distribution - In the Password screen, enter root and the root password. Click Next. No longer applicable per Jessica Friis Jessica - Does this action apply to only commodity HW? Run System Check - If the System Check Found Problems screen indicates vmf_check_sanity command failed, select Ignore. No longer applicable per Jessica Friis Select Spool Area - In the Select Spool Area For Linux Nodes screen, select the default location. Click Next. h Media Sources -In the Enter Source For New Packages screen, browse to the source for the RPM packages downloaded in Step 3, click Next. Aster Database Installation and Upgrade Guide 33

34 Installing Aster Database Install Aster Database In the Media Source Confirmation screen, use the default selections indicated on the screen. Click Next. In the Media Sources To Be Scanned screen, click Next. 34 Aster Database Installation and Upgrade Guide

35 Installing Aster Database Install Aster Database i Group Nodes - In the Group Nodes screen, put the cluster's nodes into two or three different groups (queen (including the secondary queen if applicable), workers, or loaders). For each group you will loop through this procedure: I During an initial installation of the Aster Database, all nodes should initially be shown in one group until you assign them to different groups. If the cluster s nodes are improperly grouped before any action is taken or if PUT will not allow groups to be assigned or combined into a single group, refer to the Parallel Upgrade Tool (PUT) Reference Guide or Chapter 8, Troubleshooting for troubleshooting information. i Select the node(s) in the group. (Press Ctrl-click to select more than one node.) ii Click Modify Group, which will open the Modify Group screen. iii In the Modify Group screen: Under the Choose Group heading, Select New Group. Aster Database Installation and Upgrade Guide 35

36 Installing Aster Database Install Aster Database Under the Node Type heading, select the appropriate Node Type: ADQueen (for the primary queen and, if applicable, the secondary queen), ADWorkr, or ADLoadr. If the Node Type heading is not available: * Confirm that the installed version of PUT is minimally and update to a newer version if necessary. * For new installations only, refer to the Troubleshooting PUT Appendix in the Parallel Upgrade Tool (PUT) Reference. j iv v Click Submit Changes, which returns you to the Group Nodes screen. Repeat these steps until all cluster nodes are in the appropriate groups, and then click Next. Select Packages - The Select Packages screen lists the nodes and the software package and version that will be upgraded on your system. Accept the software package installation recommendations by clicking Next and then proceed to Step k on page I- 37. If the nodes and software packages are not auto selected, perform this procedure to select the software packages: 36 Aster Database Installation and Upgrade Guide

37 Installing Aster Database Install Aster Database In the Select Packages screen, associate the package with the group on which it should be installed. For each group: i Select the appropriate package name for the node type: For the Queen (the primary and, if applicable, the secondary), select aster-dbcoordinator version For the worker group, select aster-db-worker version For the loader group, select aster-db-loader version ii iii In the Modify screen, select the group onto which the package should be installed. Click Next, which will open the Install/Upgrade Software: Package Dependencies Exist screen. Ensure that you do not click the Select All option. k iv v vi In the Install/Upgrade Software: Package Dependencies Exist screen, scroll through the list and verify that the package status for every package under the Status column indicates either: Installed (in black text) Available but not selected for upgrade (in blue text) Available but not selected for upgrade - version specific (in blue text). If, instead of the Install/Upgrade Software: Package Dependencies Exist screen, the Package Dependencies Not Met screen opens, ensure that the necessary software packages are properly installed and then restart the procedure. If the package status for every package under the Status column is correct, click Yes. This action will return you to the Select Packages screen. In the Select Packages screen, click Next. Confirm Package Selections - In the Confirm Package Selections screen, verify that the packages to be installed, and the number of nodes that each package will be installed on, are correct. Click Next. Aster Database Installation and Upgrade Guide 37

38 Installing Aster Database Install Aster Database l m Distribute Packages - No user interaction required. The time for this step to complete is dependent on the size of the packages. Begin Install? - In the Begin Install? screen, click Next. n Package Install - In the Package Install screen, click Next. This step will take time to complete. In the Overall Package Install Results screen, verify that all packages were installed successfully. Click Next. 38 Aster Database Installation and Upgrade Guide

39 Installing Aster Database Install Aster Database o Pause for Change Control Activities - This step provides an intentional pause to perform any change control activities. Click Next. p Finished! - This step cleans up temporary files and completes the upgrade. Click Finish to complete the operation prior to performing another PUT operation. Aster Database Installation and Upgrade Guide 39

40 Installing Aster Database Install Aster Database q Click Next to return to the main screen. 8 Manually "source" the asterenv.sh file as described below, to ensure that, if required, your current shell will have the correct environment variables in order to complete the installation: Required - If you will use ncli to perform Step 12, Step 13, Step 14, or Step 17, perform these steps: i Locate and open either of these files: ~/.profile or ~/.bashrc ii In the opened file, copy and paste this text as a single line into the file: [ -f /home/beehive/config/asterenv.sh ] &&. /home/beehive/config/asterenv.sh iii iv Save the file and exit the editor. Exit out of your current terminal window. v Open and log in to a new terminal window. If you did not perform steps i and ii above, you will need to manually "source" the asterenv.sh file by executing this line each time you log in:. /home/beehive/config/asterenv.sh Optional - If you will use the AMC to perform Step 12, Step 13, Step 14, and Step 17, performing this step is optional and the success of the installation will not be impacted whether or not you perform this step. If you choose to perform this step, execute this command as a single line on the queen: [ -f /home/beehive/config/asterenv.sh ] &&. /home/beehive/config/asterenv.sh 9 Ensure that SSH keys for the beehive user are set up on all nodes. To set up passwordless authentication for the Beehive user, perform this procedure: a Log in to the queen as the user root, and then issue this command to switch to the beehive user: # su - beehive 40 Aster Database Installation and Upgrade Guide

41 Installing Aster Database Install Aster Database b c d e f g h i j k l m Generate a new key by running the following command: # ssh-keygen -t dsa You will be prompted to enter the directory where the key should be saved. Press Enter to accept the default directory: Enter file in which to save the key (/root/.ssh/id_dsa): Press [Enter] key Press the Enter key when prompted for a passphrase. If you create a passphrase the installation will fail: Enter passphrase (empty for no passphrase): Press [Enter] key Enter same passphrase again: Press [Enter] key Your identification has been saved in /root/.ssh/id_dsa. Your public key has been saved in /root/.ssh/id_dsa.pub. The key fingerprint is: 04:be:15:ca:1d:0a:1e:e2:a7:e5:de:98:4f:b1:a6:01 root@auser-queen Change to the directory where your key file was created: # cd.ssh Append your DSA key file to authorized_keys to make it an SSH authorized key: # cat id_dsa.pub >> authorized_keys Change the permissions on the authorized key file: # chmod 600 authorized_keys or # chmod og-rwx authorized_keys To make sure the key file works, issue an SSH command to localhost: # ssh localhost date If you are asked to confirm, type yes and press Enter. The command should then succeed without prompting for a password. Exit the SSH session: # exit Make sure the worker and loader nodes are powered on and booted into their OS. On the Queen, change the working directory to your home directory: # cd Copy the key file to each of the Aster Database Backup nodes by running the following command, specifying the IP address of the node to which you are copying the key: # scp -pr /home/beehive/.ssh/ root@<node-ip>/home/beehive/ # ssh root@<node-ip> \ "chown -R beehive:beehive /home/beehive/.ssh" If you are asked to confirm, type yes and press Enter. If you are prompted for a password, enter it. Verify that you can SSH to each worker and loader node without a password. # su - beehive # ssh <node-ip> Aster Database Installation and Upgrade Guide 41

42 Installing Aster Database Install Aster Database n # exit Copy the key file to the queen by running the following command, specifying the IP address of the queen to which you are copying the key: # scp -pr /home/beehive/.ssh/ \ root@<target-machine-ip>/home/beehive/ # ssh root@<target-machine-ip> \ "chown -R beehive:beehive /home/beehive/.ssh" If you are asked to confirm, type yes and press Enter. If you are prompted for a password, enter it. Ensure the beehive password is correct on all nodes. o Verify that you can SSH to the queen without a password. # su - beehive # ssh <target-machine-ip> # exit 10 As the root user, execute this command on the queen and allow it to successfully complete before adding workers and loaders: service local start 11 After PUT has completed the transaction, assemble the cluster by adding workers and loaders. To assemble the cluster, on the coordinator using ncli: a For each worker, execute this command: ncli system addnode worker <ip address of worker> --preinstalled b For each loader, execute this command: ncli system addnode loader <ip address of loader> --preinstalled Alternatively, you can use the AMC to add the worker or loader nodes to the cluster. Refer to the Add New Nodes to the Cluster topic under the Cluster Expansion section in the Aster Database User Guide 12 Verify that all nodes are active (coordinator) or new (workers and loaders) by issuing this command: ncli node show Alternatively, you can use the AMC to show the status of the node. Refer to the Add New Nodes to the Cluster topic under the Cluster Expansion section in the Aster Database User Guide for information on using the AMC to show the status of the node. 13 Start the cluster by issuing this command: ncli system softstartup Alternatively, you can use the AMC to start the cluster, but doing so will shut down the system before restarting. Refer to the Add New Nodes to the Cluster topic under the Cluster Expansion section in the Aster Database User Guide for information on using the AMC to start the cluster. 14 Verify that the status of all nodes is active or prepared by issuing this command: ncli node show Alternatively, you can use the AMC to show the status of the node. Refer to the Add New Nodes to the Cluster topic under the Cluster Expansion section in the Aster Database User Guide for information on using the AMC to show the status of the node. 42 Aster Database Installation and Upgrade Guide

43 Installing Aster Database Install Aster Database 15 For the Secondary Queen Only. Aster services do not need to be started on the secondary queen. To stop Aster services from starting up automatically on reboot of the secondary Queen: a Log in to the secondary queen, as root. b Stop Aster services from starting up when the machine boots by issuing this command: # chkconfig local off. 16 Optional - Stop the TDput services by issuing this command on all nodes in the cluster: # /etc/init.d/tdput stop 17 Activate the cluster by issuing this command: ncli system activate Alternatively, you can use the AMC to activate the cluster. Refer to the Activate Aster Database topic under the Cluster Expansion section in the Aster Database User Guide for information on using the AMC to show the status of the node. Next step: Proceed to Performing Post-Installation Steps on page 45. Aster Database Installation and Upgrade Guide 43

44 Installing Aster Database Install Aster Database 44 Aster Database Installation and Upgrade Guide

45 CHAPTER 4 Performing Post-Installation Steps This section explains post-installation steps you must perform immediately after installing Aster Database. This section contains: Run Diagnostic Tests Security Configurations Use Your Aster Database Set up Event Alerts Run Diagnostic Tests Run tests to ensure Aster Database is running correctly. Procedure: 1 Open a console window and SSH or log into the console of the queen as user: root. 2 Type the following: cd /home/beehive/bin/utils/diagnostictests./testrunner.py -f BasicSanityTestSuite.conf 3 Verify from the console output that the tests pass. Contact Teradata Global Technical Support (GTS) if there are failures. Next steps: Proceed to Security Configurations. Security Configurations Disable Passwordless Root SSH If you want to disable passwordless root SSH on the cluster, you may do so now by logging in to the queen and issuing: # ncli sshkeys disable -n <IP1,IP2,...> Aster Database Installation and Upgrade Guide 45

46 Performing Post-Installation Steps Use Your Aster Database Note that when specifying multiple node IP addresses using the -n option, they must be separated by a comma only, without spaces. Reinstall JCE to Support Kerberos If your Aster cluster is configured to connect to Hadoop clusters with Kerberos authentication and uses AES-256 encryption, JCE may need to be reinstalled on all nodes after installation. Refer to Java Cryptography Extension (JCE) Policy File Installation in the Aster Database User Guide. Set Root Password on All Nodes in the Cluster Once you have installed Aster Database, you should change the password of the UNIX root user on all nodes. To do this: 1 Log in to a node as root. 2 Use the passwd command to set a new password: # passwd <new_password> 3 Repeat this for each worker and loader node. Next steps: Proceed to: Use Your Aster Database Use Your Aster Database Your Aster Database installation is complete. Refer to the Aster Database User Guide and the Aster Client Guide for information on these topics: Creating AMC user accounts Installing clients Installing drivers Creating databases and loading data Set up Event Alerts You can configure Aster Database to alert you when critical conditions occur within the cluster. For instructions on how to do this, see the Aster Database User Guide. Teradata recommends setting these crucial alerts immediately after installation, so that you are notified by the system of these events: ST0001: Disk >= 90% full ST0002: Disk >= 80% full SY0002: Node failed SY0005: vworker failed SY0008: RF == 0 46 Aster Database Installation and Upgrade Guide

47 Performing Post-Installation Steps Use Your Aster Database SY0009: RF is below the target value. Teradata also recommends, though less critical, that you configure these alerts: HM0001: Generic health monitoring related to disks running low on available space. HM0002: Generic health monitoring related to disks running low on available space. MC0002: User attempted Soft Restart MC0003: User attempted Hard Restart MC0005: User attempted to remove a node. ST0003: Disk > 65% full SY0001: Node is suspect SY0011: Disk error detected on worker node Aster Database Installation and Upgrade Guide 47

48 Performing Post-Installation Steps Use Your Aster Database 48 Aster Database Installation and Upgrade Guide

49 CHAPTER 5 Installing Aster Backup Planning Your Aster Backup Installation Supported Platforms Aster Backup runs on these 64-bit Linux operating systems: Red Hat Enterprise Linux 6.4 and 6.5 Teradata SUSE Linux Enterprise Server 11 SP1 SUSE Linux Enterprise Server 11 SP2 Node and Disk Requirements How Many Backup Nodes do I Need? Your Backup cluster should contain fewer nodes than your Aster Database. Most installations contain two to three Backup Nodes. Five nodes are usually enough for the largest Aster Database clusters. How Much Disk Space does my Backup Cluster Need? To determine the disk-space requirements of your Backup cluster, follow this formula: where: d is the amount of active data (uncompressed size) in Aster Database; n is the number of incremental backups you wish to maintain; i is the amount of data in an incremental backup; and 2.5 is the typical data compression rate for a physical backup. Note that active data in the formula refers to the amount of data, excluding replication, redundancy, and any backups. Aster Database Installation and Upgrade Guide 49

50 Installing Aster Backup Planning Your Aster Backup Installation For example, if your Aster Database has 10 TB of active data, you load 100 GB (that is, 0.1 TB) of new data each day, and you want to keep 7 days worth of daily incremental backups, then you would need a Backup cluster with at least (10 + (7 * 0.1)) / 2.5 TB of space, or 4.28 TB. This formula provides a safe estimate of the amount of space you will need whether using logical or physical backups. Storage Requirements and Recommendations RAID Type Teradata Aster recommends using RAID 10 for Aster Backup nodes. While this requires more raw disk space than RAID 5, the performance benefit warrants the extra cost in disk space. Storage Location To add more storage space, you may provision space on a separate partition. When doing this, mount the partition at /home/beehive/data, and ensure that it is writable by the user beehive. For example, if your main disk partition is /primary, then you should create a symbolic link called /home/beehive/data that points to /primary. Log Location The log files for Aster Backup are located in /home/beehive/data/logs on each backup machine. Note that there is no cluster.log for backup machines. Networking Requirements and Recommendations 1 SSH server should be running. 2 Backup Nodes should have high-bandwidth access to the Aster Database worker nodes. This may require setting up routes between the Aster Database worker nodes and Aster Backup Nodes. Tip: How long does Aster Database take to make a backup? Since Aster Database worker nodes and Backup Nodes are typically not co-located in the same rack, the network link between the Aster Database rack and the backup rack is typically the bottleneck in backup performance. This formula provides an estimate of the required time to make a backup: where d is the amount of data to be backed up (uncompressed), b is the network throughput rate, and 2.5 is the typical data compression rate of a physical backup. For example, a full backup of a 10 TB Aster Database over a 400 Mbps connection takes approximately ((10,000,000 MB / 2.5) / 400 Mbps) seconds to complete, or about 22.2 hours. Aster Backup and Aster Database Version Requirements Aster Backup must have the same version number as Aster Database. Before getting started with Aster Backup, check the version number of your Aster Database, and upgrade if 50 Aster Database Installation and Upgrade Guide

51 Installing Aster Backup Installing Aster Backup necessary. You can check the Aster Database version number by looking in the Aster Management Console (AMC) on the Admin > Cluster Management > Nodes tab. If Backup is already installed, you may check the version number on the Backup Manager machine by reading the file /home/beehive/bin/.build. Check the line BUILD_VERSION to ensure that it matches the build number shown in the AMC. Installing Aster Backup This section explains how to install Aster Backup in your cluster: Preparing the Backup Cluster Machines Obtaining Installation File Installation Script Preparing to Install Installation Procedure Preparing the Backup Cluster Machines To prepare the machines of the Aster Backup cluster, follow the steps below: 1 Check which version of Python is installed: $ python -V. Make sure Python is installed. Do this check on the machine from which you will launch the installer, and on all machines that will be part of the Backup cluster. 2 If you are installing on Red Hat, you will need the following kernel patches: On Red Hat 6.4: kernel-firmware el6.noarch.rpm kernel el6.x86_64.rpm On Red Hat 6.5: kernel-firmware el6.noarch.rpm kernel el6.x86_64.rpm 3 If you are installing on commodity SLES, no specific kernel patch is required. 4 If you are installing on Teradata SLES 11 SP1 on an appliance, the appliance must have a supported version of the kernel installed. The supported versions of the kernel are: Hardware Operating System Operating System Version Kernel Version Appliance 2 Teradata SLES 11 SP1.41 Appliance 3 and 3H Teradata SLES 11 SP1.41 Appliance 4 Teradata SLES 11 SP1.41 Appliance 5 Teradata SLES 11 SP1.53 Aster Database Installation and Upgrade Guide 51

52 Installing Aster Backup Installing Aster Backup Obtaining Installation File 5 Open the ports listed below on all firewalls that control traffic to and from the Backup cluster machines: 22 (SSH) All ports in the range These firewall ports must be opened for communication between all Backup Nodes and all Aster Database worker nodes. 6 Make sure the SSH server is started on each machine in the Backup cluster: $ sudo /etc/init.d/sshd start Work with your Account Team to obtain the correct version of the Aster Backup installation bundle, ncluster-backup-upgrade.tar for this release. This bundle contains these required files to install Aster Backup on the Backup cluster: backup-sw.tar.gz install_backup.py install_backup_node.py tc_backup_x86_64.tar.gz Installation Script Overview The installation script install_backup.py installs and registers the Backup cluster on a set of machines. One of the Backup Nodes in the Backup cluster is designated as the Backup Manager. The Backup Manager runs the administrative interface and also acts as a Backup Node, storing backed up data. Note! Note that for an upgrade, the installer gets a list of all the nodes from the Backup Manager, so you don t have to specify each machine when running the installer. If it can t get the list, it will display a notification message. If that happens, you can then upgrade the nodes separately using the upgrade-nodes argument. 52 Aster Database Installation and Upgrade Guide

53 Installing Aster Backup Installing Aster Backup Arguments Table 5-1: Arguments to install_backup.py Flag install install-nodes uninstall upgrade upgrade-nodes -h, -help, --help -m <backup_mgr_ip>, --bmgr=<backup_mgr_ip> Description Installs Aster Backup on the Backup Manager and Backup Nodes and registers all nodes. Installs Aster Backup on Backup Nodes only and registers all Backup Nodes. Uninstalls Aster Backup from the Backup Manager and Backup Nodes and removes any existing backups stored in the /home/beehive/data directory. Upgrades the existing installation of Aster Backup on the Backup Manager and all Backup Nodes. Upgrades an existing installation of Aster Backup for all Backup Nodes only. Shows the help message. Specifies the IP address of the Backup Manager. -n "<backup_node1_ip> <backup_node2_ip>...", --bnodes="<backup_node1_ip> <backup_node2_ip>..." Specifies the IP addresses of the Backup Nodes. Note that if there are more than one Backup Node, you must enclose the list of IP addresses in quotes, as in this example: -n " ". The -n option is not used with the upgrade command. -k Specifies a key for SSH when running the installer as root. When used, you won t have to supply the root password when installing. Supply the path and filename of the key on the machine which is running the Aster Backup installer. -p <package_dir>, --packagedir=<package_dir> Supplies the directory containing the installer packages backup-sw.tar.gz and tc_backup_x86_64.tar.gz. -f Forces installation without any prompts. Note that in order for this to work, you must run the installer as the root user. Unattended installation is not recommended. Preparing to Install Do the following while logged in as root on the Backup Manager and each Backup Node: 1 Create the directory for Aster Backup: # mkdir /home/beehive 2 Create a beehive group: # groupadd -g 1000 beehive 3 Create the user account beehive with the home directory /home/beehive: # useradd beehive -d /home/beehive -g beehive 4 Create a password for the user beehive, entering the password when prompted: # passwd beehive Aster Database Installation and Upgrade Guide 53

54 Installing Aster Backup Installing Aster Backup 5 Make beehive the owner of the /home/beehive directory: # chown beehive.beehive /home/beehive 6 Log in as user beehive : # su - beehive 7 Create the /home/beehive/data directory: $ mkdir /home/beehive/data 8 Check the amount of disk space available in /home/beehive/data on each Backup Node: $ df -h /home/beehive/data If the space is not sufficient to store backups, you ll need to create a symbolic link to a directory with more space on each Backup Node. The following example uses the directory /data: a b c d Change to the target directory: $ cd /data Create the symbolic link: $ ln -s /data /home/beehive/data Check that the link was created: $ ls -al /home/beehive/data lrwxrwxrwx 1 beehive beehive 6 Sep 13 15:59 /home/beehive/data -> /data/ Set permissions on the target directory and the /home/beehive/data directory: $ chmod R 755 /data $ chmod R 755 /home/beehive/data e If the previous step returns any errors, then some files in /data belong to a user other than the beehive user. To correct this issue, execute these commands in order to create a symbolic link from /home/beehive/data to /primary, which is a symbolic link to /data/ncluster where the last two directories are owned by the beehive user: $ su - beehive; $ ln -s /primary /home/beehive/data; 9 Proceed to Setting Up Passwordless SSH on page 54. Setting Up Passwordless SSH To simplify cluster configuration, Aster Database requires passwordless root SSH among the queen and all worker nodes in all directions. This means that the queen, all worker nodes, and any backup nodes must have the same SSH authorized key. This section shows you the Asterrecommended way to set this up. Depending on whether you already have an SSH key you want to use: If you already have a key, skip to Copy the SSH Key to All Nodes on page 55. Otherwise, if you need to generate a new SSH key, proceed to Generate a New SSH Key on page Aster Database Installation and Upgrade Guide

55 Installing Aster Backup Installing Aster Backup Generate a New SSH Key 1 Log in as root on the machine on which you wish to generate the SSH key. 2 Generate a new key by running the following command: # ssh-keygen -t dsa 3 You will be prompted to enter the directory where the key should be saved. Press Enter to accept the default directory: Enter file in which to save the key (/root/.ssh/id_dsa): Press [Enter] key 4 Press the Enter key when prompted for a passphrase. If you create a passphrase the installation will fail: Enter passphrase (empty for no passphrase): Press [Enter] key Enter same passphrase again: Press [Enter] key Your identification has been saved in /root/.ssh/id_dsa. Your public key has been saved in /root/.ssh/id_dsa.pub. The key fingerprint is: 04:be:15:ca:1d:0a:1e:e2:a7:e5:de:98:4f:b1:a6:01 root@aavrach-queen 5 Change to the directory where your key file was created: # cd.ssh 6 Copy your DSA key file to authorized_keys to make it an SSH authorized key: # cat id_dsa.pub >> authorized_keys 7 Change the permissions on the authorized key file: # chmod 600 authorized_keys or # chmod og-rwx authorized_keys 8 Proceed to Copy the SSH Key to All Nodes on page 55. Copy the SSH Key to All Nodes 1 Log in as root on the machine that has the SSH key you want to use. 2 To make sure the key file works, issue an SSH command to localhost: # ssh localhost date If you are asked to confirm, type yes and press Enter. The command should then succeed without prompting for a password. 3 Make sure the worker and loader nodes are powered on and booted into their OS. 4 Change the working directory to your home directory on the machine with the SSH key: # cd 5 Copy the key file to each of the Aster Database nodes by running the following command, specifying the IP address of the node to which you are copying the key: # scp -pr.ssh root@<node-ip>: If you are asked to confirm, type yes and press Enter. If you are prompted for a password, enter it. 6 Verify that you can SSH to each worker and loader node without a password. # ssh <target-machine-ip> Aster Database Installation and Upgrade Guide 55

56 Installing Aster Backup Installing Aster Backup # exit 7 Test the passwordless connections among all nodes by connecting via SSH from each of the nodes to all the other nodes. If you are asked to confirm, type yes and press Enter. 8 If you wish to do so, you may disable passwordless SSH for the root user after installation and addition of all nodes is completed. Installation Procedure Log in as root on the machine that will be the Backup Manager. 1 Locate the Aster Backup installation bundle, ncluster-backup-upgrade.tar. 2 Decompress the installation bundle by issuing this command: # tar -xvf ncluster-backup-upgrade.tar This produces these files: backup-sw.tar.gz install_backup.py install_backup_node.py tc_backup_x86_64.tar.gz 3 Save these files to a single directory on the Backup Manager. You need not place these files on the Backup Node machines, but the machine you place them on must have network connectivity to all machines that will be Backup Nodes. Notice! Do not place the installer files in the /tmp directory of a machine that will be a Backup Node! In addition, remote backup installation cannot be done to the Backup Manager. 4 Log in as root and change directories to the directory where the installer files are located, and run the installation script with the following options: # install_backup.py <command> -m <backup_mgr_ip> -n "<backup_node1_ip> <backup_node2_ip>..." -p <installer_pkg_dir> where <Mgr-IP> is the IP address of the machine that will be Backup Manager, <Node1-IP> is the address of the first Backup Node (this is typically the same machine you designated as Backup Manager), <Node2-IP> is the address of the next Backup Node, and so on. For example: # install_backup.py install -m n " " -p. 5 Answer Y when prompted. If the installer prompts you for the root password, enter it. Note: Installation should be run as the root user. Unless passwordless root SSH is enabled between the Backup Manager and the Backup Nodes, the installer will prompt for the root password of the Backup Nodes. Passwordless SSH for the beehive user should be present. 6 After the installation completes, the Backup Manager and Backup Nodes processes are started automatically, and you will see a message that installation was successful. 56 Aster Database Installation and Upgrade Guide

57 Installing Aster Backup Installing Aster Backup If the installation was unsuccessful, see Backup Install Problems on page Verify that the Backup cluster has been installed: a Log in to the Backup Manager as beehive. b c Change directories: $ cd /home/beehive/bin/exec Type ncluster_backup, passing the -h flag followed by the IP address or DNS name of the Backup Manager: $ ncluster_backup -h <backup_mgr_ip> 8 You may optionally add ncluster_backup to your path for the beehive user. Note! When installing Aster Backup, you do not provide information about the location of your Aster Database. The location of your cluster is needed only at runtime, when you create or restore a backup. You can use your Backup cluster with multiple different Aster Databases. Other Installation Options Installing a Single-Node Backup Cluster To install just the Backup Manager and use it as the sole Backup Node: # install_backup.py install -m <backup_mgr_ip> -n <backup_mgr_ip> -p <installer_pkg_dir> Changing the Environment Settings Made by Backup On each Backup Node, Aster Backup software makes the following changes to enable faster backups: vm.dirty_background_ratio=1 (default is 5 or 10). This forces the writes from the page cache to disk to happen sooner, helping keep a steady flow of dirty data to disk. vm.dirty_ratio=50 (default is 10-20). This number dictates when writes made by the application are made synchronous by the kernel. Given the write-intensive workload at the backup nodes, increasing this number makes backups run faster. nr_requests=4096 The nr_requests setting must be set on each device that houses a backup data partition. This setting relates to the number of concurrent I/O requests sent to the device. You should set this based on the number of disk spindles on the Backup Node. For a typical Backup Node with many spindles, Teradata Aster has found that a setting of 4096 results in fast backups. 1 To view the current settings, for Linux, type: $ sysctl <variable> For example, issuing: $ sysctl vm.dirty_background_ratio displays $ vm.dirty_background_ratio=10 2 To change the settings, type: Aster Database Installation and Upgrade Guide 57

58 Installing Aster Backup Upgrading Aster Backup $ sysctl -w <variable>=<value> For example: $ sysctl -w vm.dirty_background_ratio=1 3 To make these changes permanent, modify the file /etc/sysctl.conf. 4 To apply the changes to /etc/sysctl.conf immediately, issue: $ sysctl -p Uninstalling Aster Backup You can use the install_backup.py script to uninstall Aster Backup and clean up existing backups. The syntax to uninstall is: #./install_backup.py uninstall -m <backup_mgr_ip> -p <installer_pkg_dir> Here is an example: #./install_backup.py uninstall -m p. The uninstall command automatically removes Aster Backup from all Backup Nodes and from the Backup Manager. The uninstall command only removes backups stored in /home/ beehive/data. If you have backups stored in any other directory, you will need to remove them manually (this includes all backups, files related to backup, and the.metadata file). If the uninstall fails, check for the script NClusterDataController.py in the /tmp directory on all of the Backup Nodes and remove it, if found. Uninstall will fail if the script NClusterDataController.py with root permissions is present in the /tmp directory on any of the Backup Nodes. Upgrading Aster Backup To upgrade Aster Backup on an Aster Appliance, see Upgrade the Aster Backup Cluster on page 92. To upgrade Aster Backup on commodity hardware, see Upgrade the Aster Backup Cluster on page Aster Database Installation and Upgrade Guide

59 CHAPTER 6 Upgrading the Aster Database on an Aster Appliance Upgrading replaces the Aster Database software and leaves your data in place. These instructions explain how to upgrade from version 6.00.xx.xx of the Aster Database to version 6.10 of the Aster Database. These are the only versions of the Aster Database that you can upgrade from directly. To upgrade from another version, you must upgrade first to 6.00.xx.xx, and then perform a second upgrade to See Supported Indirect Upgrades on page 62 or the Aster Database Release Notes, version 6.10 for details. Tip! Run all commands in the upgrade procedure as root or another operating system user with full administrative privileges. Tip! Consider doing the following for commands in the upgrade procedure where appropriate: 1 To save the output of shell commands for later review, you may want to nohup them. This will not work for ACT or psql commands, however you may want to redirect their output to a file. 2 Run commands in the background, so they will continue to execute if your connection drops. For example, if you choose to do both of these, the command: # ncli database backupmetadata would become: # nohup ncli database backupmetadata & Contents of this chapter include: Early Planning for Upgrading the Aster Database on an Aster Appliance Component Upgrade Matrix Upgrade Paths Pre-Upgrade Procedures Upgrade Procedure Post-Upgrade Procedures Upgrade Backup Cluster and Aster Clients Common Procedures Aster Database Installation and Upgrade Guide 59

60 Upgrading the Aster Database on an Aster Appliance Early Planning for Upgrading the Aster Database on an Aster Appliance Configure the Browser to Trust the AMC Certificate Early Planning for Upgrading the Aster Database on an Aster Appliance This section provides information on these topics, which are mandatory as part of the upgrade of the Aster Database on an Aster Appliance: Data/System Privilege/Authentication Preparation Data Redistribution Preparation Data/System Privilege/Authentication Preparation Tasks associated with Data Redistribution Preparation on page 60 must be run by the internal database administrator (_bee_sysman) with the default password set to _bee_sysman. To avoid permission-related errors during redistribution, it is required to temporarily reset the password for the internal database administrator (_bee_sysman) to _bee_sysman. The data redistribution involves performing privileged operations including: Changing metadata Creating and populating new copies of redistributable tables from the originals After redistribution is complete, the _bee_sysman password must be changed back to your password. Data Redistribution Preparation A new hash function is introduced in AD6.10, and, as part of the post-upgrade procedure, the ncli system redistributefacttables command brings all the tables in line with the new hash function by updating the metadata of all tables and redistributing rows of tables that are distributed on a column of these data types: VARCHAR NUMERIC The ncli system redistributefacttables command performs the update of the metadata very quickly, but the redistribution of rows for the tables distributed on the data types listed above can be very long running (several hours). You must understand the impact of the redistributefacttables procedure as you plan your upgrade. Obtain the redistributioninfo script from SB 768, which is located at Teradata@Your Service ( This script is a python script, which helps you plan your upgrade maintenance window. It is run on your AD6.00 cluster in a queen node before the actual upgrade and will compute and display metrics to help estimate the time it will take to perform the redistributefacttables procedure. 60 Aster Database Installation and Upgrade Guide

61 Upgrading the Aster Database on an Aster Appliance Component Upgrade Matrix SB 768, also provides a pre check utility script, redistributionprecheck, to check for several known issues that can cause problems during the redistribution step. It is also run on your AD6.00 cluster in a queen node, typically from the same location as the redistributioninfo script. All issues found by the utility must be resolved before upgrading. Resolving the known issues will help towards a smoother run of the data redistribution operation. Component Upgrade Matrix This table shows what Aster Database components you must upgrade when you upgrade your cluster to 6.10 from various earlier releases: Table 6-1: Component Upgrade Matrix Component ACT Client Secondary Queen Aster Database Backup Cluster Aster Database Export Aster Database Loader SQL-MapReduce SDK SQL-Graph SDK JDBC driver ODBC driver.net driver Aster Database Analytic Foundation Aster Developer Express When upgrading from any version: Upgrade required Upgrade required Upgrade required Upgrade recommended* Upgrade required Upgrade required Upgrade required Upgrade recommended* Upgrade recommended* Upgrade recommended* No upgrade available. The Analytics Foundation is a separate distribution. Upgrade required * See the Aster Database Drivers and Utilities Support Matrix for backwards compatibility of clients and utilities. Upgrade Paths Supported Direct Upgrades Clusters that Run on the Appliance You can upgrade directly to a recommended version of the 6.10 release of the Aster Database if your cluster runs version 6.00 or on the appliance. As part of this upgrade process, you Aster Database Installation and Upgrade Guide 61

62 Upgrading the Aster Database on an Aster Appliance Obtaining Installation Files will also need to redistribute preexisting data on the cluster. Work with your Account Team to order the recommended base version of the Aster 6.10 software for the Appliance. Supported Indirect Upgrades If your cluster is running one of the Aster Database versions listed in this section, you must perform an indirect, multi-hop upgrade. Work with your Account Team to order the recommended software for your specific upgrade path Notice: It is highly recommended to back up all of your data before doing any upgrade. Because of this, in the case where you will be performing an upgrade that involves two or more hops, you should perform a backup before each upgrade. This will minimize the number of steps you need to backtrack in case of power failure, network or hardware failure, or anything else that might disrupt an upgrade. For indirect upgrades, follow the instructions in the documentation for each release when upgrading to that release. If you wish to upgrade from a release that is not listed, contact Teradata Global Technical Support (GTS) for the upgrade path to follow. For Upgrades from 5.10.xx.xx You must perform a two hop upgrade, and then redistribute preexisting data on the cluster: 1 Upgrade to 6.00 or Upgrade to the recommended version of the 6.10 release of the Aster Database 3 Redistribute Preexisting Data on the Cluster For Upgrades from You must perform a three hop upgrade, and then redistribute preexisting data on the cluster: 1 Upgrade to 5.10.xx.xx 2 Upgrade to 6.00 or Upgrade to the recommended version of the 6.10 release of the Aster Database 4 Redistribute Preexisting Data on the Cluster Obtaining Installation Files An Aster Database major release includes significant new features and enhancements, as well as changes incorporated from earlier versions. Upgrading to a major release involves moving to a new base version of the Aster Database and all associated patches. Work with your Account Team to order the new base version of the Aster software for either the Appliance or commodity hardware. The Aster software will contain the required base installation files, along with these dependency files, in order to perform the Aster Installation: cliv noarch.rpm 62 Aster Database Installation and Upgrade Guide

63 Upgrading the Aster Database on an Aster Appliance Obtaining Installation Files tdicu noarch.rpm TeraGSS_linux_x noarch.rpm tptbase noarch.rpm The Teradata At Your Service website, is an additional resource that is available to customers and Teradata employees. This is a secure site from which you can access Orange Books, technical alerts, and knowledge repositories; view and join forums; and download software packages and documentation. The following files are required to perform this installation of the Aster Database. They should be put in the /var/opt/teradata directory on your cluster: Ensure that all required files for a specified version of an installation are located in a single directory and that a separate directory is used for each subsequent version of required installation files. NOTE: The ADE files will not be included beyond the AD6.10 release. They can be downloaded for free through the Teradata Developer Exchange website, Required files: ADE-linux.gtk.x86_64.tar.gz ADE-linux.gtk.x86.tar.gz ADE-macosx.cocoa.x86.tar.gz ADE-plugin-only.zip ADE-win32.win32.x86.zip aster-clients-linux r x86_64.rpm aster-db-common r x86_64.rpm aster-db-config-common r x86_64.rpm aster-db-config-redhat r x86_64.rpm aster-db-config-suse r x86_64.rpm aster-db-coordinator r x86_64.rpm aster-db-loader r x86_64.rpm aster-db-pkg r x86_64.rpm aster-db-toolchain r x86_64.rpm aster-db-worker r x86_64.rpm cliv noarch.rpm tdicu noarch.rpm TeraGSS_linux_x noarch.rpm tptbase noarch.rpm The TDput installer package compatible with your installed operating system. To install this release of the Aster Database, the minimum required version of TDput is: For Appliances running a supported version of the TD-SLES operating system: TDput or later SLES11 build for appliance. Aster Database Installation and Upgrade Guide 63

64 Upgrading the Aster Database on an Aster Appliance Pre-Upgrade Procedures Pre-Upgrade Procedures 1 Before upgrading, verify that your Teradata Account Representative has placed the order for the software version to which you are upgrading. Work with your Teradata Customer Service Representative to confirm the approval of your requested task. The Professional Support Team will ensure all necessary files and dependency patches are downloaded from the Teradata Software Server (TSS) ahead of the upgrade date. Some items like Aster Analytics and Aster Lens may require approvals before they can be downloaded. 2 Notice: Teradata operating system package upgrades do not include the upgrade of the Aster Database and should be considered ahead of the Aster Database upgrade. 3 Notice: The amount of downtime required to perform the upgrade procedure will vary based on many site-specific factors. Contact Teradata Global Technical Support (GTS) for assistance with estimating the time needed to perform your specific upgrade procedure. 4 For appliance upgrades, check for an existing Teradata Change Control order for this upgrade. Make note of all items to be upgraded. There may be items such as Aster Analytics or Aster Lens that are to be upgraded. If so, after you complete the Aster Database upgrade, follow the upgrade procedures in the documentation for those other products. 5 If there is no existing Teradata Change Control order for this upgrade, request that the Customer Service Representative or Account team create one. 6 Obtain information on any Service Bulletins that will need to be implemented: For customers who are performing their own upgrade, work with your Teradata Customer Service Representative to obtain information on Service Bulletins that will need to be implemented as part of your upgrade procedure. For internal Teradata personnel, use the Customer Services Knowledge Search website, to locate Service Bulletins that will need to be implemented as part of the upgrade procedure. 7 Notify all Aster Database users in the organization in advance that there will be a scheduled outage for system maintenance. Notice: The amount of downtime required to perform the upgrade procedure will vary based on many site-specific factors. Contact Teradata Global Technical Support (GTS) for assistance with estimating the time needed to perform your specific upgrade procedure. 8 The minimum hardware and operating system requirements for this Aster Database upgrade on an Aster Appliance are: Hardware Operating System Operating System Version Kernel Version Appliance 2 Teradata SLES 11 SP Aster Database Installation and Upgrade Guide

65 Upgrading the Aster Database on an Aster Appliance Pre-Upgrade Procedures Hardware Operating System Operating System Version Kernel Version Appliance 3 and 3H Teradata SLES 11 SP1.41 Appliance 4 Teradata SLES 11 SP1.41 Appliance 5 Teradata SLES 11 SP1.53 Notice: This release will NOT work with any previous versions of Teradata SLES 11 SP1 kernels. You MUST first install TDC.R1, or a later version when available, and then upgrade to AD Contact Teradata Global Technical Support (GTS) to obtain an operating system upgrade to this version on Teradata Aster Appliance cluster(s). 9 Check the Release Notes for Aster Database 6.10 for the latest information on this release. 10 Ensure that you are upgrading from 6.00.xx.xx on the Teradata Aster MapReduce Appliance. If you are attempting an upgrade on any other combination of release/os/ platform, contact Teradata Global Technical Support (GTS). 11 Determine whether LDAP is configured by viewing the contents of the file /home/beehive/config/beehiveparams.cfg in order to gather LDAP information needed for upgrading. If LDAP is configured, you ll need to verify that LDAP is working after upgrade. If LDAP is configured, you ll see parameters set similar to this example: ldap_port=389 ldap_prefix=asterdata ldap_server=ldapserver.asterdata.local ldap_suffix=tls 12 Determine if other components besides Aster Database need to be upgraded. Some components require an upgrade, while others are optional. Consult the Early Planning for Upgrading the Aster Database on an Aster Appliance on page 60 for more information on suggested components to upgrade. Typically these will include: Backup Manager Backup Nodes Client-side tools. For example: JDBC/ODBC drivers ACT Keep a list of these other components, so that you can upgrade them after the Aster Database upgrade procedure has been completed. Procedures for upgrading these components are located in their respective documentation. 13 Ensure that any Teradata and third party tools you use to access Aster Database are compatible with the version you are upgrading to. You can see a list of supported versions in the Aster Database Drivers and Utilities Support Matrix. Depending on compatibility, you may decide to defer the upgrade or to upgrade the client tools to the required version. Note Teradata Studio or newer is required with Aster Database Run the following command on the queen to ensure that the pgpass file is preserved: Aster Database Installation and Upgrade Guide 65

66 Upgrading the Aster Database on an Aster Appliance Pre-Upgrade Procedures ncli node runonall "cp p /home/beehive/bin/utils/init/pgpass /var/opt/teradata/pgpass_backup" 15 Before performing your upgrade, run the following utility to check the consistency of metadata. If an inconsistency is detected, fix it before proceeding to your upgrade. /home/beehive/bin/utils/support/postupgradecatalogchecks.py 16 IMPORTANT: Analytic Tables were introduced in Aster Database version Any upgrade will cause all Analytic Tables to lose their data and become invalid. Instructions on repopulating these tables are in the Aster Database User Guide. However, repopulating the tables creates a snapshot of the data at the time the tables are repopulated. If you need to retain the Analytic Tables with the data they hold pre-upgrade, you must perform a logical backup on each analytic table before upgrading and restore the tables after upgrading. Next Step: Proceed to Remove Ghost Security Patch by Restoring Original glibc Package. Remove Ghost Security Patch by Restoring Original glibc Package When upgrading to version 6.10.x of the Aster Database on a cluster that previously had the Ghost security patch installed, you must ensure that the Ghost security patch is removed before performing the Aster Database upgrade. The Ghost security patch is removed by restoring the original glibc package. To restore the original glibc package (in order to remove the Ghost security patch) when you are performing an upgrade to version 6.10.x of the Aster Database on a cluster that previously had the Ghost security patch installed, follow this procedure: 1 (Optional) To verify that a cluster already has the Ghost security patch installed, run this command on the queen: # ncli node runonall 'rpm -qa grep aster-db-libc-patch-1-2' 2 Before performing an upgrade to version 6.10.x of the Aster Database, run this command on every node in the cluster in order to restore the original glibc package, which will remove the Ghost security patch: # rpm -e aster-db-libc-patch-1-2 If, after running the command, this error message is returned, then the Ghost security patch is not installed and you can continue with the upgrade without taking further action to restore the original glibc package: error: package aster-db-libc-patch-1-2 is not installed Next Step: Proceed to Check for These Blocker Conditions. Check for These Blocker Conditions 1 Disk Full Conditions Check for disk full conditions by issuing: # ncli node runonall df -h 66 Aster Database Installation and Upgrade Guide

67 Upgrading the Aster Database on an Aster Appliance Pre-Upgrade Procedures If any disk is over 70% full, free up space before proceeding with the upgrade. 2 Ensure that the Aster Database is running with a replication factor of two (RF=2). To do this, issue: # ncli sysman showrf Replication Factor Tier Name Target RF Current RF queen-tier 2 2 default rows If the Current RF is not 2, you must correct this before upgrading. Next Step: Proceed to Check Cluster and OS Settings. Check Cluster and OS Settings 1 Verify that passwordless root SSH is enabled on all nodes. If necessary, enable it by issuing: # ncli sshkeys enable -n <IP1,IP2,...> Note that when specifying multiple node IP addresses using the -n option, they must be separated by a comma only, without spaces. 2 Verify that the max open files is at least and is identical on all worker nodes. To do this, issue: # ncli node runonall ulimit -a If you change the OS configuration parameter that specifies the maximum number of open files, you do not need to restart the server or the cluster at this time. The cluster is restarted later in the procedure, so the configuration change will take effect at that time. 3 If you have /usr/bin in your path, you must reposition it so that it comes after the Aster Database toolchain paths, which begin with /home/beehive. Otherwise, an incorrect version of Python may be used during the upgrade. To check the current PATH settings, you can echo the PATH in the current shell session: # echo $PATH # /home/beehive/bin/utils/primitives:/home/beehive/toolchain/x86_64- unknown-linux-gnu/<aster_version>/bin:/home/beehive/clients:/usr/ local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/root/bin All paths starting with /home/beehive (these are the Aster Database toolchain paths ) should come before the /usr/bin path. Next Step: Proceed to Back Up Data and Files. Aster Database Installation and Upgrade Guide 67

68 Upgrading the Aster Database on an Aster Appliance Pre-Upgrade Procedures Back Up Data and Files 1 To disallow users from running queries, follow the steps in Block User Queries on page Check for locks on user tables by issuing one of these commands: # ncli usertable checklocks --dbname <dbname> OR # ncli usertable checklocks --all-database 3 (Optional) Run a VACUUM FULL on the system catalogs, user tables, or both, before backing up the data. Vacuuming before backing up the database can improve the speed of the backup and restore operations. Additionally, vacuuming the system catalogs can potentially speed up the overall upgrade time, although in most cases this has minimal impact to the overall upgrade time. All VACUUM operations must complete successfully before backing up any database. If you vacuum the user tables, you can choose which tables and which databases to vacuum. For example, you can vacuum only a few bloated tables, or you can vacuum every table in every database. VACUUM FULL operations can take a long time if there is a lot of data or a lot of dead space in the tables. To VACUUM, run a VACUUM FULL from ACT while logged in as _bee_sysman. As an alternative, you can use the ncli catalog vacuumfull command and the ncli usertable vacuumfull command, which are documented in the Aster Database User Guide. 4 Use Aster Database Backup to make a full physical backup of the cluster. Note that a full physical backup of the cluster does not include the backup of Analytic tables. Notice: Teradata recommends backing up all of your data before performing any upgrade. You will not be able to restore backups taken with a previous version of Aster Backup after upgrading. If you do not wish to lose previous backups, do one of the following before upgrading Aster Backup: Archive your backups before upgrading Backup Manager. Do a clean install of Backup Manager on another machine for use with Aster Database 6.10 only. Older backups are not compatible with Version 6.10 of Backup Manager. 5 Back up any custom scripts from the queen or workers to your local file system. 68 Aster Database Installation and Upgrade Guide

69 Upgrading the Aster Database on an Aster Appliance Pre-Upgrade Procedures If you have saved custom scripts stored in the filesystem of the Aster Database queen or other nodes, these files will be lost in the upgrade. Copy any such files from the cluster to your local filesystem before you upgrade. 6 Back up any SQL-MapReduce binaries and source code files that are not installed in the database, because they might get deleted. Installed SQL-MapReduce functions will be upgraded automatically, but any SQL-MapReduce binaries or source code that is not installed should be backed up. 7 Back up the AppCenter in case the Aster Database upgrade runs into issues and a full physical backup needs to be restored. The procedure to restore a full physical backup deletes data on all nodes before the restore takes place. This means that the AppCenter, or at least parts of it, will also get deleted. While the AppCenter s data resides in one of Aster s databases (for example, the /data folder), its metadata resides in its own Postgres instance. The restore of the full physical backup might not affect the AppCenter metadata, but it could wipe out apps when Aster is removed before starting the restore process. Taking a backup of AppCenter will back up metadata in its Postgres instance and also the apps. This is why Teradata recommends taking a backup. You do not need to be concerned about the AppCenter s user data (for example, visualization tables) because they are created in the Aster database and will be restored from the full physical backup. The AppCenter installs that are at risk are the ones on the loader node. The installs on the backup queen are less likely to be affected when full physical backups are restored. Nonetheless, backing up AppCenter before the Aster upgrade will help. The AppCenter s admin password is required to perform the back up. Save the backup to /root or to /opt because these two folders are not affected when Aster is removed (before restore). Next Step: Proceed to Record Database State for Post-Upgrade Validation. Record Database State for Post-Upgrade Validation Collect the table row counts using the procedure in View Row Counts for Each Table on page 96. Next Step: Proceed to Save Custom Settings. Save Custom Settings Save Custom Settings to Refer to After Upgrade After upgrading, you can use the files you ll save in this section as a reference for the settings you had before upgrading. If any of these settings were not carried over after upgrading, you can look at the files you saved and manually apply any custom setting to the new files. Do not Aster Database Installation and Upgrade Guide 69

70 Upgrading the Aster Database on an Aster Appliance Pre-Upgrade Procedures overwrite the new files with these old files after upgrading! Often the format/syntax in these files changes, so overwriting the new files can cause issues. 1 Back up and remove any custom profiles in Postgres. If you have changed any settings in the Postgres configuration files (usually this is only done if instructed to do so by Teradata Global Technical Support (GTS)), you will need to back up those files that have been modified. Custom profiles are not upgraded when upgrading Aster Database. If they are present, they will cause the upgrade to fail. If you want to continue using them after upgrading, you ll have to make a note of the settings, remove them, perform the upgrade, and then reapply the settings manually after the upgrade is complete. These files are located here: a b /primary/queendb-0/postgresql.conf on the queen /home/beehive/modelworker/postgresql.conf on the queen (this is the template file that is used to create the custom profile on new workers when they are added to the cluster). c /primary/w<vworker_id>z/postgresql.conf on the workers 2 Save any custom PATH settings on the queen. If you have edited the PATH variable on your queen, save those edits. You will need to reference them after the upgrade process completes. 3 Back up the /etc/ntp.conf file on the queen, workers and loaders. You must restore this file after completing the upgrade. 4 Back up these files on the queen (required), workers and loaders (if changed): a /etc/hosts b /etc/resolv.conf These files are not touched during upgrade. You are only making a copy as a backup. Under normal circumstances, these backups will not be used. 5 Back up the files in these directories: a b c /home/beehive/config/procmgmtconfigs/*.* on the queen, workers, and loaders. /home/beehive/config/profiles/*/*.* on the queen /home/beehive/certs on the queen, if this directory exists d all certificates, if any, in the /home/beehive/data directory on the queen 6 Back up these files: a /data/ncluster/queendb-0/pg_hba.conf on the queen b /data/ncluster/w<vworker_id>z/pg_hba.conf on the workers 7 If you have LDAP enabled, save any associated certificates. If necessary, check with your LDAP Administrator to find out the name and location of the certificate file(s). 70 Aster Database Installation and Upgrade Guide

71 Upgrading the Aster Database on an Aster Appliance Pre-Upgrade Procedures Next Step: Proceed to Quiesce the Aster Database Cluster. Quiesce the Aster Database Cluster Note: If you have not already quiesced the cluster, ensure that you do so now. 1 Notify users that the scheduled outage is beginning, and that they should log off of the Aster Database system. 2 Check to ensure there are no pending processes or running queries. To see if there are any, log in to the AMC and select Processes > Processes. A list of pending processes and running and completed queries will display. Allow all pending processes and running queries to complete. 3 As a reminder, to disallow users from running queries, follow the steps in Block User Queries on page 96. Next Step: Proceed to Clear Prepared Transactions and Initiate Replication. Clear Prepared Transactions and Initiate Replication 1 Run the steadystatechecks command, to ensure that you can safely restart the cluster: # ncli database steadystatechecks If the output shows pending DROP DATABASE operations, see If steadystatechecks Continues to Detect Pending DROP DATABASE Operations on page 151. The steadystatechecks command writes its output to standard out. If the cluster is ready to upgrade, the output will end with a message indicating that you may proceed with the upgrade. The message differs depending upon the state of the cluster, but will be similar to: Summary Result No pending "DROP DATABASE" operations or prepared transactions detected. Please proceed with the upgrade If you see an output that contains a table with results like the following example, the cluster is not ready to upgrade: Worker Aster 6.10 Upgrade Check Result w4z Prepared Transactions Detected w7z Pending "DROP DATABASE" operations Not Detected w7z Prepared Transactions Not Detected w3z Prepared Transactions Detected w6z Pending "DROP DATABASE" operations Not Detected Aster Database Installation and Upgrade Guide 71

72 Upgrading the Aster Database on an Aster Appliance Pre-Upgrade Procedures w6z Prepared Transactions Not Detected queendb Pending "DROP DATABASE" operations Not Detected queendb Prepared Transactions Not Detected w5z Pending "DROP DATABASE" operations Not Detected w5z Prepared Transactions Not Detected w2z Prepared Transactions Detected queendb-1 Prepared Transactions Detected rows Summary Result Pending "DROP DATABASE" operations or prepared transactions were detected. Re-run this test until no pending "DROP DATABASE" operations are detected. After that, restart and re-activate the cluster. Re-run this test and ensure it passes before proceeding with the upgrade If there are still pending transactions, you must wait for them to complete, then run the steadystatechecks command again until it outputs a message that ends with Please proceed with the upgrade. Do not attempt to upgrade a cluster until the steadystatechecks command returns an all clear status as indicated by a message ending in Please proceed with the upgrade. You may need to run the steadystatechecks command a few times, which is normal. 2 Shutdown and reboot the cluster by issuing these commands: Shutdown the cluster: # ncli system softshutdown Reboot the queen: # /sbin/reboot After the queen comes back, reboot the workers and loader nodes: # ncli node runonother /sbin/reboot 3 Ensure the cluster has started up successfully by issuing: # ncli system show root@perf-c profiles]# ncli system show System Status Value State Cluster State Up Incorporation State -- Backup Status Log into the AMC again, and click on the Admin tab. The workers status will go from New to Preparing to Upgrading to Prepared. 72 Aster Database Installation and Upgrade Guide

73 Upgrading the Aster Database on an Aster Appliance Pre-Upgrade Procedures 5 Verify that all workers have come up as Prepared. If any nodes fail to come up as Prepared, you should repair them now. For example, if a hard disk fails, swap the disk, reconstruct the RAID array, and bring up the node. Repeat this until all workers come up as Prepared. 6 Activate the cluster. Do this by clicking on the Activate Cluster button in the Admin > Cluster Management tab of the AMC. Once the cluster is Active, check that its current replication factor ( RF ) matches its target replication factor. To check this, open the AMC and look at the Dashboard tab, in the Nodes section. In the Replication Factor field, you should see a line like this: Replication Factor: 2 (target: 2) If the current RF and target RF are not the same, you must fix the failed nodes and activate the cluster again. 7 As a reminder, to disallow users from running queries, follow the steps in Block User Queries on page 96. Next Step: Proceed to Run the ncli Pre-Upgrade Commands. Run the ncli Pre-Upgrade Commands 1 Run the backupmetadata command: # ncli database backupmetadata The backupmetadata command creates a directory on each node. The directory name is appended with the current timestamp. All the Postgres dump files for that node are written into this directory. After running the backupmetadata command, the following directories will be created on the queen and worker nodes: On the queen: /home/beehive/data/metadata_catalog_dumps/savedpgdumpdata- <suffix timestamp>-queendb/ On the worker nodes: /home/beehive/data/metadata_catalog_dumps/savedpgdumpdata- <suffix timestamp>-<vworker_instance>/ The contents in these directories are pg_dump files of every metadata schema for every database in the queen or vworker instance. For example, on the queen node and on each vworker instance in the cluster, the directory created will include files like the following: beehive_bee_logical_partitions.dump beehive_bee_special.dump... template1_nc_system.dump template1_pg_catalog.dump template1_pg_toast.dump 2 Run the steadystatechecks command: # ncli database steadystatechecks Aster Database Installation and Upgrade Guide 73

74 Upgrading the Aster Database on an Aster Appliance Upgrade Procedure If the output shows no pending DROP DATABASE operations, you may continue to the next checklist step, even if it indicates that prepared transactions exist. There is a chance that pending DROP DATABASE operations may reappear in the output of steadystatechecks. If this happens, follow the procedure in Block User Queries on page 96 and then run it again. If the output still shows pending DROP DATABASE operations, see If steadystatechecks Continues to Detect Pending DROP DATABASE Operations on page 151. Next Step: Proceed to Upgrade Procedure. Upgrade Procedure This upgrade procedure describes how to upgrade the Aster Database in an existing Aster Database installation using the files you downloaded in Obtaining Installation Files on page 62. Preparation For systems running a version of the Teradata SLES operating system: Verify that these packages are installed: libasound libstdc++.so.6 net-snmp (requires installation of perl-snmp) Ensure that all nodes to be included in the cluster contain the same /etc/hosts file with correct and complete information. PUT and ncli both use /etc/hosts files to group nodes and to add workers and loaders. Verify that version 1.6 or 1.7 of Java is installed on the computer that will be used to connect to PUT. PUT does not currently support a connection from a computer running Java version 1.8. Procedure Perform these steps to upgrade a cluster using the Parallel Upgrade Tool (PUT): Information on using Teradata's Parallel Upgrade Tool (PUT) is documented in the Parallel Upgrade Tool (PUT) Reference Guide. This guide is available on the Teradata Information Products website: 1 Select a machine to be the PUT master node. The master node: 74 Aster Database Installation and Upgrade Guide

75 Upgrading the Aster Database on an Aster Appliance Upgrade Procedure Is typically the coordinator of the cluster. Must be located on the same network as all machines in the cluster. Hosts the software RPM files to be installed on the cluster. 2 Install PUT on all nodes in the cluster including the secondary queen (optional depending on your configuration) and the PUT master node (if it is not a node in the cluster). a b Determine if PUT is installed on the node by issuing this command: rpm -qa grep TDput If TDput-xxxx is returned, PUT is installed on the node. Issue the /etc/init.d/ TDput start command to start TDput services and then continue on to Step 3 or, if you want to upgrade the installed version of PUT, continue to Step b. If TDput-xxxx is not returned, PUT is not installed on the node. Continue on to Step b. To perform an initial installation of TDput on nodes enabled with root ssh: Information on using Teradata's Parallel Upgrade Tool (PUT) is documented in the Parallel Upgrade Tool (PUT) Reference Guide. This guide is available on the Teradata Information Products website: i ii iii iv v Execute this command on the queen in the cluster: rpm -Uvh TDput*.rpm Open a supported web browser. Enter the URL for the system in the browser bar. Typically, this is or When the PUT Logon screen appears: Enter the root ID and password for the node to which you are connecting. Select Teradata Support Mode (QuickLook ID). Enter a valid, active QuickLook ID. Run the PUT install and upgrade operation in order to install PUT on the remaining nodes in the cluster. Refer to the Parallel Upgrade Tool (PUT) Reference Guide for information about running the PUT install and upgrade operation. c To upgrade an existing installation of TDput, run the PUT install and upgrade operation in order to upgrade all the nodes at the same time. Refer to the Parallel Upgrade Tool (PUT) Reference Guide for information about running the PUT install and upgrade operation. 3 Connect to PUT from a web browser. You can connect to PUT using either an HTTP or HTTPS connection. To start PUT from a web browser: a b c Open a supported web browser. Enter the URL for the system in the browser bar. Typically, this is the master node of the queen, or When the PUT Logon screen appears: Aster Database Installation and Upgrade Guide 75

76 Upgrading the Aster Database on an Aster Appliance Upgrade Procedure i ii If a window opens asking if you want to run the TDput Loader application, click Run. Enter the root ID and password for the node to which you are connecting. iii If you have a valid, active Teradata QuickLook ID, select Teradata Support Mode (QuickLook ID), and enter a valid, active QuickLook ID. 4 Upgrade the Aster Database software using PUT. For detailed information on using PUT to perform an upgrade, or information on common PUT install and upgrade software steps, refer to the Install/Upgrade Software Section in the Parallel Upgrade Tool (PUT) Reference Guide. The subset of topics listed in this step are intended to supplement the detailed information available under the corresponding topics in the Install/Upgrade Software Section in the Parallel Upgrade Tool (PUT) Reference Guide, and provide information specific to an Aster Database software upgrade. Detailed information on using Teradata's Parallel Upgrade Tool (PUT) is documented in the Parallel Upgrade Tool (PUT) Reference Guide. This guide is available on the Teradata Information Products website: a On the PUT interface screen, click Install/Upgrade Software. b Configuration Mode - Select Typical. Click Next. 76 Aster Database Installation and Upgrade Guide

77 Upgrading the Aster Database on an Aster Appliance Upgrade Procedure c d Network Subnet - Select the subnet on which all nodes in the cluster reside. Click Next. Find All Subnets - Select the subnet that corresponds to the cluster s subnet. Click Next. This action can take several minutes to complete, and returns the IP address of all nodes on the subnet or the name of the nodes. e Select Nodes - Select the queen (including the secondary queen IP address if applicable), worker and loader nodes in the cluster from the Available list. Click >> to move them to the Selected list. Click Next. If all nodes in the cluster do not have a shared subnet, select the subnet on which the nodes you want to install are located; multiple runs of the TDput operation will be required. Aster Database Installation and Upgrade Guide 77

78 Upgrading the Aster Database on an Aster Appliance Upgrade Procedure f TVI Discovery - Use the default value, 0. Click Next. 78 Aster Database Installation and Upgrade Guide

79 Upgrading the Aster Database on an Aster Appliance Upgrade Procedure g Select Spool Area - In the Select Spool Area For Linux Nodes screen, select the default location. Click Next. h Media Sources -In the Enter Source For New Packages screen, browse to the source for the RPM packages downloaded in Step 3, click Next. Aster Database Installation and Upgrade Guide 79

80 Upgrading the Aster Database on an Aster Appliance Upgrade Procedure In the Media Source Confirmation screen, use the default selections indicated on the screen. Click Next. In the Media Sources To Be Scanned screen, click Next. 80 Aster Database Installation and Upgrade Guide

81 Upgrading the Aster Database on an Aster Appliance Upgrade Procedure i Group Nodes - TDput will recognize the existing cluster and group structure (including the queen, secondary queen if applicable, worker, and loader nodes.) The structure will appear as two systems. One with the queen, workers, and loader. And another with the secondary queen. This representation has no effect on the package installation. It is just a visual representation by TDput of the cluster layout. j Select Packages - The Select Packages screen lists the nodes and the software package and version that will be upgraded on your system. Accept the software package installation recommendations by clicking Next and then proceed to Step k on page I-83. Aster Database Installation and Upgrade Guide 81

82 Upgrading the Aster Database on an Aster Appliance Upgrade Procedure If the nodes and software packages are not auto selected, perform this procedure to select the software packages: In the Select Packages screen, associate the package with the group on which it should be installed. For each group: i Select the appropriate package name for the node type: For the Queen (the primary and, if applicable, the secondary), select aster-dbcoordinator version For the worker group, select aster-db-worker version For the loader group, select aster-db-loader version ii iii In the Modify screen, select the group onto which the package should be installed. Click Next, which will open the Install/Upgrade Software: Package Dependencies Exist screen. Ensure that you do not click the Select All option. iv In the Install/Upgrade Software: Package Dependencies Exist screen, scroll through the list and verify that the package status for every package under the Status column indicates either: If, instead of the Install/Upgrade Software: Package Dependencies Exist screen, the Package Dependencies Not Met screen opens, ensure that the necessary software packages are properly installed and then restart the procedure. Installed (in black text) Available but not selected for upgrade (in blue text) Available but not selected for upgrade - version specific (in blue text). 82 Aster Database Installation and Upgrade Guide

83 Upgrading the Aster Database on an Aster Appliance Upgrade Procedure k v vi If the package status for every package under the Status column is correct, click Yes. This action will return you to the Select Packages screen. In the Select Packages screen, click Next. Confirm Package Selections - In the Confirm Package Selections screen, verify that the packages to be installed, and the number of nodes that each package will be installed on are correct. Click Next. l m Distribute Packages - No user interaction required. The time for this step to complete is dependent on the size of the packages. Begin Install? - In the Begin Install? screen, click Next. n Package Install - In the Package Install screen, click Next. This step will take time to complete. In the Overall Package Install Results screen, verify that all packages were installed successfully. Click Next. Aster Database Installation and Upgrade Guide 83

84 Upgrading the Aster Database on an Aster Appliance Upgrade Procedure o Pause for Change Control Activities - This step provides an intentional pause to perform any change control activities. Click Next. p Finished! - This step completes the upgrade. Click Finish to complete the operation prior to performing another PUT operation. 84 Aster Database Installation and Upgrade Guide

85 Upgrading the Aster Database on an Aster Appliance Upgrade Procedure 5 After completing the PUT upgrade operation, you must update the ~/.profile or the ~/.bashrc file for the root users in order to automatically source the asterenv.sh file and then you must log out and log back in. To perform this action: a b c d Locate and open either of these files: ~/.profile or ~/.bashrc In the opened file, copy and paste this text as a single line into the file: [ -f /home/beehive/config/asterenv.sh ] &&. /home/beehive/config/ asterenv.sh Save the file and exit the editor. Exit out of your current terminal window. e Open and log in to a new terminal window. If you did not perform steps a and b above, you will need to manually "source" the asterenv.sh file by executing this line each time you log in:. /home/beehive/config/asterenv.sh 6 Start the cluster by issuing this command: ncli system softstartup Alternatively, you can use the AMC to start the cluster, but doing so will shut down the system before restarting. Refer to the Add New Nodes to the Cluster topic under the Cluster Expansion section in the Aster Database User Guide for information on using the AMC to start the cluster. 7 Verify that the status of all nodes is active or prepared by issuing this command: ncli node show Alternatively, you can use the AMC to show the status of the node. Refer to the Add New Nodes to the Cluster topic under the Cluster Expansion section in the Aster Database User Guide for information on using the AMC to show the status of the node. 8 For the Secondary Queen Only. Aster services do not need to be started on the secondary queen. To stop Aster services from starting up automatically on reboot of the secondary Queen: Aster Database Installation and Upgrade Guide 85

86 Upgrading the Aster Database on an Aster Appliance Post-Upgrade Procedures a b Log in to the secondary queen, as root. Stop Aster services from starting up when the machine boots by issuing this command: # chkconfig local off. 9 Optional - Stop the TDput services by issuing this command on all nodes in the cluster: # /etc/init.d/tdput stop 10 Activate the cluster by issuing this command: ncli system activate Alternatively, you can use the AMC to activate the cluster. Refer to the Activate Aster Database topic under the Cluster Expansion section in the Aster Database User Guide for information on using the AMC to show the status of the node. Next Step: Proceed to Post-Upgrade Procedures. Post-Upgrade Procedures Restore Pre-Upgrade Settings If you saved any configuration files before upgrading (from the section Save Custom Settings to Refer to After Upgrade on page 69), you should manually merge those with the new files of the same name on the upgraded cluster to reapply any settings that were lost in the upgrade. This section covers that procedure. If you did not save any configuration files before upgrading, you may skip this section. 1 Shutdown the server before performing this procedure. 2 Reapply the custom Postgres profiles, if necessary. For clusters that use custom Postgres profiles, you must reapply the custom profiles after upgrading, but before activating, the cluster. To do this, redefine the new Postgres profiles manually using the settings in the custom profiles you saved before upgrading. As a reminder, these files are located here: a b c /primary/queendb-0/postgresql.conf on the queen /primary/modelworker/postgresql.conf on the queen (this is the template file that is used to create the custom profile on new workers when they are added to the cluster). /primary/w<vworker_id>z/postgresql.conf on the workers 3 Review the PATH settings you saved, and reapply any custom settings that were lost during the upgrade of Aster Database. 4 Restore the /etc/ntp.conf file on the queen, workers and loaders. 5 Restore the files in the directory /home/beehive/certs 6 Compare the pre-upgrade saved file from /data/ncluster/queendb-0/pg_hba.conf (on queen and workers) with the same file that exists post-upgrade. If there are custom settings that did not survive the upgrade, you should apply them manually to the new file. 86 Aster Database Installation and Upgrade Guide

87 Upgrading the Aster Database on an Aster Appliance Post-Upgrade Procedures 7 Compare the settings in these directories with the saved ones, and manually copy over any settings that you want to apply to the upgraded cluster: /home/beehive/config/procmgmtconfigs/* (on the queen, workers, and loaders) /home/beehive/config/profiles/* (on the queen) 8 If you use connectors, such as TD connector or Hadoop connector, check that they are working before you restore QoS to its original setting and start running queries again. 9 Restore any SQL-MapReduce binaries or source files you saved. 10 Use SSH to get into the node where AppCenter is installed and verify that it is working properly by logging into the user interface. Ensure that you are able to log in successfully and see installed apps. If you cannot, reinstall AppCenter and restore the backup. 11 Restore any custom scripts or other files you saved. 12 If LDAP was configured on the cluster before starting the upgrade procedure, the LDAPrelated entries in the file pg_hba.conf are commented out during the upgrade process. After the upgrade is completed, you must de-comment these entries to enable LDAP. 13 Test all connectivity to external devices. Next Step: If you created custom functions before upgrading, proceed to Recovering Custom SQL-MR Functions. Otherwise, proceed to Restart Aster Database. Recovering Custom SQL-MR Functions If you created custom functions before upgrading, follow the procedure below to recover them after upgrading. 1 Set up your Java Eclipse development environment. a b Download Eclipse: Set up development ADC plugin for Eclipse. Instructions can be found in the Aster Developer Guide. 2 Import the source files into Eclipse. a Go to File > Import and point the wizard at the source code.zip. 3 Edit the.java file to reflect any desired changes. 4 Export the file as a.jar and upload to the cluster. a Export as a.jar: Aster Database Installation and Upgrade Guide 87

88 Upgrading the Aster Database on an Aster Appliance Post-Upgrade Procedures b Select the source code and assign a file name ending with.jar. Under JAR file, enter C:\Users\<some folder>\jarfiles\<nameofcustomsqlmrfunction>.zip. 88 Aster Database Installation and Upgrade Guide

89 Upgrading the Aster Database on an Aster Appliance Post-Upgrade Procedures Next Step: Proceed to Restart Aster Database. Restart Aster Database 1 If the Restore Pre-Upgrade Settings procedure was performed and the server is not yet restarted, do so now. 2 Run the steadystatechecks command again, to ensure that you can safely restart the cluster: # ncli database steadystatechecks If the output shows no pending DROP DATABASE operations, you may continue to the next checklist step, even if it indicates that prepared transactions exist. There is a chance that pending DROP DATABASE operations may reappear in the output of steadystatechecks. If this happens, see If steadystatechecks Continues to Detect Pending DROP DATABASE Operations on page Shutdown and reboot the cluster by issuing these commands: a b Shutdown the cluster: # ncli system softshutdown Reboot the queen: # /sbin/reboot c After the queen completes rebooting, reboot the workers and loader nodes: # ncli node runonother /sbin/reboot 4 Ensure the cluster has started up successfully by issuing: # ncli system show 5 The status of the nodes should go from New to Preparing to Upgrading to Prepared after a few minutes. Then the status of the loader nodes will go to Active. This may take anywhere from a few minutes to more than an hour. 6 If after this, the status of the worker nodes does not change to Prepared, restart the cluster again, by clicking the Soft Restart button and clicking OK. Wait for the status to change to Prepared. Next Step: Proceed to Activate Aster Database. Activate Aster Database After the worker nodes show a status of Prepared and the queen and loader nodes show as Active, you may activate the cluster. Click the Admin tab, click the Activate Cluster button and click OK in the confirmation window. The cluster should begin activating and its status should change from Stopped to Activating and finally to Active. Once the cluster status is Active and the status of all nodes is Active, the cluster upgrade is complete and the cluster is ready to run processes. Aster Database Installation and Upgrade Guide 89

90 Upgrading the Aster Database on an Aster Appliance Post-Upgrade Procedures Next Step: Proceed to Test your Cluster. Test your Cluster 1 Verify that all nodes have the new, upgraded version of Aster Database by issuing the following command on the queen: # ncli node runonall cat /home/beehive/bin/.build 2 To allow user queries, which is necessary for running diagnostic tests, you must re-enable user queries. To re-enable user queries for upgrades from 6.00.xx.xx, see Re-enable User Queries on page Run the Aster Database Diagnostic Tests Suite on the queen: a b Log in to ACT as _bee_sysman, create a dummy table, and drop it. This will issue a COMMIT on all vworkers. This first COMMIT may take a long time to complete. This is normal. Subsequent queries will be faster: # act -U _bee_sysman -w <_bee_sysman_pwd> beehive=> CREATE TABLE foo (id int, label varchar) DISTRIBUTE BY HASH (id); CREATE TABLE beehive=> DROP TABLE foo; DROP TABLE beehive=> COMMIT; Check if a user database called "sanitytest_db" exists by issuing \l. If "sanitytest_db" does exist, the Diagnostic Tests Suite should not be run. Quit ACT by issuing \q If sanitytest_db" does not exist, quit ACT by issuing \q, and then change directories and run the diagnostic tests: # cd /home/beehive/bin/utils/diagnostictests # time./testrunner.py -f BasicSanityTestSuite.conf c Contact Teradata Global Technical Support (GTS) if there are any test failures reported. 4 Collect the table row counts using the procedure View Row Counts for Each Table on page 96. Compare the counts to the ones you collected pre-upgrade to ensure that nothing has changed. 5 You may also run any of your own internal diagnostic checks at this time, to verify the consistency of your data and ensure that database objects remain unchanged. Next Step: Proceed to Redistribute Preexisting Data on the Cluster. Redistribute Preexisting Data on the Cluster A hash function distributes the data for distributed tables across all partitions in a cluster. As part of the upgrade process, all tables will be migrated to use the hash function using the ncli system redistributefacttables utility command. 90 Aster Database Installation and Upgrade Guide

91 Upgrading the Aster Database on an Aster Appliance Post-Upgrade Procedures The ncli system redistributefacttables utility command updates the partitioning scheme to use the hash function for all tables. In addition, ncli system redistributefacttables redistributes the data to the correct partitions for tables to comply with the hash function. Therefore, it is mandatory to run the ncli system redistributefacttables command after upgrading. Depending on the number of tables that require redistribution, this step can be a very long running operation for a particular cluster. For more information, contact your Customer Service Representative and refer to the redistributeinfo Tech Alert. To perform the data reditribution operation: 1 Before proceeding, clear all existing Admission Limits. a b c Log in to the AMC as an administrator (such as db_superuser). From the menu, select Admin > Configuration > Admission Limits. Make note of the existing Admission Limits as you will need to restore them after the redistribute operation. d Locate any Admission Limits that were previously created, and select X to delete the Admission Limits. When prompted, Confirm deletion of the Admission Limits. 2 Execute the following commands at a queen command prompt: ncli system redistributefacttablescheck --nodryrun ncli system redistributefacttables The ncli system redistributefacttablescheck --nodryrun command verifies that there is enough free disk space to do the redistribution. The ncli system redistributefacttables command migrates all tables to use the hash function and redistribute the data of affected tables to their correct partitions. 3 Restore any Admission Limits that were cleared in Step 1. Refer to the Aster Database User Guide for information on using the ncli system redistributefacttables, ncli system redistributefacttablescheck, and ncli system redistributefacttablesstatus commands to migrate the tables. Next Step: Proceed to Disable Passwordless Root SSH. Disable Passwordless Root SSH If you will upgrade the Aster Backup cluster as described in Upgrade the Aster Backup Cluster on page 92, you can skip this step because passwordless root SSH must be enabled in order to upgrade the Aster Backup cluster. If not, once you are satisfied that your upgrade was successful, you can disable passwordless root SSH by issuing: # ncli sshkeys disable -n <IP1,IP2,...> Note that when specifying multiple node IP addresses using the -n option, they must be separated by a comma only, without spaces. Aster Database Installation and Upgrade Guide 91

92 Upgrading the Aster Database on an Aster Appliance Upgrade Backup Cluster and Aster Clients Next Step: Proceed to Add SQL-H Configurations. Add SQL-H Configurations A SQL-H configuration must be created for each Hadoop cluster you wish to access through SQL-H. This can be done through the AMC or using ncli. The procedure for creating a SQL-H configuration is documented in the Aster Database User Guide. Next Step: Proceed to Upgrade Backup Cluster and Aster Clients. Upgrade Backup Cluster and Aster Clients This section includes procedures for upgrading Aster Backup Cluster and Aster Clients. Complete the appropriate procedures for your environment: Upgrade the Aster Backup Cluster Upgrade ACT Upgrade ODBC and JDBC Drivers Upgrade Aster Loader Tool Re-Create TD Wallet Symbolic Link Upgrade Complete! Upgrade the Aster Backup Cluster You must upgrade the Aster Backup cluster. For appliances, failure to perform these actions will result in failure to automatically and accurately update Customer System Information (CSI) for the system when an Asset Baseline (ABL) is run, since the Aster software versions will be mismatched between the nodes. No Upgrade Path for Backup Manager You will not be able to restore backups taken with a previous version of Aster Backup after upgrading. The installer will remove all previous (older versions) backups. If you do not wish to lose previous backups, do one of the following before upgrading Aster Backup: Archive your backups before upgrading Backup Manager. Do a clean install of Backup Manager on another machine for use with Aster Database 6.10 only. Older backups are not compatible with Version 6.10 of Backup Manager. Upgrade Prerequisites Teradata Aster recommends these best practices for upgrading Aster Backup cluster: 92 Aster Database Installation and Upgrade Guide

93 Upgrading the Aster Database on an Aster Appliance Upgrade Backup Cluster and Aster Clients 1 Make disaster recovery archives: Before you upgrade Aster Backup, Teradata Aster recommends that you make disaster recovery archives of your old Aster Database data backups. 2 Plan to make new backups of critical tables: Aster Database does not support cross-version backups. Your pre-upgrade backup data is only usable on a pre-upgrade version of Aster Database. Since your existing backups will not be usable in the upgraded cluster, you should plan to make new backups of all critical tables soon after you finish the Aster Backup upgrade. 3 If your Aster Backup cluster runs on Teradata SLES 11 SP1 on an appliance, ensure that you are running a supported version of the kernel on the Backup Manager and all Backup Nodes. The supported versions of the kernel are: Hardware Operating System Operating System Version Kernel Version Appliance 2 Teradata SLES 11 SP1.41 Appliance 3 and 3H Teradata SLES 11 SP1.41 Appliance 4 Teradata SLES 11 SP1.41 Appliance 5 Teradata SLES 11 SP In order to upgrade, passwordless SSH must be set up and working for the users beehive and root between all nodes in the backup cluster. After upgrading, you may disable it, if you choose. Obtaining Installation File Work with your Account Team to obtain the correct version of the Aster Backup installation bundle, ncluster-backup-upgrade.tar for this release. This bundle contains these required files to install Aster Backup on the Backup cluster: backup-sw.tar.gz install_backup.py install_backup_node.py tc_backup_x86_64.tar.gz Upgrade Backup Cluster Procedure You can perform this installation from any Linux workstation that has Python installed and has access to the machines of your Backup cluster. 1 Locate the Aster Backup installation bundle, ncluster-backup-upgrade.tar. 2 Decompress the installation bundle by issuing this command: install_backup.py install_backup_node.py backup-sw.tar.gz tc_backup_x86_64.tar.gz Aster Database Installation and Upgrade Guide 93

94 Upgrading the Aster Database on an Aster Appliance Upgrade Backup Cluster and Aster Clients 3 Run the script install_backup.py with the following options, depending on what you want to upgrade. The -p flag specifies the path to the package to install, in these examples that path is the current working directory. Make sure to use the upgrade option, which causes the existing backup files to be left in place: To upgrade the entire Backup Cluster: $ python install_backup.py upgrade -m <Mgr-IP> -p. where <Mgr-IP> is the IP address of the Backup Manager. To upgrade only the backup nodes, if needed: $ python install_backup.py upgrade-nodes -n <bkp-nodes> -p. where <bkp-nodes> is a comma delimited list of the IP addresses of the Backup Nodes. Note: If passwordless root SSH is not enabled between the Backup Manager and the Backup Nodes, the installer will prompt for the root password of the Backup Nodes. 4 The upgrade script deletes any existing backups. It will display a message like: "Please be patient as the backups are being deleted". This message will be displayed only if there are previous backups. 5 If the upgrade is unsuccessful, see Backup Install Problems on page Once the script completes, verify that the cluster has been upgraded and then exit: a Launch the ncluster_backup CLI, passing the IP address or DNS name of the Backup Manager: $ ncluster_backup -h <Backup-Manager-IP> b At the command prompt, enter: $ exit 7 Make new backups of all critical tables now. Notice: Cross-version backups are not supported in Aster Database, so your existing backups are not usable in your new cluster! 8 After you are satisfied that your upgraded cluster and backup cluster are operating correctly, delete all pre-upgrade backups. Next Step: Proceed to Upgrade ACT. Upgrade ACT Depending on the version compatibility in the Aster Database Drivers and Utilities Matrix, you may need to upgrade Aster Database Terminal (ACT) on all workstations that are used to connect to the Aster Database. 94 Aster Database Installation and Upgrade Guide

95 Upgrading the Aster Database on an Aster Appliance Upgrade Backup Cluster and Aster Clients 1 Download the latest ACT executable from 2 Install the ACT client as explained in the Aster Client Guide. 3 To check the version after upgrading, type the ACT executable name with the --version flag. For example: $ act --version Next Step: Proceed to Upgrade ODBC and JDBC Drivers. Upgrade ODBC and JDBC Drivers Depending on the version compatibility in the Aster Database Drivers and Utilities Matrix, you may need to upgrade Aster ODBC and/or JDBC on all workstations that use to connect to Aster Database. 1 Download the latest Aster ODBC and/or JDBC client from 2 Install and configure ODBC/JDBC as explained in the Aster Client Guide. 3 Note that the Aster Database ODBC driver may change in any Aster Database release. For this reason, with each new edition of Aster Database, you should re-install the driver and re-compile your applications that include it. Tip! You can check the version of the Aster Database ODBC driver on a client machine by: On Linux, Solaris or MacOS: going to the ODBC driver installation directory and viewing the contents of the.deploy file, which lists the version and build number. This file can be found in a directory that has the form: /usr/local/lib/stage/clients-odbc-<your_os>/libs On Windows: looking in the Control Panel for Add Remove Programs or Programs and Features in the Version column for the Aster ODBC Driver. Next Step: Proceed to Upgrade Aster Loader Tool. Upgrade Aster Loader Tool If you use Aster Loader Tool (ncluster_loader), you must upgrade it now. Do this: 1 Download the latest Aster Loader Tool from 2 Install Aster Loader Tool as explained in the Aster Client Guide. Next Step: Proceed to Re-Create TD Wallet Symbolic Link. Re-Create TD Wallet Symbolic Link If you use TD Wallet, you need to recreate the symbolic link: Aster Database Installation and Upgrade Guide 95

96 Upgrading the Aster Database on an Aster Appliance Common Procedures 1 Change directories: # cd /home/beehive/clients_all/linux64 2 Recreate the symbolic link: # ln -s /opt/teradata/client/tdwallet tdwalletdir Next Step: Proceed to Upgrade Complete!. Upgrade Complete! Once you have upgraded the items above, your upgrade is complete. Refer to the Aster Database 6.10 Release Notes for important information about this version of Aster Database. Tip! Now is a good time to make sure all Aster Database users can get the client software updates they will need. On your internal software distribution server or wiki, add the new Aster Database clients and drivers so that all Aster Database users can download and install them. Common Procedures View Row Counts for Each Table Use this procedure before upgrading to obtain a row count for each table. After upgrading, use the pre-upgrade table counts you collected as a sanity check to make sure there were no changes during the upgrade. 1 Connect to ACT as db_superuser, and enter the password when prompted: # act -U db_superuser 2 Make a record of the names of all tables in all databases in your Aster cluster using the following SQL: SELECT relname, database, schema, object_type, table_type FROM nc_tablesize_details ( ON (SELECT 1) PARTITION BY 1 ) GROUP BY relname, database, schema, object_type, table_type; 3 Connect to each database: \c <dbname> 4 Make a record of the row count for each table in that database using the following SQL: SELECT COUNT(*) FROM <tablename>; 5 Repeat the last two steps until you have a list of table names and row counts of all tables in all databases. Block User Queries Use Admission Limits to block user queries: 96 Aster Database Installation and Upgrade Guide

97 Upgrading the Aster Database on an Aster Appliance Configure the Browser to Trust the AMC Certificate 1 Log in to the AMC as an administrator (such as db_superuser). 2 From the menu, select Admin > Configuration > Admission Limits. 3 Click the New Admission Limit button. 4 Fill in the admission limit information as follows: a b Provide a unique name such as "Block User Queries". Use username!= '_bee_sysman' for the predicate. c Set the concurrency limit to 0. d Click OK. Re-enable User Queries 5 Now queries from users other than _bee_sysman will fail with the error "Admission denied". Note that any transactions that are currently running will continue to execute unless they are individually cancelled. To undo the settings you made in the procedure Block User Queries on page 96 and bring the cluster back on-line: 1 Log in to the AMC as an administrator (such as db_superuser). 2 From the menu, select Admin > Configuration > Admission Limits. 3 Find the Admission Limit you created previously to block user queries in the list. 4 Click the X to delete it. Confirm deletion when prompted. Reinstall JCE to Support Kerberos If your Aster cluster is configured to connect to Hadoop clusters with Kerberos authentication and uses AES-256 encryption, JCE may need to be reinstalled on all nodes after installation. Refer to Java Cryptography Extension (JCE) Policy File Installation in the Aster Database User Guide. Configure the Browser to Trust the AMC Certificate The AMC runs using secure HTTP, at an https URL on the queen machine. To open the AMC, type and the IP address or hostname of your queen: IP Address> Your browser will display a notice stating that the connection is not trusted. This notice appears because the AMC connection is secured by Teradata Aster s self-signed digital certificate. You can configure your browser to trust this certificate so that the notice does not appear. To do this, follow the instructions in one of these sections: Configure Firefox to Trust the AMC Certificate Aster Database Installation and Upgrade Guide 97

98 Upgrading the Aster Database on an Aster Appliance Configure the Browser to Trust the AMC Certificate Configure Internet Explorer to Trust the AMC Certificate Configure Firefox to Trust the AMC Certificate 1 In Firefox, click the I understand the risks link. Figure 1: Firefox: Trusting the AMC certificate 2 Click the Add Exception button. Figure 2: Add Exception button in Firefox 3 In the next window, make sure the checkbox, Permanently store this exception, is checked. 4 Click the Confirm Security Exception button. Firefox will now trust the AMC certificate. Figure 3: Add Security Exception in Firefox 98 Aster Database Installation and Upgrade Guide

99 Upgrading the Aster Database on an Aster Appliance Configure the Browser to Trust the AMC Certificate Configure Internet Explorer to Trust the AMC Certificate 1 In the IE browser, you will see the message, There is a problem with this website s security certificate. Click Continue to this website. Figure 4: Continue to this website in Internet Explorer 2 The navigation bar appears in pink with the message, Certificate Error. Figure 5: Certificate Error in Internet Explorer 3 Click on the words, Certificate Error. Figure 6: Click on Certificate Error Aster Database Installation and Upgrade Guide 99

100 Upgrading the Aster Database on an Aster Appliance Configure the Browser to Trust the AMC Certificate 4 Click View Certificates. Figure 7: Install the certificate in Internet Explorer 5 Click Install Certificate. Internet Explorer will now trust the AMC certificate. 100 Aster Database Installation and Upgrade Guide

101 CHAPTER 7 Upgrading the Aster Database on Commodity Hardware Upgrading replaces the Aster Database software and leaves your data in place. These instructions explain how to upgrade from version 6.00.xx.xx of the Aster Database to version 6.10 of the Aster Database. These are the only versions of the Aster Database that you can upgrade from directly. To upgrade from another version, you must upgrade first to 6.00.xx.xx, and then perform a second upgrade to See Supported Indirect Upgrades on page 104 or the Aster Database Release Notes, version 6.10 for details. Tip! Run all commands in the upgrade procedure as root or another operating system user with full administrative privileges. Tip! Consider doing the following for commands in the upgrade procedure where appropriate: 1 To save the output of shell commands for later review, you may want to nohup them. This will not work for ACT or psql commands, however you may want to redirect their output to a file. 2 Run commands in the background, so they will continue to execute if your connection drops. For example, if you choose to do both of these, the command: # ncli database backupmetadata would become: # nohup ncli database backupmetadata & Contents of this chapter include: Early Planning for Upgrading the Aster Database on Commodity Hardware Component Upgrade Matrix Upgrade Paths Pre-Upgrade Procedures Upgrade Procedure Post-Upgrade Procedures Upgrade Backup Cluster and Aster Clients Common Procedures Aster Database Installation and Upgrade Guide 101

102 Upgrading the Aster Database on Commodity Hardware Early Planning for Upgrading the Aster Database on Commodity Hardware Configure the Browser to Trust the AMC Certificate Early Planning for Upgrading the Aster Database on Commodity Hardware This section provides information on these topics, which are mandatory as part of the upgrade of the Aster Database on commodity hardware: Data/System Privilege/Authentication Preparation Data Redistribution Preparation Data/System Privilege/Authentication Preparation Tasks associated with Data Redistribution Preparation on page 102 must be run by the internal database administrator (_bee_sysman) with the default password set to _bee_sysman. To avoid permission-related errors during redistribution, it is required to temporarily reset the password for the internal database administrator (_bee_sysman) to _bee_sysman. The data redistribution involves performing privileged operations including: Changing metadata Creating and populating new copies of redistributable tables from the originals After redistribution is complete, the _bee_sysman password must be changed back to your password. Data Redistribution Preparation A new hash function is introduced in AD6.10, and, as part of the post-upgrade procedure, the ncli system redistributefacttables command brings all the tables in line with the new hash function by updating the metadata of all tables and redistributing rows of tables that are distributed on a column of these data types: VARCHAR NUMERIC The ncli system redistributefacttables command performs the update of the metadata very quickly, but the redistribution of rows for the tables distributed on the data types listed above can be very long running (several hours). You must understand the impact of the redistributefacttables procedure as you plan your upgrade. Obtain the redistributioninfo script from SB 768, which is located at Teradata@Your Service ( This script is a python script, which helps you plan your upgrade maintenance window. It is run on your AD6.00 cluster in a queen node before the actual upgrade and will compute and display metrics to help estimate the time it will take to perform the redistributefacttables procedure. 102 Aster Database Installation and Upgrade Guide

103 Upgrading the Aster Database on Commodity Hardware Component Upgrade Matrix SB 768, also provides a pre check utility script, redistributionprecheck, to check for several known issues that can cause problems during the redistribution step. It is also run on your AD6.00 cluster in a queen node, typically from the same location as the redistributioninfo script. All issues found by the utility must be resolved before upgrading. Resolving the known issues will help towards a smoother run of the data redistribution operation. Component Upgrade Matrix This table shows what Aster Database components you must upgrade when you upgrade your cluster to 6.10 from various earlier releases: Table 7-1: Component Upgrade Matrix Component ACT Client Secondary Queen Aster Database Backup Cluster Aster Database Export Aster Database Loader SQL-MapReduce SDK SQL-Graph SDK JDBC driver ODBC driver.net driver Aster Database Analytic Foundation Aster Developer Express When upgrading from any version: Upgrade required Upgrade required Upgrade required Upgrade recommended* Upgrade required Upgrade required Upgrade required Upgrade recommended* Upgrade recommended* Upgrade recommended* No upgrade available. The Analytics Foundation is a separate distribution. Upgrade required * See the Aster Database Drivers and Utilities Support Matrix for backwards compatibility of clients and utilities. Upgrade Paths Supported Direct Upgrades Clusters that Run on Your Own Hardware: SLES You can upgrade directly to a recommended version of the 6.10 release of the Aster Database if your cluster runs version 6.00 or on the SUSE Linux Enterprise Server 11 SP2 operating system. As part of this upgrade process, you will also need to redistribute Aster Database Installation and Upgrade Guide 103

104 Upgrading the Aster Database on Commodity Hardware Upgrade Paths preexisting data on the cluster. Work with your Account Team to order the recommended base version of the Aster 6.10 software. Clusters that Run on Your Own Hardware: Red Hat You can upgrade directly to a recommended version of the 6.10 release of the Aster Database if your cluster runs version 6.00 or on the Red Hat 6.4 or 6.5 operating system. Upgrading requires that Red Hat 6.4 or 6.5 is already installed on the cluster. As part of this upgrade process, you will also need to redistribute preexisting data on the cluster. Work with your Account Team to order the recommended base version of the Aster 6.10 software. Supported Indirect Upgrades If your cluster is running one of the Aster Database versions listed in this section, you must perform an indirect, multi-hop upgrade. Work with your Account Team to order the recommended software for your specific upgrade path Notice: It is highly recommended to back up all of your data before doing any upgrade. Because of this, in the case where you will be performing an upgrade that involves two or more hops, you should perform a backup before each upgrade. This will minimize the number of steps you need to backtrack in case of power failure, network or hardware failure, or anything else that might disrupt an upgrade. For indirect upgrades, follow the instructions in the documentation for each release when upgrading to that release. If you wish to upgrade from a release that is not listed, contact Teradata Global Technical Support (GTS) for the upgrade path to follow. For Upgrades from 5.10.xx.xx You must perform a two hop upgrade, and then redistribute preexisting data on the cluster: 1 Upgrade to 6.00 or Upgrade to the recommended version of the 6.10 release of the Aster Database 3 Redistribute Preexisting Data on the Cluster For Upgrades from You must perform a three hop upgrade, and then redistribute preexisting data on the cluster: 1 Upgrade to 5.10.xx.xx 2 Upgrade to 6.00 or Upgrade to the recommended version of the 6.10 release of the Aster Database 4 Redistribute Preexisting Data on the Cluster 104 Aster Database Installation and Upgrade Guide

105 Upgrading the Aster Database on Commodity Hardware Download Required Software Download Required Software An Aster Database major release includes significant new features and enhancements, as well as changes incorporated from earlier versions. Upgrading to a major release involves moving to a new base version of the Aster Database and all associated patches. Work with your Account Team to order the new base version of the Aster software for either the Appliance or commodity hardware. The Aster software will contain the required base installation files, along with these dependency files, in order to perform the Aster Installation: cliv noarch.rpm tdicu noarch.rpm TeraGSS_linux_x noarch.rpm tptbase noarch.rpm The Teradata At Your Service (T@YS) website, is an additional resource that is available to customers and Teradata employees. This is a secure site from which you can access Orange Books, technical alerts, and knowledge repositories; view and join forums; and download software packages and documentation. The following files are required to perform this installation of the Aster Database. They should be put in the /var/opt/teradata directory on your cluster: Ensure that all required files for a specified version of an installation are located in a single directory and that a separate directory is used for each subsequent version of required installation files. NOTE: The ADE files will not be included beyond the AD6.10 release. They can be downloaded for free through the Teradata Developer Exchange website, Required files: ADE-linux.gtk.x86_64.tar.gz ADE-linux.gtk.x86.tar.gz ADE-macosx.cocoa.x86.tar.gz ADE-plugin-only.zip ADE-win32.win32.x86.zip aster-clients-linux r x86_64.rpm aster-db-common r x86_64.rpm aster-db-config-common r x86_64.rpm aster-db-config-redhat r x86_64.rpm aster-db-config-suse r x86_64.rpm aster-db-coordinator r x86_64.rpm aster-db-loader r x86_64.rpm aster-db-pkg r x86_64.rpm aster-db-toolchain r x86_64.rpm aster-db-worker r x86_64.rpm cliv noarch.rpm Aster Database Installation and Upgrade Guide 105

106 Upgrading the Aster Database on Commodity Hardware Pre-Upgrade Procedures tdicu noarch.rpm TeraGSS_linux_x noarch.rpm tptbase noarch.rpm The TDput installer package compatible with your installed operating system. To install this release of the Aster Database, the minimum required version of TDput is: For commodity hardware running a supported version of the Linux operating system (for example, SLES11 SP2 or Redhat 6.4 or 6.5): TDput or later non- Teradata OS build for commodity. The non-teradata OS build is for both Redhat and non-teradata SLES 11. Pre-Upgrade Procedures 1 Notice: The amount of downtime required to perform the upgrade procedure will vary based on many site-specific factors. Contact Teradata Global Technical Support (GTS) for assistance with estimating the time needed to perform your specific upgrade procedure. 2 Obtain information on any Service Bulletins that will need to be implemented: For internal Teradata personnel, use the Customer Services Knowledge Search website, to locate Service Bulletins that will need to be implemented as part of the upgrade procedure. 3 Ensure that the customer has notified all Aster Database users in their organization in advance that there will be a scheduled outage for system maintenance. Notice: The amount of downtime required to perform the upgrade procedure will vary based on many site-specific factors. Contact Teradata Global Technical Support (GTS) for assistance with estimating the time needed to perform your specific upgrade procedure. 4 Check the Release Notes for Aster Database 6.10 for the latest information on this release. Note that after each operating system upgrade, data from all data dictionary views with historical data is dropped. Data collection is re-enabled after the upgraded cluster is started. 5 Ensure that you are upgrading from 6.00.xx.xx on RHEL 6.4, RHEL 6.5 or SUSE Linux Enterprise Server 11 SP2 on commodity hardware. If you are attempting an upgrade on any other combination of release/os/platform, contact Teradata Global Technical Support (GTS). 6 Determine whether LDAP is configured by viewing the contents of the file /home/ beehive/config/beehiveparams.cfg in order to gather LDAP information needed for upgrading. If LDAP is configured, you ll need to verify that LDAP is working after upgrade. If LDAP is configured, you ll see parameters set similar to this example: ldap_port=389 ldap_prefix=asterdata ldap_server=ldapserver.asterdata.local 106 Aster Database Installation and Upgrade Guide

107 Upgrading the Aster Database on Commodity Hardware Pre-Upgrade Procedures ldap_suffix=tls 7 Determine if other components besides Aster Database need to be upgraded. Some components require an upgrade, while others are optional. Consult the Component Upgrade Matrix on page 103 for more information on suggested components to upgrade. Typically these will include: Backup Manager Backup Nodes Client-side tools. For example: JDBC/ODBC drivers ACT Keep a list of these other components, so that you can upgrade them after the Aster Database upgrade procedure has been completed. Procedures for upgrading these components are located in their respective documentation. 8 Ensure that any Teradata and third party tools you use to access Aster Database are compatible with the version you are upgrading to. You can see a list of supported versions in the Aster Database Drivers and Utilities Support Matrix. Depending on compatibility, you may decide to defer the upgrade or to upgrade the client tools to the required version. Note that Teradata Studio or newer is required with Aster Database Run the following command on the queen to ensure that the pgpass file is preserved: ncli node runonall "cp p /home/beehive/bin/utils/init/pgpass /var/opt/teradata/pgpass_backup" 10 Before performing your upgrade, run the following utility to check the consistency of metadata. If an inconsistency is detected, fix it before proceeding to your upgrade. /home/beehive/bin/utils/support/postupgradecatalogchecks.py 11 IMPORTANT: Analytic Tables were introduced in Aster Database version Any upgrade will cause all Analytic Tables to lose their data and become invalid. Instructions on repopulating these tables are in the Aster Database User Guide. However, repopulating the tables creates a snapshot of the data at the time the tables are repopulated. If you need to retain the Analytic Tables with the data they hold pre-upgrade, you must perform a logical backup on each analytic table before upgrading and restore the tables after upgrading. Next Step: Proceed to Remove Ghost Security Patch by Restoring Original glibc Package. Remove Ghost Security Patch by Restoring Original glibc Package When upgrading to version 6.10.x of the Aster Database on a cluster that previously had the Ghost security patch installed, you must ensure that the Ghost security patch is removed before performing the Aster Database upgrade. The Ghost security patch is removed by restoring the original glibc package. To restore the original glibc package (in order to remove the Ghost security patch) when you are performing an upgrade to version 6.10.x of the Aster Database on a cluster that previously had the Ghost security patch installed, follow this procedure: Aster Database Installation and Upgrade Guide 107

108 Upgrading the Aster Database on Commodity Hardware Pre-Upgrade Procedures 1 (Optional) To verify that a cluster already has the Ghost security patch installed, run this command on the queen: # ncli node runonall 'rpm -qa grep aster-db-libc-patch-1-2' 2 Before performing an upgrade to version 6.10.x of the Aster Database, run this command on every node in the cluster in order to restore the original glibc package, which will remove the Ghost security patch: # rpm -e aster-db-libc-patch-1-2 If, after running the command, this error message is returned, then the Ghost security patch is not installed and you can continue with the upgrade without taking further action to restore the original glibc package: error: package aster-db-libc-patch-1-2 is not installed Next Step: Proceed to Check for These Blocker Conditions. Check for These Blocker Conditions 1 Disk Full Conditions Check for disk full conditions by issuing: # ncli node runonall df -h If any disk is over 70% full, free up space before proceeding with the upgrade. 2 Ensure that the Aster Database is running with a replication factor of two (RF=2). To do this, issue: # ncli sysman showrf Replication Factor Tier Name Target RF Current RF queen-tier 2 2 default rows If the Current RF is not 2, you must correct this before upgrading. Next Step: Proceed to Check Cluster and OS Settings. Check Cluster and OS Settings 1 Verify that passwordless root SSH is enabled on all nodes. If necessary, enable it by issuing: # ncli sshkeys enable -n <IP1,IP2,...> Note that when specifying multiple node IP addresses using the -n option, they must be separated by a comma only, without spaces. 108 Aster Database Installation and Upgrade Guide

109 Upgrading the Aster Database on Commodity Hardware Pre-Upgrade Procedures 2 Verify that the max open files is at least and is identical on all worker nodes. To do this, issue: # ncli node runonall ulimit -a If you change the OS configuration parameter that specifies the maximum number of open files, you do not need to restart the server or the cluster at this time. The cluster is restarted later in the procedure, so the configuration change will take effect at that time. 3 If you have /usr/bin in your path, you must reposition it so that it comes after the Aster Database toolchain paths, which begin with /home/beehive. Otherwise, an incorrect version of Python may be used during the upgrade. To check the current PATH settings, you can echo the PATH in the current shell session: # echo $PATH # /home/beehive/bin/utils/primitives:/home/beehive/toolchain/x86_64- unknown-linux-gnu/<aster_version>/bin:/home/beehive/clients:/usr/ local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/root/bin All paths starting with /home/beehive (these are the Aster Database toolchain paths ) should come before the /usr/bin path. Next Step: Proceed to Back Up Data and Files. Back Up Data and Files 1 To disallow users from running queries, follow the steps in Install Kernel Patches on Red Hat on page Check for locks on user tables by issuing one of these commands: # ncli usertable checklocks --dbname <dbname> OR # ncli usertable checklocks --all-database 3 (Optional) Run a VACUUM FULL on the system catalogs, user tables, or both, before backing up the data. Vacuuming before backing up the database can improve the speed of the backup and restore operations. Additionally, vacuuming the system catalogs can potentially speed up the overall upgrade time, although in most cases this has minimal impact to the overall upgrade time. All VACUUM operations must complete successfully before backing up any database. If you vacuum the user tables, you can choose which tables and which databases to vacuum. For example, you can vacuum only a few bloated tables, or you can vacuum every table in every database. VACUUM FULL operations can take a long time if there is a lot of data or a lot of dead space in the tables. Aster Database Installation and Upgrade Guide 109

110 Upgrading the Aster Database on Commodity Hardware Pre-Upgrade Procedures To VACUUM, run a VACUUM FULL from ACT while logged in as _bee_sysman. As an alternative, you can use the ncli catalog vacuumfull command and the ncli usertable vacuumfull command, which are documented in the Aster Database User Guide. 4 Use Aster Database Backup to make a full physical backup of the cluster. Note that a full physical backup of the cluster does not include the backup of Analytic tables. Notice: Teradata recommends backing up all of your data before performing any upgrade. You will not be able to restore backups taken with a previous version of Aster Backup after upgrading. If you do not wish to lose previous backups, do one of the following before upgrading Aster Backup: Archive your backups before upgrading Backup Manager. Do a clean install of Backup Manager on another machine for use with Aster Database 6.10 only. Older backups are not compatible with Version 6.10 of Backup Manager. 5 Back up any custom scripts from the queen or workers to your local file system. If you have saved custom scripts stored in the filesystem of the Aster Database queen or other nodes, these files will be lost in the upgrade. Copy any such files from the cluster to your local filesystem before you upgrade. 6 Back up any SQL-MapReduce binaries and source code files that are not installed in the database, because they might get deleted. Installed SQL-MapReduce functions will be upgraded automatically, but any SQL-MapReduce binaries or source code that is not installed should be backed up. 7 Back up the AppCenter in case the Aster Database upgrade runs into issues and a full physical backup needs to be restored. The procedure to restore a full physical backup deletes data on all nodes before the restore takes place. This means that the AppCenter, or at least parts of it, will also get deleted. While the AppCenter s data resides in one of Aster s databases (for example, the /data folder), its metadata resides in its own Postgres instance. The restore of the full physical backup might not affect the AppCenter metadata, but it could wipe out apps when Aster is removed before starting the restore process. Taking a backup of AppCenter will back up metadata in its Postgres instance and also the apps. This is why Teradata recommends taking a backup. You do not need to be concerned about the AppCenter s user data (for example, visualization tables) because they are created in the Aster database and will be restored from the full physical backup. The AppCenter installs that are at risk are the ones on the loader node. The installs on the backup queen are less likely to be affected when full physical backups are restored. Nonetheless, backing up AppCenter before the Aster upgrade will help. 110 Aster Database Installation and Upgrade Guide

111 Upgrading the Aster Database on Commodity Hardware Pre-Upgrade Procedures The AppCenter s admin password is required to perform the back up. Save the backup to /root or to /opt because these two folders are not affected when Aster is removed (before restore). Next Step: Proceed to Record Database State for Post-Upgrade Validation. Record Database State for Post-Upgrade Validation Collect the table row counts using the procedure in View Row Counts for Each Table on page 139. Next Step: Proceed to Save Custom Settings. Save Custom Settings Save Custom Settings to Refer to After Upgrade After upgrading, you can use the files you ll save in this section as a reference for the settings you had before upgrading. If any of these settings were not carried over after upgrading, you can look at the files you saved and manually apply any custom setting to the new files. Do not overwrite the new files with these old files after upgrading! Often the format/syntax in these files changes, so overwriting the new files can cause issues. 1 Back up and remove any custom profiles in Postgres. If you have changed any settings in the Postgres configuration files (usually this is only done if instructed to do so by Teradata Global Technical Support (GTS)), you will need to back up those files that have been modified. Custom profiles are not upgraded when upgrading Aster Database. If they are present, they will cause the upgrade to fail. If you want to continue using them after upgrading, you ll have to make a note of the settings, remove them, perform the upgrade, and then reapply the settings manually after the upgrade is complete. These files are located here: a b /primary/queendb-0/postgresql.conf on the queen /home/beehive/modelworker/postgresql.conf on the queen (this is the template file that is used to create the custom profile on new workers when they are added to the cluster). c /primary/w<vworker_id>z/postgresql.conf on the workers 2 Save any custom PATH settings on the queen. If you have edited the PATH variable on your queen, save those edits. You will need to reference them after the upgrade process completes. 3 Back up these files on the queen (required), workers and loaders (if changed): a b /etc/hosts /etc/resolv.conf Aster Database Installation and Upgrade Guide 111

112 Upgrading the Aster Database on Commodity Hardware Pre-Upgrade Procedures These files are not touched during upgrade. You are only making a copy as a backup. Under normal circumstances, these backups will not be used. 4 Back up the files in these directories: a b c /home/beehive/config/procmgmtconfigs/*.* on the queen, workers, and loaders. /home/beehive/config/profiles/*/*.* on the queen /home/beehive/certs on the queen, if this directory exists d all certificates, if any, in the /home/beehive/data directory on the queen 5 Back up these files: a /data/ncluster/queendb-0/pg_hba.conf on the queen b /data/ncluster/w<vworker_id>z/pg_hba.conf on the workers 6 If you have LDAP enabled, save any associated certificates. If necessary, check with your LDAP Administrator to find out the name and location of the certificate file(s). Next Step: Proceed to Quiesce the Aster Database Cluster. Quiesce the Aster Database Cluster Note: If you have not already quiesced the cluster, ensure that you do so now. 1 Notify users that the scheduled outage is beginning, and that they should log off of the Aster Database system. 2 Check to ensure there are no pending processes or running queries. To see if there are any, log in to the AMC and select Processes > Processes. A list of pending processes and running and completed queries will display. Allow all pending processes and running queries to complete. 3 As a reminder, to disallow users from running queries, follow the steps in Install Kernel Patches on Red Hat on page 139. Next Step: Proceed to Clear Prepared Transactions and Initiate Replication. Clear Prepared Transactions and Initiate Replication 1 Run the steadystatechecks command, to ensure that you can safely restart the cluster: # ncli database steadystatechecks If the output shows pending DROP DATABASE operations, see If steadystatechecks Continues to Detect Pending DROP DATABASE Operations on page 151. The steadystatechecks command writes its output to standard out. If the cluster is ready to upgrade, the output will end with a message indicating that you may proceed with the 112 Aster Database Installation and Upgrade Guide

113 Upgrading the Aster Database on Commodity Hardware Pre-Upgrade Procedures upgrade. The message differs depending upon the state of the cluster, but will be similar to: Summary Result No pending "DROP DATABASE" operations or prepared transactions detected. Please proceed with the upgrade If you see an output that contains a table with results like the following example, the cluster is not ready to upgrade: Worker Aster 6.10 Upgrade Check Result w4z Prepared Transactions Detected w7z Pending "DROP DATABASE" operations Not Detected w7z Prepared Transactions Not Detected w3z Prepared Transactions Detected w6z Pending "DROP DATABASE" operations Not Detected w6z Prepared Transactions Not Detected queendb Pending "DROP DATABASE" operations Not Detected queendb Prepared Transactions Not Detected w5z Pending "DROP DATABASE" operations Not Detected w5z Prepared Transactions Not Detected w2z Prepared Transactions Detected queendb-1 Prepared Transactions Detected rows Summary Result Pending "DROP DATABASE" operations or prepared transactions were detected. Re-run this test until no pending "DROP DATABASE" operations are detected. After that, restart and re-activate the cluster. Re-run this test and ensure it passes before proceeding with the upgrade If there are still pending transactions, you must wait for them to complete, then run the steadystatechecks command again until it outputs a message that ends with Please proceed with the upgrade. Do not attempt to upgrade a cluster until the steadystatechecks command returns an all clear status as indicated by a message ending in Please proceed with the upgrade. You may need to run the command a few times, which is normal. 2 Shutdown and reboot the cluster by issuing these commands: Aster Database Installation and Upgrade Guide 113

114 Upgrading the Aster Database on Commodity Hardware Pre-Upgrade Procedures a b c Shutdown the cluster: # ncli system softshutdown Reboot the queen: # /sbin/reboot After the queen completes rebooting, reboot the workers and loader nodes: # ncli node runonother /sbin/reboot 3 Ensure the cluster has started up successfully by issuing: # ncli system show root@perf-c profiles]# ncli system show System Status Value State Cluster State Up Incorporation State -- Backup Status Log into the AMC again, and click on the Admin tab. The workers status will go from New to Preparing to Upgrading to Prepared. 5 Verify that all workers have come up as Prepared. If any nodes fail to come up as Prepared, you should repair them now. For example, if a hard disk fails, swap the disk, reconstruct the RAID array, and bring up the node. Repeat this until all workers come up as Prepared. 6 Activate the cluster. Do this by clicking on the Activate Cluster button in the Admin > Cluster Management tab of the AMC. Once the cluster is Active, check that its current replication factor ( RF ) matches its target replication factor. To check this, open the AMC and look at the Dashboard tab, in the Nodes section. In the Replication Factor field, you should see a line like this: Replication Factor: 2 (target: 2) If the current RF and target RF are not the same, you must fix the failed nodes and activate the cluster again. 7 As a reminder, to disallow users from running queries, follow the steps in Install Kernel Patches on Red Hat on page 139. Next Step: Proceed to Run the ncli Pre-Upgrade Commands. Run the ncli Pre-Upgrade Commands 1 Run the backupmetadata command: # ncli database backupmetadata The backupmetadata command creates a directory on each node. The directory name is appended with the current timestamp. All the Postgres dump files for that node are 114 Aster Database Installation and Upgrade Guide

115 Upgrading the Aster Database on Commodity Hardware Pre-Upgrade Procedures written into this directory. After running the backupmetadata command, the following directories will be created on the queen and worker nodes: On the queen: /home/beehive/data/metadata_catalog_dumps/savedpgdumpdata- <suffix timestamp>-queendb/ On the worker nodes: /home/beehive/data/metadata_catalog_dumps/savedpgdumpdata- <suffix timestamp>-<vworker_instance>/ The contents in these directories are pg_dump files of every metadata schema for every database in the queen or vworker instance. For example, on the queen node and on each vworker instance in the cluster, the directory created will include files like the following: beehive_bee_logical_partitions.dump beehive_bee_special.dump... template1_nc_system.dump template1_pg_catalog.dump template1_pg_toast.dump 2 Run the steadystatechecks command: # ncli database steadystatechecks If the output shows no pending DROP DATABASE operations, you may continue to the next checklist step, even if it indicates that prepared transactions exist. There is a chance that pending DROP DATABASE operations may reappear in the output of steadystatechecks. If this happens, follow the procedure in Install Kernel Patches on Red Hat on page 139 and then run it again. If the output still shows pending DROP DATABASE operations, see If steadystatechecks Continues to Detect Pending DROP DATABASE Operations on page 151. Next Step: Proceed to Restart and Activate the Cluster. Restart and Activate the Cluster 1 Soft restart the cluster: # ncli system softrestart 2 Activate the cluster: # ncli system activate Next Step: Proceed to Upgrade Procedure. Aster Database Installation and Upgrade Guide 115

116 Upgrading the Aster Database on Commodity Hardware Upgrade Procedure Upgrade Procedure This upgrade procedure describes how to upgrade the Aster Database in an existing Aster Database installation using the files you downloaded in Download Required Software on page 105. Preparation For systems running a version of the Red Hat Enterprise Linux operating system, verify that net-snmp is installed on all nodes. Ensure that all nodes to be included in the cluster contain the same /etc/hosts file with correct and complete information. PUT and ncli use /etc/hosts files to group nodes and to add workers and loaders. Verify that version 1.6 or 1.7 of Java is installed on the computer that will be used to connect to PUT. PUT does not currently support a connection from a computer running Java version 1.8. Procedure Perform these steps to upgrade a cluster using the Parallel Upgrade Tool (PUT): Information on using Teradata's Parallel Upgrade Tool (PUT) is documented in the Parallel Upgrade Tool (PUT) Reference Guide. This guide is available on the Teradata Information Products website: 1 Select a machine to be the PUT master node. The master node: Is typically the coordinator of the cluster. Must be located on the same network as all machines in the cluster. Hosts the software RPM files to be installed on the cluster. 2 Install PUT on all nodes in the cluster including the secondary queen (optional depending on your configuration) and the PUT master node (if it is not a node in the cluster). a Determine if PUT is installed on the node by issuing this command: rpm -qa grep TDput If TDput-xxxx is returned, PUT is installed on the node. Issue the /etc/init.d/ TDput start command to start TDput services and then continue on to Step 3 or, if you want to upgrade the installed version of PUT, continue to Step b. If TDput-xxxx is not returned, PUT is not installed on the node. Continue on to Step b. 116 Aster Database Installation and Upgrade Guide

117 Upgrading the Aster Database on Commodity Hardware Upgrade Procedure b c Obtain the correct TDput RPM file from the Teradata Software Server (TSS) at under the TDput directory. For commodity hardware running a supported version of the Linux operating system (for example, SLES11 SP2, RHEL 6.4 or RHEL 6.5) download the latest version of the TDput RPM file. For example, TDput/NonTD/TDput x86_64.rpm. To perform an initial installation of TDput on nodes enabled with root ssh: Information on using Teradata's Parallel Upgrade Tool (PUT) is documented in the Parallel Upgrade Tool (PUT) Reference Guide. This guide is available on the Teradata Information Products website: i ii iii iv v Execute this command on the queen in the cluster: rpm -Uvh TDput*.rpm Open a supported web browser. Enter the URL for the system in the browser bar. Typically, this is or When the PUT Logon screen appears: Enter the root ID and password for the node to which you are connecting. Select Teradata Support Mode (QuickLook ID). Enter a valid, active QuickLook ID. Run the PUT install and upgrade operation in order to install PUT on the remaining nodes in the cluster. Refer to the Parallel Upgrade Tool (PUT) Reference Guide for information about running the PUT install and upgrade operation. d To upgrade an existing installation of TDput, run the PUT install and upgrade operation in order to upgrade all the nodes at the same time. Refer to the Parallel Upgrade Tool (PUT) Reference Guide for information about running the PUT install and upgrade operation. 3 Connect to PUT from a web browser. You can connect to PUT using either an HTTP or HTTPS connection. To start PUT from a web browser: a b c Open a supported web browser. Enter the URL for the system in the browser bar. Typically, this is the master node of the queen, or When the PUT Logon screen appears: i ii If a window opens asking if you want to run the TDput Loader application, click Run. Enter the root ID and password for the node to which you are connecting. iii If you have a valid, active Teradata QuickLook ID, select Teradata Support Mode (QuickLook ID), and enter a valid, active QuickLook ID. Aster Database Installation and Upgrade Guide 117

118 Upgrading the Aster Database on Commodity Hardware Upgrade Procedure 4 Upgrade the Aster Database software using PUT. For detailed information on using PUT to perform an upgrade, or information on common PUT install and upgrade software steps, refer to the Install/Upgrade Software Section in the Parallel Upgrade Tool (PUT) Reference Guide. The subset of topics listed in this step are intended to supplement the detailed information available under the corresponding topics in the Install/Upgrade Software Section in the Parallel Upgrade Tool (PUT) Reference Guide, and provide information specific to an Aster Database software upgrade. Detailed information on using Teradata's Parallel Upgrade Tool (PUT) is documented in the Parallel Upgrade Tool (PUT) Reference Guide. This guide is available on the Teradata Information Products website: a On the PUT interface screen, click Install/Upgrade Software. b Configuration Mode - Select Typical. Click Next. 118 Aster Database Installation and Upgrade Guide

119 Upgrading the Aster Database on Commodity Hardware Upgrade Procedure c d Network Subnet - Select the subnet on which all nodes in the cluster reside. Click Next. Find All Subnets - Select the subnet that corresponds to the cluster s subnet. Click Next. This action can take several minutes to complete, and returns the IP address of all nodes on the subnet or the name of the nodes. e Select Nodes - Select the queen (including the secondary queen IP address if applicable), worker and loader nodes in the cluster from the Available list. Click >> to move them to the Selected list. Click Next. If all nodes in the cluster do not have a shared subnet, select the subnet on which the nodes you want to install are located; multiple runs of the TDput operation will be required. Aster Database Installation and Upgrade Guide 119

120 Upgrading the Aster Database on Commodity Hardware Upgrade Procedure f TVI Discovery - Use the default value, 0. Click Next. 120 Aster Database Installation and Upgrade Guide

121 Upgrading the Aster Database on Commodity Hardware Upgrade Procedure g Select Spool Area - In the Select Spool Area For Linux Nodes screen, select the default location. Click Next. h Media Sources -In the Enter Source For New Packages screen, browse to the source for the RPM packages downloaded in Step 3, click Next. Aster Database Installation and Upgrade Guide 121

122 Upgrading the Aster Database on Commodity Hardware Upgrade Procedure In the Media Source Confirmation screen, use the default selections indicated on the screen. Click Next. In the Media Sources To Be Scanned screen, click Next. 122 Aster Database Installation and Upgrade Guide

123 Upgrading the Aster Database on Commodity Hardware Upgrade Procedure i Group Nodes - TDput will recognize the existing cluster and group structure (including the queen, secondary queen if applicable, worker, and loader nodes.) The structure will appear as two systems. One with the queen, workers, and loader. And another with the secondary queen. This representation has no effect on the package installation. It is just a visual representation by TDput of the cluster layout. j Select Packages - The Select Packages screen lists the nodes and the software package and version that will be upgraded on your system. Accept the software package installation recommendations by clicking Next and then proceed to Step k on page I Aster Database Installation and Upgrade Guide 123

124 Upgrading the Aster Database on Commodity Hardware Upgrade Procedure If the nodes and software packages are not auto selected, perform this procedure to select the software packages: In the Select Packages screen, associate the package with the group on which it should be installed. For each group: i Select the appropriate package name for the node type: For the Queen (the primary and, if applicable, the secondary), select aster-dbcoordinator version For the worker group, select aster-db-worker version For the loader group, select aster-db-loader version ii iii In the Modify screen, select the group onto which the package should be installed. Click Next, which will open the Install/Upgrade Software: Package Dependencies Exist screen. Ensure that you do not click the Select All option. iv In the Install/Upgrade Software: Package Dependencies Exist screen, scroll through the list and verify that the package status for every package under the Status column indicates either: If, instead of the Install/Upgrade Software: Package Dependencies Exist screen, the Package Dependencies Not Met screen opens, ensure that the necessary software packages are properly installed and then restart the procedure. Installed (in black text) Available but not selected for upgrade (in blue text) Available but not selected for upgrade - version specific (in blue text). 124 Aster Database Installation and Upgrade Guide

125 Upgrading the Aster Database on Commodity Hardware Upgrade Procedure k v vi If the package status for every package under the Status column is correct, click Yes. This action will return you to the Select Packages screen. In the Select Packages screen, click Next. Confirm Package Selections - In the Confirm Package Selections screen, verify that the packages to be installed, and the number of nodes that each package will be installed on are correct. Click Next. l m Distribute Packages - No user interaction required. The time for this step to complete is dependent on the size of the packages. Begin Install? - In the Begin Install? screen, click Next. n Package Install - In the Package Install screen, click Next. This step will take time to complete. In the Overall Package Install Results screen, verify that all packages were installed successfully. Click Next. Aster Database Installation and Upgrade Guide 125

126 Upgrading the Aster Database on Commodity Hardware Upgrade Procedure o Pause for Change Control Activities - This step provides an intentional pause to perform any change control activities. Click Next. p Finished! - This step completes the upgrade. Click Finish to complete the operation prior to performing another PUT operation. 126 Aster Database Installation and Upgrade Guide

127 Upgrading the Aster Database on Commodity Hardware Upgrade Procedure 5 After completing the PUT upgrade operation, you must update the ~/.profile or the ~/.bashrc file for the root users in order to automatically source the asterenv.sh file and then you must log out and log back in. To perform this action: a b c d Locate and open either of these files: ~/.profile or ~/.bashrc In the opened file, copy and paste this text as a single line into the file: [ -f /home/beehive/config/asterenv.sh ] &&. /home/beehive/config/ asterenv.sh Save the file and exit the editor. Exit out of your current terminal window. e Open and log in to a new terminal window. If you did not perform steps a and b above, you will need to manually "source" the asterenv.sh file by executing this line each time you log in:. /home/beehive/config/asterenv.sh 6 Start the cluster by issuing this command: ncli system softstartup Alternatively, you can use the AMC to start the cluster, but doing so will shut down the system before restarting. Refer to the Add New Nodes to the Cluster topic under the Cluster Expansion section in the Aster Database User Guide for information on using the AMC to start the cluster. 7 Verify that the status of all nodes is active or prepared by issuing this command: ncli node show Alternatively, you can use the AMC to show the status of the node. Refer to the Add New Nodes to the Cluster topic under the Cluster Expansion section in the Aster Database User Guide for information on using the AMC to show the status of the node. 8 For the Secondary Queen Only. Aster services do not need to be started on the secondary queen. To stop Aster services from starting up automatically on reboot of the secondary Queen: Aster Database Installation and Upgrade Guide 127

128 Upgrading the Aster Database on Commodity Hardware Post-Upgrade Procedures a b Log in to the secondary queen, as root. Stop Aster services from starting up when the machine boots by issuing this command: # chkconfig local off. 9 Optional - Stop the TDput services by issuing this command on all nodes in the cluster: # /etc/init.d/tdput stop 10 Activate the cluster by issuing this command: ncli system activate Alternatively, you can use the AMC to activate the cluster. Refer to the Activate Aster Database topic under the Cluster Expansion section in the Aster Database User Guide for information on using the AMC to show the status of the node. Next Step: Proceed to Post-Upgrade Procedures. Post-Upgrade Procedures Restore Pre-Upgrade Settings If you saved any configuration files before upgrading (from the section Save Custom Settings to Refer to After Upgrade on page 111), you should manually merge those with the new files of the same name on the upgraded cluster to reapply any settings that were lost in the upgrade. This section covers that procedure. If you did not save any configuration files before upgrading, you may skip this section. 1 Shutdown the server before performing this procedure. 2 Reapply the custom Postgres profiles, if necessary. For clusters that use custom Postgres profiles, you must reapply the custom profiles after upgrading, but before activating, the cluster. To do this, redefine the new Postgres profiles manually using the settings in the custom profiles you saved before upgrading. As a reminder, these files are located here: a b c /primary/queendb-0/postgresql.conf on the queen /primary/modelworker/postgresql.conf on the queen (this is the template file that is used to create the custom profile on new workers when they are added to the cluster). /primary/w<vworker_id>z/postgresql.conf on the workers 3 Review the PATH settings you saved, and reapply any custom settings that were lost during the upgrade of Aster Database. 4 Restore the files in the directory /home/beehive/certs 5 Compare the pre-upgrade saved file from /data/ncluster/queendb-0/pg_hba.conf (on queen and workers) with the same file that exists post-upgrade. If there are custom settings that did not survive the upgrade, you should apply them manually to the new file. 6 Compare the settings in these directories with the saved ones, and manually copy over any settings that you want to apply to the upgraded cluster: 128 Aster Database Installation and Upgrade Guide

129 Upgrading the Aster Database on Commodity Hardware Post-Upgrade Procedures /home/beehive/config/procmgmtconfigs/* (on the queen, workers, and loaders) /home/beehive/config/profiles/* (on the queen) 7 If you use connectors, such as TD connector or Hadoop connector, check that they are working before you restore QoS to its original setting and start running queries again. 8 Restore any SQL-MapReduce binaries or source files you saved. 9 Use SSH to get into the node where AppCenter is installed and verify that it is working properly by logging into the user interface. Ensure that you are able to log in successfully and see installed apps. If you cannot, reinstall AppCenter and restore the backup. 10 Restore any custom scripts or other files you saved. 11 If LDAP was configured on the cluster before starting the upgrade procedure, the LDAPrelated entries in the file pg_hba.conf are commented out during the upgrade process. After the upgrade is completed, you must de-comment these entries to enable LDAP. 12 Test all connectivity to external devices. Next Step: If you created custom functions before upgrading, proceed to Recovering Custom SQL-MR Functions. Otherwise, proceed to Restart Aster Database. Recovering Custom SQL-MR Functions If you created custom functions before upgrading, follow the procedure below to recover them after upgrading. 1 Set up your Java Eclipse development environment. a b Download Eclipse: Set up development ADC plugin for Eclipse. Instructions can be found in the Aster Developer Guide. 2 Import the source files into Eclipse. a Go to File > Import and point the wizard at the source code.zip. 3 Edit the.java file to reflect any desired changes. 4 Export the file as a.jar and upload to the cluster. a Export as a.jar: Aster Database Installation and Upgrade Guide 129

130 Upgrading the Aster Database on Commodity Hardware Post-Upgrade Procedures b Select the source code and assign a file name ending with.jar. Under JAR file, enter C:\Users\<some folder>\jarfiles\<nameofcustomsqlmrfunction>.zip. 130 Aster Database Installation and Upgrade Guide

131 Upgrading the Aster Database on Commodity Hardware Post-Upgrade Procedures Next Step: Proceed to Restart Aster Database. Restart Aster Database 1 If the Restore Pre-Upgrade Settings procedure was performed and the server is not yet restarted, do so now. 2 Run the steadystatechecks command again, to ensure that you can safely restart the cluster: # ncli database steadystatechecks If the output shows no pending DROP DATABASE operations, you may continue to the next checklist step, even if it indicates that prepared transactions exist. There is a chance that pending DROP DATABASE operations may reappear in the output of steadystatechecks. If this happens, see If steadystatechecks Continues to Detect Pending DROP DATABASE Operations on page Shutdown and reboot the cluster by issuing these commands: a b Shutdown the cluster: # ncli system softshutdown Reboot the queen: # /sbin/reboot c After the queen completes rebooting, reboot the workers and loader nodes: # ncli node runonother /sbin/reboot 4 Ensure the cluster has started up successfully by issuing: # ncli system show 5 The status of the nodes should go from New to Preparing to Upgrading to Prepared after a few minutes. Then the status of the loader nodes will go to Active. This may take anywhere from a few minutes to more than an hour. 6 If after this, the status of the worker nodes does not change to Prepared, restart the cluster again, by clicking the Soft Restart button and clicking OK. Wait for the status to change to Prepared. Next Step: Proceed to Activate Aster Database. Activate Aster Database After the worker nodes show a status of Prepared and the queen and loader nodes show as Active, you may activate the cluster. Click the Admin tab, click the Activate Cluster button and click OK in the confirmation window. The cluster should begin activating and its status should change from Stopped to Activating and finally to Active. Once the cluster status is Active and the status of all nodes is Active, the cluster upgrade is complete and the cluster is ready to run processes. Aster Database Installation and Upgrade Guide 131

132 Upgrading the Aster Database on Commodity Hardware Post-Upgrade Procedures Next Step: Proceed to Fix Each Access Control List (ACL). Fix Each Access Control List (ACL) 1 Using psql, connect to the local database on the queen as the _bee_sys user: # psql -p U _bee_sys -d beehive 2 Enter the password for the _bee_sys user when prompted. 3 Use the command \l to list all existing databases. This list includes user databases, the "beehive" database, and all databases whose name contains the prefix "_bee_usr". Make a note of all the databases returned. 4 For each user database, perform the following steps: a b Connect to the database: beehive=# \c <database name> Issue the following SQL commands: beehive=# SELECT _bee_special.sync_relation_acl_from_pg(); sync_relation_acl_from_pg (1 row) beehive=# UPDATE _bee_special.schema_information s SET schemaacl = n.nspacl FROM pg_namespace n WHERE s.id = n.oid AND s.schemaacl IS DISTINCT FROM n.nspacl; c You will see a message returned saying UPDATE and the number of records updated. 5 Verify that your Schema ACLs do not contain numbers: beehive=# SELECT name, schemaacl FROM _bee_special.schema_information; If your output does not contain numbers, as in the following example, then verification is successful: name schemaacl public {beehive=uc/beehive,=uc/beehive} nc_system {db_admin=u/db_admin,=u/db_admin} (2 rows) 6 Verify that your Table ACLs do not contain numbers: beehive=# SELECT tableacl FROM _bee_special.table_information; If your output does not contain numbers, as in the following example, then verification is successful: tableacl {catalog_admin=arwddxt/catalog_admin,=rwd/catalog_admin} {catalog_admin=arwddxt/catalog_admin,=rwd/catalog_admin} 132 Aster Database Installation and Upgrade Guide

133 Upgrading the Aster Database on Commodity Hardware Post-Upgrade Procedures (2 rows) 7 Type q to quit the output, and \q to quit psql. Next Step: Proceed to Test your Cluster. Test your Cluster 1 Verify that all nodes have the new, upgraded version of Aster Database by issuing the following command on the queen: # ncli node runonall cat /home/beehive/bin/.build 2 To allow user queries, which is necessary for running diagnostic tests, you must re-enable user queries. To re-enable user queries for upgrades from 6.00.xx.xx, see Re-enable User Queries on page Run the Aster Database Diagnostic Tests Suite on the queen: a b Log in to ACT as _bee_sysman, create a dummy table, and drop it. This will issue a COMMIT on all vworkers. This first COMMIT may take a long time to complete. This is normal. Subsequent queries will be faster: # act -U _bee_sysman -w <_bee_sysman_pwd> beehive=> CREATE TABLE foo (id int, label varchar) DISTRIBUTE BY HASH (id); CREATE TABLE beehive=> DROP TABLE foo; DROP TABLE beehive=> COMMIT; Check if a user database called "sanitytest_db" exists by issuing \l. If sanitytest_db" does exist, the Diagnostic Tests Suite should not be run. Quit ACT by issuing \q If sanitytest_db" does not exist, quit ACT by issuing \q, and then change directories and run the diagnostic tests: # cd /home/beehive/bin/utils/diagnostictests # time./testrunner.py -f BasicSanityTestSuite.conf c Contact Teradata Global Technical Support (GTS) if there are any test failures reported. 4 Collect the table row counts using the procedure View Row Counts for Each Table on page 139. Compare the counts to the ones you collected pre-upgrade to ensure that nothing has changed. 5 You may also run any of your own internal diagnostic checks at this time, to verify the consistency of your data and ensure that database objects remain unchanged. Next Step: Proceed to Redistribute Preexisting Data on the Cluster. Aster Database Installation and Upgrade Guide 133

134 Upgrading the Aster Database on Commodity Hardware Post-Upgrade Procedures Redistribute Preexisting Data on the Cluster A hash function distributes the data for distributed tables across all partitions in a cluster. As part of the upgrade process, all tables will be migrated to use the hash function using the ncli system redistributefacttables utility command. The ncli system redistributefacttables utility command updates the partitioning scheme to use the hash function for all tables. In addition, ncli system redistributefacttables redistributes the data to the correct partitions for tables to comply with the hash function. Therefore, it is mandatory to run the ncli system redistributefacttables command after upgrading. Depending on the number of tables that require redistribution, this step can be a very long running operation for a particular cluster. For more information, contact your Customer Service Representative and refer to the redistributeinfo Tech Alert. To perform the data reditribution operation: 1 Before proceeding, clear all existing Admission Limits. a b c Log in to the AMC as an administrator (such as db_superuser). From the menu, select Admin > Configuration > Admission Limits. Make note of the existing Admission Limits as you will need to restore them after the redistribute operation. d Locate any Admission Limits that were previously created, and select X to delete the Admission Limits. When prompted, Confirm deletion of the Admission Limits. 2 Execute the following commands at a queen command prompt: ncli system redistributefacttablescheck --nodryrun ncli system redistributefacttables The ncli system redistributefacttablescheck --nodryrun command verifies that there is enough free disk space to do the redistribution. The ncli system redistributefacttables command migrates all tables to use the hash function and redistribute the data of affected tables to their correct partitions. 3 Restore any Admission Limits that were cleared in Step 1. Refer to the Aster Database User Guide for information on using the ncli system redistributefacttables, ncli system redistributefacttablescheck, and ncli system redistributefacttablesstatus commands to migrate the tables. Next Step: Proceed to Disable Passwordless Root SSH. Disable Passwordless Root SSH If you will upgrade the Aster Backup cluster as described in Upgrade the Aster Backup Cluster on page 135, you can skip this step because passwordless root SSH must be enabled in order to upgrade the Aster Backup cluster. If not, once you are satisfied that your upgrade was successful, you can disable passwordless root SSH by issuing: 134 Aster Database Installation and Upgrade Guide

135 Upgrading the Aster Database on Commodity Hardware Upgrade Backup Cluster and Aster Clients # ncli sshkeys disable -n <IP1,IP2,...> Note that when specifying multiple node IP addresses using the -n option, they must be separated by a comma only, without spaces. Next Step: Proceed to Add SQL-H Configurations. Add SQL-H Configurations A SQL-H configuration must be created for each Hadoop cluster you wish to access through SQL-H. This can be done through the AMC or using ncli. The procedure for creating a SQL-H configuration is documented in the Aster Database User Guide. Next Step: Proceed to Upgrade Backup Cluster and Aster Clients. Upgrade Backup Cluster and Aster Clients This section includes procedures for upgrading Aster Backup Cluster and Aster Clients. Complete the appropriate procedures for your environment: Upgrade the Aster Backup Cluster Upgrade ACT Upgrade ODBC and JDBC Drivers Upgrade Aster Loader Tool Re-Create TD Wallet Symbolic Link Upgrade Complete! Upgrade the Aster Backup Cluster No Upgrade Path for Backup Manager You will not be able to restore backups taken with a previous version of Aster Backup after upgrading. The installer will remove all previous (older versions) backups. If you do not wish to lose previous backups, do one of the following before upgrading Aster Backup: Archive your backups before upgrading Backup Manager. Do a clean install of Backup Manager on another machine for use with Aster Database 6.10 only. Older backups are not compatible with Version 6.10 of Backup Manager. Upgrade Prerequisites Teradata Aster recommends these best practices for upgrading Aster Backup cluster: Aster Database Installation and Upgrade Guide 135

136 Upgrading the Aster Database on Commodity Hardware Upgrade Backup Cluster and Aster Clients 1 Make disaster recovery archives: Before you upgrade Aster Backup, Teradata Aster recommends that you make disaster recovery archives of your old Aster Database data backups. 2 Plan to make new backups of critical tables: Aster Database does not support cross-version backups. Your pre-upgrade backup data is only usable on a pre-upgrade version of Aster Database. Since your existing backups will not be usable in the upgraded cluster, you should plan to make new backups of all critical tables soon after you finish the Aster Backup upgrade. 3 If your Aster Backup cluster runs on Red Hat: a Ensure that you are running version 6.4 or 6.5 or the Red Hat Enterprise Linux operating system on the Backup Manager and all Backup Nodes. b Apply the required kernel patches on the Backup Manager and all Backup Nodes. To do this, follow the instructions in Install Kernel Patches on Red Hat on page 139, substituting the Backup Manager and Backup Node you are working on for the queen. 4 In order to upgrade, passwordless SSH must be set up and working for the users beehive and root between all nodes in the backup cluster. After upgrading, you may disable it, if you choose. Obtaining Installation File Work with your Account Team to obtain the correct version of the Aster Backup installation bundle, ncluster-backup-upgrade.tar for this release. This bundle contains these required files to install Aster Backup on the Backup cluster: backup-sw.tar.gz install_backup.py install_backup_node.py tc_backup_x86_64.tar.gz Upgrade Backup Cluster Procedure You can perform this installation from any Linux workstation that has Python installed and has access to the machines of your Backup cluster. 1 Locate the Aster Backup installation bundle, ncluster-backup-upgrade.tar. 2 Decompress the installation bundle by issuing this command: install_backup.py install_backup_node.py backup-sw.tar.gz tc_backup_x86_64.tar.gz 3 Run the script install_backup.py with the following options, depending on what you want to upgrade. The -p flag specifies the path to the package to install, in these examples that path is the current working directory. Make sure to use the upgrade option, which causes the existing backup files to be left in place: To upgrade the entire Backup Cluster: 136 Aster Database Installation and Upgrade Guide

137 Upgrading the Aster Database on Commodity Hardware Upgrade Backup Cluster and Aster Clients $ python install_backup.py upgrade -m <Mgr-IP> -p. where <Mgr-IP> is the IP address of the Backup Manager. To upgrade only the backup nodes, if needed: $ python install_backup.py upgrade-nodes -n <bkp-nodes> -p. where <bkp-nodes> is a comma delimited list of the IP addresses of the Backup Nodes. Note: If passwordless root SSH is not enabled between the Backup Manager and the Backup Nodes, the installer will prompt for the root password of the Backup Nodes. 4 The upgrade script deletes any existing backups. It will display a message like: "Please be patient as the backups are being deleted". This message will be displayed only if there are previous backups. 5 If the upgrade is unsuccessful, see Backup Install Problems on page Once the script completes, verify that the cluster has been upgraded and then exit: a Launch the ncluster_backup CLI, passing the IP address or DNS name of the Backup Manager: $ ncluster_backup -h <Backup-Manager-IP> b At the command prompt, enter: $ exit 7 Make new backups of all critical tables now. Notice: Cross-version backups are not supported in Aster Database, so your existing backups are not usable in your new cluster! 8 After you are satisfied that your upgraded cluster and backup cluster are operating correctly, delete all pre-upgrade backups. Next Step: Proceed to Upgrade ACT. Upgrade ACT Depending on the version compatibility in the Aster Database Drivers and Utilities Matrix, you may need to upgrade Aster Database Terminal (ACT) on all workstations that are used to connect to the Aster Database. 1 Download the latest ACT executable from 2 Install the ACT client as explained in the Aster Client Guide. 3 To check the version after upgrading, type the ACT executable name with the --version flag. For example: $ act --version Aster Database Installation and Upgrade Guide 137

138 Upgrading the Aster Database on Commodity Hardware Upgrade Backup Cluster and Aster Clients Next Step: Proceed to Upgrade ODBC and JDBC Drivers. Upgrade ODBC and JDBC Drivers Depending on the version compatibility in the Aster Database Drivers and Utilities Matrix, you may need to upgrade Aster ODBC and/or JDBC on all workstations that use to connect to Aster Database. 1 Download the latest Aster ODBC and/or JDBC client from 2 Install and configure ODBC/JDBC as explained in the Aster Client Guide. 3 Note that the Aster Database ODBC driver may change in any Aster Database release. For this reason, with each new edition of Aster Database, you should re-install the driver and re-compile your applications that include it. Tip! You can check the version of the Aster Database ODBC driver on a client machine by: On Linux, Solaris or MacOS: going to the ODBC driver installation directory and viewing the contents of the.deploy file, which lists the version and build number. This file can be found in a directory that has the form: /usr/local/lib/stage/clients-odbc-<your_os>/libs On Windows: looking in the Control Panel for Add Remove Programs or Programs and Features in the Version column for the Aster ODBC Driver. Next Step: Proceed to Upgrade Aster Loader Tool. Upgrade Aster Loader Tool If you use Aster Loader Tool (ncluster_loader), you must upgrade it now. Do this: 1 Download the latest Aster Loader Tool from 2 Install Aster Loader Tool as explained in the Aster Client Guide. Next Step: Proceed to Re-Create TD Wallet Symbolic Link. Re-Create TD Wallet Symbolic Link If you use TD Wallet, you need to recreate the symbolic link: 1 Change directories: # cd /home/beehive/clients_all/linux64 2 Recreate the symbolic link: # ln -s /opt/teradata/client/tdwallet tdwalletdir Next Step: Proceed to Upgrade Complete!. 138 Aster Database Installation and Upgrade Guide

139 Upgrading the Aster Database on Commodity Hardware Common Procedures Upgrade Complete! Once you have upgraded the items above, your upgrade is complete. Refer to the Aster Database 6.10 Release Notes for important information about this version of Aster Database. Tip! Now is a good time to make sure all Aster Database users can get the client software updates they will need. On your internal software distribution server or wiki, add the new Aster Database clients and drivers so that all Aster Database users can download and install them. Common Procedures View Row Counts for Each Table Use this procedure before upgrading to obtain a row count for each table. After upgrading, use the pre-upgrade table counts you collected as a sanity check to make sure there were no changes during the upgrade. 1 Connect to ACT as db_superuser, and enter the password when prompted: # act -U db_superuser 2 Make a record of the names of all tables in all databases in your Aster cluster using the following SQL: SELECT relname, database, schema, object_type, table_type FROM nc_tablesize_details ( ON (SELECT 1) PARTITION BY 1 ) GROUP BY relname, database, schema, object_type, table_type; 3 Connect to each database: \c <dbname> 4 Make a record of the row count for each table in that database using the following SQL: SELECT COUNT(*) FROM <tablename>; 5 Repeat the last two steps until you have a list of table names and row counts of all tables in all databases. Install Kernel Patches on Red Hat 1 Set the flag to disable Aster Database from checking for package version numbers on each node. To do this, issue the following command (note the leading '.' on the filename.): # ncli node runonall touch /primary/.skip_ospackages_check 2 Use the yum command to install the new RPM packages, which you downloaded onto the Aster queen and each node in the cluster. For example: On Red Hat 6.5: yum install --nogpgcheck -t --disablerepo=ncluster* kernel-firmware el6.noarch.rpm yum install --nogpgcheck -t --disablerepo=ncluster* kernel el6.x86_64.rpm Aster Database Installation and Upgrade Guide 139

140 Upgrading the Aster Database on Commodity Hardware Common Procedures Block User Queries On Red Hat 6.4: yum install --nogpgcheck -t --disablerepo=ncluster* kernel-firmware el6.noarch.rpm yum install --nogpgcheck -t --disablerepo=ncluster* kernel el6.x86_64.rpm 3 Verify that the new kernel packages have been installed correctly by issuing: # ncli node runonall 'rpm -qa grep kernel' 4 If your Red Hat OS is configured to permit you to run multiple kernel versions, you ll need to ensure that the correct kernel version is running. To do this, issue the following command to ensure that the correct kernel is actually running: # ncli node runonall uname -r Use Admission Limits to block user queries: 1 Log in to the AMC as an administrator (such as db_superuser). 2 From the menu, select Admin > Configuration > Admission Limits. 3 Click the New Admission Limit button. 4 Fill in the admission limit information as follows: a b Provide a unique name such as "Block User Queries". Use username!= '_bee_sysman' for the predicate. c Set the concurrency limit to 0. d Click OK. 5 Now queries from users other than _bee_sysman will fail with the error "Admission denied". Note that any transactions that are currently running will continue to execute unless they are individually cancelled. Re-enable User Queries To undo the settings you made in the procedure Install Kernel Patches on Red Hat on page 139 and bring the cluster back on-line: 1 Log in to the AMC as an administrator (such as db_superuser). 2 From the menu, select Admin > Configuration > Admission Limits. 3 Find the Admission Limit you created previously to block user queries in the list. 4 Click the X to delete it. Confirm deletion when prompted. Reinstall JCE to Support Kerberos If your Aster cluster is configured to connect to Hadoop clusters with Kerberos authentication and uses AES-256 encryption, JCE may need to be reinstalled on all nodes after installation. Refer to Java Cryptography Extension (JCE) Policy File Installation in the Aster Database User Guide. 140 Aster Database Installation and Upgrade Guide

141 Upgrading the Aster Database on Commodity Hardware Configure the Browser to Trust the AMC Certificate Configure the Browser to Trust the AMC Certificate The AMC runs using secure HTTP, at an https URL on the queen machine. To open the AMC, type and the IP address or hostname of your queen: IP Address> Your browser will display a notice stating that the connection is not trusted. This notice appears because the AMC connection is secured by Teradata Aster s self-signed digital certificate. You can configure your browser to trust this certificate so that the notice does not appear. To do this, follow the instructions in one of these sections: Configure Firefox to Trust the AMC Certificate Configure Internet Explorer to Trust the AMC Certificate Configure Firefox to Trust the AMC Certificate 1 In Firefox, click the I understand the risks link. Figure 8: Firefox: Trusting the AMC certificate 2 Click the Add Exception button. Figure 9: Add Exception button in Firefox Aster Database Installation and Upgrade Guide 141

142 Upgrading the Aster Database on Commodity Hardware Configure the Browser to Trust the AMC Certificate 3 In the next window, make sure the checkbox, Permanently store this exception, is checked. 4 Click the Confirm Security Exception button. Firefox will now trust the AMC certificate. Figure 10: Add Security Exception in Firefox Configure Internet Explorer to Trust the AMC Certificate 1 In the IE browser, you will see the message, There is a problem with this website s security certificate. Click Continue to this website. Figure 11: Continue to this website in Internet Explorer 2 The navigation bar appears in pink with the message, Certificate Error. Figure 12: Certificate Error in Internet Explorer 142 Aster Database Installation and Upgrade Guide

143 Upgrading the Aster Database on Commodity Hardware Configure the Browser to Trust the AMC Certificate 3 Click on the words, Certificate Error. Figure 13: Click on Certificate Error 4 Click View Certificates. Figure 14: Install the certificate in Internet Explorer 5 Click Install Certificate. Internet Explorer will now trust the AMC certificate. Aster Database Installation and Upgrade Guide 143