Field Installation Guide for Teradata Node Software • Operating System: Windows Server 2003 (64 bit) • Hardware Platform: Third-Party, Single Node System • Teradata Database: 13.0

B035-5250-070K August 2012

This document is intended for online distribution. For the current release see: http://www.info.teradata.com

The product or products described in this book are licensed products of Teradata Corporation or its affiliates. Teradata, Active Enterprise Intelligence, Applications-Within, Aprimo, Aprimo Marketing Studio, Aster, BYNET, Claraview, DecisionCast, Gridscale, MyCommerce, Raising Intelligence, Smarter. Faster. Wins., SQL-MapReduce, Teradata Decision Experts, "Teradata Labs" logo, "Teradata Raising Intelligence" logo, Teradata ServiceConnect, Teradata Source Experts, "Teradata The Best Decision Possible" logo, The Best Decision Possible, 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. 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. 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 Quest Software, 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. SAS and SAS/C are trademarks or registered trademarks of SAS Institute Inc. SPARC is a registered trademark of SPARC International, Inc. Symantec, NetBackup, and VERITAS are trademarks or registered trademarks of Symantec Corporation or its affiliates in the United States and other countries. Unicode is a registered trademark of Unicode, Inc. in the United States and other countries. UNIX is a registered trademark of The Open Group in the United States and other countries. Other product and company names mentioned herein may be the trademarks of their respective owners.

The information contained in this document is provided on an "as-is" basis, without warranty of any kind, either express or implied, including the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. Some jurisdictions do not allow the exclusion of implied warranties, so the above exclusion may not apply to you. In no event will Teradata Corporation be liable for any indirect, direct, special, incidental, or consequential damages, including lost profits or lost savings, even if expressly advised of the possibility of such damages. The information contained in this document may contain references or cross-references to features, functions, products, or services that are not announced or available in your country. Such references do not imply that Teradata Corporation intends to announce such features, functions, products, or services in your country. Please consult your local Teradata Corporation representative for those features, functions, products, or services available in your country. Information contained in this document may contain technical inaccuracies or typographical errors. Information may be changed or updated without notice. Teradata Corporation may also make improvements or changes in the products or services described in this information at any time without notice. To maintain the quality of our products and services, we would like your comments on the accuracy, clarity, organization, and value of this document. Please 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 © 2009 - 2012 by Teradata Corporation. All Rights Reserved.

Table of Contents

Preface.............................................................................................................................................................5 About This Guide.................................................................................................................................................5 Revision History...................................................................................................................................................5 Additional Information.......................................................................................................................................5

Chapter 1: Preparing for Software Installation..................................................................................7 Software Required.................................................................................................................................................7 Hardware Requirements......................................................................................................................................7 About Disk Storage Requirements.....................................................................................................................9 About Virus Protection.....................................................................................................................................10 About Technical Support..................................................................................................................................11

Chapter 2: Installing and Configuring the WS 2003 Operating System...................13 Before You Set Up the Operating System.......................................................................................................13 Configuring NetMeeting and Remote Desktop Sharing (Optional) ..........................................................14 Configuring Pagefile (Required) ......................................................................................................................15 Installing the Support Tools (MSDN/Retail) (Required) ............................................................................16 Changing the Windows Explorer Options (Required) ................................................................................16 Changing the Event Viewer Settings (Required) ..........................................................................................17 Updating the C:\boot.ini File............................................................................................................................18 Installing the MultiLanguage Software (Optional) .......................................................................................19 Configuring Terminal Services for Remote Connectivity (Recommended) .............................................19 Setting Up Remote Connectivity (Recommended) ......................................................................................20 Disabling the Event Tracker (Required) ........................................................................................................20 Disabling the Windows Firewall, Internet Connection Sharing, and Automatic Updates (Required) ........................................................................................................................................................................21

Chapter 3: Installing the Microsoft Debugging Tools and Retail Symbols............23

Field Installation Guide for Teradata Node Software Windows Server 2003 (64 bit) Third-Party, Single Node System, Release 13.0

3

Table of Contents

Installing the Microsoft Debugging Tools.......................................................................................................23 Installing the Microsoft Retail Symbols............................................................................................................23

Chapter 4: Installing the Visual Studio 64-bit Compiler...........................................................25 Installing the Visual Studio 64-bit Compiler...................................................................................................25

Chapter 5: Downloading and Installing Software............................................................................27 Obtaining a Teradata Change Control Number.............................................................................................27 Downloading and Installing Software..............................................................................................................27

Chapter 6: Configuring and Initializing the Teradata Database........................................31 Configuring and Initializing the Teradata Database......................................................................................31

Chapter 7: Post-Setup Activities........................................................................................................................33 About Post-Setup Activities...............................................................................................................................33

4

Field Installation Guide for Teradata Node Software Windows Server 2003 (64 bit) Third-Party, Single Node System, Release 13.0

Preface

About This Guide This guide is intended for use by customers installing the Teradata Database software on a third-party, single-node system. You should have basic computer knowledge, familiarity with Graphical User Interfaces (GUIs), and an understanding of the operating system.

