Teradata Virtual Machine Developer Edition Installation, Configuration, and Upgrade Guide Release B K April 2016

Transcription

1 What would you do if you knew? Teradata Virtual Machine Developer Edition Installation, Configuration, and Upgrade Guide Release B K April 2016

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. Simba, the Simba logo, SimbaEngine, SimbaEngine C/S, SimbaExpress and SimbaLib are registered trademarks of Simba Technologies 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 2016 by Teradata. All Rights Reserved.

3 Table of Contents Preface...5 Purpose... 5 Audience... 5 Revision History... 5 Additional Information...5 Related Documents... 5 Related Links...6 Product Safety Information...6 Chapter 1: Developer Edition Overview... 7 Developer Edition Description...7 Developer Edition Use Cases... 7 Chapter 2: Preparing for Teradata Virtual Machine Installation... 9 Requirements... 9 Teradata Virtual Machine Installation Components...9 Teradata Virtual Machine Templates Teradata Virtual Machine Property Files...10 Teradata Virtual Machine Scripts The pdegplsrc Packages Installing Teradata Virtual Machine...11 Specifying Administrators of a Teradata Virtual Machine Host Server Setting PowerCLI Script Execution Privileges...13 Obtaining a Teradata Change Control Number...13 Obtaining the Latest Installation Components Editing Property Files The vmwareit.properties File The deploy.properties File Unattended Deployment Temporal Settings Teradata Virtual Machine Developer Edition Installation, Configuration, and Upgrade Guide, Release

4 Table of Contents Chapter 3: Teradata Virtual Machine Deployment...25 Executing the Setup Scripts Deployment Verification Starting the Database Logging On to the Database Testing the Database Testing Viewpoint Teradata QueryGrid R for Data Analysis...28 Connecting with a Mainframe Computer...28 Connecting with a Mainframe Computer after Installation...29 Chapter 4: Upgrading Teradata Virtual Machine...31 Upgrading Developer Edition...31 PUT Overview Downloading New PUT Packages...32 Upgrading PUT in Customer Mode Upgrading the Database Upgrading Viewpoint Chapter 5: Replacing Teradata Virtual Machine...37 Replacing Developer Edition Database The replace.properties File...37 Executing the Replace Script Teradata Virtual Machine Developer Edition Installation, Configuration, and Upgrade Guide, Release 15.10

5 Preface Purpose Use the steps in this guide to install, configure, deploy, and upgrade or replace Teradata Virtual Machine Developer Edition (Developer Edition). Audience This guide is intended for use by: VMware Administrators who configure hardware in preparation for installing Developer Edition. Administrators who install, configure, and maintain Developer Edition. Database and software professionals who use the deployed Developer Edition instances, ensure the database is running, and use client applications to access the database for development and testing. Revision History Date April 2016 Description Initial Release Additional Information Related Documents Title Publication ID Teradata Viewpoint User Guide B Parallel Upgrade Tool (PUT) Reference B Teradata QueryGrid Installation and User Guides Numerous Teradata Virtual Machine Developer Edition Installation, Configuration, and Upgrade Guide, Release

6 Preface Title Teradata Virtual Machine Frequently Asked Questions Publication ID Knowledge Article KAC13A25E, accessed through tays.teradata.com. Related Links URL Description External site for product, service, resource, support, and other customer information. External site for published Teradata customer documentation. External site for access to the Teradata software server. Accessible only with an active service contract. Product Safety Information This document may contain information addressing product safety practices related to data or property damage, identified by the word Notice. A notice indicates a situation which, if not avoided, could result in damage to property, such as equipment or data, but not related to personal injury. Example Notice: Improper use of the Reconfiguration utility can result in data loss. 6 Teradata Virtual Machine Developer Edition Installation, Configuration, and Upgrade Guide, Release 15.10

7 CHAPTER 1 Developer Edition Overview Developer Edition Description Developer Edition is a SUSE Linux Enterprise Server (SLES) operating system and Teradata Database packaged into a virtual container that runs in a virtualized environment on thirdparty hardware. Developer Edition software consists of templates and associated properties files and scripts. When a Developer Edition virtual machine is deployed, it operates as a fully functional instance of the configured Teradata Database. Note: You must have administrative privileges on the destination VMware environment to install and configure Developer Edition virtual machines. Developer Edition Use Cases Once deployed by the VMware administrator, Developer Edition can be used for proof of concepts, development, testing, data validation, and as a sandbox for Teradata Database users. Possible use cases include: Virtual instances of Teradata Database for VMware ESX and ESXi Server, for customers with an existing or planned VMware ESX and ESXi Server farm where virtual instances of Teradata Database can be instantiated and removed as required for test and development work. Quick delivery of Teradata Database configured environments. Disposable sandboxes for development, a valuable and important alternative to uncontrolled data marts for building analytic prototypes and models and experimenting with data. Pre-production usage, for testing and validation of new features. Reversions, in the event of problems with the replacement process. Customers can restore to an earlier state (including Teradata Database version, customized configuration settings, and AMP data) by replacing a Teradata Virtual Machine with a previously saved template. Teradata Virtual Machine Developer Edition Installation, Configuration, and Upgrade Guide, Release

8 Chapter 1 Developer Edition Overview 8 Teradata Virtual Machine Developer Edition Installation, Configuration, and Upgrade Guide, Release 15.10

