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

Transcription

1 What would you do if you knew? Teradata Virtual Machine Base 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 Prerequisites... 5 Revision History... 5 Additional Information...6 Related Documents... 6 Related Links...6 Product Safety Information...6 Chapter 1: Base Edition Overview...7 Base Edition Description... 7 Base Edition Use Cases... 7 Chapter 2: Preparing for Teradata Virtual Machine Installation... 9 Requirements... 9 Teradata Virtual Machine Installation Components...10 Teradata Virtual Machine Templates Teradata Virtual Machine Property Files...10 Teradata Virtual Machine Scripts The pdegplsrc Packages Installing Teradata Virtual Machine...11 vsphere Essentials...12 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 Teradata Virtual Machine Base Edition Installation, Configuration, and Upgrade Guide, Release

4 Table of Contents The deploy.properties File...16 Unattended Deployment Temporal Settings Chapter 3: Teradata Virtual Machine Deployment...25 Executing the Setup Scripts SMWeb and ServiceConnect Configuration...25 ServiceConnect IP Addresses Setting Up Teradata ServiceConnect Deployment Verification Starting the Database Logging On to the Database Testing the Database Testing Viewpoint Testing Server Management...29 Teradata QueryGrid R for Data Analysis...31 Connecting with a Mainframe Computer...31 Connecting with a Mainframe Computer after Installation...32 Chapter 4: Upgrading Teradata Virtual Machine...33 Upgrading Base Edition...33 PUT Overview Downloading New PUT Packages...33 Upgrading PUT in Customer Mode Upgrading the Database Upgrading Viewpoint Teradata Virtual Machine Base Edition Installation, Configuration, and Upgrade Guide, Release 15.10

5 Preface Purpose Use the steps in this guide to install, configure, and upgrade Teradata Virtual Machine Base Edition (Base Edition). Audience This guide is intended for use by: System Administrators who configure hardware in preparation for installing Base Edition. Administrators who install, configure, and maintain Base Edition. Database and software professionals who use Base Edition, ensure the database is running, and use client applications to access the database for development and testing or production. Prerequisites Before installing Base Edition software, you must prepare the host node, including configuring virtual disks, datastores, and network connections. Revision History Date April 2016 Description Initial Release Teradata Virtual Machine Base Edition Installation, Configuration, and Upgrade Guide, Release

6 Preface Additional Information Additional Information Related Documents Title Publication ID Teradata Viewpoint User Guide B Teradata Server Management Web Services User Guide B Appliance Backup Utility Installation and User Guide B Parallel Upgrade Tool (PUT) Reference B Teradata QueryGrid Installation and User Guides Teradata Virtual Machine Frequently Asked Questions Numerous 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 Base Edition Installation, Configuration, and Upgrade Guide, Release 15.10

7 CHAPTER 1 Base Edition Overview Base Edition Description Base Edition is a customer-installable virtual Teradata Database package. It runs in a virtualized environment on third-party hardware and contains the following: SUSE Linux Enterprise Server (SLES) operating system A fully configured Teradata Database instance A virtualized version of Teradata Viewpoint, for managing the Base Edition instances A virtualized instance of the CMIC hosting Server Management (SMWeb) Support for the Appliance Backup Utility (ABU). Support for Teradata QueryGrid You must have administrative privileges on the destination VMWare environment to install and configure Base Edition virtual machines. Base Edition Use Cases Base Edition can be used in a number of contexts requiring a database solution, including the following: A Teradata development or test environment A lower-end production-capable solution An upgrade path for Teradata Express users Teradata Virtual Machine Base Edition Installation, Configuration, and Upgrade Guide, Release

