What would you do if you knew?™ Teradata Database on VMware Developer Tier Getting Started Guide Deployer Release 3.01 B035-5938-097K September 2017 The product or products described in this book are licensed products of Teradata Corporation or its affiliates. Teradata, Aster, BYNET, Claraview, DecisionCast, IntelliBase, IntelliCloud, IntelliFlex, QueryGrid, SQL-MapReduce, Teradata Decision Experts, "Teradata Labs" logo, Teradata ServiceConnect, and Teradata Source Experts 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. Amazon Web Services, AWS, Amazon Elastic Compute Cloud, Amazon EC2, Amazon Simple Storage Service, Amazon S3, AWS CloudFormation, and AWS Marketplace are trademarks of Amazon.com, Inc. or its affiliates in the United States and/or other countries. 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. CENTOS is a trademark of Red Hat, Inc., registered in the U.S. and other countries. Cloudera and CDH are trademarks or registered trademarks of Cloudera Inc. in the United States, and in jurisdictions throughout the world. Data Domain, EMC, PowerPath, SRDF, and Symmetrix are either registered trademarks or trademarks of EMC Corporation in the United States and/or other countries. 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, IBM Spectrum Protect, and z/OS are trademarks or 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 of Quest Software, Inc. 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. Sentinel® is a registered trademark of SafeNet, 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. 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. Veritas, the Veritas Logo and NetBackup are trademarks or registered trademarks of Veritas Technologies LLC or its affiliates in the U.S. 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 e-mail:
[email protected] 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 - 2017 by Teradata. All Rights Reserved. Preface Purpose Use the information in this guide to install and configure Teradata Database on VMware. Audience This guide is intended for use by: • System Administrators who configure hardware in preparation for installing Teradata Database on VMware. • Administrators who install and configure Teradata Database on VMware. • Database and software professionals who use Teradata Database on VMware, are responsible for ensuring the database is running, and use client applications to access the database for development and testing. Prerequisites Before installing software, you must prepare the host nodes, including configuring virtual disks, datastores, and network connections. This guide assumes a solid understanding of virtualization, including experience with: • Configuring hardware in preparation for installing Teradata Database on VMware. • Managing vSphere, vCenter, and ESXi technology. • Terms such as standard switches, datastores, VM templates, ova, ovf, and so forth. • Network setup for Teradata Database nodes for a bare metal installation and how it relates to a vSphere installation. • Software applications that access Teradata Database for development, testing, or production. • Teradata Database configurations including terminology. See VMware and Teradata Terminology. Revision History Date Description September 2017 • Added support for Teradata Database 16.10, Teradata Ecosystem Manager, and Server Management. • Updated the Teradata Database on VMware template versions. • Added the following new chapter and topics: Teradata Database on VMware Getting Started Guide, Deployer Release 3.01 3 Preface Date Description ∘ Supported Software for Teradata Database on VMware ∘ Teradata Database Features ∘ Preparing the ova Templates ∘ Preparing the Templates in the Local System ∘ Installing and Configuring Other Teradata Applications (chapter) ∘ Installing and Configuring Teradata Studio June 2017 • Renamed this book to Teradata Database on VMware Developer Tier Getting Started Guide. Changed terminology from edition to tier. • Changed to using a deployment executable file instead of deployment scripts to deploy the Teradata Database on VMware software. • Added VMware administrator privileges you need to install and configure the Teradata Database on VMware software. • Updated the information about database sizing. • Added instructions on running PowerCLI as Administrator. • Changed Teradata Data Stream Utility to Teradata Data Stream Controller, which is the name of the component within the DSU product. January 2017 • Updated to add support for Teradata Database 16.00 and remove support for Teradata Database 15.00. November 2016 • Updated to reflect availability of Teradata Database on VMware Development Edition at http://downloads.teradata.com/. • References to "Base Edition" now refer to "Enterprise Edition." September 2016 Initial release. This book was previously known as Teradata Virtual Machine Developer Edition Installation, Configuration, and Upgrade Guide. Supported Releases This guide applies to the following releases: • Teradata Database 16.10 • Teradata Database 15.10 Additional Information Related Documents Title Publication ID Data Stream Utility Installation, Configuration, and Upgrade Guide for B035-3153 Customers 4 Teradata Database on VMware Getting Started Guide, Deployer Release 3.01 Preface Title Publication ID Parallel Upgrade Tool (PUT) Reference B035-5716 Security Administration B035-1100 SQL Data Definition Language Syntax and Examples B035-1144 SQL External Routine Programming B035-1147 Temporal Table Support B035-1182 Teradata Database Administration B035-1093 Teradata Database Node Software Migration Guide Linux B035-5942 Teradata Database on VMware Base, Advanced, Enterprise Tiers Getting B035-5958 Started Guide Teradata Director Program Reference B035-2416 Teradata Ecosystem Manager User Guide B035-3201 Teradata Server Management Web Services User Guide B035-5350 Teradata Tools and Utilities for IBM z/OS Installation Guide B035-3128 Teradata Viewpoint User Guide B035-2206 Utilities B035-1102 Related Links URL Description http://www.teradata.com External site for product, service, resource, support, and other customer information. http://www.info.teradata.com External site for published Teradata customer documentation. http://community.teradata.com/ Community-based product forum for Teradata Database on VMware. tdvm 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. Teradata Database on VMware Getting Started Guide, Deployer Release 3.01 5 Deployer Release 3.Preface 6 Teradata Database on VMware Getting Started Guide.01 . It contains a repository for all backup and restore job definitions and as well as related configuration details for Teradata systems and backup targets. and control of both single and multi-system environments to let you more effectively manage every part of your data warehouse environment. see Teradata Database License Tiers. CHAPTER 1 Overview Teradata Database on VMware Teradata Database on VMware is a SUSE Linux Enterprise Server (SLES) operating system and Teradata Database packaged into a virtual container that runs in a virtualized environment on third-party hardware. You must have administrative privileges on the destination VMware environment to install and configure the virtual machines. Software Name Description Teradata Database Provides the same full-feature data warehouse software that powers analytics at many of the world's greatest companies. Supported Software for Teradata Database on VMware The following is a list of Teradata supported software for Teradata Database on VMware. hardware configuration scripts. Deployer Release 3. This software is bundled with Teradata Database. An additional cost applies to some of the following software. Teradata Data Stream Controller Provides administrative functions and metadata storage and is a key component of the backup and restore of Teradata systems in the public cloud. The Teradata Database on VMware software consists of properties file. and a deployment executable file. Teradata Parallel Upgrade Tool Provides a way to upgrade Teradata Database and other Teradata software. Teradata Ecosystem Manager Provides an end-to-end approach to meeting application service level agreements through monitoring. Teradata Database on VMware Getting Started Guide.01 7 . The product previously known as Teradata Virtual Machine is now known as Teradata Database on VMware. and is available with local and attached storage. administration. For a list. The Data Stream Controller (DSC) is an administrative server required to enable object-level backup and restore of the Teradata Database. and management tasks on Teradata Databases. The Base. Advanced. Teradata Viewpoint Provides a web-based management portal for Teradata performance and health management which is easy to use. and improving your overall Teradata system performance. This software is bundled with but installed and configured separately from Teradata Database. This software is obtained from Teradata Community and is installed and configured separately from other software components. Teradata Aster Databases. High availability requires at least two CMICs. which is included in certain versions of Teradata Viewpoint. Teradata Studio Provides a desktop tool for performing database administration. Teradata Data Lab. data validation. and as a sandbox for Teradata Database users. Each tier differs in scalability and performance. query development. Developer can be used for proof of concepts. Multiple VMs (CMICs) provide high availability and management of larger database systems. such as moving massive volumes of data and accessing multiple data sources in parallel. Teradata Tools and Utilities Provides utilities and libraries for integrating your Teradata system into your enterprise and streamlining the daily data warehouse management tasks. Deployer Release 3. Introduction to Teradata Database License Tiers Teradata Database on VMware offers four database license tiers depending on your use case. development and testing. For more information. Teradata Database on VMware supports multiple Server Management VMs. Teradata Server Management Monitors the VM and generates alerts related to database and operating system errors and operational state changes. 8 Teradata Database on VMware Getting Started Guide. It provides a consistent interface using configurable portlets which allows you to customize your own systems management dashboard.Chapter 1: Overview Software Name Description Teradata REST Services Provides an interface to Teradata Database allowing application developers a simplified. and Enterprise Tiers can be used as an upgrade path from Teradata Express. see Teradata Database on VMware Developer Tier Getting Started Guide. and Hadoop systems. This book is for the Developer tier. modern interface to connect to data from a web page or application. Events that affect the operation of the system generate alerts. allows you to provision and manage analytic workspaces in the Teradata data warehouse.01 . A free Developer tier is also available and can be used for evaluation purposes. Each CMIC can manage up to 70 nodes with reserve capacity to manage an additional 70 failover nodes from another CMIC. Chapter 1: Overview Each tier is unique in what it offers in the following areas: • Amount of system concurrency and number of nodes • Teradata Database features • Teradata Database software applications that are available at no additional cost • Level of customer support For a list of what is offered in each tier. it operates as a fully functional instance of the configured Teradata Database. you must install a new version. Deployer Release 3. or access TaYS with this tier. You cannot upgrade the Teradata software. see Teradata Database License Tiers. Teradata Database on VMware Base.01 9 . apply software updates. Community-driven customer support is available for Developer at http:// community. Advanced. Teradata Database License Tiers Teradata Database on VMware offers license tiers that include the rights to use the software listed. When it is deployed. You can apply software updates to the Teradata software on these tiers and access TaYS for assistance. and Enterprise come with Teradata Premier Software Support.teradata.com/tdvm. To use a later version of Developer. Developer Base Advanced Enterprise Customer Support Support type Community Premier Premier Premier Scalability System concurrency limit 2 15 Unlimited Unlimited Node limit 2 128 128 128 AMPs/vNode 4 6 to 12 6 to 12 6 to 12 Maximum database size 6 TB Unlimited Unlimited Unlimited Database Features Columnar ● ● ● ● Temporal ● ● ● ● Teradata Database on VMware Getting Started Guide. The Developer tier is free and is for evaluation purposes. resulting in a loss of data. Deployer Release 3.Chapter 1: Overview Developer Base Advanced Enterprise Row-level Security ● ● ● ● Secure Zones ● ● ● ● Workload Management TIWM TASM Applications Available at No Additional Cost Teradata Ecosystem Manager ● ● ● ● Teradata Data Stream Controller (a ● ● ● ● component of Teradata Data Stream Utility) Teradata REST Services ● ● ● ● Teradata Server Management ● ● ● ● Teradata Studio ● ● ● ● Teradata Tools and Utilities. connects VMs to the physical network. vSphere links VMs to each other within a single host. VMware vCenter vCenter is a server that is installed on either Linux or Windows and provides central management of VMs and ESXi hosts. It is a hypervisor that defines processor. Each VM represents a complete system. ● ● ● ● including Teradata Parallel Transporter Teradata Viewpoint (Single ● ● ● ● Teradata System) VMware and Teradata Terminology You should be familiar with the following terms regarding VMware and virtualization. and networking resources into multiple VMs that run applications. ESXi is installed directly on the server hardware. storage. networking. memory. and provides networking for the management interface which runs management services for vSphere hosts. VMware or Virtualization Term Description VMware vSphere VMware vSphere as a suite of products that provides network virtualization services to hosts and VMs. memory.01 . storage. with processors. VMware ESXi ESXi is also a component of vSphere. joins VMkernel services to the physical network. ESXi partitions a physical server (pNode) into multiple secure VMs (vNodes) that run on the same physical server. and BIOS so that the operating system and applications can be installed 10 Teradata Database on VMware Getting Started Guide. inserting a virtualization layer between the hardware and the operating system. A single vNode corresponds to a single VM that runs Teradata software. VMs are also completely isolated from each other by the virtualization layer to prevent a crash or configuration error in one VM from affecting the others. Parallel Database Extensions (PDE). Teradata nodes can be either physical or virtual. Deployer Release 3. and an operating system. as defined through the ESXi hypervisor. Requirements The minimum requirements for hardware. Teradata Database on VMware requires hyperthreading be enabled. vSphere Virtual Switch The vSphere virtual switch lets you set up VM access switching from a centralized interface so you can provision. Physical Node (pNode) A pNode is a physical machine running in a data center. During deployment. Teradata software. and monitor virtual networking across multiple hosts and clusters. and so on. One pNode corresponds to a single ESXi host or to the actual hardware. Ensure all pNodes are connected identically to allow vNode TPA instances to be deployed to any ESXi host. pNodes can have multiple vNodes. such as to one Dell 720. Requirements Component Minimum Requirements (unless noted) Developer Tier • Maximum Node Count: 2 • System Concurrency Limit: 2 • AMPs/vNode: 4 • Maximum Database Size: 6 TB Teradata Database on VMware Getting Started Guide.01 11 . You should understand the following Teradata terminology. Chapter 1: Overview VMware or Virtualization Term Description and run in the VM without modification. Virtual Node (vNode) A vNode is a virtual node running on a pNode in a data center. vCPU A virtual CPU corresponds to one hyperthreaded core. administer. and virtualization software are described in the table below. 730. CPUs and memory are checked to ensure they are the same on all pNodes containing vNode TPA instances. Teradata Terminology Description Teradata Node A Teradata node requires three pieces of software: a Trusted Parallel Application (TPA). The Teradata Database is classified as a TPA. IT. Hyper-threading (HT) must be enabled.01 . all of its virtual disks for the database are created on the same datastore where the VM is deployed. there are 2. See The common.properties. For each TPA VM.json file. Deployer Release 3. Server Dell PowerEdge R720xd/R730xd.json File.IT.properties. or an HP Gen9 or similar system. You can change it to 4 by setting the PhysicalCoresPerTPA to 2 in the common.Chapter 1: Overview Component Minimum Requirements (unless noted) vCPU • Teradata Database (TPA): 2 or 4 By default.5 release 2 and later 12 Teradata Database on VMware Getting Started Guide. • Data Stream Controller: 4 • Teradata Ecosystem Manager: 4 • Teradata Viewpoint: 1 • Server Management: 2 Memory • Teradata Database (TPA): 8 GiB • Data Stream Controller: 16 GiB • Teradata Ecosystem Manager: 32 GB • Teradata Viewpoint: 16 GiB • Server Management (CMIC): 16 GiB Datastores for database Minimum: 1 datastore where all the TPA VMs are deployed on the same storage datastore. Maximum: 2 datastores where the maximum number (2) of TPA VMs are deployed on different datastores. Datastore formatting VMFS 5 file system Datastore space for Total size of all drives in each image: template deployment • Teradata Database (TPA): 200 GB • Data Stream Controller: 500 GB • Teradata Ecosystem Manager: 500 GB • Teradata Viewpoint: 450 GB • Server Management (CMIC): 26 GB RAID RAID-1 LUNs recommended. Network • BYNET: Two 10 GB networks to support redundancy • Server Management: Two 10 GB separate (isolated) physical networks for CMIC connectivity • DSC: 10 GB separate network VM deployment sizes • Teradata Database (TPA): 200 GB (187 GiB) • Data Stream Controller: 500 GB • Teradata Ecosystem Manager: 500 GB • Server Management (CMIC): 26 GB • Teradata Viewpoint: 456 GB VMware ESXi ESXi 5. 5 release 2 and later.Config.EditDevice VirtualMachine.1 ∘ 64 bit Windows 7 SP1 VMware vSphere One vSphere standard vSwitch for public network.AddRemoveDevice VirtualMachine. If you do not have full VMware administrator privileges. your VMware administrator must set the following minimum permissions in vCenter for you.Config. PowerCLI • PowerCLI 5.Config.Net Framework 4.5 and later • Windows . Other browsers may not work properly with the VMware vSphere Client.0 license for at least one physical CPU (unlimited cores per CPU) VMware vCenter vCenter 5.AddNewDisk VirtualMachine. Chapter 1: Overview Component Minimum Requirements (unless noted) VMware licensing A full VMware vSphere 6. as an individual user.AllocateSpace Network.Config.Config.Assign Resource.Anonymous System.Memory VirtualMachine.Config.Execute Teradata Database on VMware Getting Started Guide. vSwitches Note: One extra vSphere standard vSwitch for DSC network.5 release 2 and later VMware vSphere Client • VMware vSphere Client version 5. Deployer Release 3.GuestOperations. using the Mozilla Firefox Extended Support Release (ESR) Web browser.Settings VirtualMachine.5 • Windows PowerShell 4 and later • Requires either a Windows workstation or laptop to run PowerCLI against the vCenter VMware Administrator Privileges You must have VMware administrator privileges to install and configure Teradata Database on VMware software.01 13 .View VirtualMachine.CPUCount VirtualMachine.Read System.AssignVMToPool System.Resource VirtualMachine.0 license or VMware vSphere Essentials 6. or for your role: Datastore. • Server: ∘ 64 bit Windows Server 2012 R2 ∘ 64 bit Windows Server 2008 R2 SP1 • Workstation: ∘ 64 bit Windows 8.Config. Teradata Database on VMware supports local virtual switches so each ESXi host must have local virtual switches for the BYNET.DeployTemplate VirtualMachine.Interact.Chapter 1: Overview VirtualMachine. you must input the gateway and public_submask properties in the common.CreateFromExisting VirtualMachine.PowerOff VirtualMachine.Interact. Server Management VM. The maximum database size allowed is 6144 GB.MarkAsTemplate Database Sizing The total size of the Teradata Database system is (Size of DBS Virtual Disks in GB) * 2 (because there are two DBS virtual disks in a TPA node). If deploying additional software.PowerOn VirtualMachine.GuestOperations.GuestOperations. Deployer Release 3. Note: You can have up to two TPA nodes.Modify VirtualMachine. Note: The DSC virtual switch must have maximum transmit unit (MTU) value of 9000.Delete VirtualMachine.01 .Inventory.Provisioning.Inventory. and DSC. If you select DHCP and the vCenter server has DHCP not configured with the default gateway.Provisioning.Reset VirtualMachine.IT. increase memory as follows: Deploying Additional Memory (GB) DSC 16 Teradata Ecosystem Manager 32 Server Management 16 Teradata Viewpoint 16 14 Teradata Database on VMware Getting Started Guide.Query VirtualMachine. Note: The Server Management virtual switch must have maximum transmit (MTU) value of 1500.json file.Interact. Memory Considerations The Developer tier requires 8 GB of memory by default and cannot be altered in the Developer tier deployment executable file. Network Considerations The Developer Tier supports both static and DHCP network protocols.properties. and seconds (2 digits) when the template was created by Teradata. text files.00. I/O. The download file names listed below are appended with 14 numbers.06. Type Download File Name Default Configuration of the Template Teradata Database Teradata_Database_16. • Templates are ready to use and include defaults for disk space and configuration. day (2 digits).03_SLES11_SP3_on_VMware • 8 GB RAM System • FSG cache setting: 90% • 187 GB operating system disk Teradata Database on VMware Getting Started Guide.10.com.01 15 . Note: After the database is deployed. go to https://downloads. there are 4 AMPs per node. Templates You will use Teradata Database on VMware templates to create a VM instance. DSC. By default. managing 2 pdisks.teradata. hours (2 digits). CHAPTER 2 Preparing for Installation Installation Components Teradata Database on VMware installation components consist of templates. When you download these templates. It is preferable to deploy your templates from vCenter because it will be faster. Ecosystem Manager. the only way to change settings is to run the removevms command and run the deploy command again. Deployer Release 3. If you deploy from your desktop PC you will be constrained by the connection to your data center. month (2 digits). representing the year (4 digits). minutes (2 digits). and Server Management.10. AMPs. • The properties files define configuration settings for the overall Teradata Database on VMware environment and the specific virtual machines. network connections. you can put them in the vCenter or in a local folder on your desktop PC. • Required templates contain the Teradata Database and underlying operating system. To download the software. • An executable file deploys the Teradata VM based on the configuration information in the property files. and memory. and a deployment executable file. • Text files are used in time zone settings.03_SLES11_SP3_on_VMware • 1 virtual core and Operating Teradata_Database_15. property files. • Optional templates contain Viewpoint and its underlying operating system. Deployer Release 3.01 . Define the values in this file for each deployment. Deployment Executable File An executable file deploys the Teradata VM based on the configuration information in the property files.00_SLES11_SP3_on_VMware • 4 virtual cores Ecosystem • 32 GB RAM Manager • 3 virtual disks: one 187 GB operating system disk and two 150 GB for the EM repository.Chapter 2: Preparing for Installation Type Download File Name Default Configuration of the Template Teradata Teradata_Viewpoint_16.json Defines the VMware vSphere configuration settings common across Teradata Database on VMware VMs.IT. Server Teradata_CMIC_12.00_SLES11_SP3_on_VMware • 1 virtual core Management • 16 GB RAM • 26 GB virtual disk Properties Files Properties File Name Description common.05.03.IT.json Defines the specifications needed by the deployment executable file to install and configure the VMs. Teradata Teradata_EM_16.00.10. node.10.00.10. If you have multiple VMs on one VMware vSphere server.properties.00_SLES11_SP3_on_VMware • 1 virtual core Viewpoint and • 16 GB RAM Operating System • 187 GB operating system disk • 256 GB data disk Data Stream Teradata_DSC_16.properties. 16 Teradata Database on VMware Getting Started Guide.IT. the common. Configure the values in this file each time something in the virtual environment changes.json properties file is unique for each VM.00_SLES11_SP3_on_VMware • 4 virtual cores Controller • 16 GB RAM • 3 virtual disks: one 187 GB operating system disk and two 150 GB for the DSC repository.00.properties. ignore the message as it should not cause an issue. and the script to create the datastores. and DSC. you cannot upgrade the Teradata software.properties.teradata. 1. or if your VMware environment has changed.json file with the values for the specific Teradata Virtual Machine installation. 4. 5. Teradata Database on VMware Getting Started Guide. 13. edit the values in the common. 11.properties. install the vSphere kit. If this is a new. 6. If this is a new installation. If necessary. 9. Community-driven customer support is available for Developer at http:// community. configure it. choose the vCenter.teradata. including vSphere and vCenter. Decide the location of the templates: vCenter or in the local system. see Installing and Configuring Other Teradata Applications. is the responsibility of your VMware administrator.IT. See Preparing the ova Templates or Preparing the Templates in the Local System. For the quickest deployment. 8. Script Description tdc.properties.com/tdvm.json files to ensure all required values are present and correctly formatted. Chapter 2: Preparing for Installation Note: If you receive an iex message when running this executable file. or access TaYS with this tier.IT.IT. You must prepare the templates before the initial deployment.properties. including configuring virtual disks and network connections. 10. start the database. Run the deployment executable file to install Teradata Database. Download the Teradata Database on VMware Developer Tier installation components from Teradata Downloads: http://downloads. Confirm that the Teradata Database installed correctly.deploy. establish the connection. Decide if you want to install other Teradata applications. single-server installation. and launches each subsequent command to deploy the components for the Teradata VM. Installation and configuration of all VMware software. apply software updates.exe Parses the common. 2. Deployer Release 3. For information. which includes an operational vCenter Server.com/ 3. 12. validates settings. 7. you must install the vSphere kit.json and node. set PowerCLI execution privileges. If this is a new installation. If you plan to use DSC. If you want the virtual machine to communicate with a mainframe computer. Teradata Viewpoint.json file. Confirm that Viewpoint installed correctly.IT. vSphere Before deploying any Teradata VM in a single-server environment. Prepare the host node.01 17 . Edit the node. Installation Process Since Developer is free. Teradata Database features that are enabled by default and are automatically installed and configured are not included in the table below. you still need to install and configure it. Not all features listed below are included in all Teradata Database tiers. If you are running this command for the first time. Enabled by Installation and Database Feature Description Default Configuration Documentation Block-Level Stores data blocks in Yes Automatic Teradata Database Compression compressed format to Although this Administration save storage space and feature is disabled improve performance. If you are prompted to confirm the change. • Manual indicates you must install and configure the feature using the Teradata Database documentation. Features that require Teradata Customer Support to enable a feature are noted. Although the package is included in the Teradata Database VM. Deployer Release 3. you must set the PowerCLI execution privileges to allow the unsigned but Teradata-certified deployment executable file to be run. see the Documentation column. 3. Fallback is mandatory for all Teradata Database license tiers and cannot be disabled. but not limited to. similar to on-premises systems. 1. 2. Setting PowerCLI Execution Privileges If this is a new installation of PowerCLI. Teradata Database Features Teradata Database on VMware offers many Teradata Database features including. If a User Account Control prompt appears. For information on how to install and configure the listed features. The following terms are used in the table below: • Automatic indicates you do not have to install or configure the feature and can begin using the feature after a Teradata Database VM is launched.Chapter 2: Preparing for Installation Running PowerCLI as Administrator The PowerCLI shell must be run as a user with administrator privileges. restart the PowerCLI terminal. See Teradata Database License Tiers. enter Y or A.01 . 1. 18 Teradata Database on VMware Getting Started Guide. Database Option Management The Teradata private cloud offers the same features that come with an on-premises Teradata Database system with a couple of exceptions. Navigate to VMware vSphere PowerCLI from your Desktop or the Start menu. click Accept. run: Set-ExecutionPolicy -ExecutionPolicy bypass 2. those listed in this topic. 3. In a PowerCLI command window. Right-click VMware vSphere PowerCLI and select Run as administrator. 10. Teradata Database on VMware Getting Started Guide. Teradata Provides the ability to No Automatic SQL Data Definition Columnar partition a table or join Must be Language Syntax and index by column. Fallback Protects data in case of Yes Automatic SQL Data Definition AMP vproc failure. it is enabled by default for private cloud.01 19 . Deployer Release 3. Examples See Release Summary for Teradata Database 14.0. Teradata Provides built-in No Manual Temporal Table Support Temporal capabilities that are Enable at the time required in a temporal you deploy.0. Advanced. Chapter 2: Preparing for Installation Enabled by Installation and Database Feature Description Default Configuration Documentation See Release Summary for by default for on- Teradata Database 14. See Release Summary for Teradata Database 14. available from https:// most frequently used data tays. See Release Summary for Teradata Database 15.10 Teradata Row.com is kept in memory.0. allows you No Automatic Security Administration Level Security to restrict data access by row in the Teradata Database. Memory Orange Book memory by ensuring the to enable. and Enterprise tiers. database management This feature is system. available only for Base. premises. See Release Summary for Teradata Database 14. If purchased. Teradata Speeds query No Manual • Utilities Intelligent performance and Contact Teradata Must be • Teradata Intelligent Memory maximizes system Customer Support configured. Language Syntax and See Introduction to Examples Teradata. configured.teradata. Teradata Secure Provides grouping of user No Automatic Security Administration Zones and database hierarchies into separate database partitions with restriction of user access to one or more zones. properties.IT. Property Category Properties Description Teradata System TDsystemname The name of the Teradata System. This setting is the name specified when you created the vSwitch in vSphere. Unless otherwise indicated.com Public Virtual public_vswitch The physical adapter with port group for the virtual Switches network. Setting Example: public_submask:192. 2. 1.json file only once unless something in your virtual environment changes.IT. Name Domain Setting domain The domain of the system being deployed which will be placed into the /etc/hosts file. The second is for redundancy and performance in MPP systems. Public Submask public_submask The public submask name in dot-decimal notation. The setting should be empty for single-node systems.properties. The default setting is VM Network. These Switches cmic_vswitch2 are only used in MPP systems with server management.properties. Example: public_vswitch:VM Network BYNET Virtual byn_vswitch1 The labels of the BYNET switches.json File The common. The files are in C:\mylocation\Teradata_Deployer\Properties. Example: 20 Teradata Database on VMware Getting Started Guide.company. Edit the node. Example: domain:corp.IT. This setting is the name specified when you created the vSwitch in vSphere. Deployer Release 3.properties. The common. Save the file. Configure the settings in this file each time something in the virtual environment changes. DSC Virtual dsu_vswitch The label of the DSC switch. This setting is the name Switch specified when you created the vSwitch in vSphere.IT. CMIC Virtual cmic_vswitch1 The labels of the server management switches.json file defines the VMware vSphere configuration settings common across all Teradata Database on VMware deployments. open and update the properties file you need to edit. The second is for redundancy and performance in MPP systems.json file before deploying each Teradata virtual machine.Chapter 2: Preparing for Installation Editing Property Files Edit the common. The first is required Switches byn_vswitch2 in MPP systems.253.168. In a text or JSON editor.0 Gateway Setting gateway The gateway name or IP address.01 . all property settings are required. 01 21 .1. Physical Disk pdiskSizeGB The size of the Teradata Database system pdisks. System Settings dns2 Examples: dns1:192.26.0. Examples: OSTimeZone=GMT+11 OSTimeZone=US/Eastern For additional Teradata time zone information.company. however the ntp2 server is optional. See the file LinuxTimeZoneStrings. If you do not plan to use it. Examples: ntp1:time00. accept the default of TemporalTimeDateWZControl false.company. TemporalTimeZoneString Since Developer is free.256 External NTP ntp1 The host name or IP address of the ntp1 server is Server Settings ntp2 required. If you did not enable it before deployment. Example: Temporal:false TemporalDaylightSavings:false TemporalTimeDateWZControl:0 TemporalTimeZoneHour:0 TemporalTimeZoneMinute:0 TemporalTimeZoneString:America Pacific Teradata Database on VMware Getting Started Guide. Time Zone Setting OSTimeZone [Optional] The time zone of the VM. change the setting to TemporalDaylightSavings true.txt for the valid settings for OSTimeZone.com You must configure the NTP servers if you plan to use the Temporal feature. Enter either a fixed time zone displacement from GMT or the time zone file name. Refer to Temporal Settings. you must redeploy TemporalTimeZoneMinute the VM to enable it. no Teradata Customer Support is available.256 [Optional] dns2:192. the database time zone syncs with the operating system. The default time zone is US/Pacific.com ntp2:time01.23. Chapter 2: Preparing for Installation Property Category Properties Description gateway:10. Settings Example: pdiskSizeGB:800 Temporal Settings Temporal If you plan to use Temporal. If you are not enabling Temporal. TemporalTimeZoneHour You must enable Temporal before deployment. see Temporal Time Zone Strings.168.254 Domain Name dns1 The DNS name or IP address. Deployer Release 3.168. "gateway": "10. Example: MainframeLHID:-1 Folder Setting Folder Folder name where the VM is being deployed on the vSphere server. "OSTimeZone": "US/Eastern". Columnar must be purchased to be enabled.8.0".254".json File Use the following sample common. "ntp2": "time01. the IP address must be static. "TemporalTimeZoneString": "America Pacific". 22 Teradata Database on VMware Getting Started Guide. { "TDsystemname": "".com".company-domain.properties. "dns2": "153.65.01 . Replace the sample data after the colon (:) with your own. Deployer Release 3.200". "dns1": "153. "TemporalTimeDateWZControl": 0. "pdiskSizeGB": "800".254.251.29. IP Address Setting IPAddressSetting Indicates whether to use a static or dynamic IP address.64. Row Level Security. Sample common. Note: Secure Zones is supported on Teradata Database 15. "Temporal": "FALSE". The Settings default is -1 to indicate the deployed system will not connect to a mainframe.IT. and Secure Database Feature RowLevelSecurity Zones are Teradata Database features that can be Settings Columnar enabled by setting it to true. "byn_vswitch2": "byn_vswitch2".company-domain. "ntp1": "time00.com". "public_vswitch": "VM Network".com". "TemporalTimeZoneMinute": 0.10 and later. accept the default of false. "byn_vswitch1": "byn_vswitch1". "cmic_vswitch1": "cmic_vswitch1".json file as a template for creating your own. Mainframe MainframeLHID The logical Host ID for mainframe connectivity. "cmic_vswitch2": "cmic_vswitch2".10". "TemporalDaylightSavings": "FALSE".company-domain. "TemporalTimeZoneHour": 0.Chapter 2: Preparing for Installation Property Category Properties Description Other Teradata SecureZones [Optional] Columnar. If you do not plan to use a feature. "public_submask": "255.25.properties. "SecureZones": "FALSE".IT. "domain": "labs. For a two node MPP deployment. "dsu_vswitch": "dsu_vswitch".255. com ESXi Datastore OS_Datastore ESXi datastore where this VM instance will reside. all property settings are required.json File The node.IT. Teradata Ecosystem Manager.json file for each Teradata Database on VMware deployment. Unless otherwise indicated. Deployer Release 3. DSC.properties. eth0 is not required. "IPAddressSetting":"static" } The node.json file contains the specifications needed by the deployment executable file to install and configure a Teradata Database or Teradata Viewpoint VM. Examples: vmName:TD-DBS vmName:TD-VP vmName:TD-DSC vmName:TD-EM vmName:TD-CMIC Ethernet eth0 Use only static IP4 addresses. This datastore is only used for the VM instances and for Teradata Database storage. and Server Management image to deploy. Network If IPAddressSetting is dhcp. Chapter 2: Preparing for Installation "RowLevelSecurity": "FALSE".01 23 . "Columnar": "FALSE". DSC. VM Name vmName Name of the Teradata Database. and Server Management. "Folder":"". For example: Details ESXiHost:esxhost01. Set the values in the node. VM Types to vmType Virtual machine type of the Teradata Database. Teradata Viewpoint.company. Examples: vmType:tpa for a database VM vmType:vp for a Viewpoint VM vmType:dsu for a DSC VM vmType:em for an Ecosystem Manager VM vmType:cmic for a Server Management VM Template File Template Refer to one of the following for the Windows file path to the template Path location: Teradata Database on VMware Getting Started Guide. Teradata Viewpoint.properties.corp.IT.datastore All TPA VMs are restricted to share the same ESXi host in the Developer tier.IT. "MainframeLHID":"-1". For example: esxhost01.properties. Property Properties Description Category VMware Host ESXiHost Name of the VMware host. Deploy Teradata Ecosystem Manager. modify the name of the VM to make it unique (for example. select Local file. and select All vCenter Actions > Deploy OVF Template. verify the . ensure it has been upgraded to the latest version. 4. then select Thin Provision from the Select virtual disk format menu if you want to speed up the clone time and save space in the datastore. Deployer Release 3. 3. and click Next. Log in to the vSphere Client using your login credentials. C:\powercli6\templates \SP3\Teradata_Database_16. c) Under Review details.10. d) Under the Name column. right-click the VM you cloned. do the following to verify the VM was cloned. f) Verify all information.Chapter 2: Preparing for Installation Property Properties Description Category • vCenter: Preparing the ova Templates • Local system: Preparing the Templates in the Local System Preparing the ova Templates Prerequisite Check that you have installed the VMware Client Integration Plug-in on your workstation. Under Inventories. 1. If you have the plug-in installed.ova b) Click Next. Teradata_Database_16. Under the Name column. c) Click Virtual Machines. 24 Teradata Database on VMware Getting Started Guide. and click Finish to clone the template. For example. use either Internet Explorer 11 or Google Chrome as your browser.ova file to the vCenter and convert it to a template. d) Under Select name and folder. a) Click the ESXi host name on which you cloned the VM. look under All vCenter Actions. 6. select the datastore on which you want to clone the VM.ova file that you want to clone. 5.10.xx_SLES11_SP3_on_VMware_20170707125811. b) Click the Related Objects tab. do the following to begin the cloning process: a) Under Select source.10.xx. select Hosts and Clusters to see all the ESXi hosts managed by the vCenter server. and select All vCenter Actions > Convert to Template.xx. If menus differ. this procedure describes how to upload the . verify the VM is in a powered off state and the status is normal.xx. Right-click the ESXi host name on which you want to clone the VM. Leave the VM Storage Policy as is. and click Next. Access the VMware Knowledge Base and search for Installing VMware Client Integration Plug-in. then click Browse and go to the directory containing the . and click Next. The VM is converted to a template. 2.xx represents the template version you are using). e) Under Select storage.ova file. Having the template reside on your local system takes the VM longer to deploy. From the vSphere Client. select a folder or datacenter in your vCenter server in which to clone your VM. For best results. From the Deploy OVF Template dialog box.xx_SLES11_SP3_on_VMware_20170707125811.01 . Before initially deploying the VM. Having the template reside on vCenter enables the VM to quickly deploy. where 16. 25.com". and click Finish to clone the template. click VM Templates. you must clone the template to another ESXi host.datastore".25.labs. "Datastore": "cs3097-05.10. { "ESXiHost": "cs3097-05. "eth0": "10. f) If you want to speed up the clone time and save space in the datastore. g) Under Ready to complete. b) Right-click the template name. "eth0": "10. "Datastore": "cs3097-05. c) Under Select a name and folder.datastore". c) Click VM Templates. do the following to verify the VM was converted to a template.teradata.xx_SLES11_SP3_on_VMware_20170707235215" } { "ESXiHost": "cs3097-05. select Thin Provision from the Select virtual disk format menu. verify the template appears. Following are examples of deploying VMs from vCenter for either of the latest Teradata Database versions and associated products. "vmType": "tpa". enter a name of the new template.xx. If you have a physical server with 2 to 7 pNodes.datastore". The template name in the examples below is the VM name you modified in step 4d.xx. then select a folder or datacenter in your vCenter server to put the new template. "eth0": "10. "Template": "Teradata_Database_16.10. and select All vCenter Actions > Clone to Template. select the ESXi host and its datastore to host the template.05.28. Chapter 2: Preparing for Installation 7. and click Next. see Templates. select the virtual disk format. b) Click the Related Objects tab. "vmName": "cobra26".xx_SLES11_SP3_on_VMware_20170707235215" } { "ESXiHost": "cs3097-05.25.teradata. Teradata Database on VMware Getting Started Guide. "Datastore": "cs3097-05. a) Click the ESXi host name on which you cloned the VM.25. "Template": "CMIC 12. "Template": "Teradata_Database_15. "eth0": "10. Deployer Release 3.labs. e) Under Select storage.teradata. d) Under the Name column. "Datastore": "cs3097-05.xx_SLES11_SP3_on_VMware_20170707235215" } { "ESXiHost": "cs3097-05.10. "vmName": "cobra26". 8.teradata. d) Under Select a compute resource. and click Next.datastore".01 25 . "vmType": "tpa". "vmName": "cobra26".labs.For the latest template version numbers.com".labs.teradata.28.25. verify all information. "vmType": "vp".labs.110". "eth0": "10. From the vSphere Client. "vmName": "cobra26".110".xx_SLES11_SP3_on_VMware_20170707235215" } { "ESXiHost": "cs3097-05.datastore".110".xx.com". "Template": "Teradata_Viewpoint_16.110".xx.28.110".28.com".28. a) From the Related Objects.com". and click Next. "vmName": "cobra26". "Datastore": "cs3097-05. "vmType": "cmic". xx.com".25. For the latest template version numbers.json Files Use the following sample node.Chapter 2: Preparing for Installation "vmType": "dsu".xx.10. month (2 digits). hours (2 digits). Having the template reside on vCenter enables the VM to deploy quicker.com".10.01 . "vmName": "cobra26".datastore".ova The download file names listed above are appended with 14 numbers representing when the template was created by Teradata: the year (4 digits).10.properties. "eth0": "10.o va • Local deployment using relative path: Teradata_Viewpoint_16. "Template": "Teradata_Database_16.xx. "Template": "Teradata_EM_16. "eth0": "10. Following is an example of deploying a Viewpoint virtual machine from your local machine using an absolute path: { "ESXiHost": "cs3097-05.25. you must prepare the templates in the local system.xx.28. "vmName": "cobra1". { "ESXiHost": "esxi-14. "Datastore": "cs3097-05.xx_SLES11_SP3_on_VMware_20170707235215" } Preparing the Templates in the Local System Before initially deploying the VM.xx_SLES11_SP3_on_VMware_20160803144556. Following are examples of deploying a Viewpoint template to the local system using either an absolute path or relative path. Deployer Release 3. and seconds (2 digits). "Datastore": "cs3097-05.labs.10.xx_SLES11_SP3_on_VMware_xxxxxxxxxxxxxx. minutes (2 digits). "eth0": "10. • Local deployment using absolute path: C:\Templates \SP3Ph2\Teradata_Viewpoint_16.ova" } Sample node. Replace the sample data after the colon (:) with your own. day (2 digits).teradata. Having the template reside on your local system takes the VM longer to deploy. "OS_Datastore": "esxi-14.110".10.110".85".cp14" 26 Teradata Database on VMware Getting Started Guide.json file as a template for creating your own. see Templates. "vmType": "tpa". For the latest template version numbers.teradata.28.10.datastore".xx_SLES11_SP3_on_VMware_xxxxxxxxxxxxxx. see Templates. "vmType": "em".com".xx.xx_SLES11_SP3_on_VMware_xxxxxxxxxxxxxx.28.xx_SLES11_SP3_on_VMware_20170707235215" } { "ESXiHost": "cs3097-05.25.xx.properties.teradata. "Template": "C:\Templates \Teradata_Viewpoint_16. "Template": "Teradata_DSC_16. "vmName": "cobra26".datastore".IT. "vmType": "vp".IT.labs.labs. com". Deployer Release 3.com/Resources/ White-Papers and search for Enabling the Temporal Data Warehouse. see Temporal Table Support. For more information.teradata.json file to true.teradata. set the Temporal property value in the node. Contact your Teradata Database Administrator for the DBSControl Flag values for the time zone variables.json file. ensure you configure your system carefully to avoid issues with your data. Chapter 2: Preparing for Installation }. "OS_Datastore": "14_data02". and then configure the other related properties based on your preferred time options and whether you plan to restore data from another Teradata system. so learn about this option before you enable it.properties. For more information.xx_SLES11_SP3_on_VMware_20160810184615" } Temporal Settings To use the Temporal option with Teradata Database on VMware. you must configure the NTP servers in the common. "eth0": "10.25.labs. use the following diagram and table.01 27 . "vmName": "cobra4".properties. To determine your settings in the properties file. you cannot turn it off.xx. To enable the Temporal option for a virtual machine. { "ESXiHost": "esxi-14.IT.88". To use the Temporal option. "Template": "Teradata_Viewpoint_16. "vmType": "vp". see Teradata Database Administration.28.10. Note: After you enable the Temporal option. see http://www. Teradata Database on VMware Getting Started Guide.IT. If you do not know your TimeZoneString. described below as 5a.Chapter 2: Preparing for Installation The following information is important when enabling this feature: • Temporal table support and Time Date with Zone Control by Database (TimeDateWZControl) are two different features. System TimeZone String:Not Set TimeZoneHour:0 57. • In the settings below. TimeZoneHour = 5 and TimeZoneMinute = 30 are examples. 5d. • In diagram scenario 5. TimeZoneString = America Pacific is an example. Time Date with Zone Control by Database must also be enabled. 5e. System TimeZone Hour:0 TimeDateWZControl:0 (Disabled) 17. • In the table settings below. System TimeZone Hour:0 TimeDateWZControl:3 (Local) 17. • If DaylightSavings is true. Deployer Release 3. Diagram Temporal Settings in the Property File DBS Control Setting Applied As Scenario 1 Temporal:false 16. However. Enter the time zone for your system. and 5f. TimeDateWZControl:0 (Disabled) TimeZoneMinute:0 TimeZoneString:Not Set 2 Temporal:true 16. • See Temporal Time Zone Strings for the valid values for TimeZoneString. System TimeZone Minute:0 DaylightSavings:false 18. 5c.01 . Enter the number of hours and minutes your installation is offset from GMT. when enabling Temporal table support. System TimeZone String:Not Set 28 Teradata Database on VMware Getting Started Guide. System TimeZone Minute:0 DaylightSavings:false 18. Note: Scenario 5 reflects six possible variations. you must include a TimeZoneString. 5b. you must copy the time zone settings from the DBSControl General Flags of the Teradata system from which you are restoring data. 18. System TimeZone Hour:0 system in system local time. 57. TimeDateWZControl:3 (Local) DaylightSavings:true TimeZoneHour:0 TimeZoneMinute:0 TimeZoneString:America Pacific (Example) 5b Temporal data is stored in the Teradata file 16. Deployer Release 3. 18. System TimeZone Hour:0 TimeDateWZControl:3 (Local) 17. System TimeZone Minute:0 observed. System TimeZone Minute:0 DaylightSavings:false 18. Temporal data is 17. System TimeZone String:Not Set TimeZoneHour:5 (Example) 57. System TimeZone Hour:0 system in UTC time. System TimeZone String:America Pacific TimeZoneHour:0 (Example) TimeZoneMinute:0 57. Daylight savings 17. TimeDateWZControl:2 (UTC) DaylightSavings:true TimeZoneHour:0 TimeZoneMinute:0 TimeZoneString:America Pacific (Example) 5c Temporal data is stored in the Teradata file 16. TimeDateWZControl:3 (Local) TimeZoneString:America Pacific (Example) 5a Temporal data is stored in the Teradata file 16. System TimeZone String:America Pacific Temporal:true (Example) TimeDateWZControl:3 (Local) 57. TimeDateWZControl:3 (Local) TimeZoneMinute:30 (Example) TimeZoneString:Not Set 4 Temporal:true 16. System TimeZone Minute:0 is observed. System TimeZone Minute:0 displayed in UTC time. TimeDateWZControl:3 (Local) Temporal:true TimeDateWZControl:3 (Local) DaylightSavings:false TimeZoneHour:0 TimeZoneMinute:0 TimeZoneString:Not Set Teradata Database on VMware Getting Started Guide. Daylight savings is not 18. Daylight savings is 17. System TimeZone Hour:5 (Example) TimeDateWZControl:3 (Local) 17. System TimeZone Hour:0 system in system local time. System TimeZone String:America Pacific Temporal:true (Example) TimeDateWZControl:2 (UTC) 57.01 29 . System TimeZone String:Not Set observed. System TimeZone Minute:0 DaylightSavings:true 18. TimeDateWZControl:3 (Local) TimeZoneMinute:0 TimeZoneString:Not Set 3 Temporal:true 16. Chapter 2: Preparing for Installation Diagram Temporal Settings in the Property File DBS Control Setting Applied As Scenario TimeZoneHour:0 57. Daylight savings is not 18. Temporal data is 17. System TimeZone Minute:30 (Example) observed. System TimeZone Hour:5 (Example) system in system local time. Daylight savings 17. 57. TimeDateWZControl:3 (Local) Temporal:true TimeDateWZControl:3 (Local) DaylightSavings:false TimeZoneHour:5 (Example) TimeZoneMinute:30 (Example) TimeZoneString:Not Set 5f Temporal data is stored in the Teradata file 16. System TimeZone Hour:0 system in UTC time. System TimeZone String:Not Set observed. System TimeZone String:Not Set Temporal:true 57. 57. TimeDateWZControl:2 (UTC) TimeDateWZControl:2 (UTC) DaylightSavings:false TimeZoneHour:5 (Example) TimeZoneMinute:30 (Example) TimeZoneString:Not Set 30 Teradata Database on VMware Getting Started Guide. System TimeZone String:Not Set entered. Time offset from GMT is 18. Time offset from GMT is entered. System TimeZone Minute:30 (Example) is not observed. Daylight savings is not 17. TimeDateWZControl:2 (UTC) Temporal:true TimeDateWZControl:2 (UTC) DaylightSavings:false TimeZoneHour:0 TimeZoneMinute:0 TimeZoneString:Not Set 5e Temporal data is stored in the Teradata file 16.Chapter 2: Preparing for Installation Diagram Temporal Settings in the Property File DBS Control Setting Applied As Scenario 5d Temporal data is stored in the Teradata file 16. 18.01 . System TimeZone Hour:5 (Example) system in UTC time. Deployer Release 3. System TimeZone Minute:0 displayed in UTC time. 01 31 . Commands must be run with sudo. Commands must be run with sudo. Commands must be run with sudo. VP Default OS User tvme iumb123 Default operating system user name (Viewpoint) and default password. Teradata Database dbc dbc Default Teradata Database user User name and password. CHAPTER 3 Installing and Configuring Teradata Database on VMware Default Passwords Notice: For security purposes. VM Type Account User Name Default Description Password TPA (Teradata Default OS User tvme iumb123 Default operating system user name Database) and default password. Commands do not need to be run with sudo. Deployer Release 3. Root OS User root iumb123 Default operating system root user name and default password if the Security Hardening feature is disabled in the Teradata Database. Commands do not need to be run with sudo. Teradata Database on VMware Getting Started Guide. we highly recommend default passwords be changed at the time you deploy Teradata Database on VMware. Root OS User root iumb123 Default operating system root user name and default password if the Security Hardening feature is disabled in the Teradata Database. EM Default OS User tvme iumb123 Default operating system user name (Ecosystem and default password if the Security Manager) Hardening feature is enabled in the Teradata Database. Commands must be run with sudo. Update and Delete (CRUD) operations on BAR. DSC Default OS User tvme iumb123 Default operating system user name and default password. Viewpoint Database viewpoint viewpoint Default Viewpoint user name and User password created on the database. Commands do not need to be run with sudo. 32 Teradata Database on VMware Getting Started Guide. Read. DSC OS User dscuser Default operating system dscuser user name. It is the same default user name and password for a superuser. Update and Delete (CRUD) operations on BARBACKUP. Used for Create. DSC Repository bar dsu#Bar! Default user name and password for User the DSC repository user. DSC Repository DSUADMIN dsu#Bar! Default Teradata Database user User name and password.Chapter 3: Installing and Configuring Teradata Database on VMware VM Type Account User Name Default Description Password Root OS User root iumb123 Default operating system root user name and default password if the Security Hardening feature is disabled in the Teradata Database. Viewpoint logs into the database with these credentials.01 . DSC Repository barbackup dsu#Bar! Default user name and password for User the backup DSC repository user. Used for Create. CMIC OS User cmic smcmic Operating system cmic user name and default password. Deployer Release 3. Viewpoint Admin admin teradata Default Viewpoint administrator User user name and password. CMIC (Server Root OS User root iumb123 Operating system root user name Management) and default password. Commands do not need to be run with sudo. Read. Root OS User root iumb123 Default operating system root user name and default password if the Security Hardening feature is disabled in the Teradata Database. Admin Teradata dbc dbc#Bar! Default Teradata Administrative User user. IT. and then save them. 1. complete the applicable procedures under Deployment Verification.properties.01 33 . make copies of the common. and Upgrade Guide for Customers. Chapter 3: Installing and Configuring Teradata Database on VMware VM Type Account User Name Default Description Password Server Management root iumb123 Server Management Client root user Client Root User name and default password.json properties files. using the properties files originally used to deploy the VMs. and press Enter.properties. the VM deploys.json File and The node. Open a VMware vSphere PowerCLI shell version 5. Postrequisite After the VM deploys. you must set the execution privileges. the executable file deploys the selected templates. • If the information is incorrect. press y. Action is only taken as needed.json and node. meaning if errors occur.exe. 2. The deployment executable file is re-entrant. 4. then proceed to the next step. label them according to the system to be deployed. 5.json File. If there are no errors. do the following: • Ensure all required values in the properties files are present and correctly formatted as described in The common. Review the information and do one of the following: • If it is correct. Teradata Database on VMware Getting Started Guide. Configuration. 7. To update the passwords for the DSC Repository for metadata. See Setting PowerCLI Execution Privileges.IT. If a message warns you that running scripts is disabled. they can be fixed and the executable runs all states again. and press Enter. b) Select the Node Properties file.properties. When validation is successful. and press Enter. type deploy. The executable file connects to the vCenter server and validates the information in the properties files. and configures the VMs based on the values in the properties files. Type the following command from the PowerCLI prompt to connect to the vCenter that manages the ESXi hosts that will be running the Teradata Database VMs: connect-VIServer -server vCenter. Run tdc.IT. At the prompt. a) Select the Common Properties file.name 3. Deploying Teradata Database on VMware Prerequisite Before starting this procedure. see Updating Passwords in the Data Stream Utility Installation. Deployer Release 3.5 or later.deploy.IT. 6. 8. [Optional] For troubleshooting purposes.server. edit the properties files and re-run the deployment executable file.properties. Navigate to the directory containing the Teradata Database on VMware deployment executable file (C:\mylocation\Teradata_Deployer\). See Configuring DSC Settings. clear your browser cache and refresh your browser. • Verify a backup location is established. Configuration. Add a backup solution. Configure the DSC settings. see the Data Stream Utility Installation. a) Open the BAR Setup portlet. For more information. If buttons in the portlet do not display properly.0. Configuration. remove all IP addresses except 39. and Upgrade Guide for Customers and refer to Configuring Storage Devices and Ports. 1.01 .42. in the Data Stream Utility Installation. • The Broker Port is 61616 • The Broker Connectivity is TCP • The DSC Server Name is 127. For the default DSC credentials. do the following: • Verify the DSC vSwitch is using at least a 10 GB network adapter. The TPA and DSC vNodes are preconfigured as media servers.0. Configuration. click Media Servers. d) Click Apply. In the Adding or Editing a Teradata System or Node section: • The dsc_name is 127. To ensure all traffic goes through the DSU network. In the Configuring a DSC section.1Repository.0.0. b) From the Categories list.1. 2. in the Data Stream Utility Installation.xx. 3. see Default Passwords. Deployer Release 3. the Broker IP of the DSC server can be found in the /etc/hosts file in the DSC LAN section. select each media server and delete the IPv6 IP addresses beginning with fe.Chapter 3: Installing and Configuring Teradata Database on VMware DSC Configuration Before using DSC on Teradata Database on VMware. Do not select Enable SSL over JMS Communication until it is configured. c) From the Media Servers list. Add the systems by following the procedure Configuring Portlet Software. and Upgrade Guide for Customers. and Upgrade Guide for Customers. Configuration. 34 Teradata Database on VMware Getting Started Guide. see Data Stream Utility Installation. SSL is not set up by default. Add a target group by following the procedure Adding or Copying a Target Group. Remove IPv6 IP addresses from media servers.xxx. and use the media server on the DSC vNode to back up and restore the DSC repository for metadata. 4. Configuring DSC Settings Contact your Teradata Viewpoint Administrator to ensure you have the appropriate permissions to configure DSC settings in Teradata Viewpoint. • After DSC has been deployed. • Verify the Teradata Viewpoint vNode is deployed at the same time as DSC. We recommend using the media servers on the TPA vNodes to back up and restore the Teradata Database. and Upgrade Guide for Customers. For more information. • Ensure users in the Teradata Viewpoint role have been granted permission to use the BAR Setup portlet as they will be using the portlet to configure the BAR system. You can run backup. Logging On to the Database After starting the database.10. Testing the Database After deploying the database. Starting the Database The database starts automatically after deployment. 2.xx.xx LANGUAGE SUPPORT MODE Standard 4.dbcinfo to see if the database is responding. see Configuring Using Portlet Software in the Data Stream Utility Installation. access the server through SSH.xx.dbcinfo. if applicable.d/tpa start. *** Total elapsed time was 1 second. For more information about the settings in the BAR Setup portlet. 3 rows found. Chapter 3: Installing and Configuring Teradata Database on VMware You have completed the configuration settings for DSC. If the database does not start. InfoKey InfoData –-------------------------------------- VERSION 16. 1. Run select * from dbc. Teradata Database on VMware Getting Started Guide. verify the database is accessible and responsive. and restore jobs using the BAR Operations portlet in Teradata Viewpoint.10. Using the default credentials. Viewpoint. sel * from dbc. For more information. and Upgrade Guide for Customers.xx RELEASE 16. Notice: We strongly recommend immediately changing the database password. Deployment Verification After deploying a Teradata virtual machine. Retain the log files to confirm your settings. No additional installation is required. Deployer Release 3. Start BTEQ. BTEQ is installed on the Teradata Database (TPA) node for Teradata Database on VMware. log on to the database. log on. test the Teradata Database and. analyze. If the database does not respond. *** Query completed. start it manually: /etc/init. Configuration.01 35 . 3. 2 columns returned. Sample result indicating response. see the Teradata Data Stream Architecture User Guide. Expand Collective > Cabinet to view the Server Management nodes you configured. you can verify the installation. 2. and confirming the system is healthy. Testing DSC After deploying a DSC VM. 5. Add the Ecosystem Manager portlet in Viewpoint. confirming data displays. 1. 1. 1. Click Add Content. Testing Server Management After deploying a Server Management (CMIC) VM. 6. If you do not see a node you configured. and click Add. and Upgrade Guide for Customers. The following components must be installed before you can use R functionality with Teradata Database: • R interpreter • Fortran compiler 36 Teradata Database on VMware Getting Started Guide. Log in to the Teradata Viewpoint portal. test if the deployment was successful by adding portlets. Deployer Release 3. 2. On the SMWeb Home page. and the Query Monitor portlets. Refer to Verifying Installation in the Data Stream Utility Installation. 4. Node Resources.Chapter 3: Installing and Configuring Teradata Database on VMware Testing Viewpoint After deploying a Viewpoint VM. you must redeploy. 2. The SMClient displays system components in a hierarchical directory structure. click Server Management Client. you can verify that it is configured on the Viewpoint node. if so. 3. In the Ecosystem Manager portlet click Servers and locate a row with the entry datacenter. If the Viewpoint does not respond. verify the installation in Server Management Client (SMClient). R for Data Analysis The Teradata VM image includes packages allowing you to install and use R table operators for data analysis. you must redeploy. access the server through SSH. Select the System Health. Confirm the System Health portlet displays green to indicate the system is healthy and the deployment was successful. ensure you have the correct IP address and.01 . It may take a few minutes for the data collectors to provide the data that displays in the portlets. If you do not see a node you configured. Configuration. 1. Testing Ecosystem Manager After deploying an Ecosystem Manager VM. Confirm each of the portlets display data. x86_64. see SQL External Routine Programming.2. install the R add-on packages from the Comprehensive R Archive Network (CRAN). Run the optional DipRTblOp DIP script to create the ExecR table operator. The teradata-udfGPL package that matches your version of the Teradata Database system is installed. see Creating the ExecR System Table Operator.rpm udfGPL Library Installation The udfGPL library is automatically installed as part of the Teradata Database on VMware operating system installation. Teradata Database on VMware Getting Started Guide. Deployer Release 3. 1. Creating the ExecR System Table Operator The ExecR table operator is required and is used to execute R scripts. 1. Check the following packages are installed: • gcc-fortran • gcc43-fortran • libgfortran43 Installing the R Interpreter Prerequisite You must have root privileges to access and install the . To apply innovative statistical techniques to analyze data stored in Teradata Database. TDR is the R package interface between R and Teradata Database. You must install the R interpreter before using R functionality. For more information.1-1. a new library (pkg) can be used within an R script.01 37 . 1. Both TDR and the udfGPL library are included in the teradata-udfGPL package.rpm. For additional information about installing R components and packages and using R. Verifying the Fortran Compiler Packages Verify the VME ESXi TPA template has the Fortran compiler packages installed before using R functionality. Display the Fortran packages that are installed. see Installing Optional R Add-On Packages. Chapter 3: Installing and Configuring Teradata Database on VMware • udfGPL library The ExecR table operator is required and is used to execute R scripts. After they are installed. rpm -qa | grep fortran 2. Each version of the Teradata Database system has a compatible version of this package. For more information. Type the following command to install the R interpreter: psh rpm -U /var/opt/teradata/extras/R/R-3. 1.Chapter 3: Installing and Configuring Teradata Database on VMware Following is an example of how to run the DipRTblOp script from a Teradata node: #cnsterm 6 Input Supervisor Command: > start dip Started 'dip' in window 1 Input Supervisor Command: > ^C -. /opt/teradata/PUTTools/misc/td_RTblop/td_installRaddon pkgname The script wraps the file downloaded from the CRAN website into a PUT-installable . 3.<control C> #cnsterm 1 Attempting to connect to CNS. run the td_installRaddon script.us. Put the downloaded R add-on package into the /tmp directory on the primary (PDN) node.rpm file and places the . 5.rpm file in the current working directory which is /tmp. 38 Teradata Database on VMware Getting Started Guide. put the package in the same common location on all nodes.Completed Type the password for user DBC or press the Enter key to quit: > xxx ***Logon successfully completed. Deployer Release 3. DIPRTBLOP is complete Please review the results in /var/opt/teradata/tdtemp/dip40. you have the option to install R add-on packages from Comprehensive R Archive Network (CRAN). After they are installed. Select one of the following DIP SQL scripts to execute: (Press the Enter key to quit) . Copy the rpm to all nodes. For MPP installations. From the /tmp directory. 2.r-project. DIPRTBLOP ...txt on node 1-1 Would you like to execute another DIP script (Y/N)? > N Exiting DIP. Go to http://cran. Using the R console..01 . 6. Run one of the following commands: • Single-node system: rpm –ivh packagename..rpm • MPP system: psh rpm –ivh directory/packagename.. Install the . 4.R Table Operator > 40 Executing DIPRTBLOP Please wait. 40...rpm 7.org/ to download the R add-on package from CRAN.rpm on all nodes using PUT or manually using rpm commands. Installing Optional R Add-On Packages To apply innovative statistical techniques to analyze data stored in Teradata Database. a new library called pkg can be used within an R script. check if the package was installed correctly.. 123. Execute the configureTCHN.125 : VMNAMEntci3:: :: 3.IT.hosts file in the following format: HOST : ipaddr : vmnameNTCI n:: :: Note: There is no space between the VM name and the NP name. sh /var/opt/teradata/tvme/script/configureTCHN. enter the TDP logical host ID in the LHID field.properties. ipaddr IP address of the VM vm Name of the VM NTCI n:: :: Representation of an Teradata network processor (NP) name The following is an example of a three vNode system: HOST : 123. Chapter 3: Installing and Configuring Teradata Database on VMware Connecting with a Mainframe Computer For more information on mainframe configuration.124 : VMNAMEntci2:: :: HOST : 123.12.123. 2. 1. Edit the TDP Parm file to add the NP information. Add the vNodes to the appropriate MVS etc.json file.123. see Teradata Director Program Reference and Teradata Tools and Utilities for IBM z/OS Installation Guide.12.sh tdpid=LHID where LHID is the TDP logical host ID. Teradata Database on VMware Getting Started Guide. 1. Ping the VM from the mainframe to confirm the deployment using the following syntax: For a single-node system: tso ping vmname For a MPP system. There is a space between the second and third trailing colon. Deployer Release 3. ping the individual nodes: tso ping vmname1 Connecting with a Mainframe Computer after Installation If you have already deployed a Teradata VM. In the node.01 39 .123 : VMNAMEntci1:: :: HOST : 123. you can execute a script to connect with a mainframe computer.12. The following is the syntax of a three vNode system: CONFIG NP DATABASE vmname CONFIG NP LHID logical host id START NP1 START NP2 START NP3 4.sh script on the deployed VM. Chapter 3: Installing and Configuring Teradata Database on VMware 40 Teradata Database on VMware Getting Started Guide. Deployer Release 3.01 . 2. Install and configure the TTU package according to the instructions in the appropriate Teradata Tools and Utilities Installation Guide at http://www. 1.info. 2. Copy the TTU packages to the appropriate Linux or Windows virtual or physical machine where the TTU software will be installed and used.info. Deployer Release 3. Teradata Database on VMware Getting Started Guide.teradata.com.01 41 . Installing and Configuring Teradata Tools and Utilities TTU can be installed on VMs running a supported version of Linux or Windows.com.10 or later at http://www.teradata. see Teradata Tools and Utilities Supported Platforms and Product Versions for 15. For more information. CHAPTER 4 Installing and Configuring Other Teradata Applications Installing and Configuring Teradata Studio 1. Ensure the Teradata Database on VMware setup process deployed the files for installing TTU. Linux and Windows versions of the files are placed in /var/opt/teradata/TTU_pkgs. Install and configure the Teradata Studio package according to the Teradata Studio and Studio Express Installation Guide. or on another system running a supported operating system.teradata. Download the Teradata Studio package from https://downloads. 3.com. 01 .Chapter 4: Installing and Configuring Other Teradata Applications 42 Teradata Database on VMware Getting Started Guide. Deployer Release 3. Deployer Release 3. Archive. APPENDIX A Acronyms Acronyms Acronym Definition AMP Access Module Processor BAR Backup. Read. Update. and Restore BTEQ Basic Teradata Query BYNET Banyan Network (BYNET) Interconnect COP Communications Processor CRAN Comprehensive R Archive Network CRUD Create.01 43 . and Delete DBC Database Computer DBS Database System DHCP Dynamic Host Configuration Protocol DIP Database Initialization Program DNS Domain Name System DSC Teradata Data Stream Controller DSU Teradata Data Stream Utility ESXi Elastic Sky X integrated GMT Greenwich Mean Time HT Hyper-Threading JMS Java Messaging Service JSON JavaScript Object Notation LHID Logical Host Identifier LUN Logical Unit Number MPP Massively Parallel Processing (Teradata Database multi-node system) MTU Maximum Transmit Unit MVS Multi-Value Compression NP Network Processor Teradata Database on VMware Getting Started Guide. 01 . Deployer Release 3.Appendix A: Acronyms Acronym Definition PDE Parallel Database Extensions PDN Primary Distribution Node PUT Teradata Parallel Upgrade Tool RAID Redundant Array of Independent Disks SLES SUSE Linux Enterprise Server SSH Secure SHell SSL Secure Sockets Layer TaYS Teradata at Your Service TCP Transmission Control Protocol TDP Teradata Director Program TDR Teradata R TPA Teradata Parallel Application TTU Teradata Tools and Utilities UTC Coordinated Universal Time VM Virtual Machine VP Viewpoint 44 Teradata Database on VMware Getting Started Guide. 01 45 . APPENDIX B Teradata Time Zones and Regions Temporal Time Zone Strings If you enabled the Temporal feature of Teradata Database and want to set the TimeZoneString. you can enter one of the following: GMT GMT+1 GMT+10 GMT+11 GMT+11:30 GMT+12 GMT+13 GMT+14 GMT+2 GMT+3 GMT+3:30 GMT+4 GMT+4:30 GMT+5 GMT+5:30 GMT+5:45 GMT+6 GMT+6:30 GMT+7 GMT+8 GMT+8:45 GMT+9 GMT+9:30 GMT-1 GMT-10 GMT-11 GMT-2 GMT-3 GMT-4 GMT-5 GMT-6 GMT-6:30 GMT-7 GMT-8 Teradata Database on VMware Getting Started Guide. Deployer Release 3. you must enter one of the following time zone regions for your system (TimeZoneString): Africa Egypt Africa Morocco Africa Namibia America Alaska America Aleutian America Argentina America Atlantic America Brazil America Central America Chile America Cuba America Eastern America Mountain America Newfoundland America Pacific America Paraguay America Uruguay Asia Gaza Asia Iran Asia Iraq Asia Irkutsk Asia Israel Asia Jordan Asia Kamchatka Asia Krasnoyarsk Asia Lebanon Asia Magadan Asia Omsk Asia Syria Asia Vladivostok Asia West Bank Asia Yakutsk Asia Yekaterinburg Australia Central Australia Eastern Australia Western Europe Central Europe Eastern Europe Kaliningrad Europe Moscow Europe Samara Europe Western Indian Mauritius Mexico Central Mexico Northwest Mexico Pacific Pacific New Zealand Pacific Samoa 46 Teradata Database on VMware Getting Started Guide.Appendix B: Teradata Time Zones and Regions Temporal Regions If you have enabled the Temporal feature of Teradata Database and have set DaylightSavings to true. Deployer Release 3.01 . rebuild the AMP. 2. SSH into one of the nodes. 4.------. then recovery using fallback is impossible. Community-driven customer support is available for Developer at http:// community.-----. are Fatal. 3. If more than a single AMP in the same fallback cluster is down. Run the command status.-----. Type Vproc -----. you cannot use this procedure.-------.----. assess if you can recover from fallback.----- ----- 0 1 1-01 Yes 0 FATAL** Online AMP 0 On 28671 1 2 1-01 Yes 0 FATAL** Online AMP 1 On 28671 2 3 1-01 Yes 0 FATAL** Online AMP 2 On 28671 3 4 1-01 Yes 0 FATAL** Online AMP 3 On 28671 4* 5 1-01 Yes 0 ONLINE Online AMP 4 On Teradata Database on VMware Getting Started Guide. Node Can Crash Vproc Config Config Cluster/ Host TVS Number Vproc# ID Move Count State Status Type Host No. Deployer Release 3. 6.01 47 . Look for AMPs marked as FATAL** and check the column Cluster/Host No.teradata.com/tdvm. If you have lost a Pdisk.-----. 9 are Fatal and are not recoverable. Rebuilding AMPs from Fallback Prerequisite Before you begin. APPENDIX C Troubleshooting Teradata Database on VMware Node Failure Recovery Node failure recovery depends on the type of failure. In the following example. 1. Run vprocmanager. SYSTEM NAME: MPP160 17/01/12 14:40:21 DBS LOGICAL CONFIGURATION ------------------------- Rcv Jrnl/ Vproc Rel. ----. redeploy the VM. If the root disk fails. 3.-------. both AMPs in cluster 0. If two AMPs with the same Cluster/Host No. the subnet mask address for the Server Management network is automatically calculated.properties. Additional Properties for Customization Additional properties can be added to the bottom of the common.255. delete the failed Pdisks that corresponds to the fatal AMPs. Note: A copy of these two configs are located in /root/tvme on any of the nodes. then follow the prompts until the system is rebuilt. 7. Note: This information is intended for advanced users only.Properties and Common.IT. If recovery is possible in your Vsphere client. Deployer Release 3.254. common.json file for troubleshooting purposes. 48 Teradata Database on VMware Getting Started Guide. you can override the calculated subnet mask by setting this property.deploy. Enter your DBC account and password.exe with the storage step using the deployed system's Node.Properties This re-creates the removed Pdisks.Appendix C: Troubleshooting Teradata Database on VMware 28670 5 6 1-01 Yes 0 ONLINE Online AMP 5 On 28670 6 7 1-01 Yes 0 ONLINE Online AMP 6 On 28670 7 8 1-01 Yes 0 ONLINE Online AMP 7 On 28670 8 9 1-01 Yes 0 ONLINE Online AMP 8 On 28669 9 10 1-01 Yes 0 ONLINE Online AMP 9 On 28669 10 11 1-01 Yes 0 ONLINE Online AMP 10 On 28669 11 12 1-01 Yes 0 ONLINE Online AMP 11 On 28669 12 1 1-02 Yes 0 FATAL** Online AMP 0 On 28668 13 2 1-02 Yes 0 FATAL** Online AMP 3 On 28668 14 3 1-02 Yes 0 FATAL** Online AMP 6 On 28668 15 4 1-02 Yes 0 FATAL** Online AMP 9 On 28668 5. Run tdc.IT. run tdc-rebuild as the root user. Use these properties only when necessary or when instructed by Teradata as performance may be impacted. For example: 255.IT. 8.01 .json Property Name Setting Description cmic_submask Subnet mask When deploying a Server Management vNode. If there are issues with the automatic calculation. contact your network administrator.IT.0. 6. When the command finishes.properties. For assistance. 01 49 . 4. Teradata Database on VMware Getting Started Guide. Deleting Datastore Files to Add Space Depending on the type of storage used. NoLockdown • TRUE Teradata recommends keeping this setting as FALSE which is • FALSE the default setting. The default is 0. 1. 5. Click the Related Objects tab and click Datastores. If you accidentally do. Notice: Setting this property to TRUE presents a high security risk. The default is 0. The ESXi host requires some CPU power for the ESXi Hypervisor. located in the left panel.00 Changes the percentage of CPU reserved on the ESXi host. EsxiCPUreserved 0. You can use third party tools to help detect and delete orphaned VM files.00 . the VMs do not allow security changes to be performed and also disables the root account when using SSH. and click . those files cannot be recovered which can be destructive to your system. 3. Select a VM in your host inventory. Click a datastore from the list. You can manually delete files from the datastore after you delete a VM.05 of the total memory.1. Different systems will have different requirements. located in the upper right corner.12. Highlight the files associated with the deleted VM. Open the vCenter Server or Virtual Infrastructure Client and log in. 2. The ESXi host requires some memory for the ESXi Hypervisor. Use with caution. Different systems have different requirements. Click the Manage tab and click Files. rounded down to a multiple of 4. When set to TRUE. Notice: Do not delete files in the datastore that are not associated with the deleted VM. Deployer Release 3. there is a known VMware issue where free space on datastores does not return the original amount of space after you delete a VM. Appendix C: Troubleshooting Teradata Database on VMware Property Name Setting Description EsxiMemReservedMB Integer Changes the percentage of memory in MB reserved on the ESXi host. 6. Depending on the warning. you may get the following password error after the VM receives power. The given new password is either blank or incorrect!" If you entered your correct password. and then contact your Cloud administrator for further assistance. 50 Teradata Database on VMware Getting Started Guide. PowerCLI Warnings PowerCLI may send warnings when accessing the deployment executable file. Passing multiple values to this parameter is obsolete. Resolving BAR Setup Connection Warnings If you get a Connection to system unsuccessful warning message when adding a Teradata Database system in the BAR Setup portlet. it may not be relevant or cause issues. the following warnings may appear repeatedly. SSH into Teradata Viewpoint and extract the DNS servers and search domains. To resolve this issue. the DSC vNode may not be able to resolve the Teradata Database COP entries. 1. but should not cause an issue.Appendix C: Troubleshooting Teradata Database on VMware The free space on the associated datastore is returned to the original amount prior to deleting the VM. "ERROR! The deployed system is not using the default password given.01 .0 and later. Check your network configuration. Deployer Release 3. Incorrect Password Error When deploying a new VM. you can verify the servers and domains configured in Teradata Viewpoint are also configured in the DSC vNode. WARNING: Parameter ‘VM’ is obsolete. In vSphere PowerCLI 6. WARNING: The version of VMware Tools on VM version number is out of date and may cause Invoke-VMScript to work improperly. check the logs for an entry similar to the following: Invoke-VMScript : 11/16/2015 6:32:01 PM Invoke-VMScript Unable to connect to the remote server The machine running the PowerCLI command and the ESXi host that contains the VMs may not be able to communicate with each other. 8.com teradata.*$/ NETCONFIG_DNS_STATIC_SEARCHLIST=\"labs.65.com teradata.com td. Extract the Teradata Database COP entries from the hosts file in Teradata Viewpoint and append them to the hosts file in the DSC vNode using the following syntax: Teradata Database on VMware Getting Started Guide.251.10\"/" /etc/ sysconfig/network/config c) If you added a server.8. # grep "NETCONFIG_DNS_STATIC_SEARCHLIST" /etc/sysconfig/network/config Sample output: NETCONFIG_DNS_STATIC_SEARCHLIST="labs.com and teradata.teradata. verify it is now there.10 is missing from Teradata Viewpoint. # sed -i "s/^NETCONFIG_DNS_STATIC_SEARCHLIST=. 3. the DNS server may not contain any DNS record for the Teradata Database COP entries.8.teradata.com teradata.64. # grep "NETCONFIG_DNS_STATIC_SERVERS" /etc/sysconfig/network/config Sample output: NETCONFIG_DNS_STATIC_SERVERS="153.64.10" b) Extract the DNS search domains: # grep "NETCONFIG_DNS_STATIC_SEARCHLIST" /etc/sysconfig/network/config Sample output: NETCONFIG_DNS_STATIC_SEARCHLIST="td.teradata.251.8. # grep "NETCONFIG_DNS_STATIC_SEARCHLIST" /etc/sysconfig/network/config Sample output: NETCONFIG_DNS_STATIC_SEARCHLIST="labs. Deployer Release 3.com td.com are missing from Teradata Viewpoint.teradata.*$/ NETCONFIG_DNS_STATIC_SERVERS=\"153. verify it is now there.teradata.teradata.com" g) Apply the change.200 153. SSH into the DSC vNode to check the DNS servers and search domains.200" Notice if 153.251. a) Extract the DNS servers.com Notice if td. e) Add any missing search domains. # grep "NETCONFIG_DNS_STATIC_SERVERS" /etc/sysconfig/network/config Sample output: NETCONFIG_DNS_STATIC_SERVERS="153.200 153. # sed -i "s/^NETCONFIG_DNS_STATIC_SERVERS=. /sbin/netconfig update -f If the warning message continues.64.com" 2.64.teradata.65. b) Add any missing servers.10" d) Extract the DNS search domains.com\"/" /etc/sysconfig/network/config f) If you added a search domain. and then add the servers and domains that are in Teradata Viewpoint.200 153.251.65. Appendix C: Troubleshooting Teradata Database on VMware a) Extract the DNS servers: # grep "NETCONFIG_DNS_STATIC_SERVERS" /etc/sysconfig/network/config Sample output: NETCONFIG_DNS_STATIC_SERVERS="153.01 51 .65. 01 .23.Appendix C: Troubleshooting Teradata Database on VMware # grep TeradataSystemNamecop* /etc/hosts | ssh root@DSC_public_ip 'cat >> /etc/hosts' For example.25.170 'cat >> /etc/hosts' 52 Teradata Database on VMware Getting Started Guide.25.170. use the following syntax: # grep system1cop* /etc/hosts | ssh root@10. if the TeradataSystemName is system1 and the public IP for the DSC vNode is 10. Deployer Release 3.23.