Revision History Date

Description

August 2012

• •

July 2010

Clarified the number of CPUs that can be used on a 3rd Party SMP.

June 2010

Added information about the SCSI interface

Updated to reflect support of a maximum of 6 CPUs. Updated the Hardware Requirements.

January 2010 Added clarification about number of CPUs supported and information about C++ compilers April 2009

Initial Release

Additional Information 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://www.teradataatyourservice.com

External site for access to the Teradata software server. Only accessible with an active service contract.

http://infocentral.daytonoh.teradata.com/tsdlibrary/index.cfm

Internal site for published Teradata service documentation.

http://infocentral.daytonoh.teradata.com/tsdlibrary/isupr.cfm

Section of the internal site for Teradata service documentation specific to software installation and upgrade information.

http://tssprod.teradata.com:8080/TSFS/

Internal site linking to Teradata software server

Field Installation Guide for Teradata Node Software Windows Server 2003 (64 bit) Third-Party, Single Node System, Release 13.0

5

Preface Additional Information

6

Field Installation Guide for Teradata Node Software Windows Server 2003 (64 bit) Third-Party, Single Node System, Release 13.0

CHAPTER 1

Preparing for Software Installation

Software Required Software Media Title

Description

Parallel Upgrade Tool (PUT) and software patches

TDPut and any patches to other software are located on the Teradata Software Server at http:// tssprod.teradata.com:8080/TSFS/ or on Teradata at Your Service at http:// www.teradataatyourservice.com.

Microsoft Windows Server 2003-x64 MultiLanguage

This disk is required if any language other than English will be used.

Teradata Database for Microsoft Windows 2003 (64-bit)

This disk contains the proprietary Teradata Database software.

Microsoft Visual Studio

This disk must be ordered separately. It contains the 64-bit compiler.

Caution: Teradata does not support systems running VMWare.

Hardware Requirements The Teradata Database software may be run on any third party single-node system that meets the requirements shown in the following table. The system must also meet Microsoft's requirements to run the Microsoft Windows Server 2003 operating system. Caution: All hardware must be supported by the OS vendor. The hardware vendor should be consulted for explicit certification with the chosen OS and respective version and update levels, as applicable. These recommendations should result in a functional, reasonably performing system. System performance is dependent on hardware and customer workload. Tuning for optimal performance can be addressed through Teradata Services. Component

Recommendation

Processors and Server Technology

WARNING: Do not enable hyperthreading on the CPU. 1 or 2 Intel Xeon 5000-series Dual Core CPUs, 2.33 GHz or greater 1 Intel Xeon 5000-series Quad or Six Core CPU, 2.33 GHz or greater

Field Installation Guide for Teradata Node Software Windows Server 2003 (64 bit) Third-Party, Single Node System, Release 13.0

7

Chapter 1 Preparing for Software Installation Hardware Requirements Component

Recommendation Note: The minimum Teradata database version for six-core Data Mart Edition for third-party SMP support is: • 13.00.01.02 (DBS and PDE) To use more than four CPUs on a third-party SMP running Teradata database, you will need to install the minimum required version of PDE and DBS or higher.

Memory

• •

8 GB minimum, 96 GB maximum Minimum memory = 1 GB per Vproc minimum

Operating System Requirements

The Microsoft Windows Server 2003-x64 Release 2 (64-bit), Enterprise Edition, operating system is delivered on two CDs. The first CD has the Windows Server 2003 64-bit operating system with service pack 2. The second CD has the new Release 2 features. Do not load the second CD. The Teradata Database is not certified to work with the Release 2 features installed. Note: See Software Required for minimum kernel information.

Operating System • Disk (non-database) •

Up to 8 GB main memory - 1 x 146 GB mirrored set (2 disks) Over 32 GB main memory - 1 x 300 or 450 GB mirrored set (2 disks)

Note: 20 GB disk space reserved for Teradata. Note: Write Cache must be disabled on internal and external drives. Some drives with cache enabled have a tendency to lock up which results in data corruption. Please consult the appropriate hardware documentation or check with your hardware vendor. Number of AMPS/ Vprocs

•

36 Vprocs maximum, 16 Vprocs recommended

Database/Storage Disk

• • • •

RAID-1 is recommended. 5 arrays maximum, 3 arrays recommended 72 disks per array maximum If using RAID-5, ensure that there are at least two primary partitions available for database storage. Four disk drives are recommended for every unit of parallelization (VAMP).

•

8

Field Installation Guide for Teradata Node Software Windows Server 2003 (64 bit) Third-Party, Single Node System, Release 13.0

Chapter 1 Preparing for Software Installation About Disk Storage Requirements Component

Recommendation The performance assumption for the disk drives is 15 MB per second on a 96 K IO size, 80/20 read-write random workload. • •

•

There must be enough storage to create a minimum of 2 AMPs. If you are only using internal drives, at least one drive must be used for the database. If the disk is already sliced, only slices of type "unassigned" (0x00) or "teradata reserved" (0xda) will be considered for Teradata pdisks. All other slice types are ignored. The slices must not already be in use for another purpose (for example, mounted file system, swap area, dump slice, and so forth) Teradata supports Linux udev persistent device naming conventions.