8 Chapter 1 Base Edition Overview Base Edition Use Cases 8 Teradata Virtual Machine Base 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 install Base Edition. For assistance with your Site ID, contact Teradata Customer Support. Base edition has the following technical requirements. For detailed requirements, see the Base Edition Bill of Materials. Component Requirements VMware licensing A full VMware vsphere 6.0 license or VMware vsphere Essentials 6.0 license for at least one physical CPU (unlimited cores per CPU) 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 Server Management: 2 GB minimum Server Dell PowerEdge R720 or equivalent Datastores for AMP configuration Twelve 600-GB HDD (recommended) Datastore formatting VMFS 5 file system RAID RAID 1, with recommend configuration of 1 AMP on each of the 12 drives, and the thirteenth drive reserved for Teradata Database OS, Viewpoint, and Server Management deployment vsphere Client vsphere PowerCLI version 5.5 release 2 or version 6.0 Windows 7 or 2008 R2 server and vsphere client vsphere vswitches Two new vsphere standard vswitches without physical adapters in the selected ESXi host PowerCLI Windows.Net Framework 4.5 Windows PowerShell V2 or latest vsphere PowerCLI toolkit Note: Base Edition requires unique management network switches. If you are running multiple Base Edition VMs, make sure to define unique network switches for each. Teradata Virtual Machine Base Edition Installation, Configuration, and Upgrade Guide, Release

10 Chapter 2 Preparing for Teradata Virtual Machine Installation Teradata Virtual Machine Installation Components Teradata Virtual Machine Installation Components Teradata Virtual Machine installation components consist of templates, property files, scripts, and text files. Required templates contain the Teradata Database and underlying operating system. Optional templates contain Viewpoint and its underlying operating system, and Server Management. 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 Server Management 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 TVME-SM SLES11_SP1_ESXi.CMIC12.00.xx.xx-1 1 virtual core 16 GB RAM 26 GB virtual disk 3 network adapters Teradata Virtual Machine Property Files Properties File Name vmwareit.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. 10 Teradata Virtual Machine Base Edition Installation, Configuration, and Upgrade Guide, Release 15.10

11 Chapter 2 Preparing for Teradata Virtual Machine Installation Installing Teradata Virtual Machine Properties File Name deploy.properties Contents Configuration settings unique to the Teradata, Viewpoint, and Server Management virtual machines. Define the values in this file for each deployment. Teradata Virtual Machine Scripts Script deploy.ps1 DatabaseVMDeployAndConfigure.ps1 ViewpointVMDeployAndConfigure.ps1 CMICVMDeployAndConfigure.ps1 Description Parses the vmwareit.properties and deploy.properties files to ensure that all required values are present and correctly formatted, validates settings, and launches each subsequent script to deploy the components of the Teradata virtual machine. Deploys the Teradata Database and underlying operating system for the Teradata virtual machine. Deploys Viewpoint and underlying operating system for the virtual machine. Deploys Server Management for the 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 your Site ID to download and install Teradata Virtual Machine. You must be a VMWare administrator to install and configure Teradata Virtual Machine software. 1 Obtain a Change Control Number for downloading the templates and scripts. 2 Prepare the host node, including configuring virtual disks, datastores, and network connections. 3 Download and save the Base Edition templates and scripts. Teradata Virtual Machine Base Edition Installation, Configuration, and Upgrade Guide, Release

12 Chapter 2 Preparing for Teradata Virtual Machine Installation vsphere Essentials 4 If this is a new, single-server installation, install the vsphere Essentials kit. 5 If applicable, limit administration of the Teradata Virtual Machine host server to certain users. 6 If this is a new installation, set PowerCLI Script execution privileges. 7 If this is a new installation, or if your VMWare environment has changed, edit the values in the vmwareit.properties file. 8 Edit the deploy.properties file with the values for the specific Teradata Virtual Machine installation. 9 Run the Setup script to install Teradata Database, Viewpoint, and Server Management into three different virtual machines. 10 Open the IP addresses in your firewall on the network segment you allocated to the CMIC. 11 Use the Server Management portlet in Viewpoint to validate the site ID and set up any proxies. 12 If necessary, start the database. 13 Confirm that the Teradata Database installed correctly. 14 Confirm that Viewpoint installed correctly. 15 Confirm Server Management connectivity. 16 If you plan to use Teradata QueryGrid, configure the connector. 17 If you want the virtual machine to communicate with a mainframe computer, establish the connection. vsphere Essentials Before deploying any Teradata virtual machines in a single-server environment, you must install the vsphere Essentials kit, which includes an operational vcenter Server. Installation and configuration of all VMWare software, including vsphere and vcenter, is the responsibility of your VMWare Admin. Teradata cannot support your VMWare environment. Contact VMWare support if you require more information. 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 the datacenter that you defined when adding the server to vcenter as part of preparing the node. 1 Open vsphere Client. 12 Teradata Virtual Machine Base Edition Installation, Configuration, and Upgrade Guide, Release 15.10

