Linux, Windows Server 2003, MP-RAS

Transcription

1 What would you do if you knew? Teradata Database Node Software Upgrade Guide: Overview and Preparation Linux, Windows Server 2003, MP-RAS Release 14.0 and Later B K July 2017

2 The product or products described in this book are licensed products of Teradata Corporation or its affiliates. Teradata, Applications-Within, Aster, BYNET, Claraview, DecisionCast, Gridscale, QueryGrid, SQL-MapReduce, Teradata Decision Experts, "Teradata Labs" logo, Teradata ServiceConnect, Teradata Source Experts, WebAnalyst, and Xkoto are trademarks or registered trademarks of Teradata Corporation or its affiliates in the United States and other countries. Adaptec and SCSISelect are trademarks or registered trademarks of Adaptec, Inc. 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, 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 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. 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 noninfringement. Some jurisdictions do not allow the exclusion of implied warranties, so the above exclusion may not apply to you. In no event will Teradata Corporation be liable for any indirect, direct, special, incidental, or consequential damages, including lost profits or lost savings, even if expressly advised of the possibility of such damages. The information contained in this document may contain references or cross-references to features, functions, products, or services that are not announced or available in your country. Such references do not imply that Teradata Corporation intends to announce such features, functions, products, or services in your country. Please consult your local Teradata Corporation representative for those features, functions, products, or services available in your country. Information contained in this document may contain technical inaccuracies or typographical errors. Information may be changed or updated without notice. Teradata Corporation may also make improvements or changes in the products or services described in this information at any time without notice. To maintain the quality of our products and services, we would like your comments on the accuracy, clarity, organization, and value of this document. Please teradata-books@lists.teradata.com Any comments or materials (collectively referred to as "Feedback") sent to Teradata Corporation will be deemed non-confidential. Teradata Corporation will have no obligation of any kind with respect to Feedback and will be free to use, reproduce, disclose, exhibit, display, transform, create derivative works of, and distribute the Feedback and derivative works thereof without limitation on a royalty-free basis. Further, Teradata Corporation will be free to use any ideas, concepts, know-how, or techniques contained in such Feedback for any purpose whatsoever, including developing, manufacturing, or marketing products or services incorporating Feedback. Copyright by Teradata. All Rights Reserved.

3 Preface Purpose The purpose of this guide, Teradata Database Upgrade Guide: Overview and Preparation, is to provide an overview of the Teradata Database upgrade process, and describe how Teradata customers and Teradata Customer Services associates collaborate to prepare for and plan a Teradata Database upgrade. In this guide you will find conceptual and background information about the various upgrade paths, the tools and methods available for an upgrade, and how the Teradata Database software and packages are distributed. The guide includes high-level descriptions of the processes that occur for each upgrade path, and who is expected or authorized to perform the upgrade. It does not include procedure or step-by-step task information, but focuses on the how and why of the process. Use this guide in conjunction with the appropriate version of the Teradata Database Upgrade Guide, published specific to your target Teradata Database release, hardware platform, and operating system environment. These guides provide procedures and step-by-step task information intended to support specific upgrades. Audience This guide is intended for use by Teradata customers, Teradata Customer Service Representatives, and other Teradata associates who need to understand the concepts related to a Teradata Database upgrade. Supported Software Releases This guide supports upgrades for Teradata Database Release 14.0 and subsequent releases. It covers all supported operating system environments. Revision History Date July 2017 August 2016 June 2015 March 2014 Description Added information for Teradata Database Release Added information for Teradata Database Release Added information for Teradata Database Release Added information for Teradata Database Release Upgrade Guide: Overview and Preparation 3

4 Preface Additional Information Date September 2013 June 2013 August 2010 April 2009 Description Added "Using Hardware Compression with Teradata DSA" to "Implementing Backup and Restore Solution" Added information for Teradata Database Release Added information on setting flags for Teradata Database Release backdown considerations Initial Release Additional Information Related Links URL Description External site for product, service, resource, support, and other customer information. External site for published Teradata customer documentation. External site for access to the Teradata software server. Only accessible with an active service contract. Product Safety Information This document may contain information addressing product safety practices related to data or property damage, identified by the word Notice. A notice indicates a situation which, if not avoided, could result in damage to property, such as equipment or data, but not related to personal injury. Example Notice: Improper use of the Reconfiguration utility can result in data loss. 4 Upgrade Guide: Overview and Preparation