•

The physical device names must appear in /proc/partitions.

•

• •

• • • Storage Host Bus Adapter Remote support

•

The physical device names must end in a letter (e.g., /dev/sdc or /dev/

cciss/c0d0a).

The partition device names must end in a number immediately after the letter of the physical device name (e.g., /dev/sdc1 or /dev/cciss/ c0d0a1). The devices must respond to scsi ioctl commands (e.g., sg_inq/dev/

sdc1 or sg_inq/dev/cciss/c0d0).

64 15K RPM disks to balance Teradata with the I/O subsystem (64 disks maximum). If you are using EMC storage, you must obtain the appropriate version of PowerPath software directly from EMC.

•

Minimum of four 4 Gbps fibre channel links to support 800 MB per second. Driver support for appropriate Linux kernel.

• •

1 Gb Ethernet adapter in SMP node. VPN connection.

Note: See About Disk Storage Requirements for more information.

About Disk Storage Requirements Use the Parallel Upgrade Tool (PUT) to set up your system and make sure the following conditions are met so that PUT will recognize Windows disk devices as candidates for Teradata pdisks: • There should be at least one physical disk or disk array LUN for each AMP. For performance and parallelism, Teradata normally recommends a minimum of two AMPs. • Each disk must be displayed in Disk Manager and be a basic disk. Windows dynamic disks are not supported. • Disks must support the SCSI Interface and respond to SCSI Inquiry commands. • Disks should be unsliced so that PUT can create the slices for Teradata. You can force a disk to appear unsliced by writing zeroes to the first block of the disk. One way to do this is to use Windows Disk Manager to remove any partitions and/or drive letters.

Field Installation Guide for Teradata Node Software Windows Server 2003 (64 bit) Third-Party, Single Node System, Release 13.0

9

Chapter 1 Preparing for Software Installation About Virus Protection

• If the disk is already sliced, only slices of type “unassigned” (0x00) or “teradata reserved” (0x3f) will be considered for Teradata pdisks. All other slice types are ignored. The slices must not already be in use for another purpose. • Do not attempt to share a disk between Teradata and the rest of the system. Teradata should always have whole disks or array LUNs for its pdisks. • Teradata disks and/or slices should all be the same capacity. Mixed disk capacities will result in less than optimal Teradata storage allocation.

About Virus Protection Teradata regularly scans its own internal systems to avoid introducing any viruses while providing remote support. However, Teradata also strongly recommends you develop and implement policies and procedures to keep your system free of viruses after initial installation. System performance may be impacted while performing active disk scans. If performance is a concern, you can set the proper controls in the anti-virus program to run the virus scans during off-peak hours. There are many virus protection applications in the marketplace and Teradata is not endorsing any particular program. However, problems created by viruses are not covered by the Teradata maintenance and support offerings. Any problems created by the installation or operation of any anti-virus software are not covered by the Teradata maintenance and support offerings either. If you want assistance to resolve any such virus-related or anti-virus software related problems, Teradata may provide assistance on a time and materials basis. Some Teradata system files change dynamically and active scanning of these files could cause high system resource utilization. Because of this, we recommend that any anti-virus product be configured to not scan the Tdat/tdconfig folder, specifically the *.dat and *.GDO files or pdesegment files. For real-time scans, exclude the following: • C:\Program Files\Teradata\TDAT • D:\Program Files\Teradata\TDAT • C:\WINNT\System32\config (This folder includes the node's Registry files.) • C:\Pagefile.sys • D:\Pagefile.sys • Exclude any files that are frequently created or modified in the LSI, EMC, PUT, NetVault, or Symantec directories. (The Auto-Protect Scan Statistics window can be used to watch which files are being scanned and look for frequent repeaters.) Or just exclude all files in those directories. For scheduled scans, exclude the following: • C:\Program Files\Teradata\TDAT\tdconfig • D:\Program Files\Teradata\TDAT\tdconfig • C:\WINNT\System32\config (This folder includes the node's Registry files.)

10

Field Installation Guide for Teradata Node Software Windows Server 2003 (64 bit) Third-Party, Single Node System, Release 13.0

Chapter 1 Preparing for Software Installation About Technical Support

• C:\Pagefile.sys • D:\Pagefile.sys Contact your local Teradata customer account representative if you have any other questions or concerns.

About Technical Support The Teradata Software Implementation Service is the recommended method for installing Teradata software in any environment. This service is designed to protect your IT investment by ensuring that your software is installed quickly and smoothly by Teradata experts, with minimal disruption of your day-to-day business routine. Contact your Teradata Sales Representative or Teradata Services Consultant to learn more about ordering this service. If you decide to install the software yourself, be advised that: • Your Teradata software must be under a valid Maintenance and Support agreement at the time of its installation. This ensures that you will have access to all updated documents and patches that might be required to complete the installation. Note: Service packs and operating system patches must be obtained from your operating system vendor. • Non-routine installation support and/or technical support required as a result of failure to follow guidelines herein is not included in your Maintenance and Support agreement and will be chargeable at the Additional Service Rates in effect at the time you report an incident. Contact your Teradata Sales Representative or Teradata Services Consultant to learn more about Maintenance and Support or Additional Service Rates agreements. To qualify for technical support following software installation: • Your system must be configured as described in this document. This ensures that you have the proper tools on the system and allows support engineers to gather diagnostic information if a problem occurs. • The Teradata software components must remain covered by a valid Maintenance and Support agreement.