13 Chapter 2 Preparing for Teradata Virtual Machine Installation Setting PowerCLI Script Execution Privileges 2 Log in to the vcenter Server associated with the Teradata Virtual Machine host server. 3 In the tree view, click the branch for the datacenter containing the Teradata Virtual Machine host server. 4 Click the Permissions tab. 5 In a blank area of the tab, right-click, then select Add Permission. The Assign Permissions window appears. 6 Under Assigned Role, select Administrator. 7 Under Users and Groups, click Add. The Select Users and Groups window appears. 8 From the Domain list, select the Active Directory where the accounts for the users who you want to designate as administrators exist. 9 In the list pane, select the applicable users or groups. 10 Click Add. 11 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. 4 Click Site. 5 Select the site to which this change control applies. Teradata Virtual Machine Base Edition Installation, Configuration, and Upgrade Guide, Release

14 Chapter 2 Preparing for Teradata Virtual Machine Installation Obtaining the Latest Installation Components 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 Base 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. 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. 14 Teradata Virtual Machine Base Edition Installation, Configuration, and Upgrade Guide, Release 15.10

15 Chapter 2 Preparing for Teradata Virtual Machine Installation Editing Property Files 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. 1 In a text editor, open the properties file you need to edit. The files are in /BaseEdition/. 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 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 Common Network Details vcenterserverusername vcenterserverpassword NetworkDomain NetworkPrimaryDns NetworkSecondaryDns 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. Example: vcenterserverusername=admin vcenterserverpassword=password The network domain and primary DNS (both required) and the secondary DNS (optional). Example: Teradata Virtual Machine Base Edition Installation, Configuration, and Upgrade Guide, Release