9 CHAPTER 2 Preparing for Teradata Virtual Machine Installation Requirements You must have a valid Site ID to obtain the Developer Edition installation components. For assistance with your Site ID, contact Teradata Customer Support. Note: Do not use a different Site ID for every Developer Edition instance. Use the same Site ID for all Developer Edition instances. Developer Edition has the following technical requirements. For detailed requirements, see the Developer Edition Bill of Materials. Component Requirements VMware ESXi version ESXi 5.5 or 6.0 Datastore space for template deployment Teradata Database: 30 GB minimum Teradata Viewpoint: 13.5 GB minimum vcenter management VMware administrator privileges Running vcenter Management instance (verified using the Microsoft Services control within the vcenter image) vcenter Standard version (must support ESXi 5.5 or 6.0 servers) vcenter 5.5 or 6.0 vsphere Client Windows OS for vsphere Client vsphere PowerCLI version 5.5 release 2 or version 6.0 PowerCLI Windows.Net Framework 4.5 Windows PowerShell V2 or latest vsphere PowerCLI toolkit Teradata Virtual Machine Installation Components Teradata Virtual Machine installation components consist of templates, property files, scripts, and text files. Teradata Virtual Machine Developer Edition Installation, Configuration, and Upgrade Guide, Release

10 Chapter 2 Preparing for Teradata Virtual Machine Installation Required templates contain the Teradata Database and underlying operating system. Optional templates contain Viewpoint and its underlying operating system. Templates are ready to use and include defaults for disk space and configuration, I/O, network connections, AMPs, and memory. Property files define configuration settings for the overall Teradata Virtual Machine environment and the specific virtual machines. Scripts deploy the Teradata virtual machine based on the configuration information in the property files. Text files are used in time zone settings. Teradata Virtual Machine Templates Template Template Name Default Configuration Teradata Database and Operating System Template Teradata Viewpoint and Operating System Template SLES 11, SP3: TVME-TD15.10 SLES11_SP3_ESXi xx.xx-1 SLES 11, SP1: TVME-TD15.00 SLES11_SP1_ESXi xx.xx-1 TVME-TD14.10 SLES11_SP1_ESXi xx.xx-1 1 virtual cores 8 GB RAM FSG cache setting: 70% 3 network adapters 187 GB OS disk 2 virtual disks (20 GB each) TVME-VP SLES11_SP1_ESXi xx.xx-1 1 virtual core 10 GB RAM 187 GB OS disk 256 GB data disk 3 network adapters Teradata Virtual Machine Property Files Properties File Name vmwareit.properties deploy.properties replace.properties Contents Virtual environment configuration settings common across Teradata virtual machines. Define the values in this file once, unless something in the virtual environment changes. Configuration settings unique to the Teradata and Viewpoint virtual machines.define the values in this file for each deployment. Configuration settings for replacing an existing Developer Edition virtual machine with a different version, while maintaining the database size, characteristics, and content. Teradata Virtual Machine Scripts Script deploy.ps1 Description Parses the vmwareit.properties and deploy.properties files to ensure that all required values are present and correctly 10 Teradata Virtual Machine Developer Edition Installation, Configuration, and Upgrade Guide, Release 15.10

11 Chapter 2 Preparing for Teradata Virtual Machine Installation Script Description formatted, validates settings, and launches each subsequent script to deploy the components of the Teradata virtual machine. TVMDEDeployAndConfigureDBS.ps1 ViewpointVMDeployAndConfigure.ps1 replace.ps1 Deploys the Teradata Database and underlying operating system for the Teradata virtual machine. Deploys Viewpoint and underlying operating system for the virtual machine. Replaces the Teradata Virtual Machine release on a previously deployed Developer Edition virtual machine while retaining all database objects and most configuration settings. Optionally backs up the prior virtual machine. The pdegplsrc Packages The following pdegplsrc packages are available in /var/opt/teradata/ opensourcepkgs: pdegplsrc x86_64.rpm in the Teradata Database template pdegplsrc x86_64.rpm in the Teradata Database template pdegplsrc x86_64.rpm in the Teradata Database template Installing Teradata Virtual Machine Prerequisite: You must have a valid Site ID to obtain the Teradata Virtual Machine installation components. You must be a VMWare administrator to install and configure Teradata Virtual Machine software. Installation and configuration of all VMWare software is the responsibility of your VMWare Admin. Teradata cannot support your VMWare environment. 1 Obtain a Change Control Number for downloading the templates and scripts. 2 Download and save the Developer Edition templates and scripts. 3 If applicable, limit administration of the Teradata Virtual Machines host server to certain users. 4 If this is a new installation, set PowerCLI Script execution privileges. 5 If this is a new installation, or if your VMWare environment has changed, edit the values in the vmwareit.properties file. 6 Edit the deploy.properties file with the values for the specific Teradata Virtual Machine installation. Teradata Virtual Machine Developer Edition Installation, Configuration, and Upgrade Guide, Release

