Netezza Software Upgrade

Netezza Software Upgrade Guide Document Number: 20668-16 Rev. 4Software Release: 5.0.xRevised: December 18, 2009

Netezza Corporation

Corporate Headquarters26 Forest St., Marlborough, Massachusetts 01752tel 508.382.8200 fax 508.382.8300 www.netezza.com

The specifications and information regarding the products described in this manual are subject to change without notice. All statements, information, and recommendations in this manual are believed to be accurate.

Netezza makes no representations or warranties of any kind, express or implied, including, without limitation, those of merchantability, fitness for a partic-ular purpose, and non infringement, regarding this manual or the products' use or performance. In no event will Netezza be liable for indirect, incidental, consequential, special, or economic damages (including lost business profits, business interruption, loss or damage of data, and the like) arising out of the use or inability to use this manual or the products, regardless of the form of action, whether in contract, tort (including negligence), breach of warranty, or otherwise, even if Netezza has been advised of the possibility of such damages.

Netezza, the Netezza logo, Netezza TwinFin, TwinFin, Snippet Blades, S-Blades, NPS, Snippet, Snippet Processing Unit, SPU, Snippet Processing Array, SPA, Performance Server, Netezza Performance Server, Asymmetric Massively Parallel Processing, AMPP, Intelligent Query Streaming and other marks are trademarks or registered trademarks of Netezza Corporation in the United States and/or other countries. All rights reserved.

Red Hat is a trademark or registered trademark of Red Hat, Inc. in the United States and/or other countries.

Linux is a trademark or registered trademark of Linus Torvalds in the United States and/or other countries.

D-CC, D-C++, Diab+, FastJ, pSOS+, SingleStep, Tornado, VxWorks, Wind River, and the Wind River logo are trademarks, registered trademarks, or service marks of Wind River Systems, Inc. Tornado patent pending.

APC and the APC logo are trademarks or registered trademarks of American Power Conversion Corporation.

All document files and software of the above named third-party suppliers are provided "as is" and may contain deficiencies. Netezza and its suppliers dis-claim all warranties of any kind, express or implied, including, without limitation, those of merchantability, fitness for a particular purpose, and non infringement.

In no event will Netezza or its suppliers be liable for indirect, incidental, consequential, special, or economic damages (including lost business profits, busi-ness interruption, loss or damage of data, and the like), or the use or inability to use the above-named third-party products, even if Netezza or its suppliers have been advised of the possibility of such damages.

All other trademarks mentioned in this document are the property of their respective owners.

Document Number: 20668-16

Software Release Number: 5.0.x

Netezza Software Upgrade Guide

Copyright © 2001-2009 Netezza Corporation.

All rights reserved.

PostgreSQL

Portions of this publication were derived from PostgreSQL documentation. For those portions of the documentation that were derived originally from Postgr-eSQL documentation, and only for those portions, the following applies:

PostgreSQL is copyright © 1996-2001 by the PostgreSQL global development group and is distributed under the terms of the license of the University of California below.

Postgres95 is copyright © 1994-5 by the Regents of the University of California.

Permission to use, copy, modify, and distribute this documentation for any purpose, without fee, and without a written agreement is hereby granted, pro-vided that the above copyright notice and this paragraph and the following two paragraphs appear in all copies.

In no event shall the University of California be liable to any party for direct, indirect, special, incidental, or consequential damages, including lost profits, arising out of the use of this documentation, even if the University of California has been advised of the possibility of such damage.

The University of California specifically disclaims any warranties, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. The documentation provided hereunder is on an "as-is" basis, and the University of California has no obligations to provide maintenance, support, updates, enhancements, or modifications.

ICU Library

The Netezza implementation of the ICU library is an adaptation of an open source library Copyright (c) 1995-2003 International Business Machines Corpo-ration and others.

ICU License - ICU 1.8.1 and laterCOPYRIGHT AND PERMISSION NOTICE

Copyright (c) 1995-2003 International Business Machines Corporation and othersAll rights reserved.

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, provided that the above copyright notice(s) and this permission notice appear in all cop-ies of the Software and that both the above copyright notice(s) and this permission notice appear in supporting documentation.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRAN-TIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OF THIRD PARTY RIGHTS. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR HOLDERS INCLUDED IN THIS NOTICE BE LIABLE FOR ANY CLAIM, OR ANY SPECIAL INDIRECT OR CONSEQUENTIAL DAM-AGES, OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.

Except as contained in this notice, the name of a copyright holder shall not be used in advertising or otherwise to promote the sale, use or other dealings in this Software without prior written authorization of the copyright holder.

ODBC Driver

The Netezza implementation of the ODBC driver is an adaptation of an open source driver, Copyright © 2000, 2001, Great Bridge LLC. The source code for this driver and the object code of any Netezza software that links with it are available upon request to [email protected]

Botan License

Copyright (C) 1999-2008 Jack Lloyd

2001 Peter J Jones2004-2007 Justin Karneges2005 Matthew Gregan2005-2006 Matt Johnston2006 Luca Piccarreta2007 Yves Jerschow2007-2008 FlexSecure GmbH2007-2008 Technische Universitat Darmstadt2007-2008 Falko Strenzke2007-2008 Martin Doering2007 Manuel Hartl2007 Christoph Ludwig2007 Patrick Sona

All rights reserved.

