4.6.5 Netezza Getting Started Tips

Netezza Performance Server Getting Started Tips Document Number: D20293-11 Rev. 1Software Release: 4.6Revised: February 25, 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 noninfringement, 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.

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.

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

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]

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 noninfringement.

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: 20293-11

Software Release Number: 4.6 and Later

Netezza Performance Server Getting Started Tips

Copyright © 2004-2009 Netezza Corporation.

All rights reserved.

Regulatory Notices

Install the NPS Series 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.

You must provide all disconnect devices and over-current protection devices.

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

FCC 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.

CSA Statement

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

Cet appareil numérique de la classe A est conforme à la norme NMB-003 du Canada.

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.

Contents

1 About the Netezza Performance ServerNPS Hardware. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

NPS Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Snippet Processing Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

Snippet Processing Arrays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

Storage Arrays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

NPS Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

NPS Software CDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

Installing Administration and Client Software . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

Linux Host Operating System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4

Powering Down the NPS System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4

Powering Down 10000-Series NPS Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5

Powering Down 5200-Series Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9

Powering Up the NPS System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10

Powering Up a 10000-Series NPS System . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11

Powering Up 5200-Series Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14

Netezza SPU LED Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-15

Getting Started with Commands and Queries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-16

Default Users and Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-16

Netezza Common Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-17

Basic Netezza CLI Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-21

Basic Netezza SQL Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-24

Choosing a Backup and Restore Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-27

Getting Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-28

PDF Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-28

Online Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-29

Netezza Support Contact Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-31

iii

iv

List of Tables

Table 1-1: NPS Release Software CDs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

Table 1-2: Rev 7 SPU LED Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-16

Table 1-3: Default Users and Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-16

Table 1-4: Netezza Common Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-17

Table 1-5: CLI Command Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-21

Table 1-6: Commonly Used Command Options. . . . . . . . . . . . . . . . . . . . . . . . 1-22

Table 1-7: Commonly Used nzload Command Options . . . . . . . . . . . . . . . . . . 1-22

Table 1-8: Log files for nzload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-23

Table 1-9: Netezza SQL Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-24

Table 1-10: SQL Tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-25

Table 1-11: Commonly Used Internal Slash Options . . . . . . . . . . . . . . . . . . . . . 1-25

Table 1-12: Commonly Used nzsql Command Options . . . . . . . . . . . . . . . . . . . 1-26

Table 1-13: Choosing a Backup and Restore Method . . . . . . . . . . . . . . . . . . . . 1-27

Table 1-14: Key User Manuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-28

v

vi

C H A P T E R 1
About the Netezza Performance Server
What’s in this chapterNPS Hardware

NPS Software

Linux Host Operating System Requirements

Powering Down the NPS System

Powering Up the NPS System

Getting Started with Commands and Queries

Getting Help

This document provides a brief introduction to some background information and getting started tips for the Netezza Performance Server (NPS). If you are a new user of the NPS data warehouse appliance, or you are moving from an older NPS system to the latest release, review this content to familiarize yourself with the basics.

NPS Hardware

A Netezza system consists of multiple hardware and software components working together to provide performance and reliability. The NPS models include configurations with one standalone rack (a standard configuration), or two or more hardware racks clustered in a high-availability (HA) configuration. Within each rack are numerous components that work together to provide the asymmetric massively parallel processing of the NPS architecture. The key hardware components within an NPS include the following:

NPS Host

Snippet Processing Units

Snippet Processing Arrays

Storage Arrays

NPS HostThe NPS host, located within the NPS rack, controls and coordinates the activity of the NPS. It performs query optimization; controls table and database operations; consolidates and returns query results; and monitors the NPS system components to detect and report problems.

1-1


The host is a highly redundant, highly available, server with dual power supplies, error-cor-recting memory, a disk channel controller, and redundant disks (RAID 5). Each NPS rack has a keyboard, video, mouse (KVM) unit to give administrators direct access to the host operating system and commands. In most cases, administrators use remote connect appli-cations to log in to the host over their secure network and run commands.

Snippet Processing UnitsThe Snippet Processing Unit (SPU) is the basic unit of processing and storage in the NPS. Each SPU is essentially a standalone microcomputer, with a CPU, logic processors, mem-ory, and disk storage. The SPU is an intelligent disk storage device, as it has logic to quickly search for the correct information and to return only the matching results of the portions of the data that are saved on its disk.

An NPS system has many SPUs: for example, there are up to 56 in the NPS model 10050 and up to 896 in the NPS model 10800. In optimal configurations, users distribute their database tables across all of the SPUs to leverage the performance of parallel query processing.

Each SPU is responsible for managing a portion of your database and tables (called a pri-mary partition), as well as for maintaining a copy of another SPU’s primary partition (called a mirror partition). If a SPU should fail, the mirror partition is used to create a new primary partition on a standby SPU within the system, which will then take the place of the failed SPU.

Snippet Processing Arrays Snippet Processing Arrays (SPAs) are racks within the NPS system that contain up to 14 SPUs and have the power supplies, fans, and communication fabric that allows the SPUs to communicate with each other and with the NPS host.

NPS systems contain at least two SPAs. If you add SPAs to the system to increase the num-ber of SPUs, the SPAs are added in pairs. For each pair of SPAs, one of the 28 SPUs takes the role of a hot standby, ready to take the place of a failed SPU within the system.

Storage ArraysThe NPS host system may also include optional internal storage arrays, which you can use for such tasks as backups, load staging, or other user disk space. New 10000-series NPS HA systems contain the Storage Pad array, which offers 5TB of user disk space for each system. The Storage Pad XL option provides 10TB per rack (or 5TB for a half-rack configu-ration such as the 10050). The NPS model 5200 does not have a Storage Pad option.