12 Chapter 2 Preparing for Teradata Virtual Machine Installation 7 Run the Setup script to install Teradata Database and Viewpoint into two different virtual machines. 8 If necessary, start the database. 9 Confirm that the Teradata Database installed correctly. 10 Confirm that Viewpoint installed correctly. 11 If you plan to use Teradata QueryGrid, configure the connector. 12 If you want the virtual machine to communicate with a mainframe computer, establish the connection. Specifying Administrators of a Teradata Virtual Machine Host Server To allow only certain users to administer a Teradata Virutal Machine host server in a shared virtual environment, add those users as administrators of a datacenter containing the server. 1 Open vsphere Client. 2 Log in to the vcenter Server associated with the Teradata Virtual Machine host server. 3 In the tree view, right-click the vcenter Server listing, and select New Datacenter. 4 In the tree view, click New Datacenter, and rename it as appropriate. 5 Add the ESXi server that will host the Teradata virtual machines to the new datacenter: a In the tree view, right-click the datacenter branch, and select Add Host. b c d e At Host, enter the name or IP address of the ESXi host. At Authorization, enter the username and password, and click Next. If an authenticity message appears, click Yes to continue. At Host Summary, click Next. 12 Teradata Virtual Machine Developer Edition Installation, Configuration, and Upgrade Guide, Release 15.10

13 Chapter 2 Preparing for Teradata Virtual Machine Installation f At Assign License, ensure that the Essentials license is selected, and click Next. g Click Next through the remaining prompts, then click Finish. The host name appears in the tree view, under the datacenter branch. 6 In the tree view, click the branch for the datacenter containing the Teradata Virtual Machine host server. 7 Click the Permissions tab. 8 In a blank area of the tab, right-click, then select Add Permission. The Assign Permissions window appears. 9 Under Assigned Role, select Administrator. 10 Under Users and Groups, click Add. The Select Users and Groups window appears. 11 From the Domain list, select the Active Directory where the accounts for the users who you want to designate as administrators exist. 12 In the list pane, select the applicable users or groups. 13 Click Add. 14 When you have finished selecting users or groups, click OK. The Select Users and Groups window closes, and the Permissions tab reflects the selected users or groups. Setting PowerCLI Script Execution Privileges If this is a new installation of PowerCLI, you must set the PowerCLI script execution privileges to allow the unsigned but Teradata-certified Teradata Virtual Machine scripts to be run. 1 In a PowerCLI command window, run: Set-ExecutionPolicy -ExecutionPolicy unrestricted 2 If you are prompted to confirm the change, enter Y. Obtaining a Teradata Change Control Number You must have a Teradata Change Control Number to download the Teradata Virtual Machine installation components from Teradata At Your Service. 1 Log on to 2 Click Change Control. 3 At Change Control, click Create. Teradata Virtual Machine Developer Edition Installation, Configuration, and Upgrade Guide, Release

14 Chapter 2 Preparing for Teradata Virtual Machine Installation 4 Click Site. 5 Select the site to which this change control applies. 6 Click Activity. 7 From the drop down list, select Customer TVME Software Download. 8 Click Synopsis. 9 At Synopsis and Description, enter Customer TVME Software Download. 10 Click Planned Date. 11 Select the date and time planned for the download. If you see a note advising you that you need a minimum of 28 days notice for a change control, ignore it. It does not apply to Teradata Virtual Machine. 12 Click Submit the Change Control. 13 When prompted for confirmation, click OK. Your change control number appears on the listing. Obtaining the Latest Installation Components Before installing Teradata Virtual Machine, download the latest templates, property files, and scripts from Teradata At Your Service. 1 Log on to 2 Click Software Downloads. 3 Click Certified Configs. 4 Click Teradata Applications. The Teradata Applications pane opens. 5 From the Sub Category drop-down list, select Teradata Virtual Machine Developer Edition. 6 Select the release you want to download. Always select the most recent release. 7 Click Submit. 8 From the download list, select the files to download. Always select the latest templates, property files, and installation scripts. 9 Select Public FTP. 10 Enter your User Name, , Site ID, and Change Control Number. 11 At FTP Directory, enter the name of destination FTP directory for the.rar file containing the selected components. 14 Teradata Virtual Machine Developer Edition Installation, Configuration, and Upgrade Guide, Release 15.10

15 Chapter 2 Preparing for Teradata Virtual Machine Installation 12 Click Submit. The system sends an that includes the URL and security information you need to retrieve the files from the FTP site. File download times vary, but you can expect a full download to take as long as 1 hour. 13 Download the files to the Windows machine where PowerCLI is installed. 14 Decompress the downloaded.rar files. Editing Property Files Edit the vmwareit.properties file only once unless something in your virtual environment changes. Edit the deploy.properties file before deploying each Teradata virtual machine. Edit the replace.properties file before running the script to change the Teradata Database release on a previously deployed Teradata virtual machine. 1 In a text editor, open the properties file you need to edit. The files are in /DeveloperEdition/. 2 Update the file as needed. 3 Save the file. Related Topics The vmwareit.properties File, on page 15 The deploy.properties File, on page 16 The replace.properties File, on page 37 The vmwareit.properties File The vmwareit.properties file contains the VMware vsphere environment and IT configuration settings common to every Teradata virtual machine deployment. Configure the values in the vmwareit.properties file only once unless something in the virtual environment changes. Property Category Properties Description VMWare Details vcenterservernameoripaddress The name or IP Address of the vcenter server. vcenter Server Credentials vcenterserverusername vcenterserverpassword Example: vcenterservernameoripaddress= [Optional} Credentials required if you want to use the - force option for unattended deployment; otherwise, you must manually provide the credentials when prompted during deployment. Teradata Virtual Machine Developer Edition Installation, Configuration, and Upgrade Guide, Release