Redistribution and use in source and binary forms, for any use, with or without modification, of Botan (http://botan.randombit.net/license.html) is permitted provided that the following conditions are met:

1. Redistributions of source code must retain the above copyright notice, this list of conditions, and the following disclaimer.

2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions, and the following disclaimer in the documentation and/or other materials provided with the distribution.

THIS SOFTWARE IS PROVIDED BY THE AUTHOR(S) "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, ARE DISCLAIMED.

IN NO EVENT SHALL THE AUTHOR(S) OR CONTRIBUTOR(S) BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CON-SEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBIL-ITYOF SUCH DAMAGE.

Regulatory Notices

Install the NPS system in a restricted-access location. Ensure that only those trained to operate or service the equipment have physical access to it. Install each AC power outlet near the NPS rack that plugs into it, and keep it freely accessible.

Provide approved 30A circuit breakers on all power sources.

Product may be powered by redundant power sources. Disconnect ALL power sources before servicing.

High leakage current. Earth connection essential before connecting supply. Courant de fuite élevé. Raccordement à la terre indispensable avant le raccor-dement au réseau.

FCC - Industry Canada Statement

This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to part 15 of the FCC rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This equipment gen-erates, uses, and can radiate radio-frequency energy and, if not installed and used in accordance with the instruction manual, may cause harmful interference to radio communications. Operation of this equipment in a residential area is likely to cause harmful interference, in which case users will be required to correct the interference at their own expense.

This Class A digital apparatus meets all requirements of the Canadian Interference-Causing Equipment Regulations.

Cet appareil numérique de la classe A respecte toutes les exigences du Règlement sur le matériel brouilleur du Canada.

WEEE

Netezza Corporation is committed to meeting the requirements of the European Union (EU) Waste Electrical and Electronic Equipment (WEEE) Directive. This Directive requires producers of electrical and electronic equipment to finance the takeback, for reuse or recycling, of their products placed on the EU market after August 13, 2005.

CE Statement (Europe)

This product complies with the European Low Voltage Directive 73/23/EEC and EMC Directive 89/336/EEC as amended by European Directive 93/68/EEC.

Warning: This is a class A product. In a domestic environment this product may cause radio interference in which case the user may be required to take adequate measures.

VCCI Statement

この装置は、情報処埋装置等電波障害自主規制協議会　（VCCI）の基準に基づくクラス A 情報技術装置です。この装置を家庭環境で使用すると電波妨害を引き起越すことがあります。この場合には使用者が適切な対策を講ずるう要求されることがあります。

Contents

Preface

1 Overview of the Upgrade ProcessPrerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

About the Upgrade Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

Recommended Upgrade Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

Upgrade Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

Upgrade Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

Upgrade Verification Testing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4

Downgrade Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4

Netezza-Related Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4

Best Practices for a Successful Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5

Prepare Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5

Verify Netezza Operational Health . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5

Obtain the Latest Software Kit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5

Manage Upgrade Session Disconnects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5

Use a Two-Stage Upgrade Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6

Upgrade Clients to Match Netezza Software Release . . . . . . . . . . . . . . . . . . . . . . 1-6

2 Preparing for the Netezza UpgradeObtaining the Upgrade Kit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Downloading the Release Software Using FTP or Web Browsers . . . . . . . . . . . . . . 2-1

Using the Software CDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3

Unpacking the Upgrade Kit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4

unpack Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4

How to Run the unpack Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5

Running the Pre-Upgrade Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6

Resolving Pre-Upgrade Check Failures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7

Planning the Upgrade Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8

3 Upgrading the Netezza SoftwareRunning the nzupgrade Command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Interactive Upgrades . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2

Steps Following a Successful Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4

v

Steps Following a Failed Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4

Default Option Upgrades . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4

Custom Data and Capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4

Managing System Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5

Restoring Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5

Upgrade Cleanup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6

Enabling Optional Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6

Upgrading Client Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6

NzAdmin Client Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6

CLI Tools Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6

Web GUI Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7

SQL Clients. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7

About the Client Kits and CDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7

Obtaining the Latest Netezza Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7

4 Downgrading the Netezza SoftwarePreparing for Downgrades. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

Running the Pre-Downgrade Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

Resolve Pre-Downgrade Check Failures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2

Plan the Downgrade Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3

Downgrading a Netezza System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3

Interactive Downgrades . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3

Default Option Downgrades . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5

Restoring Custom Data and Capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5

Review Event Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5

Downgrade Cleanup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5

Downgrading Client Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5

Index

vi

Tables

Table 1-1: Upgrade Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Table 3-1: nzupgrade Input Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2

vii

viii

PrefaceThis guide describes how to upgrade your Netezza software from Release 5.0 or later to Release 5.0.x. The Netezza software resides on a Netezza host and controls the basic oper-ation of the system, such as the starting and stopping of services, system administration commands, the processing of Netezza SQL commands, and Netezza host operations.

You can also use the instructions in this guide to patch a Netezza release. A patch installa-tion process is typically much faster than an upgrade, as only the patch steps are required.

This guide does not describe the following procedures:

Installing the Netezza software for the first time on a host. Netezza systems are shipped with the Netezza software preinstalled.

Installing or configuring Netezza client applications, such as NzAdmin or Web Admin, or SQL clients such as the ODBC, JDBC, or OLE DB. The client applications are described in the Netezza System Administrator’s Guide, and the SQL clients in the Netezza ODBC, JDBC and OLE DB Installation and Configuration Guide.

About This Guide

The Netezza Software Upgrade Guide for Release 5.0.x is written for Netezza personnel and users who plan to upgrade or patch the Netezza software on a supported Netezza system.

The Purpose of This Guide

The Netezza Software Upgrade Guide for Release 5.0.x describes the upgrade prerequi-sites, the procedures to upgrade your Netezza system software, best practices, and troubleshooting information. This document includes the steps to upgrade your system either from the software CDs or from a downloaded copy of the upgrade kit.

Topics See

Reviewing system prerequisites, supported paths, and spe-cial information about the upgrade and downgrade processes

“Overview of the Upgrade Process” on page 1-1

Unpacking the upgrade software kit and running pre-upgrade verification checks to ensure that your system is ready for a software upgrade

“Preparing for the Netezza Upgrade” on page 2-1

Upgrading the Netezza software on your system and enabling the new release

“Upgrading the Netezza Software” on page 3-1

Downgrading your Netezza software to return to the previ-ously running release

“Downgrading the Netezza Software” on page 4-1

ix

Symbols and Conventions

This guide uses the following typographical conventions:

Italics for emphasis on terms and user-defined values such as user input

Upper case for SQL commands; for example INSERT, DELETE

Bold for command line input; for example, nzsystem stop

If You Need Help

If you are having trouble using the Netezza appliance, you should:

1. Retry the action, carefully following the instructions given for that task in the documentation.

2. Go to the Netezza Knowledge Base at https://knowledge.netezza.com. Enter your sup-port username and password. You can search the knowledge base or the latest updates to the product documentation. Click Netezza HelpDesk to submit a support request.

3. If you are unable to access the Netezza Knowledge Base, you can also contact Netezza Support at the following telephone numbers:

North American Toll-Free: +1.877.810.4441

United Kingdom Free-Phone: +0.800.032.8382

International Direct: +1.508.620.2281

Refer to your Netezza maintenance agreement for details about your support plan choices and coverage.

Netezza Welcomes Your Comments

Let us know what you like or dislike about our manuals. To help us with future versions of our manuals, we want to know about any corrections or clarifications that you would find useful.

Include the following information:

The name and version of the manual that you are using

Any comments that you have about the manual

Your name, address, and phone number

Send us an e-mail message using the following address: [email protected]

The doc alias is reserved exclusively for reporting errors and omissions in our documentation.

We appreciate your suggestions.

x

C H A P T E R 1
Overview of the Upgrade Process
What’s in this chapterPrerequisites

About the Upgrade Process

Netezza-Related Software

Best Practices for a Successful Upgrade

This chapter provides an overview of the process to upgrade the Netezza software. It includes important steps that you should follow to prepare for an upgrade. These steps include reviewing the supported upgrade paths, obtaining the release software, and check-ing the Netezza system for any problems that might prevent an upgrade.

This document uses the term Release 5.0.x to represent Release 5.0 or any service pack of that release.

Prerequisites

Table 1-1 lists the software, hardware, and other prerequisites that your existing Netezza system must meet before you can upgrade it to Release 5.0.x. The upgrade process checks your Netezza system to verify that it meets the hardware and software prerequisites before upgrading the system.

Table 1-1: Upgrade Prerequisites

Prerequisite Description How to Manually Check

Supported Upgrade Paths

You can upgrade to Release 5.0.x from Release 5.0 including patch levels. To upgrade to or install Release 5.0.6 or later, the Netezza system must have HPF v4.4 or later installed.

Note: You cannot upgrade from any prior release such as 4.0.x or 4.5.x to 5.0.x.

You may downgrade from Release 5.0.x to the 5.0.x release from which you upgraded. See Chapter 4, “Downgrading the Netezza Software.”

Use the nzrev command, or run the nzupgrade check command.

1-1

Netezza Software Upgrade Guide for Release 5.0.x


The Netezza software upgrade process automatically performs prerequisite checks of the Netezza system and manages the software updates as well as backups and restores of cus-tomizations to system configuration files. The process also eases downgrades for those situations where you decide to revert to your previously running release. The upgrade pro-cess also includes a pre-upgrade verification step to report any issues that need to be addressed for best results.

Recommended Upgrade Process Follow this overall process to upgrade a Netezza system. The following chapters provide more details about these steps.

1. Obtain the software release package.

2. Unpack the upgrade software and files to a directory on your system. (This step only places the new kit files on your system; it does not affect the current Netezza release.)

3. Run a verification check to ensure that your system is ready for the upgrade and that the software will install properly. Resolve any reported problems to help ensure a problem-free upgrade.

4. Work with Netezza support to plan the time required for the actual upgrade, then schedule the maintenance window for the upgrade.

5. Upgrade the system at the scheduled maintenance window.

6. Ensure that custom settings and configuration changes are restored to your system.

Supported Hardware

This release requires the Netezza TwinFin system hard-ware. Release 5.0.x is NOT supported on z-series or earlier models such as the 5200-, 8000-, or 10000-series systems.

Run the nzupgrade check command.

Supported Host OS

Red Hat Enterprise Linux 5.3 Run the nzupgrade check command.

User Account Information Required

Make sure that you have the following account information:

• Root or equivalent superuser account password to the Netezza system

• The Netezza nz account password

• The Netezza admin account password

Verify that you can log in to the Netezza system as the nz user as well as root or a user account that has superuser or sudo privileges. Make sure that you can log in to nzsql using the admin account and password. If the upgrade commands cannot find the admin password in your nz account envi-ronment, you will be prompted for the password.

Table 1-1: Upgrade Prerequisites (continued)

Prerequisite Description How to Manually Check

1-2 20668-16 Rev.4


7. Test the operation of the new release by verifying that your usual queries and tasks con-tinue to work as expected. If there are multiple Netezza users at your site, select a few users to upgrade their clients and test the new release.

8. Enable and/or start to use the new features of the release, and continue to verify the operation of the system. (The Netezza Release Notes outlines the new features and changes in this release. Chapter 3 describes the optional features for the release, if any, and how to enable them.)

9. After the release passes your verification testing, roll out the new release to the Netezza users. Direct users to update their Netezza client applications.

Upgrade LogsThe upgrade process provides user messaging in the screen display and also captures extensive message logging to document the steps and actions taken during all phases of the upgrade. The log files are typically used by Support to diagnose problems that occurred during a failed upgrade; the information is very technical in nature. The log files reside in the /nz/var/log directory and are named upgrade.target-rel.date. The upgrade command dis-plays the name of the uncompressed log file at the beginning of the command session. An example follows:

Logfile: /nz/var/log/upgrade.5.0.20090108

If you run the upgrade command several times in the same day, the log is appended with the incremental number n for each additional time the command runs. If an upgrade fail-ure should occur, the log file provides valuable information that can help Support to identify the source of the problem.

After the upgrade completes, the cleanup operations compress the log file and save it as upgrade.target-ver.date.n.gz in the same directory. The upgrade command displays the name of the compressed log file. An example follows:

Logfile: /nz/var/log/upgrade.5.0.20090108.gz

If the upgrade does not complete successfully, it displays a message similar to the follow-ing with one or more reasons for the failure:

ERROR: NPS software initial install was NOT successful!Please contact Netezza Customer Support for assistance.

Make sure that you review the command output messages for more information on the errors. The messages provide details about the issues that have blocked the upgrade. In some cases, the errors may be conditions or prerequisites that are blocking the upgrade or downgrade. Other reasons could include a configuration problem that you may need to resolve. If you have any questions about the errors, contact Support for assistance; they will often request the upgrade log files for further investigation.

Upgrade BackupsThe upgrade process creates extensive backups of key Netezza host data and configuration files. It saves a copy of the /nz/data directory and the system configuration files in the /nz/var/backups directory. After the upgrade completes successfully, it compresses the backups directory into a file named upgrade.target-rel.date.tar.gz.

The upgrade backups are typically used by Support to troubleshoot an unsuccessful upgrade, and in very rare cases, to recover files that may not have been replaced following the upgrade failure.

20668-16 Rev.4 1-3


Upgrade Verification Testing As a best practice, you should plan a testing period to evaluate the Netezza operations after the upgrade to the new release. During the tests, run typical queries to make sure that they behave as expected and that the system is operating normally. If you have multiple Netezza users at your site, you may want to select one or two target users to upgrade their Netezza client applications and test the new release.

After your testing confirms that your queries and processes are operating normally, begin to use the new features and likewise test the results with select users. Make sure that your queries and analysis continue to work as expected.

After you verify that the Netezza system is operating normally and queries behave as expected, notify the other Netezza users of the new release. They should update their cli-ents and test their typical queries and operations.

Downgrade SupportThe upgrade process also provides features that can help to ease the process of downgrad-ing to the previous version of the Netezza software. Downgrades are not common, but they can be helpful if a new software release introduces a change which has an unexpected effect on your existing operations or queries. In those cases, downgrades can help to restore the previous release before users are impacted.

The downgrade process follows the same overall process of an upgrade:

1. Run the pre-downgrade check to ensure that your system is ready for the downgrade.

2. Resolve any required changes to help ensure a problem-free downgrade. You may need to work with Netezza Support to resolve some of the recommended actions.

3. Downgrade the system.

4. Ensure that custom settings and configuration changes are restored to your system.

5. Test and verify the operation of the previous release; ensure that your usual queries and operations continue to work without problem.

Always work with Netezza Support or your Sales representative to troubleshoot any upgrade problems. Never downgrade a Netezza system on your own. Netezza can help you to address common issues as well as to determine whether a downgrade is necessary. Chapter 4, “Downgrading the Netezza Software,” provides more detail about this process.

Netezza-Related Software

You use the software upgrade process described in this guide to upgrade the Netezza soft-ware to Release 5.0.x. The Netezza system has many software components such as flash, host firmware, a Linux host operating system, and host drivers. These additional applica-tions are not upgraded during the Netezza software upgrade process; instead, you upgrade these applications if needed using separate installation programs.

The Netezza software upgrade requires Netezza operational downtime because the Netezza software must be stopped during the upgrade, but it usually does not require a reboot of the system. If you want to or need to upgrade your Linux host Red Hat kernel version, con-tact Netezza Support for assistance and information.

1-4 20668-16 Rev.4



The following sections describe some common best practices that help to make the upgrade process run more smoothly.

Prepare BackupsBefore you upgrade, make sure that you have a recent, full database backup. This provides some safety and recovery for situations such as power outages, failures, or other events that might occur during the upgrade process. For a complete description of how to create a backup, refer to the Netezza System Administrator’s Guide.

Verify Netezza Operational HealthIt is important to verify that the Netezza system is error-free and operating normally before you upgrade. The upgrade process includes a pre-check that verifies the Netezza system status and prerequisites before you actually start the upgrade. You should run the check several days before the planned upgrade to identify and resolve any reported problems. The upgrade step automatically runs the check as well to confirm that the system is still ready and that no errors have occurred in the meantime.

Obtain the Latest Software KitAlthough you can use the CDs sent to you to upgrade your system, there may be a more recent installation package available. Periodically, Netezza creates patch kits for supported Netezza releases. The patch kits contain updates for the Netezza software such as resolu-tions to reported issues as well as improvements for the release.

Before you upgrade to Release 5.0.x, check the Netezza FTP site (ntzftp.netezza.com) or the Netezza Knowledge Base at https://knowledge.netezza.com.

On the FTP site, navigate to the Releases/5.0.x directory for the upgrade target release. There may be one or more patchx subdirectories. As a best practice, use the pack-age.tar.z file in the latest 5.0.x patch directory as the upgrade software kit. If a release does not have any patches, use the package.tar.z file in the target release 5.0.x directory.

On the Knowledge Base, click Downloads and select the 5.0.x release target in the drop-down list. The Downloads page shows the latest available kits, upgrade instruc-tions (this guide), readme files, and information for the release. Select a kit to download it.

Follow the instructions in this guide to upgrade or patch to the new release using pack-age.tar.z. There is also a Documentation area on the Netezza FTP site and the Knowledge Base with the latest documentation for supported releases. As a best practice, look for updates to this and the other user guides for your release.

Manage Upgrade Session DisconnectsIf you upgrade the Netezza appliance using a remote login session, you should run the nzupgrade command under the screen program to avoid idle-session time-outs and lost connections.

20668-16 Rev.4 1-5


To upgrade a Netezza system under the screen program, log in to the Netezza appliance as root and enter a command similar to the following:

# screen /nz/kit.5.0/sbin/nzupgrade upgrade

If the session is lost, the nzupgrade process continues to run. Log back in to the Netezza system as root and run the following command to attach to your session:

# screen -r

Note: The screen program is not available on prior releases of Netezza software. If your sys-tem does not have the screen command, contact Support for assistance.

If you do not use the screen program, and your remote session to the Netezza system is lost or disconnected, the upgrade continues to run in the background. You can reconnect to the Netezza system and take either of the following actions:

Use the ps command to find the nzupgrade process and stop it with the command: kill -INT pid

Wait for the nzupgrade process to complete. Use the tail -f command or similar to watch the log file at /nz/var/log/upgrade.version.YYYYMMDD.# and review the upgrade progress.

As a best practice, run nzupgrade within the screen program.

Use a Two-Stage Upgrade ProcessAs a best practice, customers or Netezza personnel who upgrade a Netezza to a new release should plan to perform the upgrade in two stages. During the first stage, upgrade the Netezza software and evaluate the new release by running common queries and typical user operations. During this initial testing phase, if any issues or unexpected changes occur and a downgrade is recommended by Support, you can use the standard downgrade process as documented later in this guide.

After that initial test period completes successfully, start to use the new features and repeat the evaluation testing. New features can sometimes change the data format, which may not be supported by prior Netezza releases. If a downgrade should be recommended after this time, the standard downgrade procedure will detect the new data format and could stop with a message directing the user to contact Netezza Support or to perform steps prior to the downgrade. Support may be required to use downgrade procedures to address the format changes so that the standard downgrade procedure can then be used.

Upgrade Clients to Match Netezza Software Release Following the upgrade, you should install the latest NzAdmin and/or Web GUI tools to ensure that your management interfaces match the release to which you just upgraded the system. The NzAdmin tool will notify users when their version of the software is not com-patible with the Netezza host software.

You should also alert your SQL client users, such as the ODBC, JDBC, or OLE DB users, or the UNIX or Windows SQL clients, to upgrade their clients to match the latest release. This ensures that your users see the latest features, and it helps to avoid any compatibility prob-lems between the clients and the Netezza software.

1-6 20668-16 Rev.4

C H A P T E R 2
Preparing for the Netezza Upgrade
What’s in this chapterObtaining the Upgrade Kit

Unpacking the Upgrade Kit

Running the Pre-Upgrade Check

Resolving Pre-Upgrade Check Failures

Planning the Upgrade Schedule

This chapter describes how to prepare for the Netezza software upgrade by obtaining the software upgrade kit, unpacking the software, and running a pre-check to identify any issues to resolve before the upgrade can occur.

Obtaining the Upgrade Kit

The Netezza software upgrade kit is delivered on CD-ROMs in the software package kit. It is also available electronically from the Netezza FTP site as well as the Netezza Knowledge Base. To use the CDs to upgrade, you must have physical access to the Netezza system hardware and the CD drives on the Netezza host.

If you do not have physical access to the Netezza system because it is located in a remote facility or within a secured data center, consider using the downloaded software method. You can download the software using FTP or use a Web browser. You require a Netezza Sup-port account and password.

The upgrade files and packages typically include the updates for the Netezza host software, ODBC/JDBC drivers, Netezza client kits, documentation, and the Support toolkit. Contact your Netezza Sales representative or Support for more information about your Support user account.

If the Netezza system cannot access the Internet or use FTP, you can also download the software to another system which has FTP or WGET access. You can then copy the software kits to drives or locations that are accessible to the Netezza system.

Downloading the Release Software Using FTP or Web Browsers If you plan to download the upgrade software from the Netezza FTP support site, you can either use an FTP command line utility or use a Web browser to navigate to the Support servers to download the files to the Netezza system or any system in your network.

2-1


Accessing the Netezza FTP SiteTo access the Netezza FTP site, you can use any of the following methods:

From a command line prompt, enter the following command:

ftp ntzftp.netezza.com

From a Web browser, enter one of the following URLs:

http://ntzftp.netezza.com

https://ntzftp.netezza.com

You must supply your Netezza FTP user account and password to access the server, where you will begin in your home directory location.

To access the software kits, navigate to the Releases/version directory, where version is the Netezza software version that you want to download. For example, to navigate to the Netezza Release 5.0 software location, navigate to Releases/5.0. As a best practice, check for a patch subdirectory to see if there is a more recent package.tar.z file for the release; if there is, use the package.tar.z file in the latest patch directory for your upgrade.

Accessing the Netezza Knowledge BaseTo access the Netezza Knowledge Base, use a Web browser to connect to https://knowl-edge.netezza.com. You must supply your Netezza Support user account and password to access the server.

To access the software kits, click Downloads. Select the software release to which you are planning to upgrade, and the page updates to display links to the latest software, client, and other kits. Click the software kits that you require to download them to your system.

Overview of the Software KitsThe software version directory contains files such as the following:

*cli.package.tar — Netezza client installation packages for the supported client operat-ing systems

datadirect.package.tar.z — DataDirect Driver Manager for ODBC support

doc.package.tar.z — Netezza documentation for the release

hpfconfig.package.tar.z — Netezza Host Platform Configuration files

nzjdbcsetup.exe — JDBC driver for Netezza clients

nzodbcsetup.exe — ODBC driver for Netezza clients

nzoledbsetup.exe and nzoledbsetup64.exe — OLE DB provider for Netezza clients (32- and 64-bit installers, respectively)

nzsetup.exe — NzAdmin client installation kit

package.tar.z — Netezza software installation files (required for the upgrade)

webadmin.package.tar.z — Web Admin client installation kit

Not all of these files may be present in the directory; typically, the release directory includes only the packages that were updated for the release. In addition to these pack-ages, there are packages for host platform configurations (hpfconfigver.package.tar.z), host management software (ibmhostmgmt.package.tar.z), firmware and diagnostics tools

2-2 20668-16 Rev.4

Obtaining the Upgrade Kit

(fdtver.package.tar.z), and the Red Hat operating system. These additional packages are not often used during routine Netezza upgrades, but are available for full system installa-tions or re-installations.

To perform a Netezza software upgrade, you must download the package.tar.z file. The package.tar.z file provides the Netezza installation program and pre-upgrade check, which informs you if your system needs other updates before you can proceed with the Netezza upgrade. Save the file on the Netezza system in a location such as /tmp/release or in loca-tion that is accessible from the Netezza system. Use the following command to uncompress the package.tar.z file:

tar -xzvpf package.tar.z

After the Netezza software upgrade, you may need to download other client kits such as NzAdmin, Web Admin, ODBC, JDBC, OLE DB, or Netezza client CLIs for your Netezza cli-ent users to update to the latest software release. The downloads will vary depending upon the clients that you use, but you should ensure that you and your Netezza users upgrade to the latest clients for best performance.

Using the Software CDsIf you plan to upgrade using CDs, make sure that you have at least the Netezza Server Soft-ware CD before you begin. The following table lists the Release 5.0.x CDs.

Netezza Software CDs

The Netezza Server Software CD contains the Netezza software installation files.

The Netezza Solaris and AIX Clients CD contains the Netezza client software such as the CLI and the ODBC/JDBC drivers for Solaris/AIX clients.

The Netezza Linux and HP Clients CD contains the interface software such as the CLI and the ODBC/JDBC drivers for Linux/HP clients.

The Netezza Windows Client CD contains the Netezza client software such as the NzAd-min interface, the Netezza CLI, the ODBC/JDBC drivers, and the OLE DB connector. This CD also includes the Web Admin UI installation program.

The Netezza DataDirect Driver Manager CD contains the Netezza-licensed version of the ODBC driver from DataDirect Technologies.

The Netezza Documentation CD contains the Netezza documentation set.

The Host Platform Configuration CD (formerly the Netezza Software Support CD) con-tains various programs, tools, and files for upgrading the Netezza Linux system files.

The Netezza Firmware/Diagnostics/Tools DVD contains firmware and flash for various devices and components of the Netezza appliance as well as diagnostics and Support tools.

The IBM Host Firmware CD contains firmware for the IBM host server included in your appliance.

The IBM Host Management CD contains host-related software.

20668-16 Rev.4 2-3


Mounting CDs If you use CDs to upgrade your system, you use the mount command to make the system aware of a CD and you use the umount command to “disconnect” or unmount that CD prior to ejecting it from the disk drive.

To mount a CD on your Netezza system:

1. Log on as root or become root using the su - command.

2. Place the appropriate CD in the CD tray.

3. Mount the CD using the following command:

mount /media/cdrom

For systems with a DVD/CD-RW drive: mount /media/cdrecorder

4. To change to the mount point, use the cd command and specify the mount pathname that you used in step 3. This guide uses the term /mountPoint to refer to the applicable CD mount point location on your system, as used in step 3.

Unmounting and Ejecting CDsTo unmount and eject the CD that is currently mounted in the CD drive:

1. Log on as root or become root using the su - command.

2. Change to any directory other than the CD mount point. If you are still “in” the CD mount point, the next command will often fail with a “device busy” error.

3. Unmount the CD using one of the following commands:

For systems with a CD-ROM drive: umount /media/cdrom

For systems with a DVD/CD-RW drive: umount /media/cdrecorder

4. Open the CD tray so that you can remove the CD using the following command:

eject


The upgrade kit contains the following two files:

A software package file, typically named npsos.release.tar.gz, which contains all the Netezza software upgrade files in compressed format

The unpack script, which places the new software on the system but does not affect the Netezza running version

unpack ScriptYou use the unpack script to extract the contents of the software package file into a new, empty directory on the Netezza system. The unpack script does not modify or replace any existing Netezza software files, nor does it change the running version of the software. Make sure that you change to the directory where the command resides to run the command.

The script has the following syntax:

./unpack [-f] [unpack_directory]

2-4 20668-16 Rev.4


The -f argument specifies that the command should unpack the upgrade software to the default directory, which is /nz. You can specify a different location using the unpack_directory argument.

The script creates a new directory with the following name in the specified location:

kit.release

The release value is a string with two or three digits separated by periods. It represents the major, minor, and service pack (if applicable) release numbers, such as 5.0 or 5.0.2.

Note: If the kit.release directory already exists, the new directory will be named kit.release.build, where build represents a unique build number for the software package. If the build number does not make the directory unique, the unpack script adds unique integers such as .1, .2, and so on, until the new unpack location is unique.

The unpack script performs some checks to confirm that the upgrade package can be used on the current Netezza system. For example, it confirms that there is sufficient disk space in the specified unpack location and that the current host operating system and Netezza release support upgrades to the kit that you are installing.

How to Run the unpack ScriptTo run the unpack script:

1. Log in to the Netezza system as the nz user account. You do not have to log in as root or a superuser account, although those accounts will work as well.

2. If you are installing from CD, mount the Netezza Server Software CD.

3. Change to the location where the upgrade kit resides using one of the following commands:

If you downloaded the software, change to the directory where the unpack com-mand is located.

If you are using CDs: cd /mountPoint

4. Run the unpack program using the following command:

./unpack

5. If you did not specify a directory using the install-dir command line argument, the script prompts you to specify a location for the upgrade files. The default is /nz.

The command creates the destination directory type.release in the specified location, and unpacks the software files in that directory. The script displays information about the installation and includes a progress bar. Sample command output follows:

$ ./unpack

----------------------------------------------------------------------Netezza Performance Server -- NPS Operating System 5.0 Copyright 2002-2009 Netezza Corporation. All rights reserved.----------------------------------------------------------------------

Validating package checksum ... ok

Where should the NPS Operating System be unpacked? [/nz]

0% 25% 50% 75% 100%|||||||||||||||||||||||||||||||||||||||||||||||||||

20668-16 Rev.4 2-5


You can check the system to prepare for an upgrade with:/nz/kit.5.0/sbin/nzupgrade check

You can start the upgrade (which also checks the system) with (as root):

/nz/kit.5.0/sbin/nzupgrade upgrade

Unpacking complete.

If you are installing from CDs, you can eject the Netezza Server Software CD as it is no longer needed.

As a next step, run the nzupgrade check command to check the system before you upgrade. The verification check looks for any issues that might prevent an upgrade or that should be resolved before upgrading. You could also run the nzupgrade upgrade command to start the upgrade, which also performs the verification checks and if no problems are found, pro-ceeds with the upgrade.

Running the Pre-Upgrade Check

The pre-upgrade check verifies the operational health and status of the current Netezza system. It confirms the hardware and software status of the system, operational states, and other prerequisites for a successful upgrade. It displays messages about any problems that should or must be resolved before you upgrade. The command does not impact the running Netezza system.

You should run the check at least several days before you start the actual upgrade. You can run the pre-upgrade check at any time, and you can run it as needed to confirm any changes that have been made to address reported issues for the Netezza system. The upgrade step also runs the pre-upgrade check automatically to confirm that no problems have occurred on the system since the previous check.

To run the pre-upgrade check:

1. Log in to the Netezza system with a root or superuser account. Note that you can also use nz or any valid account, or use sudo to run the command with superuser privileges. If you use an account with superuser privileges, the command also checks the host operating system to identify any potential problems.

2. Change to the directory where the software upgrade package kit was installed, such as /nz/kit.5.0.

3. Change to the sbin directory using the following command:

cd sbin

4. Run the following command:

./nzupgrade check

The command output varies depending upon the problems that the command finds. The following is sample command output for a pre-upgrade check that found no issues:

----------------------------------------------------------------------Netezza Performance Server Operating SystemCopyright 2007-2009 Netezza Corporation. All rights reserved.----------------------------------------------------------------------

2-6 20668-16 Rev.4


Logfile: /nz/kit.5.0/var/log/upgrade.5.0.20090417

Checking the system for validity...

System checks succeeded.


/nz/kit.5.0/sbin/nzupgrade upgrade

Logfile: /nz/kit.5.0/var/log/upgrade.5.0.20090417.gz

The following is sample command output where the pre-upgrade check detected active data slice regenerations which could impact the upgrade. The upgrade process instructs you to retry the upgrade after the regeneration finishes.


Logfile: /nz/var/log/upgrade.5.0.B1.20091221.2


ERROR: Regen in progress!Regen 1002 to 1003: 4277.0 of 31128.1 MB (13.74%) restoredRegen 1004 to 1003: 4276.0 of 31119.1 MB (13.74%) restored

Please wait for regen to complete before upgrading.System check failed.Logfile: /nz/var/log/upgrade.5.0.B1.20091221.2.gz


If your pre-upgrade check finds problems on the Netezza system, refer to the command output for more information about the required or recommended changes that are needed before you can upgrade the Netezza software. If the pre-upgrade check finds a problem, consider using the nzupgrade -v check command to obtain more verbose output during the check. The output messages will describe the problems or issues, and may offer guidance for the recommended changes.

The problems reported by the pre-upgrade verification typically fall into these categories:

The current system hardware, OS, or Netezza revision does not meet the supported upgrade prerequisites for the release. For example, if you attempt to upgrade a system that does not have the correct revision of a hardware component, the upgrade process displays an error similar to the following and exits:

ERROR: NPS version 5.0 is not supported on this hardware. Please contact Netezza Customer Support for assistance.

If you are upgrading to Release 5.0.6 or later, the upgrade will fail if the installed HPF release is less than v4.4. You must upgrade the HPF software following the instructions in the HPF Release Notes included in the HPF v4.4 software package or CD before you can upgrade the Netezza software.

20668-16 Rev.4 2-7


As another example, if some of the SPUs on the system are older versions that do not support Release 5.0.x, the upgrade exits with an error similar to the following:

ERROR: Some SPUs in this system are not supported by NPS version 5.0. Please contact Netezza Customer Support for assistance.

Unsupported SPUs (by hardware ID):1001, 1003, 1005

For these problems, contact Netezza Support to determine the possible steps to resolve the issues.

An existing process such as a data slice regeneration is in progress. If the upgrade detects that one or more regenerations are active (as in the example in the section “Running the Pre-Upgrade Check” on page 2-6), an error message stops the upgrade and instructs you to wait until the process finishes.

There is a hardware, configuration, or other system problem that must be resolved. For common problems, the upgrade verification typically provides more information about commands or steps to resolve the issues. Contact Netezza Support for assistance with resolving issues that are blocking the upgrade.

An external table or a view uses a datatype that has been deprecated for use in user objects, such as TEXT or OIDVECTOR. For external tables, the pre-upgrade check dis-plays errors and will block the upgrade so that you can recreate those external tables and cast any deprecated types to supported datatypes. For views, the pre-upgrade check displays warnings, which do not block the upgrade. Following the upgrade, test any queries which use those views to ensure that they are operating as expected, and if necessary, recreate the views and cast deprecated types to supported datatypes.

The database contains identifiers which do not confirm to the “legal” and supported characters for an identifier. Although the commands and Netezza user interfaces do not allow users to create invalid identifiers, it is possible that they could have been loaded into the database or created by string functions such as trim() or others. Review the reported identifier problems and change the names of the identifiers to proceed with the upgrade.

Planning the Upgrade Schedule

A Netezza software upgrade typically requires a few hours of Netezza system downtime to convert the system over to the new release, and to ensure that custom settings are restored. The actual software upgrade is just one of several steps, and each step can vary depending upon your environment, the amount of data in your system, the current version of your soft-ware, and other factors.

You should work with your Netezza Support or Sales representative to plan the expected downtime based on the size and current release of your Netezza system, as well as any pre-upgrade verification changes. With a better estimate of the time, you can schedule the upgrade and alert your users to the maintenance window when the system will be unavailable.

2-8 20668-16 Rev.4

C H A P T E R 3
Upgrading the Netezza Software
What’s in this chapterRunning the nzupgrade Command

Custom Data and Capabilities

Upgrade Cleanup

Enabling Optional Features

Upgrading Client Software

Obtaining the Latest Netezza Documentation

This chapter describes how to upgrade the Netezza software. The chapter also provides best practices for installing the latest Netezza documentation as well as upgrading client users and applications.

Running the nzupgrade Command

You use the nzupgrade command to upgrade the Netezza software. The command first runs the pre-upgrade verification check (as described in “Running the Pre-Upgrade Check” on page 2-6) to confirm that there are no blocking problems on the system. If the upgrade check passes, it starts the upgrade process. If the upgrade check fails, the command dis-plays messages about the problems and then exits without upgrading the system.

The nzupgrade command requires the Netezza system to be in a running state. If the Netezza system is in the stopped state, the upgrade command reports an error and exits. If the nzupgrade command encounters any problems during the upgrade, it exits and backs out any changes that it made up until the problem. It restores the system to its previous release, but it does not automatically restart the system. You can restart the Netezza sys-tem using the /nz/kit/bin/nzstart command.

You can run the nzupgrade command in interactive mode or using a “silent” mode in which the upgrade process uses default responses to any prompts and proceeds without user interaction.

Note: You also use the nzupgrade command to downgrade the Netezza software release. For the downgrade case, note that the -K argument becomes a required argument. For more information about downgrade operations, see Chapter 4, “Downgrading the Netezza Software.”

The nzupgrade command has the following syntax:

nzupgrade [-f] [-v] [-D data] [-K kit] [-O old-kit] {check | upgrade}

3-1


The following table describes the command inputs.

Interactive UpgradesTo upgrade the Netezza software using the interactive process:

1. Log in to the Netezza system as the root user or a user that has sudo or other supe-ruser privileges.

Note: Make sure that you log in to the active host where the nps resource group is run-ning. To identify the active host, you can use the crm_resource command as follows:

crm_resource -r nps -Wcrm_resource[5377]: 2009/01/31_10:13:12 info: Invoked: crm_resource -r nps –W resource nps is running on: npsrack1

If you run the nzupgrade command from the standby host, the upgrade checks will fail and the command exists with a message to run the command from the active host.

Table 3-1: nzupgrade Input Options

Input Description

-f Forces the upgrade to continue without prompting for input. The upgrade process uses all the default values for any prompts. If the nzupgrade com-mand has a required argument which does not have a default, the command exits and you must use the interactive mode.

-v Specifies verbose output, which displays a subset of the information that normally would appear only in the log file. The -v option displays a user-friendly version of additional detail from the log file. The complete informa-tion is always written to the upgrade log file.

-D data Specifies the location of the Netezza data directory to use. The upgrade process checks the value of the NZ_DATA_DIR environment variable; other-wise, it attempts to determine the data directory relative to the location of the Netezza kit.

-K kit Specifies the location of the unpacked software kit files. The default is the location where the nzupgrade command resides.Note that for downgrades, you can specify the -K argument to point to the pathname of the kit directory to which you want to downgrade, or you can run the nzupgrade command from that downgrade kit directory. For more information, see Chapter 4, “Downgrading the Netezza Software.”

-O old_kit Specifies the location of the existing Netezza kit directory. The default is the directory referenced by the kit symbolic link.

check Checks the currently active system to verify that the upgrade will succeed, but does not perform the upgrade. No changes are made to the system. For more information, see “Running the Pre-Upgrade Check” on page 2-6.

upgrade Upgrades the Netezza software to a new release. This option requires supe-ruser permissions. It runs the check option by default and proceeds to the upgrade if the checks pass.

3-2 20668-16 Rev.4

Running the nzupgrade Command

2. Change to the directory where the software kit is installed with a command similar to the following:

cd /nz/kit.5.0

The software kit location is listed at the end of the unpack script output, as shown in the example on page “How to Run the unpack Script” on page 2-5.


cd sbin


./nzupgrade upgrade

Note: If you are remotely connected to the Netezza system, consider using the screen command (screen ./nzupgrade upgrade). For more information, see “Manage Upgrade Session Disconnects” on page 1-5.

The command starts the upgrade process. It stops the Netezza system and uses the kit files in the /nz/kit.5.0.x area to upgrade the Netezza host software. The command also updates the catalog whenever the new release introduces a catalog change.

Sample command output follows:


Logfile: /nz/var/log/upgrade.5.0.20090417.1



Performing upgrade of NPS from version 5.0 to version 5.0.2 Would you like to continue? (y/n) [y]

Stopping NPS...System state change complete.

Dumping the system catalog ...Loading the system catalog ...System catalog upgrade complete.

NPS software upgrade succeeded.

You can start your system with:nzstart

Please remember to upgrade all NPS client software.

Compressing backup data...Backups: /nz/var/backups/upgrade.5.0.20090417.tar.gzLogfile: /nz/var/log/upgrade.5.0.20090417.1.gz

This example shows that the upgrade has completed successfully, as indicated by the mes-sage “NPS software upgrade succeeded.” Proceed to the section “Steps Following a Successful Upgrade” on page 3-4.

20668-16 Rev.4 3-3


If the upgrade fails, it displays the message “ERROR: NPS software initial install was NOT successful!” It is important that you investigate and resolve the reasons for a failed upgrade before you restart the Netezza software. Proceed to the section “Steps Following a Failed Upgrade” on page 3-4.

Steps Following a Successful UpgradeAfter the upgrade completes successfully, log in as nz and change to the /nz/kit/bin direc-tory to start the Netezza software. You first use the nzstart command to start the system, as in the following example:

/nz/kit/bin/nzstart

After the system starts, run the following command to create the latest system views for the release:

nzsql -u admin system -f /nz/kit/bin/adm/tools/create_system_views.sql

Note: You must specify the admin account password for this command to complete. If you do not know the admin account password, you can skip this step, but alert the Netezza database administrator to run the command later. Until this command is run, the Netezza system will work properly, but you will not be able to use the system views that it creates.

Steps Following a Failed UpgradeIf the upgrade does not complete successfully, it displays a message similar to the follow-ing with one or more reasons for the failure:

ERROR: NPS software initial install was NOT successful!Please contact Netezza Customer Support for assistance.

Make sure that you review the command output messages for more information on the errors. The messages provide details about the issues that have blocked the upgrade. In some cases, the errors may be conditions or prerequisites that are blocking the upgrade or downgrade. Other reasons could include a configuration problem that you may need to resolve. If you have any questions about the errors, contact Support for assistance.

Default Option UpgradesIf you use the nzupgrade -f option, the upgrade uses the same steps as described in the section “Interactive Upgrades” on page 3-2. However, the upgrade process will not prompt you for any responses; instead, it uses the default response for any questions. In the unlikely event that an upgrade prompt has no default answer, the process exits and reports an error.


The upgrade process will examine your system configuration files for changes and restore any custom settings automatically. If the upgrade process is unable to restore certain set-tings, it displays a message to alert you to possible restorations that you will need to make manually.

3-4 20668-16 Rev.4


Managing System Configuration FilesThe upgrade process takes special steps to protect changes made to system configuration files on the Netezza system. These files include files such as callHome.txt, sendMail.cfg, network.cfg, and others used by the operating system.

The upgrade process compares the current files with the new system configuration files and performs these steps:

If an old file is the same as the new version of the file, the upgrade process installs the new version.

If the old file has been changed/customized in any way, and the new version has not introduced any new changes for the Netezza release, the upgrade process leaves the old version in place.

If the old file has been customized, and the new version has changes related to the new Netezza release, the upgrade process displays warning messages similar to the following:

WARNING: File /nz/kit.5.0/sys/startup.cfg may have conflicting changes.

The previous version is saved as /nz/var/tmp/nz/kit.5.0.B2/sys/startup.cfg.5.0Please re-apply any necessary local configuration.

WARNING: File /etc/sysctl.conf has conflicting changes.The previous version is saved as /nz/var/tmp/etc/

sysctl.conf.prevPlease re-apply any necessary local configuration.

The upgrade process creates a backup copy of the old file named filename.release, and then installs the new version of the file. The backup copy is saved under the /nz/var/tmp directory. After the upgrade, you can compare the filename.release file to the new file, and if necessary, edit the new file to apply any customizations that you require for your environment.

Note: In the sample output, there are two types of messages: the startup.cfg file may have conflicting changes, but the sysctl.conf file has conflicting changes. The may have messages usually can be safely ignored. The has conflicting changes messages are more important; for these files, check the backup file and the newly installed file to look for the differences. Edit the newly installed file to restore any changes which are needed for your Netezza system.

Restoring EventsDuring the upgrade to Release 5.0.x, the upgrade process reviews your Netezza nzevents and migrates all the rules to the new event format. If you have customized events, this will preserve your customizations and restore them automatically.

20668-16 Rev.4 3-5


Upgrade Cleanup

After a successful software upgrade, the upgrade process performs the following cleanup tasks:

Creates a compressed file of the backups created in the /nz/var/backups directory as well as the upgrade log saved in the /nz/var/log directory. The backups directory con-tains copies of the previous release’s /nz/kit/data directory, including any core files, plus the log files and various system configuration files.

Deletes the plan files in the previous release’s directory.

Enabling Optional Features

At this time, there are no optional features to enable for the Netezza 5.0.x software.

Upgrading Client Software

After you upgrade to a new release or service pack of a release, you should upgrade your Netezza client software to use the same software release. The client software consists of the following applications:

NzAdmin

CLI tools

Web Admin (the Web GUI)

SQL clients such as ODBC, JDBC, OLE DB, and others.

You can obtain the Netezza client applications on the Netezza Client Software CDs.

NzAdmin Client UpdatesNzAdmin is a Windows application that allows users to access and manage the Netezza sys-tem. After you upgrade to a new Netezza software release or service pack and complete a preliminary system test of the new release, alert your NzAdmin users to install the latest NzAdmin software on any Windows client systems that will be used to access the upgraded system. If an NzAdmin application is at an earlier revision than the Netezza software on the server, users will receive an error message that the versions are not compatible. To update the NzAdmin software, install the latest NzAdmin client kit. For a description of how to install the NzAdmin client, refer to the Netezza System Administrator’s Guide.

CLI Tools UpdatesThe CLI tools allow you to install a set of common nz* management commands on a UNIX client system. These commands include nzrev, nzstate, nzreclaim and others that are help-ful for Netezza users to have at a remote UNIX client workstation to obtain information about current system status or version, or to start some administration tasks such as load-ing data or reclaiming space. After you upgrade to a new Netezza software release or service pack and complete a preliminary system test of the new release, alert your CLI cli-ent users to install the CLI package to ensure that they have the latest version of the

3-6 20668-16 Rev.4


commands for managing the Netezza system. To update the CLI tools, install the latest cli-ent kit. For a description of how to install the CLI, refer to the Netezza System Administrator’s Guide.

Web GUI UpdatesThe Web GUI is an application that you can install on the Netezza host or on any Linux sys-tem that has network access to the Netezza. It provides a Web-based interface to the Netezza system and supports many of the same tools and displays that are offered through the NzAdmin interface. After you upgrade to a new Netezza software release, it is recom-mended that you update your Web GUI; if you install a service pack to an existing release, you typically do not have to update the Web GUI. For a description of how to install the Web GUI, refer to the Netezza System Administrator’s Guide.

SQL Clients The SQL clients allow users to access the Netezza system as a data source. Netezza sup-ports connectivity from clients that use applications such as ODBC, JDBC, and OLE DB to access the Netezza database. Before you upgrade to a new Netezza software release, it is recommended that you review the supported SQL client revisions described in the Netezza Release Notes to ensure that the clients and revisions used at your site will work with the Netezza release. After you upgrade the Netezza software, your client users may need to upgrade the drivers to the latest versions for best access performance. For a description of how to install the ODBC and JDBC drivers, refer to the Netezza ODBC, JDBC and OLE DB Installation and Configuration Guide.

About the Client Kits and CDsThere are client CDs for Windows and for UNIX platforms. If there are many client users at your site, you may want to place the client application files in a network location, and then inform your users where they can find the installers online.

The Windows client CD contains three installation packages: the NzAdmin kit, Web GUI kit (which can be installed only on Linux systems), and the ODBC and JDBC drivers.

For UNIX clients, there are two CDs: one for Linux/HP and one for Solaris/AIX. Each CD contains the platform-specific executables for the Netezza CLI tools.


The Netezza documentation is provided on a separate documentation CD with the Netezza software. The documentation is also available on the Netezza FTP site and the Netezza Knowledge Base in each release directory as one package (doc.package.tar.z). The docu-mentation is also available as separate PDF files in the FTP Documentation area and on the Knowledge Base Documentation page.

Note: As Netezza updates a document for changes, revisions, or corrections, the updated version is posted immediately to the Documentation area of the FTP site and Knowledge Base. As a best practice, check for updated PDFs there before you use the documentation CD or doc.package.tar.z.

You can install the contents of the documentation package to a network location or the Netezza system if you have multiple users at your site who require access to the user guides.

20668-16 Rev.4 3-7


If you would like to have the latest documentation included on the Netezza system, do the following:

1. Log on to the Netezza system as nz.

2. Change to the following location:

cd /nz/kit.5.0.x

3. Create a doc subdirectory:

mkdir doc

4. Change to the doc directory:

cd doc

5. If you are installing from CD, do the following:

a. Mount the Netezza Documentation CD.

b. Copy the user guide files using the following commands:

cp /mountPoint/*.pdf . cp -r /mountPoint/index* .

6. If you are installing from downloaded software, do the following:

a. Copy the documentation package from the downloaded software area to the doc directory. For example, if the downloaded software is in /tmp/5.0.x:

cp /tmp/5.0.x/doc.package.tar.z .

b. Run the following command:

tar -xzvpf doc.package.tar.z

c. Optionally, delete the doc package file to free the disk space:

rm doc.package.tar.z

3-8 20668-16 Rev.4

C H A P T E R 4
Downgrading the Netezza Software
What’s in this chapterPreparing for Downgrades

Running the Pre-Downgrade Check

Downgrading a Netezza System

Restoring Custom Data and Capabilities

Downgrade Cleanup

Downgrading Client Software

This chapter describes how to downgrade a Netezza system from a running 5.0.x release to a previous 5.0.x version.

Never downgrade the Netezza system unless you encounter issues or changes in behavior that affect your queries or system operation. Be sure to work with Netezza Support to trou-bleshoot any issues, as there may be simple steps to resolve them. If Netezza Support determines that the best course of action is to return to the previous release, Support will work with you to make that transition.

Preparing for Downgrades

The downgrade process re-activates a previous Netezza software release on a Netezza sys-tem. The downgrade process is identical in behavior to the upgrade process; you use the nzupgrade command to reactivate a Netezza kit in a specific directory. The following sec-tions describe the process in more detail.

Before you downgrade, make sure that your Netezza system meets the downgrade prerequi-sites. Use the pre-downgrade verification process to check the system and identify and required changes that may be necessary to perform the downgrade. The downgrade process will not run if there are required changes found by the verification check.

Running the Pre-Downgrade Check

The pre-downgrade verification check is the same process as an upgrade verification check. It uses the nzupgrade check command, but also includes the -K argument to identify the Netezza release kit directory to which you want to downgrade. The command verifies the operational health and status of the current Netezza system. It confirms the hardware and software status of the system, existing configuration settings, and other prerequisites for a

4-1


successful downgrade. It displays messages about any problems which should or must be resolved before you can downgrade. The command does not impact the running Netezza system.

To run the pre-downgrade check:

1. Log in to the Netezza system with a root or superuser account. Note that you can also use the nz account, or use sudo to run the command with superuser privileges. If you use an account with superuser privileges, the command also checks the host operating system to identify any potential problems.

2. Change to the kit directory of the current running release, which is usually the /nz/kit symbolic link:

cd /nz/kit/sbin

Note: You can also change to the kit directory of the target release to which you are downgrading (/nz/kit.target/sbin) and run the nzupgrade command from that directory. If you use this process, omit the -K option in the next step, as the downgrade will auto-matically use the target release as the destination.

3. Run the following command, where -K specifies the pathname of the kit to which you want to downgrade.

./nzupgrade -K /nz/kit.5.0 check

The command checks the system and displays the following output. The messages in the output can vary depending upon the release to which you are planning to downgrade, as well as any problems that the command finds. The following is sample command output for a pre-downgrade check that found no issues:


Logfile: /nz/var/log/upgrade.5.0.20090417




./nzupgrade -K /nz/kit.5.0 upgrade

Logfile: /nz/var/log/upgrade.5.0.20090417.gz

Some of the reported problems may be warnings; these warnings indicate that a downgrade would proceed, but you should be prepared for certain changes. Errors typically indicate situations that will prevent the downgrade from running until they are resolved.

Resolve Pre-Downgrade Check FailuresIf your pre-downgrade check reports any warnings or errors, refer to the command output for more information about the mandatory or recommended changes that are needed before you can downgrade. Also consider re-running the nzupgrade check command with the -v option to obtain more verbose output during the check. The output messages will describe the problems or issues, and may offer guidance for the recommended changes.

4-2 20668-16 Rev.4


Some common problems reported by the pre-downgrade verification include a hardware, system configuration setting, or a system problem that must be resolved. For common prob-lems, the downgrade verification may provide more information about commands or steps to resolve the issues. For more complex issues, contact Support for assistance with the downgrade.

Plan the Downgrade ScheduleLike Netezza upgrades, downgrades often require a few hours of Netezza system downtime to convert the system back to the previous release, and to ensure that custom settings and configurations are restored. The software downgrade is just one of several steps, and each step can vary depending upon your environment, the amount of data in your system, the current version of your software, and other factors.

You can help to reduce the Netezza system downtime and impact to your users by working with your Netezza Sales and Support representatives to plan the time needed for your envi-ronment. With a better estimate of the time, you can schedule the downgrade and alert your users to the maintenance window when the system will be unavailable.


You use the nzupgrade command to downgrade the Netezza software. The command first runs the pre-downgrade verification check to confirm that there are no blocking problems on the system, then it starts the downgrade process. If upgrade command finds any issues that would impact the downgrade, the command displays messages about the problems and then exits without downgrading the software.

You can run the nzupgrade command in interactive mode or using a “silent” mode in which the process uses default responses to any prompts and proceeds without user interaction required. For a complete description of the command arguments, see “Running the nzup-grade Command” on page 3-1.

Interactive DowngradesTo downgrade the Netezza software using the interactive process:

1. Log in to the Netezza system as the root user or a user that has sudo or other supe-ruser privileges.

Note: Make sure that you log in to the active host where the nps resource group is run-ning. To identify the active host, you can use the crm_resource command as follows:

crm_resource -r nps -Wcrm_resource[5377]: 2009/01/31_10:13:12 info: Invoked: crm_resource -r nps –W resource nps is running on: npsrack1

If you run the nzupgrade command from the standby host, the upgrade checks will fail and the command exists with a message to run the command from the active host.

2. Change to the directory that holds the Netezza software kit to which you want to down-grade with a command similar to the following:

cd /nz/kit.target_release


cd sbin

20668-16 Rev.4 4-3



./nzupgrade upgrade

The command starts the process to downgrade the Netezza software to the specified kit. It first checks to make sure that there are no blocking issues for the downgrade. If the checks pass, it prompts you to continue:

Would you like to continue? (y/n) [y]

Press Enter to continue, or press n and Enter to exit the command and stop the pro-cess.

If you choose to continue, the downgrade process stops the Netezza system and redi-rects the system to use the kit files in the downgrade target location. If you are down-grading to a different major release, the command also updates the catalog.

Sample command output follows:

----------------------------------------------------------------------Netezza Performance Server Operating SystemCopyright 2007-2009 Netezza Corporation. All rights reserved.----------------------------------------------------------------------Logfile: /nz/var/log/upgrade.5.0.20090418

Checking the system for validity...System checks succeeded.Performing downgrade of NPS from version 5.0.2 to version 5.0Would you like to continue? (y/n) [y]Bringing NPS offline...System state change complete.Stopping NPS...System state change complete.Dumping the system catalog ...

Loading the system catalog ...

System catalog upgrade complete.

NPS software upgrade succeeded.

You can start your system with:

nzstart

Please remember to upgrade all NPS client software.

Compressing backup data...Backups: /nz/var/backups/upgrade.5.0.20090418.tar.gzLogfile: /nz/var/log/upgrade.5.0.20090418.gz

Following the successful downgrade, make sure that you log in as nz and change to the /nz/kit/bin directory to start the Netezza software using the nzstart command.

If the downgrade failed, make sure that you review the command output messages for more information on the errors. In some cases, the errors may be conditions or prerequisites that are blocking the downgrade. Other reasons could include a configuration problem that you may need to resolve. If you have any questions about the errors, contact Support for assistance.

4-4 20668-16 Rev.4


Default Option DowngradesIf you include the -f option to the nzupgrade command, it uses the same steps as described in the previous section, “Interactive Downgrades” on page 4-3. However, the process will not prompt you for any responses; instead, it uses the default response for any questions. In the unlikely event that a prompt has no default answer, the process exits with an error.


The downgrade process examines your system configuration files for changes and restores any custom settings automatically. If the upgrade is unable to restore certain settings, it displays a message to alert you to possible restorations that you should perform.

Review Event DefinitionsThe restoration process ensures that all the latest event definitions are restored to the ear-lier Netezza release, but it results in duplication of events; the older events could be identical to the new events, or they may have different thresholds or values if you custom-ized the events in the 5.0.x system.

After you downgrade, make sure that you review the events and remove any duplicates or incorrect event definitions using the nzevent delete command.

Downgrade Cleanup

After a successful software downgrade, the downgrade process performs the same cleanup tasks as performed for an upgrade. For a description, see “Upgrade Cleanup” on page 3-6.

Downgrading Client Software

After you downgrade to the previous release or service pack of a release, you should like-wise update your Netezza client software to use the same software release. The client software consists of the following applications:

NzAdmin: If a user’s NzAdmin application is at a later revision than the Netezza soft-ware on the server, the user will receive an error message that the versions are not compatible. To update the NzAdmin software, users must install the correct NzAdmin client kit. For a description of how to install the NzAdmin client, refer to the Netezza System Administrator’s Guide.

CLI tools: After you downgrade to a previous Netezza software release or service pack, alert your CLI client users to install the CLI package for that same release to ensure that they use matching release versions for the commands. To update the CLI tools, you simply install the correct client kit over the current version. For a description of how to install the CLI, refer to the Netezza System Administrator’s Guide.

Web Admin (the Web GUI): After you downgrade to a previous Netezza software release, you should install the Web GUI for the earlier release; if you downgrade from a later service pack to an earlier version of the same base release, you typically do not have to update the Web GUI. For a description of how to install the Web GUI, refer to the Netezza System Administrator’s Guide.

20668-16 Rev.4 4-5


SQL clients such as ODBC, JDBC, OLE DB, and others: Make sure that the clients sup-port the Netezza release to which you downgraded. For a description of how to install the ODBC and JDBC drivers, refer to the Netezza ODBC, JDBC and OLE DB Installation and Configuration Guide.

You can obtain the Netezza client applications on the Netezza Client Software CDs.

4-6 20668-16 Rev.4

Index

Index

Bbackup

files 1-3Netezza system, prior to upgrade 1-5

CCDs

mounting 2-4Netezza software 2-3unmounting 2-4

cleanupdowngrades 4-5upgrades 3-6

CLI tools, updating 3-6client applications

downgrade 4-5updating after Netezza upgrade 1-6upgrading 3-6

client CDs 3-7create_system_views.sql script 3-4customized files

restoring after downgrades 4-5restoring after upgrades 3-4

Ddatatypes, deprecated 2-8documentation

FTP site 3-7installing 3-7latest updates 3-7

downgradeabout 1-4cautions 4-1client applications 4-5failures, resolving 4-4Netezza software 4-1pre-downgrade check 4-1preparing for 4-1resolving pre-downgrade check problems 4-2restoring customizations 4-5running 4-3schedule 4-3silent option 4-5

downtime, planning 2-8

FFTP

account, Netezza 2-1latest documentation updates 3-7software directory, contents of 2-2using to retrieve upgrade software 2-1

KKnowledge Base, accessing 1-5

Llogs, upgrade 1-3

NNetezza

documentation, installing 3-7FTP account 2-1FTP site

about 1-5accessing 2-2

Knowledge Baseabout 1-5accessing 2-2

software, CDs 2-3NzAdmin client, updating 3-6nzstart command, running after upgrade 3-4nzupgrade command 3-1

OODBC clients, updating 3-7

Ppackage.tar.z, obtaining latest 1-5patch kits, looking for 1-5pre-downgrade check

about 4-1failures, resolving 4-2

prerequisites, upgrade 1-1pre-upgrade check

about 2-6resolving problems 2-7

Rrelease software, downloading 2-1remote login session, managing disconnects 1-5remote session upgrade, recovering following disconnect

1-6

Sscreen command 1-5software release directory, contents of 2-2software, downloading upgrade kits 2-1SQL clients, updating 3-7system health, verifying 1-5

Index-1

Index

Ttwo-stage upgrade process 1-6

UUNIX client CDs 3-7unpack script

about 2-4running 2-5

upgradebackups 1-3best practices 1-5cleanup 3-6client applications 1-6default options 3-4failures, how to resolve 1-3host OS support 1-2kit, obtaining 2-1locating latest package.tar.z file 1-5logs 1-3Netezza releases 1-1Netezza-related software 1-4nzupgrade command 3-1prerequisites 1-1pre-upgrade check 2-6process, about 1-2restoring options 3-4running 3-2schedule 2-8silent mode 3-1supported hardware 1-2two-stage best practice 1-6user accounts required 1-2verification process 1-4workflow 1-2

upgrade kitobtaining 2-1unpacking 2-4

upgrade session time-outs, avoiding 1-5

WWeb browser, using to retrieve upgrade software 2-2Web GUI client, updating 3-7WGET, using to retrieve upgrade software 2-1Windows client CD 3-7

Index-2

Documents

Netezza Software Upgrade