NPS Software

The NPS appliance leverages a variety of software applications to perform its day-to-day system tasks as well as to allow users to run administration and data analysis tasks. For example, the NPS host uses the Red Hat Enterprise Linux (RHEL) operating system (described in more detail in “Linux Host Operating System Requirements” on page 1-4), and it also has software to manage the NPS hardware devices and components, such as firmware, flash, and other applications. These applications are preinstalled when you pur-chase an NPS system; when the system is installed onsite, Netezza engineers will help you to finalize the configuration and system settings to connect the system into your data cen-ter environment.

1-2 D20293-11 Rev.1

NPS Software

Periodically, Netezza issues patches to correct reported problems as well as to improve sys-tem performance. Netezza also issues new major and minor software releases to add new features and capabilities. When software updates and new releases are available, Netezza Support will work with you to plan upgrade paths as well as to install the patches and upgrades to your system.

NPS Software CDsThe NPS software release kits include several CD-ROMs of the software and documentation for your NPS system. Table 1-1 lists the software CDs that are typically shipped with an NPS software release. These software images are also available as downloadable files from the Netezza FTP site, ntzftp.netezza.com.

Note: To access the FTP site, you must have a logon account and password. If you do not have an account or cannot remember the password, contact Netezza Support for assistance as described in “Netezza Support Contact Information” on page 1-31.

The NPS software kits also include the Red Hat Enterprise Linux software, which is used on the NPS host. The kits could include several CDs for RHEL 4.0 or a DVD for RHEL 5.2.

Installing Administration and Client SoftwareThe NzAdmin tool and Web Admin application are administrative tools that you can use to manage the NPS system from remote workstations. You can install the NzAdmin software on one or more supported Windows client systems to perform administrative tasks and

Table 1-1: NPS Release Software CDs

Description

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

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

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

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

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

The NPS Documentation CD contains the Netezza documentation set.

The NPS Flash Updater for Z Series CD contains tools to update flash on all SPUs.

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

The NPS Host Health Drivers CD contains updated health drivers for HP host servers.

The NPS Host Firmware CD contains updated firmware for the host server.

D20293-11 Rev.1 1-3


obtain status for the system. Netezza also provides a Web Admin application that you can install on the NPS host. The Web Admin application allows administrators to access the NPS system using a Web browser to perform various management tasks. To use NzAdmin or the Web Admin applications, you must install the software located on one of the CDs labeled “NPS Client CD” (for either UNIX or Windows clients). Refer to the client installa-tion instructions in the NPS System Administrator’s Guide for details.

For business intelligence and data integration applications, the Netezza ODBC and/or JDBC driver, or OLE-DB provider, must be installed on the client systems to communicate with the NPS. For a description of the ODBC, JDBC, and OLE DB support and how to install and configure them, refer to the NPS ODBC, JDBC and OLE DB Installation and Configuration Guide.

Linux Host Operating System Requirements

The NPS host server runs the Linux operating system. New NPS 10000-series SL/XL and later systems have the Red Hat Enterprise Linux (RHEL) version 5.2 software. In previous NPS releases, NPS hosts used RHEL version 4.0 or Red Hat Linux Advanced Server (LAS) 2.1 operating systems. The operating system is preinstalled on the NPS host.

Never patch or otherwise alter the Linux kernel or other Linux binaries on your system unless Netezza directs you to do so. Netezza does not support custom modifications of the kernel.

Netezza provides kernel updates when security updates, patches, or other service packs become available for the operating system. Upgrade kits are also available to upgrade the Linux operating systems. Netezza Support will work with you to upgrade and maintain your NPS host operating systems.

Netezza supports client connections from a variety of operating systems such as: HP-UX (11i); Red Hat Linux 7.3, RHEL version 2.1, 3.0, and 4.0; Windows 2000, 2003, XP, and Vista; AIX 5.1, 5.2, 5.3; and Solaris versions 2.7, 2.8, 2.9, or 2.10.


This section describes the steps to completely power down an NPS system. Typically, you only power down an NPS system to perform tasks such as moving the system, or if the data center or office location is undergoing maintenance that requires systems to be powered off.

When you perform host firmware updates, you may need to power-cycle the hosts and stor-age arrays, but you do not need to completely power-cycle the racks. For a complete description of how to perform host firmware updates, refer to the NPS Software Upgrade Guide.

Note: To completely power down an NPS system, you must have physical access to the NPS to press power switches.

1-4 D20293-11 Rev.1


Powering Down 10000-Series NPS SystemsThe procedures for powering down a 10000-series system vary depending upon the type of NPS model that you have. These procedures and models include the following:

Standard NPS systems

Standard NPS systems with the optional Storage Pad array

HA NPS systems that use the Red Hat Cluster Manager solution

HA NPS systems that use the Linux-HA and DRBD solution and have one or more Stor-age Pad arrays

The following sections describe the power-down procedures for each of these NPS types. You must have the root password (or superuser or sudo privileges) to power down the NPS system.

Powering Down a Standard NPS SystemTo power down a standard NPS system:

1. Shut down the NPS system:

a. Log on as nz to the NPS system.

b. Enter the following command:

nzstate

c. If the system state is Stopped, continue with step 2.

d. If the system state is Online, enter the following command:

nzstop

2. Log out of nz and log on as root using the following command:

su -

3. Shut down the Linux operating system using the following command:

shutdown -h now

The system displays a series of messages as it stops processes and other system activ-ity. When it finishes, it displays the message “power down” which indicates that it is now safe to turn off the power to the system.

4. Press the power button on the NPS host (located in the front of the NPS cabinet) to power down the host system.