16 Chapter 2 Preparing for Teradata Virtual Machine Installation Property Category Common Network Details Network Switch vswitch0 External NTP Server Settings Properties NetworkDomain NetworkPrimaryDns NetworkSecondaryDns VirtualNetworkPortGroupName NTPServer1 NTPServer2 NTPServer3 Description Example: vcenterserverusername=admin vcenterserverpassword=password The network domain and primary DNS (both required) and the secondary DNS (optional). Example: NetworkDomain=corp.company.com NetworkPrimaryDns= NetworkSecondaryDns= The physical adapter with port group for the virtual network. The default value is VM Network. Example: VirtualNetworkPortGroupName=VM Network [Optional] The HostName/IP-Address of the external NTP servers, in the format xxx.xxx.xxx.xxx. Example: NTPServer1= NTPServer2= NTPServer3= You must configure the NTP servers if you plan to use the Temporal feature. The deploy.properties File The deploy.properties file contains the specifications needed by the deployment scripts to install and configure a given Teradata Database or Viewpoint virtual machine. Set the values in the deploy.properties file for each Teradata Virtual Machine deployment. Property Category Properties Description VMWare Host Details ESXiHostName Name of the VMware host on which the virtual machine will run. Example: ESXiHostName=esxhost01.corp.company.com Datastore Datastore Datastore associated with the host. Example: Datastore=datastore001-vol01 16 Teradata Virtual Machine Developer Edition Installation, Configuration, and Upgrade Guide, Release 15.10

17 Chapter 2 Preparing for Teradata Virtual Machine Installation Property Category Properties Description Type of Teradata Virtual Machines to Deploy VMWare Template Details VM Name and Location DBS Configuration VM Configuration DeployDatabaseVM DeployViewpointVM DeployDBSOVFTemplate ExistingDBSTemplateName DatabaseOVFFilePath ViewpointOVFFilePath DbsVMName ViewpointVMName LocationName NumberOfDataDisks DataDiskSizeGB NumCPU MemoryGB The Teradata Database or Teradata Viewpoint image to deploy when the value is set to true. Set the value to false when you do not want the image to be deployed. Examples: DeployDatabaseVM=true DeployViewpointVM=true Source of the template for the virtual machine being deployed in the specified VMWare environment. To use an OVF template from your local computer, set DeployDBSOVFTemplate to true and specify the DatabaseOVFFilePath value. Example: DeployDBSOVFTemplate=true DatabaseOVFFilePath=C:\TVME\TVME- TD15.10 SLES11_SP3_ESXi ovf To use a template that was previously loaded to the vcenter environment, set DeployDBSOVFTemplate to false and specify the ExistingDBSTemplateName value. Example: DeployDBSOVFTemplate=false ExistingDBSTemplateName =TVME- TD15.10 SLES11_SP3_ESXi The name of the virtual machine and the folder to which it should be deployed in the VMware environment. Examples: DbsVMName=TVME-DE1 ViewpointName=TD-VP Location=FolderName Total number of data disks and size of each data disk. The number of data disks must be even, and the data disk size must be an increment of 10 GB. The maximum database size (NumberOfDataDisks X DataDiskSizeGB) is 4090 GB. Examples: NumberOfDataDisks=4 DataDiskSizeGB=20 Number of CPUs and amount of memory. Allocate at least 2 GB of memory for each data disk. MemoryGB must be at least 8 GB, and it must be at least twice the value of NumberOfDataDisks. Teradata Virtual Machine Developer Edition Installation, Configuration, and Upgrade Guide, Release

18 Chapter 2 Preparing for Teradata Virtual Machine Installation Property Category Properties Description Examples: NumCPU=4 MemoryGB=16 TASM Values TASM System management option, based on one of the following system types: Appliance (1XXX) Enterprise (5XXX, the default) Example: TASM=Enterprise Timezone LinuxOSTimeZone The time zone of the virtual machine. Enter either a fixed time zone displacement from GMT or the time zone file name. See the file LinuxTimeZoneStrings.txt for the valid values for this field. If you are not enabling Temporal, the database time zone syncs with the OS. The default time zone is US/Pacific. Examples: LinuxOSTimeZone=GMT+11 or LinuxOSTimeZone=US/Eastern DBSControl Flags FSG Cache Percentage Mainframe Connectivity Temporal Settings: Temporal TimeDateWZControl DaylightSavings TimeZoneHour TimeZoneMinute TimeZoneString Other Settings: Columnar BlockLevelCompression RowLevelSecurity Secure Zones FSG Cache Percentage LHID Database features, enabled by setting the value to true. Accept the default of false if you do not plan to use the feature. Note: If you plan to enable Temporal, see Temporal Settings first. The Temporal feature can result in subtle data quality issues if not handled carefully. See the file TeradataTimeZoneStrings.txt for the valid values for TimeZoneString. If you plan to use the Temporal feature, you must define the NTP servers in the vmwareit.propertes file. The percentage of memory to allocate to the FSG cache, with an allowable value of 0 to 99 and a default value of 65. Example: FSGCachePercentage=65 Use this property to enable mainframe connectivity. Mainframe connectivity is available on Teradata Database and later. 18 Teradata Virtual Machine Developer Edition Installation, Configuration, and Upgrade Guide, Release 15.10