Field Installation Guide for Teradata Node Software Windows Server 2003 (64 bit) Third-Party, Single Node System, Release 13.0

11

Chapter 1 Preparing for Software Installation About Technical Support

12

Field Installation Guide for Teradata Node Software Windows Server 2003 (64 bit) Third-Party, Single Node System, Release 13.0

CHAPTER 2

Installing and Configuring the WS 2003 Operating System

Before You Set Up the Operating System The Microsoft Windows Server 2003 operating system with service pack 2 is required. How to install the operating system is not covered in this document. See your vendor's installation guide for instructions. Caution: Teradata does not support systems running VMWare. The operating system must be installed natively. All system disks must be mirrored. If you are setting up a two-disk system, Disk 0 should be both the system disk and the application disk, and it should be mirrored by Disk 1. If you are setting up a four-disk system, Disk 0 should be mirrored by Disk 2, and Disk 1 should be mirrored by Disk 3. This permits a primary disk and its mirror to be on different SCSI channels and protects the system from becoming unbootable if an internal SCSI controller fails. Disk 0 should be the system disk, and Disk 1 should be the application disk. When installing the Teradata Database software on a third-party system, for best performance set up the data hard drives into two mirrored drives of equal size. If you are using RAID 5, it is best to have as few drives in a drive group as possible. The manufacturer provides detailed instructions describing how to configure the arrays of the physical drives and configure the logical drives. For the Parallel Upgrade Tool (PUT) to recognize the Windows disk devices as candidates for Teradata pdisks during configuration, follow these guidelines: • Format the disks as Basic, not Dynamic • Verify that the disks are visible to Windows (that is, the disks must show up as “online” in the Windows disk manager display) • Do not assign drive letters to the disks • It is preferable that the disks not be partitioned so PUT can create the proper partitioning for Teradata • If the disks are already partitioned, all partitions should be the same size and unformatted • The partition for the operating system must be listed as drive C • To prevent the CD drive letter from interfering with the drive letters assigned to the hard disks later, change the letter from its current letter (probably D) to Z

Field Installation Guide for Teradata Node Software Windows Server 2003 (64 bit) Third-Party, Single Node System, Release 13.0

13

Chapter 2 Installing and Configuring the WS 2003 Operating System Configuring NetMeeting and Remote Desktop Sharing (Optional)

Configuring NetMeeting and Remote Desktop Sharing (Optional) NetMeeting speeds up some remote support activities and allows remote access while in Safe Mode. To enable NetMeeting for remote support, configure NetMeeting's Remote Desktop Sharing as follows. Note: If Remote Desktop Sharing is not configured or is later disabled, there may be significantly longer unavailability times for some system recovery scenarios. 1 Log on to the node. 2 Select Start > Run. 3 In the Run window: a Type conf. b Click OK. 4 In the initial NetMeeting setup window, click Next. 5 Enter the information requested in the next window and click Next.

Note: This information is only used to set up NetMeeting and does not have to be valid. 6 In the next window: a Clear Log on to a directory server when NetMeeting Starts. b Select Do not list my name in the directory. c Click Next. 7 Select Local Area Network and click Next. 8 In the next window: a Clear Put a shortcut to NetMeeting on my desktop. b Clear Put a shortcut to NetMeeting on my Quick Launch bar. c Click Next. 9 Click Next through the subsequent screens until you get to the end. 10 Click Finish.

The NetMeeting application starts up and allows configuration of Remote Desktop Sharing. 11 In the NetMeeting window: a Open the Tools menu. b Select Remote Desktop Sharing. 12 In the Welcome window, click Next. 13 When reminded that you must have administrator privileges and use the administrator

password to use Remote Desktop Sharing, click Next.

14

Field Installation Guide for Teradata Node Software Windows Server 2003 (64 bit) Third-Party, Single Node System, Release 13.0

Chapter 2 Installing and Configuring the WS 2003 Operating System Configuring Pagefile (Required) 14 When asked if you want to enable a password-protected screen saver, select No, I will

do this later and click Next.

15 When told that you have successfully set up the computer to use Remote Desktop

Sharing, click Finish.

16 Select Tools > Options. 17 In the Options window: a Click the Security tab. b Select I prefer to receive secure incoming calls. c Select I prefer to make secure outgoing calls. d Click OK. 18 In the NetMeeting window, select Call > Exit and Activate Remote Desktop Sharing.

Configuring Pagefile (Required) Pagefile is required to support memory dumps and to provide enough virtual memory for the Teradata Database and other applications to run properly. 1 Select Start > Settings > Control Panel > System. 2 In the System Properties window: a Click the Advanced tab. b Click Settings in the Performance area. 3 In the Performance Options window: a Click the Advanced tab. b Click Change. 4 In the Virtual Memory window: a Highlight Drive C. b In the Paging file size for selected drive section, set Initial size and Maximum size