5. Switch off the power to the two PDU units (located in the rear of the NPS cabinet at the bottom) to completely power down the NPS rack. Make sure that you switch off power to both power switches.

D20293-11 Rev.1 1-5


Powering Down a Standard NPS System with a Storage Pad Array To power down a standard NPS system that also has the optional Storage Pad array, such as a 10050XL or a 10100XL system:




nzstate



nzstop

2. Log out of nz and log on as root using the following command:

su -


shutdown -h now



5. In the back of the NPS rack, locate the Storage Pad array component and do the following:

a. Press and hold the power button for storage processor A (SP A) for a few seconds until the power shuts off. (See Figure 1-1 for the location of the SP A and B power switches.)

b. Press and hold the power button for storage processor B(SP B) for a few seconds until the power shuts off.

Figure 1-1: Storage Pad SP Power Switches

c. Press the standby power supply (SPS) toggle switch on its left side (the O side) to turn the SPS off (see Figure 1-2).

SP A Power SwitchSP B Power Switch

1-6 D20293-11 Rev.1


Figure 1-2: Storage Pad Standby Power Supply (SPS) Switch

6. Switch off the power to the two PDU units (located in the rear of the NPS cabinet at the bottom) to completely power down the NPS rack. Make sure that you switch off power to both power switches.

Powering Down an HA NPS System (Red Hat Cluster Manager) To power down a high-availability (HA) NPS system that uses the Red Hat Cluster Manager cluster solution:

1. Log on as root to host 1 using the following command:

su -

2. Enter the following three commands to stop the NPS services:

/sbin/cluadmin -- service disable NPS

service cluster stop

ssh ha2 'service cluster stop'

3. Log in to host 2 as root, then shut down the Linux operating system using the following command:

shutdown -h now


4. Press the power button on host 2 (located in the front of the NPS cabinet) to power down that host.


shutdown -h now


6. Press the power button on host 1 (located in the front of the NPS cabinet) to power down the host.

7. Press the power button on the MSA500G2 (located on the bottom right corner of MSA500G2) to power down the device.

8. Switch off the power to the two PDU units (located in the rear of the NPS cabinet at the bottom) to completely power down the NPS rack. Make sure that you switch off power to both power switches, and repeat this step on each rack of your HA system.

SPS Switch

D20293-11 Rev.1 1-7


Powering Down an HA NPS System with One or More Storage Pad Arrays To power down a high-availability (HA) NPS system which has one or more Storage Pad arrays:

1. Log on as root to host 1 using the following command:

su -

2. Enter the following commands to stop the clustering processes:

/usr/sbin/crm_resource -r nps -p target_role -v stopped

service heartbeat stop

ssh ha2 'service heartbeat stop'


shutdown -h now


4. Press the power button on host 2 (located in the front of the NPS cabinet) to power down that NPS host.


shutdown -h now


6. Press the power button on host 1 (located in the front of the NPS cabinet) to power down the NPS host.

7. In the back of each NPS rack that has a Storage Pad array (usually host 1 for an SL-series system or in each rack for an XL-series system), locate the Storage Pad array component and do the following steps:

a. Press and hold the power button for storage processor A (SP A) for a few seconds until the power shuts off. (See Figure 1-1 on page 1-6 for the location of the SP A and B power switches.)

b. Press and hold the power button for storage processor B (SP B) for a few seconds until the power shuts off.

c. Press the standby power supply (SPS) toggle switch on its left side (the O side) to turn the SPS off. (See Figure 1-2 on page 1-7 for a description of the location of the switch.)

d. If you have a 10000XL-series system, repeat these steps to power down each Stor-age Pad array; there is one in each rack of the NPS system.

8. Switch off the power to the two PDU units (located in the rear of the NPS cabinet at the bottom) to completely power down the NPS rack. Make sure that you switch off power to both power switches, and repeat this step on each rack of your HA system.

1-8 D20293-11 Rev.1


Powering Down 5200-Series SystemsThe procedures to power down a 5200 system vary for each type of 5200 system. There are three types of 5200 systems:

5200-BSA (Business Solutions Appliance)

5200-OA (Office Area)

5200-DC (Data Center)

To power down a 5200-BSA system:

1. Shut down any applications that are currently running on the second, separate host for your business applications. (This is the DL145G3 host for HP-based systems, or the x3550 server for IBM-based systems.) Stop the applications using their standard shut-down procedures, then shut down the host operating system using the instructions for that operating system.

2. Press the power button on the front of the second host (DL145G3 or x3550) to power down that server.




nzstate



nzstop

4. Log out of nz, then log on as root using the following command:

su -


shutdown -h now



7. Disconnect the two power cables that lead from the auto-transfer switch to the main power to completely power down the system.

To power down a 5200-OA system:




nzstate


D20293-11 Rev.1 1-9



nzstop

2. Log out of nz, then log on as root using the following command:

su -


shutdown -h now



5. Switch off the power to the UPS located in the bottom of the rack to power down the UPS.

6. Disconnect the power cable that leads from the isolation transformer to the main power to completely power down the system.

To power down a 5200-DC system:




nzstate



nzstop

2. Log out of nz and log on as root.


shutdown -h now



5. Disconnect the two power cables that lead from the auto-transfer switch to the main power to completely power down the system.


This section describes the steps to power up an NPS system. Typically, you power up an NPS to return it to service after it was powered off for routine maintenance or if it was relocated.

1-10 D20293-11 Rev.1


Powering Up a 10000-Series NPS SystemThe procedures for powering up a 10000-series system vary depending upon the type of NPS model that you have. These procedures and models include the following:

Standard NPS systems

Standard NPS systems with the optional Storage Pad array