5 CHAPTER 1 Introduction to the Teradata Database Upgrade Process About the Teradata Database Upgrade Process This guide provides a conceptual overview of the issues and processes involved in an upgrade, and provides recommendations on how customers should plan, prepare for, and execute a Teradata Database Release upgrade. Included in this guide are: Definitions of processes and upgrade path types Descriptions of the tools and methods used during upgrades Explanations of the types of upgrade procedures that may be performed by customers Descriptions of the software media used in upgrades Planning timelines and checklists Descriptions of procedures that must be performed prior to an upgrade An overview of the upgrade procedures Descriptions of activities that occur after the upgrade Your Service Agreement Consult your Teradata Service Agreement to determine the CS upgrade services to which you are entitled and those that may be purchased separately. Type of Service Agreement Available to Type of Coverage Business Critical Teradata EDW customers Full upgrade planning Change control Implementation services Base Teradata EDW customers Upgrade support is available for purchase through Teradata's Software Implementation (SWI) suite of offers. Core Support Teradata Appliance customers Upgrade support is available for purchase through Teradata's SWI suite of offers. Customers with either a base service agreement or a core support agreement are strongly encouraged to take advantage of the Teradata SWI offer program. If an SWI offer is not purchased, the customer may perform an unassisted upgrade. Upgrade Guide: Overview and Preparation 5

6 Chapter 1: Introduction to the Teradata Database Upgrade Process Release Numbering Standards Contacting Teradata Your Teradata Service Consultant can assist you in choosing the right upgrade service option for your environment. Customers with a Business Critical service agreement can consult directly with their Customer Service Representative (CSR) for upgrade planning and implementation questions. Customers choosing an SWI option or the unassisted upgrade option can get basic questions answered by opening an incident through Service. Release Numbering Standards Teradata Database software follows a standard release numbering convention. When planning an upgrade, it is important to understand the definition of the version numbering. A Teradata Database version number uses the format of 4 two-digit qualifiers, separated by periods. For example: Note: The release numbers used as examples here do not reflect actual Teradata Database software versions. The first qualifier (16 in the example) identifies a major release number. The second qualifier (10 in the example) identifies a minor release number. The third qualifier (01 in the example) identifies a maintenance release number. The fourth qualifier (03 in the example) identifies a patch or efix number. Process Definitions There are three process paths to moving to a new Teradata Database Release. As you consider moving to a new Teradata Database Release, you will need to determine which process path you should use: Database Upgrade Migration Fresh Installation Here are basic definitions for the process paths: Database Upgrade A database upgrade is the process of modifying the Teradata Database software with a new version of the software on a computer system that is already running a previous version. The user data remains in place on the disk arrays. Migration A migration process involves archiving user data from a source system, then restoring that data to a destination system. The destination system must have Teradata Database installed before the migration process occurs. Fresh Installation A fresh installation is generally the first instance of installing Teradata Database on a computer system. Teradata performs the initial installation on every system it manufactures. In some cases, such as when 6 Upgrade Guide: Overview and Preparation

7 Chapter 1: Introduction to the Teradata Database Upgrade Process About Upgrade Path Types changing to a different operating system, a fresh installation is performed at a customer site on a system that has been reconfigured and does not currently contain Teradata Database software. About Upgrade Path Types Upgrades are classified into the following categories: Upgrade Type Major Minor Performed By Teradata Customer Services Teradata Customer Services Maintenance/Patch Teradata Customer Services Customer Installation/Migration Teradata Customer Services In some cases, instead of an upgrade process, a system upgrade is accomplished using a migration. Major Upgrade Path A Teradata Database major release generally includes significant new features and enhancements, as well as changes incorporated in earlier versions as a result of Requests for Change (RFCs) and Discrepancy Reports (DRs). Upgrading to a major release involves moving to a new base version of Teradata Database and all associated patches. For example, moving from Teradata xx to Teradata 16.0 is a major upgrade. A major upgrade may involve the conversion of system tables, user data or custom user features. Software for a major release, provided through base packages, is distributed on CD-ROM or DVD, or through the Electronic Software Distribution method. Software patches are downloaded from the Teradata Software Server (TSS). Major upgrades are performed only by Teradata Customer Services. Minor Upgrade Path A Teradata Database minor release may include a number of new features and enhancements, as well as incorporating changes to previous releases made as a result of Requests for Change (RFCs) and Discrepancy Reports (DRs). For example, moving from Teradata 16.0 to is a minor upgrade. A minor upgrade generally does not include the conversion of system tables, user data or custom user features. However, depending on the features and enhancements included in a specific minor release, some minor upgrades can be more complex and require special handling. Software for a minor release, provided through base packages, is distributed on CD-ROM or DVD, or through the Electronic Software Distribution method. Software patches are downloaded from the Teradata Software Server (TSS). Minor upgrades are performed only by Teradata Customer Services. Upgrade Guide: Overview and Preparation 7