19 Chapter 2 Preparing for Teradata Virtual Machine Installation Property Category Properties Description Static IP Address and Host Name for Database VM Static IP Address and Host Name for Viewpoint VM IPAddressSetting HostNameForDbsVM IPAddressForDbsVM SubnetmaskForDbsVM NetworkGatewayForDbsVM IPAddressForVPVM HostNameForVPVM SubnetmaskForVPVM networkgatewayforvpvm At LHID, enter the logical host ID of the Teradata Director Program (TDP). You must enter that ID to connect to the mainframe. Leave this blank if you do not want to enable mainframe connectivity. For more information, see Connecting with a Mainframe Computer. The IP address setting and the host name, IP address, subnet mask, and network gateway for the Teradata Database virtual machine. The default host name is TVME. If IPAddressSetting=dhcp (the default), only the HostNameForDbsVM property value is required; if IPAddressSetting=static, all other property values are required. The subnetmask value must be in the format of XXX.XXX.XXX.X. In HostNameForDbsVM, you can enter a short host name in the format hostname instead of the fully-qualified domain name in the format hostname.domain. The domain name is specified in the vmwareit.properties file. Examples: IPAddressSetting=static HostNameForDbsVM=TVME IPAddressForDbsVM= SubnetmaskForDbsVM= NetworkGatewayForDbsVM= Static IP address, host name, subnet mask, and network gateway for the Viewpoint virtual machine. The default host name is TVME-VP. The subnetmask value must be in the format of XXX.XXX.XXX.X. In HostNameForVPVM, you can enter a short host name in the format hostname instead of the fully-qualified domain name in the format hostname.domain. The domain name is specified in the vmwareit.properties file. Examples: IPAddressForVPVM= HostNameForVPVM=TVME-VP subnetmaskforvpvm= networkgatewayforvpvm= Teradata Virtual Machine Developer Edition Installation, Configuration, and Upgrade Guide, Release

20 Chapter 2 Preparing for Teradata Virtual Machine Installation Unattended Deployment Teradata Virtual Machine allows unattended deployment using a command line parameter. The unattended deployment uses login credentials provided in the vmwareit.properties file, and assumes the default response to each prompt normally shown during deployment. To deploy Teradata Virtual Machine without manual intervention: Specify the vcenter login credentials in the vmwareit.properties file. Configure the other values in the vmwareit.properties file and the deploy.properties or replace.properties file. Run the deployment script with a -force parameter. Temporal Settings To use the Temporal option in a Teradata Virtual Machine, you must configure your system carefully to avoid subtle problems that can result. Note: Once you enable Temporal, you cannot turn it off. Use care when configuring this option. To enable the Temporal option for a virtual machine, set the Temporal property value in the deploy.properties file to true. Then configure the other related properties based on your preferred time options and whether you plan to restore data from another Teradata system. To use the Temporal option, you must configure the NTP servers in the vmwareit.properties file. Consult your Database Administrator for details on the DBSControl Flag values for the time zone variables. Use this diagram and table to determine your settings in the properties file. 20 Teradata Virtual Machine Developer Edition Installation, Configuration, and Upgrade Guide, Release 15.10

21 Chapter 2 Preparing for Teradata Virtual Machine Installation If you do not know your TimeZoneString, see Teradata Database Administration, B Notes: Temporal table support and Time Date with Zone Control by Database (TimeDateWZControl) are two different features. However, when enabling Temporal table support, Time Date with Zone Control by Database must also be enabled. If DaylightSavings is true, you must include a TimeZoneString. In the settings below, TimeZoneHour = 5 and TimeZoneMinute = 30 are examples. Enter the number of hours and minutes your installation is offset from GMT. See the file TeradataTimeZoneStrings.txt for the valid values for TimeZoneString. In the table settings below, TimeZoneString = America Pacific is an example. Enter the time zone for your system. In scenario 5, you must copy the time zone settings from the DBScontrol General Flags of the Teradata system from which you are restoring data. Scenario 5 reflects those six possible variations. Diagram Scenario Temporal Settings in the Property File DBS Control Setting Applied As 1 Temporal=false TimeDateWZControl=0 (Disabled) DaylightSavings=false TimeZoneHour=0 TimeZoneMinute=0 16. System TimeZone Hour=0 17. System TimeZone Minute=0 18. System TimeZone String=Not Set 57. TimeDateWZControl=0 (Disabled) Teradata Virtual Machine Developer Edition Installation, Configuration, and Upgrade Guide, Release