HA NPS systems that use the Red Hat Cluster Manager solution

HA NPS systems with one or more Storage Pad arrays

The following sections describe the power-on procedures for each of these NPS models.

Powering Up a Standard NPS SystemTo power up a standard NPS system:

1. Switch on the power to the two PDU units (located in the rear of the NPS cabinet at the bottom) to power up the NPS system rack. Make sure that you switch on both power controls, one for each unit.

2. Press the power button on the NPS host (located in the front of the NPS cabinet) to power up the host system.

A series of messages appears as the NPS host system boots.

3. After the host has started, log in as nz to the NPS system.

4. Confirm that the NPS system is online using the following command:

nzstate

Powering Up a Standard NPS System with a Storage Pad Array To power up a standard NPS system that also has the optional Storage Pad array, such as a 10050XL or a 10100XL system:

1. Switch on the power to the two PDU units (located in the rear of the NPS cabinet at the bottom) to power up the NPS system rack. Make sure that you switch on both power controls, one for each unit.


a. Toggle the standby power supply (SPS) switch to the right side (the — side) to turn the SPS on (see Figure 1-3).

Figure 1-3: Storage Pad Standby Power Supply (SPS) Switch

SPS Switch

D20293-11 Rev.1 1-11


b. Press the power button for storage processor A (SP A) to power the device (see Figure 1-4). Note that SP B automatically powers up after you power up SP A.

Note that SP A may not power up right away if the SPS battery is not charged. Wait a few minutes to allow the battery to charge and then power up SP A again.

Figure 1-4: Storage Pad SP Power Switches

Note: Wait five minutes for the Storage Pad array to initialize before proceeding to step 3 to power the host.




5. Confirm that the NPS system is online using the following command:

nzstate

Powering Up an HA HPS System (Red Hat Cluster Manager) To power up a high availability (HA) NPS system that uses the Red Hat Cluster Manager solution:

1. Switch on the power to the two PDU units (located in the rear of each NPS cabinet at the bottom) to power up the NPS rack. Make sure that you switch on both power con-trols for each PDU in each rack of the HA system.

2. Press the power button on the MSA500G2 (located on the bottom right corner of MSA500G2) in host 1.

A series of messages appears as the MSA500G2 performs a self-test. Wait until the self-test completes and both LCDs on the storage array display the message that start-up has completed. This process usually takes about two minutes to complete.

3. Press the power button on host 1 (located in the front of the NPS cabinet) to power up the host system.


SP A Power SwitchSP B Power Switch

1-12 D20293-11 Rev.1


4. Wait at least 30 seconds after powering up host 1, then press the power button on host 2 (located in the front of the NPS cabinet) to power up that host. The delay ensures that host 1 completes its start-up operations first, and thus is the primary host for the HA system.

5. After both hosts have completed the power-up sequence, log in to host 1 as root and run the following command to verify that the cluster services have started:

clustat -i 3

Note: When the cluster manager starts and is ready, status appears as follows. (This could take about one minute.)

Member Status Node ID Power Switch

ha1 up 0 good

ha2 up 0 good

6. Log on to host 1 as the nz account using the following command:

su - nz

7. Verify that the NPS system is online using the following command:

nzstate

Powering Up an HA NPS System with One or More Storage Pad ArraysTo power up a high-availability (HA) NPS system which uses the Linux-HA and DRBD solu-tion and has one or more Storage Pad arrays:

1. Switch on the power to the two PDU units (located in the rear of each NPS cabinet at the bottom) to power up the NPS rack. Make sure that you switch on both power con-trols for each PDU in each rack of the HA system.


a. Toggle the standby power supply (SPS) switch to the right side (the — side) to turn the SPS on. See Figure 1-3 on page 1-11 for the location of the switch.

b. Press the power button for storage processor A (SP A) to power the device. See Figure 1-4 on page 1-12 for the location of the switch. Note that SP B automati-cally powers up after you power up SP A.

Note that SP A may not power up right away if the SPS battery is not charged. Wait a few minutes to allow the battery to charge and then power up SP A again.

c. If you have a 10000XL-series system, repeat these steps to power up each Storage Pad array; there is one in each rack of the NPS system.

Note: Wait five minutes after powering up the last Storage Pad array before proceeding to step 3 to power the host.

3. Press the power button on host 1 (located in the front of the NPS cabinet) to power up the host system.


D20293-11 Rev.1 1-13


4. Wait at least 30 seconds after powering up host 1, then press the power button on host 2 (located in the front of the NPS cabinet) to power up that host. The delay ensures that host 1 completes its start-up operations first, and thus is the primary host for the HA system.

5. After both hosts have completed the power-up sequence, log in to host 1 as root and run the following command to verify that the cluster services have started:

/usr/sbin/crm_mon -i3

The output of the command refreshes at the specified interval rate of 3 seconds (-i3). Review the output and watch for the resource groups to all have a Started status. This usually takes about 2 to 3 minutes, then proceed to step 6. Sample output follows:

============Last updated: Mon Oct 6 12:48:09 2008Current DC: nps50230 (6ea6cffe-3b61-4d29-ac92-5f36ea5f4033)2 Nodes configured.3 Resources configured.============

Node: nps50224 (e00c23e5-1b17-4281-8a2d-403f27129e10): onlineNode: nps50230 (6ea6cffe-3b61-4d29-ac92-5f36ea5f4033): online