to the same size as the physical memory size. For example, a 32 GB node would be set to 32768 MB.

c Click Set. d Click OK.

If you are told that you that you must reboot for the changes you made to take effect, click OK. 5 In the Performance Options window, click OK. 6 In the System Properties window, click OK.

Field Installation Guide for Teradata Node Software Windows Server 2003 (64 bit) Third-Party, Single Node System, Release 13.0

15

Chapter 2 Installing and Configuring the WS 2003 Operating System Installing the Support Tools (MSDN/Retail) (Required)

If you are asked if you want to restart the computer now, click No. 7 Close the System Properties window.

Installing the Support Tools (MSDN/Retail) (Required) Perform this task only when installing the operating system from a Retail version or MSDN. 1 Insert the Microsoft Windows Server 2003 operating system disk. 2 On the disk, navigate to the \SUPPORT\TOOLS folder and double-click SUPTOOLS.MSI. 3 In the Welcome window, click Next. 4 In the End User License Agreement window: a Read the license agreement. b Select I Agree. c Click Next. 5 In the User Information window: a Enter the names of the user and the business organization. b Click Next. 6 In the Destination Directory window: a Accept the default C:\Program Files\Support Tools folder. b Click Install Now. 7 In the Completing the Windows Support Tools Setup window, click Finish. 8 In the \SUPPORT\TOOLS folder: a Double-click the deploy.cab file. b Highlight all the files within this compressed file. c Copy and paste the files into the C:\Program Files\Support Tools folder. 9 Remove the disk.

Changing the Windows Explorer Options (Required) To aid in troubleshooting, change the Windows Explorer options so you can see file extensions, file attributes, and system files. 1 Right-click Start and select Explore.

16

Field Installation Guide for Teradata Node Software Windows Server 2003 (64 bit) Third-Party, Single Node System, Release 13.0

Chapter 2 Installing and Configuring the WS 2003 Operating System Changing the Event Viewer Settings (Required) 2 In the Start Menu window, select Tools > Folder Options. 3 In the Folder Options window, click the View tab and set the following recommended

options:

a Select Show hidden files and folders. b Clear Hide extensions for known file types. c Clear Hide protected operating system files (Recommended).

If you are warned that you have chosen to display protected operating system files, click Yes. d Click OK. 4 Close the Start Menu window.

Changing the Event Viewer Settings (Required) Due to the high volume of event logging activity associated with the Parallel Database Extension (PDE) operations, change the Event Viewer settings to provide a larger file with wrapping enabled. 1 Select Start > Programs > Administrative Tools > Event Viewer. 2 In the Event Viewer window: a Right-click Application. b Select Properties. 3 In the Application Properties window: a Click the General tab. b Verify the Maximum log size is 16384 KB. c Verify that Overwrite events as needed is selected. d Click OK. 4 In the Event Viewer window: a Right-click System. b Select Properties. 5 In the System Properties window: a Click the General tab. b Verify the Maximum log size is 16384 KB. c Verify that Overwrite events as needed is selected. d Click OK.

Field Installation Guide for Teradata Node Software Windows Server 2003 (64 bit) Third-Party, Single Node System, Release 13.0

17

Chapter 2 Installing and Configuring the WS 2003 Operating System Updating the C:\boot.ini File 6 Close the Event Viewer window.

Updating the C:\boot.ini File Edit the C:\boot.ini file to enable the node to boot from the boot disk to Disk 1 if Disk 0 fails. Entries are also included to enable Safe Mode boot options for easier repair and recovery if necessary. Updating the C:\boot.ini file is only required if the root disk is configured as a software RAID mirror. If the system is using hardware RAID mirroring for the root disk, the C: \boot.ini file should not be updated. Note: If you have not selected to "Show hidden files and folders" in the Tools > Folder Options, you will not see the C:\boot.ini file. Note: In the lines beginning with "multi," enter the text as one continuous line; do not enter line breaks as shown in the example. 1 If necessary, make the boot.ini file writable. a On the desktop, double-click My Computer. b Double-click the C drive. c Right-click boot.ini and select Properties. d At the Boot.ini Properties window, General tab, clear the Read-only check box, then

click OK.

2 Edit the C:\boot.ini file to match the example shown below. [boot loader] timeout=10 default=multi(0)disk(0)rdisk(0)partition(2)\WINDOWS redirect=COM2 redirectbaudrate=9600 [operating systems] multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Windows Server 2003 Enterprise x64 Edition" /noexecute=optout /fastdetect /redirect multi(0)disk(0)rdisk(1)partition(2)\WINDOWS="Windows Server 2003 Enterprise x64 Edition - FT Mirror" /noexecute=optout /fastdetect /redirect multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Windows Server 2003 Enterprise x64 Edition - Safe Mode" /safeboot:minimal /sos /bootlog /noguiboot multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Windows Server 2003 Enterprise x64 Edition - Safe Mode with Networking" /safeboot:network /sos /bootlog /noguiboot