22 Chapter 2 Preparing for Teradata Virtual Machine Installation Diagram Scenario Temporal Settings in the Property File TimeZoneString=Not Set DBS Control Setting Applied As 2 Temporal=true TimeDateWZControl=3 (Local) DaylightSavings=false TimeZoneHour=0 TimeZoneMinute=0 TimeZoneString=Not Set 3 Temporal=true TimeDateWZControl=3 (Local) DaylightSavings=false TimeZoneHour=5 (Example) TimeZoneMinute=30 (Example) TimeZoneString=Not Set 4 Temporal=true TimeDateWZControl=3 (Local) DaylightSavings=true TimeZoneHour=0 TimeZoneMinute=0 TimeZoneString=America Pacific (Example) 16. System TimeZone Hour=0 17. System TimeZone Minute=0 18. System TimeZone String=Not Set 57. TimeDateWZControl=3 (Local) 16. System TimeZone Hour=5 (Example) 17. System TimeZone Minute=0 18. System TimeZone String=Not Set 57. TimeDateWZControl=3 (Local) 16. System TimeZone Hour=0 17. System TimeZone Minute=0 18. System TimeZone String=America Pacific (Example) 57. TimeDateWZControl=3 (Local) 5a 5b 5c Temporal data is stored in the Teradata file system in system local time. Daylight savings is observed. Temporal=true TimeDateWZControl=3 (Local) DaylightSavings=true TimeZoneHour=0 TimeZoneMinute=0 TimeZoneString=America Pacific (Example) Temporal data is stored in the Teradata file system in UTC time. Daylight savings is observed. Temporal=true TimeDateWZControl=2 (UTC) DaylightSavings=true TimeZoneHour=0 TimeZoneMinute=0 TimeZoneString=America Pacific (Example) Temporal data is stored in the Teradata file system in system local time. Temporal data is displayed in UTC time. Daylight savings is not observed. 16. System TimeZone Hour=0 17. System TimeZone Minute=0 18. System TimeZone String=America Pacific (Example) 57. TimeDateWZControl=3 (Local) 16. System TimeZone Hour=0 17. System TimeZone Minute=0 18. System TimeZone String=America Pacific (Example) 57. TimeDateWZControl=2 (UTC) 16. System TimeZone Hour=0 17. System TimeZone Minute=0 18. System TimeZone String=Not Set 57. TimeDateWZControl=3 (Local) 22 Teradata Virtual Machine Developer Edition Installation, Configuration, and Upgrade Guide, Release 15.10

23 Chapter 2 Preparing for Teradata Virtual Machine Installation Diagram Scenario 5d 5e 5f Temporal Settings in the Property File Temporal=true TimeDateWZControl=3 (Local) DaylightSavings=false TimeZoneHour=0 TimeZoneMinute=0 TimeZoneString=Not Set Temporal data is stored in the Teradata file system in UTC time. Temporal data is displayed in UTC time. Daylight savings is not observed. Temporal=true TimeDateWZControl=2 (UTC) DaylightSavings=false TimeZoneHour=0 TimeZoneMinute=0 TimeZoneString=Not Set Temporal data is stored in the Teradata file system in system local time. Daylight savings is not observed. Time offset from GMT is entered. Temporal=true TimeDateWZControl=3 (Local) DaylightSavings=false TimeZoneHour=5 (Example) TimeZoneMinute=30 (Example) TimeZoneString=Not Set Temporal data is stored in the Teradata file system in UTC time. Daylight savings is not observed. Time offset from GMT is entered. Temporal=true TimeDateWZControl=2 (UTC) DaylightSavings=false TimeZoneHour=5 (Example) TimeZoneMinute=30 (Example) TimeZoneString=Not Set DBS Control Setting Applied As 16. System TimeZone Hour=0 17. System TimeZone Minute=0 18. System TimeZone String=Not Set 57. TimeDateWZControl=2 (UTC) 16. System TimeZone Hour=5 (Example) 17. System TimeZone Minute=30 (Example) 18. System TimeZone String=Not Set 57. TimeDateWZControl=3 (Local) 16. System TimeZone Hour=5 (Example) 17. System TimeZone Minute=30 (Example) 18. System TimeZone String=Not Set 57. TimeDateWZControl=2 (UTC) Teradata Virtual Machine Developer Edition Installation, Configuration, and Upgrade Guide, Release

24 Chapter 2 Preparing for Teradata Virtual Machine Installation 24 Teradata Virtual Machine Developer Edition Installation, Configuration, and Upgrade Guide, Release 15.10

25 CHAPTER 3 Teradata Virtual Machine Deployment Executing the Setup Scripts The start-up script, deploy.ps1, verifies that all required property file values are present and correctly formatted, and validates other settings. If it finds no errors, the script deploys the virtual machine. If you use the -force parameter, the script runs unattended. See Unattended Deployment for more information. 1 Open the PowerCLI console. 2 Change the directory to the location where the downloaded Teradata Virtual Machine installation files are stored. 3 Run the deploy.ps1 script:.\deploy.ps1 -vmitfile vmwareit.properties -tvmefile deploy.properties Note: For unattended deployment, use the -force parameter:.\deploy.ps1 -force -vmitfile vmwareit.properties -tvmefile deploy.properties 4 Review the information. If it is correct, press y. If the information is not correct, edit the property files and re-run the script. The system prompts you to log on to the vcenter server. 5 Type your vcenter User name and Password, then click OK. The script connects to the vcenter server and validates the information in the property files. When validation is successful, the script deploys the selected templates, and configures the virtual machines based on the values in the property files. 6 If a message warns you that running scripts is disabled, you must set the script execution privileges, then re-run the script. See Setting PowerCLI Script Execution Privileges. Deployment Verification Teradata Virtual Machine Developer Edition Installation, Configuration, and Upgrade Guide, Release