Resource Group: npsdrbd_exphome_device (heartbeat:drbddisk): Started nps50230drbd_nz_device (heartbeat:drbddisk): Started nps50230exphome_filesystem (heartbeat::ocf:Filesystem): Started nps50230nz_filesystem (heartbeat::ocf:Filesystem): Started nps50230fabric_ip (heartbeat::ocf:IPaddr): Started nps50230wall_ip (heartbeat::ocf:IPaddr): Started nps50230nzbootpd (lsb:nzbootpd): Started nps50230snmptrapd (lsb:snmptrapd): Started nps50230storagepadinit (lsb:storagepadinit): Started nps50230nzinit (lsb:nzinit): Started nps50230fencing_route_to_ha1 (stonith:apcmaster): Started nps50230fencing_route_to_ha2 (stonith:apcmaster): Started nps50224

Press Control-C to exit the crm_mon command and return to the command prompt.

6. Log on to host 1 as the nz account using the following command:

su - nz

7. Verify that the NPS system is online using the following command:

nzstate

Powering Up 5200-Series SystemsThe procedures to power up a 5200 system vary for each type of 5200 system. There are three types of 5200 systems:

5200-BSA (Business Solutions Appliance)

5200-OA (Office Area)

5200-DC (Data Center)

1-14 D20293-11 Rev.1

Netezza SPU LED Descriptions

To power up a 5200-BSA system:

1. Confirm that the two power cables that lead from the main power are connected to the auto-transfer switch.




4. Start the NPS system using the following command:

nzstart

5. Press the power button on the front of the second host (the DL145G3 or the x3550 host) to power up the application server.

6. After the host starts, log in to the second host and follow the procedures to start your business intelligence applications using their standard start-up procedures.

To power up a 5200-OA system:

1. Confirm that the power cable that leads from the main power is connected to the isola-tion transformer.

2. Switch on the power to the UPS located in either the front or the back of the rack at the bottom to power up the UPS.





nzstart

To power up a 5200-DC system:

1. Confirm that the two power cables that lead from the main power are connected to the auto-transfer switch.





nzstart

Netezza SPU LED Descriptions

The Rev 7 SPUs which are part of the 10000-series, 5200, and z-series NPS systems have three front-facing LEDs that provide administrators with a high-level status of each SPU. When lit, the LEDs can be green or amber in color. The three LEDs are stacked in a row from top to bottom on each SPU.

D20293-11 Rev.1 1-15


The LEDs indicate activity such as hard disk, LAN, or database activity; when the top or bottom LEDs are amber, they indicate a potential problem situation on the SPU such as a hardware fault or SPU firmware issue. Table 1-2 describes the LEDs. To manage SPUs using the nzspu command or the NzAdmin interface, see the NPS System Administrator’s Guide.


This section provides an overview of the Netezza system, and includes information on how to start using an NPS.

Default Users and PasswordsTable 1-3 lists default users and passwords for the host computer. Be sure to change these passwords immediately upon initializing your system.

Note: Users who have permission to write or modify information in the directory /nz/data/ also have access to modify database configuration data, including database administrator passwords.

As the admin database user, you can create other database users and groups to grant and manage access to the objects (such as databases, tables, views, and so on) and administra-tion tasks (such as creating or dropping tables, deleting rows, and creating users). Groups allow you to organize users that have related roles or functions. Groups make it easier to assign the same permissions to all the users by changing the permissions on the group,

Table 1-2: Rev 7 SPU LED Description

LED Color Indication

Top Green Database activity (such as a query in progress)

Amber Auxiliary 1 (indicates a hardware fault or SPU firmware issue)

Middle Green Not used (physical LAN0 activity)

Amber Physical LAN 1 link activity

Bottom Green Hard disk activity (such as reads or writes, loads, and so on)

Amber Auxiliary 0 (indicates a hardware fault or SPU firmware issue)

Table 1-3: Default Users and Passwords

User Password Description

nz nz Linux user, not exposed to NPS client users

admin password NPS database super-user for the NPS host software, with full access to all system functions and objects at all times

root netezza Linux super-user which provides system root login

1-16 D20293-11 Rev.1


rather than changing each user account. When you assign or revoke permissions to the group, all the users in the group have that change in permission. For details about user and group management, refer to the NPS System Administrator’s Guide.

Note: There is also a default database group called public. All users are automatically assigned as members of the public group. You cannot delete the public group, or remove users from it. This group allows you to grant all users the same privilege in one step.

Netezza Common Tasks Table 1-4 lists some of the common tasks that users perform on the NPS and the com-mands or interfaces that you can use to perform those tasks. Note that commands in bold are command line input. SMALL CAPS signify SQL commands.

Note: In Table 1-4, the references in the “Where to Find More Information” column are to the NPS System Administrator’s Guide, unless otherwise noted.

Table 1-4: Netezza Common Tasks

Category Description Command/ToolWhere to Find More Information

Loading data Load data nzload Refer to Chapter 9, Loading Database Data.CREATE EXTERNAL

TABLE

Update data nzload

Unloading data Unload data CREATE EXTERNAL TABLE

nzbackup

Refer to Chapter 12, Backing Up and Restoring Databases.

Sessions Manage or view session

nzsession Refer to Chapter 10, Creating and Main-taining Databases with the CLI.

View session NzAdmin or Web Admin tool

Refer to Chapter 11, Creating and Maintaining Databases with the NzAdmin tool.

Terminate jobs nzsession abort Refer to Chapter 10, Creating and Main-taining Databases with the CLI.

Change priorities nzsession priority

Display session usage

nzsession show

D20293-11 Rev.1 1-17


Queries Display query table nzstats Refer to Chapter 14, Displaying NPS Statistics.

NzAdmin or Web Admin tool

Refer to Chapter 6, Managing the NPS with the NzAdmin Tool.

_v_qrystat view Refer to Chapter 10, Creating and Main-taining Databases with the CLI.

Query history table nzstats Refer to Chapter 14, Displaying NPS Statistics.