3 Save the changes you've made and exit the boot.ini file. 4 Make the boot.ini file read-only again. a Right-click boot.ini and select Properties.

18

Field Installation Guide for Teradata Node Software Windows Server 2003 (64 bit) Third-Party, Single Node System, Release 13.0

Chapter 2 Installing and Configuring the WS 2003 Operating System Installing the MultiLanguage Software (Optional) b At the Boot.ini Properties window, General tab, check the Read-only check box,

then click OK.

5 Close the C window.

Installing the MultiLanguage Software (Optional) Prerequisite: You must have the Microsoft Windows Server 2003 Operating System disk and the Microsoft Windows Server 2003 Multilanguage disk. This topic describes how to set up the operating system for languages other than English. You can have several languages installed with one default language that is normally used. The standard languages are English, French, German, Japanese, and Spanish. Other languages may be specified on the customer order. 1 Insert the Microsoft Windows Server 2003 Multilanguage disk. 2 In the MultiLanguage File Installation window: a Select the languages you want to install.

To uninstall a language, clear the check box, then click OK. b Select the language to be used as the default. c Click OK.

A Copying Files window shows the files copied from the disk to the system drive. Depending on the languages you chose, you may see the Installation Complete window almost immediately. If a Files Needed window appears, navigate to the i386 folder on the Microsoft Windows Server 2003 Operating System disk and click OK. 3 When prompted, insert the Multilanguage disk again, and click Yes.

A Copying Files window shows the files copied from the Multilanguage disk to the system drive. An Installing MultiLanguage Files window shows each language as it is being installed. 4 In the Installation Complete window, click OK. 5 In the next window, click Yes to reboot for the new settings to take effect.

Configuring Terminal Services for Remote Connectivity (Recommended) 1 Select Start > Run. 2 In the Run window: a Type gpedit.msc. b Click OK.

Field Installation Guide for Teradata Node Software Windows Server 2003 (64 bit) Third-Party, Single Node System, Release 13.0

19

Chapter 2 Installing and Configuring the WS 2003 Operating System Setting Up Remote Connectivity (Recommended) 3 In the Group Policy window select Computer Configuration > Administrative

Templates > Windows Components > Terminal Services.

4 In the Terminal Services frame: a Right-click Restrict Terminal Services users to a single remote session. b Select Properties. 5 In the Restrict Terminal Services window: a Click the Setting tab. b Select Disabled. c Click OK. 6 Close the Group Policy window.

Setting Up Remote Connectivity (Recommended) This topic describes how to set up the ability to have multiple remote sessions for users. 1 Select Start > Settings > Control Panel > System. 2 In the System Properties window: a Click the Remote tab. b Select Enable Remote Desktop on this computer. c Click Select Remote Users. 3 In the Remote Desktop Users window, click Add. 4 In the Select Users window: a Enter the users who will be allowed to connect to this computer.

Note: Members of the Administrator group have access without being added. b Click OK. 5 In the Remote Desktop Users window, click OK. 6 Close the System Properties window.

Disabling the Event Tracker (Required) 1 Select Start > Run. 2 In the Run window: a Type gpedit.msc. b Click OK.

20

Field Installation Guide for Teradata Node Software Windows Server 2003 (64 bit) Third-Party, Single Node System, Release 13.0

Chapter 2 Installing and Configuring the WS 2003 Operating System Disabling the Windows Firewall, Internet Connection Sharing, and Automatic Updates (Required) 3 In the Group Policy window, select Computer Configuration > Administrative

Templates > System.

4 In the System frame: a Right-click Display Shutdown Event Tracker. b Select Properties. 5 In the Display Shutdown Event Tracker Properties window: a Click the Setting tab. b Select Disabled. c Click OK. 6 Close the Group Policy window.

Disabling the Windows Firewall, Internet Connection Sharing, and Automatic Updates (Required) 1 Select Start > Settings > Control Panel > Windows Firewall. 2 In the Windows Firewall window: a Click the General tab. b Select Off. c Click OK. 3 Select Start > Settings > Control Panel > Administrative Tools > Services. 4 In the Services window, double-click Windows Firewall/Internet Connection Sharing

(ICS).

5 In the Windows Firewall/Internet Connection Sharing (ICS) window: a Click the General tab. b Set Startup type to Disabled. c Click Stop. d Click OK. 6 Select Start > Settings > Control Panel > Administrative Tools > Services. 7 In the Services window, double-click Automatic Updates. 8 In the Automatic Updates window: a Click the General tab. b Set Startup type to Disabled.

Field Installation Guide for Teradata Node Software Windows Server 2003 (64 bit) Third-Party, Single Node System, Release 13.0

21

Chapter 2 Installing and Configuring the WS 2003 Operating System Disabling the Windows Firewall, Internet Connection Sharing, and Automatic Updates (Required) c Click Stop. d Click OK. 9 Close the Services window.

22

Field Installation Guide for Teradata Node Software Windows Server 2003 (64 bit) Third-Party, Single Node System, Release 13.0