26 Chapter 3 Teradata Virtual Machine Deployment Starting the Database The database starts automatically after deployment. If the database does not start, start it manually: /etc/init.d/tpa start. Logging On to the Database After starting the database, log on. For more information, see Knowledge Article KAC13A25E. We also strongly recommend immediately changing the database password. For instructions and best practices, see Knowledge Article KAP23E402. Knowledge Articles can be accessed through Testing the Database After a Teradata Virtual Machine deployment, verify that the database is accessible and responsive. 1 Start BTEQ. 2 Using the default credentials, log in to the database. 3 Run select * from dbc.dbcinfo to see if the database is responding. Sample result indicating response: 4 If the database does not respond, try to access the server through SSH. 5 If you cannot access the server, review Knowledge Article KAC13A25E. Knowledge Articles can be accessed through If you are unable to resolve the issue, contact Teradata Customer Service for assistance. Testing Viewpoint After deploying a Viewpoint virtual machine, confirm that you can add and use required portlets. 1 Log in to Viewpoint. 2 If Viewpoint is not already configured, use the Monitored Systems portlet under Administration to configure it. For more information, see the Teradata Viewpoint User Guide. 26 Teradata Virtual Machine Developer Edition Installation, Configuration, and Upgrade Guide, Release 15.10

27 Chapter 3 Teradata Virtual Machine Deployment If have trouble with the configuration, you may have to add the Teradata node to the hosts file. To do that, edit /etc/hosts, and add an entry for the Teradata node in this format: ipaddress tdservername tdservernamecop1 3 On the main Viewpoint window, click Add Content. 4 Select the System Health, Node Resources, and Query Monitor portlets. 5 Click Add, and confirm that they all work. 6 If Viewpoint does not respond, ensure you have the correct IP address and, if so, try to access the server through SSH. If you cannot access the server, review Knowledge Article KAC13A25E. Knowledge Articles can be accessed through If you are unable to resolve the issue, contact Teradata Customer Service for assistance. Teradata QueryGrid The Teradata QueryGrid connector packages are included with Teradata VM, and can be installed as needed. The following table lists the folders and.rpm files: Table 1: TD Template Folder /var/opt/teradata/tvme/pkgs File tdsqlh_td x86_64.rpm tdsqlh x86_64.rpm /var/opt/teradata/tvme/pkgs/hdp tdsqlh_hdp x86_64.rpm tdsqlh_hdp x86_64.rpm tdsqlh_hdp x86_64.rpm /var/opt/teradata/tvme/pkgs/cdh tdsqlh_cdh x86_64.rpm tdsqlh_cdh x86_64.rpm Table 2: TD Template Folder /var/opt/teradata/tvme/pkgs File tdsqlh_td x86_64.rpm tdsqlh_td x86_64.rpm tdsqlh_td x86_64.rpm tdsqlh x86_64.rpm /var/opt/teradata/tvme/pkgs/hdp tdsqlh_hdp x86_64.rpm tdsqlh_hdp x86_64.rpm tdsqlh_hdp x86_64.rpm Teradata Virtual Machine Developer Edition Installation, Configuration, and Upgrade Guide, Release

28 Chapter 3 Teradata Virtual Machine Deployment Folder /var/opt/teradata/tvme/pkgs/cdh /var/opt/teradata/tvme/pkgs/t2t File tdsqlh_cdh x86_64.rpm tdsqlt x86_64.rpm tdsqlt_lic x86_64.rpm Table 3: TD Template Folder /var/opt/teradata/tvme/pkgs File tdsqlh_td x86_64.rpm tdsqlh_td x86_64.rpm tdsqlh x86_64.rpm /var/opt/teradata/tvme/pkgs/hdp tdsqlh_hdp x86_64.rpm tdsqlh_hdp x86_64.rpm tdsqlh_hdp x86_64.rpm /var/opt/teradata/tvme/pkgs/cdh /var/opt/teradata/tvme/pkgs/t2t tdsqlh_cdh x86_64.rpm tdsqlt x86_64.rpm tdsqlt_lic x86_64.rpm For more information about installing and configuring Teradata QueryGrid, consult the appropriate documentation or contact your account executive to discuss installation services. R for Data Analysis Teradata Virtual Machine includes Fortran packages on the image, allowing you to install and use R for data analysis. For more information, see SQL External Routine Programming, B Connecting with a Mainframe Computer For more information on mainframe configuration, see Teradata Director Program Reference, B , and Teradata Tools and Utilities for IBM z/os Installation Guide, B In the deploy.properties file, enter the TDP Logical Host ID in the LHID field. 2 Add the virtual machine to the appropriate MVS etc.hosts file in this format: HOST : ipaddr : vmnamentcin:: :: ipaddr vm The IP address of the VM. The name of the VM. 28 Teradata Virtual Machine Developer Edition Installation, Configuration, and Upgrade Guide, Release 15.10