Refer to Chapter 6, Managing the NPS with the NzAdmin Tool.

_v_qryhist view Refer to Chapter 10, Creating and Main-taining Databases with the CLI.

Data Distribution View Data Distribution



Privileges Create user NzAdmin or Web Admin tool


CREATE USER Refer to the NPS Database User’s Guide, Appendix B.

[Create] User Refer to Chapter 8, Establishing Secu-rity and Access Control.

Table 1-4: Netezza Common Tasks (continued)


1-18 D20293-11 Rev.1


Privileges (continued)

Create group NzAdmin or Web Admin tool


CREATE GROUP Refer to the NPS Database User’s Guide, Appendix B.

[Create] Group Refer to Chapter 8, Establishing Secu-rity and Access Control.

Grant rights NzAdmin or Web Admin tool


GRANT Refer to the NPS Database User’s Guide, Appendix B.

Revoke access NzAdmin or Web Admin tool

Refer to Chapter 11, Creating and MaintainingDatabases with the NzAdmin tool.

REVOKE Refer to the NPS Database User’s Guide, Appendix B.

Alter access NzAdmin or Web Admin tool

Refer to Chapter 11, Creating and MaintainingDatabases with the NzAdmin tool.

ALTER USER

ALTER GROUP

Refer to the NPS Database User’s Guide, Appendix B.



D20293-11 Rev.1 1-19


Monitoring Show system state nzstate show Refer to Chapter 4, Managing the NPS with the CLI.

Review system messages

Browse to the nz log directory.

Refer to Chapter 4, Managing the NPS with the CLI.

View statistics nzstats show -type <table_name>

Refer to Chapter 14, Displaying NPS Statistics.

View mirroring information

nzinventory show -type dataSlices

Refer to Chapter 4, Managing the NPS with the CLI.

Notification when the system changes states, a hardware component failed, or when the disk is more than 80 per-cent full

nzevent Refer to Chapter 4, Managing the NPS with the CLI.

NzAdmin tool or Web Admin tool

Refer to Chapter 6 or Chapter 7.

Tables Create a table NzAdmin tool Refer to Chapter 10, Creating and Main-taining Databases with the NzAdmin Tool.

CREATE TABLE Refer to the NPS Database User’s Guide, Appendix B.

View table specifics NzAdmin tool or Web Admin

Refer to Chapter 11, Creating and Main-taining Databases with the NzAdmin Tool.

CREATE VIEW

DROP VIEW

Refer to the NPS Database User’s Guide, Appendix B.



1-20 D20293-11 Rev.1


Basic Netezza CLI InformationThis section includes basic information to get you started with the CLI commands.

Running the CLI Commands from a Host, Linux Client, and Windows ClientTable 1-5 lists the NPS commands and the locations where they can be found on the NPS host and on client systems. You can run all of the nz* commands from the NPS host, but certain commands are not available on clients. In the table, a checkmark indicates that the command can be run from that location, while a dash indicates that the command is not available from that location

Table 1-5: CLI Command Locations

Default Location /nz/kit/bin /usr/local/nz/binC:\Program Files\Netezza\Bin

PlatformNPS Server Host

Linux Client

Solaris Client

HPUXClient

AIX Client

Windows Client

nzbackup — — — — —

nzhostbackup — — — — —

nzhostrestore — — — — —

nzrestore — — — — —

nzstart — — — — —

nzstop — — — — —

nzcontents — —

nzconvert

nzevent

nzinventory

nzload

nzpassword

nzreclaim

nzrev

nzsession

nzsfi

nzspu

nzsql —

nzstate

D20293-11 Rev.1 1-21


Common CLI Command OptionsTable 1-6 lists some common nz* command options and their default values.

Commonly Used nzload Command OptionsTable 1-7 lists commonly used nzload command options. For more information on nzload command options, refer to the NPS System Administrator’s Guide.

nzstats

nzsystem

Table 1-6: Commonly Used Command Options

Option Description Default value

-u <user> Database username [NZ_USER]

-pw <password> Database password [NZ_PASSWORD]

-db <database> Database name [NZ_DATABASE]

-host <name/ip> Netezza hostname or IP address [NZ_HOST]

Table 1-7: Commonly Used nzload Command Options

Options Description

-t <name> Specifies the target table into which to load the data.

-df <data file path> Specifies the dataobject filepath. If you do not specify a path the system uses the special token <stdin> to store the filepath string.

-maxErrors <n> Specifies to abort the load after encountering ‘n’ bad input rows. Do not set this to 0 (unlimited) or greater than 100,000. The default is 1.

Note: Internally, the NPS system uses external tables when working with the -maxErrors option. It is normal to see a reference to external tables in a related error message.

-delim <char> Specifies the separator between successive input fields. (The default is \t.)

Table 1-5: CLI Command Locations (continued)

Default Location /nz/kit/bin /usr/local/nz/binC:\Program Files\Netezza\Bin

PlatformNPS Server Host

Linux Client

Solaris Client

HPUXClient

AIX Client

Windows Client

1-22 D20293-11 Rev.1


Table 1-8 lists nzload log files. For more information about the log files and how to use them, refer to the NPS System Administrator’s Guide.

-escapeChar <char> Specifies an escape character in char or varchar fields. You can specify the –escapeChar option to permit any character preceded with a backslash (\) to be interpreted as an escape character. In this way, you could use the zero (byte 0), line feed (byte 10), carriage return (byte 13), or the closing delimiter.

-ctrlChars Allows an ASCII value 1-31 in char() and var-char() fields. (You must escape NUL, CR, and LF.)

-crlnString Allows unescaped carriage returns (CR) in char and varchar fields. (LF becomes only end of row.)