CHAPTER 3

Installing the Microsoft Debugging Tools and Retail Symbols

Installing the Microsoft Debugging Tools The Microsoft debugging tools must be installed before requesting any support from Teradata. 1 Go to the following Microsoft website:

For 64-bit tools: http://www.microsoft.com/whdc/devtools/debugging/install64bit.mspx For 32-bit tools:http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx Note: If this URL is no longer correct, find the new URL from Microsoft’s main web page, http://www.microsoft.com. 2 Install the appropriate debugging tools for your system.

Installing the Microsoft Retail Symbols The Microsoft retail symbols must be installed before requesting any support from Teradata. 1 Go to the following Microsoft website:

http://www.microsoft.com/whdc/devtools/debugging/symbolpkg.mspx Note: If this URL is no longer correct, find the new URL from Microsoft’s main web page, http://www.microsoft.com. 2 In the Download Windows Symbol Packages window, click Windows Server 2003 and

Windows XP x64 Edition.

3 Install the appropriate retail symbols for your system.

Field Installation Guide for Teradata Node Software Windows Server 2003 (64 bit) Third-Party, Single Node System, Release 13.0

23

Chapter 3 Installing the Microsoft Debugging Tools and Retail Symbols Installing the Microsoft Retail Symbols

24

Field Installation Guide for Teradata Node Software Windows Server 2003 (64 bit) Third-Party, Single Node System, Release 13.0

CHAPTER 4

Installing the Visual Studio 64-bit Compiler

Installing the Visual Studio 64-bit Compiler Prerequisite: The Microsoft Visual Studio software must have been ordered separately. To support system and customer Stored Procedures or User Defined Functions, a compatible C++ compiler must be installed. See Knowledge Article KAP1952DA, accessible from Teradata @ Your Service, for further information on compatible compilers. Note: In this procedure, Visual Studio 2005 is used as an example. 1 Insert the Microsoft Visual Studio disk.

Setup should begin automatically. If it doesn't, navigate to the CD-ROM drive and double-click the setup.exe file. 2 Select Install Visual Studio 2005 and click Next. 3 Accept the license agreement, enter the Product Key, and click Next. 4 Under Select Features to Install, select Custom and click Next. 5 Select Features to Install again. 6 Expand Visual C++, check the X64 Compilers and Tools check box, clear the SQL

server install check box, and click Install. Leave all other defaults checked.

7 When asked, insert the second disk and follow the prompts to Finish. 8 If prompted to reboot the system, do so; otherwise no reboot is required. 9 Restart the database so that it detects the compiler. 10 Go to the Teradata command window and run the following command to check

whether the startup routine is able to find the compiler:

C:\Documents and Settings\Administrator> cufconfig -o 11 If the compiler has been properly installed, you will see output similar to that shown

below.

Go to the folder specified in the compiler path (in this example, C:\Program Files (x86)\Microsoft Visual Studio 8\VC\bin\amd64) and verify that the CL.EXE file exists.

Version: 6 ModTime: 1219773826 SWDistNodeID: 33 SourceDirectoryPath: C:\Program Files\teradata\Tdat\tdconfig\teradata\tdbs_udf\usr\ CompilerTempDirectory: C:\Program Files\teradata\Tdat\TdTemp\UDFTemp\

Field Installation Guide for Teradata Node Software Windows Server 2003 (64 bit) Third-Party, Single Node System, Release 13.0

25

Chapter 4 Installing the Visual Studio 64-bit Compiler Installing the Visual Studio 64-bit Compiler

UDFLibraryPath: C:\Program Files\teradata\Tdat\tdconfig\udflib\ CompilerPath: C:\Program Files (x86)\Microsoft Visual Studio 8\VC\bin\amd64\CL.EXE LinkerPath: C:\Program Files (x86)\Microsoft Visual Studio 8\VC\bin\amd64\LINK.EXE UDFServerMemPath: C:\Program Files\teradata\Tdat\TdTemp\udfsrv\ MaximumCompilations: 10 UDFServerTasks: 2 SecureServerAMPs: 20 ParallelUserServerAMPs: 2 SecureServerPEs: 20 ParallelUserServerPEs: 2 TDSPLibBase: C:\Program Files\teradata\Tdat\tdconfig\tdsplib\ SecureGroupMembership: tdatudf

26

Field Installation Guide for Teradata Node Software Windows Server 2003 (64 bit) Third-Party, Single Node System, Release 13.0

CHAPTER 5

Downloading and Installing Software

Obtaining a Teradata Change Control Number You must have a Teradata Change Control Number in order to download the latest PUT software and Teradata Database software patches from Teradata @ Your Service. 1 Open an incident through Teradata @ Your Service at http://

www.teradataatyourservice.com to obtain a Teradata Change Control Number. Change Control Numbers are valid for 365 days, as long as a valid support contract is in place.

2 Record the Change Control Number for future use.