8 Chapter 1: Introduction to the Teradata Database Upgrade Process About Upgrade Path Types Maintenance and Patch Upgrade Path A Teradata Database maintenance release generally does not include many new features or enhancements. A maintenance release bundles all of the fixes to the previous major or minor release at a given point in time. For example, moving from Teradata 15.0 to is a maintenance upgrade. A single efix is typically released for an emergency fix. Teradata distributes patch or efix packages to correct problems in major, minor or maintenance releases. For example, Teradata Database is a patch release number. Patches and efixes are distributed on the Teradata Software Server (TSS). Efixes that have been certified by Teradata System Integration Testing are available for customer use on Your Service. To perform a patch upgrade, you must first have installed on your system the base packages of: PDE TDBMS tgtw Every subsequent patch package accumulates the changes provided in earlier patches for the particular maintenance release. For example, for maintenance release : Patch contains only one patch Patch contains two patches: Patch contains three patches: You only need to install patch to get the changes included in earlier patches.01 and.02. Maintenance and patch upgrades are considered customer-executable in most cases. Installation/Migration Path A migration process involves archiving user data from a source system, then restoring that data to a destination system. The destination system must already have Teradata Database installed before the migration process occurs. Teradata supports migrations from no more than two previous versions of the Teradata Database using the migration process. If your starting version is more than two versions removed from the target version, you may need to use a multi-step migration, involving intermediary Teradata versions. When moving from one operating system to another, a migration process is required. For example, moving from an MP-RAS system to a Linux system requires archiving user data from the source MP-RAS system, then restoring the data to a destination system running Linux. The destination system may be the same physical system as the source. In this case, after archiving the user data, the system requires a fresh installation of the operating system, the Teradata Database (either the same version or a more recent version), and other node software. Additionally, some hardware upgrades may be required. Consult your Teradata Services Consultant for details specific to your Teradata system. 8 Upgrade Guide: Overview and Preparation

9 Upgrade Tools and Methods Chapter 1: Introduction to the Teradata Database Upgrade Process Upgrade Tools and Methods Teradata provides a variety of tools and methods used during an upgrade. These tools and methods have been designed to plan and track the upgrade process, automate upgrade steps, reduce manual activity, and reduce or avoid downtime associated with implementing a new software version. What is the Change Control Process? The Change Control process is the formal process that Teradata Customer Services uses to proactively manage a customer's SWI-entitled system. It ensures that an effective plan is developed, approved, scheduled, and executed to provide the customer with the highest availability and a minimum of interruptions to their processing schedule. A Change Control incident is a critical component of the Change Control process. An incident is associated with a specific customer and planned change. Each incident associates specific customer and site information, a Change Control number, a Change Control plan, and status and approval information, as well as other documents related to the incident. The incident also includes information used by Teradata CS to track the activities associated with the incident and to maintain Customer Information records. A Change Control incident must be created for all system changes. Content and management practices for the Change Control incident will vary depending on the SWI service level entitlement defined for the customer's system. Change Control incidents should be created a minimum of 28 days prior to the estimated implementation date. In an emergency situation, this requirement may be waived. A Change Control number is required for both CSR-performed upgrades and customer-executed upgrades and is required to download software for the upgrade. Change Controls implemented for Business Critical or SWI-entitled systems include CSR consulting, Change Control plan preparation, software upgrade implementation, upgrade validation testing, as well as fallback and recovery planning. The plan includes activities to be performed by Teradata CS and the customer. The plan is reviewed by Teradata CS technical associates, and must be approved before the upgrade procedure begins. Changes made to a system during an upgrade are tracked in the Customer Information System, associated with the Change Control number. This ensures Teradata Customer Services has an accurate record of each system configuration. What Is PUT? The Parallel Upgrade Tool (PUT) is an intelligent, interactive software utility that automates much of the installation and upgrade processes for Teradata Database software. PUT is run via a web browser or as an application. PUT uses a graphical user interface (GUI) to install/ upgrade PUT and other software, as well as install and configure the Teradata Database. PUT installs or upgrades one or more software packages on a single node or simultaneously across multiple nodes of a Teradata system. By eliminating manual upgrade tasks, PUT greatly reduces the likelihood of errors occurring during the upgrade. By performing the upgrade in parallel across multiple nodes, PUT significantly reduces the amount of time needed to perform an upgrade. Upgrade Guide: Overview and Preparation 9