-dateStyle <style> Specifies how to interpret the date format. Styles include Y[2]MD, DMY[2], MDY[2], and MONDY[2]. The default is YMD.

-dateDelim <char> Specifies the delimiter (date component separa-tor) to use with the dateStyle option. The default -dateDelim option is a dash (-). The -dateDelim value cannot be the same as the -timeDelim value.

timeStyle <style> Specifies the 24 hour or 12 hour time format, such as 24HOUR or 12HOUR. The default is 24HOUR.

-timeDelim <char> Specifies the delimiter to use for time formats. The default is a colon (:).

Table 1-8: Log files for nzload

File format Description

<table>.<database>.nzlog Includes summary report and information about any bad records encountered. (The sys-tem appends to the nzlog file each time you load the same table into the same database.)

<table>.<database>.nzbad Includes the bad records in their original state. (The system overwrites the nzbad file each time you load the same table into the same database.)

Table 1-7: Commonly Used nzload Command Options (continued)

Options Description

D20293-11 Rev.1 1-23


Basic Netezza SQL InformationThis section includes basic information to get you started with the Netezza SQL commands.

SQL CommandsTable 1-9 lists some of the Netezza SQL commands. For more information on particular commands, refer to the NPS Database User’s Guide.

Table 1-9: Netezza SQL Commands

List of SQL Commands

ALTER AGGREGATE ALTER DATABASEALTER FUNCTION ALTER GROUPALTER SEQUENCEALTER SESSIONALTER SYNONYMALTER TABLEALTER USERALTER VIEWBEGIN COMMENTCOMMITCOPYCREATE AGGREGATECREATE DATABASECREATE EXTERNAL TABLECREATE FUNCTION CREATE GROUP

CREATE MATERIALIZED VIEWCREATE OR REPLACE VIEW CREATE SEQUENCECREATE SYNONYMCREATE TABLECREATE TABLE ASCREATE USERCREATE VIEWDELETEDROP AGGREGATE DROP DATABASEDROP FUNCTION DROP GROUPDROP SEQUENCEDROP SYNONYMDROP TABLEDROP USERDROP VIEW

EXPLAINEXTRACTGENERATE EXPRESS STATISTICSGENERATE STATISTICSGRANTINSERTRESETREVOKEROLLBACKSELECTSETSET SESSIONSET SYSTEM DEFAULTSET TRANSACTIONSHOWSHOW SYSTEM DEFAULTTRUNCATEUPDATE

1-24 D20293-11 Rev.1


SQL Quick TipsTable 1-10 lists SQL tips for getting started.

Commonly Used nzsql Internal Slash CommandsTable 1-11 lists commonly used internal slash commands that you can use when you are in an nzsql session. For more information on the slash options, refer to the NPS Database User’s Guide.

Table 1-10: SQL Tips

Tip Sample

Use single quotes around string literals. 'The quick brown fox'

Use double quotes around labels. SELECT Iname AS “Last Name”

Identifiers are case sensitive, but they are treated as uppercase (sys-tem default) unless you enclose them in double quotes.

Rather than returning an unknown quantity of records, first get a sense as to the size of your result set.

SELECT COUNT (*) FROM (your_query) AS “Wrapper”;

Limit the number of records that your application returns.

...LIMIT <nnn>;

Parse the query, but do not actually run it. ...LIMIT 0;

Table 1-11: Commonly Used Internal Slash Options

Command Description

\? Lists the available internal slash commands.

\h Lists the available NZSQL commands.

\h cmd Displays help for a specific NZSQL command. For example: \h create table.

\q Quits nzsql.

\l Lists all databases.

\dt Lists all tables.

\dSt Lists all system tables.

\d table Describes a table.

\dv Lists all views.

D20293-11 Rev.1 1-25


Commonly Used nzsql Command Line OptionsTable 1-12 lists commonly used nzsql command line options. For more information about the nzsql command options, refer to the NPS Database User’s Guide.

A sample SQL statement follows.

\dSv Lists all system views.

\d view Describes a view.

\echo text Writes <text> to stdout.

\! cmd Shell escape or command. (Runs a shell command without leaving the nzsql session.)

Table 1-12: Commonly Used nzsql Command Options

Option Description

-A Use unaligned table output mode.

Note: You can combine this option with the next option to “dump” a table. For high volume output, use an external table.

-t Print rows only.

-f filename Execute queries from a file, then exit.

-o filename Send query output to filename.

-c query Run only single query or slash command, then exit.

-E Display queries that internal commands generate.

-F string Set the field separator. The default is a vertical bar '|'.

-x Enable expanded table output.

-h Display help.

Table 1-11: Commonly Used Internal Slash Options (continued)

Command Description

USERDB(MARK)=> insert into state_table values ('VA', 'Virginia');

INSERT 0 1

DatabaseUsername

Prompt

Query Response

Query

1-26 D20293-11 Rev.1


Choosing a Backup and Restore MethodNetezza provides three backup and restore methods. The one you choose depends on your needs and particular situation. The three methods are:

Create full and incremental backups and restore any increment by using the nzbackup and nzrestore commands.

Manually unload and reload individual table data by using the nzsql CREATE EXTER-NAL TABLE command and specifying compressed internal format external tables.

For information about using the nzsql CREATE EXTERNAL TABLE command, see the Netezza Performance Server Database User’s Guide.

Manually unload and reload individual table data by using the nzsql CREATE EXTER-NAL TABLE command and specifying text format external tables.

Table 1-13 lists the differences among the backup and restore methods.

Table 1-13: Choosing a Backup and Restore Method

Featurenzbackup and nzrestore

Compressed External Tables