Downloading and Installing Software This topic contains instructions on how to get and install the other software required to successfully run your Teradata system. Warning: Do not change the name of any software package. In some cases, there may be both a base package on the CD and a patch on Teradata @ Your Service. In these cases, both must be installed. For example, for the Teradata Database, both TNT and TNT_x8664 are required. 1 Make sure that all hardware and storage is set up before installing software. 2 Using the following commands, create a folder on the node into which you will copy the

packages to be installed. In this example, the folder will be called Base. cd /home /home #mkdir Base /home #

3 Insert the Teradata Database disk. 4 Copy the following packages from the CD to the folder you created:

• • • • • •

bteq bynet cliv2 dul dultape fastld

Field Installation Guide for Teradata Node Software Windows Server 2003 (64 bit) Third-Party, Single Node System, Release 13.0

27

Chapter 5 Downloading and Installing Software Downloading and Installing Software

• • • •

piom tdicu TeraGSS TNT

Warning:: Do not copy or install the following packages from the CD: • adept • BootDiskMon • certifiedHotfixes_WS03SP2_x8664 • FaultDetector • LSI_7X02XP_FW • LsiHbaUtils • MDS • OpenPERL • OpenSSH • PCI-Configurator • PERL_Modules • ppc2fw • ppc4fw • SHCW • SM3G_KCS_x8664 • SM3G_Node • WinTools • WS03_ServicePack_x8664 After all packages and patches have been installed, PUT reboots the server. 5 After the server reboots, start PUT again and select the Install/Upgrade Software

operation. It should show that it is in a restartable state.

6 Using the following commands, create a folder on the node into which you will copy the

patches to be installed. In this example, the folder will be called Patches. cd /home /home #mkdir Patches /home #

7 Log on to Teradata @ Your Service at http://www.teradataatyourservice.com and select

the following:

28

Menu/Section

Selection

Teradata @ Your Service - Home

Software Downloads

Software Downloads

Certified Configs

Certification Lists

Current Lists

Node Type

Single Node

Field Installation Guide for Teradata Node Software Windows Server 2003 (64 bit) Third-Party, Single Node System, Release 13.0

Chapter 5 Downloading and Installing Software Downloading and Installing Software

Menu/Section

Selection

Target OSs

Your operating system

Application Version

n/a

Teradata Releases

Version of Teradata being installed

Bus Type

SM3G

8 Download the following packages and patches:

• • • • • • • • • • • • • • •

bteq bynet cliv2 cliv2_x8664 dul JRE5_64 piom PUTTools tdicu tdicu_x8664 tdodbc TDput TeraGSS TeraGSS_x8664 TNT

9 After downloading, transfer the files to the Patches folder you created.

Note: Do not unzip or untar the packages. 10 Install the Parallel Upgrade Tool (PUT) as described in the Parallel Upgrade Tool (PUT)

Reference.

Note: The most current version of PUT is required. 11 Use PUT to set the system parameters as described in the Parallel Upgrade Tool (PUT)

Reference.

12 Use PUT's Install/Upgrade Software operation to install the selected software packages

on the node as described in the Parallel Upgrade Tool (PUT) Reference.

Field Installation Guide for Teradata Node Software Windows Server 2003 (64 bit) Third-Party, Single Node System, Release 13.0

29

Chapter 5 Downloading and Installing Software Downloading and Installing Software

30

Field Installation Guide for Teradata Node Software Windows Server 2003 (64 bit) Third-Party, Single Node System, Release 13.0

CHAPTER 6

Configuring and Initializing the Teradata Database

Configuring and Initializing the Teradata Database 1 Verify the correct Teradata Database patch version is installed: a Start > All Programs > Teradata Database > Teradata Command Prompt. b Enter tdatcmd to properly set the path for the session. c Enter pdepath -i.

The following is an example of the output: vader:~# pdepath -i PDE: 13.00.00.07 TDBMS: 13.00.00.09 TDGSS: 13.00.00.03 TGTW: 13.00.00.05 PDEGPL: 13.00.00.07 vader:~

Warning: If the base version (xx.xx.xx.00) is shown, do not proceed with configuring Teradata. Contact the Teradata Global Support Center for assistance. 2 Use PUT's Configure Teradata operation to configure and initialize the Teradata

Database. See the Parallel Upgrade Tool (PUT) Reference, B035-5713.

Field Installation Guide for Teradata Node Software Windows Server 2003 (64 bit) Third-Party, Single Node System, Release 13.0

31

Chapter 6 Configuring and Initializing the Teradata Database Configuring and Initializing the Teradata Database

32

Field Installation Guide for Teradata Node Software Windows Server 2003 (64 bit) Third-Party, Single Node System, Release 13.0

CHAPTER 7

Post-Setup Activities

About Post-Setup Activities For the protection of the data on your system, Teradata recommends that you follow the manufacturer's instructions to perform certain tasks. For example, create the following: • Emergency repair disk • Backup tape

Field Installation Guide for Teradata Node Software Windows Server 2003 (64 bit) Third-Party, Single Node System, Release 13.0

33

Chapter 7 Post-Setup Activities About Post-Setup Activities

34

Field Installation Guide for Teradata Node Software Windows Server 2003 (64 bit) Third-Party, Single Node System, Release 13.0