29 Chapter 3 Teradata Virtual Machine Deployment NTCIn:: :: The Teradata representation of an network processor (NP) name. Note that there is no space between the VM name and the NP name, but there is a space between the second and third trailing colon. Example: HOST : : TVMEntci4:: :: 3 Edit the TDP Parm file to add the NP information using the following syntax: CONFIG NP DATABASE vmname CONFIG NP LHID logical host id START NP1 Example: CONFIG NP DATABASE TVME CONFIG NP LHID 33 START NP1 4 To confirm the deployment, ping the VM from the mainframe. Example: tso ping tvme Connecting with a Mainframe Computer after Installation Follow this procedure to configure a connection to the mainframe after the VM has been deployed. 1 Execute the configuretchn.sh script on the deployed VM: sh /var/opt/teradata/tvme/script/configuretchn.sh tdpid=lhid where LHID is the TDP Logical Host ID. Example: sh /var/opt/teradata/tvme/script/configuretchn.sh tdpid=33 Teradata Virtual Machine Developer Edition Installation, Configuration, and Upgrade Guide, Release

30 Chapter 3 Teradata Virtual Machine Deployment 30 Teradata Virtual Machine Developer Edition Installation, Configuration, and Upgrade Guide, Release 15.10

31 CHAPTER 4 Upgrading Teradata Virtual Machine Upgrading Developer Edition The upgrade process allows you to apply a major or minor database upgrade to your virtual machine, while retaining your data. You must be at Developer Edition or higher to upgrade. The process also allows you to upgrade your version of Viewpoint. Upgrades require PUT. You cannot migrate between the Base Edition and the Developer Edition. They are separate products. Note: Upgrading and replacing are different procedures. Do not use the upgrade procedure to upgrade to Developer Edition from a pre version. You must use the replace procedure for that. Follow the steps to upgrade Developer Edition or Viewpoint. 1 Obtain a Change Control number for the upgrade. 2 Download and upgrade to the latest version of PUT. 3 Use PUT to upgrade the database version. 4 Use PUT to upgrade Viewpoint, if applicable. PUT Overview PUT is a browser-based utility that simplifies Teradata Virtual Machine upgrade procedures. Use PUT to upgrade the database and Viewpoint. PUT Package TDput PUTSRC PUTTools Description TDput is the PUT application. System Readiness Check (SRC). A package of tools designed to assist with system changes. This package must be installed with PUTSRC using the PUT Install/ Upgrade Software operation after PUT is installed. Always use the latest version of PUT. All PUT packages are available from Teradata At Your Service: Teradata Virtual Machine Developer Edition Installation, Configuration, and Upgrade Guide, Release

32 Chapter 4 Upgrading Teradata Virtual Machine Downloading New PUT Packages Before using PUT, always upgrade to the most recent version. 1 Log on to 2 Click Software Downloads. 3 Click Certified Configs. 4 Under Software Patches, click Parallel Upgrade Tool (PUT). 5 At Platform, select the version of the operating system. 6 Click Submit. 7 On the Teradata PUT page, select PUTSRC, PUTTools, and TDput for download. 8 Specify values to complete the download request: Parameter Download Type Download Readme Files? User Name Site ID Change Control Number FTP Directory Value Public FTP Yes The name on your account The address on your account The Site ID for your installation The previously-obtained Change Control Number The directory on the FTP server to store the downloaded files 9 Click Submit. 10 FTP the PUT files from the Teradata FTP server to your Windows machine. 11 Decompress the files as needed. Upgrading PUT in Customer Mode Always use the most recent version of PUT. You can upgrade PUT using Customer Mode. 1 Obtain the PUT packages and place them in the Customer Mode directory: /var/opt/teradata/customermodepkgs Be sure to delete any old files from that directory before copying the PUT files there. 2 Log into PUT Customer Mode. 3 Select Install/Upgrade PUT. 4 At the Install/Upgrade Software: Customer Mode step, confirm the summary, and click Next. 32 Teradata Virtual Machine Developer Edition Installation, Configuration, and Upgrade Guide, Release 15.10

33 Chapter 4 Upgrading Teradata Virtual Machine 5 At the Finished! step, PUT displays a summary of what was upgraded. Click Finish. Upgrading the Database Always use the most current version of PUT. If you need additional PUT help, see Parallel Upgrade Tool (PUT) Reference. 1 Obtain the latest database efix or maintenance cert list: a b c d e f g h i j k l Log on to Click Software Downloads. Click Certified Configs. Under Software Patches, click Teradata Database. At Teradata Releases, select the correct release for your installation. At Target OSs, select the target operating system. Click Submit. Click Select all packages for download. Select Public FTP. Enter your User Name, , Site ID, and Change Control Number. At FTP Directory, enter the name of destination FTP directory for the.zip file containing the selected patches. Click Submit. The system sends an that includes the URL and security information you need to retrieve the files from the FTP site. m Make sure the Customer Mode source directory (/var/opt/teradata/ customermodepkgs) is empty. n Transfer the files into the Customer Mode directory of your target system: /var/opt/teradata/customermodepkgs 2 Log in to PUT Customer Mode. 3 Select Install/Upgrade Software. 4 At the Customer Mode step, confirm the summary, and click Next. 5 At the DBC Login Information Entry step, enter the password for the DBC user, and click Next. 6 At the Start of Database Down Time step, make sure the database is ready to shut down, and click Next. PUT advances to the Finished! step, where it displays a summary of what was upgraded. Teradata Virtual Machine Developer Edition Installation, Configuration, and Upgrade Guide, Release