10 Chapter 1: Introduction to the Teradata Database Upgrade Process Acquiring the Software Media for an Upgrade What Is VM&F? Version Migration and Fallback is used for Business Critical and SWI-entitled systems to back down the software. Note: VM&F is supported for Teradata systems running either MP-RAS or Linux. It is not supported for systems running on Windows. VM&F is a method used when performing a Teradata Database upgrade where a new image of the active boot environment is created, including a complete version of the operating system and Teradata Database software. This new image is called the alternate boot environment (ABE). After the ABE is created, PUT is used to install or upgrade software in the ABE, allowing the upgrade to proceed without disturbing the current system environment. When the system is rebooted, the ABE becomes the active boot environment, also known as the primary boot environment (PBE). Teradata's standard upgrade practice is to utilize VM&F when upgrading operating system packages or performing a certified software list upgrade. Teradata CSR's and customers should jointly consider the benefits and considerations of VM&F during the upgrade planning process. VM&F is one of the significant benefits which Business Critical and SWI customers receive. Benefits of VM&F Using VM&F provides increased database availability during an upgrade, because upgrades are applied to the ABE while the database is fully accessible. There is no need to bring down the database prior to the node reboot at the conclusion of the upgrade. This allows much more flexibility in planning and scheduling an upgrade. In addition, VM&F supports a simple and quick fallback to the previous software version should the upgrade not be successful for some reason, such as regression or performance problems. If an upgrade fails, or the system does not boot properly after an upgrade, the system can be redirected to boot from the preupgrade software image. This is known as falling back. Considerations for Using VM&F VM&F requires additional internal disk space to contain the ABE. Most newer MP-RAS and Linux systems have been configured to use VM&F, so the additional internal disk space is already configured. If you are only installing packages that do not require a node reboot, using VM&F may extend the downtime. Changes to the database copied by VM&F into the ABE before the reboot are not automatically reflected in the ABE, and may require special handling. When using the VM&F approach, it may be necessary to stop user access to the database for applications, such as automatic loading, or for database backup processing. Acquiring the Software Media for an Upgrade Teradata Database software releases are available in three media formats: Teradata Software CD or DVD 10 Upgrade Guide: Overview and Preparation

11 Chapter 1: Introduction to the Teradata Database Upgrade Process Acquiring the Software Media for an Upgrade Compressed images of the Teradata Software CD or DVD, downloaded through the Electronic Software Distribution system Teradata Software Server (TSS) The format you use will depend on the type of upgrade and your support agreement with Teradata. CD & DVD Media A Teradata Software CD or DVD is used for major or minor software upgrades. Teradata Database major or minor releases are distributed on CD or DVD media. The media contains the entire set of base packages for the release. The quantity and type of CDs and DVDs you receive are based on the type of software purchase you've made. Electronic Software Distribution US customers using the electronic software distribution method can download compressed images of Teradata Software CD or DVD media, and Teradata Software documentation CDs. The Electronic Software Distribution (ESD) Guide is delivered as an attachment from Information Products, Teradata, along with other information needed to download and install software using this method. Teradata Software Server The Teradata Software Server (TSS) website contains the latest maintenance updates and patches to released Teradata Database, operating system, and Client software. Patch packages contain updates to the base packages which are distributed on the Teradata Database software CD or DVD. You must have the required base packages installed before you can apply maintenance or patch packages. Upgrade Guide: Overview and Preparation 11

12 Chapter 1: Introduction to the Teradata Database Upgrade Process Acquiring the Software Media for an Upgrade 12 Upgrade Guide: Overview and Preparation