Text Format External Tables

Schema backup — —

Full automatic database backup — —

Manual per-table backup —

Manual per-table restore

Veritas NetBackup — —

Tivoli Storage Manager — —

Automatic incremental — —

Compressed format —

Non-proprietary format — —

Machine-size independent a

a. This option often requires more time.

a

Rowid preserved —

Transaction ID preserved — — —

Upgrade safe

Downgrade safe — —

D20293-11 Rev.1 1-27


Getting Help

This section describes how to find the Netezza customer user guides and documentation, how to use online help, and how to contact Netezza Support when you have questions or a possible problem.

PDF DocumentationNetezza includes user guides in Adobe PDF format on the NPS Documentation CD. Updated guides are also available on the Netezza FTP site (ntzftp.netezza.com) in the Doc-umentation area. Table 1-14 lists several of the commonly used manuals.

Note: As of NPS Release 3.0, the user guides are not installed by default to the /nz/kit/doc directory on the NPS host; however, the NPS Software Upgrade Guide describes how to manually copy the PDF files to that location or to any network location if you want to make the guides available across your network to your users.

Table 1-14: Key User Manuals

File Description

Netezza_database_users_guide.pdf NPS Database User’s Guide describes the Netezza SQL language used for queries to databases on the NPS systems.

Netezza_system_admin_guide.pdf NPS System Administrator’s Guide is written for system and database administrators. It describes how to manage the NPS systems and database.

Netezza_release_notes.pdf Netezza Performance Server Release Notes includes a list of new features and enhance-ments, known issues, and customer-reported issues that have been fixed in the release.

Netezza_getting_started_tips.pdf Netezza Performance Server Getting Started Tips (this guide) describes background infor-mation and tips for using the NPS system.

Netezza_odbc_jdbc_guide.pdf NPS ODBC, JDBC and OLE DB Installation and Configuration Guide provides information for those who want to install and configure ODBC clients, JDBC clients, or the OLE DB connector to communicate with the NPS.

1-28 D20293-11 Rev.1

Getting Help

Online HelpNetezza documentation includes online help for the administration UIs and commands.

NPS Web Admin HelpYou can view the entire system administration help or specific context-sensitive help for the NPS Web Admin interface. The help is best viewed using an Internet Explorer Web browser; other browsers may not support the help window navigation controls.

To view the system administration help, click Help Contents in the navigation pane. A sample help screen follows:

To view context-sensitive help, click the question mark on any page. A sample context-sensitive help screen follows:

D20293-11 Rev.1 1-29


NzAdmin Online HelpFrom the NzAdmin interface, you can view context-sensitive administration help for various tasks, or you can open the entire system administration contents.

To view the system administration help, select Help > NzAdmin Help from the menu.

To view task-oriented help, select an item in the left navigation frame and press F1 to obtain help for that item. A sample help page for the Alerts task follows.

Netezza CLI Commands Online HelpNetezza CLI commands are commands that begin with an “nz” prefix. You can view online help for a Netezza CLI command by entering the command followed by -h. Sample com-mand help follows:

> nzsystem -h

Usage: nzsystem [-h|-rev] [-hc] <subcmd> [<subcmd options>]

Options:

-h or -? or --help display this help-[rR]ev or -V print the software revision of this program-hc display help for <subcmd>

Subcommands:

showState show the overall system state (default) showRev show the system's software revisionshowRegistry show the system's configuration registryoffline take the system offlinepause pause the systemrestart stop and then automatically start the systemresume bring the system back onlinestop stop the systeminitTopology create the initial topology configurationset configure system setting(s)

1-30 D20293-11 Rev.1

Getting Help

Netezza CLI commands often include subcommands. In the preceding example of the nzsystem command, the subcommands are listed in a distinct section. You can view help for Netezza CLI subcommands by entering the name of the CLI command, followed by -hc, followed by the name of the subcommand. Sample subcommand online help follows:

> nzsystem -hc stop

Usage: nzsystem stop [<subcmd options>]

Subcmd Options:

-host <name/IP> host name or IP address [NZ_HOST]-timeout <secs> time to wait before exiting with a timeout error

(default = 300)-u <user name> login using <user name> [NZ_USER]-pw <password> authentication password [NZ_PASSWORD]-pw <password> authentication password [NZ_PASSWORD]-now do not wait for current work to finish-nowAfter <secs> time for work to finish before resorting to '-now'

(default = 300)-force do not prompt for confirmation

Netezza SQL Commands Online HelpTo manage databases and run queries on the NPS, you use the Netezza Structured Query Language (NZSQL). You access NZSQL using the nzsql command. While you are in the nzsql interpreter, you can obtain help for the available commands by using the \h slash command followed by the Netezza SQL command. Sample Netezza SQL command online help follows:

> \h generate statistics

Command: GENERATE STATISTICSDescription: Generates statistics on a database, table, and columns within a table.Syntax:GENERATE STATISTICS [ ON table [ ( column_name [, ... ] ) ] ]GENERATE EXPRESS STATISTICS ON table [ ( column_name [, ... ] ) ]

Netezza Support Contact Information For assistance with the Netezza products, contact Netezza Support over the Internet at the Netezza Support website: https://support.netezza.com. Users require a valid customer login to access the Support site.

For critical issues, you can also contact Support by telephone:

North American Toll-Free: +1.877.810.4441

United Kingdom Free-Phone: +0.800.032.8382

International Direct: +1.508.620.2281

If you contact Support by telephone, be sure to also submit a ticket on the website so that relevant information is saved along with the report and resolution.

D20293-11 Rev.1 1-31


1-32 D20293-11 Rev.1

Documents

4.6.5 Netezza Getting Started Tips