16 Chapter 2 Preparing for Teradata Virtual Machine Installation Editing Property Files Property Category Network Switch vswitch0 Network Switches vswitch1 and vswitch2 External NTP Server Settings Properties VirtualNetworkPortGroupName PrimaryPortGroupName SecondaryPortGroupName NTPServer1 NTPServer2 NTPServer3 Description 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 The virtual switches used for communication between Teradata Virtual Machine components in the network. Neither switch should have any physical adaptors. Example: PrimaryPortGroupName=Primary SecondaryPortGroupName=Secondary [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, Teradata Viewpoint, or Server Management virtual machine. Set the values in the deploy.properties file for each Teradata Virtual Machine deployment. Property Category Properties Description TVM Base Edition Virtual Machines to Deploy DeployDatabaseVM DeployViewpointVM DeployServerManagementVM The Teradata Database, Teradata Viewpoint, or Server Management 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 DeployServerManagementVM=true 16 Teradata Virtual Machine Base Edition Installation, Configuration, and Upgrade Guide, Release 15.10

17 Chapter 2 Preparing for Teradata Virtual Machine Installation Editing Property Files Property Category Properties Description TVME OVF Template File Path in the Local System DatabaseOVFFilePath ViewpointOVFFilePath ServerManagementOVFFilePath The absolute Windows file path of the template locations in the local system. Examples: DatabaseOVFFilePath=E: \TVME-15.10\Templates\TVME- TD15.10 SLES11_SP3_ESXi \TVME- TD15.10 SLES11_SP3_ESXi ovf ViewpointOVFFilePath=E: \TVME-15.11\Templates\TVME- VP SLES11_SP1_ESXi \TVME- VP SLES11_SP1_ESXi ovf ServerManagementOVFFilePath=E: \TVME-15.11\Templates\TVME- SM SP1_SLES11_ESXi.CMIC \TVME- SM SP1 SLES11_ESXi.CMIC ovf VMWare Host Details VM Names and Location ESXiHostName DbsVMName ViewpointName CMICName LocationName The name of the VMWare host. Example: ESXiHostName=esxhost01.corp.company.com The names of the virtual machines and the folder to which they should be deployed. Example: DbsVMName=TD-DBS ViewpointName=TD-VP CMICName=TD-CMIC Location=FolderName OS Datastore OSDatastore The datastore for vcenter, Teradata Database, Teradata Viewpoint, and Server Management as named on the specified ESXi host. AMPs Datastore Prefix DBS Configuration AMPsDatastorePrefix NumberOfDataDisks NumberOfAMPS DataDiskSizeGB Example: OSDatastore=LUN_OS The prefix for the AMP datastores as configured on the specified ESXi host, where an incrementing suffix such as 01, 02, and so on, is specified to distinguish each datastore. The Host should be configured for 12 datastores. Example: AMPsDatastorePrefix=LUN_ The number of data disks, number of AMPs, and data disk size. The number of data disks must be even, and the number of AMPS must equal or be 2, 3, or 4 times the number of data disks. Examples: Teradata Virtual Machine Base Edition Installation, Configuration, and Upgrade Guide, Release

18 Chapter 2 Preparing for Teradata Virtual Machine Installation Editing Property Files Property Category Properties Description NumberOfDataDisks=4 NumberOfAMPS=4 DataDiskSizeGB=300 VM Configuration NumCPU MemoryGB The amount of memory and the number of CPUs. Allocate at least 2 GB of memory for each AMP. MemoryGB must be at least 8 GB, and it must be at least twice the value of NumberOfAMPs. Examples: NumCPU=4 MemoryGB=16 TASM Values TASM The 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 Temporal Settings: Temporal TimeDateWZControl DaylightSavings TimeZoneHour TimeZoneMinute TimeZoneString Other Settings: Columnar BlockLevelCompression RowLevelSecurity Secure Zones 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. You may not use these features without the appropriate license. The fact that this feature may be included in product media or downloads, or described in documentation that you receive does not authorize you to use it without the appropriate license. Contact your Teradata Sales representative to purchase and enable this feature. See the file TeradataTimeZoneStrings.txt for the valid values for TimeZoneString. 18 Teradata Virtual Machine Base Edition Installation, Configuration, and Upgrade Guide, Release 15.10

19 Chapter 2 Preparing for Teradata Virtual Machine Installation Editing Property Files Property Category Properties Description If you plan to use the Temporal feature, you must define the NTP servers in the vmwareit.propertes file. Teradata Site ID SITE-ID Unique identifier for the Teradata Virtual Machine installation environment. Must be all uppercase with no special characters including dashes and underlining, and cannot exceed 15 characters. FSG Cache Percentage Mainframe Connectivity Static IP Address and Host Name for Database VM Static IP Address and Host Name for Viewpoint VM FSG Cache Percentage LHID IPAddressForDbsVM HostNameForDbsVM SubnetmaskForDbsVM NetworkGatewayForDbsVM IPAddressForVPVM HostNameForVPVM SubnetmaskForVPVM networkgatewayforvpvm Example: SITE-ID=CUSTOMERNAME The percentage of memory to allocate to the FSG cache, with an allowable value of 0 to 99 and a default value of 70. Example: FSGCachePercentage=70 Use this property to enable mainframe connectivity. Mainframe connectivity is available on Teradata Database and later. 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. Static IP address, host name, subnet mask, and network gateway for the Teradata Database virtual machine. The default host name is TVME. 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: IPAddressForDbsVM= HostNameForDbsVM=TVME 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. Teradata Virtual Machine Base Edition Installation, Configuration, and Upgrade Guide, Release

20 Chapter 2 Preparing for Teradata Virtual Machine Installation Editing Property Files Property Category Properties Description Static IP Address and Host Name for Server Management VM Database Login for Server Management IPAddressForCMICVM SubnetmaskForCMICVM networkgatewayforcmicvm DbsVMLogin DbsVMPassword 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= Static IP address, subnet mask, and network gateway for the Server Management (CMIC) virtual machine. The subnetmask value must be in the format of XXX.XXX.XXX.X. In HostNameForCMICVM, 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: IPAddressForCMICVM= subnetmaskforcmicvm= networkgatewayforcmicvm= Credentials required if you want to use the -force option for unattended deployment when creating only a Server Management virtual machine after deploying Teradata Database and Teradata Viewpoint virtual machines; otherwise, you must manually provided the credentials when prompted during deployment of the Server Management virtual machine. Example: DbsVMLogin=root DbsVMPassword=password 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 and deploy.properties files. Run the deployment script with a -force parameter. 20 Teradata Virtual Machine Base Edition Installation, Configuration, and Upgrade Guide, Release 15.10

21 Chapter 2 Preparing for Teradata Virtual Machine Installation Temporal Settings 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. Note: You may not use this feature without the appropriate license. The fact that this feature may be included in product media or downloads, or described in documentation that you receive does not authorize you to use it without the appropriate license. Contact your Teradata Sales representative to purchase and enable this feature. 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. If you do not know your TimeZoneString, see Teradata Database Administration, B Teradata Virtual Machine Base Edition Installation, Configuration, and Upgrade Guide, Release

22 Chapter 2 Preparing for Teradata Virtual Machine Installation Temporal Settings 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 TimeZoneString=Not Set 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=0 (Disabled) 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 Temporal data is stored in the Teradata file system in system local time. Daylight savings is observed. Temporal=true TimeDateWZControl=3 (Local) 16. System TimeZone Hour=0 17. System TimeZone Minute=0 18. System TimeZone String=America Pacific (Example) 57. TimeDateWZControl=3 (Local) 22 Teradata Virtual Machine Base Edition Installation, Configuration, and Upgrade Guide, Release 15.10

23 Chapter 2 Preparing for Teradata Virtual Machine Installation Temporal Settings Diagram Scenario 5b 5c 5d 5e Temporal Settings in the Property File 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. 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 DBS Control Setting Applied As 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) 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) Teradata Virtual Machine Base Edition Installation, Configuration, and Upgrade Guide, Release