13 CHAPTER 2 Database Upgrade Planning Overview of the Upgrade Procedure Phases The upgrade planning process includes scheduling of activities that must occur across multiple phases of the upgrade process, beginning one to two months prior to the actual upgrade, and completing a day or two following the upgrade. These phases include: Deciding on the upgrade target and method Creating a Change Control plan for the upgrade Preparing the system for the upgrade Preparing the Teradata Database for the upgrade Preparing for the upgrade procedure Performing the upgrade Performing post-upgrade activities Choosing the Upgrade Target Release For a major or minor Teradata Database upgrade, decide the Teradata Database release you want to upgrade to by reviewing information about the features and requirements contained in the releases and the associated Teradata Tools and Utilities. Consult with your Teradata Solutions Architect for your overall Teradata Warehouse operation and with your CSR about any additional requirements for updating the hardware platform model(s), storage arrays, and other applications and processes running on your system. For a maintenance or patch upgrade, you will only be updating your current Teradata Database release and will not need to choose a different target release. Choosing the Upgrade Process There may be special circumstances where you would choose a migration or fresh installation to achieve the upgrade results you want. For example, if you are on an older Teradata Database version that is not the minimum level for a specific upgrade, a standard database upgrade will not work. Your system will require special handling, which could include a two-phase upgrade or a data migration. Note: See IDA00108C82, Minimum Starting Version and Free Space Requirements for Teradata Database Upgrades and Migrations for more information. Customers can access this document by doing a general search on the document number from Your Service ( If you want to move to a different operating system as part of the upgrade, your system will require a data archive, a fresh installation of the operating system and the Teradata database, and a restore of the data. Upgrade Guide: Overview and Preparation 13

14 Chapter 2: Database Upgrade Planning Creating an Upgrade Plan Consult with your Teradata Services Consultant to determine the upgrade process appropriate for your system and target upgrade version. Choosing to Use VM&F or Non-VM&F Business Critical and SWI customers should consult with their Teradata CSR to determine if VM&F should be employed for the upgrade. Note: VM&F is supported for Teradata systems running either MP-RAS or Linux. It is not supported for systems running on Windows. Creating an Upgrade Plan The upgrade plan outlines the implementation, test, backout, and recovery plans for the upgrade process. Subsequent chapters in this document provide more information that will help you create the plan. Your Teradata CSR creates the upgrade plan for Business Critical and SWI customers. Customers who choose to perform maintenance or patch/efix upgrades unassisted can access a Teradata Database Upgrade Guide specific to their hardware platform, operating system, and Teradata Database release through Your Service. These guides provide details for the activities and procedures used in the specific upgrade context. Teradata CSRs can access documentation for major upgrades specific to the hardware platform, operating system and Teradata Database release to assist in preparing the upgrade plan. The plan should include all other activities that are required for the system either before or after the actual upgrade. These activities may require a separate Change Control incident, and include such items as: Updates to system components, such as the Administration Workstation (AWS), node memory, or firmware Implementation of a Teradata Open Backup solution, if not already in place Upgrading to the latest required Teradata Tools and Utilities Third party applications that communicate with the database must be compatible with the Teradata Database software, such as BusinessObjects, Microstrategies, etc. Teradata applications that communicate with the Teradata database, such as CRM, TMSM, Viewpoint, etc. The plan must designate who is responsible for performing all activities associated with the upgrade: Teradata CS, Teradata Professional Services (PS), the customer, or another vendor. Include a timeline in the plan, showing when each of the activities will be performed. The Change Control incident number is included with the plan. Business Critical and SWI customer upgrade plans are reviewed and approved by Teradata CS before the upgrade begins. Overview of the Upgrade Timeline The upgrade timeline must account for all the activities that occur during the multiple phases of an upgrade. If your system has Business Critical support or is SWI entitled, consult with your Teradata CSR or open an incident to request a Teradata CSR call you to review documentation specific to the Teradata Database upgrade target and process to determine the set of activities required to upgrade your system. Major upgrades generally require more activities and consequently more time for preparation and execution. 14 Upgrade Guide: Overview and Preparation

15 High Density systems can take substantially longer to upgrade. Use the Estimator tool and review the output carefully to determine the approximate time. This topic provides an overview of the types of activities that occur during the preparation, pre-operation activities, upgrade, and post-upgrade phases of an upgrade, to help you create a timeline for the upgrade. Not all activities are required for every upgrade; some activities are optional. More detailed information about these activities is included in subsequent chapters of this guide. For specific step-by-step instructions on how to perform these activities, refer to the Teradata Database Upgrade Guide associated with your target release, operating system, and platform hardware. One to Three Months Prior to the Planned Upgrade Once you have determined the Teradata Database upgrade target and process, you will need between 4 and 12 weeks to prepare for the upgrade. During this period, your system will be analyzed to determine if any changes need to be made prior to the upgrade, and you will schedule these changes to be implemented. Open a Change Control incident and obtain a Change Control number Determine if the CMIC needs to be upgraded; if so, schedule the upgrade well in advance Implement an Open Teradata Backup solution, if not already implemented Install or upgrade to the latest set of required Teradata Tools and Utilities Upgrade firmware on all systems to the latest Teradata certified releases Examine the memory size of the nodes to determine if they meet the requirement for the target release Obtain the required software media Install or upgrade to the latest released version of TDput, PUTSRC, and PUTTools Run the following to determine whether the system and database are prepared for the upgrade: PUT System Readiness Check (SRC) Pre-Upgrade Preparation script (found in PUTTools package) Run the Cylinder Index Space Test Run SCANDISK and CheckTable to validate the structure of the database files and tables. Run the Upgrade Estimator tool to estimate the time required for the upgrade If running 3rd party applications on the TPA nodes, verify compatibility with the Teradata versions you are upgrading to If running any Teradata applications such as TCRM, verify compatibility with the Teradata version you are upgrading to Any problems or issues found during this phase must be corrected or addressed. If changes to the system are required, you must allocate sufficient time to make these changes before performing the upgrade. One Week Prior to the Planned Upgrade Consult with the system administrator to schedule system downtime, and notify users Run SCANDISK and CheckTable again, if not performed in the past 30 days Obtain sufficient tape media for a data archive Ensure sufficient free space is available in the node file system Ensure you have installed or upgraded to the latest version of TDput, PUTSRC, and PUTTools One Day Prior to the Planned Upgrade Archive user data Save Crashdumps Chapter 2: Database Upgrade Planning Creating an Upgrade Plan Upgrade Guide: Overview and Preparation 15

16 Chapter 2: Database Upgrade Planning Creating an Upgrade Plan Immediately Prior to the Upgrade Just before you begin the actual upgrade process, you must perform these activities: Ensure all ETL operations are complete. Back up system disks Stop Replication Services Ensure you have installed or upgraded to the latest version of PUT Stop TDPs During the Upgrade Install the latest drivers for the Host Channel Adapter Run the first phase of the PUT Install/Upgrade Software Operation Stop the Teradata Database Run the second phase of the PUT Install/Upgrade Software Operation Verify the upgrade succeeded and the status of the system Immediately After the Upgrade Set MAXPERM for CRASHDUMPS database (major upgrades only) Perform any system-specific activities required by the upgrade Back up system disks Run SCANDISK and CheckTable again Resync MDS Restart Replication Services Enable Logons Enable TDPs Return the system to the users Run cleanup script Run an Asset Baseline Report 16 Upgrade Guide: Overview and Preparation

17 CHAPTER 3 System and Database Upgrade Preparation Obtaining a Change Control Number If you are a Business Critical or SWI entitled customer, your Teradata CSR will obtain a Change Control number to track the upgrade activities. If you are performing an unassisted upgrade, you can request a Change Control number by submitting an incident to Your Service. The Change Control number is associated with the upgrade plan and is required to download software patches from the Teradata Software Server (TSS). Preparing the Teradata System for an Upgrade In this phase you will ensure the Teradata system is ready for a Teradata Database upgrade. Upgrading the CMIC Contact Teradata to determine if your CMIC needs to be upgraded and, if needed, to schedule the upgrade. New software releases become available for the CMIC on a regular basis and the newest version must be installed before a Teradata Database upgrade. CMIC upgrades are performed by Teradata CSRs well before a scheduled Teradata Database upgrade. Implementing Backup and Restore Solution You must implement an Open Teradata Backup (OTB) solution so you can archive data prior to the upgrade. If you do not already have an OTB solution installed, contact your Teradata account representative to initiate installing this solution. Teradata recommends that OTB planning, delivery, and mentoring be implemented one to three months in advance of a planned Teradata Database upgrade. Refer to the Open Teradata Backup Release Definition for the network software that supports your Teradata Database release. The document can be downloaded from: Data Stream Architecture Teradata Data Stream Architecture (DSA) enables you to back up and restore your Teradata Database Release or later data using Teradata Viewpoint portlets and Symantec NetBackup, and is an alternative to the ARC-based BAR architecture. It can co-exist with BAR applications on the same BAR hardware. Refer to the Teradata Data Stream Architecture User Guide for more information. Upgrade Guide: Overview and Preparation 17

18 Chapter 3: System and Database Upgrade Preparation Preparing the Teradata System for an Upgrade Note: Legacy BAR software only restores from legacy BAR archives, and DSA only supports restores of DSA archives. Using Hardware Compression with Teradata DSA When using Data Stream Architecture to restore an archive made on a source system with hardware blocklevel compression, you must install the hardware compression driver package (teradata-expressdx) on the target system, even if it is not set up for hardware compression, so the target can read the compressed archive. The teradata-expressdx driver package is provided with systems that are equipped with compression hardware. Upgrading Teradata Tools and Utilities Review documentation for the latest Teradata Tools and Utilities and the Teradata Database Base System Release Definition to determine any upgrades required to support the target Teradata Database version. Teradata Tools and Utilities Packages on Teradata Nodes Automatically Upgraded During a Teradata Database Upgrade Certain Teradata Tools and Utilities packages allow communication between a Teradata client and the Teradata Database and are required on each node. These software packages are distributed on the Teradata Database CD-ROM or DVDs and are installed on the system nodes automatically as part of the Teradata Database upgrade. Patches for the Teradata Tools and Utilities packages are downloaded from the Teradata Software Server (TSS). Teradata Tools and Utilities Applications On Client Servers That Require Upgrading Before a Teradata Database Upgrade Database administration, Backup and Recovery and workload management utilities are very closely connected with the Teradata Database functionality and the latest releases of these products must be installed before upgrading to a new Teradata Database release. These can either be network attached or channel attached. Backup and Recovery - ARC Teradata Manager Teradata Administrator Wizards (such as for index and statistics) Visual Explain Teradata System Emulation Tool Teradata Dynamic Workload Manager Query Director Metadata Services Teradata Tools and Utilities Applications That Do Not Require Upgrading New releases of the Teradata Database will operate properly with earlier releases of the Teradata Tools and Utilities. However, new features of the Teradata Database release may not be usable with earlier Teradata Tools and Utilities releases. Often systems with many users require much effort to distribute updated Teradata Tools and Utilities applications to the users. These multi-user client applications are certified to work with new Teradata Database releases and can be upgraded in phases as time and resources permit: 18 Upgrade Guide: Overview and Preparation

19 Chapter 3: System and Database Upgrade Preparation Preparing the Teradata System for an Upgrade Application programming interfaces (CLI, ODBC, IDBC, OLEDB, PP2, Net Provider, and Teradata PT API) Support libraries (ICU and TeraGSS) End user utilities (SQL Assistant and BTEQ) Load/Unload utilities (FastLoad, FastExport, MultiLoad, TPUMP, Teradata Parallel Transporter, OLELOAD, and Access Modules) Developer Tools (IDE, such as Eclipse and Visual Studio) Upgrading Channel Drivers On Teradata systems that are channel-connected to a mainframe, new versions of the channel packages should be upgraded before upgrading the Teradata Database software. Consult the Teradata Database Base System Release Definition for the Teradata Database target release for specific requirements. The new package versions can be installed at the same time as the required Teradata Tools and Utilities packages. Note: For all upgrades, the channel package version must match the database version at the maintenance level. Channel and database software must be upgraded at the same time or PDE will not start up. Upgrading System Firmware and Drivers Arrange a time for the Teradata Customer Services to update firmware and drivers on your system to the latest Teradata certified releases. Although these upgrades are not required, Teradata strongly recommends that they be done prior to the Teradata Database upgrade. Firmware and driver updates are performed by Teradata CSRs. Reviewing Node Memory Size Each Teradata system node must have a minimum amount of random access memory (RAM). While the Teradata Database can run on a system with the minimum RAM, performance may be compromised. Determining the appropriate amount of RAM for your system requires that you factor in workload, performance requirements, and the cost of memory to make the optimum choice. Consult the Base System Release Definition for the specific Teradata Database release for the node memory requirements for your system. If you need to increase node memory, consult with your Teradata CSR to arrange for this activity. Installing or Upgrading to the Latest Version of TDput, PUTSRC, and PUTTools Preparing for an upgrade and the upgrade procedure itself both require that your system is running the latest version of TDput, PUTSRC, and PUTTools. Use the currently-installed version of TDput to upgrade to the most recent version. PUTSRC and PUTTools are then upgraded by the newly-installed version of TDput. Upgrade Guide: Overview and Preparation 19

20 Chapter 3: System and Database Upgrade Preparation Preparing the Teradata Database for an Upgrade PUT is used during the preparation phase of an upgrade to evaluate your system to ensure it is ready for an upgrade. During the actual upgrade procedure, PUT is used to automate many of the tasks required for the upgrade. If you do not have PUT installed, or if your system is running an older PUT version, you must install or upgrade to the latest PUT release. Determining System Readiness Your system hardware and software must be set up properly and running without problems before a Teradata Database upgrade begins. PUT includes the System Readiness Check utility that evaluates the system, searches for problems and creates a summary report. Preparing the Teradata Database for an Upgrade In this phase you will ensure the Teradata Database is ready for an upgrade. Determining Database Readiness The Pre-Upgrade Preparation Script evaluates the Teradata Database to find any problems that must be addressed before a major or a minor Teradata Database upgrade is performed. The script combines several inspections into a single script. The script also runs queries to generate data to input into the Upgrade Estimator Tool, which estimates the time required for the upgrade. The script inspects the following areas for problems and creates a summary report: Reserved Words conflicts DBQL Data Stored Procedures with no source In-Doubt Transactions (Replication systems only) MDS Rows Default Role assigned to user DBC Potential Unicode Conversion errors Examine the summary report and resolve any problems it finds. More information about how to resolve these problems is provided in the specific Teradata Database Upgrade Guide for your system, OS and Teradata Database target release. The summary report also provides data you will use when you run the Upgrade Estimator Tool. Make sure you save this information for later use. The SCANDISK Utility The SCANDISK command requests that the file system validate its internal structures and report any discrepancies it may find. During an upgrade procedure, SCANDISK is run several weeks prior to the upgrade during the preparation phase. You may optionally run the utility again a week or so before the upgrade, and immediately after the 20 Upgrade Guide: Overview and Preparation

21 upgrade. Running SCANDISK while users are logged on reduces the time the system is unavailable due to the upgrade. However, system performance may be degraded while this command is running. SCANDISK is part of the Teradata Database Ferret utility. Chapter 3: System and Database Upgrade Preparation Running the Upgrade Estimator The CheckTable Utility The CheckTable utility verifies the structure of the Teradata Database system tables and user tables. CheckTable provides four levels of internal data structure checking. Prior to starting an upgrade, run the CheckTable utility at level two for DBC, then run CheckTable again at level one for all user tables. Level two checking does the following: Determines whether row IDs on any given subtable are consistent with row IDs on other subtables by comparing lists of these IDs in those objects Compares the checksum of primary and fallback rows Verifies that hash codes reflect correct row distribution in each subtable Notice: On systems with a large number of objects, running the CheckTable utility may take a considerable length of time. If CheckTable reports any problems, they must be corrected before the Teradata Database upgrade is performed. Checking Cylinder Index Space Several features in Teradata Database releases change the file system structure and expand the Cylinder Indexes. When performing a major or a minor upgrade, you must determine whether or not there is enough space in the Cylinder Indexes to manage the upgrade. Running the Upgrade Estimator The Upgrade Estimator Tool is a spreadsheet calculator that helps you estimate the time needed to perform a major or a minor upgrade to the Teradata Database Release. Data generated by the Pre-Upgrade Preparation Script is used as input to the Upgrade Estimator Tool. System upgrade times are affected by these variables: Amount of system RAM Type of CPU Available contiguous unused space on the system disk Speed of disk array input/output The Upgrade Estimator Tool does not take these variables into consideration when estimating upgrade times. Therefore, the estimated time must be considered a very rough estimate. Upgrade Guide: Overview and Preparation 21

22 Chapter 3: System and Database Upgrade Preparation Preparing for the Upgrade Procedure Preparing for the Upgrade Procedure In this phase you will ensure you have everything you need to begin the upgrade procedure itself. Scheduling Downtime and Notifying Users You will need to coordinate with your system administrator to schedule downtime and notify users of the system's availability. Obtaining the Required Software Media If you are upgrading to a new major or minor Teradata Database release, your software will be located on the CD or DVD that you get with your purchase. It is required that the latest patches be downloaded from the Teradata Software Server (TSS). Maintenance and efix updates can be obtained from the Teradata Software Server. Rerunning SCANDISK and CheckTable If it has been a few weeks between the time you started getting the system ready for the upgrade and the actual start of the process, you may want to run SCANDISK and CheckTable just prior to beginning the upgrade to make sure nothing has changed on the system. Obtaining Tape Media for an Archive If you are going to be archiving data prior to the upgrade, make sure that you obtain enough tape media for your stored data. Tape media can be obtained from your local database or system administrator. Checking for Sufficient Node File System Space New Teradata Database software packages may require additional free space in the node file system. Before you begin the upgrade, check to ensure you have enough space in these file systems. The amount of file system space required varies by Teradata Database release. You can check the requirements for your Teradata Database target release by reviewing IDA00108C82, Minimum Starting Version and Free Space Requirements for Teradata Database Upgrades and Migrations. Customers can find this Knowledge Article by doing a general search for the reference number from Your Service ( tays.teradata.com). Rechecking for Latest Version of TDput, PUTSRC, and PUTTools PUT is constantly improving and new versions are available often. Make sure you have the latest version of TDput, PUTSRC, and PUTTools downloaded and installed before you begin a Teradata Database upgrade, even if you upgraded your version of PUT earlier in the upgrade preparation phase. 22 Upgrade Guide: Overview and Preparation