24 Chapter 2 Preparing for Teradata Virtual Machine Installation Temporal Settings Diagram Scenario Temporal Settings in the Property File DBS Control Setting Applied As 5f 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 16. System TimeZone Hour=5 (Example) 17. System TimeZone Minute=30 (Example) 18. System TimeZone String=Not Set 57. TimeDateWZControl=2 (UTC) 24 Teradata Virtual Machine Base 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. SMWeb and ServiceConnect Configuration If you deployed a Server Management virtual machine, you must open the required IP addresses and configure Teradata ServiceConnect settings in the Viewpoint Server Teradata Virtual Machine Base Edition Installation, Configuration, and Upgrade Guide, Release

26 Chapter 3 Teradata Virtual Machine Deployment SMWeb and ServiceConnect Configuration Management portlet to complete the installation. These steps enable communication between the system and Teradata Customer Services, who can then use ServiceConnect to remotely assist with additional configuration options including the following: Configuration of other remote access models Installation and configuration of a policy server Integration with a customer RADIUS server If these options do not display, they are not available at your site. ServiceConnect IP Addresses For Teradata ServiceConnect to function properly, the following IP addresses must be open in your firewall on the network segment you have allocated to the CMIC: IP Address ServiceConnect Component serviceconnect.teradata.com scremote1.teradata.com scremote2.teradata.com scremote3.teradata.com scremote4.teradata.com scremote5.teradata.com scremote6.teradata.com Setting Up Teradata ServiceConnect Configure Teradata ServiceConnect as the final step in deploying a Server Management virtual machine. If you require a proxy server for outgoing connections, note the following when configuring the applicable option: If you enable the Proxy Auto-Configuration option, you cannot enable the HTTP Proxy or SOCKS Proxy option. However, you can complete the authentication fields for either if the.pac file points to a proxy server that requires this information. If you have a *.pac file at a known URL, you can configure it, along with any authentication for the HTTP and SOCKS servers, if required. 1 Log in to Teradata Viewpoint as administrator. 2 Click. 3 Open the Server Management portlet. 4 From the Configure list, click ServiceConnect. The Teradata ServiceConnect details appear, including the SiteID. Note: If the SiteID is not displayed, enter the value. 26 Teradata Virtual Machine Base Edition Installation, Configuration, and Upgrade Guide, Release 15.10

27 Chapter 3 Teradata Virtual Machine Deployment Deployment Verification 5 Click Create Connection. The system creates a connection, configures devices, generates an Asset Baseline, and sends an alert. 6 [Optional] If you require outgoing connections to go through a proxy server, click Advanced options and do the following: Proxy Options Auto- Configuration Description a. If you have an automatic proxy configuration script, under Proxy Auto- Configuration, select Enable. b. In the URL box, type the IP address of your proxy server. The format is server IP Address/*.pac file path. HTTP SOCKS a. Under HTTP Proxy, select Enable. b. In the Host IP Address box, type the IP address of the HTTP proxy host. The IP address must be a valid IPv4 or IPv6 address. If it is IPv4, it is pinged to ensure the connection is valid. c. In the Port box, type the port number for the HTTP proxy. d. If credential authentication is required, click Authenticate using the following information, and type the login credentials. a. Under SOCKS Proxy, select Enable. b. In the Host IP Address box, type the name or address of the SOCKS proxy host. The IP address must be a valid IPv4 or IPv6 address. If it is IPv4, it is pinged to ensure the connection is valid. c. In the Port box, type the port number for the SOCKS proxy. d. If credential authentication is required, click Authenticate using the following information, and type the login credentials. 7 Click Apply. 8 [Optional] From the Configure list, click Alerts to further configure the alerts. The Alert Actions list in the Server Management portlet displays action sets that you configure in the Alert Setup portlet. 9 Click Close. Deployment Verification After a Base Edition deployment, test the Teradata Database and, if applicable, Viewpoint and Server Management. Retain the Base Edition log files to confirm your settings. Teradata Virtual Machine Base Edition Installation, Configuration, and Upgrade Guide, Release

28 Chapter 3 Teradata Virtual Machine Deployment Deployment Verification 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. 28 Teradata Virtual Machine Base Edition Installation, Configuration, and Upgrade Guide, Release 15.10

29 Chapter 3 Teradata Virtual Machine Deployment Teradata QueryGrid 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. Testing Server Management Follow the steps below to test the connectivity for Server Management: 1 Access Teradata At Your Service at and sign on. 2 At Incidents, click Create. 3 Click Site. 4 Select the site for this installation, and click the green arrow. 5 At Incident Type, select Installation, and click the green arrow. 6 At Product Area, select Teradata Database Software, and click the green arrow. 7 At Problem Type, select Other/Not Sure, and click the green arrow. 8 At Synopsis, enter Request to Complete TVMBE CMIC Configuration and Test. 9 At Description, list your address. This address will receive the confirmation of successful configuration. 10 Click Submit the incident. 11 Monitor the incident, then close it when Teradata Customer Services validates the connection. 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: Teradata Virtual Machine Base Edition Installation, Configuration, and Upgrade Guide, Release

30 Chapter 3 Teradata Virtual Machine Deployment Teradata QueryGrid 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 /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 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 30 Teradata Virtual Machine Base Edition Installation, Configuration, and Upgrade Guide, Release 15.10