Netezza System Admin Guide

IBM Netezza
Release 7.2.1.1
IBM Netezza System Administrator’s

Guide
IBM
Note
Before using this information and the product it supports, read the information in “Notices” on page D-1
Revised: December 4, 2015

This edition applies to IBM Netezza Release 7.2.1.1 and to all subsequent releases until otherwise indicated in new
editions.
© Copyright IBM Corporation 2001, 2015.
US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.
Contents
Figures . . . . . . . . . . . . . .. ix The nzsql command . . . . . . . . .. 3-5
NzAdmin overview . . . . . . . . . .. 3-12
Tables . . . . . . . . . . . . . .. xi Starting the NzAdmin tool. . . . . . .. 3-12
Displaying system components and databases 3-13
Using the System view . . . . . . . .. 3-14
Electronic emission notices . . . .. xiii Status indicators . . . . . . . . . .. 3-15
Main menu . . . . . . . . . . . .. 3-16
Regulatory and compliance . . . .. xvii Administration commands. . . . . . .. 3-16
Setting an automatic refresh interval . . .. 3-17
About this publication . . . . . . .. xix Netezza Performance Portal overview . . . .. 3-18
If you need help . . . . . . . . . . .. xix
How to send your comments . . . . . . .. xix Chapter 4. Manage Netezza HA
systems . . . . . . . . . . . . .. 4-1
Chapter 1. Administration overview 1-1 Linux-HA and DRBD overview . . . . . .. 4-1
Administrator’s roles . . . . . . . . . .. 1-1 Differences with the previous Netezza HA solution 4-2
Administration tasks . . . . . . . . . .. 1-1 Linux-HA administration . . . . . . . .. 4-2
Initial system setup and information . . . . .. 1-1 Heartbeat configuration . . . . . . . .. 4-3
Netezza software directories . . . . . .. 1-2 Cluster Information Base. . . . . . . .. 4-3
External network connections . . . . . .. 1-5 Important information about host 1 and host 2 4-3
Domain Name Service (DNS) Updates . . .. 1-5 Failover timers . . . . . . . . . . .. 4-4
Remote access . . . . . . . . . . .. 1-8 Netezza cluster management scripts . . . .. 4-4
Administration interfaces . . . . . . . .. 1-8 Active and standby nodes . . . . . . .. 4-5
Other Netezza documentation . . . . . . .. 1-9 Cluster and resource group status . . . .. 4-5
The nps resource group . . . . . . . .. 4-7
Chapter 2. Netezza client software Failover criteria . . . . . . . . . . .. 4-7
Relocate to the standby node . . . . . .. 4-8
installation. . . . . . . . . . . .. 2-1
Safe manual control of the hosts and Heartbeat 4-8
Client software packages. . . . . . . . .. 2-1
Transitioning to maintenance (non-Heartbeat)
Install the Netezza CLI client on a Linux/UNIX
mode . . . . . . . . . . . . . .. 4-9
system . . . . . . . . . . . . . . .. 2-2
Transitioning from maintenance to clustering
Installing on Linux/UNIX Clients. . . . .. 2-2
mode . . . . . . . . . . . . . .. 4-10
Path for Netezza CLI client commands . . .. 2-6
Configuring Cluster Manager events . . .. 4-11
Removing the CLI clients from UNIX systems 2-6
Logging and messages . . . . . . . .. 4-12
Install the Netezza tools on a Windows client . .. 2-6
DRBD administration . . . . . . . . .. 4-12
Installation requirements. . . . . . . .. 2-7
Monitor DRBD status . . . . . . . .. 4-13
Installing the Netezza tools . . . . . . .. 2-7
Sample DRBD status output . . . . . .. 4-14
Environment variables . . . . . . . .. 2-8
Detecting split-brain . . . . . . . . .. 4-14
Removing the IBM Netezza tools . . . . .. 2-8
Administration reference and troubleshooting .. 4-15
Clients and Unicode characters . . . . . .. 2-9
IP address requirements . . . . . . .. 4-15
Client timeout controls . . . . . . . . .. 2-10
Force Heartbeat to shut down . . . . .. 4-16
Netezza port numbers . . . . . . . . .. 2-10
Shut down Heartbeat on both nodes without
Changing the default port numbers . . . .. 2-11
causing relocate . . . . . . . . . .. 4-16
Non-default NPS port numbers for clients .. 2-12
Restart Heartbeat after maintenance network
Encrypted passwords . . . . . . . . .. 2-13
issues . . . . . . . . . . . . . .. 4-16
Stored passwords . . . . . . . . . . .. 2-14
Resolve configuration problems . . . . .. 4-16
Fixed a problem, but crm_mon still shows
Chapter 3. Netezza administration failed items . . . . . . . . . . . .. 4-17
interfaces . . . . . . . . . . . .. 3-1 Output from crm_mon does not show the nps
Netezza CLI overview . . . . . . . . .. 3-1 resource group. . . . . . . . . . .. 4-17
Commands and locations . . . . . . .. 3-1 Linux users and groups required for HA . .. 4-17
Command locations . . . . . . . . .. 3-3 Checking for user sessions and activity . .. 4-18
Command syntax . . . . . . . . . .. 3-3
Issuing commands . . . . . . . . . .. 3-4 Chapter 5. Manage the Netezza
Identifiers in commands . . . . . . . .. 3-4 hardware . . . . . . . . . . . .. 5-1
SQL command overview . . . . . . . . .. 3-5
Netezza hardware components . . . . . .. 5-1
© Copyright IBM Corp. 2001, 2015 iii

Display hardware components . . . . . .. 5-2 AekSecurityEvent. . . . . . . . . . .. 6-15
Hardware types. . . . . . . . . . .. 5-4
Hardware IDs . . . . . . . . . . .. 5-5 Chapter 7. Manage the Netezza server 7-1
Hardware location . . . . . . . . . .. 5-5 Software revision levels . . . . . . . . .. 7-1
Hardware roles . . . . . . . . . . .. 5-8 Display the Netezza software revision . . .. 7-1
Hardware states . . . . . . . . . .. 5-9 Display the software revision levels . . . .. 7-1
Data slices, data partitions, and disks . . .. 5-11 System states . . . . . . . . . . . .. 7-2
IBM Netezza Storage Design . . . . . .. 5-12 Display the current system state . . . . .. 7-2
Netezza C1000 Storage Design . . . . .. 5-13 System states reference . . . . . . . .. 7-4
IBM PureData System for Analytics N3001-001 Wait for a system state . . . . . . . .. 7-5
storage design . . . . . . . . . . .. 5-15 Manage the system state . . . . . . . . .. 7-6
System resource balance recovery . . . .. 5-17 Start the system. . . . . . . . . . .. 7-6
Hardware management tasks . . . . . . .. 5-18 Stop the system . . . . . . . . . . .. 7-7
Callhome file . . . . . . . . . . .. 5-19 Pause the system . . . . . . . . . .. 7-7
Display hardware issues . . . . . . .. 5-19 Resume the system . . . . . . . . .. 7-7
Manage hosts . . . . . . . . . . .. 5-19 Take the system offline . . . . . . . .. 7-8
Manage SPUs . . . . . . . . . . .. 5-20 Restart the system . . . . . . . . . .. 7-8
Manage disks . . . . . . . . . . .. 5-23 Overview of the Netezza system processing .. 7-8
Manage data slices . . . . . . . . . .. 5-25 System states when Netezza starts . . . .. 7-10
Display data slice issues . . . . . . .. 5-26 System errors . . . . . . . . . . . .. 7-11
Monitor data slice status . . . . . . .. 5-26 System logs. . . . . . . . . . . . .. 7-12
Regenerate a data slice . . . . . . . .. 5-27 Backup and restore manager . . . . . .. 7-12
Rebalance data slices . . . . . . . .. 5-29 Bootserver manager . . . . . . . . .. 7-13
Active path topology . . . . . . . .. 5-29 Client manager . . . . . . . . . .. 7-13
Handle transactions during failover and Database operating system . . . . . .. 7-13
regeneration . . . . . . . . . . .. 5-31 Event manager . . . . . . . . . .. 7-14
Automatic query and load continuation . . .. 5-32 Flow communications retransmit . . . .. 7-15
Power procedures . . . . . . . . . .. 5-32 Host statistics generator . . . . . . .. 7-15
PDU and circuit breakers overview . . . .. 5-32 Load manager . . . . . . . . . . .. 7-15
Powering on the IBM Netezza 1000 and IBM Postgres . . . . . . . . . . . . .. 7-15
PureData System for Analytics N1001 . . .. 5-34 Session manager . . . . . . . . . .. 7-16
Powering off the IBM Netezza 1000 or IBM SPU cores manager . . . . . . . . .. 7-16
PureData System for Analytics N1001 system . 5-35 Startup server . . . . . . . . . . .. 7-16
Powering on the IBM PureData System for Statistics server . . . . . . . . . .. 7-17
Analytics N200x . . . . . . . . . .. 5-37 System Manager . . . . . . . . . .. 7-17
Powering off the IBM PureData System for The nzDbosSpill file . . . . . . . . .. 7-17
Analytics N200x system . . . . . . .. 5-38 System configuration . . . . . . . . .. 7-18
Powering on the IBM Netezza High Capacity Displaying the software revision level and
Appliance C1000 . . . . . . . . . .. 5-39 configuration registry settings . . . . .. 7-18
Powering off the IBM Netezza High Capacity Changing configuration settings . . . . .. 7-19
Appliance C1000 . . . . . . . . . .. 5-40
Powering on IBM PureData System for
Chapter 8. Event rules . . . . . . .. 8-1
Analytics N3001-001 . . . . . . . . .. 5-41
Template event rules . . . . . . . . . .. 8-1
Powering off IBM PureData System for
Event rule management . . . . . . . . .. 8-5
Analytics N3001-001 . . . . . . . . .. 5-42
Copy a template event to create an event rule 8-5
Copy and modify a user-defined event rule .. 8-6
Chapter 6. About self-encrypting Generate an event . . . . . . . . . .. 8-6
drives . . . . . . . . . . . . . .. 6-1 Delete an event rule . . . . . . . . .. 8-6
Locking the SEDs . . . . . . . . . . .. 6-1 Disable an event rule . . . . . . . . .. 8-7
Unlocking the SEDs . . . . . . . . . .. 6-3 Add an event rule . . . . . . . . . .. 8-7
SED keystore . . . . . . . . . . . .. 6-3 Event match criteria . . . . . . . . .. 8-7
IBM Security Key Lifecycle Manager configuration Event rule attributes . . . . . . . . .. 8-11
steps . . . . . . . . . . . . . . .. 6-4 Event notifications . . . . . . . . .. 8-12
SED authentication keys . . . . . . . . .. 6-7 The sendMail.cfg file . . . . . . . .. 8-12
Generate authentication keys . . . . . .. 6-8 Event email aggregation . . . . . . .. 8-14
List authentication keys . . . . . . . .. 6-8 Creating a custom event rule . . . . . .. 8-16
Check authentication keys . . . . . . .. 6-9 Template event reference . . . . . . . .. 8-17
Extract authentication keys . . . . . .. 6-12 System state changes . . . . . . . .. 8-17
Change the host authentication key . . . . .. 6-12 Hardware service requested . . . . . .. 8-18
Resume host AEK key change . . . . .. 6-13 Hardware needs attention . . . . . . .. 8-20
Change the SPU authentication key. . . . .. 6-14
iv IBM Netezza System Administrator’s Guide

Hardware path down . . . . . . . .. 8-20 Chapter 11. Security and access
Hardware restarted . . . . . . . . .. 8-22 control . . . . . . . . . . . . .. 11-1
Disk space threshold notification . . . .. 8-22 Netezza database users and user groups . . .. 11-1
Runaway query notification . . . . . .. 8-24 Access model . . . . . . . . . . .. 11-3
System state . . . . . . . . . . .. 8-25 Default Netezza groups and users . . . .. 11-3
Disk predictive failure errors event . . . .. 8-25 User authentication method . . . . . .. 11-4
Regeneration errors . . . . . . . . .. 8-26 Password content controls and reuse . . .. 11-5
Disk errors event . . . . . . . . . .. 8-27 Create Netezza database users . . . . .. 11-7
Hardware temperature event . . . . . .. 8-28 Alter Netezza database users . . . . . .. 11-8
System temperature event . . . . . . .. 8-29 Delete Netezza database users . . . . .. 11-8
History-data events . . . . . . . . .. 8-30 Create Netezza database groups . . . . .. 11-8
SPU cores event . . . . . . . . . .. 8-32 Alter Netezza database groups . . . . .. 11-9
Voltage faults event . . . . . . . . .. 8-33 Delete Netezza database groups . . . . .. 11-9
Transaction limits event. . . . . . . .. 8-33 Security model. . . . . . . . . . . .. 11-9
Switch port events . . . . . . . . .. 8-34 Administrator privileges . . . . . . .. 11-10
Reachability and availability events . . . .. 8-35 Object privileges . . . . . . . . . .. 11-11
Topology imbalance event . . . . . . .. 8-35 Object privileges by class . . . . . . .. 11-12
Event types reference . . . . . . . . .. 8-36 Scope of object privileges . . . . . . .. 11-12
Display alerts . . . . . . . . . . . .. 8-36 Revoke privileges . . . . . . . . .. 11-15
Privileges by object . . . . . . . . .. 11-15
Chapter 9. About the callhome service 9-1 Inherited connection privileges . . . . .. 11-17
Set up callHome.txt . . . . . . . . . .. 9-2 Indirect object privileges . . . . . . .. 11-17
Custom callhome email subject fields . . .. 9-5 Functions that are always available . . .. 11-17
Set up the sendMail.cfg File . . . . . . .. 9-6 Creating an administrative user group . .. 11-17
Configure access to the IBM Support servers . .. 9-8 Logon authentication . . . . . . . . .. 11-18
Enable the callhome service. . . . . . . .. 9-8 Local authentication . . . . . . . .. 11-19
nzcallhome verbose output . . . . . . .. 9-9 LDAP authentication . . . . . . . .. 11-19
Enable callhome debug logging . . . . .. 9-9 Kerberos authentication . . . . . . .. 11-22
Enable PMR creation . . . . . . . .. 9-10 Commands related to authentication methods 11-27
Enable status reporting . . . . . . . .. 9-10 Passwords and logons . . . . . . . .. 11-28
Enable inventory reporting . . . . . .. 9-10 Netezza client encryption and security . . .. 11-29
Enable email-only PMR notification . . . .. 9-11 Configuring the SSL certificate . . . . .. 11-30
Display callhome service status . . . . . .. 9-11 Configure the Netezza host authentication for
Callhome event rules . . . . . . . . .. 9-12 clients . . . . . . . . . . . . .. 11-31
Callhome event severities . . . . . . . .. 9-13 Commands related to Netezza client
Blocking callhome events . . . . . . . .. 9-14 connection methods . . . . . . . .. 11-34
Information collected by callhome . . . . .. 9-14 User and group limits . . . . . . . . .. 11-34
Testing the callhome services . . . . . . .. 9-15 Password expiration . . . . . . . .. 11-35
Generate callhome events . . . . . . .. 9-15 User rowset limits . . . . . . . . .. 11-36
Callhome processing verification (HTTPS only) 9-17 Query timeout limits . . . . . . . .. 11-37
Callhome processing verification (email only) 9-17 Session timeout . . . . . . . . . .. 11-38
Sample callhome email . . . . . . . .. 9-17 Session priority . . . . . . . . . .. 11-38
Generate callhome reports . . . . . . . .. 9-19 Logging Netezza SQL information . . . . .. 11-39
Generate a system upgrade request . . . . .. 9-19 Logging Netezza SQL information on the
Disable the callhome service . . . . . . .. 9-19 server . . . . . . . . . . . . .. 11-39
Disable callhome event rules . . . . . . .. 9-20 Logging Netezza SQL information on the
Remove callhome event rules . . . . . . .. 9-21 client . . . . . . . . . . . . .. 11-39
Group public views. . . . . . . . . .. 11-40
Chapter 10. Enhanced cryptography
support . . . . . . . . . . . .. 10-1 Chapter 12. Manage user content on
NPS requirements for enhanced cryptography the Netezza appliance . . . . . .. 12-1
support . . . . . . . . . . . . . .. 10-2 Databases and user tables . . . . . . . .. 12-1
How to enable SP 800-131a support. . . . .. 10-2 Netezza database schema overview . . . .. 12-2
Enabling SP 800-131a support. . . . . . .. 10-3 Table size and storage space . . . . . .. 12-3
Updating connections for crypto support . . .. 10-5 Disk space usage in tables . . . . . . .. 12-4
Checking the connection types . . . . . .. 10-5 Database and table guidelines . . . . .. 12-5
Disabling enhanced cryptography support . .. 10-6 Row IDs in tables. . . . . . . . . .. 12-5
Enhanced cryptography troubleshooting . . .. 10-7 Transaction IDs . . . . . . . . . .. 12-5
Downgrading an SP 800-131a crypto NPS system 10-10 Distribution keys . . . . . . . . . . .. 12-6
Select a distribution key . . . . . . .. 12-7
Contents v
Criteria for selecting distribution keys . . .. 12-7 The nzbackup command . . . . . . . .. 13-11
Choose a distribution key for a subset table 12-7 Command syntax for nzbackup. . . . .. 13-12
Distribution keys and collocated joins . . .. 12-8 Specifying backup privileges . . . . .. 13-15
Dynamic redistribution or broadcasts . . .. 12-8 Examples of the nzbackup command . . .. 13-15
Verify distribution . . . . . . . . .. 12-8 Backup archive directory . . . . . . .. 13-17
Data skew . . . . . . . . . . . . .. 12-10 Incremental backups . . . . . . . .. 13-18
Specify distribution keys . . . . . . .. 12-10 Backup History report . . . . . . . .. 13-20
View data skew . . . . . . . . . .. 12-11 Back up and restore users, groups, and
Clustered base tables . . . . . . . . .. 12-12 permissions . . . . . . . . . . .. 13-21
Organizing keys and zone maps . . . .. 12-13 The nzrestore command . . . . . . . .. 13-22
Select organizing keys . . . . . . . .. 12-14 The nzrestore command syntax . . . . .. 13-23
Reorganize the table data . . . . . . .. 12-14 Specifying restore privileges . . . . . .. 13-28
Copy clustered base tables . . . . . .. 12-15 Examples of the nzrestore command . . .. 13-29
Database statistics . . . . . . . . . .. 12-15 Database statistics after restore . . . . .. 13-30
Maintain table statistics automatically . .. 12-16 Restore tables. . . . . . . . . . .. 13-30
GENERATE STATISTICS command . . .. 12-17 Incremental restoration . . . . . . .. 13-31
Just in Time statistics . . . . . . . .. 12-17 Veritas NetBackup connector . . . . . .. 13-34
Zone maps . . . . . . . . . . .. 12-18 Installing the Veritas NetBackup license . .. 13-34
Groom tables . . . . . . . . . . . .. 12-20 Configuring NetBackup for a Netezza client 13-35
GROOM and the nzreclaim command . .. 12-20 Integrate Veritas NetBackup to Netezza . .. 13-36
Identify clustered base tables that require NetBackup troubleshooting . . . . . .. 13-40
grooming . . . . . . . . . . . .. 12-21 Procedures for backing up and restoring by
Organization percentage . . . . . . .. 12-22 using Veritas NetBackup . . . . . . .. 13-40
Groom and backup synchronization . . .. 12-23 IBM Spectrum Protect (formerly Tivoli Storage
Session management . . . . . . . . .. 12-23 Manager) connector . . . . . . . . .. 13-42
The nzsession command . . . . . . .. 12-23 Tivoli Storage Manager backup integration 13-43
Transactions . . . . . . . . . . . .. 12-25 Tivoli Storage Manager encrypted backup
Transaction control and monitoring . . .. 12-25 support. . . . . . . . . . . . .. 13-43
Transactions per system . . . . . . .. 12-25 Configuring the Netezza host . . . . .. 13-43
Transaction concurrency and isolation . .. 12-26 Configure the Tivoli Storage Manager server 13-48
Concurrent transaction serialization and Special considerations for large databases 13-54
queueing, implicit transactions . . . . .. 12-26 The nzbackup and nzrestore commands with
Concurrent transaction serialization and the Tivoli Storage Manager connector. . .. 13-57
queueing, explicit transactions . . . . .. 12-27 Host backup and restore to the Tivoli Storage
Netezza optimizer and query plans . . . .. 12-28 Manager server . . . . . . . . . .. 13-57
Execution plans . . . . . . . . . .. 12-28 Backing up and restoring data by using the
Display plan types . . . . . . . . .. 12-28 Tivoli Storage Manager interfaces . . . .. 13-58
Analyze query performance . . . . . .. 12-29 Troubleshooting . . . . . . . . . .. 13-60
Query status and history . . . . . . . .. 12-30 EMC NetWorker connector . . . . . . .. 13-61
Preparing your system for EMC NetWorker
Chapter 13. Database backup and integration. . . . . . . . . . . .. 13-62
restore . . . . . . . . . . . . .. 13-1 NetWorker installation. . . . . . . .. 13-62
NetWorker configuration . . . . . . .. 13-62
General information about backup and restore
NetWorker backup and restore . . . . .. 13-64
methods . . . . . . . . . . . . . .. 13-1
Host backup and restore . . . . . . .. 13-66
Backup options overview . . . . . . .. 13-2
NetWorker troubleshooting . . . . . . .. 13-67
Database completeness . . . . . . . .. 13-3
Portability . . . . . . . . . . . .. 13-3
Compression in backups and restores . . .. 13-4 Chapter 14. History data collection 14-1
Multi-stream backup. . . . . . . . .. 13-4 Types of history databases . . . . . . . .. 14-1
Multi-stream restore . . . . . . . . .. 13-5 History database versions . . . . . . . .. 14-2
Special columns . . . . . . . . . .. 13-6 History-data staging and loading processes . .. 14-2
Upgrade and downgrade concerns . . . .. 13-6 History-data files . . . . . . . . . .. 14-3
Compressed unload and reload . . . . .. 13-7 History log files . . . . . . . . . .. 14-4
Encryption key management in backup and History event notifications . . . . . . .. 14-4
restore . . . . . . . . . . . . .. 13-7 Setting up the system to collect history data . .. 14-4
File system connector for backup and recovery 13-7 Planning for history-data collection . . . .. 14-4
Third-party backup and recovery solutions Creating a history database . . . . . .. 14-5
support . . . . . . . . . . . . .. 13-8 Creating history configurations . . . . .. 14-5
Host backup and restore . . . . . . . .. 13-9 Managing access to a history database . . .. 14-9
Create a host backup . . . . . . . .. 13-10 Managing the collection of history data . . .. 14-9
Restore the host data directory and catalog 13-10 Changing the owner of a history database .. 14-9
vi IBM Netezza System Administrator’s Guide

Dropping a history database. . . . . .. 14-10 DBMS Group . . . . . . . . . . .. 16-2
Starting the collection of history data . . .. 14-11 Host CPU Table . . . . . . . . . .. 16-3
Stopping the collection of history data . .. 14-11 Host File System Table . . . . . . . .. 16-3
Changing history configuration settings . .. 14-11 Host Interface Table . . . . . . . . .. 16-4
Displaying history configuration settings 14-12 Host Mgmt Channel Table . . . . . . .. 16-4
Dropping history configurations . . . .. 14-12 Host Network Table . . . . . . . . .. 16-5
Managing history configurations by using Host Table . . . . . . . . . . . .. 16-6
NzAdmin . . . . . . . . . . . .. 14-13 Hardware Management Channel Table. . .. 16-7
Maintaining a history database . . . . .. 14-13 Per Table Per Data Slice Table . . . . .. 16-8
History views and tables . . . . . . . .. 14-14 Query Table . . . . . . . . . . .. 16-8
$v_hist_column_access_stats . . . . . .. 14-15 Query History Table . . . . . . . . .. 16-9
$v_hist_incomplete_queries . . . . . .. 14-16 SPU Partition Table . . . . . . . . .. 16-10
$v_hist_log_events . . . . . . . . .. 14-17 SPU Table . . . . . . . . . . . .. 16-10
$v_hist_queries, $v_hist_successful_queries, System Group . . . . . . . . . .. 16-10
and $v_hist_unsuccessful_queries . . . .. 14-17 Table Table . . . . . . . . . . .. 16-11
$v_hist_table_access_stats. . . . . . .. 14-18 System statistics . . . . . . . . . . .. 16-12
$hist_column_access_n. . . . . . . .. 14-19 The nzstats command . . . . . . . .. 16-12
$hist_failed_authentication_n . . . . .. 14-20 Display table types and fields . . . . .. 16-12
$hist_log_entry_n . . . . . . . . .. 14-21 Display a specific table . . . . . . .. 16-12
$hist_nps_n . . . . . . . . . . .. 14-21
$hist_plan_epilog_n. . . . . . . . .. 14-22 Chapter 17. System Health Check
$hist_plan_prolog_n . . . . . . . .. 14-22 tool . . . . . . . . . . . . . .. 17-1
$hist_query_epilog_n . . . . . . . .. 14-23
Tool versioning . . . . . . . . . . .. 17-1
$hist_query_overflow_n . . . . . . .. 14-25
Policy rules . . . . . . . . . . . . .. 17-2
$hist_query_prolog_n . . . . . . . .. 14-25
Daemon modes . . . . . . . . . . .. 17-3
$hist_service_n . . . . . . . . . .. 14-27
Using the health check tool . . . . . . .. 17-4
$hist_session_epilog_n . . . . . . . .. 14-27
Running and analyzing the health check report 17-4
$hist_session_prolog_n . . . . . . .. 14-28
Enabling automatic notifications . . . . .. 17-5
$hist_state_change_n . . . . . . . .. 14-29
Integration with the callhome service . . .. 17-7
$hist_table_access_n . . . . . . . .. 14-30
Running the sysinfo report . . . . . .. 17-7
$hist_version . . . . . . . . . . .. 14-31
Managing the monitoring daemon . . . .. 17-9
History table helper functions . . . . . .. 14-31
The nzhealthcheck command . . . . . . .. 17-9
Chapter 15. Workload management 15-1 Appendix A. Netezza CLI . . . . .. A-1

WLM techniques . . . . . . . . . . .. 15-1
Summary of command-line commands . . . .. A-1
Scheduler rules . . . . . . . . . . .. 15-2
Command privileges . . . . . . . . .. A-3
Scheduler rules tasks . . . . . . . .. 15-7
Commands without special privileges . . .. A-4
Guaranteed resource allocation (GRA) . . . .. 15-8
Exit codes . . . . . . . . . . . .. A-4
Resource minimums and maximums . . .. 15-10
Netezza CLI command syntax. . . . . . .. A-4
Resource group example . . . . . . .. 15-11
The nzbackup command . . . . . . . .. A-4
Guaranteed resource allocation example . .. 15-13
The nzcallhome command . . . . . . . .. A-4
Allocations for several plans associated with
The nzconfigcrypto command . . . . . .. A-8
the same group . . . . . . . . . .. 15-14
The nzcontents command . . . . . . . .. A-9
Configuring limits for resource groups . .. 15-15
The nzconvert command . . . . . . . .. A-10
Resource allocations for the admin user . .. 15-15
The nzds command . . . . . . . . . .. A-10
Disabling, enabling, and configuring GRA 15-16
The nzevent command . . . . . . . . .. A-14
GRA compliance. . . . . . . . . .. 15-16
The nzhealthcheck command. . . . . . .. A-18
Monitoring resource utilization and
The nzhistcleanupdb command . . . . . .. A-19
compliance . . . . . . . . . . .. 15-17
The nzhistcreatedb command . . . . . .. A-21
Resource group assignments. . . . . .. 15-21
The nzhostbackup command . . . . . . .. A-24
Short query bias (SQB) . . . . . . . .. 15-22
The nzhostrestore command . . . . . . .. A-26
Priority query execution (PQE) . . . . . .. 15-24
The nzhw command . . . . . . . . .. A-28
Priority levels . . . . . . . . . .. 15-25
The nzkey command . . . . . . . . .. A-34
Priority weighting and resource allocation 15-25
The nzkeydb command . . . . . . . .. A-37
Specifying priorities . . . . . . . .. 15-26
The nzkeybackup command . . . . . . .. A-39
Changing the priority of all jobs in a session 15-29
The nzkeyrestore command . . . . . . .. A-40
The nzkmip command . . . . . . . . .. A-40
Chapter 16. Netezza statistics . . .. 16-1 The nzload command . . . . . . . . .. A-42
Netezza stats tables . . . . . . . . . .. 16-1 The nznpssysrevs command . . . . . . .. A-42
Database Table. . . . . . . . . . .. 16-2 The nzpassword command . . . . . . .. A-43
Contents vii
The nzreclaim command . . . . . . . .. A-45 Host name and IP address changes . . . .. B-4
The nzrestore command . . . . . . . .. A-47 Rebooting the system . . . . . . . . .. B-4
The nzrev command . . . . . . . . .. A-47 Reformat the host disks . . . . . . . .. B-5
The nzsession command . . . . . . . .. A-49 Fix system errors . . . . . . . . . .. B-5
The nzspupart command . . . . . . . .. A-54 View system processes . . . . . . . .. B-5
The nzstart command . . . . . . . . .. A-56 Stop errant processes . . . . . . . . .. B-5
The nzstate command . . . . . . . . .. A-58 Change the system time . . . . . . . .. B-6
The nzstats command . . . . . . . . .. A-60 Determine the kernel release level . . . .. B-6
The nzstop command . . . . . . . . .. A-63 Linux system administration . . . . . . .. B-6
The nzsystem command . . . . . . . .. A-65 Display directories. . . . . . . . . .. B-7
The nzzonemapformat command . . . . .. A-68 Find files . . . . . . . . . . . . .. B-7
Customer service troubleshooting commands A-69 Display file content . . . . . . . . .. B-7
The nzconvertsyscase command. . . . .. A-70 Find Netezza hardware . . . . . . . .. B-7
The nzdumpschema command . . . . .. A-71 Time command execution . . . . . . .. B-8
The nzinitsystem command . . . . . .. A-73 Set default command line editing . . . . .. B-8
The nzlogmerge command . . . . . .. A-73 Miscellaneous commands . . . . . . .. B-8
Appendix B. Linux host administration Appendix C. Netezza user and system

reference . . . . . . . . . . . .. B-1 views . . . . . . . . . . . . . .. C-1
Linux accounts . . . . . . . . . . . .. B-1 User views . . . . . . . . . . . . .. C-1
Set up Linux user accounts . . . . . . .. B-1 System views . . . . . . . . . . . .. C-2
Modify Linux user accounts . . . . . .. B-2
Delete Linux user accounts . . . . . . .. B-2 Notices . . . . . . . . . . . . .. D-1
Change Linux account passwords . . . .. B-2 Trademarks . . . . . . . . . . . . .. D-3
Linux groups . . . . . . . . . . . .. B-3 Terms and conditions for product documentation D-3
Add Linux groups. . . . . . . . . .. B-3
Modify Linux groups . . . . . . . . .. B-4
Index . . . . . . . . . . . . . .. X-1
Delete Linux groups . . . . . . . . .. B-4
Linux Host system . . . . . . . . . .. B-4
viii IBM Netezza System Administrator’s Guide

Figures
3-1. NzAdmin main system window 3-14 5-12. IBM Netezza 1000-3 and IBM PureData
3-2. NzAdmin hyperlink support . . . .. 3-15 System for Analytics N1001-002 PDUs and
5-1. Sample nzhw show output . . . . .. 5-3 circuit breakers . . . . . . . . .. 5-34
5-2. Sample nzhw show output for Netezza 8-1. Alerts Window . . . . . . . . .. 8-37
C1000 . . . . . . . . . . . .. 5-4 12-1. Record Distribution window . . . .. 12-9
5-3. IBM PureData System for Analytics N200x 12-2. Table Skew window . . . . . . .. 12-12
system components and locations . . .. 5-6 12-3. Organizing tables with CBTs . . . .. 12-13
5-4. IBM Netezza system components and 13-1. Database backups timeline . . . . .. 13-18
locations . . . . . . . . . . .. 5-7 15-1. GRA usage sharing . . . . . . .. 15-13
5-5. IBM PureData System for Analytics 15-2. Several plans in a group share the group's
N3001-001 components and locations . .. 5-8 resources. . . . . . . . . . .. 15-14
5-6. SPUs, disks, data slices, and data partitions 5-13 15-3. Effects of the admin user on GRA 15-16
5-7. Netezza C1000 SPU and storage 15-4. Resource Allocation Performance window 15-19
representation . . . . . . . . .. 5-14 15-5. Resource Allocation Performance History
5-8. Model N3001-001 storage architecture window . . . . . . . . . . .. 15-20
overview . . . . . . . . . . .. 5-16 15-6. Resource Allocation Performance graph 15-21
5-9. Model N3001-001 storage architecture 15-7. SQB queuing and priority . . . . .. 15-24
overview in one-host mode . . . . .. 5-17 15-8. GRA and priority . . . . . . . .. 15-26
5-10. Balanced and unbalanced disk topologies 5-18
5-11. IBM Netezza 1000-6 and N1001-005 and
larger PDUs and circuit breakers . . .. 5-33
© Copyright IBM Corp. 2001, 2015 ix

x IBM Netezza System Administrator’s Guide
Tables
2-1. Netezza supported platforms. . . . .. 2-1 8-24. TransactionLimitEvent rule . . . . .. 8-34
2-2. Environment variables . . . . . . .. 2-8 9-1. IBM Support servers for call home PMR
2-3. Netezza port numbers for database access 2-10 access . . . . . . . . . . . .. 9-8
3-1. Command summary . . . . . . .. 3-1 9-2. Callhome event rules . . . . . . .. 9-12
3-2. nzsql command parameters . . . . .. 3-5 9-3. Callhome event conditions and severities 9-13
3-3. The nzsql slash commands . . . . .. 3-10 10-1. Troubleshooting nzstart errors . . . .. 10-7
3-4. Status indicators . . . . . . . .. 3-15 11-1. Administrator privileges . . . . .. 11-10
3-5. Automatic refresh . . . . . . . .. 3-17 11-2. Object privileges . . . . . . . .. 11-11
4-1. HA tasks and commands (Old design and 11-3. Slash commands to display privileges 11-14
new design) . . . . . . . . . .. 4-2 11-4. Privileges by object . . . . . . .. 11-15
4-2. Cluster management scripts . . . . .. 4-4 11-5. Indirect object privileges . . . . .. 11-17
4-3. HA IP addresses . . . . . . . .. 4-15 11-6. Netezza supported platforms for Kerberos
5-1. Key Netezza hardware components to authentication . . . . . . . . .. 11-23
monitor . . . . . . . . . . . .. 5-1 11-7. Authentication-related commands 11-27
5-2. Hardware description types . . . . .. 5-4 11-8. Client connection-related commands 11-34
5-3. Hardware roles . . . . . . . . .. 5-8 11-9. User and group settings . . . . . .. 11-34
5-4. Hardware states. . . . . . . . .. 5-10 11-10. Public views . . . . . . . . .. 11-40
5-5. Data slice status . . . . . . . . .. 5-27 11-11. System views . . . . . . . . .. 11-41
5-6. System states and transactions . . . .. 5-31 12-1. Data type disk usage . . . . . . .. 12-4
6-1. nzkey check output samples . . . .. 6-10 12-2. Table skew . . . . . . . . . .. 12-11
7-1. Netezza software revision numbering 7-2 12-3. Database information . . . . . .. 12-15
7-2. Common system states . . . . . . .. 7-3 12-4. Generate statistics syntax . . . . .. 12-16
7-3. System states reference . . . . . . .. 7-4 12-5. Automatic Statistics . . . . . . .. 12-17
7-4. Netezza processes . . . . . . . .. 7-8 12-6. The cbts_needing_groom input options 12-22
7-5. Error categories . . . . . . . . .. 7-11 12-7. The 64th read/write transaction queueing 12-27
7-6. Configuration settings for short query bias 12-8. The _v_qrystat view . . . . . . .. 12-30
(SQB) . . . . . . . . . . . .. 7-19 12-9. The _v_qryhist view . . . . . . .. 12-31
7-7. Configuration settings for the updating 13-1. Choose a backup and restore method 13-1
virtual tables . . . . . . . . . .. 7-20 13-2. Backup and restore commands and content 13-2
7-8. Configuration settings for plan history 7-20 13-3. Retaining specials . . . . . . . .. 13-6
7-9. Configuration settings for downtime event 13-4. nzbackup command parameters 13-12
logging. . . . . . . . . . . .. 7-20 13-5. Environment settings. . . . . . .. 13-14
7-10. Configuration settings for backup 7-21 13-6. Backup history source . . . . . .. 13-20
8-1. Template event rules . . . . . . .. 8-1 13-7. Backup and Restore Behavior 13-21
8-2. Netezza template event rules . . . . .. 8-3 13-8. The nzrestore command options 13-23
8-3. Event types . . . . . . . . . .. 8-7 13-9. Environment settings. . . . . . .. 13-27
8-4. Event argument expression syntax 8-12 13-10. Backup history target . . . . . .. 13-32
8-5. Notification substitution tags . . . .. 8-13 13-11. Restore history source . . . . . .. 13-34
8-6. Notification syntax . . . . . . . .. 8-13 13-12. NetBackup policy settings . . . . .. 13-35
8-7. System state changes . . . . . . .. 8-18 14-1. History loading settings . . . . . .. 14-8
8-8. HardwareServiceRequested event rule 8-19 14-2. $v_hist_column_access_stats . . . .. 14-15
8-9. HardwareNeedsAttention event rule 8-20 14-3. $v_hist_incomplete_queries . . . .. 14-16
8-10. HardwarePathDown event rule 8-21 14-4. $v_hist_log_events . . . . . . .. 14-17
8-11. HardwareRestarted event rule . . . .. 8-22 14-5. $v_hist_queries,
8-12. DiskSpace event rules . . . . . . .. 8-23 $v_hist_successful_queries, and
8-13. Threshold and states . . . . . . .. 8-23 $v_hist_unsuccessful_queries . . . .. 14-17
8-14. RunAwayQuery event rule . . . . .. 8-25 14-6. $v_hist_table_access_stats View 14-19
8-15. SCSIPredictiveFailure event rule 8-26 14-7. $hist_column_access_n . . . . . .. 14-19
8-16. RegenFault event rule . . . . . . .. 8-27 14-8. $hist_failed_authentication_n 14-20
8-17. SCSIDiskError event rule . . . . . .. 8-27 14-9. $hist_log_entry_2 . . . . . . . .. 14-21
8-18. ThermalFault event rule . . . . . .. 8-29 14-10. $hist_nps_n . . . . . . . . . .. 14-21
8-19. SysHeatThreshold event rule . . . .. 8-29 14-11. $hist_plan_epilog_n . . . . . . .. 14-22
8-20. The histCaptureEvent rule . . . . .. 8-30 14-12. $hist_plan_prolog_n . . . . . . .. 14-23
8-21. The histLoadEvent rule . . . . . .. 8-31 14-13. $hist_query_epilog_n. . . . . . .. 14-24
8-22. The spuCore event rule . . . . . .. 8-33 14-14. $hist_query_overflow_n . . . . . .. 14-25
8-23. VoltageFault event rule . . . . . .. 8-33 14-15. $hist_query_prolog_n . . . . . .. 14-25
© Copyright IBM Corp. 2001, 2015 xi

14-16. $hist_service_n . . . . . . . . .. 14-27 A-11. The nzhistcreatedb input options A-21
14-17. $hist_session_epilog_n . . . . . .. 14-28 A-12. The nzhistcreatedb output messages A-23
14-18. $hist_session_prolog_n . . . . . .. 14-28 A-13. The nzhostbackup input options A-25
14-19. $hist_state_change_n . . . . . . .. 14-30 A-14. The nzhostrestore input options A-27
14-20. $hist_table_access_n . . . . . . .. 14-30 A-15. The nzhostrestore options . . . . .. A-27
14-21. $hist_version . . . . . . . . .. 14-31 A-16. The nzhw input options . . . . . .. A-29
15-1. Workload management feature summary 15-1 A-17. The nzhw options . . . . . . . .. A-32
15-2. Assign resources to active resource groups 15-11 A-18. The nzkey input options . . . . . .. A-35
15-3. Example of resource groups . . . .. 15-12 A-19. The nzkey input options . . . . . .. A-36
15-4. Example of a distribution of resources A-20. The nzkeydb input options . . . . .. A-37
within resource groups . . . . . .. 15-26 A-21. The nzkeydb input options . . . . .. A-38
16-1. Netezza Groups and Tables . . . . .. 16-1 A-22. The nzkeybackup input options A-39
16-2. Database Table . . . . . . . . .. 16-2 A-23. The nzkeyrestore input options A-40
16-3. DBMS Group. . . . . . . . . .. 16-2 A-24. The nzkmip input options . . . . .. A-41
16-4. Host CPU Table . . . . . . . . .. 16-3 A-25. The nzkmip input options . . . . .. A-41
16-5. Host File System Table . . . . . .. 16-3 A-26. The nzpassword input options A-43
16-6. Host Interfaces Table . . . . . . .. 16-4 A-27. The nzpassword options. . . . . .. A-44
16-7. Host Management Channel Table 16-5 A-28. The nzreclaim input options . . . .. A-45
16-8. Host Network Table . . . . . . .. 16-5 A-29. The nzreclaim options . . . . . .. A-46
16-9. Host Table . . . . . . . . . .. 16-6 A-30. The nzrev input options . . . . . .. A-48
16-10. Hardware Management Channel Table 16-7 A-31. The nzsession input options . . . .. A-49
16-11. Per Table Data Slice Table . . . . .. 16-8 A-32. The nzsession options . . . . . .. A-50
16-12. Query Table . . . . . . . . . .. 16-8 A-33. Session information . . . . . . .. A-52
16-13. Query History Table . . . . . . .. 16-9 A-34. The nzspupart input options . . . .. A-54
16-14. SPU Partition Table . . . . . . .. 16-10 A-35. The nzspupart options . . . . . .. A-54
16-15. SPU Table . . . . . . . . . .. 16-10 A-36. The nzstart inputs . . . . . . . .. A-57
16-16. System Group . . . . . . . . .. 16-11 A-37. The nzstate inputs . . . . . . . .. A-58
16-17. Table Table . . . . . . . . . .. 16-11 A-38. The nzstate options . . . . . . .. A-58
17-1. Health check tool versions and the A-39. The nzstats inputs . . . . . . . .. A-60
corresponding supported NPS versions .. 17-1 A-40. The nzstats options . . . . . . .. A-61
17-2. The nzhealthcheck input options 17-9 A-41. The nzstop inputs . . . . . . . .. A-64
A-1. Command-line summary . . . . . .. A-1 A-42. The nzstop options . . . . . . .. A-64
A-2. The nzcallhome input options . . . .. A-5 A-43. The nzsystem inputs . . . . . . .. A-65
A-3. The nzconfigcrypto input options A-8 A-44. The nzsystem options . . . . . .. A-65
A-4. The nzconfigcrypto input options A-9 A-45. The nzzonemapformat input options A-68
A-5. The nzds input options . . . . . .. A-11 A-46. Diagnostic commands . . . . . .. A-69
A-6. The nzds options . . . . . . . .. A-12 A-47. The nzconvertsyscase input options A-71
A-7. The nzevent input options . . . . .. A-14 A-48. The nzdumpschema inputs . . . . .. A-72
A-8. The nzevent options . . . . . . .. A-15 A-49. The nzlogmerge options . . . . . .. A-73
A-9. The nzhealthcheck input options A-18 C-1. User views. . . . . . . . . . .. C-1
A-10. The nzhistcleanupdb input options A-20 C-2. System views . . . . . . . . . .. C-2
xii IBM Netezza System Administrator’s Guide

Electronic emission notices
When you attach a monitor to the equipment, you must use the designated
monitor cable and any interference suppression devices that are supplied with the
monitor.
Federal Communications Commission (FCC) Statement
This equipment was tested and found to comply with the limits for a Class A
digital device, according 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 generates, uses, and can
radiate radio frequency energy and, if not installed and used in accordance with
the instruction manual, might cause harmful interference to radio communications.
Operation of this equipment in a residential area is likely to cause harmful
interference, in which case the user is required to correct the interference at their
own expense.
Properly shielded and grounded cables and connectors must be used to meet FCC
emission limits. IBM® is not responsible for any radio or television interference
caused by using other than recommended cables and connectors or by
unauthorized changes or modifications to this equipment. Unauthorized changes
or modifications might void the authority of the user to operate the equipment.
This device complies with Part 15 of the FCC Rules. Operation is subject to the
following two conditions: (1) this device might not cause harmful interference, and
(2) this device must accept any interference received, including interference that
might cause undesired operation.
Industry Canada Class A Emission Compliance Statement
This Class A digital apparatus complies with Canadian ICES-003.
Avis de conformité à la réglementation d'Industrie Canada
Cet appareil numérique de la classe A est conforme à la norme NMB-003 du

Canada.
Australia and New Zealand Class A Statement
This product is a Class A product. In a domestic environment, this product might

cause radio interference in which case the user might be required to take adequate
measures.
European Union EMC Directive Conformance Statement
This product is in conformity with the protection requirements of EU Council

Directive 2004/108/EC on the approximation of the laws of the Member States
relating to electromagnetic compatibility. IBM cannot accept responsibility for any
failure to satisfy the protection requirements resulting from a nonrecommended
modification of the product, including the fitting of non-IBM option cards.
© Copyright IBM Corp. 2001, 2015 xiii

This product is an EN 55022 Class A product. In a domestic environment, this
product might cause radio interference in which case the user might be required to
take adequate measures.
Responsible manufacturer:
International Business Machines Corp.

New Orchard Road
Armonk, New York 10504
914-499-1900
European Community contact:
IBM Technical Regulations, Department M456

IBM-Allee 1, 71137 Ehningen, Germany
Telephone: +49 7032 15-2937
Email: tjahn@de.ibm.com
Germany Class A Statement
Deutschsprachiger EU Hinweis: Hinweis für Geräte der Klasse A EU-Richtlinie

zur Elektromagnetischen Verträglichkeit
Dieses Produkt entspricht den Schutzanforderungen der EU-Richtlinie

2004/108/EG zur Angleichung der Rechtsvorschriften über die elektromagnetische
Verträglichkeit in den EUMitgliedsstaaten und hält die Grenzwerte der EN 55022
Klasse A ein.
Um dieses sicherzustellen, sind die Geräte wie in den Handbüchern beschrieben zu

installieren und zu betreiben. Des Weiteren dürfen auch nur von der IBM
empfohlene Kabel angeschlossen werden. IBM übernimmt keine Verantwortung für
die Einhaltung der Schutzanforderungen, wenn das Produkt ohne Zustimmung der
IBM verändert bzw. wenn Erweiterungskomponenten von Fremdherstellern ohne
Empfehlung der IBM gesteckt/eingebaut werden.
EN 55022 Klasse A Geräte müssen mit folgendem Warnhinweis versehen werden:

“Warnung: Dieses ist eine Einrichtung der Klasse A. Diese Einrichtung kann im
Wohnbereich Funk-Störungen verursachen; in diesem Fall kann vom Betreiber
verlangt werden, angemessene Maßnahmen zu ergreifen und dafür
aufzukommen.”
Deutschland: Einhaltung des Gesetzes über die

elektromagnetische Verträglichkeit von Geräten
Dieses Produkt entspricht dem “Gesetz über die elektromagnetische Verträglichkeit

von Geräten (EMVG)”. Dies ist die Umsetzung der EU-Richtlinie 2004/108/EG in
der Bundesrepublik Deutschland.
Zulassungsbescheinigung laut dem Deutschen Gesetz über die

elektromagnetische Verträglichkeit von Geräten (EMVG) (bzw. der
EMC EG Richtlinie 2004/108/EG) für Geräte der Klasse A
Dieses Gerät ist berechtigt, in Übereinstimmung mit dem Deutschen EMVG das
EG-Konformitätszeichen - CE - zu führen.
Verantwortlich für die Einhaltung der EMV Vorschriften ist der Hersteller:
xiv IBM Netezza System Administrator’s Guide

International Business Machines Corp.
New Orchard Road
Armonk, New York 10504
914-499-1900
Der verantwortliche Ansprechpartner des Herstellers in der EU ist:
IBM Deutschland
Technical Regulations, Department M456
IBM-Allee 1, 71137 Ehningen, Germany
Telephone: +49 7032 15-2937
Email: tjahn@de.ibm.com
Generelle Informationen: Das Gerät erfüllt die Schutzanforderungen nach EN 55024

und EN 55022 Klasse A.
Japan VCCI Class A Statement
This product is a Class A product based on the standard of the Voluntary Control
Council for Interference (VCCI). If this equipment is used in a domestic
environment, radio interference might occur, in which case the user might be
required to take corrective actions.
Japan Electronics and Information Technology Industries

Association (JEITA) Statement
Japan Electronics and Information Technology Industries Association (JEITA)

Confirmed Harmonics Guidelines (products less than or equal to 20 A per phase)
Japan Electronics and Information Technology Industries

Association (JEITA) Statement
Japan Electronics and Information Technology Industries Association (JEITA)

Confirmed Harmonics Guidelines (products greater than 20 A per phase)
Electronic emission notices xv

Korea Communications Commission (KCC) Statement
This is electromagnetic wave compatibility equipment for business (Type A). Sellers
and users need to pay attention to it. This is for any areas other than home.
Russia Electromagnetic Interference (EMI) Class A Statement
People's Republic of China Class A Electronic Emission

Statement
Taiwan Class A Compliance Statement
xvi IBM Netezza System Administrator’s Guide

Regulatory and compliance
Regulatory Notices
Install the NPS® system in a restricted-access location. Ensure that only those
people 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 circuit breakers on all power sources.
The IBM PureData® System for Analytics appliance requires a readily accessible
power cutoff. This can be a Unit Emergency Power Off Switch (UEPO), a circuit
breaker or completely remove power from the equipment by disconnecting the
Appliance Coupler (line cord) from all rack PDUs.
CAUTION:
Disconnecting power from the appliance without first stopping the NPS
software and high availability processes might result in data loss and increased
service time to restart the appliance. For all non-emergency situations, follow the
documented power-down procedures in the IBM Netezza System Administrator’s
Guide to ensure that the software and databases are stopped correctly, in order, to
avoid data loss or file corruption.
Product might 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 raccordement au
réseau.
Homologation Statement
This product may not be certified in your country for connection by any means
whatsoever to interfaces of public telecommunications networks. Further
certification may be required by law prior to making any such connection. Contact
an IBM representative or reseller for any questions.
© Copyright IBM Corp. 2001, 2015 xvii

xviii IBM Netezza System Administrator’s Guide
About this publication
The IBM Netezza® data warehouse appliance is a high performance, integrated
database appliance that provides unparalleled performance, extensive scaling, high
reliability, and ease of use. The Netezza appliance uses a unique architecture that
combines current trends in processor, network, and software technologies to
deliver a high performance system for large enterprise customers.
These topics are written for system administrators and database administrators. In
some customer environments, these roles can be the responsibility of one person or
several administrators.
You should be familiar with Netezza concepts and user interfaces, as described in
the IBM Netezza Getting Started Tips. Be comfortable with using command-line
interfaces, Linux operating system utilities, windows-based administration
interfaces, and installing software on client systems to access the Netezza
appliance.
If you need help

If you are having trouble using the IBM Netezza appliance, follow these steps:
1. Try the action again, carefully following the instructions for that task in the
documentation.
2. Go to the IBM Support Portal at: http://www.ibm.com/support. Log in using
your IBM ID and password. You can search the Support Portal for solutions. To
submit a support request, click the Service Requests & PMRs tab.
3. If you have an active service contract maintenance agreement with IBM, you
can contact customer support teams by telephone. For individual countries,
visit the Technical Support section of the IBM Directory of worldwide contacts
(http://www.ibm.com/support/customercare/sas/f/handbook/contacts.html).
How to send your comments

You are encouraged to send any questions, comments, or suggestions about the
IBM Netezza documentation. Send an email to netezza-doc@wwpdl.vnet.ibm.com
and include the following information:
v The name and version of the manual that you are using
v Any comments that you have about the manual
v Your name, address, and phone number
We appreciate your suggestions.
© Copyright IBM Corp. 2001, 2015 xix

xx IBM Netezza System Administrator’s Guide
Chapter 1. Administration overview
This section provides an introduction and overview to the tasks involved in
administering an IBM Netezza data warehouse appliance.
Administrator’s roles
IBM Netezza administration tasks typically fall into two categories:
System administration
Managing the hardware, configuration settings, system status, access, disk
space, usage, upgrades, and other tasks
Database administration
Managing the user databases and their content, loading data, backing up
data, restoring data, controlling access to data and permissions
In some customer environments, one person can be both the system and database
administrator to do the tasks when needed. In other environments, multiple people
might share these responsibilities, or they might own specific tasks or
responsibilities. You can develop the administrative model that works best for your
environment.
In addition to the administrator roles, there are also database user roles. A database
user is someone who has access to one or more databases and has permission to
run queries on the data that is stored within those databases. In general, database
users have access permissions to one or more user databases, or to one or more
schemas within databases, and they have permission to do certain types of tasks
and to create or manage certain types of objects within those databases.
Administration tasks
The administration tasks generally fall into these categories:
v Service level planning
v Deploying and installing Netezza clients
v Managing a Netezza system
v Managing system notifications and events
v Managing Netezza users and groups
v Managing databases
v Loading data (described in the IBM Netezza Data Loading Guide)
v Backing up and restoring databases
v Collecting and evaluating history data
v Workload management
Initial system setup and information

A factory-configured and installed IBM Netezza system includes the following
components:
v A Netezza data warehouse appliance with preinstalled Netezza software
© Copyright IBM Corp. 2001, 2015 1-1

v A preconfigured Linux operating system (with Netezza modifications) on one or
both system hosts. Netezza high-availability (HA) models have two hosts, while
non-HA models have one host.
v Several preconfigured Linux users and groups, which must not be modified or
deleted.
– The nz user is the default Netezza system administrator account. The Linux
user is named nz with a default password of nz. The Netezza software runs
as this user, and you can access the system by using a command shell or
remote access software as the nz user.
– Netezza HA systems also require a Linux user (hacluster) and two Linux
groups (hacluster and haclient) that are added automatically to the host
during the Heartbeat RPM installation.
v A Netezza database user named admin (with a default password of password).
The admin user is the database super-user, and has full access to all system
functions and objects. You cannot delete the admin user. You use the admin
account to start creating user databases and other database user groups and
accounts to which you can assign appropriate permissions and access.
v A preconfigured database group named public. All database users are
automatically placed in the group public and therefore inherit all of its
privileges. The group public has default access privileges to selected system
views, such as lists of available databases, tables, and views. You cannot delete
the group public.
Netezza Support and Sales representatives work with you to install and initially
configure the Netezza in your customer environment. Typically, the initial rollout
consists of installing the system in your data center, and then configuring the
system host name and IP address to connect the system to your network and make
it accessible to users. They also work with you to do initial studies of the system
usage and query performance, and might advocate other configuration settings or
administration ideas to improve the performance of and access to the Netezza for
your users.
Related concepts:
“Linux users and groups required for HA” on page 4-17
Netezza software directories

The IBM Netezza software is installed in several directories on the Netezza host as
follows:
v The /nz directory is the Netezza host software installation directory.
v The /export/home/nz directory is a home directory for the nz user.
v The Linux operating system boot directories.
Host software directory

The IBM Netezza host installation directory contains the following software
directories and files.
/nz The root of the Netezza software installation tree. On a production host,
the default software installation directory is /nz. If you are a Linux user
that is connected to the Netezza host, include /nz/kit/bin and
/nz/kit/bin/adm in your PATH.
/nz/data->
A link to the current data directory.
1-2 IBM Netezza System Administrator’s Guide

/nz/kit->
A link to the current kit of executable files. The kit link points to the
current software revision in use.
/nz/data.<ver>/
System catalog and other host-side database files.
/nz/kit.<rev>/
The set of optimized executable files and support files that are needed to
run the product. The <rev> represents the revision of the software.
/nz/tmp/
Netezza temporary files.
/nzscratch
A location for Netezza internal files. This location is not mirrored. The
/nzscratch/tmp directory is the default temporary files directory, which is
specified by the NZ_TMP_DIR variable. It holds files that are created and
used by the transaction manager and other processes. The contents of
NZ_TMP_DIR are deleted when the Netezza software starts and when the
Netezza system restarts. Do not store large files in /nzscratch or its
subdirectories; if /nzscratch runs out of space, Netezza processes can fail.
The /nz directory
The /nz directory is the top-level directory that contains the Netezza software
installation kits, data, and important information for the system and database. As a
best practice, use caution when you are viewing files in this directory or its
subfolders because unintended changes can impact the operation of the Netezza
system or cause data loss. Never delete or modify files or folders in the /nz
directory unless directed to do so by Netezza Support or an IBM representative.
Do not store large files, unrelated files, or backups in the /nz directory.
The system manager monitors the size of the /nz directory. If the /nz directory
reaches a configured usage percentage, the system manager stops the Netezza
software and logs a message in the sysmgr.log file. The default threshold is 95%,
which is specified by the value of the
sysmgr.hostFileSystemUsageThresholdToStopSystem registry setting. Do not
change the value of the registry setting unless directed to do so by Netezza
Support.
A sample sysmgr.log file message for a case where the /nz directory has reached
the configured 95% capacity threshold follows.
Error: File system /nz usage exceeded 95 threshold on rack1.host1 System will
be stopped
If the Netezza software stops and this message is in the sysmgr.log file, contact
Netezza Support for assistance to carefully review the contents of the /nz directory
and to delete appropriate files. When the /nz directory usage falls below the
configured threshold, you can start the Netezza software.
The data directory
The /nz/data directory contains the following subdirectories:

data.<ver>/base
Contains system tables, catalog information, and subdirectories for the
databases. Each database that you create has its own subdirectory whose
Chapter 1. Administration overview 1-3

name matches the database object ID value. For example, base/1/ is the
system database, base/2/ is the master_db database, and base/nnn is a user
database, where nnn is the object ID of the database.
data.<ver>/cache
Contains copies of compiled code that were dynamically generated on the
host, cross-compiled to run on the SPUs, then downloaded to the SPUs for
execution. The copies are saved to eliminate extra steps and duplicate
work for similar queries.
data.<ver>/config
Contains configuration files such as:
callHome.txt
The callhome attachment file.
sendMail.cfg
A file that contains the configuration parameters for the sendmail
program.
system.cfg
The system configuration file, which contains settings that control
the system.
If the Netezza system uses options such as LDAP or Kerberos

authentication or other applications, this directory might also contain
additional files.
data.<ver>/plans
Contains copies of the most recent execution plans for reference. The
system stores the execution plan (for each query) in a separate file with a
.pln extension, and includes the following information:
v The original SQL that was submitted.
v The plan itself, describing how the various tables and columns are to be
accessed, when joins, sorts, and aggregations are performed, and other
processes.
v If the system was able to reuse a cached (already compiled) version of
the code.
The system also generates a separate C program (.cpp file) to process
each snippet of each plan. The system compares this code against files in
/nz/data/cache to determine whether the compilation step can be
skipped.
The kit directory
The kit directory contains the following subdirectories:

kit.<rev>/
Top-level directory for the release <rev> (for example, kit.6.0).
kit.<rev>/bin/
All user-level CLI programs.
kit.<rev>/bin/adm
Internal CLI programs.
kit.<rev>/log/<pgm name>/
Component log files, one subdirectory per component that contains a file

per day of log information up to seven days. The information in the logs
includes when the process started, when the process exited or completed,
and any error conditions.
kit.<rev>/ sbin
Internal host and utility programs that are not intended to be run directly
by users. These programs are not prefixed (for example, clientmgr).
kit.<rev>/share/
Postgres-specific files.
kit.<rev>/sys/
System configuration files, startup.cfg, and some subdirectories (init,
include, strings).
kit.<rev>/sys/init/
Files that are used for system initialization.
nz user home directory

The host software runs under a preconfigured Linux user named nz. The home
directory for the nz user is /export/home/nz. The default shell configuration file, in
addition to standard UNIX specifications, adds /nz/kit/bin to the PATH
environment variable so that user nz can automatically locate CLI commands.
Linux boot directories

To ensure that the system starts the IBM Netezza software when it boots, Netezza
places some entries in the init.d directory, which is a standard system facility for
starting applications. Never modify the Linux operating system boot directories or
files unless you are directed to by Netezza Support or documented Netezza
procedures. Changes to these files can impact the operation of the host.
External network connections

During the on-site installation of the IBM Netezza system, Netezza installation
engineers work with you to configure your system by using the site survey
information that is prepared for your environment. The initial setup process
includes steps to configure the external network connections (that is, the host name
and IP address information) of your Netezza system.
CAUTION:
If you need to change the host name or IP address information, do not use the
general Linux procedures to change this information. Contact Netezza Support
for assistance to ensure that the changes are using Netezza procedures to ensure
that the changes are propagated to the high availability configuration and
related services.
Domain Name Service (DNS) Updates

The IBM Netezza server uses a domain name service (DNS) server to provide
name resolution to devices such as S-Blades within the system. This allows SPUs to
have a DNS name (such as spu0103) and an IP address.
To change the DNS settings for your system, use the nzresolv service to manage
the DNS updates. The nzresolv service updates the resolv.conf information
stored on the Netezza host; for highly available Netezza systems, the nzresolv
service updates the information stored on both hosts. (You can log in to either host
to do the DNS updates.) You must be able to log in as the root user to update the
resolv.conf information; any Linux user such as nz can display the DNS
information by using the show option.

Note: Do not manually edit the /etc/resolv.conf* files, even as the root user. Use
the nzresolv service to update the files and to ensure that the information is
maintained correctly on the hosts.
The Netezza system manages the DNS services as needed during actions such as
host failovers from the master host to the standby host. Never manually restart the
nzresolv service unless directed to do so by Netezza Support for troubleshooting.
A restart can cause loss of contact with the localhost DNS service, and
communication issues between the host and the system hardware components. Do
not use any of the nzresolv subcommands other than update, status, or show
unless directed to do so by Netezza Support.
Displaying the DNS information

About this task
To display the current DNS information for the system, do the following steps:
Procedure
1. Log in to the active host as a Linux user such as nz.
2. Enter the following command:
[nz@nzhost1 ~]$ service nzresolv show
Example
Sample output follows:

search yourcompany.com
nameserver 1.2.3.4
nameserver 1.2.5.6
Changing DNS information

About this task
You update the DNS information by using the nzresolv service. You can change
the DNS information by using a text editor, and read the DNS information from a
file or enter it on the command line. Any changes that you make take effect
immediately (and on both hosts, for HA systems). The DNS server uses the
changes for the subsequent DNS lookup requests.
Updating DNS information with a text editor:

About this task
To change the DNS information, do the following steps:
Procedure
1. Log in to either host as root.
[root@nzhost1 ~]# service nzresolv update
Note: If you use the service command to edit the DNS information, you must
use vi as the text editor tool, as shown in these examples. However, if you
prefer to use a different text editor, you can set the $EDITOR environment
variable and use the /etc/init.d/nzresolve update command to edit the files
using by your editor of choice.
3. Review the system DNS information as shown in the sample file.

# !!! All lines starting ’# !!!’ will be removed.
# !!!
nameserver 1.2.3.4
nameserver 1.2.5.6
4. Enter, delete, or change the DNS information as required. When you are
finished, save your changes and exit (or you can exit without saving the
changes) using one of the following commands:
v :wq to save the changes.
v :q to exit the file.
v :q! to exit without saving any changes that you made in the file.
CAUTION:
Use caution before you change the DNS information; incorrect changes can
affect the operation of the IBM Netezza system. Review any changes with
the DNS administrator at your site to ensure that the changes are correct.
Overwriting DNS information with a text file:

About this task
To change the DNS information by reading the information from an existing text
file, do the following steps:
Procedure
2. Create a text file with your DNS information. Make your text file similar to the
following format:
nameserver 1.2.3.4
nameserver 1.2.5.6
3. Enter the following command, where file is the fully qualified path name to
the text file:
[root@nzhost1 ~]# service nzresolv update file
Appending DNS information from the command prompt:

About this task
To change the DNS information by entering the information from the command
prompt, do the following steps:
Procedure
2. Enter the following command (note the dash character at the end of the
command):
[root@nzhost1 ~]# service nzresolv update -
The command prompt proceeds to a new line where you can enter the DNS
information. Enter the complete DNS information because the text that you
type replaces the existing information in the resolv.conf file.
3. After you finish typing the DNS information, type one of the following
commands:
v Control-D to save the information that you entered and exit the editor.
v Control-C to exit without saving any changes.

Displaying DNS service status
You can display the status of the nzresolv service on your IBM Netezza hosts.
About this task
To display the current status of the Netezza nzresolv service, do the following
steps:
Procedure
1. Log in to the active host as a Linux user such as nz.
[nz@nzhost1 ~]$ service nzresolv status
Example

Configured for local resolv.conf
If you log in to the standby host of the Netezza system and run the command, the
status message is Configured for upstream resolv.conf.
Remote access
IBM Netezza systems are typically installed in a data center, which is often highly
secured from user access and sometimes in a geographically separate location.
Thus, you might need to set up remote access to Netezza so that your users can
connect to the system through the corporate network. Common ways to remotely
log on to another system through a shell (Telnet, rlogin, or rsh) do not encrypt data
that is sent over the connection between the client and the server. Consequently,
the type of remote access you choose depends upon the security considerations at
your site. Telnet is the least secure and SSH (Secure Shell) is the most secure.
If you allow remote access through Telnet, rlogin, or rsh, you can more easily
manage this access through the xinetd daemon (Extended Internet Services). The
xinetd daemon starts programs that provide Internet services. This daemon uses a
configuration file, /etc/xinetd.conf, to specify services to start. Use this file to
enable or disable remote access services according to the policy at your site.
If you use SSH, it does not use xinetd, but rather its own configuration files. For
more information, see the Red Hat documentation.
Administration interfaces
IBM Netezza offers several ways or interfaces that you can use to perform the
various system and database management tasks:
v Netezza commands (nz* commands) are installed in the /nz/kit/bin directory
on the Netezza host. For many of the nz* commands, you must be able to log on
to the Netezza system to access and run those commands. In most cases, users
log in as the default nz user account, but you can create other Linux user
accounts on your system. Some commands require you to specify a database
user account, password, and database to ensure that you have permissions to do
the task.
v The Netezza CLI client kits package a subset of the nz* commands that can be
run from Windows and UNIX client systems. The client commands might also

require you to specify a database user account, password, and database to
ensure that you have database administrative and object permissions to do the
task.
v The SQL commands support administration tasks and queries within a SQL
database session. You can run the SQL commands from the Netezza nzsql
command interpreter or through SQL APIs such as ODBC, JDBC, and the OLE
DB Provider. You must have a database user account to run the SQL commands
with appropriate permissions for the queries and tasks that you perform.
v The NzAdmin tool is a Netezza interface that runs on Windows client
workstations to manage Netezza systems.
v Netezza Performance Portal. The Netezza Performance Portal is a web browser
client that provides detailed monitoring capabilities for your Netezza systems.
You can use the portal to answer questions about system usage, workload,
capacity planning, and overall query performance.
The nz* commands are installed and available on the Netezza system, but it is
more common for users to install Netezza client applications on client
workstations. Netezza supports various Windows and UNIX client operating
systems. Chapter 2, “Netezza client software installation,” on page 2-1 describes
the Netezza clients and how to install them. Chapter 3, “Netezza administration
interfaces,” on page 3-1 describes how to get started by using the administration
interfaces.
The client interfaces provide you with different ways to do similar tasks. While
most users tend to use the nz* commands or SQL commands for tasks, you can
use any combination of the client interfaces, depending on the task or your
workstation environment, or interface preferences.
Related concepts:
Chapter 2, “Netezza client software installation,” on page 2-1
This section describes how to install the Netezza CLI clients and the NzAdmin
tool.
Other Netezza documentation

The IBM Netezza documentation set contains other documents that can help you
in your day-to-day use of the Netezza system and features:
v IBM Netezza Database User’s Guide describes the Netezza SQL commands and
how to use them to create queries and how to create and manage database
objects
v IBM Netezza Data Loading Guide describes how to load data into a Netezza
system
v IBM Netezza ODBC, JDBC, OLE DB, and .NET Installation and Configuration Guide
describes how to configure data connectivity clients to connect to your Netezza
system and run queries through the supported drivers
v IBM Netezza Advanced Security Administrator's Guide describes how to manage
multi-level security, audit logging and history, and authentication within the
Netezza database
v IBM Netezza Getting Started Tips provides a high-level overview of Netezza
appliances and concepts for the new user, plus an overview of the
documentation set
v IBM Netezza Software Upgrade Guide describes how to upgrade the Netezza
software

v IBM Netezza Release Notes describes new features and changes in a Netezza
software release, and a summary of known issues and fixes for
customer-reported issues
There are several Netezza documents that offer more specialized information about
features or tasks. For more information, see IBM Netezza Getting Started Tips.

Chapter 2. Netezza client software installation
This section describes how to install the Netezza CLI clients and the NzAdmin
tool.
In most cases, the only applications that IBM Netezza administrators or users must
install are the client applications to access the Netezza system. Netezza provides
client software that runs on various systems such as Windows, Linux, Solaris,
AIX®, and HP-UX systems.
The instructions to install and use the Netezza Performance Portal are in the IBM
Netezza Performance Portal User's Guide, which is available with the software kit for
that interface.
This section does not describe how to install the Netezza system software or how
to upgrade the Netezza host software. Typically, Netezza Support works with you
for any situations that might require software reinstallations, and the steps to
upgrade a Netezza system are described in the IBM Netezza Software Upgrade Guide.
If your users or their business reporting applications access the Netezza system
through ODBC, JDBC, or OLE-DB Provider APIs, see the IBM Netezza ODBC,
JDBC, OLE DB, and .NET Installation and Configuration Guide for detailed
instructions on the installation and setup of these data connectivity clients.
Related concepts:
“Administration interfaces” on page 1-8
Client software packages

If you have access to IBM Passport Advantage® or the IBM Fix Central downloads
area, you can obtain the Netezza client software. You must have support accounts
with permission to download the IBM Netezza software from these locations.
To access Passport Advantage, go to http://www.ibm.com/software/howtobuy/

passportadvantage/pao_customers.htm.
To access Fix Central, go to http://www.ibm.com/support/fixcentral.
The following table lists the supported operating systems and revisions for the
Netezza CLI clients.
Table 2-1. Netezza supported platforms
Operating system 32-bit 64-bit
Windows
Windows 2008, Vista, 7, 8 Intel / AMD Intel / AMD
Windows Server 2012, 2012 R2 N/A Intel / AMD
Linux
Red Hat Enterprise Linux 5.2, 5.3, 5.5, 5.9; and 6 Intel / AMD Intel / AMD
through 6.5
Red Hat Enterprise Linux 6.2+ N/A PowerPC®
Red Hat Enterprise Linux 7.1 N/A POWER8® LE mode

Table 2-1. Netezza supported platforms (continued)
SUSE Linux Enterprise Server 11 Intel / AMD Intel / AMD
®
SUSE Linux Enterprise Server 10 and 11, and IBM System z IBM System z
Red Hat Enterprise Linux 5.x, and Red Hat
Enterprise Hat 6.1
Ubuntu Server 15.04 Intel / AMD Intel / AMD
UNIX
IBM AIX 6.1 with 5.0.2.1 C++ runtime libraries, N/A PowerPC
7.1
HP-UX 11i versions 1.6, 2 (B.11.22 and B.11.23), Itanium Itanium
and 3
Oracle Solaris 10, 11 SPARC SPARC
Oracle Solaris 10 x86 x86
The Netezza client kits are designed to run on the proprietary hardware
architecture for the vendor. For example, the AIX, HP-UX, and Solaris clients are
intended for the proprietary RISC architecture. The Linux client is intended for
RedHat or SUSE on the 32-bit Intel architecture.
Note: Typically, the Netezza clients also support the update releases for each of the
OS versions listed in the table, unless the OS vendor introduced architecture
changes in the update.
Install the Netezza CLI client on a Linux/UNIX system

The IBM Netezza UNIX clients contain a tar file of the client software for a
platform and an unpack script. You use the unpack script to install the client nz
commands and their necessary files to the UNIX client system. “Client software
packages” on page 2-1 lists the supported UNIX client operating systems.
Installing on Linux/UNIX Clients

The topic describes how to install the IBM Netezza UNIX client packages on 32-bit
and 64-bit operating system workstations.
About this task
If you are installing the clients on 64-bit operating systems, there are some
additional steps to install a second, 64-bit client package. The IBM Netezza clients
are 32-bit operating system executables and they require 32-bit libraries that are not
provided with the clients. If the libraries are not already installed on your system,
you must obtain and install the libraries using your operating system update
process.
Procedure
1. Obtain the nz-platformclient-version.archive) client package from the IBM
Fix Central site and download it to the client system. Use or create a new,
empty directory to reduce any confusion with other files or directories. There
are several client packages available for different common operating system
types, as described in “Client software packages” on page 2-1. Make sure that

you obtain the correct client package. These instructions use the Linux client
package as an example of the procedure.
2. Log in to the workstation as the root user or a superuser account.
3. Change to the directory where you saved the client package, then uncompress
and extract the contents.
For the Linux client, use the gunzip command to uncompress the client
package, then you use a command such as tar xzf nz-linuxclient-
version.tar.gz to extract the package. To extract the other UNIX packages,
such as AIX, you might need to run other commands, such as uncompress to
uncompress the archive.The unpack process for the Linux package creates a
linux directory, a linux64 directory, a webadmin directory, and a
datadirect.package.tar.z file. Ignore the webadmin directory, which contains
the deprecated Web Admin interface client.
4. For all clients (either 32-bit or 64-bit operating system clients), change to the
linux directory and run the unpack command: ./unpack.
Note: On an HP-UX 11i client, /bin/sh might not be available. You can use the
command form sh ./unpack to unpack the client.
The unpack command checks the client system to ensure that it supports the
CLI package and prompts you for an installation location. The default is
/usr/local/nz for Linux, but you can install the CLI tools to any location on
the client. The program prompts you to create the directory if it does not
already exist. Sample command output follows:
------------------------------------------------------------------
IBM Netezza -- NPS Linux Client 7.1
(C) Copyright IBM Corp. 2002, 2013 All Rights Reserved.
------------------------------------------------------------------
Validating package checksum ... ok
Where should the NPS Linux Client be unpacked? [/usr/local/nz]
Directory ’/usr/local/nz’ does not exist; create it (y/n)? [y] Enter
0% 25% 50% 75% 100%
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Unpacking complete.
5. If your client has a 64-bit operating system, change to the linux64 directory
and run the unpack command to install the additional 64-bit files: ./unpack.
The unpack command prompts you for an installation location. The default is
/usr/local/nz for Linux, but you should use the same location that you used
for the 32-bit CLI files in the previous step. Sample command output follows:
------------------------------------------------------------------
IBM Netezza -- NPS Linux Client 7.1
(C) Copyright IBM Corp. 2002, 2013 All Rights Reserved.
------------------------------------------------------------------
Validating package checksum ... ok
Where should the NPS Linux Client be unpacked? [/usr/local/nz]
Installing in an existing directory. Changing permissions to
overwrite existing files...
0% 25% 50% 75% 100%
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Unpacking complete.
Results
The client installation steps are complete, and the Netezza CLI commands are
installed to your specified destination directory. The NPS commands are located in
the bin directory where you unpacked the NPS clients. If you are using a 64-bit
operating system on your workstation, note that there is a 64-bit nzodbcsql
command in the bin64 directory for testing the SQL command connections.
Chapter 2. Netezza client software installation 2-3

What to do next
Test to make sure that you can run the client commands. Change to the bin
subdirectory of the client installation directory (for example, /usr/local/nz/bin).
Run a sample command such as the nzds command to verify that the command
succeeds or to identify any errors.
./nzds -host nzhost -u user -pw password
The command displays a list of the data slices on the target NPS system. If the
command runs without error, your client system has the required libraries and
packages to support the Netezza clients. If the command fails with a library or
other error, the client may require some additional libraries or shared objects.
For example, on a Red Hat Enterprise Linux 64-bit client system, you could see an
error similar to the following:
[root@myrhsystem bin]# ./nzds
-bash: ./nzds: /lib/ld-linux.so.2: bad ELF interpreter: No such file or directory
For example, on a SUSE 10/11 64-bit client system, you could see an error similar
to the following:
mylinux:/usr/local/nz/bin # ./nzds
./nzds: error while loading shared libraries: libssl.so.4: cannot open shared
object file: No such file or directory
mylinux:/usr/local/nz/bin # ldd nzds

linux-gate.so.1 => (0xffffe000)
libcrypt.so.1 => /lib/libcrypt.so.1 (0xf76f1000)
libdl.so.2 => /lib/libdl.so.2 (0xf76ec000)
libssl.so.4 => not found
libcrypto.so.4 => not foundlibm.so.6 => /lib/libm.so.6 (0xf76c4000)
libc.so.6 => /lib/libc.so.6 (0xf7582000)
/lib/ld-linux.so.2 (0xf773f000)
These errors indicate that the client is missing 32-bit library files that are required
to run the NPS clients. Identify the packages that provide the library and obtain
those packages. You may need assistance from your local workstation IT
administrators to obtain the operating system packages for your workstation.
To identify and obtain the required Red Hat packages, you could use a process
similar to the following.
v Use the yum provides command and specify the file name to see which package
provides the file that could not be found (ld-linux.so.2 in this example).
yum provides ld-linux.so.2
Loaded plugins: product-id, refresh-packagekit, security, subscription-manager
This system is not registered to Red Hat Subscription Management. You can use
subscription-manager to register.
RHEL64 | 3.9 kB 00:00 ...
glibc-2.12-1.107.el6.i686 : The GNU libc libraries
Repo : RHEL64
Matched from:
Other : ld-linux.so.2
In this example, the missing package is glibc-2.12-1.107.el6.i686.
v In some cases, the NPS command could report an error for a missing libssl file.
You can use the yum provides command to obtain more information about the
packages that contain the library, and if any of the files already exist on your
workstation.

yum provides */libssl*
Loaded plugins: product-id, refresh-packagekit, security, subscription-manager
This system is not registered to Red Hat Subscription Management. You can use
subscription-manager to register.
nss-3.14.0.0-12.el6.x86_64 : Network Security Services
Repo : RHEL64
Matched from:
Filename : /usr/lib64/libssl3.soopenssl-devel-1.0.0-27.el6.x86_64 : Files for
: development of applications which will use OpenSSL
Repo : RHEL64
Matched from:
Filename : /usr/lib64/pkgconfig/libssl.pc
Filename : /usr/lib64/libssl.so
To resolve the problem, you may need to obtain and install the package
nss-3.14.0.0-12.el6.x86_64 or you might be able to create a symbolic link if
the library already exists on your system. Use caution when creating symbolic
links or changing the library files. You should consult with your IT department
to ensure that you can obtain the needed packages, or that changes to the
symbolic links will not impact the operation of other applications on your
workstation.
Based on the missing libraries and packages, use the following steps to obtain the
Red Hat packages.
v Mount the Red Hat distribution DVD or ISO file to the client system. Insert the
DVD into the DVD drive.
v Open a terminal window and log in as root.
v Run the following commands:
[root@myrhsystem]# mkdir /mnt/cdrom
[root@myrhsystem]# mount -o ro /dev/cdrom /mnt/cdrom
v Create the text file server.repo in the /etc/yum.repos.d directory.
Note: To use gedit, run the command: gedit /etc/yum.repos.d/server.repo

and add the following text to the file where baseurl is the mount point and the
RHEL distribution. In the example, the mounting point is cdrom and the RHEL
distribution is Workstation but it could be a server or the ISO file.
name=server
baseurl=file:///mnt/cdrom/Workstation
enabled=1
v Run the command: yum clean all
v Run the command to import related public keys: rpm --import
/mnt/cdrom/*GPG*
v Run the following command to install the required libraries: yum install
<package-name> where <package-name> is the file that contains the libraries that
you require for the NPS command operations.
To identify and obtain the required SUSE packages, you could use a process
similar to the following.
v Log in to the SUSE system as root or a superuser.
v If the test NPS command failed with the error that libssl.so.4 or
libcrypto.so.4 or both could not be found, you could be able to resolve the
issue by adding a symbolic link to the missing file from the NPS client
installation directory (for example, /usr/local/nz/lib). Use the ls /lib/libssl*
command to list the available libraries in the standard OS directories. You could
then create symbolic links to one of your existing libssl.so and libcrypto.so
files by using commands similar to the following:

mylinux:/usr/local/nz/lib # ln -s /usr/lib/libssl.so.0.9.8 /lib/libssl.so.4
mylinux:/usr/local/nz/lib # ln -s /usr/lib/libcrypto.so.0.9.8 /lib/libcrypto.so.4
v If you are missing other types of files or libraries, use the zypper wp command
and specify the file name to see which package provides it. An example follows.
zypper wp ld-linux.so.2
Loading repository data...
Reading installed packages...
S | Name | Type | Version | Arch | Repository
--+-------------+---------+----------+--------+---------------------------------
i | glibc-32bit | package | 2.9-13.2 | x86_64 | SUSE-Linux-Enterprise-Desktop-11
In this example, the missing package is glibc-32bit.
If the error indicates that you are missing other libraries or packages, use the
following steps to obtain the SUSE packages.
v Open a terminal window and log in as root.
v Run the yast command to open the YaST interface.
v One the YaST Control Center, select Software and go to the software repositories
to configure and enable a DVD, a server, or an ISO file as a repository source.
Select the appropriate source for your SUSE environment. Consult with your IT
department about the policies for package updates in your environment.
v On the Software tab, go to Software Management and search for the required
package or library such as glibc-32bit in this example.
v Click Accept to install the required package.
v Exit YaST by clicking Quit.
Path for Netezza CLI client commands

You can run most of the CLI commands from the IBM Netezza client systems,
except for nzstart and nzstop which run only on the host Netezza system.
To run the CLI commands on Solaris, you must include /usr/local/lib in your
environment variable LD_LIBRARY_PATH. Additionally, to use the ODBC driver on
Linux, Solaris, or HP-UX, you must include /usr/local/nz/lib, or the directory
path to nz/lib where you installed the Netezza CLI tools.
Related reference:
“Command locations” on page 3-3
Removing the CLI clients from UNIX systems

About this task
To remove the client CLI kits from a UNIX system, complete the following steps:
Procedure
1. Change to the directory where you installed the clients. For example,
/usr/local/nz.
2. Delete the nz commands manually.
Install the Netezza tools on a Windows client

The IBM Netezza Client Components for Windows contains the Windows nzsetup.exe
command, which installs the IBM Netezza Windows client tools. The installation
program installs the NzAdmin tool, several nz command-line executable files and
libraries, online help files, and Netezza guides in PDF format.

Installation requirements
The installation package requires a computer system that runs a supported
Windows operating system such as Windows Vista (32-bit), 2008 (32-bit and 64-bit),
Windows 7 (32-bit and 64-bit), and Windows Server 2012 (64-bit). The client system
must also have either a CD/DVD drive or a network connection.
If you are using or viewing object names that use UTF-8 encoded characters, your
Windows client systems require the Microsoft universal font to display the
characters within the NzAdmin tool. The Arial Unicode MS font is installed by
default on some Windows systems, but you might have to run a manual
installation for other Windows platforms such as 2003 or others. For more
information, see the Microsoft support topic at http://office.microsoft.com/en-us/
help/hp052558401033.aspx.
Installing the Netezza tools

About this task
To install the IBM Netezza tools on Windows, complete the following steps:
Procedure
1. Insert the IBM Netezza Client Components for Windows DVD in your media drive
and go to the admin directory. If you downloaded the client package
(nzsetup.exe) to a directory on your client system, change to that directory.
2. Double-click or run nzsetup.exe.
This program is a standard installation program that consists of a series of
steps in which you select and enter information that is used to configure the
installation. You can cancel the installation at any time.
Results
The installation program displays a license agreement, which you must accept to
install the client tools. You can also specify the following information:
Destination folder
You can use the default installation folder or specify an alternative
location. The default folder is C:\Program Files\IBM Netezza Tools. If you
choose a different folder, the installation program creates the folder if one
does not exist.
Setup type
Select the type of installation: typical, minimal, or custom.
Typical
Install the nzadmin program, the help file, the documentation, and
the console utilities, including the loader.
Minimal
Install the nzadmin program and help files.
Custom
Displays a screen where you can select to install any combination
of the administration application, console applications, or
documentation.
After you complete the selections and review the installation options, the client
installer creates the Netezza Tools folder, which has several subfolders. You cannot
change the subfolder names or locations.

Bin Executable files and support files
Doc Copies of the Netezza user guides and an Acrobat Index to search the doc
set
Help Application help files
jre Java™ runtime environment files for the Netezza tools
sys Application string files
Uninstall Netezza Tools
Files to remove Netezza tools from the client system
The installation program displays a dialog when it completes, and on some

systems, it can prompt you to restart the system before you use the application.
The installer stores copies of the software licenses in the installation directory,
which is usually C:\Program Files\IBM Netezza Tools (unless you specified a
different location).
The installation program adds the Netezza commands to the Windows Start >
Programs menu. The program group is IBM Netezza and it has the suboptions
IBM Netezza Administrator and Documentation. The IBM Netezza Administrator
command starts the NzAdmin tool. The Documentation command lists the PDFs of
the installed documentation.
To use the commands in the bin directory, you must open a Windows
command-line prompt (a DOS prompt).
Environment variables
The following table lists the operating system environment variables that the
installation tool adds for the IBM Netezza console applications.
Table 2-2. Environment variables
Variable Operation Setting
PATH append <installation directory>\bin
NZ_DIR set Installation directory (for example C:\Program
Files\IBM Netezza Tools)
Removing the IBM Netezza tools

About this task
You can remove or uninstall the Windows tools by using the Windows Add or
Remove Programs interface in the Control Panel. The uninstallation program
removes all folders, files, menu commands, and environment variables. The
registry entries that are created by other IBM Netezza applications, however, are
not removed.
To remove the IBM Netezza tools from a Windows client, complete the following
steps:
Procedure
1. Click Start > Control Panel > Uninstall. The menu options can vary with each
Windows operating system type.

2. Select IBM Netezza Tools, then click Uninstall/Change. The Uninstall IBM
Netezza Tools window appears.
3. Click Uninstall. The removal usually completes in a few minutes. Wait for the
removal to complete.
4. Using the File Explorer, check the installation location, which is usually
C:\Program Files\IBM Netezza Tools. If the Windows client was the only
installed Netezza software, you can delete the IBM Netezza Tools folder to
completely remove the application.
Clients and Unicode characters

If you create object names that use characters outside the 7-bit-ASCII character
range, the nzsql command, the ODBC, JDBC, and OLE-DB drivers, NzAdmin tool,
and the IBM Netezza Performance Portal interface all support the entering and
display of those characters. On Windows systems, users must ensure that they
have appropriate fonts that are loaded to support their character sets of choice.
IBM Netezza commands that display object names such as nzload, nzbackup, and
nzsession can also display non-ASCII characters, but they must operate on a
UTF-8 terminal or DOS window to display characters correctly.
For UNIX clients, make sure that the terminal window in which you run these nz
commands uses a UTF-8 locale. The output in the terminal window might not
align correctly.
Typically, Windows clients require two setup steps.
This procedure is a general recommendation that is based on common practices. If

you encounter any difficulty with Windows client setup, see Microsoft Support to
obtain the setup steps for your specific platform and fonts.
1. Set the command prompt to use an appropriate True Type font that contains
the required glyphs. To select a font:
a. Select Start > Programs > Accessories.
b. Right-click Command Prompt and then select Properties from the menu.
c. Select the Font tab. In the Font list, the True Type fixed width font or fonts
are controlled by the registry setting
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Console\TrueTypeFont
On a standard US system, the font is Lucida Console (which does not
contain UTF-8 mapped glyphs for Kanji). On a Japanese system, the font is
MS Gothic, which contains those glyphs.
2. In a DOS command prompt window, change the code page to UTF-8 by
entering the chcp 65001 command:
As an alternative to these DOS setup steps, the input/output from the DOS clients
can be piped from/to nzconvert and converted to a local code page, such as 932
for Japanese.
On a Windows system, the fonts that you use for your display must meet the
Microsoft requirements as outlined on the Support site at http://
support.microsoft.com/default.aspx?scid=kb;EN-US;Q247815.

Client timeout controls
In some customer environments where users connect over VPNs to the IBM
Netezza appliance, users might encounter issues where active SQL sessions
timeout because of VPN/TCP connection settings in the customer environment.
For these environments, Netezza adds TCP KEEPALIVE packet support with the
following new settings in the /nz/data/postgresql.conf file:
tcp_keepidle
The number of seconds between keepalive messages that are sent on an
otherwise idle database connection. A value of 0 uses the system default
(7200 seconds). The idle timeout can be used to keep connections from
being closed by your network controls (such as firewalls, agents, or
network management software) that have idle session timeout settings. In
general, your tcp_keepidle setting should be less than the network idle
timeout settings. If the setting is longer than the network timeout, the
network could close the idle database connections.
tcp_keepinterval
The number of seconds to wait for a keepalive response before
retransmitting the message. A value of 0 uses the system default (75
seconds).
tcp_keepcount
The number of retransmission attempts that must occur before the
connection is considered dead. A value of 0 uses the system default (9
attempts).
After you define (or modify) these settings in the postgresql.conf file, you must
restart the Netezza software to apply the changes.
Netezza port numbers

The IBM Netezza system uses the following port numbers or environmental
variables for the CLI commands and the NzAdmin tool. The following table lists
the default ports and corresponding environment variables:
Table 2-3. Netezza port numbers for database access
Port Environment variable Description
5480 NZ_DBMS_PORT The postgres port for the nzsql command,
NzAdmin tool, ODBC, and JDBC.
5481 NZ_CLIENT_MGR_PORT The port for the CLI and NzAdmin tool
messaging.
5482 NZ_LOAD_MGR_PORT Before to release 3.1, this port handled loads. As of
release 3.1, this port is not required.
5483 NZ_BNR_MGR_PORT The port for the nzbackup and nzrestore
commands.
Netezza personnel, if granted access for remote service, use port 22 for SSH, and
ports 20 and 21 for FTP.

Changing the default port numbers
About this task
For security or port conflict reasons, you can change one or more default port
numbers for the IBM Netezza database access.
Important: Be careful when you are changing the port numbers for the Netezza
database access. Errors can severely affect the operation of the Netezza system. If
you are not familiar with editing resource shell files or changing environment
variables, contact Netezza Support for assistance.
Before you begin, make sure that you choose a port number that is not already in
use. To check the port number, you can review the /etc/services file to see
whether the port number is specified for another process. You can also use the
netstat | grep port command to see whether the designated port is in use.
To change the default port numbers for your Netezza system, complete the
following steps:
Procedure
1. Log in to the Netezza host as the nz user.
2. Change to the /nz/kit/sys/init directory.
3. Create a backup of the current nzinitrc.sh file:
[nz@nzhost init]$ cp nzinitrc.sh nzinitrc.sh.backup
4. Review the nzinitrc.sh file to see whether the Netezza port or ports that are
listed in Table 2-3 on page 2-10 that you want to change are present in the file.
For example, you might find a section that looks similar to the following, or
you might find that these variables are defined separately within the
nzinitrc.sh file.
# Application Port Numbers
# ------------------------
# To change the application-level port numbers, uncomment the

following lines,
# and then change the numbers to their new values. Note that these
new values
# will need to be set on clients as well.
# NZ_DBMS_PORT=5480; export NZ_DBMS_PORT

# NZ_CLIENT_MGR_PORT=5481; export NZ_CLIENT_MGR_PORT
# NZ_LOAD_MGR_PORT=5482; export NZ_LOAD_MGR_PORT
# NZ_BNR_MGR_PORT=5483; export NZ_BNR_MGR_PORT
# NZ_RECLAIM_MGR_PORT=5484; export NZ_RECLAIM_MGR_PORT
If you do not find your variable or variables in the file, you can edit the file to
define each variable and its new port definition. To define a variable in the
nzinitrc.sh file, use the format NZ_DBMS_PORT=value; export NZ_DBMS_PORT.
Tip: You can append the contents of the nzinitrc.sh.sample file to the
nzinitrc.sh file to create an editable section of variable definitions. You must
be able to log in to the Netezza host as the root user; then, change to the
/nz/kit/sys/init directory and run the following command:
[nz@nzhost init]$cat nzinitrc.sh.backup nzinitrc.sh.sample
>nzinitrc.sh

5. Using a text editor, edit the nzinitrc.sh file. For each port that you want to
change, remove the comment symbol (#) from the definition line and specify
the new port number. For example, to change the NZ_DBMS_PORT variable
value to 5486:
NZ_DBMS_PORT=5486; export NZ_DBMS_PORT
# NZ_CLIENT_MGR_PORT=5481; export NZ_CLIENT_MGR_PORT
# NZ_LOAD_MGR_PORT=5482; export NZ_LOAD_MGR_PORT
# NZ_BNR_MGR_PORT=5483; export NZ_BNR_MGR_PORT
# NZ_RECLAIM_MGR_PORT=5484; export NZ_RECLAIM_MGR_PORT
6. Review your changes carefully to make sure that they are correct and save the
file.
If you change the default port numbers, some of the Netezza CLI commands
might no longer work. For example, if you change the NZ_DBMS_PORT or
NZ_CLIENT_MGR_PORT value, commands such as nzds, nzstate, and others
can fail because they expect the default port value. To avoid this problem, copy
the custom port variable definitions in the nzinitrc.sh file to the
/export/home/nz/.bashrc file. You can edit the .bashrc file by using any text
editor.
7. To place the new port value or values into effect, stop and start the Netezza
server by using the following commands:
[nz@nzhost init]$ nzstop
[nz@nzhost init]$ nzstart
Non-default NPS port numbers for clients

If your IBM Netezza system uses non-default port numbers, your client users must
specify the port number when they connect by using commands such as nzsql,
nzload, or by using clients such as NzAdmin. For example, if you change the
NZ_DBMS_PORT number from the default of 5480, your client users must specify
the new port value, otherwise their commands return an error that they cannot
connect to the database server at port 5480.
Some Netezza commands such as nzsql and nzload have a -port option that
allows the user to specify the DB access port. In addition, users can create local
definitions of the environment variables to specify the new port number.
For example, on Windows clients, users can create an NZ_DBMS_PORT user

environment variable in the System Properties > Environment Variables dialog to
specify the non-default port of the Netezza system. For clients such as NzAdmin,
the environment variable is the only way to specify a non-default database port for
a target Netezza system. For many systems, the variable name and value take
effect immediately and are used the next time that you start NzAdmin. When you
start NzAdmin and connect to a system, if you receive an error that you cannot
connect to the Netezza database and the reported port number is incorrect, check
the variable name and value to confirm that they are correct. You might have to
restart the client system for the variable to take effect.
For a Linux system, you can define a session-level variable by using a command
similar to the following format:
$ NZ_DBMS_PORT=5486; export NZ_DBMS_PORT
For the instructions to define environment variables on your Windows, Linux, or

UNIX client, see the operating system documentation for your client.

If a client user connects to multiple Netezza hosts that each use different port
numbers, those users might have to use the -port option on the commands as an
override, or change the environment variable value on the client before they
connect to each Netezza host.
Encrypted passwords
Database user accounts must be authenticated during access requests to the IBM
Netezza database. For user accounts that use local authentication, Netezza stores
the password in encrypted form in the system catalog. For more information about
encrypting passwords on the host and the client, see the IBM Netezza Advanced
Security Administrator's Guide.
Local authentication requires a password for every account. If you use LDAP
authentication, a password is optional. During LDAP authentication, Netezza uses
the services of an LDAP server in your environment to validate and verify Netezza
database users.
v When you are using the Netezza CLI commands, the clear-text password must
be entered on the command line. You can set the environment variable
NZ_PASSWORD to avoid typing the password on the command line, but the
variable is stored in clear text with the other environment variables.
v To avoid displaying the password on the command line, in scripts, or in the
environment variables, you can use the nzpassword command to create a locally
stored encrypted password.
You cannot use stored passwords with ODBC or JDBC.
The nzpassword command syntax is:

nzpassword add -u user -pw password -host hostname
Where:
v The user name is the Netezza database user name in the Netezza system catalog.
If you do not specify the user name on the command line, the nzpassword
command uses the environment variable NZ_USER.
v The password is the Netezza database user password in the Netezza system
catalog or the password that is specified in the environment variable
NZ_PASSWORD. If you do not supply a password on the command line or in the
environment variable, the system prompts you for a password.
v The host name is the Netezza host. If you do not specify the host name on the
command line, the nzpassword command uses the environment variable NZ_HOST.
You can create encrypted passwords for any number of user name/host pairs.
When you use the nzpassword add command to cache the password, quotation
marks are not required around the user name or password values. You must only
qualify the user name or password with a surrounding set of single quotation
mark, double quotation mark pairs (for example, '"Bob"') if the value is
case-sensitive. If you specify quoted or unquoted names or passwords in
nzpassword or other nz commands, you must use the same quoting style in all
cases.
If you qualify a user name that is not case-sensitive with quotation marks (for
example '"netezza"'), the command might still complete successfully, but it might
not work in all command cases.

After you type the nzpassword command, the system sends the encrypted
password to the Netezza host where it is compared against the user
name/password in the system catalog.
v If the information matches, the Netezza stores the encrypted information in a
local password cache, and displays no additional message.
– On Linux and Solaris, the password cache is the file .nzpassword in the user
home directory. The system creates this file without access permissions to
other users, and refuses to accept a password cache whose permission allows
other users access.
– On Windows, the password cache is stored in the registry.
v If the information does not match, Netezza displays a message that indicates
that the authentication request failed. Netezza also logs all verification attempts.
v If the database administrator changed a user password in the system catalog, the
existing nzpasswords are invalid.
Related concepts:
“Logon authentication” on page 11-18
Stored passwords
If client users use the nzpassword command to store database user passwords on a
client system, they can supply only a database user name and host on the
command line. Users can also continue to enter a password on the command line
if displaying clear-text passwords is not a concern for security.
If you supply a password on the command line, it takes precedence over the
environment variable NZ_PASSWORD. If the environment variable is not set, the
system checks the locally stored password file. If there is no password in this file
and you are using the nzsql command, the system prompts you for a password,
otherwise the authentication request fails.
In all cases, using the -pw option on the command line, using the NZ_PASSWORD
environment variable, or using the locally stored password that is stored through
the nzpassword command. IBM Netezza compares the password against the entry
in the system catalog for local authentication or against the LDAP or KERBEROS
account definition. The authentication protocol is the same, and Netezza never
sends clear-text passwords over the network.
In release 6.0.x, the encryption that is used for locally encrypted passwords
changed. In previous releases, Netezza used the Blowfish encryption routines;
release 6.0 now uses the Advanced Encryption Standard AES-256 standard. When
you cache a password by using a release 6.0 client, the password is saved in
AES-256 format unless there is an existing password file in Blowfish format. In that
case, new stored passwords are saved in Blowfish format.
If you upgrade to a release 6.0.x or later client, the client can support passwords in
either the Blowfish format or the AES-256 format. If you want to convert your
existing password file to the AES-256 encryption format, you can use the
nzpassword resetkey command to update the file. If you want to convert your
password file from the AES-256 format to the Blowfish format, use the nzpassword
resetkey -none command.
Important: Older clients, such as those for release 5.0.x and those clients earlier
than release 4.6.6, do not support AES-256 format passwords. If your password file
is in AES-256 format, the older client commands prompt for a password, which can

cause automated scripts to hang. Also, if you use an older client to add a cached
password to or delete a cached password from an AES-256 format file, you can
corrupt the AES-256 password file and lose the cached passwords. If you typically
run multiple releases of Netezza clients, use the Blowfish format for your cached
passwords.

Chapter 3. Netezza administration interfaces
This section provides a high-level description of the IBM Netezza administration
interfaces, such as the command-line interface, the NzAdmin, and the SQL
commands. This section describes how to access and use these interfaces.
For information about the Netezza Performance Portal, see the IBM Netezza
Performance Portal User's Guide, which is available with the software kit for that
interface.
In general, the Netezza CLI commands are used most often for the various
administration tasks. Many of the tasks can also be performed by using SQL
commands or the interactive interfaces. Throughout this publication, the primary
task descriptions use the CLI commands and reference other ways to do the same
task.
Netezza CLI overview

You can use the IBM Netezza command-line interface (CLI) to issue commands to
manage Netezza software, hardware, and databases.
You can use Netezza CLI commands (also called nz commands) to monitor and
manage a Netezza system. Most nz* commands are issued on the Netezza host
system. Some are included with the Netezza client kits, and some are available in
optional support toolkits and other packages. This publication describes the host
and client nz commands.
Commands and locations

Table 3-1 lists the commonly used nz commands for tasks on the Netezza system,
and their availability on the Netezza host or in the Netezza client kits.
Note: When investigating problems, Netezza support personnel might ask you to
issue other internal nz commands that are not listed.
Table 3-1. Command summary
Host or Client Kit Availability
Netezza Linux Solaris HP AIX Windows
Command Description Host Client Client Client Client Client
nzbackup Backs up an existing v
database.
nzcontents Displays the revision v
and build number of
all the executable files,
plus the checksum of
Netezza binaries.
nzconvert Converts character v v v v v v
encodings for loading
with the nzload
command or external
tables.

Table 3-1. Command summary (continued)
nzds Manages and displays v v v v v v
information about the
data slices on the
system.
nzevent Displays and manages v v v v v v
event rules.
nzhistcleanupdb Deletes old history v
information from a
history database.
nzhistcreatedb Creates a history v
database with all its
tables, views, and
objects for history
collection and
reporting.
nzhostbackup Backs up the host v
information, including
users and groups.
nzhostrestore Restores the host v
information.
nzhw Displays information v v v v v v
about the hardware
components of a
system.
nzload Loads data into v v v v v v
database files.
nzodbcsql A client command on v v v v
Netezza UNIX clients
that tests ODBC
connectivity.
nzpassword Stores a local copy of v v v v v v
the user's password.
nzreclaim Uses the SQL GROOM v v v v v
TABLE command to
reclaim disk space from
user tables, and also to
reorganize the tables.
nzrestore Restores the contents of v
a database backup.
nzrev Displays the current v v v v v v
software revision for
any Netezza software
release.

Table 3-1. Command summary (continued)
nzsession Shows a list of current v v v v v v
system sessions (load,
client, and sql).
Supports filtering by
session type or user,
which you can use to
abort sessions, and
change the current job
list for a queued
session job.
nzspupart Displays information v v v v v v
about the SPU
partitions, including
status information and
the disks that support
the partition.
nzsql Invokes the SQL v v v v v v
command interpreter.
nzstart Starts the system. v
nzstate Displays the current v v v v v v
system state or waits
for a specific system
state to occur before it
returns.
nzstats Displays system level v v v v v v
statistics.
nzstop Stops the system. v
nzsystem Changes the system v v v v v v
state or displays the
current system
information.
Command locations
The following table shows the default location of each CLI command and in which
of the host and client kits they are available:
Command Type Default Location

Netezza host /nz/kit/bin
Linux, Solaris, HP, or AIX client /usr/local/nz/bin
Windows client C:\Program Files\Netezza Tools\Bin
Add the appropriate bin directory to your search path to simplify command
invocation.
Related concepts:
“Path for Netezza CLI client commands” on page 2-6
Command syntax
All IBM Netezza CLI commands have the following top-level syntax options:
Chapter 3. Netezza administration interfaces 3-3

-h Displays help. You can also enter -help.
-rev Displays the software revision level. You can also enter -V.
-hc Displays help for the subcommand (if the command has subcommands).
For many Netezza CLI commands you can specify a timeout. This time is the
amount of time the system waits before it abandons the execution of the command.
If you specify a timeout without a value, the system waits 300 seconds. The
maximum timeout value is 100 million seconds.
Issuing commands
To issue an nz command, you must have access to the IBM Netezza system (either
directly on the Netezza KVM or through a remote shell connection) or you must
install the Netezza client kit on your workstation. If you are accessing the Netezza
system directly, you must be able to log in by using a Linux account (such as nz).
While some of the nz commands can operate and display information without
additional access requirements, some commands and operations require that you
specify a Netezza database user account and password. The account might also
require appropriate access and administrative permissions to display information
or process a command.
The following are several examples.

v To display the state of a Netezza system by using a Windows client command,
run the following command:
C:\Program Files\Netezza Tools\Bin>nzstate show -host mynps -u user
-pw passwd
System state is ’Online’.
v To display the valid Netezza system states by using a Windows client command,
C:\Program Files\Netezza Tools\Bin>nzstate listStates
State Symbol Description

------------ ------------------------------------------------------------
initialized used by a system component when first starting
paused already running queries will complete but new ones are queued
pausedNow like paused, except running queries are aborted
offline no queries are queued, only maintenance is allowed
offlineNow like offline, except user jobs are stopped immediately
online system is running normally
stopped system software is not running
down system was not able to initialize successfully
Note: In this example, you did not have to specify a host, user, or password.
The command displayed information that was available on the local Windows
client.
v To back up a Netezza database (you must run the command while logged in to
the Netezza system, as this is not supported from a client):
[nz@npshost ~]$ nzbackup -dir /home/user/backups -u user -pw
password -db db1
Backup of database db1 to backupset 20090116125409 completed
successfully.
Identifiers in commands
When you use the IBM Netezza commands and specify identifiers for users,
passwords, database names, and other objects, you can pass normal identifiers that

are unquoted on the Linux command line. The Netezza server performs the
appropriate case-conversion for the identifier.
However, if you use delimited identifiers, the supported way to pass them on the
Linux command line is to use the following syntax:
’\’Identifier\’’
The syntax is single quotation mark, backslash, single quotation mark, identifier,
backslash, single quotation mark, single quotation mark. This syntax protects the
quotation marks so that the identifier remains quoted in the Netezza system.
SQL command overview

IBM Netezza database users, if permitted, can perform some administrative tasks
by using SQL commands while they are logged in through SQL sessions. For
example, users can do the following tasks:
v Manage Netezza users and groups, access permissions, and authentication
v Manage database objects (create, alter, or drop objects, for example)
v Display and manage session settings
v Manage history configurations
Throughout this publication, SQL commands are shown in uppercase (for example,
CREATE USER) to stand out as SQL commands. The commands are not
case-sensitive and can be entered by using any letter casing. Users must have
Netezza database accounts and applicable object or administrative permissions to
do tasks. For detailed information about the SQL commands and how to use them
to do various administrative tasks, see the IBM Netezza Database User’s Guide.
The nzsql command

The nzsql command invokes a SQL command interpreter on the IBM Netezza host
or on a IBM Netezza client system. You can use this SQL command interpreter to
create database objects, run queries, and manage the database.
To run the nzsql command, enter:

nzsql [options] [security options] [dbname [user] [password]]
The following table describes the nzsql command parameters. For more
information about the command parameters and how to use the command, see the
IBM Netezza Database User’s Guide.
Table 3-2. nzsql command parameters
Parameters Description
-a Echo all input from a script.
-A Use unaligned table output mode. This is equivalent to specifying
-P format=unaligned.
-c <query> Run only a single query (or slash command) and exit.
-d <dbname> Specify the name of the database to which to connect. If you do
or not specify this parameter, the nzsql command uses the value
-D <dbname> specified for the NZ_DATABASE environment variable (if it is
specified) or prompts you for a password (if it is not).

Table 3-2. nzsql command parameters (continued)
-schema <schemaname> Specify the name of the schema to which to connect. This option
is used for Netezza Release 7.0.3 and later systems that are
configured to use multiple schemas. If the system does not
support multiple schemas, this parameter is ignored. If you do not
specify this parameter, the nzsql command uses the value
specified for the NZ_SCHEMA environment variable (if it is specified)
or a schema that matches the database account name (if it is not
and if enable_user_schema is set to TRUE), or the default schema
for the database (otherwise).
-e Echo queries that are sent to the server.
-E Display queries generated by internal commands.
-f <file name> Run queries from a file, then exit.
-F <string> Set the field separator. The default: is a vertical bar (|). This is
equivalent to specifying -P fieldsep=<string>.
-h Display help for the nzsql command.
-H Set the table output mode to HTML. This is equivalent to
specifying -P format=html.
-host <host> Specify the hostname of the database server.
-l List available databases, then exit.
-n Disable readline mode. This is required when input uses a
double-byte character set such as Japanese, Chinese, or Korean
-o <file name> Send query output to the specified file or, if a vertical bar (|) is
specified instead of a file name, to a pipe.
-O <file name> Send query output and any error messages to the specified file or,
if a vertical bar (|) is specified instead of a file name, to a pipe.
-P opt[=val] Set the printing option represented by opt to the value
represented by val.
-port <port> Specify the database server port.
-pw <password> Specify the password of the database user. If you do not specify
this parameter, the nzsql command uses the value specified for
the NZ_PASSWORD environment variable (if it is specified) or
prompts you to enter a password (if it is not).
-q Run quietly, that is, without issuing messages. Only the query
output is returned.
-r Suppress the row count that otherwise is displayed at the end of
the query output.
-R <string> Set the record separator. The default is the newline character. This
is equivalent to specifying -P recordsep=<string>.
-s Use single-step mode, which requires that each query be
confirmed.
-S Use single-line mode, which causes a newline character to
terminate a query.
-t Print rows only This is equivalent to specifying -P tuples_only.
-time Print the time that is taken by queries.
-T <text> Set the HTML table tag options such as width and border. This is
equivalent to specifying -P tableattr=<text>.

Table 3-2. nzsql command parameters (continued)
-u <username> Specifies the database user name. If you do not specify this
or parameter, the nzsql command uses the value specified for the
-U <username> NZ_USER environment variable (if it is specified) or prompts you to
enter a user name (if it is not).
-v <name>=<value> Set the specified session variable to the specified value. Specify
this parameter once for each variable to be set, for example:
nzsql -v HISTSIZE=600 -v USER=user1 -v PASSWORD=password
-V Display version information and exit.
-w Do not require a password for the database user. The password is
supplied by other mechanisms (Kerberos, for example).
-W <password> Specify the password of the database user. (Same as -pw.)
-x Expand table output. This is equivalent to specifying -P expanded.
-X Do not read the startup file (~/.nzsqlrc).
-securityLevel Specify the security level (secured or unsecured) for a client
<level> connection to the Netezza system. This option does not apply
when you are logged in to the Netezza system and running the
command.
preferredUnSecured
You prefer an unsecured connection, but you will accept
a secured connection if the system is configured to use
only secured connections. This is the default.
preferredSecured
You prefer a secured connection, but you will accept an
unsecured connection if the system is configured to use
only unsecured connections.
onlyUnSecured
You require an unsecured connection. If the system is
configured to use only secured connections, the
connection attempt is rejected.
onlySecured
You require a secured connection. If the system is
configured to use only unsecured connections or has a
release level that is earlier than 4.5, the connection
attempt is rejected.
-caCertFile <path> Specify the path to the root CA certificate file on the client system.
This option is used by Netezza clients that use peer authentication
to verify the Netezza host system. The default value is NULL,
which skips the peer authentication process.
Within the nzsql command interpreter, enter the \h slash commands for help about
or to run a command:
Within the nzsql command interpreter, enter the following slash commands for
help about or to run a command:
\h List all SQL commands.
\h <command>
Display help about the specified SQL command.
\? List and display help about all slash commands.

\g Run a query. This has the same effect as terminating the query with a
semicolon.
\q Quit
nzsql behavior differences on UNIX and Windows clients
Starting in NPS release 7.2.1, the nzsql command is included as part of the
Windows client kit. In a Windows environment, note that there are some
behavioral differences when users press the Enter key or the Control-C key
sequence than in a UNIX nzsql command line environment. The Windows
command prompt environment does not support many of the common UNIX
command formats and options. However, if your Windows client is using a Linux
environment like cygwin or others, the nzsql.exe command could support more of
the UNIX-only command line options noted in the documentation.
In a UNIX environment, if you are typing a multiline SQL query into the nzsql
command line shell, the Enter key acts as a newline character to accept input for
the query until you type the semi-colon character and press Enter. The shell
prompt also changes from => to -> for the subsequent lines of the input.
MYDB.SCH(USER)=> select count(*) (press Enter)
MYDB.SCH(USER)-> from ne_part (press Enter)
MYDB.SCH(USER)-> where p_retailprice < 950.00 (press Enter)
MYDB.SCH(USER)-> ; (press Enter)
COUNT
-------
1274
(1 row)
In a UNIX environment, if you press Control-C, the entire query is cancelled and
you return to the command prompt:
MYDB.SCH(USER)-> where p_retailprice < 950.00 (press Control-C)
MYDB.SCH(USER)=>
In a Windows client environment, if you are typing a multiline SQL query into the
nzsql command line shell, the Enter key acts similarly as a newline character to
accept input for the query until you type the semi-colon character and press Enter.
MYDB.SCH(USER)-> where p_retailprice < 950.00 (press Enter)
COUNT
-------
1274
(1 row)
However, in a Windows environment, the Control-C or Control-Break key

sequences do not cancel the multiline query, but instead, cancel only that line of
the query input:
MYDB.SCH(USER)-> where p_retailprice < 950.00 (press Control-C)

COUNT
-------
100000
(1 row)
The Control-C (or a Control-Break) cancelled the WHERE clause on the third input
line, and thus the query results were larger without the restriction. In a single
input line (where the prompt is =>, note that Control-C cancels the query and you
return to the nzsql command prompt.
MYDB.SCH(USER)=> select count(*) from ne_part (press Control-C)
MYDB.SCH(USER)=>
nzsql requires the more command on Windows
When you run the nzsql command on a Windows client, you could see the error
more not recognized as an internal or external command. This error occurs
because nzsql uses the more command to process the query results. The error
indicates that the nzsql command could not locate the more command on your
Windows client.
To correct the problem, add the more.com command executable to your client
system's PATH environment variable. Each Windows OS version has a slightly
different way to modify the environment variables, so refer to your Windows
documentation for specific instructions. On a Windows 7 system, you could use a
process similar to the following:
v Click Start, and then type environment in the search field. In the search results,
click Edit the system environment variables. The System Properties dialog
opens and displays the Advanced tab.
v Click Environment variables. The Environment Variables dialog opens.
v In the System variables list, select the Path variable and click Edit. The Edit
System Variable dialog opens.
v Place the cursor at the end of the Variable value field. You can click anywhere in
the field and then press End to get to the end of the field.
v Append the value C:\Windows\System32; to the end of the Path field. Make
sure that you use a semi-colon character and type a space character at the end of
the string. If your system has the more.com file in a directory other than
C:Windows\System32, use the pathname that is applicable on your client.
v Click OK in the Edit System Variable dialog, then click OK in the Environment
Variables dialog, then click OK in the System Properties dialog.
After you make this change, the nzsql command should run without displaying
the more not recognized error.
The nzsql session history

On UNIX clients, the IBM Netezza system stores the history of your nzsql session
in the file $HOME/.nzsql_history. In interactive sessions, you can also use the
up-arrow key to display the commands that you ran.
On Windows clients, you can use the up-arrow key to display the commands that
ran previously.
By default, an nzsql batch session continues even if the system encounters errors.
You can control this behavior with the ON_ERROR_STOP variable, for example:
nzsql -v ON_ERROR_STOP=

You do not have to supply a value; defining it is sufficient.
You can also toggle batch processing with a SQL script. For example:
\set ON_ERROR_STOP
\unset ON_ERROR_STOP
You can use the $HOME/.nzsqlrc file to store values, such as the ON_ERROR_STOP,
and have it apply to all future nzsql sessions and all scripts.
Displaying information about databases and objects

Use nzsql slash commands to display information about databases and objects.
The following table describes the slash commands that display information about
objects or privileges within the database, or within the schema if the system
supports multiple schemas.
Table 3-3. The nzsql slash commands
Command Description
\d <object> Describe the named object such as a table, view, or
sequence
\da[+] List user-defined aggregates. Specify + for more detailed
information.
\df[+] List user-defined functions. Specify + for more detailed
information.
\de List temp tables.
\dg List groups (both user and resource groups) except
_ADMIN_.
\dG List user groups and their members.
\dGr List resource groups to which at least one user has been
assigned, including _ADMIN_, and the users assigned to
them.
\di List indexes.
\dm List materialized views
\ds List sequences.
\dt List tables.
\dv List views.
\dx List external tables.
\dy List synonyms.
\dSi List system indexes.
\dSs List system sequences.
\dSt List system tables.
\dSv List system views.
\dMi List system management indexes.
\dMs List system management sequences.
\dMt List system management tables.
\dMv List system management views.
\dp <user> List the privileges that were granted to a user either
directly or by membership in a user group.

Table 3-3. The nzsql slash commands (continued)
Command Description
\dpg <group> List the privileges that were granted to a user group.
\dpu <user> List the privileges that were granted to a user directly
and not by membership in a user group.
\du List users.
\dU List users who are members of at least one user group
and the groups of which each is a member.
Suppressing row count information

You can use the nzsql -r option or the NO_ROWCOUNT session variable to suppress
the row count information that displays at the end of the query output. A sample
query that displays the row count follows:
mydb.myschema(myuser)=> select count(*) from nation;
COUNT
-------
25
(1 row)
Note: Starting in Release 7.0.3, the nzsql environment prompt has changed. As
shown in the example command, the prompt now shows the database and schema
(mydb.myschema) to which you are connected. For systems that do not support
multiple schemas, there is only one schema that matches the name of the user who
created the database. For systems that support multiple schemas within a database,
the schema name will match the current schema for the connection.
To suppress the row count information, you can use the nzsql -r command when
you start the SQL command-line session. When you run a query, the output does
not show a row count:
COUNT
-------
25
You can use the NO_ROWCOUNT session variable to toggle the display of the row
count information within a session, as follows:
COUNT
-------
25
(1 row)
mydb.myschema(myuser)=> \set NO_ROWCOUNT

COUNT
-------
25
mydb.myschema(myuser)=> \unset NO_ROWCOUNT

COUNT
-------
25
(1 row)

NzAdmin overview
NzAdmin is a tool that you can use to manage an IBM Netezza the system, obtain
information about the hardware, and manage various aspects of the user
databases, tables, and other objects. Because the NzAdmin tool runs on a Windows
client system, to use it you must first install the IBM Netezza windows client
application as described in “Install the Netezza tools on a Windows client” on
page 2-6. You must have NzAdmin database accounts and applicable object or
administrative privileges to do tasks.
Starting the NzAdmin tool

There are several ways to start an NzAdmin session:
v Click Start > Programs > IBM Netezza > IBM Netezza Administrator.
v Create a shortcut on the desktop.
v Run the nzadmin.exe by using the Run window:
v Run the nzadmin.exe file from a command window. To bypass the login dialog,
enter the following login information:
– -host or /host and the name or IP address of the Netezza host.
– -user or /user and a Netezza user name. The name you specify can be
delimited. A delimited user name is contained in quotation marks.
– -pw or /pw and the password of the specified user. To specify that a saved
password is to be used, enter -pw without entering a password string.
You can specify these parameters in any order, but you must separate them by
spaces or commas. If you specify:
– All three parameters, NzAdmin bypasses the login dialog and connects you
to the host that you specify.
– Less than three parameters, NzAdmin displays the login dialog and prompts
you to complete the remaining fields.
When you log in to the NzAdmin tool you must specify the name of the host, your
user name, and your password. The drop-down list in the host field displays the
host addresses or names that you specified in the past. If you choose to save the
password on the local system, when you log in again, you need to enter only the
host and user names.

After you log in, the NzAdmin tool checks whether its version level matches that
of the IBM Netezza system. If not, the NzAdmin tool displays a warning message
and disables certain commands. This causes operations involving event rules,
statistics, and system hardware to be unavailable.
Displaying system components and databases

The NzAdmin tool displays information in two panes:
Navigation pane
The pane on the left is the navigation pane. It displays a tree view of the
components that comprise the selected view type (System or Database).
Content pane
The pane on the right is the content pane. It displays information about or
the contents of the item selected in the tree view in the navigation pane.
At the top of the navigation pane there are tabs that you can use to select the view
type:
System
The navigation pane displays components related to system hardware such
as SPA units, SPU units, and data slices.
Database
The navigation pane displays components related to database processing
such as databases, users, groups, and database sessions.
In the status bar at the bottom of the window, the NzAdmin tool displays your
user name and the duration (days, hours, and minutes) of the current NzAdmin
session or, if the host system is not online, a message indicating this.
You can access commands by using the menu bar or the toolbar, or by
right-clicking a object and using its pop-up menu.

Figure 3-1. NzAdmin main system window
Using the System view

When displaying the System view type, you can navigate among the system
components by using either the navigation pane or the content pane. As you move
the mouse pointer over an image in the content pane, a tool tip displays
information about the corresponding component, such as its hardware ID. Click an
image in the content pane to display more information about the corresponding
component.
For example, as you move the mouse pointer over the image of a SPA unit, a tool
tip displays the slot number, hardware ID, role, and state of each of the SPUs that
comprise it. Clicking a SPU displays the SPU status window and selects the
corresponding object in the tree view shown in the navigation pane.

Figure 3-2. NzAdmin hyperlink support
Status indicators
Each component has a status indicator:
Table 3-4. Status indicators
Indicator Status Description
Normal The component is operating normally.
Warning The meaning depends on the specific component or components.
Failed The component is down, has failed, or is likely to fail. For example,
if two fans on the same SPA are down, the SPA is flagged as being
likely to fail.
Missing The component is missing and so no state information is available
for it.

Main menu
The NzAdmin main menu contains the following items:
Command Description
File > New Create a new database, table, view, materialized
view, sequence, synonym, user, or group. Available
only in the Database view.
File > System State Change the system state.
File > Reconnect Reconnect to the system with a different host name,
address, or user name.
File > Exit Exit the NzAdmin tool.
View > Toolbar Show or hide the toolbar.
View > Status Bar Show or hide the status bar.
View > System Objects Show or hide the system tables and views, and the
object privilege lists in the Object Privileges window.
View > SQL Statements Display the SQL window, which shows a subset of
the SQL commands run in this session.
View > Refresh Refresh the current view. This can be either the
System or Database view.
Tools > Workload Management Display workload management information:
Performance
Summary, history, and graph workload
management information.
Settings
The system defaults that determine the
limits on session timeout, row set, query
timeout. and session priority; and the
resource allocation that determines resource
usage among groups.
Tools > Table Skew Display any tables that meet or exceed a specified
skew threshold.
Tools > Table Storage Display table and materialized view storage usage
by database or by user.
Tools > Query History Display a window that you can use to create and
Configuration alter history configurations, and to set the current
configuration.
Tools > Default Settings Display the materialized view refresh threshold.
Tools > Options Display the Preferences tab where you can set the
object naming preferences and whether you want to
automatically refresh the NzAdmin window.
Help > NzAdmin Help Display the online help for the NzAdmin tool.
Help > About NzAdmin Display the NzAdmin and Netezza revision
numbers and copyright text.
Administration commands
You can access system and database administration commands from both the tree
view and the status pane of the NzAdmin tool. In either case, a pop-up menu lists
the commands that can be issued for the selected components.
v To activate a pop-up menu, right-click a component in a list.

v The Options hyperlink menu is in the top bar of the window.
Setting an automatic refresh interval

About this task
You can manually refresh the current (System or Database) view by clicking the
refresh icon on the toolbar, or by choosing Refresh from a menu. In addition, you
can specify that both views are to be periodically automatically refreshed, and the
refresh interval. To do this:
Procedure
1. In the main menu, click Tools > Options
2. In the Preferences tab, enable automatic refresh and specify a refresh interval.
Results
The refresh interval you specify remains in effect until you change it.
To reduce communication with the server, the NzAdmin tool refreshes data based
on the item you select in the left pane. The following table lists the items and
corresponding data that is retrieved on refresh.
Table 3-5. Automatic refresh
Selected item Data retrieved
Server (system view): All topology and hardware state information.
v SPA Units
v SPA ID n
v SPU units
Event rules Event rules.

Table 3-5. Automatic refresh (continued)
Selected item Data retrieved
Individual statistic such as DBMS Specific statistic information.
Group
Server (database view) All databases and their associated objects, users,
groups, and session information.
Databases All database information and associated objects.
Database <name> Specific database, table, and view information.
Schemas All schemas within a database (for systems that
support multiple schemas).
Schema <name> Specific schema, table, and view information.
Tables Table information.
Views View information.
Sequences Sequences information.
Synonyms Synonyms information.
Functions User-defined functions information.
Aggregates User-defined aggregates information.
Procedures Stored procedure information.
Users User information.
Groups Group information.
Sessions Session information.
If the NzAdmin tool is busy communicating with the server (for example, if it is
processing a user command or doing a manual refresh), it does not perform an
automatic refresh.
Netezza Performance Portal overview

Use the IBM Netezza Performance Portal to monitor and administer a Netezza
system.
The Netezza Performance Portal is a web-based client for monitoring and

administering Netezza systems. It replaces the deprecated Web Admin client. For
more information, refer to the IBM Netezza Performance Portal User's Guide.

Chapter 4. Manage Netezza HA systems
The IBM Netezza high availability (HA) solution uses Linux-HA and Distributed
Replicated Block Device (DRBD) as the foundation for cluster management and
data mirroring. The Linux-HA and DRBD applications are commonly used,
established, open source projects for creating HA clusters in various environments.
They are supported by a large and active community for improvements and fixes,
and they also offer the flexibility for Netezza to add corrections or improvements
on a faster basis, without waiting for updates from third-party vendors.
All the Netezza models except the Netezza 100 are HA systems, which means that
they have two host servers for managing Netezza operations. The host server
(often called host within the publication) is a Linux server that runs the Netezza
software and utilities.
Linux-HA and DRBD overview

High-Availability Linux (also called Linux-HA) provides the failover capabilities
from a primary or active IBM Netezza host to a secondary or standby Netezza
host. The main cluster management daemon in the Linux-HA solution is called
Heartbeat. Heartbeat watches the hosts and manages the communication and status
checks of services. Each service is a resource. Netezza groups the Netezza-specific
services into the nps resource group. When Heartbeat detects problems that imply
a host failure condition or loss of service to the Netezza users, Heartbeat can
initiate a failover to the standby host. For details about Linux-HA and its terms
and operations, see the documentation at http://www.linux-ha.org.
Distributed Replicated Block Device (DRBD) is a block device driver that mirrors
the content of block devices (hard disks, partitions, and logical volumes) between
the hosts. Netezza uses the DRBD replication only on the /nz and /export/home
partitions. As new data is written to the /nz partition and the /export/home
partition on the primary host, the DRBD software automatically makes the same
changes to the /nz and /export/home partition of the standby host.
The Netezza implementation uses DRBD in a synchronous mode, which is a tightly

coupled mirroring system. When a block is written, the active host does not record
the write as complete until both the active and the standby hosts successfully write
the block. The active host must receive an acknowledgement from the standby host
that it also completed the write. Synchronous mirroring (DRBD protocol C) is most
often used in HA environments that want the highest possible assurance of no lost
transactions if the active node fails over to the standby node. Heartbeat typically
controls the DRBD services, but commands are available to manually manage the
services.
For details about DRBD and its terms and operations, see the documentation at
http://www.drbd.org.

Differences with the previous Netezza HA solution
In previous releases, the IBM Netezza HA solution used the Red Hat Cluster
Manager as the foundation for managing HA host systems. The Linux-HA solution
uses different commands to manage the cluster. The following table outlines the
common tasks and the commands that are used in each HA environment.
Table 4-1. HA tasks and commands (Old design and new design)
Old command (Cluster
Task Manager) New command (Linux-HA)
Display cluster status clustat -i 5 crm_mon -i5
Relocate NPS service cluadmin -- service /nzlocal/scripts/
relocate nps heartbeat_admin.sh --migrate
Enable the NPS cluadmin -- service crm_resource -r nps -p target_role
service enable nps -v started
Disable the NPS cluadmin -- service crm_resource -r nps -p target_role
service disable nps -v stopped
Start the cluster on service cluster start service heartbeat start
each node
Stop the cluster on service cluster stop service heartbeat stop
each node
Some additional points of differences between the solutions:

v All Linux-HA and DRBD logging information is written to /var/log/messages
on each host.
v In the new cluster environment, pingd replaces netchecker (the Network Failure
Daemon). pingd is a built-in part of the Linux-HA suite.
v The cluster manager HA solution also required a storage array (the MSA500) as
a quorum disk to hold the shared data. A storage array is not used in the new
Linux-HA/DRBD solution, as DRBD automatically mirrors the data in the /nz
and /export/home partitions from the primary host to the secondary host.
Note: The /nzdata and /shrres file systems on the MSA500 are deprecated.
v In some customer environments that used the previous cluster manager solution,
it was possible to have only the active host running while the secondary was
powered off. If problems occurred on the active host, the Netezza administrator
on-site would power off the active host and power on the standby. In the new
Linux-HA DRBD solution, both HA hosts must be operational at all times.
DRBD ensures that the data saved on both hosts is synchronized, and when
Heartbeat detects problems on the active host, the software automatically fails
over to the standby with no manual intervention.
Related concepts:
“Logging and messages” on page 4-12
Linux-HA administration
When you start an IBM Netezza HA system, Heartbeat automatically starts on both
hosts. It can take a few minutes for Heartbeat to start all the members of the nps
resource group. You can use the crm_mon command from either host to observe the
status, as described in “Cluster and resource group status” on page 4-5.

Heartbeat configuration
Heartbeat uses the /etc/ha.d/ha.cf configuration file first to load its configuration.
The file contains low-level information about fencing mechanisms, timing
parameters, and whether the configuration is v1 (old-style) or v2 (CIB). IBM
Netezza uses the v2 implementation.
CAUTION:
Do not modify the file unless directed to in Netezza documentation or by
Netezza Support.
Cluster Information Base

Most of the Heartbeat configuration is stored in the Cluster Information Base (CIB).
The CIB is on disk at /var/lib/heartbeat/crm/cib.xml. Heartbeat synchronizes it
automatically between the two Netezza hosts.
CAUTION:
Never manually edit the CIB file. You must use cibadmin (or crm_resource) to
modify the Heartbeat configuration. Wrapper scripts like heartbeat_admin.sh
update the file safely.
Note: It is possible to get into a situation where Heartbeat does not start properly
because of a manual CIB modification. The CIB cannot be safely modified if
Heartbeat is not started (that is, cibadmin cannot run). In this situation, you can
run /nzlocal/scripts/heartbeat_config.sh to reset the CIB and /etc/ha.d/ha.cf
to factory-default status. After you do this, it is necessary to run
/nzlocal/scripts/heartbeat_admin.sh --enable-nps to complete the CIB
configuration.
Important information about host 1 and host 2

In the Red Hat cluster manager implementation, the HA hosts were commonly
called HA1 and HA2. The terms stemmed from the hardware and rack
configurations as HA systems were typically multi-rack systems, and HA1 was
located in the first rack (usually the leftmost rack from the front), while HA2 was
located in the second rack of the HA system. Either HA1 or HA2 could serve as
the active or standby host, although HA1 was most often the “default” active host
and so HA1 is often synonymous with the active host. The names HA1 and HA2
are still used to refer to the host servers regardless of their active/standby role.
In IBM Netezza HA system designs, host1/HA1 is configured by default to be the

active host. You can run cluster management commands from either the active or
the standby host. The nz commands must be run on the active host, but the
commands run the same regardless of whether host 1 or host 2 is the active host.
The Netezza software operation is not affected by the host that it runs on; the
operation is identical when either host 1 or host 2 is the active host.
However, when host 1 is the active host, certain system-level operations such as
S-Blade restarts and system reboots often complete more quickly than when host
2/HA2 is the active host. An S-Blade restart can take one to two minutes longer to
complete when host 2 is the active host. Certain tasks such as manufacturing and
system configuration scripts can require host 1 to be the active host, and they
display an error if run on host 2 as the active host. The documentation for these
commands indicates whether they require host 1 to be the active host, or if special
steps are required when host 2 is the active host.
Chapter 4. Manage Netezza HA systems 4-3

Failover timers
There are several failover timers that monitor Heartbeat operations and timings.
The default settings cover the general range of IBM Netezza system
implementations. Although Netezza has not encountered many cases where
environments require different values, each customer environment is unique. Do
not change failover timers without consultation from Netezza Support.
The failover timers are configured in /etc/ha.d/ha.cf.

Deadtime
Specifies the failure detection time (default: 30 seconds). For a busy
Netezza system in a heavily loaded environment, you might increase this
value if you observe frequent No local heartbeat errors or Cluster node
returning after partition errors in the /var/log/messages file.
Warntime
Specifies the warning for late heartbeat (default: 10 seconds).
Keepalive
Specifies the interval between liveness pings (default: 2 seconds).
You can change the settings by editing the values in ha.cf on both hosts and
restarting Heartbeat, but use care when you are editing the file.
Netezza cluster management scripts

IBM Netezza provides wrapper scripts for many of the common cluster
management tasks. These wrapper scripts help to simplify the operations and to
guard against accidental configuration changes that can cause the Netezza HA
operations to fail.
The following table lists the common commands. These commands are listed here
for reference.
Table 4-2. Cluster management scripts
Type Scripts
Initial installation heartbeat_config.sh sets up Heartbeat for the first time
scripts
heartbeat_admin.sh --enable-nps adds Netezza services to
cluster control after initial installation
Host name change heartbeat_admin.sh --change-hostname
Fabric IP change heartbeat_admin.sh --change-fabric-ip
Wall IP change heartbeat_admin.sh --change-wall-ip
Manual migrate heartbeat_admin.sh --migrate
(relocate)
Linux-HA status and crm_mon monitors cluster status
troubleshooting
commands crm_verify sanity checks configuration, and prints status
The following is a list of other Linux-HA commands available. This list is also
provided as a reference, but do not use any of these commands unless directed to
by Netezza documentation or by Netezza Support.
Linux-HA configuration commands:

cibadmin
Main interface to modify configuration
crm_resource
Shortcut interface for modifying configuration
crm_attribute
Shortcut interface for modifying configuration
crm_diff
Diff and patch two different CIBs
Linux-HA administration commands:

crmadmin
Low-level query and control
crm_failcount
Query and reset failcount
crm_standby
Mark a node as standby, usually for maintenance
Active and standby nodes

There are two ways to determine which IBM Netezza host is the active host and
which is the standby.
v Use the crm_resource command.
v Review the output of the crm_mon command.
A sample crm_resource command and its output follow.

[root@nzhost1 ~]# crm_resource -r nps -W
crm_resource[5377]: 2009/01/31_10:13:12 info: Invoked: crm_resource -r

nps -W
resource nps is running on: nzhost1
The command output displays a message about how it was started, and then
displays the host name where the nps resource group is running. The host that
runs the nps resource group is the active host.
You can obtain more information about the state of the cluster and which host is
active by using the crm_mon command. See the sample output that is shown in
“Cluster and resource group status.”
If the nps resource group is unable to start, or if it has been manually stopped
(such as by crm_resource -r nps -p target_role -v stopped), neither host is
considered the active host and the crm_resource -r nps -W command does not
return a host name.
Cluster and resource group status

To check the state of the cluster and the nps resource group, run the following
command:
crm_mon -i5
Sample output follows. This command refreshes its display every 5 seconds, but
you can specify a different refresh rate (for example, -i10 is a 10-second refresh
rate). Press Control-C to exit the command.

[root@nzhost1 ~]# crm_mon -i5
============
Last updated: Wed Sep 30 13:42:39 2009
Current DC: nzhost1 (key)
2 Nodes configured.
3 Resources configured.
============
Node: nzhost1 (key): online
Resource Group: nps
drbd_exphome_device (heartbeat:drbddisk): Started nzhost1
drbd_nz_device (heartbeat:drbddisk): Started nzhost1
exphome_filesystem (heartbeat::ocf:Filesystem): Started nzhost1
nz_filesystem (heartbeat::ocf:Filesystem): Started nzhost1
fabric_ip (heartbeat::ocf:IPaddr): Started nzhost1
wall_ip (heartbeat::ocf:IPaddr): Started nzhost1
nz_dnsmasq (lsb:nz_dnsmasq): Started nzhost1
nzinit (lsb:nzinit): Started nzhost1
fencing_route_to_ha1 (stonith:apcmaster): Started nzhost2
The host that is running the nps resource group is the active host. Every member
of the nps resource group starts on the same host. The sample output shows that
they are all running on nzhost1.
The crm_mon output also shows the name of the Current Designated Coordinator
(DC). The DC host is not an indication of the active host. The DC is an
automatically assigned role that Linux-HA uses to identify a node that acts as a
coordinator when the cluster is in a healthy state. This is a Linux-HA
implementation detail and does not affect Netezza. Each host recognizes and
recovers from failure, regardless of which one is the DC. For more information
about the DC and Linux-HA implementation details, see http://www.linux-
ha.org/DesignatedCoordinator.
The resources under the nps resource group are as follows:

v The DRBD devices:
v Both file system mounts:
v The 10.0.0.1 IP setup on the fabric interface:
v The floating wall IP (external IP for HA1 + 3):
v The DNS daemon for Netezza:
v The Netezza daemon which performs prerequisite work and then starts the
Netezza software:
The fence routes for internal Heartbeat use are not part of the nps resource group.
If these services are started, it means that failovers are possible:

The nps resource group
The nps resource group contains the following services or resources:
v drbd_exphome_device
v drbd_nz_device
v exphome_filesystem
v nz_filesystem
v fabric_ip
v wall_ip
v nz_dnsmasq
v nzinit
The order of the members of the group matters; group members are started
sequentially from first to last. They are stopped sequentially in reverse order, from
last to first. Heartbeat does not attempt to start the next group member until the
previous member starts successfully. If any member of the resource group is unable
to start (returns an error or times out), Heartbeat performs a failover to the
standby node.
Failover criteria
During a failover or resource migration, the nps resource group is stopped on the
active host and started on the standby host. The standby host then becomes the
active host.
It is important to differentiate between a resource failover and a resource migration

(or relocation). A failover is an automated event which the cluster manager
performs without human intervention when it detects a failure case. A resource
migration occurs when an administrator intentionally moves the resources to the
standby.
A failover can be triggered by any of the following events:

v Both maintenance network links to the active host are lost.
v All fabric network links to the active host are lost.
v A user manually stops Heartbeat on the active host.
v The active host is cleanly shut down, such as if someone issued the command
shutdown -h on that host.
v The active host is uncleanly shut down, such as during a power failure to the
system (both power supplies fail).
v If any member of the nps resource group cannot start properly when the
resource group is initially started.
v If any one of the following members of the nps resource group fails after the
resource group was successfully started:
– drbd_exphome_device or drbd_nz_device: These correspond to low-level
DRBD devices that serve the shared file systems. If these devices fail, the
shared data would not be accessible on that host.
– exphome_filesystem or nz_filesystem: These are the actual mounts for the
DRBD devices.
– nz_dnsmasq: The DNS daemon for the IBM Netezza system.
Note: If any of these resource group members experiences a failure, Heartbeat first
tries to restart or repair the process locally. The failover is triggered only if that

repair or restart process does not work. Other resources in the group that are not
listed previously are not monitored for failover detection.
The following common situations do not trigger a failover:

v Any of the failover criteria that occurs on the STANDBY host while the active
host is working correctly.
Heartbeat might decide to fence (forcibly power cycle) the standby host when it
detects certain failures to try to restore the standby host to a state of good
health.
v A single maintenance network link to the active host is lost.
v Losing some (but not all) of the fabric network links to the active host.
v Network connectivity from the Netezza host (either active or standby) to the
customer network is lost.
v One or both network connections that serve the DRBD network fail.
Relocate to the standby node

The following commands can be used to manually relocate the nps resource group
from the active IBM Netezza node to the standby node. At the conclusion of this
process, the standby node becomes the active node and the previous active node
becomes the standby.
Note: In the previous Netezza Cluster Manager solution, HA1 is the name of the
primary node, and HA2 the secondary node. In Linux-HA/DRBD, either host can
be primary; thus, these procedures call one host as the active host and one as the
standby host.
To relocate the nps resource group from the active host to the standby host:
[root@nzhost1 ~]# /nzlocal/scripts/heartbeat_admin.sh --migrate
Testing DRBD communication channel...Done.
Checking DRBD state...Done.
Migrating the NPS resource group from NZHOST1 to

NZHOST2................................................Complete.
20100112_084039 INFO : Run crm_mon to check NPS’ initialization
status.
The command blocks until the nps resource group stops completely. To monitor
the status, use the crm_mon -i5 command. You can run the command on either
host, although on the active host you must run it from a different terminal
window.
Safe manual control of the hosts and Heartbeat

About this task
In general, you should not have to stop Heartbeat unless the IBM Netezza HA
system requires hardware or software maintenance or troubleshooting. During
these times, it is important that you control Heartbeat to ensure that it does not
interfere with your work by taking STONITH actions to regain control of the hosts.
The recommended practice is to shut down Heartbeat completely for service.
To shut down the nps resource group and Heartbeat, complete the following steps:
Procedure
1. Identify which node is the active node by using the following command:

2. Stop Heartbeat on the standby Netezza host:
[root@nzhost2 ~]# service heartbeat stop
Stopping High-Availability services:
[ OK ]
This command blocks until it completes successfully. Wait and let the command
complete. You can check /var/log/messages for status messages, or you can
monitor progress on a separate terminal session by using either of the
following commands: tail -f /var/log/messages or crm_mon -i5.
3. Stop Heartbeat on the active Netezza host:
Stopping High-Availability services:
[ OK ]
In some rare cases, the Heartbeat cannot be stopped by using this process. In
these cases, you can force Heartbeat to stop as described in “Force Heartbeat to
shut down” on page 4-16.
Related concepts:
“Shut down Heartbeat on both nodes without causing relocate” on page 4-16
Transitioning to maintenance (non-Heartbeat) mode

About this task
To enter maintenance mode, complete the following steps:
Procedure
1. While logged in to either host as root, display the name of the active node:
2. As root, stop Heartbeat on the standby node (nzhost2 in this example):
3. As root, stop Heartbeat on the active node:
4. As root, make sure that there are no open nz sessions or any open files in the
shared directories /nz, /export/home, or both. For details, see “Checking for
user sessions and activity” on page 4-18.
[root@nzhost1 ~]# lsof /nz /export/home
5. Run the following script in /nzlocal/scripts to make the IBM Netezza system
ready for non-clustered operations. The command prompts you for a
confirmation to continue, shown as Enter in the output.
[root@nzhost1 ~]# /nzlocal/scripts/nz.non-heartbeat.sh
---------------------------------------------------------------
Thu Jan 7 15:13:27 EST 2010
File systems and eth2 on this host are okay. Going on.
File systems and eth2 on other host are okay. Going on.
This script will configure Host 1 or 2 to own the shared disks and
own the fabric.
When complete, this script will have:

mounted /export/home and /nz
aliased 10.0.0.1 on eth2
run the rackenable script appropriate for this host

based on the last octet of eth2
being 2 for rack 1 or 3 for rack 2
To proceed, please hit enter. Otherwise, abort this. Enter
Okay, we are proceeding.

Thu Jan 7 15:13:29 EST 2010
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda6 16253924 935980 14478952 7% /
/dev/sda10 8123168 435272 7268604 6% /tmp
/dev/sda9 8123168 998808 6705068 13% /usr
/dev/sda8 8123168 211916 7491960 3% /var
/dev/sda7 8123168 500392 7203484 7% /opt
/dev/sda3 312925264 535788 296237324 1% /nzscratch
/dev/sda1 1019208 40192 926408 5% /boot
none 8704000 2228 8701772 1% /dev/shm
/dev/sda12 4061540 73940 3777956 2% /usr/local
/dev/drbd0 16387068 175972 15378660 2% /export/home
/dev/drbd1 309510044 5447740 288340020 2% /nz
Done mounting file systems
eth2:0 Link encap:Ethernet HWaddr 00:07:43:05:8E:26
inet addr:10.0.0.1 Bcast:10.0.15.255 Mask:255.255.240.0
UP BROADCAST RUNNING MULTICAST MTU:9000 Metric:1
Interrupt:122 Memory:c1fff000-c1ffffff
Done enabling IP alias
Running nz_dnsmasq: [ OK ]
nz_dnsmasq started.
Ready to use NPS in non-cluster environment

6. As the nz user, start the Netezza software:
[nz@nzhost1 ~] nzstart
Transitioning from maintenance to clustering mode

About this task
To reinstate the cluster from a maintenance mode, complete the following steps:
Procedure
1. Stop the IBM Netezza software by using the nzstop command.
2. Make sure that Heartbeat is not running on either node. Use the service
heartbeat stop command to stop the Heartbeat on either host if it is running.
3. Make sure that there are no nz user login sessions, and make sure that no users
are in the /nz or /export/home directories. Otherwise, the nz.heartbeat.sh
command is not able to unmount the DRBD partitions. For details, see
“Checking for user sessions and activity” on page 4-18.
4. Run the following script in /nzlocal/scripts to make the Netezza system
ready for clustered operations. The command prompts you for a confirmation
to continue, shown as Enter in the output.
[root@nzhost1 ~]# /nzlocal/scripts/nz.heartbeat.sh
---------------------------------------------------------------
Thu Jan 7 15:14:32 EST 2010
This script will configure Host 1 or 2 to run in a cluster
When complete, this script will have:

unmounted /export/home and /nz
Disabling IP alias 10.0.0.1 from eth2
To proceed, please hit enter. Otherwise, abort this. Enter

Okay, we are proceeding.
Thu Jan 7 15:14:33 EST 2010
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda6 16253924 935980 14478952 7% /
/dev/sda10 8123168 435272 7268604 6% /tmp
/dev/sda9 8123168 998808 6705068 13% /usr
/dev/sda8 8123168 211928 7491948 3% /var
/dev/sda7 8123168 500544 7203332 7% /opt
/dev/sda3 312925264 535788 296237324 1% /nzscratch
/dev/sda1 1019208 40192 926408 5% /boot
none 8704000 2228 8701772 1% /dev/shm
/dev/sda12 4061540 73940 3777956 2% /usr/local
Done unmounting file systems
eth2:0 Link encap:Ethernet HWaddr 00:07:43:05:8E:26
UP BROADCAST RUNNING MULTICAST MTU:9000 Metric:1
Interrupt:122 Memory:c1fff000-c1ffffff
Done disabling IP alias

Shutting down dnsmasq: [ OK ]
nz_dnsmasq stopped.
Ready to use NPS in a cluster environment
Note: If the command reports errors that it is unable to unmount /nz or

/export/home, you must manually make sure that both partitions are mounted
before you run the command again. The script might unmount one of the
partitions, even if the script failed. Otherwise, the script might not run.
5. As root, start the cluster on the first node, which becomes the active node:
[root@nzhost1 ~] service heartbeat start
Starting High-Availability services:
[ OK ]
6. As root, start the cluster on the second node, which becomes the standby node:
[root@nzhost2 ~] service heartbeat start
Starting High-Availability services:
[ OK ]
Configuring Cluster Manager events

About this task
You can configure the Cluster Manager to send events when a failover is caused by
any of the following events:
v Node shutdown
v Node restart
v Node fencing actions (STONITH actions)
To configure the Cluster Manager, complete the following steps:
Procedure
1. Log in to the active host as the root user.
2. Using a text editor, edit the /nzlocal/maillist file as follows. Add the lines
that are shown in bold.
#
#Email notification list for the cluster manager problems
#
#Enter email addresses of mail recipients under the TO entry, one
to a line
#
#Enter email address of from email address (if a non-default is
desired)

#under the FROM entry
#
TO:
admin1@yourcompany.com
admin2@yourcompany.com
FROM:
NPS001ClusterManager@yourcompany.com
For the TO: email addresses, specify one or more email addresses for the users
who want to receive email about cluster manager events. For the FROM: email
address, specify the email address that you want to use as the sender of the
event email.
3. Save and close the maillist file.
4. Log in as root to the standby host and repeat steps 2 on page 4-11 and 3 on the
standby host.
The /nzlocal/maillist files must be identical on both hosts in the cluster.
5. After you configure the maillist files, test the event mail by shutting down or
restarting either host in the cluster. Your specified TO addresses will receive
email about the event.
Logging and messages

All the logging information is stored in the /var/log/messages file on each host.
The log file on the active host typically contains more information, but messages
can be written to the log files on both hosts. Any event or change in status for
Heartbeat is documented in this log file. If something goes wrong, you can often
find the explanation in this log file. If you are working with IBM Netezza Support
to troubleshoot Linux-HA or DRBD issues, be sure to send a copy of the log files
from both Netezza hosts.
Related reference:
“Differences with the previous Netezza HA solution” on page 4-2
DRBD administration
DRBD provides replicated storage of the data in managed partitions (that is, /nz
and /export/home). When a write occurs to one of these locations, the write action
occurs at both the local node and the peer standby node. Both perform the same
write to keep the data in synchronization. The peer responds to the active node
when finished, and if the local write operation is also successfully finished, the
active node reports the write as complete.
Read operations are always performed by the local node.
The DRBD software can be started, stopped, and monitored by using the
/sbin/service drbd start/stop/status command (as root):
While you can use the status command as needed, only stop and start the DRBD
processes during routine maintenance procedures or when directed by IBM
Netezza Support. Do not stop the DRBD processes on an active, properly working
Netezza HA host to avoid the risk of split-brain.
Related tasks:
“Detecting split-brain” on page 4-14

Monitor DRBD status
You can monitor the DRBD status by using one of two methods:
v service drbd status
v cat /proc/drbd
Sample output of the commands follows. These examples assume that you are
running the commands on the primary (active) IBM Netezza host. If you run them
from the standby host, the output shows the secondary status first, then the
primary.
[root@nzhost1 ~]# service drbd status
drbd driver loaded OK; device status:
version: 8.2.6 (api:88/proto:86-88)
GIT-hash: 3e69822d3bb4920a8c1bfdf7d647169eba7d2eb4 build by root@nps22094, 2009-06-09
16:25:53
m:res cs st ds p mounted fstype
0:r1 Connected Primary/Secondary UpToDate/UpToDate C /export/home ext3
1:r0 Connected Primary/Secondary UpToDate/UpToDate C /nz ext3
[root@nzhost1 ~]# cat /proc/drbd
version: 8.2.6 (api:88/proto:86-88)
GIT-hash: 3e69822d3bb4920a8c1bfdf7d647169eba7d2eb4 build by root@nps22094, 2009-06-09
16:25:53
0: cs:Connected st:Primary/Secondary ds:UpToDate/UpToDate C r---
ns:15068 nr:1032 dw:16100 dr:3529 al:22 bm:37 lo:0 pe:0 ua:0 ap:0 oos:0
1: cs:Connected st:Primary/Secondary ds:UpToDate/UpToDate C r---
ns:66084648 nr:130552 dw:66215200 dr:3052965 al:23975 bm:650 lo:0 pe:0 ua:0 ap:0 oos:0
In the sample output, the DRBD states are one of the following values:
Primary/Secondary
The "healthy" state for DRBD. One device is Primary and one is Secondary.
Secondary/Secondary
DRBD is in a suspended or waiting mode. This usually occurs at boot time
or when the nps resource group is stopped.
Primary/Unknown
One node is available and healthy, the other node is either down or the
cable is not connected.
Secondary/Unknown
This is a rare case where one node is in standby, the other is either down
or the cable is not connected, and DRBD cannot declare a node as the
primary/active node. If the other host also shows this status, the problem
is most likely in the connection between the hosts. Contact Netezza
Support for assistance in troubleshooting this case.
The common Connection State values include the following values:

Connected
The normal and operating state; the host is communicating with its peer.
WFConnection
The host is waiting for its peer node connection; usually seen when other
node is rebooting.
Standalone
The node is functioning alone because of a lack of network connection
with its peer. It does not try to reconnect. If the cluster is in this state, it
means that data is not being replicated. Manual intervention is required to
fix this problem.

The common State values include the following values:
Primary
The primary image; local on active host.
Secondary
The mirror image, which receives updates from the primary; local on
standby host.
Unknown
Always on other host; state of image is unknown.
The common Disk State values include the following values:

UpToDate
The data on the image is current.
DUnknown
This value is an unknown data state; usually results from a broken
connection.
Sample DRBD status output

The DRBD status before Heartbeat start:
M:res cs st ds p mounted fstype
0:r1 Connected Secondary/Secondary UpToDate/UpToDate C
1:r0 Connected Secondary/Secondary UpToDate/UpToDate C
The DRBD status when the current node is active and the standby node is down:
0:r1 WFConnection Primary/Unknown UpToDate/DUnknown C /export/home ext3
1:r0 WFConnection Primary/Unknown UpToDate/DUnknown C /nz ext3
The DRBD status as displayed from the standby node:

0:r1 Connected Secondary/Primary UpToDate/UpToDate C
1:r0 Connected Secondary/Primary UpToDate/UpToDate C
Detecting split-brain
About this task
Split-brain is an error state that occurs when the images of data on each IBM
Netezza host are different. It typically occurs when synchronization is disabled and
users change data independently on each Netezza host. As a result, the two
Netezza host images are different, and it becomes difficult to resolve what the
latest, correct image should be.
Important: Split-brain does not occur if clustering is enabled. The fencing controls
prevent users from changing the replicated data on the standby node. Allow DRBD
management to be controlled by Heartbeat to avoid the split-brain problems.
However, if a split-brain problem occurs, the following message is written to the

/var/log/messages file:
Split-Brain detected, dropping connection!
While DRBD does have automatic correction processes to resolve split-brain

situations, the Netezza implementation disables the automatic correction. Manual
intervention is required, which is the best way to ensure that as many of the data
changes are restored as possible.

To detect and repair split-brain, work with IBM Support to follow this procedure:
Procedure
1. Look for Split in /var/log/messages, usually on the host that you are trying to
make the primary/active host. Let DRBD detect this condition.
2. Because split-brain results from running both images as primary Netezza hosts
without synchronization, check the Netezza logs on both hosts. For example,
check the pg.log files on both hosts to see when/if updates occur. If there is an
overlap in times, both images have different information.
3. Identify which host image, if either, is the correct image. In some cases, neither
host image might be fully correct. You must choose the image that is the more
correct. The host that has the image which you decide is correct is the
“survivor”, and the other host is the “victim”.
4. Perform the following procedure:
a. Log in to the victim host as root and run these commands:
drbdadm secondary resource
drbdadm disconnect resource
drbdadm -- --discard-my-data connect resource
where resource can be r0, r1, or all.

Complete these steps for one resource at a time; that is, run all the
commands in steps a. and b. for r0 and then repeat them all for r1. There is
an all option, but use it carefully. The individual resource commands
usually work more effectively.
b. Log in to the survivor host as root and run this command:
drbdadm connect resource
where resource can be r0, r1, or all
Note: The connect command might display an error that instructs you to
run drbdadm disconnect first.
5. Check the status of the fix by using drbdadm primary resource and the service
drbd status command. Make sure that you run drbdadm secondary resource
before you start Heartbeat.
Related concepts:
“DRBD administration” on page 4-12
Administration reference and troubleshooting

The following sections describe some common administration task references and
troubleshooting steps.
IP address requirements
The following table is an example block of the eight IP addresses that are
recommended for a customer to reserve for an HA system:
Table 4-3. HA IP addresses
Entity Sample IP address
HA1 172.16.103.209
HA1 Host Management 172.16.103.210
Floating IP 172.16.103.212

Table 4-3. HA IP addresses (continued)
Entity Sample IP address
HA2 172.16.103.213
HA2 Host Management 172.16.103.214
Reserved 172.16.103.215
Reserved 172.16.103.216
In the IP addressing scheme, there are two host IPs, two host management IPs, and
the floating IP, which is HA1 + 3.
Force Heartbeat to shut down

There might be times when you try to stop Heartbeat by using the normal process
as described in “Safe manual control of the hosts and Heartbeat” on page 4-8, but
Heartbeat does not stop even after it waits a few minutes. If you must stop
Heartbeat, you can use the following command to force Heartbeat to stop itself:
crmadmin -K hostname
You must run this command twice. Then, try to stop Heartbeat again by using
service heartbeat stop. This process might not stop all of the resources that
Heartbeat manages, such as /nz mount, drbd devices, nzbootpd, and other
resources.
Shut down Heartbeat on both nodes without causing relocate

If you stop Heartbeat on the active node first, Linux-HA identifies this as a
resource failure and initiates a failover to the standby node. To avoid this, always
stop Heartbeat on the standby first. After it stops completely, you can stop
Heartbeat on the active node.
Related tasks:
“Safe manual control of the hosts and Heartbeat” on page 4-8
Restart Heartbeat after maintenance network issues

If a host loses its maintenance network connection to the system devices, the IBM
Netezza HA system performs a fencing operation (STONITH) to stop the failed
host. After the host restarts, Heartbeat fails to start on the reboot. After the
maintenance network is repaired, you must manually restart Heartbeat to resume
normal cluster operations. To restart Heartbeat on the recovered node, log in to
that host as root and use the service heartbeat start command.
Resolve configuration problems

If you make a configuration change to the nps resource group or Heartbeat, and
there are problems after the change, you can often diagnose the problem from the
status information of the crm_verify command:
crm_verify -LVVVV
You can specify one or more V characters. The more Vs that you specify, the more
verbose the output. Specify at least four or five Vs and increase the number as
needed. You can specify up to 12 Vs, but that large a number is not recommended.

[root@ nzhost1 ha.d]# crm_verify -LVVV
crm_verify[18488]: 2008/11/18_00:02:03 info: main: =#=#=#=#= Getting XML
=#=#=#=#=
crm_verify[18488]: 2008/11/18_00:02:03 info: main: Reading XML from: live
cluster
crm_verify[18488]: 2008/11/18_00:02:03 notice: main: Required feature set:
1.1
crm_verify[18488]: 2008/11/18_00:02:03 notice: cluster_option: Using
default value ’60s’ for cluster option ’cluster-delay’
default value ’-1’ for cluster option ’pe-error-series-max’
default value ’-1’ for cluster option ’pe-warn-series-max’
default value ’-1’ for cluster option ’pe-input-series-max’
default value ’true’ for cluster option ’startup-fencing’
crm_verify[18488]: 2008/11/18_00:02:03 info: determine_online_status:
Node nzhost1 is online
crm_verify[18488]: 2008/11/18_00:02:03 info: determine_online_status:
Node nzhost2 is online
Fixed a problem, but crm_mon still shows failed items

Heartbeat sometimes leaves error status on crm_mon output, even after an item is
fixed. To resolve this problem, use crm_resource in Cleanup Mode:
crm_resource -r name_of_resource -C -H hostname
For example, if the fencing route to ha1 is listed as failed on host1, use the
crm_resource -r fencing_route_to_ha1 -C -H host1 command.
Output from crm_mon does not show the nps resource group
If the log messages indicate that the nps resource group cannot run anywhere, the
cause is that Heartbeat tried to run the resource group on both HA1 and HA2, but
it failed in both cases. Search in /var/log/messages on each host to find this first
failure. Search from the bottom of the log for the message cannot run anywhere
and then scan upward in the log to find the service failures. You must fix the
problems that caused a service to fail to start before you can successfully start the
cluster.
After you fix the failure case, you must restart Heartbeat following the instructions
in “Transitioning from maintenance to clustering mode” on page 4-10.
Linux users and groups required for HA

To operate properly, Heartbeat requires the following Linux user and groups that
are added automatically to each of the IBM Netezza hosts during the Heartbeat
RPM installation:
v User: hacluster:x:750:750::/home/hacluster:/bin/bash
v Groups:
– hacluster:x:750:
– haclient:x:65:
Do not modify or remove the user or groups because those changes will impact
Heartbeat and disrupt HA operations on the Netezza system.
Related concepts:
“Initial system setup and information” on page 1-1

Checking for user sessions and activity
About this task
Open nz user sessions and nz user activity can cause the procedures to stop
Heartbeat and to return to clustering to fail. Use the nzsession command to see
whether there are active database sessions in progress. For example:
[nz@nzhost1 ~]$ nzsession -u admin -pw password
ID Type User Start Time PID Database State Priority
Name Client IP Client PID Command
----- ---- ----- ----------------------- ----- -------- ------
------------- --------- ---------- ------------------------
16748 sql ADMIN 14-Jan-10, 08:56:56 EST 4500 CUST active normal
127.0.0.1 4499 create table test_2
16753 sql ADMIN 14-Jan-10, 09:12:36 EST 7748 INV active normal
127.0.0.1 7747 create table test_s
16948 sql ADMIN 14-Jan-10, 10:14:32 EST 21098 SYSTEM active normal
127.0.0.1 21097 SELECT session_id, clien
The sample output shows three sessions: the last entry is the session that is created
to generate the results for the nzsession command. The first two entries are user
activity. Wait for those sessions to complete or stop them before you use the
nz.heartbeat.sh or nz.non-heartbeat.sh commands.
To check for connections to the /export/home and /nz directory, complete the
following steps:
Procedure
1. As the nz user on the active host, stop the IBM Netezza software:
[nz@nzhost1 ~]$ /nz/kit/bin/nzstop
2. Log out of the nz account and return to the root account; then use the lsof
command to list any open files that are in /nz or /export/home.
Results
The output that is displayed will look similar to this:

[root@nzhost1 ~]# lsof /nz /export/home
COMMAND PID USER FD TYPE DEVICE SIZE NODE NAME
bash 2913 nz cwd DIR 8,5 4096 1497025 /export/home/nz
indexall. 4493 nz cwd DIR 8,5 4096 1497025 /export/home/nz
less 7399 nz cwd DIR 8,5 4096 1497025 /export/home/nz
lsof 13205 nz cwd DIR 8,5 4096 1497025 /export/home/nz
grep 13206 nz cwd DIR 8,5 4096 1497025 /export/home/nz
tail 22819 nz 3r REG 8,5 146995 1497188 /export/home/nz/f_5.log
This example shows several open files in the /export/home directory. If necessary,
you can close open files by issuing a command such as kill and supplying the
process ID (PID) shown in the second column from the left. Use caution with the
kill command; if you are not familiar with Linux system commands, contact
Support or your Linux system administrator for assistance.

Chapter 5. Manage the Netezza hardware
This section describes administration tasks for hardware components of the IBM
Netezza appliance. Most of the administration tasks focus on obtaining status and
information about the operation of the appliance, and in becoming familiar with
the hardware states. This section also describes tasks to perform if a hardware
component fails.
Netezza hardware components

The IBM Netezza appliance has a number of hardware components that support
the operation of the device. The Netezza appliance consists of one or more racks of
hardware, with host servers, switches, SPUs, disks, power controllers, cooling
devices, I/O cards, management modules, and cables. However, in the day-to-day
administration of the device, only a subset of these components require
administrative attention of any kind. Many of these components are redundant and
hot-swappable to ensure highly available operation of the hardware.
The following table lists the key hardware components to monitor:

Table 5-1. Key Netezza hardware components to monitor
Component Description Comments/Management Focus
Host Each Netezza HA system has one or Tasks include monitoring of the
servers two host servers to run the Netezza hardware status of the active/standby
software and supporting applications. hosts, and occasional monitoring of
If a system has two host servers, the disk space usage on the hosts. At
hosts operate in a highly available times, the host might require Linux
(HA) configuration; that is, one host OS or health driver upgrades to
is the active or primary host, and the improve its operational software.
other is a standby host ready to take
over if the active host fails.
Snippet SPAs contain the SPUs and associated Tasks include monitoring of the SPA
processing disk storage which drive the query environment, such as fans, power,
arrays processing on the Netezza appliance. and temperature. SPUs and disks are
(SPAs) IBM Netezza 100 systems have one monitored separately.
host server and thus are not HA
configurations.
Snippet SPUs provide the CPU, memory, and Tasks include monitoring the status
Processing Netezza FPGA processing power for of each SPU. If a SPU fails, the disks
Units the queries that run on the system. that it “owns” are redirected to other
(SPUs) SPUs for processing ownership.
Storage In the IBM Netezza High Capacity Tasks include monitoring the status
group Appliance C1000 model, disks reside of the disks within the storage group.
within a storage group. The storage
group consists of three disk
enclosures: an intelligent storage
enclosure with redundant hardware
RAID controllers, and two expansion
disk enclosures. There are four
storage groups in each Netezza C1000
rack.

Table 5-1. Key Netezza hardware components to monitor (continued)
Component Description Comments/Management Focus
Disks Disks are the storage media for the Tasks include monitoring the health
user databases and tables that are and status of the disk hardware. If a
managed by the Netezza appliance. disk fails, tasks include regenerating
the disk to a spare and replacing the
disk.
Data slices Data slices are virtual partitions on Tasks include monitoring the
the disks. They contain user mirroring status of the data slices and
databases and tables, and their also the space consumption of the
content is mirrored to ensure HA data slice.
access to the data in the event of a
disk failure.
Fans and These components control the Tasks include monitoring the status
blowers thermal cooling for the racks and of the fans and blowers, and if a
components such as SPAs and disk component fails, replacing the
enclosures. component to ensure proper cooling
of the hardware.
Power These components provide electrical Tasks include monitoring the status
supplies power to the various hardware of the power supplies, and if a
components of the system. component fails, replacing the
component to ensure redundant
power to the hardware.
The Netezza appliance uses SNMP events (described in Chapter 8, “Event rules,”
on page 8-1) and status indicators to send notifications of any hardware failures.
Most hardware components are redundant; thus, a failure typically means that the
remaining hardware components assume the work of the component that failed.
The system might or might not be operating in a degraded state, depending on the
component that failed.
CAUTION:
Never run the system in a degraded state for a long time. It is imperative to
replace a failed component in a timely manner so that the system returns to an
optimal topology and best performance.
Netezza Support and Field Service work with you to replace failed components to
ensure that the system returns to full service as quickly as possible. Most of the
system components require Field Service support to replace. Components such as
disks can be replaced by customer administrators.
Display hardware components

You use the nzhw show command to display information about the hardware
components of your IBM Netezza system. You can also use the NzAdmin tool or
IBM Netezza Performance Portal interface to display hardware information and
status.
The following figure shows some sample output of the nzhw show command:

Figure 5-1. Sample nzhw show output
Legend:
1 Hardware type
2 Hardware ID
3 Hardware role
4 Hardware state
5 Security
For an IBM Netezza High Capacity Appliance C1000 system, the output of the
nzhw show command: includes information about the storage groups:
Chapter 5. Manage the Netezza hardware 5-3

Figure 5-2. Sample nzhw show output for Netezza C1000
Related reference:
“The nzhw command” on page A-28
Use the nzhw command to manage the hardware of the IBM Netezza system.
Hardware types
Each hardware component of the IBM Netezza system has a type that identifies the
hardware component.
The following table describes the hardware types. You see these types when you
run the nzhw command or display hardware by using the NzAdmin or IBM
Netezza Performance Portal UIs.
Table 5-2. Hardware description types
Description Comments
Rack A hardware rack for the Netezza system
SPA Snippet processing array (SPA)
SPU Snippet processing unit (SPU)
Disk enclosure A disk enclosure chassis, which contains the disk devices
Disk A storage disk, contains the user databases and tables
Fan A thermal cooling device for the system
Blower A fan pack used within the S-Blade chassis for thermal cooling
Power supply A power supply for an enclosure (SPU chassis or disk)
MM A management device for the associated unit (SPU chassis, disk
enclosure). These devices include the AMM and ESM components, or a
RAID controller for an intelligent storage enclosure in a Netezza C1000
system.
Store group A group of three disk enclosures within a Netezza C1000 system
managed by redundant hardware RAID controllers
Ethernet switch Ethernet switch (for internal network traffic on the system)
Host A high availability (HA) host on the Netezza appliance
SAS Controller A SAS controller within the Netezza HA hosts

Table 5-2. Hardware description types (continued)
Description Comments
Host disk A disk resident on the host that provides local storage to the host
Database A Netezza Database Accelerator Card (DAC), which is part of the
accelerator card S-Blade/SPU pair
Hardware IDs
Each hardware component has a unique hardware identifier (ID) that is in the
form of an integer, such as 1000, 1001, or 1014. You can use the hardware ID to
manage a specific hardware component, or to uniquely identify which component
in command output or other informational displays.
To display information about a component by the hardware ID, specify the ID in

the command as in the following example:
[nz@nzhost ~]$ nzhw show -id 1609
Description HW ID Location Role State Security
------------- ----- -------------------------- --------- ----------- --------
Disk 1609 spa1.diskEncl1.disk13 Active Ok Enabled
Hardware location
IBM Netezza uses two formats to describe the position of a hardware component
within a rack.
v The logical location is a string in a dot format that describes the position of a
hardware component within the Netezza rack. For example, the nzhw output that
is shown in Figure 5-1 on page 5-3 shows the logical location for components; a
Disk component description follows:
In this example, the location of the disk is in SPA 1, disk enclosure one, disk
position one.
Similarly, the disk location for a disk on a system shows the location including
storage group:
Disk 1029 spa1.storeGrp1.diskEncl2.disk5 Active Ok
v The physical location is a text string that describes the location of a component.
You can display the physical location of a component by using the nzhw locate
command. For example, to display the physical location of disk ID 1011:
[nz@nzhost ~]$ nzhw locate -id 1011
Turned locator LED ’ON’ for Disk: Logical
Name:’spa1.diskEncl4.disk1’ Physical Location:’1st Rack, 4th
DiskEnclosure, Disk in Row 1/Column 1’
As shown in the command output, the nzhw locate command also lights the
locator LED for components such as SPUs, disks, and disk enclosures. For
hardware components that do not have LEDs, the command displays the
physical location string.
The following figure shows an IBM PureData System for Analytics N200x-010
system with a closer view of the storage arrays and SPU chassis components and
locations.

Figure 5-3. IBM PureData System for Analytics N200x system components and locations
A Each IBM PureData System for Analytics N200x rack is one array of disk
enclosures. There are 12 enclosures in a full rack configuration, and IBM
PureData System for Analytics N200x-005 half racks have 6 enclosures.
Each disk enclosure has 24 disks, numbered 1 to 24 from left to right on
the front of the rack.
B SPU1 occupies slots 1 and 2. SPU3 occupies slots 3 and 4, up to SPU13
which occupies slots 13 and 14
C The disk enclosures
D Host 1, host 2, and a KVM
E SPU chassis
The following figure shows an IBM Netezza 1000-12 system or an IBM PureData
System for Analytics N1001-010 with a closer view of the storage arrays and SPU
chassis components and locations.

Figure 5-4. IBM Netezza system components and locations
A Each disk array has four disk enclosures. Each enclosure has 12 disks,
numbered as in the chart shown in the figure.
B SPU1 occupies slots 1 and 2. SPU3 occupies slots 3 and 4, up to SPU11
which occupies slots 11 and 12
C Disk array 1 with four enclosures.
D Disk array 2 with four enclosures.
E Host 1, host 2, and a KVM
F SPU chassis 1
G SPU chassis 2
For detailed information about the locations of various components in the front
and back of the system racks, see the Site Preparation and Specifications guide for
your model type.
The following figure shows an IBM PureData System for Analytics N3001-001
system with host and disk numbering.

Figure 5-5. IBM PureData System for Analytics N3001-001 components and locations
A The host marked in the figure is HA1. It is always placed in the rack
directly above HA2.
B The first disk in the host occupies the slot labeled as 0, the second one
occupies slot 1, and, following this pattern, the last disk resides in slot 23.
Sample output of the nzhw locate command on this system looks like the
following:
[nz@v10-12-h1 ~]$ nzhw locate -id 1011
Turned locator LED ’ON’ for disk: Logical Name:’spa1.diskEncl1.disk12’

Physical Location:’upper host, host disk in slot 11’.
Hardware roles
Each hardware component of the IBM Netezza system has a hardware role, which
represents how the hardware is being used. The following table describes the
hardware roles. You see these roles when you run the nzhw command or display
hardware status by using the NzAdmin or IBM Netezza Performance Portal UIs.
Table 5-3. Hardware roles
Role Description Comments
None The None role indicates that the hardware All active SPUs must be
is initialized, but it has yet to be discovered discovered before the system
by the Netezza system. This process can make the transition from
usually occurs during system startup the Discovery state to the
before any of the SPUs send their discovery Initializing state.
information.
Active The hardware component is an active Normal system state
system participant. Failing over this device
can impact the Netezza system.
In model N3001-001, for host disks 9 - 24,

this role means that the disk is currently
associated with the virtual SPU.

Table 5-3. Hardware roles (continued)
Role Description Comments
Assigned The hardware is transitioning from spare to Transitional state
active. In Netezza 100, IBM Netezza 1000,
IBM PureData System for Analytics
appliances, this is the role when a disk is
involved in a regeneration. It is not yet
active, so it cannot participate in queries.
Failed The hardware failed. It cannot be used as a Monitor your supply of spare
spare. After maintenance is performed, you disks. Do not operate without
must activate the hardware by using the spare disks.
nzhw command before it can become a
spare and used in the system.
Inactive The hardware is not available for any The Inactive role could refer to
system operations. an S-Blade that was
deactivated, or a new
In model N3001-001, for host disks 9 - 24, replacement disk that was
this role means that the disk is currently added to the system.
not associated with the virtual SPU. To
associate the disk with virtual SPU, run the For an S-Blade, you must
nzhw activate command. activate the hardware by using
the nzhw command before it
can become a spare and used
in the system.
After a new disk is added to

the system, its role is set to
Inactive. The disk transitions
to Sparing while the system
performs firmware checks,
updates, and formats the disk,
and then the disk becomes a
Spare.
Mismatched This role is specific to disks. If the disk has To use the disk as a spare,
a UUID that does not match the host activate it, otherwise, remove it
UUID, then it is considered mismatched. from the system. To delete it
You must activate the hardware by using from the system catalog, use
the nzhw command before it can become a the nzhw delete command.
spare and used in the system.
Spare The hardware is not used in the current Normal system state.
running Netezza system, but it is available
to become active in the event of a failover.
Sparing A replacement disk is in the process of A transitional system state
firmware updates and formatting. where a replacement disk is
checked and formatted before
it can become a spare disk.
Incompatible The hardware is incompatible with the Some examples are disks that
system. It must be removed and replaced are smaller in capacity than
with compatible hardware. the smallest disk in use, or
blade cards which are not
Netezza SPUs.
Hardware states
The state of a hardware component represents the power status of the hardware.
Each hardware component has a state.

The following table describes the hardware states for all components except a SPU.
SPU states are the system states, which are described in Table 7-3 on page 7-4.
You see these states when you run the nzhw command or display hardware status
by using the NzAdmin or IBM Netezza Performance Portal UIs.
Table 5-4. Hardware states
State Description Comments
None The None state indicates that the All active SPUs must be
hardware is initialized, but it has yet to discovered before the system can
be discovered by the IBM Netezza make the transition from the
system. This process usually occurs Discovery state to the Initializing
during system startup before any of the state. If any active SPUs are still
SPUs have sent their discovery in the booting state, there can be
information. an issue with the hardware
startup.
Ok The Netezza system has received the Normal state
discovery information for this device,
and it is working properly.
Down The device is turned off.
Invalid
Online The system is running normally. It can
service requests.
Missing The System Manager detects a new This typically occurs when a disk
device in a slot that was previously or SPU has been removed and
occupied but not deleted. replaced with a spare without
deleting the old device. The old
device is considered absent
because the System Manager
cannot find it within the system.
Unreachable The System Manager cannot The device may have been failed
communicate with a previously or physically removed from the
discovered device. system.
Critical The management module detects a Contact Netezza Support to
critical hardware problem, and the obtain help with identifying and
problem component amber service light troubleshooting the cause of the
might be illuminated. critical alarm.
Warning The system manager has detected a Contact Netezza Support to
condition that requires investigation. troubleshoot the warning
For example, a host disk may have condition and to determine
reported a predictive failure error whether a proactive replacement
(PFE), which indicates that the disk is is needed.
reporting internal errors.
Checking The system manager is checking or These are normal states for new
Firmware updating the firmware of a disk before replacement disks that are being
it can be brought online as a spare. checked and updated before they
Updating
are added to service.
Firmware
Unsupported The hardware component is not a Contact Netezza Support because
supported model for the appliance. the replacement part is not
supported on the appliance.
The System Manager also monitors the management modules (MMs) in the
system, which have a status view of all the blades in the system. As a result, you
might see messages similar to the following in the sysmgr.log file:

2011-05-18 13:34:44.711813 EDT Info: Blade in SPA 5, slot 11 changed
from state ’good’ to ’discovering’, reason is ’No critical or warning
events’
2011-05-18 13:35:33.172005 EDT Info: Blade in SPA 5, slot 11 changed
from state ’discovering’ to ’good’, reason is ’No critical or warning
events’
A transition from “good” to “discovering” indicates that the IMM (a management

processor on the blade) rebooted and that it is querying the blade hardware for
status. The blade remains in the “discovering” state during the query. The IMM
then determines whether the blade hardware state is good, warning, or critical, and
posts the result to the AMM. The System Manager reports the AMM status by
using these log messages. You can ignore these normal messages. However, if you
see a frequent number of these messages for the same blade, there might be an
issue with the IMM processor on that blade.
Data slices, data partitions, and disks

It is important to understand the relationship of SPUs, disks, data slices, and data
partitions in the IBM Netezza appliance. Netezza uses these terms to help identify
hardware components for system management tasks and troubleshooting events.
Disks
A disk is a physical drive on which data resides. In a Netezza system, host servers
have several disks that hold the Netezza software, host operating system, database
metadata, and sometimes small user files. The Netezza system also has many more
disks that hold the user databases and tables. Each disk has a unique hardware ID
to identify it.
For the IBM PureData System for Analytics N200x appliances, 24 disks reside in
each disk enclosure, and full rack models have 12 enclosures per rack for a total of
288 disks per rack.
For IBM Netezza 1000 or IBM PureData System for Analytics N1001 systems, 48
disks reside in one storage array; a full-rack system has two storage arrays for a
total of 96 disks.
For IBM PureData System for Analytics N3001-001 appliances, all disks are located
on two hosts. 16 out of 24 disks on each host are used for storing data slices.
Data slices
A data slice is a logical representation of the data that is saved on a disk. The data
slice contains “pieces” of each user database and table. When users create tables
and load their data, they distribute the data for the table across the data slices in
the system by using a distribution key. An optimal distribution is one where each
data slice has approximately the same amount of each user table as any other. The
Netezza system distributes the user data to all of the data slices in the system by
using a hashing algorithm.
Data partitions
A data partition is a logical representation of a data slice that is managed by a

specific SPU. That is, each SPU owns one or more data partitions, which contains
the user data that the SPU is responsible for processing during queries. For
example, in the IBM PureData System for Analytics N200x appliances, each SPU

typically owns 40 data partitions although one or two may own 32 partitions. For
example, in IBM Netezza 1000 or IBM PureData System for Analytics N1001
systems, each SPU typically owns 8 data partitions although one SPU has only 6
partitions. For a Netezza C1000 system, each SPU owns 9 data partitions by
default. SPUs could own more than their default number of partitions; if a SPU
fails, its data partitions are reassigned to the other active SPUs in the system. In
IBM PureData System for Analytics N3001-001 appliances, each of the two virtual
SPUs owns 14 data partitions.
IBM Netezza Storage Design

The following figure shows a conceptual overview of SPUs, disks, data slices, and
data partitions in an IBM Netezza 100, IBM Netezza 1000, IBM PureData System
for Analytics N1001, and IBM PureData System for Analytics N200x appliance.
Each SPU in an IBM Netezza system "owns" a set of data partitions where the user
data is stored. For the IBM Netezza 100, IBM Netezza 1000, and IBM PureData
System for Analytics N1001 systems, each SPU owns eight data partitions which
are numbered from 0 to 7. For IBM PureData System for Analytics N200x systems,
each SPU typically owns 40 data partitions which are numbered 0 through 39.
For SPU ID 1003, its first data partition (0) points to data slice ID 9, which is stored
on disk 1070. Each data partition points to a data slice. As an example, assume that
disk 1014 fails and its contents are regenerated to a spare disk ID 1024. In this
situation, the SPU 1003’s data partition 7, which previously pointed to data slice 16
on disk 1014, is updated to point to data slice 16 on the new disk 1024 (not
shown).

Figure 5-6. SPUs, disks, data slices, and data partitions
If a SPU fails, the system moves all its data slices to the remaining active SPUs for
management. The system moves them in pairs (the pair of disks that contain the
primary and mirror data slices of each other). In this situation, some SPUs that
normally had 8 partitions will now own 10 data partitions. You can use the nzds
command to review the data slices on the system and the SPUs that manage them.
Netezza C1000 Storage Design

In a Netezza C1000 system, each storage group has an intelligent storage controller
which resides in disk enclosure 3.
The intelligent storage controller contains two redundant RAID controllers that
manage the disks and associated hardware within a storage group. The RAID
controllers are caching devices, which improves the performance of the read and
write operations to the disks. The caches are mirrored between the two RAID
controllers for redundancy; each controller has a flash backup device and a battery
to protect the cache against power loss.
The RAID controllers operate independently of the Netezza software and hosts.
For example, if you stop the Netezza software (such as for an upgrade or other
maintenance tasks), the RAID controllers continue to run and manage the disks
within their storage group. It is common to see the activity LEDS on the storage
groups operating even when the Netezza system is stopped. If a disk fails, the
RAID controller initiates the recovery and regeneration process; the regeneration
continues to run even when the Netezza software is stopped. If you use the nzhw
command to activate, fail, or otherwise manage disks manually, the RAID
controllers ensure that the action is allowed at that time; in some cases, commands
return an error when the requested operation, such as a disk failover, is not
allowed.
The RAID controller caches are disabled when any of the following conditions
occur:
v Battery failure
v Cache backup device failure
v Peer RAID controller failure (that is, a loss of the mirrored cache)
When the cache is disabled, the storage group (and the Netezza system)
experiences a performance degradation until the condition is resolved and the
cache is enabled again.
The following figure shows an illustration of the SPU/storage mapping. Each SPU
in a Netezza C1000 system owns nine user data slices by default. Each data slice is
supported by a three disk RAID 5 storage array. The RAID 5 array can support a
single disk failure within the three-disk array. (More than one disk failure within
the three-disk array results in the loss of the data slice.) Seven disks within the
storage group in a RAID 5 array are used to hold important system information
such as the nzlocal, swap and log partition.
Figure 5-7. Netezza C1000 SPU and storage representation
A SPU
B Data slice 1
C Data slice 9
D nzlocal, swap, and log partitions
If a SPU fails, the system manager distributes the user data partitions and the
nzlocal and log partitions to the other active SPUs in the same SPU chassis. A

Netezza C1000 system requires a minimum of three active SPUs; if only three SPUs
are active and one fails, the system transitions to the down state.
IBM PureData System for Analytics N3001-001 storage design

Model N3001-001 uses 28 out of its 48 disks to store data in the warehouse. On
each of these disks, four equal disk partitions are created.
Each disk partition is used to store one copy of a data slice. Disks are divided into
groups of four with two disks from each host in such a group. In each group, there
are 16 disk partitions (four on every disk) that are used to store data slices with
four copies of every data slice.
Each of the data slices always uses disk partition 1, 2, 3, 4 from the disks in the
group.
Each host runs one virtual SPU. The data slice is owned by the virtual SPU that
runs on the host where the disk with the first disk partition of that SPU is
physically located.
Data mirroring for these disk partitions is handled on the software level by the
virtual SPU as RAID0 with 4 parties.
Remote disks are accessed using iSCSI using the network that connects two hosts.
In addition, there are 4 spare disks (2 per host) used as a target for the regen
operation of failed disks.

Figure 5-8. Model N3001-001 storage architecture overview. The figure presents how data slices are mapped to disk
partitions. A1 - A14 are data slices of the first SPU and B1 - B14 are data slices of the second SPU. The arrows show
how disk partitions are mirrored for data slices A1. This mirroring pattern is analogical for all other data slices.
One-host mode
When one of the hosts is not available, manually failed, or its SPU is manually
failed using nzhw, the system switches into one-host mode.
In this mode, only one virtual SPU is working and only two disks from each disk
group are used.
Each data slice is now stored on two disk partitions instead of four, and two data
slices must read data from the same disk.

Figure 5-9. Model N3001-001 storage architecture overview in one-host mode
System resource balance recovery

The system resource balance is an important part of overall system performance.
When a component fails, or when an administrator performs a manual failover, the
resulting configuration (that is, topology) can result in unequal workloads among
the resources and possible performance impacts.
For example, the default disk topology for IBM Netezza 100/1000 or IBM PureData
System for Analytics N1001 systems configures each S-Blade with eight disks that
are evenly distributed across the disk enclosures of its SPA, as shown in the
following figure. If disks failover and regenerate to spares, it is possible to have an
unbalanced topology where the disks are not evenly distributed among the
odd-numbered and even-numbered enclosures. This causes some of the SAS (also
called HBA) paths, which are shown as the dark lines that connect the blade
chassis to the disk enclosures, to carry more traffic than the others.

Figure 5-10. Balanced and unbalanced disk topologies
The System Manager can detect and respond to disk topology issues. For example,
if an S-Blade has more disks in the odd-numbered enclosures of its array, the
System Manager reports the problem as an overloaded SAS bus. You can use the
nzhw rebalance command to reconfigure the topology so that half of the disks are
in the odd-numbered enclosures and half in the even-numbered. The rebalance
process requires the system to transition to the “pausing now” state for the
topology update.
When the Netezza system restarts, the restart process checks for topology issues
such as overloaded SAS buses or SPAs that have S-Blades with uneven shares of
data slices. If the system detects a spare S-Blade for example, it will reconfigure the
data slice topology to distribute the workload equally among the S-Blades.
Related reference:
“Hardware path down” on page 8-20
“Rebalance data slices” on page 5-29
Hardware management tasks

This section describes some administration tasks for the hardware components that
are typically monitored and managed by IBM Netezza administrators.
These components include the following components:

v Hosts
v SPUs
v Disks
Other hardware components of the system do not have special administration

tasks. In general, if one of the other components such as a power supply, fan, host,
or other component fails, you are alerted. Netezza Support works with you to
schedule Service so that the failed components can be replaced to restore full
operations and hardware redundancy.

Callhome file
The callHome.txt file is in the /nz/data/config directory and it defines important
information about the IBM Netezza system such as primary and secondary
administrator contact information, and system information such as location, model
number, and serial number. Typically, the Netezza installation team member edits
this file for you when the Netezza system is installed on-site, but you can review
or edit the file as needed to ensure that the contact information is current.
Related reference:
“Add an event rule” on page 8-7
You can use the nzevent add command to add an event rule. You can also use the
NzAdmin tool to add event rules by using a wizard for creating events.
“Display a specific table” on page 16-12
You can use the nzstats command to display the statistics of a specific group or
table.
Display hardware issues

You can display a list of the hardware components that have problems and require
administrative attention by using the nzhw show -issues command.
This command displays such problems as components that have failed or

components that are in an “abnormal” state such as: disks that are assigned,
missing, incompatible, or unsupported; SPUs that are incompatible.
For example, the following command shows two failed disks on the system:
[nz@nzhost ~]$ nzhw show -issues
----------- ----- ---------------------- -------- ----------- --------
Disk 1498 spa1.diskEncl11.disk21 Failed Ok Disabled
Disk 1526 spa1.diskEncl9.disk4 Failed Ok Disabled
The disks must be replaced to ensure that the system has spares and an optimal
topology. You can also use the NzAdmin andIBM Netezza Performance Portal
interfaces to obtain visibility to hardware issues and failures.
Manage hosts
In general, there are few management tasks that relate to the IBM Netezza hosts. In
most cases, the tasks are for the optimal operation of the host. For example:
v Do not change or customize the kernel or operating system files unless directed
to do so by Netezza Support or Netezza customer documentation. Changes to
the kernel or operating system files can impact the performance of the host.
v Do not install third-party software on the Netezza host without first testing the
impact on a development or test Netezza system. While management agents or
other applications might be of interest, it is important to test and verify that the
application does not impact the performance or operation of the Netezza system.
v During Netezza software upgrades, host and kernel software revisions are
verified to ensure that the host software is operating with the latest required
levels. The upgrade processes might display messages that inform you to update
the host software to obtain the latest performance and security features.
v On Netezza HA systems, Netezza uses DRBD replication only on the /nz and
/export/home partitions. As new data is written to the Netezza /nz partition and
the /export/home partition on the primary Netezza system, the DRBD software
automatically makes the same changes to the /nz and /export/home partition of
the standby Netezza system.

v Use caution when you are saving files to the host disks; in general, do not store
Netezza database backups on the host disks, and do not use the host disks to
store large files that can grow and fill the host disks over time. Be sure to clean
up and remove any temporary files that you create on the host disks to keep the
disk space as available as possible for Netezza software and database use.
If the active host fails, the Netezza HA software typically fails over to the standby
host to run the Netezza database and system. Netezza Support works with you to
schedule field service to repair the failed host.
For the N3001-001 appliance, this process is similar. If the active host is
unreachable, the NPS services automatically fail over to the second host. It may
take 15 minutes for NPS to start discovering its SPUs. Next, the discovery process
waits up to 15 minutes for both SPUs to report their status. After that time, if only
the local SPU reports status, the system transitions into one-host mode. If the
second host becomes unreachable for more than 15 minutes, the active host
transitions into one-host mode.
Model N3001-001
For the N3001-001 appliance, both hosts are by default used for running the virtual
SPUs. Resources of both hosts, such as CPU or memory, are in use and none of the
hosts is marked as spare in nzhw.
You can switch to the one-host mode in which the resources of only one host are in
use. To do this, run the following command:
nzhw failover -id XXXX
where XXXX is the hwid of the host that you do not want to use. It is only
possible to fail over a host that is a standby in the cluster.
When the system runs in one-host mode, the role of the other host and its virtual
SPU is Failed and disks located on that host that are normally used to store data
(disks 9 - 24) have the role Inactive. The data slices remain mirrored but only with
two disks. In the two-host mode, each data slice is backed up by four disks.
To switch back from one-host mode to two-host mode, run the following
command:
nzhw activate -id XXXX
where XXXX is the hwid of the failed host. This operation activates the host, its
SPU, and all of its disks. Then, a rebalance is requested.
Note: Switching from one-host mode to two-host mode may take a significant
amount of time, for example a few hours. It depends on the amount of data stored
in the system.
Manage SPUs
Snippet Processing Units (SPUs) or S-Blades are hardware components that serve
as the query processing engines of the IBM Netezza appliance.

Each SPU has CPUs and FPGAs and memory and I/O to process queries and
query results. Each SPU has associated data partitions that it “owns” to store the
portions of the user databases and tables that the SPU processes during queries.
In model N3001-001, the SPUs are emulated using host resources, such as CPU and
memory. The SPUs are not physical components of the system and there is no
FPGA.
You can use the nzhw command to activate, deactivate, failover, locate, and reset a
SPU, or delete SPU information from the system catalog.
To indicate which SPU you want to control, you can refer to the SPU by using its
hardware ID. You can use the nzhw command to display the IDs, and obtain the
information from management UIs such as NzAdmin or IBM Netezza Performance
Portal.
The basic SPU management tasks are as follows:
Monitor SPU Status
To obtain the status of one or more SPUs, you can use the nzhw command with the
show options.
To show the status of all the SPUs:

[nz@nzhost ~]$ nzhw show -type spu
----------- ----- ---------- ------ ----------- --------
SPU 1007 spa1.spu1 Failed Booting N/A
SPU 1008 spa1.spu3 Failed Booting N/A
SPU 1009 spa1.spu5 Spare Booting N/A
SPU 1010 spa1.spu7 Spare Discovering N/A
SPU 1011 spa1.spu9 Active Discovering N/A
To show detailed information about SPU ID 1082:

[nz@nzhost ~]$ nzhw show -id 1082 -detail
Description HW Location Role State Security Serial Version
ID number
----------- ---- ---------- ------ ----------- -------- ------------ -------
SPU 1012 spa1.spu11 Active Discovering N/A Y011UF3CD01L 10.0
Detail
-----------------------------------------------------
40 CPU Cores; 125.90GB Memory; Ip Addr: 10.0.13.197;;
Activate a SPU
You can use the nzhw command to activate a SPU that is inactive or failed.
To activate a SPU:
nzhw activate -u admin -pw password -host nzhost -id 1004
For model N3001-001, if you have enabled the one-host mode by failing over a
SPU, you must activate that SPU to switch back to two-host mode. You must then
request a rebalance operation using nzds. In such case, switching to two-host mode
may take a significant amount of time, for example a few hours. It depends on the
amount of data stored in the system.

Deactivate a SPU
You can use the nzhw command to make a spare SPU unavailable to the system. If
the specified SPU is active, the command displays an error.
To deactivate a spare SPU:

nzhw deactivate -u admin -pw password -host nzhost -id 1004
Fail over a SPU
You can use the nzhw command to initiate a SPU failover.
To fail over a SPU, enter:

nzhw failover -u admin -pw password -host nzhost -id 1004
For model N3001-001, when a SPU is failed over, the system switches into one-host
mode in which the resources of only one host are used. You can only fail over a
SPU of the standby host. In order to fail over a SPU that is running on the active
host, you must first migrate the cluster to the other host. To switch back to
two-host mode, activate the failed SPU.
Locate a SPU
You can use the nzhw command to turn on or off a SPU LED and display the
physical location of the SPU. The default is on.
To locate a SPU, enter:

nzhw locate -u admin -pw password -host nzhost -id 1082
Turned locator LED ’ON’ for SPU: Logical Name:’spa1.spu11’ Physical
Location:’1st Rack, 1st SPA, SPU in 11th slot’
To turn off a SPU LED, enter:

nzhw locate -u admin -pw password -host nzhost -id 1082 -off
Turned locator LED ’OFF’ for SPU: Logical Name:’spa1.spu11’
Physical Location:’1st Rack, 1st SPA, SPU in 11th slot’
For model N3001-001, the SPUs are emulated and the output of the locate
command is the following:
Logical Name:’spa1.spu2’ Physical Location:’lower host, virtual SPU’
Reset a SPU
You can use the nzhw command to power cycle a SPU (a hard reset).
To reset a SPU, enter:

nzhw reset -u admin -pw password -id 1006
Delete a SPU entry from the system catalog
You can use the nzhw command to remove a failed, inactive, or incompatible SPU
from the system catalog.
To delete a SPU entry, enter:

nzhw delete -u admin -pw password -host nzhost -id 1004

Replace a failed SPU
If a SPU hardware component fails and must be replaced, Netezza Support works
with you to schedule service to replace the SPU.
Related reference:
Manage disks
The disks on the system store the user databases and tables that are managed and
queried by the IBM Netezza appliance. You can use the nzhw command to activate,
failover, and locate a disk, or delete disk information from the system catalog.
To protect against data loss, never remove a disk from an enclosure or remove a
RAID controller or ESM card from its enclosure unless directed to do so by
Netezza Support or when you are using the hardware replacement procedure
documentation. If you remove an Active or Spare disk drive, you could cause the
system to restart or to transition to the down state. Data loss and system issues can
occur if you remove these components when it is not safe to do so.
Netezza C1000 systems have RAID controllers to manage the disks and hardware
in the storage groups. You cannot deactivate a disk on a C1000 system, and the
commands to activate, fail, or delete a disk return an error if the storage group
cannot support the action at that time.
To indicate which disk you want to control, you can refer to the disk by using its
hardware ID. You can use the nzhw command to display the IDs, and obtain the
information from management UIs such as NzAdmin or IBM Netezza Performance
Portal.
For model IBM PureData System for Analytics N3001-001, the physical disks are
represented as two nzhw objects:
v A disk in an emulated enclosure in SPA (like for other N3001 systems).
v A host disk.
The majority of disk management operations should be performed on the storage
array disks, not on the host disk. The only operation that must be run on the host
disk is activation. This operation is required to assign a newly inserted physical
disk to the virtual SPU.
The basic disk management tasks are as follows:
Monitor disk status
To obtain the status of one or more disks, you can use the nzhw command with the
show options.
To show the status of all the disks (the sample output is abbreviated for the
documentation), enter:
[nz@nzhost ~]$ nzhw show -type disk
----------- ----- ---------------------- ------ ----------- --------

To show detailed information about disk ID 1076, enter:

[nz@nzhost ~]$ nzhw show -id 1076 -detail
Description HW Location Role State Security Serial number
ID
----------- ---- -------------------- ------ ----- -------- --------------------
Disk 1076 spa1.diskEncl4.disk2 Active Ok Enabled S0M1YDHX0000B429FVYS
Version Detail
------- ------------------------------------
E56B 558.91 GiB; Model ST600MM0026; SED;
Activate a disk
You can use the nzhw command to make an inactive, failed, or mismatched disk
available to the system as a spare.
To activate a disk, enter:

nzhw activate -u admin -pw password -host nzhost -id 1004
In some cases, the system might display a message that it cannot activate the disk
yet because the SPU has not finished an existing activation request. Disk activation
usually occurs quickly, unless there are several activations that are taking place at
the same time. In this case, later activations wait until they are processed in turn.
Note: For a Netezza C1000 system, you cannot activate a disk that is being used
by the RAID controller for a regeneration or other task. If the disk cannot be
activated, an error message similar to the following appears:Error: Can not
update role of Disk 1004 to Spare - The disk is still part of a non healthy
array. Please wait for the array to become healthy before activating.
For model N3001-001, in addition to activating a disk, it is sometimes required to

activate a host disk. This happens when a new disk is inserted into the system.
The new disk is not assigned to the virtual SPU and therefore cannot be used until
the activate operation is called on the host disk that represents the same physical
disk. When a host disk is being activated, the system is paused, the storage
configuration between the hosts is synchronized, and the SPUs are restarted. The
entire operation takes about four minutes on an idle system. When the system is in
use, the duration of the operation depends on how fast it can be paused because
pausing does not interrupt the running transactions. After the operation the system
is switched back to online state. During the whole precess several intermediate
system states can also be observed (such as Discovering, Initializing, and
Resuming).
Fail over a disk
You can use the nzhw command to initiate a failover. You cannot fail over a disk
until the system is at least in the initialized state.
To fail over a disk, enter:

nzhw failover -u admin -pw password -host nzhost -id 1004

On a Netezza C1000 system, when you fail a disk, the RAID controller
automatically starts a regeneration to a spare disk. Note that the RAID controller
may not allow you to fail a disk if you are attempting to fail a disk in a RAID 5
array that already has a failed disk.
Note: For a Netezza C1000 system, the RAID controller still considers a failed disk
to be part of the array until the regeneration is complete. After the regen
completes, the failed disk is logically removed from the array.
Locate a disk
You can use the nzhw command to turn on or off the LED on a disk in the storage
arrays. (This command does not work for disks in the hosts.) The default is on.
The command also displays the physical location of the disk.
To turn on a disk LED, enter:

nzhw locate -u admin -pw password -host nzhost -id 1004
Turned locator LED ’ON’ for Disk: Logical
To turn off a disk LED, enter:

nzhw locate -u admin -pw password -host nzhost -id 1004 -off
Turned locator LED ’OFF’ for Disk: Logical
For model N3001-001, you can locate both disks and host disks, including the host
disks managed by the hardware RAID controller.
Delete a disk entry from the system catalog
You can use the nzhw command to remove a disk that is failed, inactive,
mismatched, or incompatible from the system catalog. For Netezza C1000 systems,
do not delete the hardware ID of a failed disk until after you have successfully
replaced it using the instructions in the Replacement Procedures: IBM Netezza C1000
Systems.
To delete a disk entry, enter:

nzhw delete -u admin -pw password -host nzhost -id 1004
Replace a failed disk
If a disk hardware component fails and must be replaced, Netezza Support works
with you to schedule service to replace the disk.
Related reference:
Manage data slices

A data slice is a logical representation of the data that is saved in the partitions of
a disk. The data slice contains pieces of each user database and table. The IBM
Netezza system distributes the user data to all of the disks in the system by using
a hashing algorithm.

Each data slice has an ID, and is logically owned by a SPU to process queries on
the data that is contained within that data slice.
The following are basic data slice management tasks:

v Monitor status, space consumption, and overall health
v Rebalance data slices to the available SPUs
v Regenerate (or regen) a data slice after a disk failure
v Display the current topology of the data slices
You can use the nzhw, nzds, and nzspupart commands to manage data slices. To
indicate which data slice you want to control, you can refer to the data slice by
using its data slice ID. You can use the nzds command to display the IDs, and
obtain the information from management UIs such as NzAdmin or IBM Netezza
Performance Portal.
Related reference:
“The nzds command” on page A-10
Use the nzds command to manage and obtain information about the data slices in
the system.
Display data slice issues

You can quickly display a list of any data slices that have issues and that might
require administrative attention by using the nzds show -issues command. This
command displays data slices that are in the Degraded state (a loss of data
redundancy) or that are Repairing (that is, the data is being regenerated to a spare
disk). For example, the following command shows that several data slices are
being repaired:
[nz@nzhost ~]$ nzds show -issues
Data Slice Status SPU Partition Size (GiB) % Used Supporting Disks
---------- --------- ---- --------- ---------- ------ ----------------
15 Repairing 1137 3 356 46.87 1080,1086
16 Repairing 1137 2 356 46.79 1080,1086
46 Repairing 1135 4 356 46.73 1055,1098
You can also use the NzAdmin and IBM Netezza Performance Portal interfaces to
obtain visibility to hardware issues and failures.
Monitor data slice status

To obtain the status of one or more data slices, you can use the nzds command
with the show options.
To show the status of all the data slices (the sample output is abbreviated for the
documentation), enter:
[nz@nzhost ~]$ nzds show
---------- ------- ---- --------- ---------- ------ ----------------
1 Repairing 1017 2 356 58.54 1021,1029
2 Repairing 1017 3 356 58.54 1021,1029
3 Healthy 1017 5 356 58.53 1022,1030
4 Healthy 1017 4 356 58.53 1022,1030
5 Healthy 1017 0 356 58.53 1023,1031
6 Healthy 1017 1 356 58.53 1023,1031
7 Healthy 1017 7 356 58.53 1024,1032
8 Healthy 1017 6 356 58.53 1024,1032
Data slices 1 and 2 in the sample output is regenerating due to a disk failure. The
command output could be different on different models of appliances.

Note: For model N3001-001, each healthy data slice is stored on partitions of four
different disks. Two of these disks are always located on the first host and the
other two are located on the second host.
Note: For a Netezza C1000 system, three disks hold the user data for a data slice;
the fourth disk is the regen target for the failed drive. The RAID controller still
considers a failed disk to be part of the array until the regeneration is complete.
After the regen completes, the failed disk is logically removed from the array.
To show detailed information about the data slices that are being regenerated, you
can use the -regenstatus and -detail options, for example:
[nz@nzhost ~]$ nzds show -regenstatus -detail
Start Time % Done
---------- --------- ---- --------- ---------- ------ -------------------
------------------- ------
2 Repairing 1255 1 3725 0.00 1012,1028,1031,1056
2011-07-01 10:41:44 23
The status of a data slice shows the health of the data slice. The following table
describes the status values for a data slice. You see these states when you run the
nzds command or display data slices by using the NzAdmin or IBM Netezza
Performance Portal UIs.
Table 5-5. Data slice status
State Description
Healthy The data slice is operating normally and the data is protected in a
redundant configuration; that is, the data is fully mirrored.
Repairing The data slice is in the process of being regenerated to a spare disk
because of a disk failure.
Degraded The data slice is not protected in a redundant configuration. Another
disk failure could result in loss of a data slice, and the degraded
condition impacts system performance.
On a N3001-001 system, a data slice is marked as degraded when

fewer than four disks are used to store it. If two or three disks are
used for it, the data slice is still mirrored.
Regenerate a data slice

If a disk encounters problems or fails, you perform a data slice regeneration to
create a copy of the primary and mirror data slices on an available spare disk.
During regeneration, the regular system processing continues for the bulk of the
regeneration.
Note: In the IBM PureData System for Analytics N1001 or IBM Netezza 1000 and
later models, the system does not change states during a regeneration; that is, the
system remains online while the regeneration is in progress. There is no
synchronization state change and no interruption to active jobs during this process.
If the regeneration process fails or stops for any reason, the system transitions to
the Discovering state to establish the topology of the system.
You can use the nzspupart regen command or the NzAdmin interface to
regenerate a disk. If you do not specify any options, the system manager checks
for any degraded partitions and if found, starts a regeneration if there is a spare
disk in the system.

nz@nzhost ~]$ nzspupart regen
Are you sure you want to proceed (y|n)? [n] y
Info: Regen Configuration - Regen configured on SPA:1 Data slice 20 and 19
For IBM PureData System for Analytics N2001 and later systems, each disk
contains partitions for the user data and the log and swap partitions. When the
system regenerates a disk to a spare, the system copies all of the partitions to the
spare. If you issue the nzspupart regen command manually, specify:
v The hardware ID of the SPU that has the degraded partitions
v One of the partition IDs
v The hardware ID for the spare disk
The regeneration affects all partitions on that disk. For example:
nz@nzhost ~]$ nzspupart regen -spu 1099 -part 1 -dest 1066
You can then issue the nzspupart show -regenstatus or the nzds show
-regenstatus command to display the status of the regeneration. For example:
[nz@nzhost ~]$ nzspupart -regenstatus
SPU Partition Id Partition Type Status Size (GiB) % Used Supporting Disks % Done Repairing Disks Starttime
---- ------------ -------------- --------- ---------- ------ ------------------- ------- --------------- ---------
1099 0 Data Repairing 356 0.00 1065,1066 0.00 1066 0
1099 1 Data Repairing 356 0.00 1065,1066 0.00 1066 0
1099 100 NzLocal Repairing 1920989772 0.00 1065,1066,1076,1087 0.00 1066 0
1099 101 Swap Repairing 32 0.00 1065,1066,1076,1087 0.00 1066 0
1099 110 Log Repairing 1 3.31 1065,1066 0.00 1066 0
For systems earlier than the N200x models, you have to specify the data slice IDs
and spare disk ID. For example, to regenerate dataslice IDs 11 and 17 affected by
the failing disk and regenerate them on spare disk ID 1024, enter:
nzds regen -u admin -pw password -ds "11,17" -dest 1024
If you want to control the regeneration source and target destinations, you can
specify source SPU and partition IDs, and the target or destination disk ID. The
spare disk must reside in the same SPA as the disk that you are regenerating. You
can obtain the IDs for the source partition by issuing the nzspupart show -details
command.
To regenerate a degraded partition and specify the information for the source and
destination, enter the following command:
nzspupart regen -spu 1035 -part 7 -dest 1024
Note: Regeneration can take several hours to complete. If the system is idle and
has no other activity except the regeneration, or if the user data partitions are not
very full, the regeneration takes less time to complete. You can review the status of
the regeneration by issuing the nzspupart show -regenStatus command. During
the regeneration, user query performance can be impacted while the system is
busy processing the regeneration. Likewise, user query activity can increase the
time that is required for the regeneration.
If the system manager is unable to remove the failed disk from the RAID array, or
if it cannot add the spare disk to the RAID array, a regeneration setup failure can
occur. If a regeneration failure occurs, or if a spare disk is not available for the
regeneration, the system continues processing jobs. The data slices that lose their
mirror continue to operate in an unmirrored or degraded state; however, you
should replace your spare disks as soon as possible and ensure that all data slices
are mirrored. If an unmirrored disk fails, the system is brought to a down state.

Rebalance data slices
Each SPU owns or manages a number of data slices for query processing. The
SPUs and their data slices must reside in the same SPA. If a SPU fails, the System
Manager reassigns its data slices to the other active SPUs in the same SPA. The
System Manager randomly assigns a pair of data slices (the primary and mirrors)
from the failed SPU to an available SPU in the SPA. The System Manager ensures
that each SPU has no more than two data slices more than one of its peers.
After the failed SPU is replaced or reactivated, you must rebalance the data slices
to return to optimal performance. The rebalance process checks each SPU in the
SPA; if a SPU has more than two data slices more than another SPU, the System
Manager redistributes the data slices to equalize the workload and return the SPA
to an optimal performance topology. (The System Manager changes the system to
the discovering state to perform the rebalance.)
In addition, if an S-Blade does not have an equal distribution of disks in the

odd-numbered versus even-numbered enclosures of its array, the System Manager
reports the problem as an overloaded SAS bus. The nzhw rebalance command also
reconfigures the topology so that half of the disks are in the odd-numbered
enclosures and half in the even-numbered.
You can use the nzhw command to rebalance the data slice topology. The system
also runs the rebalance check each time the that system is restarted, or after a SPU
failover or a disk regeneration setup failure.
To rebalance the data slices:

nzhw rebalance -u admin -pw password
If a rebalance is not required, the command displays a message that a rebalance is

not necessary and exits without completing the step.
You can also use the nzhw rebalance -check option to have the system check the
topology and only report whether a rebalance is needed. The command displays
the message Rebalance is needed or There is nothing to rebalance. If a
rebalance is needed, you can run the nzhw rebalance command to perform the
rebalance, or you could wait until the next time the Netezza software is stopped
and restarted to rebalance the system.
For a N3001-001 system, the rebalance operation is used for switching the system
back to two-host mode after activating the failed SPU. Rebalance is automatically
requested by the system when the transition to two-host mode is requested by the
activate operation for a host.
Related concepts:
“System resource balance recovery” on page 5-17
Active path topology

The active path topology defines the ports and switches that offer the best
connection performance to carry the traffic between the S-Blades and their disks.
For best system performance, all links and components must remain balanced and
equally loaded.
To display the current storage topology, use the nzds show -topology command:

[nz@nzhost ~]$ nzds show -topology
===============================================================================
Topology for SPA 1
spu0101 has 8 datapartitions: [ 0:1 1:2 2:11 3:12 4:10 5:9 6:18 7:17 ]
hba[0] 4 disks
port[2] 2 disks: [ 1:encl1Slot10 11:encl1Slot06 ] -> switch 0
hba[1] 4 disks
...............................................................................
spu0103 has 8 datapartitions: [ 0:22 1:21 2:16 3:15 4:13 5:14 6:5 7:6 ]
hba[0] 4 disks
hba[1] 4 disks
...............................................................................
spu0105 has 6 datapartitions: [ 0:19 1:20 2:7 3:8 4:4 5:3 ]
hba[0] 3 disks
port[3] 1 disks: [ 4:encl2Slot12 ] -> switch 1
hba[1] 3 disks
port[1] 1 disks: [ 3:encl1Slot01 ] -> switch 1
...............................................................................
Switch 0
port[1] 6 disks: [ 1:encl1Slot10 7:encl1Slot04 11:encl1Slot06 15:encl1Slot08
19:encl1Slot09 21:encl1Slot11 ] -> encl1

20:encl2Slot10 22:encl2Slot11 ] -> encl2
Switch 1
17:encl1Slot12 ] -> encl1

18:encl2Slot09 ] -> encl2
===============================================================================
This sample output shows a normal topology for an IBM Netezza 1000-3 system.
The command output is complex and is typically used by Netezza Support to
troubleshoot problems. If there are any issues to investigate in the topology, the
command displays a WARNING section at the bottom, for example:
WARNING: 2 issues detected
spu0101 hba [0] port [2] has 3 disks
SPA 1 SAS switch [sassw01a] port [3] has 7 disks
These warnings indicate problems in the path topology where storage components
are overloaded. These problems can affect query performance and also system
availability if other path failures occur. Contact Support to troubleshoot these
warnings.
To display detailed information about path failure problems, you can use the
following command:
[nz@nzhost ~]$ nzpush -a mpath -issues
spu0109: Encl: 4 Slot: 4 DM: dm-5 HWID: 1093 SN: number PathCnt: 1
PrefPath: yes
PrefPath: yes
PrefPath: no

If the command does not return any output, there are no path failures observed on
the system. It is not uncommon for some path failures to occur and then clear
quickly. However, if the command displays some output, as in this example, there
are path failures on the system and system performance can be degraded. The
sample output shows that spu0111 is not using the higher performing preferred
path (PrefPath: no) and there is only one path to each disk (PathCnt: 1) instead of
the normal two paths. Contact Netezza Support and report the path failures to
initiate troubleshooting and repair.
Note: It is possible to see errors that are reported in the nzpush command output
even if the nzds -topology command does not report any warnings. In these cases,
the errors are still problems in the topology, but they do not affect the performance
and availability of the current topology. Be sure to report any path failures to
ensure that problems are diagnosed and resolved by Support for optimal system
performance.
Related reference:
Handle transactions during failover and regeneration

When a disk failover occurs, the system continues processing any active jobs while
it runs a disk regeneration. No active queries must be stopped and restarted.
If a SPU fails, the system state changes to the pausing -now state (which stops
active jobs), and then transitions to the discovering state to identify the active SPUs
in the SPA. The system also rebalances the data slices to the active SPUs.
After the system returns to an online state:

v The system restarts transactions that did not return data before the pause -now
transition.
v Read-only queries begin again with their original transaction ID and priority.
The following table describes the system states and the way IBM Netezza handles
transactions during failover.
Table 5-6. System states and transactions
System state Active transactions New transactions
Offline(ing) Now Aborts all transactions. Returns an error.
Offline(ing) Waits for the transaction to finish. Returns an error.
Pause(ing) Now Aborts only those transactions that Queues the transaction.
cannot be restarted.
Pause(ing) Waits for the transaction to finish. Queues the transaction.
The following examples provide specific instances of how the system handles
failovers that happen before, during, or after data is returned.
v If the pause -now occurs immediately after a BEGIN command completes, before
data is returned, the transaction is restarted when the system returns to an
online state.
v If a statement such as the following completes and then the system transitions,
the transaction can restart because data has not been modified and the reboot
does not interrupt a transaction.
BEGIN;
SELECT * FROM emp;

v If a statement such as the following completes, but the system goes transitions
before the commit to disk, the transaction is aborted.
BEGIN;
INSERT INTO emp2 FROM emp;
v A statement such as the following can be restarted if it has not returned data, in
this case a single number that represents the number of rows in a table. This
sample includes an implicit BEGIN command.
SELECT count(*) FROM small_lineitem;
v If a statement such as the following begins to return rows before the system
transitions, the statement will be aborted.
INSERT INTO emp2 SELECT * FROM externaltable;
This transaction and others that would normally be aborted will be restarted if
the nzload -allowReplay option applied to the associated table.
Note: There is a retry count for each transaction. If the system transitions to
pause -now more than the number of retries that are allowed, the transaction is
stopped.
Automatic query and load continuation

When a SPU unexpectedly restarts or is failed-over, the System Manager initiates a
state change from online to pause -now. During this transition, rather than aborting
all transactions, the IBM Netezza system aborts only those transactions that cannot
be restarted.
The system restarts the following transactions:

v Read-only queries that have not returned data. The system restarts the request
with a new plan and the same transaction ID.
v Loads. If you have enabled load continuation, the system rolls back the load to
the beginning of the replay region and resends the data.
After the system restarts these transactions, the system state returns to online. For
more information, see the IBM Netezza Data Loading Guide.
Power procedures
This section describes how to power on an IBM Netezza system and how to
power-off the system. Typically, you would only power off the system if you are
moving the system physically within the data center, or in the event of possible
maintenance or emergency conditions within the data center.
The instructions to power on or off an IBM Netezza 100 system are available in the
Site Preparation and Specifications: IBM Netezza 100 Systems.
Note: To power cycle a Netezza system, you must have physical access to the
system to press power switches and to connect or disconnect cables. Netezza
systems have keyboard/video/mouse (KVM) units that you can use to enter
administrative commands on the hosts.
PDU and circuit breakers overview

On the IBM Netezza 1000-6 and larger models, and the IBM PureData System for
Analytics N1001-005 and larger models. the main input power distribution units
(PDUs) are at the bottom of the rack on the right and left sides, as shown in the

following figure.
Figure 5-11. IBM Netezza 1000-6 and N1001-005 and larger PDUs and circuit breakers
A OFF setting
B ON setting
C PDU circuit breakers. 3 rows of 3 breaker pins.
v To close the circuit breakers (power up the PDUs), press in each of the nine
breaker pins until they engage. Be sure to close the nine pins on both main
PDUs in each rack of the system.
v To open the circuit breakers (power off the PDUs), pull out each of the nine
breaker pins on the left and the right PDU in the rack. If it becomes difficult to
pull out the breaker pins by using your fingers, you can use a tool such as a
pair of needle-nose pliers to gently pull out the pins.
On the IBM Netezza 1000-3 and IBM PureData System for Analytics N1001-002
models, the main input power distribution units (PDUs) are on the right and left
sides of the rack, as shown in the following figure.

Figure 5-12. IBM Netezza 1000-3 and IBM PureData System for Analytics N1001-002 PDUs and circuit breakers
A Two circuit breakers at the top of the PDU

B OFF setting
C ON setting
At the top of each PDU is a pair of breaker rocker switches. The labels on the
switches are upside down when you view the PDUs.
v To close the circuit breakers (power up the PDUs), you push the On toggle of
the rocker switch in. Make sure that you push in all four rocker switches, two
on each PDU.
v To open the circuit breakers (power off the PDUs), you must use a tool such as a
small flathead screwdriver; insert the tool into the hole that is labeled OFF and
gently press until the rocker toggle pops out. Make sure that you open all four
of the rocker toggles, two on each PDU.
Powering on the IBM Netezza 1000 and IBM PureData System

for Analytics N1001
About this task
To power on an IBM Netezza 1000 or IBM PureData System for Analytics N1001
system, complete the following steps:
Procedure
1. Make sure that the two main power cables are connected to the data center
drops; there are two power cables for each rack of the system.
2. Do one of the following steps depending on which system model you have:

v For an IBM Netezza 1000-6, N1001-005 or larger model, push in the nine
breaker pins on both the left and right lower PDUs as shown in Figure 5-11
on page 5-33. Repeat these steps for each rack of the system.
v For an IBM Netezza 1000-3 or N1001-002 model, close the two breaker
switches on both the left and right PDUs as shown in Figure 5-12 on page
5-34.
3. Press the power button on both host servers and wait for the servers to start.
This process can take a few minutes.
4. Log in as root to one of the hosts and confirm that the Netezza software is
started:
a. Run the crm_mon command to obtain the cluster status:
============
Last updated: Tue Jun 2 11:46:43 2009
2 Nodes configured.
============
Resource Group: nps
b. Identify the active host in the cluster, which is the host where the nps
resource group is running:
crm_resource[5377]: 2009/06/01_10:13:12 info: Invoked: crm_resource

-r nps -W
5. Log in as nz to the active host and verify that the Netezza server is online:
[nz@nzhost1 ~]$ nzstate
6. If your system runs the Call Home support feature, enable it.
[nz@nzhost1 ~]$ nzOpenPmr --on
Powering off the IBM Netezza 1000 or IBM PureData System

for Analytics N1001 system
About this task
To power off an IBM Netezza 1000 or IBM PureData System for Analytics N1001
system, complete the following steps:
Procedure
1. Log in to the host server (ha1) as root.
Note: Do not use the su command to become root.

2. Identify the active host in the cluster, which is the host where the nps resource
group is running:

-r nps -W
3. Log in to the active host (nzhost1 in this example) as the nz user.
4. Check to see if Call Home is enabled, and if so, disable it.
a. Check if Call Home is enabled:
[nz@nzhost1 ~]$ nzOpenPmr --status
b. If Call Home is enabled, disable it:
[nz@nzhost1 ~]$ nzOpenPmr --off
5. Run the following command to stop the IBM Netezza server:
nz@nzhost1 ~]$ nzstop
6. From the active host, stop Heartbeat on each host, starting with the non-active
host. For example, if HA1 is the active host, type the following commands to
stop the clustering processes:
[root@nzhost1 ~]# ssh ha2 ’service heartbeat stop’
7. Log in as root on the standby host (nzhost2 in this example), and run the
following command to shut down the host:
[root@nzhost2 ~]# shutdown -h now
The system displays a series of messages as it stops processes and other
system activity. When it finishes, it displays the message “power down”
which indicates that it is now safe to turn off the power to the server.
8. Press the power button on Host 2 (located in the front of the cabinet) to
power down that NPS host.
9. As root on the active host, run the following command to shut down the host:
system activity. When it finishes, it displays the message “power down”
which indicates that it is now safe to turn off the power to the server.
power down that NPS host.
11. Do one of the following steps depending on which appliance model you have:
v For an IBM Netezza 1000-6 or N1001-005 or larger model, pull out the nine
breaker pins on both the left and right lower PDUs as shown in Figure 5-11
on page 5-33. Repeat these steps for each rack of the system.
v For an IBM Netezza 1000-3 or N1001-002 model, use a small tool such as a
pocket screwdriver to open the two breaker switches on both the left and
right PDUs as shown in Figure 5-12 on page 5-34.
12. Disconnect the main input power cables (two per rack) from the data center
power drops. Do not disconnect the power cords from the plug/connector on
the PDUs in the rack; instead, disconnect them from the power drops outside
the IBM Netezza 1000 rack.

Powering on the IBM PureData System for Analytics N200x
About this task
To power on an IBM PureData System for Analytics N200x system, complete the
following steps:
Procedure
1. Switch on the power to the two PDUs located in the rear of the cabinet at the
bottom. Make sure that you switch on both power controls. Repeat this steps
for each rack of a multi-rack system.
2. Press the power button on Host 1. The power button is on the host in the front
of the cabinet. Host 1 is the upper host in the rack, or the host located in rack
one of older multi-rack systems. A series of messages appears as the host
system boots.
3. Wait at least 30 seconds after powering up Host 1, then press the power button
on Host 2. (Host 2 is the lower host in the rack, or the host located in rack two
of older multi-rack systems.) The delay ensures that Host 1 completes its
start-up operations first, and thus is the primary host for the system.
4. Log in as root to Host 1 and run the crm_mon command to monitor the status of
the HA services and cluster operations:
The output of the command refreshes at the specified interval rate of 5 seconds
(-i5).
5. 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 the next step.
============
2 Nodes configured.
============
Resource Group: nps
6. Press Ctrl-C to exit the crm_mon command and return to the command prompt.
7. Log in to the nz account.
[root@nzhost1 ~]# su - nz
8. Verify that the system is online using the following command:
9. If your system runs the Call Home support feature, enable it.
[nz@nzhost1 ~]$ nzOpenPmr --on

Powering off the IBM PureData System for Analytics N200x
system
About this task
To power off an IBM PureData System for Analytics N200x system, complete the
following steps:
Procedure
Note: Do not use the su command to become root.

group is running:

-r nps -W
3. Log in to the active host (nzhost1 in this example) as the nz user.
4. Check to see if Call Home is enabled, and if so, disable it.
a. Check if Call Home is enabled:
[nz@nzhost1 ~]$ nzOpenPmr --status
b. If Call Home is enabled, disable it:
[nz@nzhost1 ~]$ nzOpenPmr --off
5. On the active host (nzhost1 in this example), run the following command to
stop the Netezza server:
[nz@nzhost1 ~]$ nzstop
6. Log in as root to ha1 and type the following commands to stop the clustering
processes:
7. As root on the standby host (nzhost2 in this example), run the following
command to shut down the host:
system activity. When it finishes, it displays the message power down which
indicates that it is now safe to turn off the power to the server.
power down that Netezza host.
9. On host 1, shut down the Linux operating system using the following
command:
system activity. When it finishes, it displays the message power down which
indicates that it is now safe to turn off the power to the server.
power down that Netezza host.
11. Switch off the power to the two PDUs located in the rear of the cabinet at the
bottom. Make sure that you switch off both power controls. (Repeat this steps
for each rack of a multi-rack system.)

Powering on the IBM Netezza High Capacity Appliance C1000
About this task
To power on an IBM Netezza High Capacity Appliance C1000, complete the

following steps:
Procedure
1. Make sure that the two main power cables are connected to the data center
drops; there are two power cables for each rack of the system. For a North
American power configuration, there are four power cables for the first two
racks of a Netezza C1000 (or two cables for a European Union power
configuration);
2. Switch the breakers to ON on both the left and right PDUs. (Repeat these
steps for each rack of the system.)
3. Press the power button on both host servers and wait for the servers to start.
This process can take a few minutes.
5. Change to the nz user account and run the following command to stop the
Netezza server: nzstop
6. Wait for the Netezza system to stop.
7. Log out of the nz account to return to the root account, then type the
following command to power on the storage groups:
[root@nzhost1 ~]# /nzlocal/scripts/rpc/spapwr.sh -on all -j all
8. Wait five minutes and then type the following command to power on all the
S-blade chassis:
[root@nzhost1 ~]# /nzlocal/scripts/rpc/spapwr.sh -on all
9. Run the crm_mon -i5 command to monitor the status of the HA services and
cluster operations. 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
the next step.
============
2 Nodes configured.
============
Resource Group: nps
10. Press Ctrl-C to exit the crm_mon command and return to the command prompt.
11. Log into the nz account.
12. Verify that the system is online using the following command:

Powering off the IBM Netezza High Capacity Appliance C1000

About this task
To power off an IBM Netezza High Capacity Appliance C1000, complete the
following steps:
CAUTION:
Unless the system shutdown is an emergency situation, do not power down a
Netezza C1000 system when there are any amber (Needs Attention) LEDs
illuminated in the storage groups. It is highly recommended that you resolve the
problems that are causing the Needs Attention LEDs before you power off a
system to ensure that the power-up procedures are not impacted by the
unresolved conditions within the groups.
Procedure
group is running:

-r nps -W
2. Log in as root to the standby host (nzhost1 in this example) and run the
following command to stop the Netezza server:
[root@nzhost1 ~]# nzstop
3. Type the following commands to stop the clustering processes:
4. On ha1, type the following commands to power off the S-blade chassis and
storage groups:
[root@nzhost1 ~]# /nzlocal/scripts/rpc/spapwr.sh -off all
[root@nzhost1 ~]# /nzlocal/scripts/rpc/spapwr.sh -off all -j all
5. Log into ha2 as root and shut down the Linux operating system using the
following command:
The system displays a series of messages as it stops processes and other system
activity. When it finishes, it displays the message power down which indicates
that it is now safe to turn off the power to the server.
6. Press the power button on host 2 (located in the front of the cabinet) to power
down that Netezza host.
7. Log into ha1 as root and shut down the Linux operating system using the
following command:
activity. When it finishes, it displays the message power down which indicates
that it is now safe to turn off the power to the server.
8. Press the power button on host 1 (located in the front of the cabinet) to power
down that Netezza host.
9. Switch the breakers to OFF on both the left and right PDUs. (Repeat this step
for each rack of the system.)

Powering on IBM PureData System for Analytics N3001-001
Perform the following steps to power on the IBM PureData System for Analytics
N3001-001 appliance.
Procedure
1. Press the power button on Host 1. The power button is located on the host in
the front of the cabinet. Host 1 is the upper host in a single-rack system, or the
host located in rack one of a multi-rack system. A series of messages appears as
the host system boots.
2. Wait for at least 30 seconds after powering up Host 1. Then press the power
button of Host 2. The delay ensures that Host 1 completes its startup
operations first and therefore becomes the primary host for the system. Host 2
is the lower host in a single-rack system, or the host located in rack two of a
multi-rack system.
3. Log in to Host 1 as root and run the crm_mon command to monitor the status of
HA services and cluster operations:
The output of the command is refreshed at the specified interval rate of 5

seconds (-i5).
4. Review the output of the command and wait for the resource groups until they
all have the Started status. This usually takes two to three minutes. Then,
proceed to the next step. The command returns the following output:
============
Last updated: Fri Aug 29 02:19:25 2014
Current DC: hostname-1 (3389b15b-5fee-435d-8726-a95120f437dd)
2 Nodes configured.
============
Node: hostname-1 (3389b15b-5fee-435d-8726-a95120f437dd): online

Node: hostname-2 (d346b950-bd01-49e3-9385-88b0a7bbbd6a): online
Resource Group: nps

drbd_exphome_device (heartbeat:drbddisk): Started hostname-1
drbd_nz_device (heartbeat:drbddisk): Started hostname-1
exphome_filesystem (heartbeat::ocf:Filesystem): Started hostname-1
nz_filesystem (heartbeat::ocf:Filesystem): Started hostname-1
fabric_ip (heartbeat::ocf:IPaddr):
wall_ip (heartbeat::ocf:IPaddr):
nz_dnsmasq (lsb:nz_dnsmasq):
nzinit (lsb:nzinit): Started hostname-1
floating_management_ip (heartbeat::ocf:IPaddr): Started hostname-1
fencing_route_to_ha1 (stonith:external/ipmioverlan):Started hostname-2
fencing_route_to_ha2 (stonith:external/ipmioverlan): Started hostname-1
5. Press Ctrl + C to exit the crm_mon command and return to the command
prompt.
6. Log in to the nz account:
7. Run the following command to verify that the system is online:

System state is 'Online'.
Powering off IBM PureData System for Analytics N3001-001

Perform the following steps to power off the IBM PureData System for Analytics
N3001-001 appliance.
Procedure
1. Log in to Host 1 (ha1) as root.
Note: Do not use the su command to switch to root.

2. Identify the active host in the cluster. This is the host on which the NPS
resource group is running. To do this, run the following command:
crm_resource[5377]: 2009/06/07_10:13:12 info: Invoked: crm_resource -r nps -W

3. On the active host , in this example nzhost1, run the following commands to
stop the Netezza server:
[nz@nzhost1 ~]$ su - nz
[nz@nzhost1 ~]$ nzstop
[nz@nzhost1 ~]$ exit
4. Run the following commands to stop the clustering processes:

[root@nzhost1 ~]# ssh ha2 'service heartbeat stop'
5. Log in as root to the standby host, in this example nzhost2. Run the following
command to shut down the host:
activity. When it finishes, a message is displayed that indicates that it is now
safe to power down to the server.
6. Press the power button on Host 2 to power down that Netezza host. The
button is located in the front of the cabinet.
7. On Host 1, run the following command to shut down the Linux operating
system:
activity. When it finishes, a message is displayed that indicates that it is now
safe to power down to the server.
8. Press the power button on Host 1 to power down that Netezza host. The
button is located in the front of the cabinet.

Chapter 6. About self-encrypting drives
The IBM PureData System for Analytics N3001 and N3001-001 appliances use
self-encrypting drives (SEDs) for improved security and protection of the data
stored on the appliance.
Self-encrypting drives (SEDs) encrypt data as it is written to the disk. Each disk
has a disk encryption key (DEK) that is set at the factory and stored on the disk.
The disk uses the DEK to encrypt data as it writes, and then to decrypt the data as
it is read from disk. The operation of the disk, and its encryption and decryption,
is transparent to the users who are reading and writing data. This default
encryption and decryption mode is referred to as secure erase mode. In secure erase
mode, you do not need an authentication key or password to decrypt and read
data. SEDs offer improved capabilities for an easy and speedy secure erase for
situations when disks must be repurposed or returned for support or warranty
reasons.
For the optimal security of the data stored on the disks, SEDs have a mode
referred to as auto-lock mode. In auto-lock mode, the disk uses an authentication
encryption key (AEK) to protect its DEK. When a disk is powered off, the disks are
automatically locked. When the disk is powered on, the SED requires a valid AEK
to read the DEK and unlock the disk to proceed with read and write operations. If
the SED does not receive a valid authentication key, the data on the disk cannot be
read. The auto-lock mode helps to protect the data when disks are accidentally or
intentionally removed from the system.
In many environments, the secure erase mode may be sufficient for normal
operations and provides you with easy access to commands that can quickly and
securely erase the contents of the disk before a maintenance or repurposing task.
For environments where protection against data theft is paramount, the auto-lock
mode adds an extra layer of access protection for the data stored on your disks.
SEDs are currently available on the following appliances:

v IBM PureData System for Analytics N3001
v IBM PureData System for Analytics N3001-001
Locking the SEDs

The IBM NPS software provides commands to configure the SEDs on the IBM
PureData System for Analytics N3001 models to use auto-lock mode.
By default, the SEDs on the IBM PureData System for Analytics N3001 appliances
operate in secure erase mode. The IBM installation team can configure the disks to
run in auto-lock mode by creating a keystore and defining an authentication key
for your host and storage disks when the system is installed in your data center. If
you choose not to auto-lock the disks during system installation, you can lock
them later. Contact IBM Support to enable the auto-lock mode. The process to
auto-lock the disks requires a short NPS service downtime window.

CAUTION:
Do not attempt to auto-lock the disks on your own. You must work with IBM
Support to ensure that the disks are auto-locked correctly and completely with a
conforming authentication key. If the process is not performed correctly, or if
authentication key used to auto-lock the disks is incorrect or lost, your system
could be unable to start and you could lose the data on your disks.
While it is recommended that you configure your SEDs to operate in auto-lock

mode, make sure that this is appropriate for your environment. After the drives are
configured for auto-lock mode, you cannot easily disable or undo the auto-lock
mode for SEDs.
The NPS system requires an AEK for the host drives and an AEK for the drives in
the storage arrays that are managed by the SPUs. You have two options for storing
the keys. The AEKs can be stored in a password protected keystore repository on
the NPS host, or if you have implemented an IBM Security Key Lifecycle Manager
(ISKLM) server, you can store the AEKs in your ISKLM server for use with the
appliance. The commands to create the keys are the same for locally or ISKLM
stored systems.
For locally stored keys, the key repository is stored in the /nz/var/keystore
directory on the NPS host. The repository is locked and protected.
For ISKLM configurations, there is no local keystore on the NPS hosts. The ISKLM
support requires some additional configuration for your NPS hosts to become a
client of the ISKLM server. The configuration steps are described in the section
“IBM Security Key Lifecycle Manager configuration steps” on page 6-4.
You should use the nzkeybackup command to create a backup copy of the AEKs
after you change the keys. If the keystore on the NPS host or the ISKLM server is
lost, the disks cannot be read. Make sure that you carefully protect the keystore
backups for the appliance in a secure area, typically in a location that is not on the
NPS hosts.
Note: When auto-lock mode is enabled, and a disk is failed over either
automatically or manually using the nzhw failover -id <diskHwId> command, the
system automatically securely erases the disk contents. Contact IBM Support for
assistance with the process to securely erase one or more disks on the system. If a
disk is physically removed from the system before it is failed over, the system
detects the missing drive and fails over to an available spare disk, but the removed
disk is not securely erased because it is no longer in the system. In auto-lock
mode, the disk is locked when it is powered down, so the contents are not
readable.
About the IBM Security Key Lifecycle Manager support
Starting in NPS release 7.2.1, you can configure your IBM PureData System for
Analytics N3001 models to send the AEKs to an IBM Security Key Lifecycle
Manager (ISKLM) server in your environment. The NPS support requires ISKLM
version 2.5.0.5 or later.
In this configuration, the ISKLM server only stores and sends the AEKs that are
manually generated on the NPS host. The ISKLM server cannot be used to
automatically create and rotate the AEKs on a scheduled basis. You must have an
ISKLM server already set up and running in your environment, and you need
assistance from the ISKLM administrator to add the NPS host as a client of the

ISKLM server, and you must obtain information such as the device group name,
device serial number, certificates, and ISKLM server and port information from the
ISKLM administrator. The NPS documentation does not provide instructions for
setting up and activating ISKLM in your environment.
Important: If you configure your N3001 system to use ISKLM as the key
repository, note that you cannot downgrade from NPS release 7.2.1 to an earlier 7.2
release unless you convert from ISKLM to a local keystore for your SEDs. The IBM
Netezza Software Upgrade Guide has instructions for disabling ISKLM support and
returning to a local keystore before downgrading.
Unlocking the SEDs

After your SEDs are operating in auto-lock mode, it is possible to unlock them and
restore them to the default secure erase mode, but the process requires significant
assistance from IBM Support.
Typically, after you configure SEDs to use auto-lock mode, you would never
change them back to the default secure erase mode. If for some reason you must
reconfigure the SEDs, it is possible to do so, but this process is very complex and
requires a lengthy service window and possible service charges. There is also a risk
of data loss especially if your backups for the system are stale or incomplete. Make
sure that reconfiguring your SEDs to secure erase mode is appropriate for your
environment.
CAUTION:
The process to reconfigure SEDs to secure erase mode from the auto-lock mode
is not a process that you can run on your own. You must work with IBM
Support to reset the system correctly.
There are two options for reconfiguring your host SEDs to secure erase mode:
v The first option is to have IBM Support replace your host drives with a set of
new drives that are custom-built with the correct releases of software for your
system. The host motherboards/planars must also replaced (or the host disks
securely erased) to clear the RAID controller NVRAM that holds the AEK.
Reconfiguring the host SEDs requires system downtime, charges for the
replacement disks and planars, and approximately a day of downtime to replace
the disks and restore your NPS host backups and metadata.
v The second option is to completely reinitialize your system to a factory default
level, then reload all your data from the most recent full backup. This option
could require a service window of several days for the reinitialization and
complete reload.
To change the storage array SEDs from auto-lock mode to standard secure erase
mode, there is an IBM Support process to disable the authentication key. This
process requires you to securely erase the storage drives and reload the full
database backups from your most recent NPS backup. If it is an option, such as for
a non-production test system, a full system reinitialization would also reset the
drives from auto-lock mode. You would then need to restore your NPS data from
your backups, or start creating new data from new load sources.
SED keystore
The keystore holds the AEKs for unlocking the host and SPU drives that are
configured to run in auto-lock mode.
Chapter 6. About self-encrypting drives 6-3

If you chose to auto-lock the drives at installation time, the IBM installation team
probably created the keystore during the appliance installation process. The
nzkeydb command creates and manages the keystores. If you use a local keystore,
the keystore is stored in the /nz/var/keystore directory. The keystore has a
password to help protect it from users who are not allowed to see the contents or
manage keys.
Important: If you use the IBM Security Key Lifecycle Manager (ISKLM) to store
and retrieve the AEKs for your NPS appliance, you can lock the drives using a
local keystore and then migrate to ISKLM management of the keys, or you can
configure the system to use ISKLM to create the keys and lock the drives. See the
“IBM Security Key Lifecycle Manager configuration steps” section for the
instructions to configure ISKLM support. After you configure ISKLM, the keys are
sent to the ISKLM server for storage and are not stored locally on the system.
If you lose the keystore, either because the local keystore is corrupted or deleted,
or because connectivity to the ISKLM server is lost, you lose the ability to unlock
your SED drives when they power on. As a best practice, make sure that you have
a recent backup of the current keys. You use the nzkeybackup command to create a
compressed tar file backup of the current keystore. You should always back up the
keystore after any key changes. Make sure that you save the keystore backups in a
safe location away from the NPS appliance.
Note: The nzhostbackup also captures the local keystore in the host backup, but
nzkeybackup is better because it does not require you to pause the NPS system and
stop query activity, and nzkeybackup -sklm can capture the keys that are stored in
an ISKLM server.
You can use the nzkeyrestore command to restore a keystore from a keystore
backup file.
Refer to the following command descriptions for more information:

v “The nzkeydb command” on page A-37
v “The nzkeybackup command” on page A-39
v “The nzkeyrestore command” on page A-40
IBM Security Key Lifecycle Manager configuration steps

If you want to store and retrieve your SED AEKs from an IBM Security Key
Lifecycle Manager (ISKLM) server in your environment, you must configure the
NPS appliance as a client.
The following list summarizes the steps needed for the ISKLM server setup. It is
important to work with your IBM Security Key Lifecycle Manager (ISKLM) system
administrator to configure the ISKLM server to communicate with the NPS
appliance.
ISKLM server setup
The ISKLM administrator must complete the following tasks:

v Create a device group for a Generic device type. The group is identified by its
group name.

v Create a device under the new group to represent the NPS appliance. The device
is identified by a unique serial number that is assigned by the ISKLM
administrator. (This serial number does not have to be the serial number of the
NPS appliance
v Set the new device to allow KMIP delete action. (This allows the ISKLM server
to delete old AEKs after the NPS administrator changes them on the NPS host.)
v Export the CA certificate that the client (the NPS appliance) can use to
authenticate the server certificate. The certificate must be in PEM (.pem) format.
NPS appliance setup
After the ISKLM administrator has added the NPS appliance to the ISKLM server,
make sure that you have the following information:
v The CA certificate and the client certificate in .pem format from the ISKLM
server
v The device group name created on the ISKLM server
v The device serial number created on the ISKLM server
v The ISKLM IP address and KMIP port value
To configure the ISKLM information on the NPS appliance, the NPS administrator
must do the following steps:
1. Log in to the active NPS host as the root user.
2. Save a copy of the CA certificate and client certificate files (must be in .pem
format) in the /nz/data/security directory.
3. Log in to the active NPS host as the nz user.
4. Using any text editor, edit the /nz/data/config/system.cfg file (or create the
file if it does not exist).
5. Define the following settings in the system.cfg file:
startup.kmipDevGrpSrNum = Device_serial_number
startup.kmipDevGrp = Device_group_name
startup.kmipClientCert = /nz/data/security/client.pem
startup.kmipClientKey = /nz/data/security/privkey.pem
startup.kmipCaCert = /nz/data/security/ca.pem
startup.keyMgmtServer = tls://ISKLM_IP_ADDRESS:KMIP_PORT
startup.keyMgmtProtocol = local
The keyMgmtProtocol = local setting indicates that the system uses a locally
managed keystore and keys. Keep the local setting until you verify that the
connections to the ISKLM server are correctly configured and working. After
that verification, and after uploading the AEKs to the ISKLM server, you can
change the setting to use the ISKLM keystore.
6. Save the system.cfg file.
7. Log out of the nz account and return to the root account.
Testing the ISKLM server connection
As root, use the nzkmip test command on the NPS host to test ISKLM
connectivity. This command requires you to specify a label and key (either directly
or in a file) to test the ISKLM server operations:
[root@nzhost ~]# /nz/kit/bin/adm/nzkmip test -label spuaek
-file /tmp/new_spukey.pem
Connecting to SKLM server at tls://1.2.3.4:5696
Success: Connection to SKLM store succeeded

Preparing to switch from the local to the ISKLM keystore
After you confirm that the ISKLM connection is working, follow these steps to
prepare for switching over to the ISKLM server.
1. As root, run the following command to populate the keys from the local
keystore to the ISKLM keystore:
[root@nzhost ~]# /nz/kit/bin/adm/nzkmip populate
2. To confirm that the keys were populated correctly, query the _t_kmip_mapping
table:
SYSTEM.ADMIN(ADMIN)=> select * from _t_kmip_mapping;
DISKLABEL | UID
-------------+-----------------------------------------
spuaek | KEY-56e36030-3a9c-4313-8ce6-4c6d5d898211
spuaekOld | KEY-56e36030-3a9c-4313-8ce6-4c6d5d898312
hostkey1 | KEY-56e36030-3a9c-4313-8ce6-4c6d5d898432
hostkey1Old | KEY-56e36030-3a9c-4313-8ce6-4c6d5d898541
hostkey2 | KEY-56e36030-3a9c-4313-8ce6-4c6d5d898865
hostkey2Old | KEY-56e36030-3a9c-4313-8ce6-4c6d5d898901
(6 rows)
3. For each UUID listed in the table, run the following command to display the
value of the key:
[root@nzhost ~]# /nz/kit/bin/adm/nzkmip get
-uuid KEY-56e36030-3a9c-4313-8ce6-4c6d5d898211
Key Value : t7Nº×nq¦CÃ<"*"ºìýGse»¤;|%
4. Create a backup of the local keystore with nzkeybackup. As a best practice, save
the backup to a secure location away from the NPS host.
Switch from local keystore to ISKLM
After you have completed and tested the ISKLM connection, and you have created
a local keystore backup file, follow these steps to switch to the ISKLM server:
1. Log in to the NPS host as the nz user.
2. Stop the system using the nzstop command.
3. Rename the local GSKit keystore to keydb.pl2 and keydb.sth files.
4. Log in as root and edit the /nz/data/config/system.cfg file.
5. Change the setting for the keyMgmtProtocol to kmipv1.1 to switch to the
ISKLM server support:
startup.keyMgmtProtocol = kmipv1.1
6. Save and close the system.cfg file.
7. Log out of the root account to return to the nz account.
8. Start the system using the nzstart command. After the system starts, AEKs that
you create with the nzkey command are stored in and retrieved from the
ISKLM server.
9. Remove the renamed GSKit keystore files keydb.pl2 and keydb.sth.
Disable ISKLM AEK storage
If you need to change the NPS host to disable ISKLM support and return to a local
GSKit keystore for managing the keys, follow these steps:
1. Log in as root to the NPS host.
2. Dump the keys from ISKLM server to a local GSKit keystore:
[root@nzhost ~]# /nz/kit/bin/adm/nzkey dump
DB creation successful

Switch from ISKLM to the local keystore
After you have dumped the AEKs from the ISKLM server, follow these steps to
switch to a local keystore for the AEKs:
1. Log in to the NPS host as the nz user.
2. Stop the system using the nzstop command.
3. Log in as root and edit the /nz/data/config/system.cfg file.
4. Change the setting for the keyMgmtProtocol to local to switch to the local
GSKit keystore support:
startup.keyMgmtProtocol = local
5. Save and close the system.cfg file.
6. Run the following command to verify that the keys were dumped correctly:
[root@nzhost ~]# /nz/kit/bin/adm/nzkey list
7. Log out of the root account to return to the nz account.
8. Start the system using the nzstart command.
9. After the system starts, use the nzsql command to connect to the SYSTEM
database and delete entries from the _t_kmip_mapping table because the
system is now using a local GSKit keystore.
SYSTEM.ADMIN(ADMIN)=> truncate table _t_kmip_mapping;
TRUNCATE TABLE
After the system starts, AEKs that you create with the nzkey command are stored
and retrieved from the local keystore.
SED authentication keys

The authentication keys you use to lock the SEDs have the following requirements
and behaviors.
You can create and apply an authentication key to auto-lock the host drives and
the drives in the storage arrays. An authentication key must be 32 bytes. The keys
are managed using the IBM GSKit software. No other key management software or
server is required.
CAUTION:
Always protect and back up the authentication keys that you create and apply to
the disks. If you lose the keys, the disks cannot be unlocked when they are
powered on. You will be unable to read data from the disks, and you could
prevent the NPS system from starting.
You could create a conforming key for the host and SPU AEKs, but as a best
practice, you should use the nzkey generate command to automatically create a
random, conformant AEK for the host or SPU drives and store it in your local
keystore or in the ISM Security Key Lifecycle Manager if you have configured that
support for your appliance.
Each of the hosts in the appliance use an AEK to auto-lock the SEDs. The keys are
referred to as hostkey1 and hostkey2. The host RAID controllers have specific
requirements for the host authentication keys:
v The key value must be 32 bytes in length.
v The key is case-sensitive.
v The key must contain at least one number, one lowercase letter, one uppercase
letter, and one non-alphanumeric character (for example, < > @ +). You cannot
specify a blank space, single quotation character, double quotation character,
exclamation point, or equals sign in the key value.
v The key can use only the printable characters in the range ASCII 0x21 to 0x7E.
The SEDs in the storage arrays use the SPU AEK to auto-lock the drives. The
storage array SPU keys must meet the following requirements:
v The key value must be 32 bytes in length.
v The key can use characters in the range ASCII from 0x00 to 0xFF.
Generate authentication keys

You use the nzkey generate command to create a conformant host or SPU key for
the SED drives.
Before you begin
If you want to change the host or SPU key that is used to lock your SEDs, you can
create a key manually, or you can use the nzkey generate command to create a
conforming key. Run separate commands to create the host key and the SPU key.
Procedure
2. Use the following command to create a host key:
[root@nzhost1 nz]# /nz/kit/bin/adm/nzkey generate -hostkey
-file /export/home/nz/hostkey.txt
Host key written to file
3. Use the following command to create a SPU key:
[root@nzhost1 nz]# /nz/kit/bin/adm/nzkey generate -spukey
-file /export/home/nz/spukey.txt
SPU key written to file
Results
The command creates saves the key in the specified file in plaintext. You can then
specify the host or key file as part of an nzkey change operation.
Important: The key files are in plain text and unencrypted. After you use the files
to change the key for the hosts or SPUs, make sure that you delete the generated
key files to protect the keys from being read by users who log in to the NPS
system.
List authentication keys

You use the nzkey list command to list the key labels that are in the keystore.
Before you begin
You can use the nzkey list command to display information about the keys that
are currently defined in the keystore without displaying the key text.
Procedure
2. Use the following command to list the key labels:

[root@nzhost1 nz]# /nz/kit/bin/adm/nzkey list
hostkey1
hostkey1Old
hostkey2
hostkey2Old
spuaek
spuaekOld
The sample output shows all the possible keys, although the output could
include a subset of these labels.
v hostkey1 is the label for the current AEK for host1. It is in the keystore if the
host1 drives have been auto-locked.
v hostkey1Old is the label for the previous AEK for host1 when a key change
is in progress. It is in the keystore if you changed the AEK for the host1
drives.
v hostkey2 is the label for the current AEK for host2. It is in the keystore if the
host2 drives have been auto-locked.
v hostkey2Old is the label for the previous AEK for host2 when a key change
is in progress. It is in the keystore if you changed the AEK for the host2
drives.
v spuaek is the label for the current AEK for the SPU. It is in the keystore if
the SPU drives have been auto-locked.
v spuaekOld is the label for the previous AEK for the SPU when a key change
is in progress. It is in the keystore if you changed the AEK for the SPU
drives.
Results
The command shows the labels for the keys that are currently in the keystore. If
AEKs has not been set, the command displays the message No keys found in key
store. You can use the -hostkey or -spukey option to list only the AEK labels for
the hosts or SPU.
Check authentication keys

You use the nzkey check command to check whether AEK is enabled, whether
SEDs are auto-locked, and more information about the AEK state for the SEDs.
Before you begin
You can use the nzkey check command to display information about auto-lock
state for the SEDs on the hosts and SPUs.
Procedure
2. Use the following command to check the AEK status. You must specify the
-spukey or the -hostkey option.
[root@nzhost1 nz]# /nz/kit/bin/adm/nzkey check {-spukey | -hostkey}
The command displays the following output.

Table 6-1. nzkey check output samples. Possible output for the nzkey check command.
Output Description
AEK feature is enabled The AEK key feature is enabled for the
system. This indicates that the IBM
installers or IBM support has enabled
the auto-lock feature on the system.
AEK feature is not enabled The AEK key feature is not enabled for
the system. This indicates that the IBM
installers or IBM support has not
enabled the auto-lock feature on the
system
Host AEK status: When you specify the -hostkey
Verification of host ha1 AEK key: SUCCESS operation and AEK is enabled, this
Verification of host ha2 AEK key: SUCCESS message indicates that the host SEDs
are auto-locked. If the report shows a
failure, make sure that you contact IBM
Support promptly to investigate.
Failures indicate problems that must be
resolved to avoid downtime and
potential data loss.
Host AEK status: When you specify the -hostkey
Host ha1 AEK key not set operation and AEK is enabled, this
Host ha2 AEK key not set message indicates that the host SEDs
are not auto-locked.

Table 6-1. nzkey check output samples (continued). Possible output for the nzkey check
command.
Output Description
AEK key operations are not in progress When you specify the -spukey
SPU AEK status: operation and AEK is enabled, the
Unused = 2 command displays information about
Unset = 0 whether AEK operations are in
Old = 0 progress, and the status of the APU
New = 286
AEKs applied to the storage array
Error = 0
Error(Old) = 0 disks.
Fatal = 0
Repair = 0 If the SPU key change is in progress,
------------------ you can also use the -progress option
Total disks = 288 to display a progress percentage until
the update is complete.
You can use this command to identify

whether some or all of the disks are
using the new AEK, the old/former
AEK, or whether there are errors or
issues to investigate. The status values
indicate the following conditions:
v Unused indicates that the drives are
out of service and cannot be checked.
(It may be in the inactive or failed
role.)
v Unset indicates that the key for a
disk in the Assigned, Assigning,
Active, and Spare states is not set.
v Old indicates that the drives use the
previous/former AEK.
v New indicates that the drives use the
new AEK.
v Error indicates that the key check
failed due to an unexpected error,
such as a disk I/O error.
v Error(old) indicates that the drives
could authenticate with the old key,
but not the new one.
v Fatal indicates that the disk could
not authenticate with either the new
key or the old key.
v Repair indicates that the key
operation has been deferred until a
regen is complete on the disks's
raided partner.
This sample output shows that 286 of

288 drives in an N3001-010 system are
using the new SPU AEK for
auto-locking. Two drives (Unused) are
out of service and could not be
checked.
SPU AEK key not set When you specify the -spukey
operation and AEK is enabled, this
message indicates that the storage array
SEDs are not auto-locked.

Results
The command provides more information about whether AEK feature is enabled or
disabled, and whether keys have been applied to auto-lock the SEDs in the hosts
and storage arrays. The command also provides information to alert you when
there may be issues with the drives that need further investigation and possible
troubleshooting from IBM Support.
Extract authentication keys

You use the nzkey extract command to extract the AEK defined in the keystore
and save the plaintext key for a specific key label to a file.
Before you begin
You can use the nzkey list command to list the available key labels defined in the
keystore. You can extract only one key to a file. If the file exists, the command
displays an error.
Procedure
2. Use the following command to extract the key for a specified label. For
example:
[root@nzhost1 nz]# /nz/kit/bin/adm/nzkey extract -label hostkey1
-file /nz/var/hostkey1.txt
Key written to file
Results
The command creates a file with the extracted AEK. This file can be helpful in
cases where you need the current key to reapply a key to SEDs for
troubleshooting, or if you want to preserve the key in a third-party key tracking
system. As a best practice, make sure that the output file is safe from unauthorized
access. Consider deleting the file or moving it to a secure location to protect the
key.
Change the host authentication key

You use the nzkey change -hostkey command to change the AEK for the hosts on
the appliance.
Before you begin
Before you begin, make sure that you have your new AEK for the hosts. You
should use the nzkey generate command to generate a new AEK for the host key.
To change the host AEK, the NPS system must be in the Stopped state. The new
AEK takes effect on both hosts when the nzkey command finishes running
successfully. The command creates a backup copy of the current keystore before it
changes the key. After the change is finished, you should create a backup of the
new keystore using the nzkeybackup command.
Procedure
1. Log in to the active host of the NPS system as the nz user.
2. Transition the system to the Stopped state, for example:

[nz@nzhost1 ~]$ nzsystem stop
3. Run the nzstate command to confirm that the system is in the Stopped state.
4. Log in as the root user:
[nz@nzhost1 ~]$ su - root
5. Use the nzkey change command to change the host key:
[root@nzhost-h1 ~] /nz/kit/bin/adm/nzkey change -hostkey
-file /usr/key/hostkey_change -backupdir /nz/var/backups/
# Keystore archive /nz/var/backups/keydb_20140711054140.tar.gz written
==========================================================
AEK Summary
==========================================================
Result: Key operation completed successfully.

6. Create a backup of the updated keystore:
[root@nzhost-h1 ~] /nz/kit/bin/adm/nzkeybackup /nz/var/keybackup.tar.gz
Keystore archive /nz/var/keybackup.tar.gz written
7. Log out of the root account and return to the nz account.
8. Run the nzstart command to return the system to the Online state.
What to do next
After they key is successfully applied, move the /nz/var/keybackup.tar.gz to a

secure location away from the appliance so that you have a backup available for
disaster recovery of the keystore. You should also delete the host key file
(/usr/key/hostkey_change in this example) as a security precaution for someone
finding your authentication key outside the protected keystore.
For more information about the command:

v “The nzkey command” on page A-34
Resume host AEK key change

You use the nzkey resume command to resume an interrupted host AEK create or
change operation.
Before you begin
You would typically use the nzkey resume command to resume a host AEK change
operation that was interrupted and did not complete. This command can also be
used to resume a host AEK create operation, but typically the IBM installers or
IBM support perform the tasks to create and enable the AEKs to auto-lock drives.
To resume the host AEK operation, you must have the backup file pathname for
the interrupted operation.
Procedure
2. Use the following command to resume a host AEK change operation. For
example:
[root@nzhost1 nz]# /nz/kit/bin/adm/nzkey resume
-backupDir /nz/var/hostbup_01
Results
The command resumes the host key operation. If the command displays an error,
contact IBM Support for assistance.

Change the SPU authentication key
You use the nzkey change -spukey command to change the AEK for the storage
array SEDs.
Before you begin
Before you begin, make sure that you have your new AEK for the SPU. You should
use the nzkey generate command to generate a new AEK for the SPU key.
If you are changing the SPU key for the storage array drives, system must be in
the Paused or Offline mode because the system manager must be running to
propagate the new key but no queries or I/O activity should be active. The new
AEK is immediately communicated from the system manager to the SPUs. Note
that if you attempt to transition the system to the Online state, the state transition
wait until all the SPUs and disks are updated with the new AEK. The command
creates a backup copy of the current keystore before it changes the key. After the
change is finished, you should create a backup of the new keystore using the
nzkeybackup command.
Procedure
1. Log in to the active host of the NPS system as the nz user.
2. Transition the system to the Paused or Offline state, for example:
[nz@nzhost1 ~]$ nzsystem pause
Are you sure you want to pause the system (y|n)? [n] y
3. Log in as the root user:
[nz@nzhost1 ~]$ su - root
4. Use the nzkey change command to change the SPU key:
[root@nzhost-h1 ~] /nz/kit/bin/adm/nzkey change -spukey
-file /tmp/spukey_change -backupdir /tmp/backups/
# Keystore archive /tmp/backups/keydb_20140711054140.tar.gz written
==========================================================
AEK Summary
==========================================================
Result: Key operation completed successfully.

-> You can run ’nzsystem resume’ to resume the system state.
5. Create a backup of the updated keystore:
[root@nzhost-h1 ~] /nz/kit/bin/adm/nzkeybackup /nz/var/keybackup.tar.gz
6. Log out of the root account and return to the nz account.
7. Run the nzsystem resume command to return the system to the Online state.
What to do next
After they key is successfully applied, move the /nz/var/keybackup.tar.gz to a

safe location away from the appliance so that you have a backup available for
disaster recovery of the keystore. You should also delete or move the SPU key file
(/tmp/spukey_change in this example) as a precaution.
For more information about the command:

v “The nzkey command” on page A-34

AekSecurityEvent
The NPS system has a default event type AekSecurityEvent that can monitor and
report issues with the SED drives.
The AekSecurityEvent monitors the SED drives and sends an email to the
configured event contacts when any of the following conditions occur:
v The system has transitioned to the Down state because of a SPU AEK operation
failure.
v A SPU AEK operation has occurred, such as successful completion of key create
or change for the SPU key.
v A labelError has been detected on a disk for the SPU key. A labelError typically
occurs when the new SPU key is not applied to a disk and the disk still uses the
old/former key to authenticate.
v A fatal error is detected on a disk for the SPU key. A fatal error occurs when
neither the current SPU key nor the previous SPU key can be used to key to
authenticate the drive.
v A key repair state is detected on a disk during a SPU key create or change. A
key repair state issue occurs when the key operation is deferred on a SED
because of a key fatal error on the drive's RAID partner disk.
v The system manager has started a key repair operation. This usually occurs just
before applying the key on the deferred disk after the regen on the disk has
finished.
To create and enable an event rule for the AekSecurityEvent, you use the nzevent
command to add an event rule as in the following example. Make sure that you
run the command on the active host.
[nz@nzhost1 ~]$ nzevent copy -useTemplate
-name AekSecurityEvent -newName SedAekEvent -eventType AekSecurityEvent
-on 1 -dst user@mycompany.com

Chapter 7. Manage the Netezza server
This section describes how to manage the IBM Netezza server and processes. The
Netezza software that runs on the appliance can be stopped and started for
maintenance tasks, so this section describes the meaning and impact of system
states.
This section also describes log files and where to find operational and error
messages for troubleshooting activities. Although the system is configured for
typical use in most customer environments, you can also tailor software operations
to meet the special needs of your environment and users by using configuration
settings.
Software revision levels

The software revision level is the release or version of the IBM Netezza software
that is running on your Netezza appliance.
The revision level typically includes a major version number, a release number, a
maintenance release number, and a fix pack number. Some releases also include a
patch designation such as P1 or P2.
Display the Netezza software revision

You can use the nzrev command to display the current IBM Netezza software
revision. If you enter the nzrev command with no arguments, Netezza returns the
release number string and the build number. For example:
nzrev
Release 7.1.0.0 [Build 34879]
When you enter the nzrev -rev command, Netezza returns the entire revision
number string, including all fields (such as variant and patch level, which in this
example are both zero).
nzrev -rev
7.1.0.0-P0-F1-Bld34879
From a client system, you can use the following command to display the revision
information:
nzsystem showRev -host host -u user -pw password
Related reference:
“The nzrev command” on page A-47
Use the nzrev command to display the IBM Netezza software revision level.
Display the software revision levels

You can use the nzcontents command to display the revision and build number of
all the executable files on the host. This command takes several seconds to run and
results in multiple lines of output.
Note: Programs with no revisions are scripts or special binary files.

When you enter the nzcontents command, IBM Netezza displays the program
names, the revision stamps, the build stamps, and checksum. The following sample
output shows a small set of output, and the checksum values are truncated to fit
the output messages on the page.
Program Revision Stamp Build Stamp CheckSum
-------------- ------------------------ ----------------------------- --------------
adm Directory
nzbackup 7.1.0.0-P0-F1-Bld34879 2014-01-08.34879...24438 3d5da...
nzcontents ab685...
nzconvert 7.1.0.0-P0-F1-Bld34879 2014-01-08.34879...24438 3a52...
nzds 7.1.0.0-P0-F1-Bld34879 2014-01-08.34879...24438 d3f2...
The following table describes the components of the Revision Stamp fields.
Table 7-1. Netezza software revision numbering
Version Release Maintenance Fixpack -Pn -Fn -Bldn
Numeric Numeric Numeric Numeric Alphanumeric Alphanumeric Alphanumeric
Incremented Incremented Incremented Incremented Incremented for Rare cases of a Incremented

for major for minor for for quarterly a monthly patch hot fix release. serially for a
releases. releases. maintenance update release after a production build
releases. releases. fixpack release. number.
Commonly P1
and P2.
System states
The IBM Netezza system state is the current operational state of the appliance.
In most cases, the system is online and operating normally. There might be times
when you must stop the system for maintenance tasks or as part of a larger
procedure.
You can manage the Netezza system state by using the nzstate command. It can
display and wait for a specific state to occur.
Related reference:
“The nzstate command” on page A-58
Use the nzstate command to display the current system state or to wait for a
particular system state to occur.
Display the current system state

You can use the nzstate command to display the current system state.
[nz@nzhost ~]$ nzstate
The following table lists the common system states and how they are invoked and
exited.

Table 7-2. Common system states
States Description Invoked Exited
Online Select this state to The system enters The system exits the
make the IBM this state when you online state when
Netezza fully use the nzsystem you use the nzsystem
operational. This restart or resume stop, offline, pause,
state is the most command, or after or restart
common system you boot the system. commands.
state. In this state,
the system is ready
to process or is
processing user
queries.
Tip: You can also use the nzsystem restart command to quickly
stop and start all server software. You can use the nzsystem restart
command only on a running Netezza that is in a non-stopped state.
Offline Select this state to The system enters The system exits this
interrupt the this state when you state when you use
Netezza. In this state, use the nzsystem the nzsystem resume
the system completes offline command. or stop command.
any running queries,
but displays errors
for any queued and
new queries.
Paused Select this state when The system enters the The system exits the
you expect a brief paused state when paused state when
interruption of server you use the nzsystem you use the nzsystem
availability. In this pause command. resume or stop
state, the system command, or if there
completes any is a hardware failure
running queries, but on an active SPU.
prevents queued or
new queries from
starting. Except for
the delay while in
the paused state,
users do not notice
any interruption in
service.
Down The system enters the Not user invoked. You must repair the
down state if there is system hardware and
insufficient hardware then use the nzsystem
for the system to resume command.
function even in
failover mode. For
more information
about the cause of
the Down state, use
the nzstate -reason
command.
Chapter 7. Manage the Netezza server 7-3

Table 7-2. Common system states (continued)
States Description Invoked Exited
Stopped Select this state for The system enters the The system exits the
planned tasks such as stopped state when stopped state when
installation of new you use the nzsystem you use the nzstart
software. In this stop or the nzstop command.
state, the system command. If you use
waits for currently the nzstop command,
running queries to the system stops all
complete, prevents running queries.
queued or new
queries from starting,
and then shuts down
all Netezza software.
System states reference

When the IBM Netezza software is running, the system and SPUs can transition
through the following operational states. The states that end in the letters ing (such
as Pausing, Pausing Now, Discovering) are typically transitional states that are
short in duration. The other states such as those described in Table 7-2 on page 7-3
are usually the longer duration states; the system usually remains in those states
until operator action forces a state change. The following table describes all of the
system states.
Table 7-3. System states reference
State Description
Down The system is not configured (there is no configuration information
for the data slices to SPU topology) or there is not enough working
hardware to operate the system even in failover.
The SPUs can never be in this state.

Discovered The SPUs and other components are discovered, but the system is
waiting for all components to complete start-up before transitioning
to the initializing state.
Discovering The System Manager is in the process of discovering all the system
components that it manages.
Going Offline The system is in an interim state that is going to offline.
Going Offline (Now) The system is in an interim state that is going to offline now.
Going Pre-Online The system is in an interim state, going to pre-online.
Going to Maintain
Initialized The system uses this state during the initial startup sequence.
Initializing The system is initializing. You cannot execute queries or
transactions in this state.
Maintain
Missing The System Manager detected a new, unknown SPU in a slot that
was previously occupied but not deleted.
Offline (Now) This state is similar to offline, except that the system stops user jobs
immediately during the transition to offline.
For more information, see Table 5-4 on page 5-10.

Online The system is running normally. It can service requests.

Table 7-3. System states reference (continued)
State Description
Paused The system is paused. You cannot run user jobs.
Paused (Now) This state is similar to paused, except that the system stops user
jobs immediately when it transitions to paused.
For more information, see Table 5-4 on page 5-10.

Pausing The system is transitioning from online to paused. In this state, no
new queries or transactions are queued, although the system allows
current transactions to complete unless you used the nzsystem
pause -now command.
Pausing Now The system is attempting to pause because of a hardware failure, or
the administrator entered the nzsystem pause -now command.
Pre-Online The system has completed initialization. The system goes to the
resume state.
Resuming The system is waiting for all its components (SPUs and host
processes) to reach the online state before it changes the system
state to online.
Stopped The system is not running. Commands assume this state when they
attempt to connect to a system and get no response.
The SPUs can never be in this state.

Stopped (Now) This state is similar to stopped, except that the system stops user
jobs immediately when it makes the transition to stopped.
Stopping The system is transitionimg from online to stopped.
Stopping Now The system is attempting to stop, or the administrator entered the
nzsystem stop -now command.
Unreachable The System Manager cannot communicate with the SPU because it
has failed or it was physically removed from the system.
Wait for a system state

You use the nzstate command to wait for a specific operational state to occur
before you proceed with other commands or actions. You can use the nzstate
command to list the system states that you can wait for, as follows:
[nz@nzhost ~]$ nzstate listStates

------------ ------------------------------------------------------------
v To wait for the online state or else timeout after 10 seconds, enter:
nzstate waitfor -u admin -pw password -host nzhost -type online
-timeout 10
v To test scripts or do maintenance, enter:
nzsystem pause -force
nzstate waitfor -u admin -pw password -host nzhost -type paused
-timeout 300

Do some maintenance, and then resume the system:
nzsystem resume
nzstate waitfor -u admin -pw password -host nzhost -type online
-timeout 120
Run a query.
Manage the system state

You use the nzstart to start the IBM Netezza system operations. You use the
nzstop command stop the Netezza system operations. The nzsystem command
provides more state change options, such as pausing the system, resuming the
system, and restarting the system.
All nzsystem subcommands, except the nzsystem showState and showRev

commands, require the Manage System administrative privilege. For more
information, see Table 11-1 on page 11-10.
Note: When you stop and start the Netezza system operations on a Netezza C1000
system, the storage groups continue to run and perform tasks such as media
checks and health checks for the disks in the array, as well as disk regenerations
for disks that fail. The RAID controllers are not affected by the Netezza system
state.
Start the system

When you start the IBM Netezza system, you bring the system and database
processes fully online so that the Netezza system is ready to run user queries and
other tasks.
You can use the nzstart command to start system operation if the system is in the
stopped state. The nzstart command is a script that initiates a system start by
setting up the environment and invoking the startup server. The nzstart command
does not complete until the system is online. The nzstart command also verifies
the host configuration to ensure that the environment is configured correctly and
completely; it displays messages to direct you to files or settings that are missing
or misconfigured.
To start the Netezza system, enter:

nzstart
(startupsvr) Info: NZ-00022: --- program ’startupsvr’ (23328)
starting on host ’nzhost’ ... ---
Restriction: You must run nzstart on the host and be logged on as the user nz.
You cannot run it remotely from Netezza client systems.
For IBM Netezza 1000 and IBM PureData System for Analytics N1001 systems, a
message is written to the sysmgr.log file if there are any storage path issues that
are detected when the system starts. The log displays a message similar to mpath
-issues detected: degraded disk path(s) or SPU communication error, which
helps to identify problems within storage arrays.
Related reference:
“The nzstart command” on page A-56
Use the nzstart command to start system operation after you stop the system. The
nzstart command is a script that initiates a system start by setting up the
environment and starting the startup server.

Stop the system

When you stop the IBM Netezza system, you stop the database processes and
services. The system aborts and rolls back any active queries, so user queries or
tasks such as loads, backups, and others cannot run. Typically, you stop the server
when directed to do so as part of a specific administration procedure or when you
must perform a major management task. You can use the nzstop command to stop
a running system. (You can also use the nzsystem stop command, but nzstop is the
recommended method.) Stopping a system stops all Netezza host processes.
Restriction: You must run nzstop on the host and be logged on as the user nz.
You cannot run it remotely.
To stop the system, use the nzstop command.
To stop the system or exit after waiting for 5 minutes (300 seconds), enter nzstop
-timeout 300.
Related reference:
“The nzstop command” on page A-63
Use the nzstop command to stop the IBM Netezza software operations. Stopping a
system stops all the IBM Netezza processes that were started with the nzstart
command.
Pause the system

Certain management tasks such as host backups require the system to be in the
paused state. When you pause the system, the system queues any new queries or
work until the system is resumed. By default, the system finishes the queries and
transactions that are active at the time the pause command is issued.
To transition to the paused state, enter:

[nz@nzhost ~]$ nzsystem pause
Enter y to continue. The transition completes quickly on an idle system, but it can
take much longer if the system is busy processing active queries and transactions.
When the transition completes, the system enters the paused state, which you can
confirm with the nzstate command as follows:
System state is ’Paused’.
You can use the -now option to force a transition to the paused state, which causes
the system to abort any active queries and transactions. As a best practice, use the
nzsession show -activeTxn command to display a list of the current active
transactions before you force the system to terminate them.
Resume the system

When a system is paused or offline, you can resume the normal operations by
resuming the system. When you resume the system from a paused state, it starts to
process all the transactions that were submitted and queued while it was paused.
In some cases, the system also restarts certain transactions that support the restart
operations.
To resume the system and return it to the online state, enter:

[nz@nzhost ~]$ nzsystem resume
The command usually completes quickly; you can confirm that the system has
returned to the online state by using the following command:
Take the system offline

When you take the system offline, the system does not queue any new work or
transactions. The state only allows maintenance tasks to run. By default, the system
finishes the queries and transactions that are active at the time the offline
command is issued.
To make the transition to the offline state, enter:

[nz@nzhost ~]$ nzsystem offline
Are you sure you want to take the system offline (y|n)? [n] y
Enter y to continue. The transition completes quickly on an idle system, but it can
take much longer if the system is busy processing active queries and transactions.
When the transition completes, the system enters the offline state, which you can
confirm with the nzstate command as follows:
System state is ’Offline’.
You can use the -now option to force a transition to the offline state, which causes
the system to abort any active queries and transactions. As a best practice, use the
nzsession show -activeTxn command to display a list of the current active
transactions before you force the system to terminate them.
Restart the system

When a system is in the online state but a system problem occurs, you can restart
the system, which stops and starts all server software. You can use the nzsystem
restart command only on a running system that is in a non-stopped state.
To restart the system, enter:

[nz@docspubox ~]$ nzsystem restart
Are you sure you want to restart the system (y|n)? [n] y
Overview of the Netezza system processing

When you start the IBM Netezza system, you automatically start a number of
system processes. The following table describes the Netezza processes.
Table 7-4. Netezza processes
Process Description
bnrmgr v Handles incoming connections from the nzbackup and nzrestore
commands.
v Starts an instance of the backupsvr or restoresvr to handle each client
instance.
bootsvr v Informs TFTP client (the SPUs) of the location of their initial program
or download images on the host.
v Informs the SPUs where to upload their core file if a SPU is instructed
to create a core image for debugging purposes.

Table 7-4. Netezza processes (continued)
Process Description
clientmgr v Handles incoming connections from nz applications.
v This is not unlike the postmaster that handles incoming connections
from nzsql, ODBC, and others.
dbosDispatch v Accepts execution plans from the Postgres, backup, and restore process
or processes.
v Dynamically generates C code to process the query, and cross-compiles
the query so that it can be run on the host.
v Broadcasts the compiled code to the SPUs for execution.
dbosEvent v Receives responses and results from the SPUs. As appropriate, it might
have the SPUs do more steps as part of the query.
v Rolls up the individual result sets (aggregated, sorted, consolidated)
and sends the final results back to the client's Postgres, backup, or
restore process.
eventmgr v Processes events and event rules. When an event occurs, such as the
system changes state, a hardware component fails or is restarted, the
eventmgr checks to see whether any action must be taken based on
the event and if so, it takes action. The action can be sending an email
message or running an external program. For more information about
event rules, see Chapter 8, “Event rules,” on page 8-1.
loadmgr v Handles incoming connections from the nzload command.
v Starts an instance of the loadsvr to handle each instance of the nzload
command.
nzvacuumcat v At boot time, the system starts the nzvacuumcat command, which in
turn invokes the internal VACUUM command on system catalogs to
remove unneeded rows from system tables and compact disk space to
enable faster system table scanning.
v During system operation, the nzvacuumcat program monitors the
amount of host disk space that is used by system tables in each
database. It checks every 60 seconds. If the system catalog disk space
for a particular database grows over a threshold amount (128 KB), the
nzvacuumcat program initiates a system table vacuum (VACUUM) on
that database.
v The VACUUM command works on system tables only after it obtains
an exclusive lock on all system catalog tables. If it is unable to lock the
system catalog tables, it quits and tries again. Only when the
VACUUM command succeeds does the nzvacuumcat program change
the size of the database.
v While the VACUUM command is working, the system prevents any
new SQL or system table activity to start. This window of time is
usually about 1 to 2 seconds, but can be longer if significant amounts
of system catalog updates or deletes have occurred since the last
VACUUM operation.
postgres v Validates the access rights (user name, password, ACL).
v Parses the SQL, and generates the optimized execution plan.
v Returns the results set to the client application when the query finishes
executing.
Two default postgres jobs are associated with the sysmgr and the
sessionmgr processes.

Table 7-4. Netezza processes (continued)
Process Description
postmaster v Accepts connection requests from clients (nzsql, ODBC, and other
clients).
v Starts one postgres process per connection to service the client.
sessionmgr v Keeps the session table current with the state of the different sessions
that are running the system. For more information, see “Session
manager” on page 7-16.
startupsvr v Launches and then monitors all of the other processes. If any system
process dies, startupsvr follows a set of predefined rules, and either
restarts the failed process or restarts the entire system.
v Controlled by /nz/kit/sys/startup.cfg
statsmgr v Handles requests for statistics from the nzstats command. For more
information, see “Statistics server” on page 7-17.
statsSvr v Communicates with the nzstats command to obtain host-side
operational statistics.
v The nzstats command communicates with the sysmgr to obtain SPU
statistics.
sysmgr v Monitors and manages the overall state of the system.
v Periodically polls the SPUs to ensure that they are operational.
v Initiates state changes upon requests from the user or as a result of a
change in hardware status (for example, a SPU failure).
Related reference:
“System logs” on page 7-12
System states when Netezza starts

When you boot the system, the IBM Netezza software automatically starts. The
system goes through the following states:
1. Stopped
2. Discovering
3. Initializing
4. Preonlining
5. Resuming
6. Online
When you power up (or reset) the hardware, each SPU loads an image from its
flash memory and runs it. This image is then responsible for running diagnostic
tests on the SPU, registering the SPU with the host, and downloading runtime
images for the SPU CPU and the FPGA disk controller. The system downloads
these images from the host through TFTP.

System errors
During system operation different types of errors can occur. The following table
describes some of those errors.
Table 7-5. Error categories
Category Description Example
User error An error on the part of the user, Invalid user name, invalid SQL
usually because of incorrect or invalid syntax.
input.
Component A hardware or software system SPU failure; host process
failure component failure. crashes.
Environment A request of an environment facility A file is locked; a buffer is full.
failure fails. This is often because of resource
or access problems.
Recoverable A detected internal programming error Unknown case value or msg
internal error that is not severe enough to abort the type; file close fails.
program.
Unrecoverable A detected internal programming error Core, memory corruption, assert
internal error or a corrupted internal state that fails.
requires the program to abort.
The IBM Netezza system can take the following actions when an error occurs:
Display an error message
Presents an error message string to the users that describes the error. This
is the common system response whenever a user request is not fulfilled.
Try again
During intermittent or temporary failures, keep trying until the error
condition disappears. The retries are often needed when resources are
limited, congested, or locked.
Fail over
Switches to an alternate or spare component because an active component
has failed. Failover is a system-level recovery mechanism and can be
triggered by a system monitor or an error that is detected by software that
is trying to use the component.
Log the error
Adds an entry to a component log. A log entry contains a date and time, a
severity level, and an error/event description.
Send an event notification
Sends notification through email or by running a command. The decision
whether to send an event notification is based on a set of user-configurable
event rules.
Abort the program
Terminates the program because it cannot continue because of an
irreparably damaged internal state or because continuing would corrupt
user data. Software asserts that detect internal programming mistakes often
fall into this category because it is difficult to determine that it is safe to
continue.
Clean up resources
Frees or releases resources that are no longer needed. Software components
are responsible for their own resource cleanup. In many cases, resources

are freed locally as part of each specific error handler. In severe cases, a
program cleanup handler runs before the program exits and frees/releases
any resources that are still held.
System logs
All major software components that run on the host have an associated log. Log
files have the following characteristics:
v Each log consists of a set of files that are stored in a component-specific
directory. For managers, there is one log per manager. For servers, there is one
log per session, and their log files have pid identifiers, date identifiers, or both
(<pid>.<yyyy-mm-dd>).
v Each file contains one day of entries, for a default maximum of seven days.
v Each file contains entries that have a timestamp (date and time), an entry
severity type, and a message.
The system rotates log files, that is, for all the major components there are the
current log files and the archived log files.
v For all IBM Netezza components (except postgres), the system creates a new log
file at midnight if there is constant activity for that component. If, however you
load data on Monday and then do not load again until Friday, the system creates
a new log file dated the previous day from the new activity, in this case,
Thursday. Although the size of the log files is unlimited, every 30 days the
system removes all log files that were not accessed.
v For postgres logs, by default, the system checks the size of the log file daily and
rotates it to an archive file if it is greater than 1 GB in size. The system keeps 28
days (four weeks) of archived log files. (Netezza Support can help you to
customize these settings if needed.)
To view the logs, log on to the host as user nz. When you view an active logfile,
use a file viewer command such as more, less, cat, tail, or similar commands. If
you use a text editor such as emacs or vi, you could cause an interruption and
possible information loss to log files that are actively capturing log messages while
the system is running.
Related concepts:
“Logging Netezza SQL information” on page 11-39
You can log information about all user or application activity on the server, and
you can log information that is generated by individual Windows clients.
Related tasks:
“Logging Netezza SQL information on the server” on page 11-39
Related reference:
“Overview of the Netezza system processing” on page 7-8
Backup and restore manager

The backup and restore manager logs information about the nzbackup and
nzrestore commands. The log file records the start and stop times of the nzbackup
and nzrestore processes and the start and stop times of the backupsvr and
restoresvr processes.
Log file
/nz/kit/log/bnrmgr/bnrmgr.log
Current backup and restore manager log

/nz/kit/log/bnrmgr/bnrmgr.YYYY-MM-DD.log
Archived log
Sample messages
2012-12-12 18:12:05.645586 EST Info: NZ-00022: --- program ’bnrmgr’ (26082)
2012-12-12 18:17:09.315244 EST Info: system is online - enabling backup and
restore sessions
Bootserver manager
The bootsvr.log file records the initiation of all SPUs on the system, usually when
the system is restarted by the nzstart command and also all stopping and
restarting of the bootsvr process.
Log files
/nz/kit/log/bootsvr/bootsvr.log
Current log
/nz/kit/log/bootsvr/bootsvr.YYYY-MM-DD.log
Archived log
Sample messages
2012-12-12 18:12:07.399506 EST Info: NZ-00022: --- program ’bootsvr’ (26094)
2012-12-12 18:15:25.242471 EST Info: Responded to boot request from device
[ip=10.0.14.28 SPA=1 Slot=1] Run Level = 3
Client manager
The clientmgr.log file records all connection requests to the database server and
also all stopping and starting of the clientmgr process.
Log files
/nz/kit/log/clientmgr/clientmgr.log
Current log
/nz/kit/log/clientmgr/clientmgr.YYYY-MM-DD.log
Archived log
Sample messages
2012-12-12 18:12:05.874413 EST Info: NZ-00022: --- program ’clientmgr’ (26080)
2012-12-12 18:12:05.874714 EST Info: Set timeout for receiving from the socket
300 sec.
2012-12-12 18:17:21.642075 EST Info: admin: login successful
Database operating system

The dbos.log file records information about the SQL plans submitted to the
database server and also the restarting of the dbos process.
Log files
/nz/kit/log/dbos/dbos.log
Current log
/nz/kit/log/dbos/dbos.YYYY-MM-DD.log
Archived log

Sample messages
2012-12-12 18:12:03.258402 EST Info: NZ-00022: --- program ’dbos’ (25991) starting
on host ’nzhost’ ... ---
2012-12-12 18:12:03.321092 EST Info: cacheDir=/nz/data.1.0/cache cacheImg=/nz/data
.1.0/cache/cache_img.txt m_size=52190 m_numDirs=307 m_ROWSIZE=170 m_planHistFiles=
2000
2012-12-12 18:17:38.713027 EST Info: plan queued: planid 1 tx 0x189402 cli 1 uid 1
001 sid 16056 pid [29672] (run 0/1)
2012-12-12 18:17:38.713306 EST Info: plan prep : planid 1 tx 0x189402 cli 1 uid 1
001 sid 16056 pid [29672] (run 0/1)
Plan ID
The plan number queued or started. This number relates to the
corresponding execution plan in the /nz/data/plans directory. The system
increments it for each new portion of SQL processed and resets it to 1
when you restart the system.
Q ID The queue to which this plan was assigned.
Tx ID The unique transaction identifier.
cli The ID of the client process.
UID The unique ID of the dbos client. Every time a client connects it receives a
unique number.
SID The ID related to the ID returned from the nzsession.
PID The process ID of the calling process running on the Netezza host.
Event manager
The eventmgr.log file records system events and the stopping and starting of the
eventmgr process.
Log files
/nz/kit/log/eventmgr/eventmgr.log
Current log
/nz/kit/log/eventmgr/eventmgr.YYYY-MM-DD.log
Archived log
Sample messages
2012-12-12 18:12:05.926667 EST Info: NZ-00022: --- program ’eventmgr’ (26081)
2012-12-12 18:13:25.064891 EST Info: received & processing event type =
hwNeedsAttention, event args = ’hwId=1037, hwType=host, location=upper host,
devSerial=06LTY66, eventSource=system, errString=Eth RX Errors exceeded threshold,
reasonCode=1052’ event source = ’System initiated event’
2012-12-12 18:16:45.987066 EST Info: received & processing event type =
sysStateChanged, event args = ’previousState=discovering, currentState=initializing,
eventSource=user’ event source = ’User initiated event’
Event type
The event that triggered the notification.
Event args
The argument that is being processed.
ErrString
The event message, which can include hardware identifications and other
details.

eventSource
The source of the event; system is the typical value.
Flow communications retransmit

The flow communications retransmit log file records retransmission processes.
Log files
/nz/kit/log/fcommrtx/fcommrtx.log
Current® log
/nz/kit/log/fcommrtx/fcommrtx.2006-03-01.log
Archived log
Sample messages
2012-12-12 18:12:03.055247 EST Info: NZ-00022: --- program ’fcommrtx’ (25990) star
ting on host ’nzhost’ ... ---
2012-12-12 18:12:03.055481 EST Info: FComm : g_defenv_spu2port=0,6,1,7,2,8,3,9,4,1
0,5,11,6,0,7,0,8,1,9,2,10,3,11,4,12,5,13,0
2012-12-12 18:12:03.055497 EST Info: FComm : g_defenv_port2hostthread=0,1,2,3,4,5,
6,7,8,9,10,11,12,13
Host statistics generator

The hostStatsGen.log file records the starting and stopping of the hostStatsGen
process.
Log files
/nz/kit/log/hostStatsGen/hostStatsGen.log
Current log
/nz/kit/log/hostStatsGen/hostStatsGen.YYYY-MM-DD.log
Archived log
Sample messages
2012-12-12 18:12:04.969116 EST Info: NZ-00022: --- program ’hostStatsGen’ (26077)
Load manager
The loadmgr.log file records details of load requests, and the stopping and starting
of the loadmgr process.
Log file
/nz/kit/log/loadmgr/loadmgr.log
Current log
/nz/kit/log/loadmgr/loadmgr.YYYY-MM-DD.log
Archived log
Sample messages
2004-05-13 14:45:07.454286 EDT Info: NZ-00022:
--- log file ’loadmgr’ (12225) starting on host ’nzhost’ ...
Postgres
The postgres.log file is the main database log file. It contains information about
database activities.

Log files
/nz/kit/log/postgres/pg.log
Current log
/nz/kit/log/postgres/pg.log.n
Archived log
Sample messages
2012-12-31 04:02:10.229470 EST [19122] DEBUG: connection: host=1.2.3.4 user=
MYUSR database=SYSTEM remotepid=6792 fetype=1
2012-12-31 04:02:10.229485 EST [19122] DEBUG: Session id is 325340
2012-12-31 04:02:10.231134 EST [19122] DEBUG: QUERY: set min_quotient_scale to
default
2012-12-31 04:02:10.231443 EST [19122] DEBUG: QUERY: set timezone = ’gmt’
2012-12-31 09:02:10.231683 gmt [19122] DEBUG: QUERY: select current_timestamp,
avg(sds_size*1.05)::integer as avg_ds_total, avg(sds_used/(1024*1024))::integer as
avg_ds_used from _v_spudevicestate
Session manager
The sessionmgr.log file records details about the starting and stopping of the
sessionmgr process, and any errors that are associated with this process.
Log files
/nz/kit/log/sessionmgr/sessionmgr.log
Current log
/nz/kit/log/sessionmgr/sessionmgr.YYYY-MM-DD.log
Archived log
Sample messages
2012-12-12 18:11:50.868454 EST Info: NZ-00022: --- program ’sessionmgr’ (25843)
SPU cores manager

The spucores.log file contains the core file if a SPU aborts. If several SPUs abort,
the system creates a core file for two of the SPUs. A SPU log file has a name in the
form /nz/kit/log/spucores/spulog<spuid>.<date>_<info>.gz .
Startup server
The startupsvr.log file records the start of the IBM Netezza processes and any
errors that are encountered with this process.
Log files
/nz/kit/log/startupsvr/startupsvr.log
Current log
/nz/kit/log/startupsvr/startupsvr.YYYY-MM-DD.log
Archived log
Sample messages
2012-12-12 18:11:43.951689 EST Info: NZ-00022: --- program ’startupsvr’ (25173)
2012-12-12 18:11:43.952733 EST Info: NZ-00307: starting the system, restart = no
2012-12-12 18:11:43.952778 EST Info: NZ-00313: running onStart: ’prepareForStart’
2012-12-12 18:11:43 EST: Rebooting SPUs via RICMP ...

Statistics server
The statssvr.log file records the details of starting and stopping the statsSvr and
any associated errors.
Log files
/nz/kit/log/statsSvr/statsSvr.log
Current log
/nz/kit/log/statsSvr/statsSvr.YYYY-MM-DD.log
Archived log
Sample messages
2012-12-12 18:12:05.794050 EST Info: NZ-00022: --- program ’statsSvr’ (26079)
System Manager
The sysmgr log file records details of stopping and starting the sysmgr process,
and details of system initialization and system state status.
Log file
/nz/kit/log/sysmgr/sysmgr.log
Current log
/nz/kit/log/sysmgr/sysmgr.YYYY-MM-DD.log
Archived log
Output
2012-12-12 18:12:05.578573 EST Info: NZ-00022: --- program ’sysmgr’ (26078) starting
on host ’nzhost’ ... ---
2012-12-12 18:12:05.579716 EST Info: Starting sysmgr with existing topology
2012-12-12 18:12:05.882697 EST Info: Number of chassis level switches for each
chassis in this system: 1
The nzDbosSpill file

The host data handling software in DbosEvent has a disk work area that the
system uses for large sorts on the host.
The IBM Netezza system has two sorting mechanisms:

v The Host Merge that takes sorted SPU return sets and produces a single-sorted
set. It uses temporary disk space to handle SPU double-duty situations.
v A traditional sorter that begins with a random table on the host and sorts it into
the order that you want. It can use a simple external sort method to handle large
data sets.
The file on the Linux host for this disk work area is $NZ_TMP_DIR/nzDbosSpill.
Within DBOS, there is a database that tracks segments of the file presently in use.
To avoid having a runaway query use up all the host computer disk space, there is
a limit on the DbosEvent database, and hence the size of the Linux file. This limit
is in the Netezza Registry file. The tag for the value is
startup.hostSwapSpaceLimit.

System configuration
The behavior of an IBM Netezza system is determined by configuration settings
that are loaded from the configuration file, system.cfg, during system startup and
are stored in the configuration registry. These settings influence such things as
system management, workload management, host processes, and SPUs, and are
used to control and tune the system.
Attention: Never change a configuration setting unless directed to do so

explicitly by either:
v Your IBM Netezza support representative
v A documented Netezza procedure
Incorrect configuration settings can result in significant loss of performance and
other problems.
Related reference:
“The nzsystem command” on page A-65
Use the nzsystem command to change the system state, and show and set
configuration information.
Displaying the software revision level and configuration

registry settings
To display the software revision level and the configuration registry settings, issue
the nzsystem command.
For example:
v To display all system registry settings, enter:
nzsystem showRegistry
The resulting output looks similar to this:

# Netezza NPS configuration registry
# Date: 30-Apr-09 12:48:44 EDT
# Revision: 5.0.D1
#
# Configuration options used during system start
# These options cannot be changed on a running system
#
startup.numSpus = 6
startup.numSpares = 0
startup.simMode = no
startup.autoCreateDb
. = 0
.
.
system.twoPhaseSpu2SpuDist = no
system.autoDumpandgo = yes
v To display only those registry settings that affect the plan history, enter:
nzsystem showRegistry | grep planHist
The resulting output looks similar to this:

host.planHistFiles = 2000
host.planHistKeepArchives = 10
host.planHistArchive = yes

Changing configuration settings
There are some configuration settings that you can change yourself, without
involving your IBM Netezza support representative. These settings are referred to
in documented Netezza procedures elsewhere in this publication or elsewhere in
the Netezza product library.
Attention: Never change a configuration setting unless directed to do so

explicitly by either:
v Your IBM Netezza support representative
v A documented Netezza procedure
Incorrect configuration settings can result in significant loss of performance and
other problems.
There are two ways to change configuration settings:

Temporarily
For you to be able to change a configuration setting temporarily, you must
either be the admin user or your user account must have the Manage
System privilege. To change a configuration setting temporarily, pause the
system, issue the appropriate nzsystem set command, then resume the
system. This is done by issuing the following commands:
nzsystem pause
nzsystem set -arg setting=value
nzsystem resume
A change made in this way remains effective only until the system is
restarted; at system startup, all configuration settings are read from the
system configuration file and loaded into the registry.
Permanently
To change a configuration setting permanently, edit the corresponding line
in the configuration file, system.cfg. Configuration settings are loaded
from this file to the registry during system startup.
The following tables describe the configuration settings that you can change
yourself, without involving your IBM Netezza support representative.
Table 7-6. Configuration settings for short query bias (SQB)
Setting Type Default Description
host.schedSQBEnabled bool true Whether SQB is enabled (true) or disabled (false).
host.schedSQBNominalSecs int 2 The threshold, in seconds, below which a query is to be
regarded as being short.
host.schedSQBReservedGraSlots int 10 The number of GRA scheduler slots that are to be reserved
for short queries.
host.schedSQBReservedSnSlots int 6 The number of snippet scheduler slots that are to be reserved
for short queries.
host.schedSQBReservedSnMb int 50 The amount of memory, in MB, that each SPU is to reserve
for short query execution.
host.schedSQBReservedHostMb int 64 The amount of memory, in MB, that the host is to reserve for
short query execution.

Table 7-7. Configuration settings for the updating virtual tables
host.graVtUpdateInterval int 600 The number of seconds between updates to the
_vt_sched_gra table, which contains resource usage statistics
for completed jobs.
host.snVtUpdateInterval int 60 The number of seconds between updates to the _vt_sched_sn
table, which contains resource usage statistics for completed
snippets.
host.sysVtUpdateInterval int 600 The number of seconds between updates of the
_vt_sched_sys virtual table.
host.sysUtilVtUpdateInterval int 60 The number of seconds between updates of the
_vt_system_util virtual table.
Table 7-8. Configuration settings for plan history

host.planHistArchive bool true The system stores the plan files and C++ source files that it
creates for each snippet. This setting determines where these
files are stored:
true The files are stored in a compressed archive (tar)
file. This option was introduced in Release 7.0.
false The files are stored in plan directories. This was the
only option that was available in Release 6.0.8 and
earlier.
host.planHistFiles int 2000 If host.planHistArchive=true, the maximum number of plans
that can be stored in a single compressed archive file. If
host.planHistArchive=false, the maximum number of plan
directories.
host.planHistKeepArchives int 10 The number of compressed archive files to keep.
Table 7-9. Configuration settings for downtime event logging

sysmgr.numberOfDownPortToRiseEvent int 5 The number of ports on the same switch that must be
down for the amount of time specified by
sysmgr.portDownTime1ToRiseEvent before the
system logs a HW_NEEDS_ATTENTION event.
Specify 0 to deactivate logging
HW_NEEDS_ATTENTION events based on
sysmgr.portDownTime1ToRiseEvent.
sysmgr.portDownTime1ToRiseEvent int 300 The number of seconds that the system waits after
the number of ports specified by
sysmgr.numberOfDownPortToRiseEvent go down
before logging a HW_NEEDS_ATTENTION event.
For example, if
sysmgr.numberOfDownPortToRiseEvent=5 and
sysmgr.portDownTime1ToRiseEvent=300, when at
least 5 ports on the same switch are down for at least
300 seconds the system logs a
HW_NEEDS_ATTENTION event.
Under normal operating conditions, ports sometimes

go down for a few seconds at a time. The delay
introduced by this setting prevents events from being
logged for such transient state changes.

Table 7-9. Configuration settings for downtime event logging (continued)
sysmgr.portDownTime2ToRiseEvent int 600 The number of seconds that any one port must be
down before the system logs a
HW_NEEDS_ATTENTION event for that port. This
happens independently of the settings for
sysmgr.numberOfDownPortToRiseEvent and
sysmgr.portDownTime1ToRiseEvent.
Under normal operating conditions, ports sometimes

go down for a few seconds at a time. The delay
introduced by this setting prevents events from being
logged for such transient state changes.
Table 7-10. Configuration settings for backup

host.bnrNumStreamsDefault int 0 The default number of streams to use for a backup operation
as described in “Multi-stream backup” on page 13-4. A value
of 0 or 1 causes the system to use to one stream per backup
location. The maximum number of streams is 16.
Related reference:

Chapter 8. Event rules
The IBM Netezza event manager monitors the health, status, and activity of the
Netezza system operation and can act when a specific event occurs. Event
monitoring is a proactive way to manage the system without continuous human
observation.
You can configure the event manager to continually watch for specific conditions
such as system state changes, hardware restarts, faults, or failures. In addition, the
event manager can watch for conditions such as reaching a certain percentage of
full disk space, queries that have run for longer than expected, and other Netezza
system behaviors.
This section describes how to administer the Netezza system by using event rules
that you create and manage.
Template event rules

Event management consists of creating rules that define conditions to monitor and
the actions to take when that condition is detected. The event manager uses these
rules to define its monitoring scope, and thus its behavior when a rule is triggered.
Creating event rules can be a complex process because you must define the
condition clearly so that the event manager can detect it, and you must define the
actions to take when the match occurs.
To help ease the process of creating event rules, IBM Netezza supplies template
event rules that you can copy and tailor for your system. The template events
define a set of common conditions to monitor with actions that are based on the
type or effect of the condition. The template event rules are not enabled by default,
and you cannot change or delete the template events. You can copy them as starter
rules for more customized rules in your environment.
As a best practice, you can begin by copying and by using the template rules. If
you are familiar with event management and the operational characteristics of
your Netezza appliance, you can also create your own rules to monitor conditions
that are important to you. You can display the template event rules by using the
nzevent show -template command.
Note: Release 5.0.x introduced new template events for the IBM Netezza 100, IBM
Netezza 1000, and later systems. Previous event template rules specific to the
z-series platform do not apply to the new models and were replaced by similar,
new events.
The following table lists the predefined template event rules.

Table 8-1. Template event rules
Template event rule name Description
Disk80PercentFull Notifies you when a disk is more than 80 percent full.
“Disk space threshold notification” on page 8-22.
Disk90PercentFull Notifies you when a disk is more than 90 percent full.
“Disk space threshold notification” on page 8-22.

Table 8-1. Template event rules (continued)
HardwareNeedsAttention Notifies you when the system detects a condition that
can impact the hardware. For more information, see
“Hardware needs attention” on page 8-20.
HardwareRestarted Notifies you when a hardware component successfully
restarts. For more information, see “Hardware
restarted” on page 8-22.
HardwareServiceRequested Notifies you of the failure of a hardware component,
which most likely requires a service call, hardware
replacement, or both. For more information, see
“Hardware service requested” on page 8-18.
HistCaptureEvent Notifies you if there is a problem that prevents
history-data files from being written to the staging
area.
HistLoadEvent Notifies you if there is a problem that prevents the
external tables that contain history data from being
loaded to the history database.
HwPathDown Notifies you when the status of a disk path changes
from the Up to the Down state (a path has failed). For
more information, see “Hardware path down” on page
8-20.
NPSNoLongerOnline Notifies you when the system goes from the online
state to another state. For more information, see
“System state changes” on page 8-17.
RegenFault Notifies you when the system cannot set up a data slice
regeneration.
RunAwayQuery Notifies you when a query exceeds a timeout limit. For
more information, see “Runaway query notification” on
page 8-24.
SCSIDiskError Notifies you when the System Manager detects that an
active disk has failed, or when an FPGA error occurs.
SCSIPredictiveFailure Notifies you when the SCSI SMART threshold of the
disk is exceeded.
SpuCore Notifies you when the system detects that a SPU
process has restarted and resulted in a core file. For
more information, see “SPU cores event” on page 8-32.
SystemHeatThresholdExceeded When any three boards in an SPA reach the red
temperature threshold, the event runs a command to
shut down the SPAs, SFIs, and RPCs. For more
information, see “System temperature event” on page
8-29. Enabled by default for z-series systems only.
SystemOnline Notifies you when the system is online. For more
information, see “System state changes” on page 8-17.
SystemStuckInState Notifies you when the system is stuck in the Pausing
Now state for more than the timeout specified by the
sysmgr.pausingStateTimeout (420 seconds). For more
information, see “System state changes” on page 8-17.
ThermalFault Notifies you when the temperature of a hardware
component exceeds its operating thresholds. For more
information, see “Hardware temperature event” on
page 8-28.

Table 8-1. Template event rules (continued)
TopologyImbalance Notifies you when the system detects a disk topology
imbalance after a disk regeneration or when the system
transitions to the online state after a rebalance. For
more information, see “Topology imbalance event” on
page 8-35.
Transaction Limit Event Sends an email notification when the number of
outstanding transaction objects exceeds 90 percent of
the available objects. For more information, see
“Transaction limits event” on page 8-33.
VoltageFault Notifies you when the voltage of a hardware
component exceeds its operating thresholds. For more
information, see “Voltage faults event” on page 8-33.
Netezza might add new event types to monitor conditions on the system. These
event types might not be available as templates, which means you must manually
add a rule to enable them. For a description of more event types that can assist
you with monitoring and managing the system, see “Event types reference” on
page 8-36.
The action to take for an event often depends on the type of event (its effect on the
system operations or performance). The following table lists some of the
predefined template events and their corresponding effects and actions.
Table 8-2. Netezza template event rules
Template name Type Notify Severity Effect Action
Disk80PercentFull hwDiskFull Admins, Moderate Full disk Reclaim space or remove
(Notice) DBAs to Serious prevents some unwanted databases or older
Disk90PercentFull operations. data. For more information, see
“Disk space threshold
notification” on page 8-22.
HardwareNeeds hwNeeds Admins, Moderate Possible Investigate and identify whether
Attention Attention NPS change or issue more assistance is required from
that can start Support. For more information,
to affect see “Hardware needs attention”
performance. on page 8-20.
Hardware hwRestarted Admins, Moderate Any query or Investigate whether the cause is
Restarted (Notice) NPS data load in hardware or software. Check for
progress is lost. SPU cores. For more information,
see “Hardware restarted” on
page 8-22.
HardwareService hwService Admins, Moderate Any query or Contact Netezza. For more
Requested Requested NPS to Serious work in information, see “Hardware
(Warning) progress is lost. service requested” on page 8-18.
Disk failures
initiate a
regeneration.
Chapter 8. Event rules 8-3

Table 8-2. Netezza template event rules (continued)
HistCapture histCapture Admins, Moderate The The size of the staging area
Event Event NPS to Serious history-data reaches the configured size
collection threshold, or there is no available
process disk space in /nz/data. Either
(alcapp) is increase the size of the threshold
unable to save or free up disk space by deleting
captured old files.
history data in
the staging
area; alcapp
stops collecting
new data.
HistLoadEvent histLoadEvent Admins, Moderate The The history configuration might
NPS to Serious history-data be changed, the history database
loader process might be deleted, or there might
(alcloader) is be some session connection error.
unable to load
history data
into the history
database; new
history data is
not available in
reports until it
can be loaded.
HwPathDown hwPathDown Admins Serious to Query Contact Netezza Support. For
Critical performance more information, see
and possible “Hardware path down” on page
system 8-20.
downtime.
NPSNoLongerOnline sysState Admins, Varies Availability Depends on the current state. For
Changed NPS, status. more information, see “System
SystemOnline (Information) DBAs state changes” on page 8-17.
RegenFault regenFault Admins, Critical Might prevent Contact Netezza Support. For
NPS user data from more information, see
being “Regeneration errors” on page
regenerated. 8-26.
RunAwayQuery runaway Admins, Moderate Can consume Determine whether to allow you
Query DBAs resources that to run, manage workload. For
(Notice) are needed for more information, see “Runaway
operations. query notification” on page 8-24.
SCSIDiskError scsiDiskError Admins, Serious Adversely Schedule disk replacement as
NPS affects system soon as possible. See “Disk
performance. errors event” on page 8-27.
SCSIPredictiveFailure scsiPredictive Admins, Critical Adversely Schedule disk replacement as
Failure NPS affects soon as possible. See “Disk
performance. predictive failure errors event”
on page 8-25.
SpuCore spuCore Admins, Moderate A SPU core file The system created a SPU core
NPS was created. file. See “SPU cores event” on
page 8-32.

Table 8-2. Netezza template event rules (continued)
SystemHeatThreshold sysHeatThres Admins, Critical System Before you power on the system,
Exceeded hold NPS shutdown. check the SPA that caused this
event to occur. For more
information, see “System
temperature event” on page 8-29.
SystemStuckInState systemStuck Admins, Moderate A system is Contact Netezza Support. See
InState NPS stuck in the “System state” on page 8-25.
(Information) Pausing Now
state.
ThermalFault hwThermal Admins, Serious Can drastically Contact Netezza Support. For
Fault NPS reduce disk life more information, see
expectancy if “Hardware temperature event”
ignored. on page 8-28.
TopologyImbalance topology Admins, Serious Can impact Contact Netezza Support. For
Imbalance NPS query more information, see “Topology
performance imbalance event” on page 8-35.
until the
imbalance is
resolved.
TrasactionLimit transaction Admins, Serious New Stop some existing sessions that
Event LimitEvent NPS transactions are might be old and require
blocked if the cleanup, or stop/start the
limit is Netezza server to close all
reached. existing transactions.
VoltageFault hwVoltage Admins, Serious Might indicate For more information, see
Fault NPS power supply “Voltage faults event” on page
issues. 8-33.
Event rule management

To start using events, you must create and enable some event rules. You can use
any of the following methods to create and activate event rules:
v Copy and enable a template event rule
v Add an event rule
You can copy, modify, and add events by using the nzevent command or the
NzAdmin interface. You can also generate events to test the conditions and event
notifications that you are configuring. The following sections describe how to
manage events by using the nzevent command. The NzAdmin interface has an
intuitive interface for managing events, including a wizard tool for creating events.
For information about accessing the NzAdmin interface, see “NzAdmin overview”
on page 3-12.
Copy a template event to create an event rule

You can use the nzevent copy command to copy a predefined template for
activation.
The following example copies a template event named NPSNoLongerOnline to

create a user-defined rule of the same name, adds a sample email address for
contact, and activates the rule:

nzevent copy -u admin -pw password -useTemplate -name
NPSNoLongerOnline -newName NPSNoLongerOnline -on yes -dst
jdoe@company.com
When you copy a template event rule, which is disabled by default, your new rule
is likewise disabled by default. You must enable it by using the -on yes argument.
In addition, if the template rule sends email notifications, you must specify a
destination email address.
Copy and modify a user-defined event rule

You can copy, modify, and rename an existing user-defined rule by using the
nzevent copy command.
The following example copies, renames, and modifies an existing event rule:
nzevent copy -u admin -pw password -name NPSNoLongerOnline -newName
MyModNPSNoLongerOnline -on yes -dst jdoe@company.com -ccDst
tsmith@company.com -callhome yes
When you copy an existing user-defined event rule, your new rule is enabled
automatically if the existing rule is enabled. If the existing rule is disabled, your
new rule is disabled by default. You must enable it by using the -on yes argument.
You must specify a unique name for your new rule; it cannot match the name of
the existing user-defined rule.
Generate an event
You can use the nzevent generate command to trigger an event for the event
manager. If the event matches a current event rule, the system takes the action that
is defined by the event rule.
You might generate events for the following cases:

v To simulate a system event to test an event rule.
v To add new events because the system is not generating events for conditions
for which you would like notification.
If the event that you want to generate has a restriction, specify the arguments that
would trigger the restriction by using the -eventArgs option. For example, if a
runaway query event has a restriction that the duration of the query must be
greater than 30 seconds, use a command similar to the following to ensure that a
generated event is triggered:
nzevent generate -eventtype runawayquery -eventArgs ’duration=50’
In this example, the duration meets the event criteria (greater than 30) and the
event is triggered. If you do not specify a value for a restriction argument in the
-eventArgs string, the command uses default values for the arguments. In this
example, duration has a default of 0, so the event would not be triggered since it
did not meet the event criteria.
To generate an event for a system state change:

nzevent generate -eventType sysStateChanged
-eventArgs ’previousState=online, currentState=paused’
Delete an event rule

You can delete event rules that you create. You cannot delete the template events.

To delete an event rule, enter: nzevent delete -u admin -pw password -name
<rule_name>.
Disable an event rule

To disable an event rule, enter: nzevent modify -u admin -pw password -name
<rule_name> -on no.
Add an event rule

You can use the nzevent add command to add an event rule. You can also use the
NzAdmin tool to add event rules by using a wizard for creating events.
Adding an event rule consists of two tasks: specifying the event match criteria and
specifying the notification method. These tasks are described in more detail after
the examples.
Note: Although the z-series events are not templates on IBM Netezza 1000 or
N1001 systems, you can add them by using nzevent if you have the syntax that is
documented in the previous releases. However, these events are not supported on
IBM Netezza 1000 or later systems.
To add an event rule that sends an email when the system transitions from the
online state to any other state, enter:
nzevent add -name TheSystemGoingOnline -u admin -pw password
-on yes -eventType sysStateChanged -eventArgsExpr ’$previousState
== online && $currentState != online’ -notifyType email -dst
jdoe@company.com -msg ’NPS system $HOST went from $previousState to
$currentState at $eventTimestamp.’ -bodyText
’$notifyMsg\n\nEvent:\n$eventDetail\nEvent
Rule:\n$eventRuleDetail’
Note: If you are creating event rules on a Windows client system, use double
quotation marks instead of single quotation marks to specify strings.
Related concepts:
“Callhome file” on page 5-19
Event match criteria

The IBM Netezza event manager uses the match criterion portion of the event rule
to determine which events generate a notification and which ones the system
merely logs. A match occurs if the event type is the same and the optional event
args expression evaluates to true. If you do not specify an expression, the event
manager uses only the event type to determine a match.
The event manager generates notifications for all rules that match the criteria, not
just for the first event rule that matches. The following table lists the event types
that you can specify and the arguments and the values that are passed with the
event. You can list the defined event types by using the nzevent listEventTypes
command. Used only on z-series systems such as the 10000-series, 8000z-series, and
5200-series systems.
Table 8-3. Event types
Event type Tag name Possible values
sysStateChanged previousState, currentState, <any system state>, <Event
eventSource Source>

Table 8-3. Event types (continued)
hwFailed Used only on z-series systems such as the 10000-series,
8000z-series, and 5200-series systems.
hwRestarted hwType, hwId, spaId, v spu, <SPU HW ID>, <SPA
spaSlot, devSerial, ID>, <SPA Slot>,
devHwRev, devFwRev <SPU/SFI Serial>,
<Hardware Revision>,
<Firmware Revision>
v sfi, <SFI HW ID>, <SPA
ID>, <SPA Slot>,
<SPU/SFI Serial>,
<Hardware Revision>,
<Firmware Revision>
v fan, <FAN HW ID>, <SPA
ID>, <SPA Slot>
v pwr, <POWER SUPPLY
HW ID>, <SPA ID>, <SPA
Slot>
hwDiskFull hwType, hwId, spaId, spu, <SPU HW ID>, <Spa
spaSlot, diskHwId, location, Id>,<SPA Slot>, <Disk HW
partition, threshold, value ID>, <Location String>
<partition #>, <threshold>,

<value>
For more information, see “Disk space threshold
notification” on page 8-22
runawayQuery sessionId, planId, duration <Session Id>, <Plan Id>,
<seconds>
For more information, see “Runaway query notification” on
page 8-24.
custom1 or custom2 User-specified rule. Use with the nzevent generate
command.
For more information, see “Creating a custom event rule”
on page 8-16.
smartThreshold Used only on z-series systems such as the 10000-series,
regenError Used only on z-series systems such as the 10000-series,
diskError Used only on z-series systems such as the 10000-series,
hwHeatThreshold Used only on z-series systems such as the 10000-series,
sysHeatThreshold errType, errCode, errString <Err Type>, <Err Code>,
<Err String
For more information, see “System temperature event” on
page 8-29.
fwMismatch

systemStuckInState duration, currentState, <seconds>, <any system
expectedState state>, <any system state>
For more information, see “System state changes” on page
8-17.
histCaptureEvent configName, histType, <Config Name>,
storageLimit, <query/audit>, <Storage
loadMinThreshold, Limit>, <Min Threshold>,
loadMaxThreshold, <Max Threshold>, <Disk Full
diskFullThreshold, Threshold>, <Load Interval>,
loadInterval, nps, database, <Target NPS>, <Target DB
capturedSize, stagedSize, Name>, <Captured Size
storageSize, dirName, MB>, <Staged Size MB>,
errCode, errString <Storage(total) Size MB>,
<Dir Name>, <Err Code>,
<Err String>
histLoadEvent configName, histType, <Config Name>,
storageLimit, <query/audit>, <Storage
loadMinThreshold, Limit>, <Min Threshold>,
loadMaxThreshold, <Max Threshold>, <Disk Full
diskFullThreshold, Threshold>, <Load Interval>,
loadInterval, nps, database, <Target NPS>, <Target DB
batchSize, stagedSize, Name>, <Batch Size MB>,
dirName, errCode, errString <Staged Size MB>, <Dir
Name>, <Err Code>, <Err
String>
hwVoltageFault hwType, hwId, label, v SPU, <SPU HW ID>,
location, curVolt, errString, <Label String>, <Location
eventSource String>, <Current
Voltage>, <Err String>,
<Event Source>
v Disk Enclosure, <Encl HW
ID>, <Label String>,
<Location String>,
<Current Voltage>, <Err
String>, <Event Source>
spuCore hwId, location, errString, <HW ID>, <Location
eventSource String>, <Err String>, <Event
Source>
regenFault hwIdSpu, hwIdSrc, <SPU HW ID>, <Source Disk
locationSrc, hwIdTgt, HW ID>, <Source Disk
locationTgt, errString, Location>, <Target Disk HW
devSerial, eventSource ID>, <Target Disk
Location>,<Error String>,
<SPU Serial>, <Event
Source>

hwServiceRequested hwType, hwId, location, v spu, <SPU HW ID>,
errString, devSerial, <Location String>, <Error
eventSource String>, <SPU Serial>,
<Event Source>
v disk, <Disk HW ID>,
<Location String>, <Error
String>, <Disk Serial>,
<Event Source>
v disk enclosure power
supply, <PS HW ID>,
String>, <Unknown>,
<Event Source>
v disk enclosure fan, <Fan
HW ID>, <Location
String>, <Error String>,
<Unknown>, <Event
Source>
v AMM, <AMM HW ID>,
String>, <Unknown>,
<Event Source>
v chassis power supply, <PS
HW ID>, <Location
String>, <Error String>,
<Unknown>,<Event
Source>
v chassis fan, <FAN HW
ID>, <Location String>,
<Error String>,
<Unknown>, <Event
Source>
scsiDiskError spuHwId, diskHwId, <SPU HW ID>, <Location
location, errType, errCode, String>, <Err Type>, <Err
oper, dataPartition, lba, Code>, <Oper>, <Data
tableId, dataSliceId, Partition>, <LBA>, <Table>,
devSerial, fpgaBoardSerial, <DataSlice>, <Block>, <SPU
diskSerial, diskModel, Serial>, <FPGA Board
diskMfg, eventSource Serial>, <Disk Serial>, <Disk
Model>, <Disk
Manufacturer>, <Event
Source>
scsiPredictiveFailure spuHwId, diskHwId, <SPU HW ID>, <Disk HW
scsiAsc, scsiAscq, fru, ID>, <SCSI ASC>, <SCSI
location, devSerial, ASCQ>,<Fru>, <Location
diskSerial, diskModel, String>, <SPU Serial>, <Disk
diskMfg, eventSource Serial>, <Disk Model>, <Disk
Manufacturer>, <Event
Source>

hwThermalFault hwType, hwId, label, spu, <SPU HW ID>, <Label
location, devSerial, errString, String>, <Location String>,
curVal, eventSource <SPU Serial>, <Error String>,
<Current Value>, <Event
Source>
Disk Enclosure, <Encl HW

ID>, <Label String>,
String>, <Current Value>,
<Event Source>
For more information, see “Hardware temperature event”
on page 8-28.
transactionLimitEvent CurNumTX <Current Number of
Transactions>
nwIfChanged hwType, hwId, location, <HW TYPE>, <HW ID>,
interfaceName, prevState, <Location String>, <interface
currState name>, <previous state>,
<current state>
numCpuCoreChanged hwId, location, <SPU HW ID>, <Location
initialNumCore, String>, <Number of CPU
lastNumCore, curNumCore cores of SPU on
initialization>, <Last Number
of Online CPU cores of
SPU>, <Current Number of
Online CPU Cores of SPU>
hwNeedsAttention hwType, hwId, location, spu, <SPU HW ID>,
<Event Source>
hwPathDown hwType, hwId, location, spu, <SPU HW ID>,
<Event Source>
topologyImbalance errString <Error String>
Event rule attributes

An event consists of three attributes: an event type, a timestamp, and a list of
event-specific arguments that are represented as a list of tag=value pairs. By using
text substitution in the form of $tag, you can create an expression to match a
specific event instance rather than all events of a specific type.
For example, to receive an email when the system is not online, it is not enough to
create an event rule for a sysStateChanged event. Because the sysStateChange
event recognizes every state transition, you can be notified whenever the state
changes at all, such as from online to paused.
You can add an event args expression to further qualify the event for notification.
If you specify an expression, the system substitutes the event arguments into the
expression before evaluating it. The system uses the result combined with the
event type to determine a match. So, to send an email message when the system is
no longer online, you would use the expression: $previousState == online &&

$currentState!=online. The system gets the value of previousState and
currentState from the actual argument values of a sysStateChanged event.
You can specify an event by using equality expressions, wildcard expressions,

compound AND expressions, or OR expressions. The following table describes
these expressions.
Table 8-4. Event argument expression syntax
Expression Syntax Example
EqualityExpr <string> == <string> ‘$hwType == spu’
<string> != <string> ‘$hwType != spu’

WildcardExpr <string> ~ <string> '$errString ~ *spu*'
<string> !~ <string> '$errString !~ *ascq*'

AndExpr EqualityExpr ‘&&’ EqualityExpr '$previousState == online &&
$currentState != online’
OrExpr EqualityExpr ‘||’ EqualityExpr '$threshold == 80 || $threshold
== 85’
Event notifications
When an event occurs, you can have the system send an email or run an external
command. Email can be aggregated whereas commands cannot.
v To specify an email, you must specify a notification type (-notifyType email), a
destination (-dst), a message (-msg), and optionally, a body text (-bodyText), and
the callhome file (-callHome).
You can specify multiple email addresses that are separated by a comma and no
space. For example,
jdoe@company.com,jsmith@company.com,sbrown@company.com
v To specify that you want to run a command, you must specify a notification
type (-notifyType runCmd), a destination (-dst), a message (-msg), and
optionally, a body text (-bodyText), and the callhome file (-callHome).
When you are defining notification fields that are strings (-dst, -ccDst, -msg,
-bodyText), you can use $tag syntax to substitute known system or event values.
Table 8-5 on page 8-13 lists the system-defined tags that are available.
Related concepts:
“Event email aggregation” on page 8-14
The sendMail.cfg file

If you send email, you must modify the sendMail.cfg file. It contains the name of
the mail server and its port, the sender name and address, and a CC field for a list
of email names that are automatically appended to the ccDst field defined in the
event rule.
The sendmail.cfg file also contains options that you can use to specify a user
name and password for authentication on the mail server. You can find a copy of
this file in the /nz/data/config directory on the IBM Netezza host.

Table 8-5. Notification substitution tags
Source Tag Description
Event eventType One of the event types (for example,
sysStateChanged).
eventTimestamp The data and time the event occurred (for
example 17-Jun-02, 14:35:33 EDT).
eventArgs The event arguments (for example, hwType = spu,
hwId =1002).
eventDetail Shorthand for the eventType, eventArgs, and
eventTimestamp.
Event rule eventType One of the event types (for example, hwDiskFull).
eventArgsExpr The event argument match expression (for
example, hwType == spu).
notifyType The type of notification, email, or runCmd.
notifyDst The notification destination (from -dst) (for
example, jdoe@company.com).
notifyCcDst The cc notification destination (from -ccDst) (for
example, jsmith@company.com).
notifyMsg The notification message (from -msg).
notifyCallHome A boolean that indicates whether callhome was
requested (from -callHome).
notifyCallHomeFile The callhome file name.
eventRuleDetail Shorthand for tags eventArgsExpr through
notifyCallHomeFile.
eventAggrCount The aggregate count of events for notification
(email only)
Environment NZ_HOST The host environment variable.
NZ_DIR The nz directory.
NZ_BIN_DIR The nz bin directory.
NZ_DATA_DIR The nz data directory.
NZ_KIT_DIR The nz kit directory.
NZ_LOG_DIR The nz log directory.
NZ_SBIN_DIR The nz sbin directory.
NZ_SYS_DIR The nz system directory.
NZ_TMP_DIR The nz temp directory.
If you specify the email or runCmd arguments, you must enter the destination and
the subject header. You can use all the following arguments with either command,
except the -ccDst argument, which you cannot use with the runCmd. The
following table lists the syntax of the message.
Table 8-6. Notification syntax
Argument Description Example
-dst Your email address -dst 'jdoe@company.com,bsmith@company.com'
You can specify multiple recipients.

Table 8-6. Notification syntax (continued)
Argument Description Example
-msg The subject field of the -msg ‘NPS system $HOST went from
email $previousState to $currentState at
$eventTimestamp.’
This message substitutes the host name for

$HOST, the previous system state for
$previousState, the current system state for
$currentState, and the date and time the event
occurred for $eventTimeStamp.
-bodyText Optional body of the email -bodyText '$notifyMsg\n\nEvent:\
n$eventDetail\nEvent Rule:\
n$eventRuleDetail'
This message substitutes the text in the -msg

argument for the $notifyMsg, outputs a
newline and the word ‘Event’ then the
contents of the eventType through eventArgs,
newline, and the word ‘Event Rule’ and then
the contents of eventArgsExpr through
notifyCallHomeFile.
-ccDst Optional cc specification -ccDst
'rdoe@company.com,tsmith@company.com'
You can specify multiple recipients.

-callHome Optional file -callHome yes
Event email aggregation

Some events, such as notification of power recycling, host-to-switch network
connectivity failures, and other events, can generate many email messages. To
avoid filling your inbox with email, you can aggregate your event rule notifications
by defining a system-wide aggregation time interval and a per-event-rule
notification count.
If you set email aggregation and events-per-rule reach the threshold value for the
event rule or the time interval expires, the system aggregates the events and sends
a single email per event rule.
Note: You specify aggregation only for event rules that send email, not for event
rules that run commands.
Related concepts:
“Event notifications” on page 8-12
Related reference:
“Hardware restarted” on page 8-22
If you enable the event rule HardwareRestarted, you receive notifications when
each SPU successfully restarts (after the initial startup). Restarts are usually related
to a software fault, whereas hardware causes can include uncorrectable memory
faults or a failed disk driver interaction.
“Disk space threshold notification” on page 8-22

Setting the system-wide aggregation time interval
About this task
You can enable event aggregation system-wide and specify the time interval. You
can specify 0 - 86400 seconds. If you specify 0 seconds, there is no aggregation,
even if aggregation is specified on individual events.
To set system-wide aggregation, complete the following steps:
Procedure
1. Pause the system using the command nzsystem pause -u bob -pw 1234 -host
nzhost
2. Specify aggregation of 2 minutes (120 seconds), enter nzsystem set -arg
sysmgr.maxAggregateEventInterval=120
3. Resume the system, enter nzsystem resume -u bob -pw 1234 -host nzhost
4. Display the aggregation setting, enter nzsystem showRegistry | grep
maxAggregateEventInterval
Specify event rule email aggregation

When you add or enable (modify) an event that specifies email notification, you
can enable event aggregation by specifying the aggregation count.
To aggregate email messages for the event rule NPSNoLongerOnline, enter:

nzevent modify -u admin -pw password -name NPSNoLongerOnline -on
yes -dst jdoe@company.com -eventAggrCount 1
You can specify any aggregation count 1 - 1000.

v If you issue the nzstop command, the system sends no in-memory aggregations,
instead it updates the event log. In such cases, check the event log, especially if
the aggregation interval is 15 minutes or longer.
v If you modify or delete an event rule, the system flushes all events that are
aggregated for the event rule.
Disable individual event rule email aggregation

If event rule aggregation is enabled system wide, you can disable event rule
aggregation for individual event rules by setting the count to 0.
To disable email messages for the event rule NPSNoLongerOnline, enter:

nzevent modify -u admin -pw password -name NPSNoLongerOnline -on
yes -dst jdoe@company.com -eventAggrCount 1
Sample aggregated email messages

The aggregated email describes the number of messages that are aggregated and
the time interval for the event rule.
The body of the message lists the messages by time, with the earliest events first.
The Reporting Interval indicates whether the notification trigger was the count or
time interval. The Activity Duration indicates the time interval between the first
and last event so that you can determine the granularity of the events.
For example, the following aggregation is for the Memory ECC event:
Subject: NPS nzdev1 : 2 occurrences of Memory ECC Error from 11-Jun-07
18:41:59 PDT over 2 minutes.
Date: Sun, 11 Jun 2007 18:44:05 PDT

From: NPS Event Manager <eventsender@netezza.com>
Reply-To: NPS Event Manager <eventsender@netezza.com>
To: Jane Doe

Message Header
Host : nzdev1.
Event : Memory ECC Error.
Event Rule Detail .
Start : 06-11-07 18:41:59.
Reporting Interval : 2 minutes.
Activity Duration : 00:00:05.
Number of events : 2.
Message Details
1 hwType=spu, hwId=1002, spaId=1, spaSlot=4, errType=2,
errCode=12,devSerial=040908061230, devHwRev=5.20814r1.20806r1,
devFwRev=3.0B1 BLD[4428], eventSource=System initiated, Memory ECC
Error on 06-11-07 18:42:05 PDT
2 hwType=spu, hwId=1002, spaId=1, spaSlot=4, errType=2, errCode=12,
devSerial=040908061230, devHwRev=5.20814r1.20806r1, devFwRev=3.0B1
BLD[4428], eventSource=System initiated, Memory ECC Error on 06-11-07
18:42:10 PDT
Creating a custom event rule

About this task
You can use the Custom1 and Custom2 event rules to define and generate events
of your own design for conditions that are not already defined as events by the
NPS software. An example of a custom event might be to track the user login
information, but these events can also be used to construct complex events.
If you define a custom event, you must also define a process to trigger the event
using the nzevent generate command. Typically, these events are generated by a
customer-created script which is invoked in response to either existing NPS events
or other conditions that you want to monitor.
To create a custom event rule, complete the following steps:
Procedure
1. Use the nzevent add command to define a new event type. Custom events are
never based on any existing event types. This example creates three different
custom events. nNewRule4 and NewRule5 use the variable eventType to
distinguish between the event types. The NewRule6 event type uses a custom
variable and compares it with the standard event type.
[nz@nzhost ~]$ nzevent add -eventType custom1 -name NewRule4
-notifyType email -dst myemail@company.com -msg "NewRule4 message"
-eventArgsExpr ’$eventType==RandomCustomEvent’

-eventArgsExpr ’$eventType==sysStateChanged’

-eventArgsExpr ’$randomEventType==sysStateChanged’
2. Use the nzevent generate command to trigger the custom events.
[nz@nzhost ~]$ nzevent generate -eventtype custom1
-eventArgs ’eventType=RandomCustomEvent’
-eventArgs ’eventType=sysStateChanged’
-eventArgs ’randomEventType=sysStateChanged’

3. After generating these custom events, email is sent to the specified destination
and the following messages are logged in the /nz/kit/log/eventmgr/
eventmgr.log file:
2015-11-24 09:43:31.820612 EST (16210) Info: received & processing event
type =custom1, event args = ’eventType=RandomCustomEvent’ event source =
’User initiated event’
2015-11-24 09:43:31.820724 EST (16210) Info: invoking mail notifier,
cmd = ’/nz/kit.7.2.1.0.45837/sbin/sendMail -dst "myemail@company.com"
-msg "NewRule4 message"’
type =custom1, event args = ’eventType=sysStateChanged’ event source =
’User initiated event’
type =custom1, event args = ’randomEventType=sysStateChanged’ event
source = ’User initiated event’
What to do next
Consider creating a script that runs the nzevent generate command as needed
when your custom events occur.
Template event reference

The following sections describe the predefined template event rules in more detail.
System state changes

The NPSNoLongerOnline and SystemOnline rules enable the system to notify you
when the system state changes, or when a state change exceeds a specified
timeout.
These events occur when the system is running. The typical states are
v Online
v Pausing Now
v Going Pre-Online
v Resuming
v Going OffLine Now
v Offline (now)
v Initializing
v Stopped
The Failing Back and Synchronizing states apply only to z-series systems.
The following is the syntax for the template event rule NPSNoLongerOnline:
-name NPSNoLongerOnline -on no -eventType sysStateChanged
-eventArgsExpr ’$previousState == online && $currentState != online’
-notifyType email -dst ’you@company.com’ -ccDst ’’ -msg ’NPS system
$HOST went from $previousState to $currentState at $eventTimestamp
$eventSource.’ -bodyText ’$notifyMsg\n\nEvent:\n$eventDetail\n’
-callHome yes -eventAggrCount 1
The following is the syntax for event rule SystemOnline:

-name SystemOnline -on no -eventType sysStateChanged -eventArgsExpr
’$previousState != online && $currentState == online’ -notifyType
email -dst ’you@company.com’ -ccDst ’’ -msg ’NPS system $HOST went
online at $eventTimestamp $eventSource.’ -bodyText
’$notifyMsg\n\nEvent:\n$eventDetail\n’ -callHome yes -eventAggrCount
50
The valid values for the previousState and currentState arguments are:
initializing pausedNow syncingNow
initialized preOnline syncedNow
offlining preOnlining failingBack
offliningNow resuming failedBack
offline restrictedResuming maintaining
offlineNow stopping maintain
online stoppingNow recovering
restrictedOnline stopped recovered
pausing stoppedNow down
pausingNow syncing unreachable
paused synced badState
For more information about states, see Table 5-4 on page 5-10.
The following table describes the state changes.

Table 8-7. System state changes
Previous state Current state Severity Notify Impact Action
Online Not Online Varies Admins, NPS, System no longer Determine
DBAs processing queries cause
Not Online Online n/a Admins, NPS, Normal None
DBAs
Not Synchronizing Synchronizing n/a Admins, NPS Query processing is None
suspended until
complete
Synchronizing Not Synchronizing n/a Admins, NPS Query processing is Contact IBM
resumed when Online Netezza
Hardware service requested

It is important to be notified when a hardware component fails so that Support can
notify service technicians that can replace or repair the component. For devices
such as disks, a hardware failure causes the system to bring a spare disk online,
and after an activation period, the spare disk transparently replaces the failed disk.
However, it is important to replace the failed disk with a healthy disk so that you
restore the system to its normal operation with its complement of spares.
In other cases, such as SPU failures, the system reroutes the work of the failed SPU
to the other available SPUs. The system performance is affected because the
healthy resources take on extra workload. Again, it is critical to obtain service to
replace the faulty component and restore the system to its normal performance.
If you enable the event rule HardwareServiceRequested, the system generates a

notification when there is a hardware failure and service technicians might be
required to replace or repair components.
The following is the syntax for the event rule HardwareServiceRequested:

-name ’HardwareServiceRequested’ -on no -eventType hwServiceRequested
-eventArgsExpr ’’ -notifyType email -dst ’you@company.com’ -ccDst ’’
-msg ’NPS system $HOST - Service requested for $hwType $hwId at
$eventTimestamp $eventSource.’ -bodyText
’$notifyMsg\n\nlocation:$location\nerror
string:$errString\ndevSerial:$devSerial\nevent source:$eventSource\n’
The following table lists the arguments to the HardwareServiceRequested event

rule.
Table 8-8. HardwareServiceRequested event rule
Arguments Description Example
hwType The type of hardware affected spu, disk, pwr, fan, mm
hwId The hardware ID of the component 1013
that reports a problem
location A string that describes the physical
location of the component
errString Specifies more information about the
error or condition that triggered the
event. If the failed component is not
inventoried, it is specified in this
string.
devSerial Specifies the serial number of the 601S496A2012
component, or Unknown if the
component has no serial number.
Restriction: Do not aggregate this event.
For source disks used in a disk regeneration to a spare disk, the

HardwareServiceRequested event also notifies you when regeneration encounters a
read sector error on the source disk. The event helps you to identify when a
regeneration requires some attention to address possible issues on the source and
newly created mirror disks. The error messages in the event notification and in the
sysmgr.log and eventmgr.log files contain information about the bad sector, as in
the following example:
2012-04-05 19:52:41.637742 EDT Info: received & processing event type
= hwServiceRequested, event args = ’hwType=disk, hwId=1073,
location=Logical Name:’spa1.diskEncl2.disk1’ Logical Location:’1st
rack, 2nd disk enclosure, disk in Row 1/Column 1’, errString=disk md:
md2 sector: 2051 partition type: DATA table: 201328,
devSerial=9QJ2FMKN00009838VVR9...
The errString value contains more information about the sector that had a read
error:
v The md value specifies the RAID device on the SPU that encountered the issue.
v The sector value specifies which sector in the device has the read error.
v The partition type specifies whether the partition is a user data (DATA) or
SYSTEM partition.
v The table value specifies the table ID of the user table that is affected by the bad
sector.
If the system notifies you of a read sector error, contact IBM Netezza Support for
assistance with troubleshooting and resolving the problems.

Hardware needs attention
The system monitors the overall health and status of the hardware and can notify
you when changes occur that can affect the system availability or performance.
These changes can include replacement disks with invalid firmware, storage
configuration changes, unavailable/unreachable components, disks that reach a
grown defects early warning threshold, ethernet switch ports that are down, and
other conditions that can be early warnings of problems that can affect system
behavior or the ability to manage devices within the system.
If you enable the HwNeedsAttention event rule, the system generates a notification
when it detects conditions that can lead to problems or that serve as symptoms of
possible hardware failure or performance impacts.
The following is the syntax for the HwNeedsAttention event rule:

-name ’HardwareNeedsAttention’ -on no -eventType hwNeedsAttention
-msg ’NPS system $HOST - $hwType $hwId Needs attention. $eventSource.’
-bodyText ’$notifyMsg\n\nlocation:$location\nerror
The following table lists the arguments to the HardwareNeedsAttention event rule.
Table 8-9. HardwareNeedsAttention event rule
hwType The type of hardware affected spu
hwId The hardware ID of the component 1013
that has a condition to investigate
location A string that describes the physical
location of the component
errString If the failed component is not
inventoried, it is specified in this
string.
devSerial Specifies the serial number of the 601S496A2012
component, or Unknown if the
component has no serial number.
Hardware path down

If the path between an S-Blade/SPU and its disks fails, and you enable the
HwPathDown event rule, the system generates a notification when it detects that a
storage path has transitioned from the Up to the Down state. Failed paths
adversely affect system and query performance.
The following is the syntax for the HwPathDown event rule:

-name ’HwPathDown’ -on no -eventType hwPathDown -eventArgsExpr ’’
-notifyType email -dst ’you@company.com’ -ccDst ’’
-msg ’NPS system $HOST - $hwType $hwId - Hardware Path Down.
$eventSource.’ -bodyText ’$notifyMsg\n\nlocation:$location\nerror

Note: The aggregation count of 1000 is large because some kinds of storage
failures can cause hundreds of path failures on large, multi-rack systems. The
aggregation count reduces the number of email notifications for those cases. All
path failures in the last 2 minutes are grouped into a single notification email.
The following table lists the arguments to the HardwarePathDown event rule.
Table 8-10. HardwarePathDown event rule
hwType For a path down event, the SPU that SPU
reported the problem
hwId The hardware ID of the SPU that 1013
loses path connections to disks
location A string that describes the physical First Rack, First SPA, SPU in third
location of the SPU slot
errString If the failed component is not Disk path event:Spu[1st Rack, 1st
inventoried, it is specified in this SPA, SPU in 5th slot] to Disk [disk
string. hwid=1034
sn="9WK4WX9D00009150ECWM"
SPA=1 Parent=1014 Position=12
Address=0x8e92728
ParentEnclPosition=1 Spu=1013]
(es=encl1Slot12 dev=sdl major=8
minor=176 status=DOWN)
If you are notified of hardware path down events, contact IBM Netezza Support
and alert them to the path failure or failures. It is important to identify and resolve
the issues that are causing path failures to return the system to optimal
performance as soon as possible.
A sample email follows:

Event:
Message Header
Host:nzhost.
Event:Hardware Path Down.
Event Rule Detail:.
Start: 11-08-11 11:10:41 EST.
Reporting Interval: 2 minutes.
Activity Duration:00:00:01.
Number of events:12.
Message Details
1 hwType=SPU, hwId=1017, location=1st Rack, 1st SPA, SPU in 9th slot,

devSerial=Y011UF0CJ23G, eventSource=system, errString=Disk path
event:Spu\[1st Rack, 1st SPA, SPU in 9th slot\] to
Disk\[sn=9QJ60E9M000090170SXW hwid=1027 eshp=NA es=encl4Slot01 dev=sda
Major=8 Minor=0 status=DOWN]
If you receive a path down event, you can obtain more information about the
problems. This information might be helpful when you contact Netezza Support.
To see whether there are current topology issues, use the nzds show -topology
command. The command displays the current topology, and if there are issues, a
WARNING section at the end of the output.
Related concepts:
“System resource balance recovery” on page 5-17

“Active path topology” on page 5-29
Related reference:
“Start the system” on page 7-6
Hardware restarted
If you enable the event rule HardwareRestarted, you receive notifications when
each SPU successfully restarts (after the initial startup). Restarts are usually related
to a software fault, whereas hardware causes can include uncorrectable memory
faults or a failed disk driver interaction.
The following is the syntax for the event rule HardwareRestarted:

-name HardwareRestarted -on no -eventType hwRestarted -eventArgsExpr
’’ -notifyType email -dst ’you@company.com’ -ccDst ’’ -msg ’NPS system
$HOST - $hwType $hwId restarted at $eventTimestamp.’ -bodyText
’$notifyMsg\n\nSPA ID: $spaId\nSPA Slot: $spaSlot\n’ -callHome yes
-eventAggrCount 50
You can modify the event rule to specify that the system include the device serial
number, its hardware revision, and firmware revision as part of the message,
subject, or both.
The following table describes the arguments to the HardwareRestarted event rule.
Table 8-11. HardwareRestarted event rule
hwType The type of hardware affected spu
hwId The hardware ID of the regen source 1013
SPU having the problem
spaId The ID of the SPA A number 1 - 32
spaSlot The SPA slot number Usually a slot number from 1
to 13
devSerial The serial number of the SPU 601S496A2012
devHwRev The hardware revision 7.21496rA2.21091rB1
devFwRev The firmware revision 1.36
Related concepts:
Disk space threshold notification

You can use the hwDiskFull event type (defined in the default event rules
Disk80PercentFull and Disk90PercentFull) to receive notification when any one of
the system’s SPUs’ disk space becomes more than 80-85, or 90-95 percent full.
The following is the syntax for the event rule Disk80PercentFull:

-name Disk80PercentFull -on no -eventType hwDiskFull -eventArgsExpr
’$threshold == 80 || $threshold == 85’ -notifyType email -dst
’you@company.com’ -ccDst ’’ -msg ’NPS system $HOST - $hwType $hwId
$partition partition is $value % full at $eventTimestamp.’ -bodyText
’$notifyMsg\n\nSPA ID: $spaId\nSPA Slot: $spaSlot\nThreshold:
$threshold\nValue: $value\n’ -callHome yes -eventAggrCount 50
The following is the syntax for the event rule Disk90PercentFull:

-name Disk90PercentFull -on no -eventType hwDiskFull -eventArgsExpr
’$threshold == 90 || $threshold == 95’ -notifyType email -dst ’<your
email here>’ -ccDst ’’ -msg ’URGENT: NPS system $HOST - $hwType $hwId
$partition partition is $value % full at $eventTimestamp.’ -bodyText
’$notifyMsg\n\nSPA ID: $spaId\nSPA Slot: $spaSlot\nThreshold:
$threshold\nValue: $value\n’ -callHome yes -eventAggrCount 50
The following table lists the arguments to the DiskSpace event rules.
Table 8-12. DiskSpace event rules
hwType The type of hardware affected spu, disk
hwId The hardware ID of the disk that has 1013
the disk space issue
spaId The ID of the SPA
spaSlot The SPA slot number
partition The data slice number 0,1,2,3
threshold The threshold value 75, 80, 85, 90, 95
value The actual percentage full value 84
After you enable the event rule, the event manager sends you an email when the
system disk space percentage exceeds the first threshold and is below the next
threshold value. The event manager sends only one event per sampled value.
For example, if you enable the event rule Disk80PercentFull, which specifies
thresholds 80 and 85 percent, the event manager sends you an email when the disk
space is at least 80, but less than 85 percent full. When you receive the email, your
actual disk space might be 84 percent full.
The event manager maintains thresholds for the values 75, 80, 85, 90, and 95. Each
of these values (except for 75) can be in the following states:
Armed
The system has not reached this value.
Disarmed
The system has exceeded this value.
Fired The system has reached this value.
Rearmed
The system has fallen below this value.
Note: If you enable an event rule after the system reached a threshold, you are not
notified that it reached this threshold until you restart the system.
The following table lists these thresholds and their states.

Table 8-13. Threshold and states
Threshold Armed Triggered Disarmed Rearmed
75 never never never never
80 startup >= 80 && < 85 >= 80 < 75
85 startup >= 85 && < 90 >= 85 < 80
90 startup >= 90 && < 95 >= 90 < 85

Table 8-13. Threshold and states (continued)
Threshold Armed Triggered Disarmed Rearmed
95 startup >= 95 >= 95 < 90
After the IBM Netezza System Manager sends an event for a particular threshold,
it disarms all thresholds at or below that value. (So if 90 is triggered, it does not
trigger again until it is rearmed). The Netezza System Manager rearms all
disarmed higher thresholds when the disk space percentage full value falls below
the previous threshold, which can occur when you delete tables or databases. The
Netezza System Manager arms all thresholds (except 75) when the system starts
up.
Tip: To ensure maximum coverage, enable both event rules Disk80PercentFull and
Disk90PercentFull.
To send an email when the disk is more than 80 percent full, enable the predefined
event rule Disk80PercentFull:
nzevent modify -u admin -pw password -name Disk80PercentFull -on
yes -dst jdoe@company.com
If you receive a diskFull notification from one or two disks, your data might be
unevenly distributed across the data slices (data skew). Data skew can adversely
affect performance for the tables that are involved and for combined workloads.
Tip: Consider aggregating the email messages for this event. Set the aggregation
count to the number of SPUs.
Related concepts:
“Data skew” on page 12-10
Runaway query notification

You can use the RunAwayQuery event type to monitor queries that exceed
configured query timeout limits.
The runaway query timeout is a limit that you can specify system-wide (for all
users), or for specific groups or users. The default query timeout is unlimited for
users and groups, but you can establish query timeout limits by using a system
default setting, or when you create or alter users or groups. The runaway query
timeout limit does not apply to the admin database user.
The following is the syntax for the event rule RunAwayQuery:

-name ’RunAwayQuery’ -on no -eventType runawayQuery -eventArgsExpr ’’
$HOST - long-running query detected at $eventTimestamp.’ -bodyText
’$notifyMsg\n\nsessionId: $sessionId\nplanId: $planId\nduration:
$duration seconds’ -callHome yes -eventAggrCount 0
The following table lists the arguments to the RunAwayQuery event rule. The
arguments are case-sensitive.

Table 8-14. RunAwayQuery event rule
Arguments Description Examples
sessionId The ID of the runaway session Use these arguments for the email
message.
planId The ID of the plan
duration The amount of time (in seconds) that
the query was running when it
exceeded its timeout.
Note: Typically you do not aggregate this event because you should consider the
performance impact of each individual runaway query.
When you specify the duration argument in the -eventArgsExpr string, you can
specify an operator such as: ‘==’, ‘!=’, ‘>’, ‘>=’, ‘<’, or ‘<=’ to specify when to send
the event notification. Use the greater-than (or less-than) versions of the operators
to ensure that the expression triggers with a match. For example, to ensure that a
notification event is triggered when the duration of a query exceeds 100 seconds,
specify the -eventArgsExpr as follows:
-eventArgsExpr ’$duration > 100’
If a query exceeds its timeout threshold and you added a runaway query rule, the
system sends you an email that informs you how long the query ran. For example:
NPS system alpha - long-running query detected at 07-Nov-03, 15:43:49
EST.
sessionId: 10056
planId: 27
duration: 105 seconds
Related concepts:
“Query timeout limits” on page 11-37
You can place a limit on the amount of time a query is allowed to run before the
system notifies you by using the runaway query event. The event email shows
how long the query has been running, and you can decide whether to terminate
the query.
System state
You can also monitor for events when a system is “stuck” in the Pausing Now
state. The following is the syntax for event rule SystemStuckInState:
-name ’SystemStuckInState’ -on no -eventType systemStuckInState
-eventArgsExpr ’’ -notifyType email -dst ’<your email here>’ -ccDst ’’
-msg ’NPS system $HOST - System Stuck in state $currentState for
$duration seconds’ -bodyText ’The system is stuck in state change.
Contact Netezza support team\nduration: $duration seconds\nCurrent
State: $currentState\nExpected State: $expectedState’ -callHome yes
-eventAggrCount 0
It is important to monitor the transition to or from the Online state because that
transition affects system availability.
Disk predictive failure errors event

The hard disks where your user databases reside record certain performance and
reliability data as they perform I/O. This status is referred to as Self-Monitoring
Analysis and Reporting Technology (SMART) status. You can use the event
manager to notify you when certain threshold values are crossed in the recorded
performance or reliability data.

Exceeding these thresholds might indicate that the disk has started to run poorly
(that is, it reads or writes data more slowly than it should) and affects the speed at
which queries are processed. It might even indicate that the disk might fail soon.
IBM Netezza sets the thresholds that are based on analysis of disk drives and their
performance characteristics. If you receive any of these events, contact Netezza
Support and have them determine the state of your disk. Do not aggregate these
events. The templates do not aggregate these events by default.
The following is the syntax for the event rule SCSIPredictiveFailure event:
-name ’SCSIPredictiveFailure’ -on no -eventType scsiPredictiveFailure
-msg ’NPS system $HOST - SCSI Predictive Failure value exceeded for
disk $diskHwId at $eventTimestamp’ -bodyText
’$notifyMsg\n\nspuHwId:$spuHwId\ndisk
location:$location\nscsiAsc:$scsiAsc\nscsiAscq:$scsiAscq\nfru:$fru\nde
vSerial:$devSerial\ndiskSerial:$diskSerial\ndiskModel:$diskModel\ndisk
Mfg:$diskMfg\nevent source:$eventSource\n’ -callHome no
-eventAggrCount 0
The following table lists the output from the SCSIPredictiveFailure event rule.
Table 8-15. SCSIPredictiveFailure event rule
spuHwId The hardware ID of the SPU that owns or
manages the disk that reported the event
diskHwId The hardware ID of the disk 1013
scsiAsc The attribute sense code, which is an Vendor specific
identifier of the SMART attribute
scsiAscq The attribute sense code qualifier of the Vendor specific
SMART attribute
fru The FRU ID for the disk
location The location of the disk
devSerial The serial number of the SPU to which 601S496A2012
the disk is assigned
diskSerial The disk serial number 7.21496rA2.21091rB1
diskModel The disk model number
diskMfg The disk manufacturer
Regeneration errors
If the system encounters hardware problems while it attempts to set up or perform
a regeneration, the system triggers a RegenFault event rule.
The following is the syntax for the event rule RegenFault:

-name ’RegenFault’ -on no -eventType regenFault -eventArgsExpr ’’
-notifyType email -dst ’<your email here>’ -ccDst ’’ -msg ’NPS system
$HOST - regen fault on SPU $hwIdSpu.’ -bodyText
’$notifyMsg\n\nhwIdSrc:$hwIdSrc\nsource
location:$locationSrc\nhwIdTgt:$hwIdTgt\ntarget
location:$locationTgt\ndevSerial:$devSerial\nerror
string:$errString\nevent source:$eventSource\n’ -callHome no
-eventAggrCount 0

The event rule RegenFault is enabled by default.
The following table lists the output from the event rule RegenFault.
Table 8-16. RegenFault event rule
hwIdSpu The hardware ID of the SPU that owns or 1013
manages the problem disk
hwIdSrc The hardware ID of the source disk
locationSrc The location string of the source disk
hwIdTgt The hardware ID of the target spare disk
locationTgt The location string of the target disk
errString The error string for the regeneration issue
devSerial The serial number of the owning or reporting
SPU
Disk errors event

When the disk driver detects an error, it notifies the system. If a serious error
occurs, the system fails over the disk. You can also configure the event manager to
notify you with email when the disk is failed over.
Note: If you receive a significant number of disk error messages, contact IBM
Netezza Support to investigate the state of your disks.
If you enable the event rule SCSIDiskError, the system sends you an email message
when it fails a disk.
The following is the syntax for the event rule SCSIDiskError:

-name ’SCSIDiskError’ -on no -eventType scsiDiskError -eventArgsExpr
’’ -notifyType email -dst ’<your email here>’ -ccDst ’’ -msg ’NPS
system $HOST - disk error on disk $diskHwId.’ -bodyText
’$notifyMsg\nspuHwId:$spuHwId\ndisk location:$location\nerrType:
$errType\nerrCode:$errCode\noper:$oper\ndataPartition:$dataPartition\n
lba:$lba\ndataSliceId:$dataSliceId\ntableId:$tableId\nblock:$block\nde
vSerial:$devSerial\nfpgaBoardSerial:$fpgaBoardSerial\ndiskSerial:$disk
Serial\ndiskModel:$diskModel\ndiskMfg:$diskMfg\nevent
source:$eventSource\n’ -callHome no -eventAggrCount 0
The following table lists the output from the SCSIDiskError event rule.
Table 8-17. SCSIDiskError event rule
Argument Description Examples
spuHwId The hardware ID of the SPU that owns or manages
the disk or FPGA
diskHwId The hardware ID of the disk where the error 1013
occurred
location The location string for the disk
errType The type of error, that is, whether the error is the 1 (Failure), 2 (Failure imminent) 3 (Failure
type failure, failure possible, or failure imminent possible), 4 (Failure unknown)
errCode The error code that specifies the cause of the error 110

Table 8-17. SCSIDiskError event rule (continued)
oper The operation in progress when the disk driver 0 (read), 1 (write)
encountered the error; the possible values are read
or write
dataPartition The data partition number on which the error 1
occurred
Iba The logical block address where the error occurred 145214014
tableId The table ID where the error occurred 200350
dataSliceId The data slice ID where the error occurred 3
block The table-relative block number where the error 9
occurred
devSerial The serial number of the SPU that owns the disk or
FPGA
fpgaBoardSerial The serial number of the Netezza DB Accelerator
card where the FPGA resides
diskSerial The disk serial number 7.21496rA2.21091rB1
diskModel The disk model number WesternDigital
diskMfg The disk manufacturer
Hardware temperature event

The event manager monitors the hardware temperature of key components within
the system to maintain reliability and prevent failures because of overheating. The
system monitors the actual temperatures from SPUs and disk enclosures. If the
internal temperature rises above specified operational levels, the system sends the
hwThermalFault event through the event rule ThermalFault. Some hardware
components and models do not report thermal settings. For example, the S-blades
(SPUs) on IBM PureData System for Analytics N200x systems do not report
thermal data.
Running a system at elevated temperatures can adversely affect disk life

expectancy. If you receive a hardware temperature event, do the following:
v Physically investigate the machine room.
v Verify that the ambient temperate is within acceptable limits.
v Check that the airflow to and from the Netezza system is not occluded.
v Verify that there are no signs of combustion.
v Check that the cooling components (fans, blowers, or both) are functioning
properly.
v Check the temperature event emails for specific details.
In some cases, you might need to replace components such as cooling units (fans,
blowers, or both), or perhaps a SPU.
The following is the syntax for event rule ThermalFault:

-name ’ThermalFault’ -on no -eventType hwThermalFault -eventArgsExpr
$HOST -$hwType $hwId Hardware Thermal Fault at $eventTimestamp’

-bodyText
’$notifyMsg\n\nlabel:$label\nlocation:$location\ncurVal:$curVal\nerror
string:$errString\nevent source:$eventSource\n’ -callHome no
-eventAggrCount 0
The following table lists the output from the ThermalFault event rule.
Table 8-18. ThermalFault event rule
hwType The hardware type where the error occurred SPU* or disk enclosure
hwId The hardware ID of the component where the 1013
fault occurred
label The label for the temperature sensor. For the
IBM Netezza Database Accelerator card, this
label is the BIE temperature. For a disk
enclosure, it is temp-1-1 for the first
temperature sensor on the first enclosure.
location A string that describes the physical location of
the component
curVal The current temperature reading for the
hardware component
errString The error message The board temperature
for the SPU exceeded 45
degrees centigrade.
The default behavior is to send email notification.
System temperature event

For an Netezza z-series (also called Mustang) system, the system temperature
event can notify you when three boards (SPUs or SFIs) in an SPA reach the red
threshold.
The following is the syntax for event rule SystemHeatThresholdExceeded:

-name SystemHeatThresholdExceeded -on no -eventType sysHeatThreshold
-eventArgsExpr ’’ -notifyType runCmd -dst ’$NZ_BIN_DIR/adm/nzpwrdown’
-msg ’Urgent: NPS system $HOST -$hwType $hwId System Heat Threshold
Exceeded at $eventTimestamp’ -bodyText ’$notifyMsg\n\nError
Type:$errType\nError Code:$errCode\nError String:$errString\n’
-callHome no -eventAggrCount 0
The following table lists the SystemHeatThresholdExceeded event rule arguments.

Table 8-19. SysHeatThreshold event rule
Argument Description
errCode The integer code for the onboard 301 for warning, 302 for critical
temperature error
errString The error message Thermal overload warning.
Multiple devices are reporting
excessive operating
temperatures. Please
investigate.
errType The type of error 4 (Unknown cannot fail over)

The default behavior is to run the nzstop command and then use RPC to power off
the IBM Netezza system.
Attention: Before you power on the machine, check the SPA that reported this
event. You might need to replace one or more SPUs or SFIs.
After you confirm that the temperature within the environment returns to normal,
you can power on the RPCs by using the following command. Make sure that you
are logged in as root or that your account has sudo permissions to run the
following command: /nzlocal/scripts/rpc/spapwr.sh -on all.
History-data events
There are two event notifications that alert you to issues with history-data
monitoring:
histCaptureEvent
A problem prevented the history-data collection process (alcapp) from
writing history-data files to the staging area.
histLoadEvent
A problem prevented the history-data loader process (alcloader) from
loading history data into the history database.
The following is the syntax for the histCaptureEvent rule:

-name ’HistCaptureEvent’ -on no -eventType histCaptureEvent
-msg ’NPS History Capture Event from $HOST’ -bodyText ’History data
capture error:\nConfiguration Name =$configName\nStorage Limit
=$storageLimit\nLoad Min Threshold =$loadMinThreshold\nLoad Max
Threshold =$loadMaxThreshold\nDisk Full Threshold
=$diskFullThreshold\nLoad Interval =$loadInterval\nTarget NPS
=$nps\nTarget Database =$database\nCurrent Batch Size(MB)
=$capturedSize\nStaged Batches Size(MB) =$stagedSize\nTotal Data
Size(MB) =$storageSize\nBatch Directory =$dirName\nError Code
=$errCode\nError Message = $errString\n’ -callHome yes -eventAggrCount
0
The following table describes the output from the histCaptureEvent rule.
Table 8-20. The histCaptureEvent rule
host The name of the IBM Netezza system that nps1
had the history event
configName The name of the active history fullhist
configuration
storageLimit The storage limit size of the staging area
in MB
loadMinThreshold The minimum load threshold value in MB
loadMaxThreshold The maximum load threshold value in
MB
diskFullThreshold Reserved for future use.
loadInterval The load interval timer value in minutes
nps The Netezza location of the history localhost
database

Table 8-20. The histCaptureEvent rule (continued)
database The name of the history database into
which the captured data is loaded
capturedSize The size in MB of the captured data
currently being written to
$NZ_DATA/hist/staging/
alc_$TIMESEQUENCE
stagedSize The size in MB of all staged files in the
/nz/data/hist/loading directory
storageSize The size in MB of capturedSize plus
stagedSize
dirName The name of the directory which contains alc_$TIMESEQUENCE
the currently captured data
errCode The number which represents the error
problem:
97 History Storage Limit Exceeded
98 History Disk Full Threshold
Exceeded (not used in this
release)
99 History Capture Failure, which
can be a problem that relates to a
disk I/O error or an internal
problem
errString The text string (shown in errCode History Storage
description) for the related error code Limit Exceeded
The following is the syntax for the histLoadEvent rule:

-name ’HistLoadEvent’ -on no -eventType histLoadEvent -eventArgsExpr
’’ -notifyType email -dst ’you@company.com’ -ccDst ’’ -msg ’NPS
History Load Event from $HOST’ -bodyText ’History data load
error:\nConfiguration Name =$configName\nStorage Limit
=$storageLimit\nLoad Min Threshold =$loadMinThreshold\nLoad Max
Threshold =$loadMaxThreshold\nDisk Full Threshold
=$diskFullThreshold\nLoad Interval =$loadInterval\nTarget NPS
=$nps\nTarget Database =$database\nLoaded Batch Size(MB)
=$batchSize\nStaged Batches Size(MB) =$stagedSize\nBatch Directory
=$dirName\nError Code =$errCode\nError Message = $errString\n’
The following table describes the output from the histLoadEvent rule.
Table 8-21. The histLoadEvent rule
host The name of the Netezza system that had the nps1
history event
configName Name of the active history configuration
storageLimit The storage limit size of the staging area in
MB
loadMinThreshold The minimum load threshold value in MB
loadMaxThreshold The maximum load threshold value in MB
diskFullThreshold Reserved for future use.

Table 8-21. The histLoadEvent rule (continued)
loadInterval The load interval timer value in minutes
nps The location of the history database localhost
database The name of the history database into which
the data could not be loaded
batchSize The size in MB of the batch of history files
which are currently being loaded
(/nz/data/hist/loading/alc_$TIMESEQUENCE
directory)
stagedSize The size in MB of all staged files in the
/nz/data/hist/loading directory except the
batch which is loading
dirName The name of the directory that contains the alc_$TIMESEQUENCE
staged batch files
errCode The number which represents the error
problem:
100 History Load Connection Failure
(not used in this release)
101 History Load Config Info Not
Found, which indicates that the
configuration used to collect the data
cannot be found on the system. The
configuration might be dropped or
renamed before the files can be
loaded. In this case, many fields in
the event rule might be set to
_UNKNOWN_ (for string fields) or
-1 (for int fields).
102 History Load Failure, which can be
an ODBC failure such as corrupted
configuration information, or an
internal problem
errString The text string (shown in errCode History Load Config
description) for the related error code Info Not Found
Related concepts:
“History event notifications” on page 14-4
SPU cores event

For IBM Netezza 1000 and later systems, you can now trigger an event when the
system detects a SPU core file. The spuCore event can help you to troubleshoot
query problems on the system.
The following is the syntax for the spuCore event:

-name ’SpuCore’ -on no -eventType spuCore -eventArgsExpr ’’
$HOST - Process Cored on SPU $hwId at $eventTimestamp’ -bodyText
’$notifyMsg\n\nhwId:$hwId\nerror string:$errString\nevent
source:$eventSource\n’ -callHome no -eventAggrCount 0
The following table lists the output from the spuCore event rule.

Table 8-22. The spuCore event rule
hwId The hardware ID of the SPU on which a 1013
process cored
errString Specifies the name of the process that created
the core file
Voltage faults event

On IBM Netezza 1000 and later systems, the system monitors the voltages and
power for the SPUs and disk enclosures. If the voltage sensors detect variations
that are outside the specified operational range, the system sends the
hwVoltageFault event through the event rule VoltageFault.
The following is the syntax for event rule VoltageFault:

-name ’VoltageFault’ -on no -eventType hwVoltageFault -eventArgsExpr
$HOST -$hwType $hwId Hardware Voltage Fault at $eventTimestamp’
-bodyText
’$notifyMsg\n\nlabel:$label\nlocation:$location\nvoltage:$curVolt\nerr
or string:$errString\nevent source:$eventSource\n’ -callHome no
-eventAggrCount 0
The following table lists the output from the VoltageFault event rule.
Table 8-23. VoltageFault event rule
hwType The hardware type where the error occurred SPU* or disk enclosure
hwId The hardware ID of the component where the 1013
fault occurred
label The label for the nominal voltage sensor. For
example, voltage-1-1 represents the first voltage
sensor in the first disk enclosure. For the
Netezza Database Accelerator card, BIE 0.9V is
an example for the 0.9V nominal voltage.
location A string that describes the physical location of
the component
curVolt Specifies the current voltage of the component.
This value is a string that also includes the
sensor that exceeded the voltage threshold.
errString Specifies more information about the voltage
fault; if the problem component is the Netezza
Database Accelerator card, it is specified in the
string.
Transaction limits event

The TransactionLimitEvent sends an email notification when the number of
outstanding transaction objects exceeds 90 percent of the available objects. There is
a limit of approximately 65,000 transaction objects. New transactions are blocked
with an error message that there is no space for the transactions array.

This event notifies you when 90 percent (approximately 59,000) of the transaction
objects are in use, and also provides information about the oldest transaction. A
sample email follows:
NPS system nzhost - current number (59000) of transactions exceeded 90%
of total limit at 30-Aug-11, 14:00:59 EDT.
Oldest Active Transaction:
txid: 0x4eeba
Session id: 101963
PID: 19760
Database: system
User: admin
Client IP: 127.0.0.1
Client PID: 19759
Transaction start date: 2011-08-30 10:55:08
To reduce the outstanding transaction count you may want to consider

completing/aborting the above transaction.
The number of transaction objects in use can drop by the completion of active
transactions, but if the problem relates to older transactions that have not been
cleaned up, you can abort the oldest session. In addition, you can use the
nzsession -activeTxn command to identify the active transactions. You can
identify and abort the older transactions as necessary to free the transaction
objects. (You can also stop and restart the IBM Netezza software to clean up the
transactions.)
Note: The notification repeats every three hours if the object count remains above
90 percent, or when the object count drops below 85 percent but later reaches
59,000 again.
The following table lists the output of the transaction limit event.
Table 8-24. TransactionLimitEvent rule
curNumTX Specifies the current number of transaction
objects which are in use.
Switch port events

The system manager logs events when the following criteria are met:
v For chassis switches, the system manager logs a HW_NEEDS_ATTENTION
event when either:
– The number of ports specified by sysmgr.numberOfDownPortToRiseEvent are
down for more the number of seconds specified by
sysmgr.portDownTime1ToRiseEvent
– Any one port is down for more than the number of seconds specified by
sysmgr.portDownTime2ToRiseEvent
“Changing configuration settings” on page 7-19 describes how to modify these
configuration settings, if necessary.
v For fabric switches, the system manager logs a HW_NEEDS_ATTENTION event
when it detects that a port or link is down.
v For all switches, the system manager logs the HW_RESTARTED event when it
detects that a switch has rebooted.

Reachability and availability events
The system manager now detects and logs events when devices such as
management modules, ESMs, SAS switches, and fans/blowers are unreachable or
unavailable. These new monitoring tools help you to identify and troubleshoot
possible issues within the system that can affect system performance.
Availability event
A device is unavailable to the system when it is in the Down or Missing state. A

device can be unavailable for a short time because of system maintenance tasks
such as a part replacement. The system manager now detects extended periods
when a device is unavailable and logs an event to notify you of the problem. The
sysmgr.availabilityAlertTime setting specifies how long the device must be Down
or Missing before it is considered unavailable. The default value is 300 seconds.
When the timeout expires, the system manager logs a HW_NEEDS_ATTENTION
event to notify you of the problem.
If a device is unavailable, the most common reasons are that the device is no
longer operating normally and has transitioned to the Down state, it was powered
off, or it was removed from the system. Investigate to determine the cause of the
availability issue and take steps to replace the device or correct the problem.
Reachability event
A device is unreachable when it does not respond to a status request from its
device manager. A device can be unreachable for a short time because it is busy
and cannot respond in time to the status request, or there might be congestion on
the internal network of the system that delays the status response. The system
manager now detects extended periods when a device is unreachable and logs an
event to notify you of the problem. The sysmgr.reachabilityAlertTime setting
specifies how long the device manager waits for status before it declares a device
to be unreachable. The default value is 300 seconds. When the timeout expires, the
system manager raises a HW_NEEDS_ATTENTION event to notify you of the
problem.
If a device is unreachable, the most common reasons are that the device is busy
and cannot respond to status requests, or there might be a problem with the
device. If the device is temporarily busy, the problem usually clears when the
device can respond to a status request.
Topology imbalance event

The TopologyImbalance event sends an email notification when the system detects
a disk topology imbalance after a disk regeneration or when the system transitions
to the online state after a rebalance.
When an imbalance problem is detected, the system writes more detailed

information to the sysmgr.log and the eventmgr.log files. A sample email for this
event follows:
From: NPS Event Manager [mailto:eventsender@netezza.com]
Sent: Friday, June 15, 2012 6:06 PM
To: <you@company.com>
Subject: NPS system nzhost - Regen imbalance event has been recorded at
15-Jun-12, 08:36:07 EDT System initiated.
NPS system nzhost - Topology imbalance event has been recorded at 15-
Jul-12, 08:36:07 EDT System initiated.

Warning:
Topology imbalance after rebalance :
...
SPA 1 SAS switch [sassw01b] port [4] has 7 disks
For systems that use an older topology configuration, you could encounter
situations where the event is triggered frequently but for a known situation. In that
event, you can disable the event by setting the following registry value. You must
pause the system, set the variable, and then resume the system.
[nz@nzhost ~]$ nzsystem set -arg
sysmgr.enableTopologyImbalanceEvent=false
Event types reference

There are some event types that are not available as templates, but that you can
use to create rules for various monitoring events.
Network Interface State Change event
The Network Interface State Change event sends an email notification when the
state of a network interface on a SPU has changed.
The new event is not available as an event template in Release 5.0.x. You must add
the event by using the following command:
[nz@nzhost ~]$ nzevent add -name SpuNetIfChanged -eventType
nwIfChanged -notifyType email -msg ’A network interface on a SPU has
changed states.’ -dst <your email here>
S-Blade CPU core events
The numCpuCoreChanged event notifies you when a SPU CPU core goes offline
and the SPU is operating at a reduced performance. You can add the event by
using a command similar to the following:
nzevent add -name SpuCpuCoreChangeEvent -eventType numCpuCoreChanged
-notifyType email -msg "Num Core Changed" -dst <email_id> -bodyText
’\n Hardware id = $hwId\n Location = $location\n Current number of
cores = $currNumCore\n Changed number of cores = $changedNumCore’
If a SPU has a core failure, the system manager also fails over that SPU.
Display alerts
If the NzAdmin tool detects an alert, it displays the Alert entry in the navigation
list. The NzAdmin tool displays each error in the list and indicates the associated
component. The Component, Status, and other columns provide more information.
For the hardware alerts, the alert color indicator takes on the color of the related
component. If, however, the component is green, the NzAdmin tool sets the alert
color to yellow.

Figure 8-1. Alerts Window
v To view the alerts list, click the Alerts entry in the left pane.
v To get more information about an alert, double-click an entry or right-click and
select Status to display the corresponding component status window.
v To refresh alerts, select View > Refresh or click the refresh icon on the toolbar.

Chapter 9. About the callhome service
The callhome service is an automated notification process that detects problem
conditions on the IBM PureData System for Analytics appliances and reports them
to IBM Netezza Support.
The callhome service is an optional feature that improves and simplifies the work
to report the most common types of problems that could occur on the appliance. If
you enable callhome, the service watches your system for issues such as failed
SPUs/S-Blades or disks, host failovers, unexpected system state changes, or SPU
core files. When it detects a problem, the callhome service automatically gathers
the basic information for the problem, and contacts IBM Support with information
about the problem.
The callhome service contacts the automated IBM Support servers, which open a
PMR for your system that is then assigned to a Support engineer for investigation.
The PMR is identical to a PMR that you create when you report problems for your
Netezza appliance. The callhome service ensures that the PMR contains the
required information about the system and problem. You can review and update
the PMR with more information and follow its progress as you would for any
PMR that you create. The customer contacts that you designate also receive an
email with the PMR number.
The log files and diagnostics are the same files that IBM Support engineers request
when first addressing an issue. Since the callhome service includes these files in
the automated notification, the PMR moves more quickly to analysis and
resolution. If necessary, the Support engineer could contact your site administrators
for more information as needed, but the initial information is already part of the
callhome problem report.
The callhome service is supported on the following appliance models:

v IBM PureData System for Analytics N1001 (including the IBM Netezza TwinFin®
and IBM Netezza 1000 models)
v IBM PureData System for Analytics N200x
v IBM PureData System for Analytics N3001
Note: Callhome does not support the IBM Netezza 100 (Skimmer®) models, the
IBM Netezza High Capacity Appliance C1000 appliances, or the IBM Netezza
Platform Development Software installations.
The callhome service uses the IBM PureData System for Analytics appliance to
have Hypertext Transfer Protocol Secure (HTTPS)/Simple Object Access Protocol
(SOAP) access and Simple Mail Transport Protocol (SMTP) in the data center. If
you do not allow HTTPS/SOAP connections from the data center, you can
configure callhome to use SMTP notifications to report events to the IBM Support
servers. If HTTPS/SOAP or SMTP access is not available or supported in your data
center, you cannot use the callhome service.
Important: The callhome service is not required. If you do not enable callhome,
you can still open PMRs by using the standard IBM Support processes. If you
choose to enable callhome, you can configure and enable the service yourself, or
you can obtain assistance from IBM Support to configure the callhome service on

deployed systems. For new systems, the IBM Netezza installation engineer can
help you to set up the callhome service. You can disable the callhome service at
any time to temporarily or permanently stop the automatic notifications and
collection of problem information.
Set up callHome.txt
You use the callHome.txt file to specify important contact and service information
about your IBM Netezza system.
Before you begin
Make sure that you gathered the required information for your system including
model information, administrative contacts, and system location information.
Procedure
1. Log in to the active host of the IBM Netezza system as the nz user.
2. Change to the /nz/data/config directory. Use caution when working in the
/nz/data directory or its subdirectories. Any unintentional changes or deletions
in this directory area can impact the performance and data on your system.
3. Make a backup copy of the callHome.txt file using the following command:
cp callHome.txt callHome.txt.bk
4. Using a text editor such as vi, edit the callHome.txt file.
A sample of a callHome.txt file follows. Your file will also have some content
at the bottom to show update history.
# callHome.txt
#
# Call home attachment file containing installation-specific attributes.
customer.company =
customer.address1 =
customer.address2 =
customer.address3 =
customer.ICN =
contact1.name = <contact name>

contact1.phone =
contact1.email =
contact1.cell =
contact1.events =
contact2.name =
contact2.phone =
contact2.email =
contact2.cell =
contact2.events =
system.description = <sys description>

system.location = <sys location>
system.model = <model #>
system.MTM = <machine type / model>
system.serial = <serial #>
system.CC = <2 digit ISO country code>
system.modemNumber =
Important: To enable callhome support, you must specify values for the
customer.company, customer.address1, customer.address2, and customer.ICN
fields; at least one complete customer contact block with name, phone, email,
and an event option; and the system block including model, MTM, serial, and

cc. For your customer<n>.email address, if you have an email distribution list
for all of your Netezza administrators, consider using that list for the event
notification emails.
5. Type the information for your company name and address, the contact name
and phone number for the persons who manage the Netezza system at your
site, and the system information.
When you use the callHome.txt file with the callhome support utility, note that
the following fields are strictly enforced.
customer.address<n>
Specify the street address of the data center or facility where the IBM
Netezza system is located. This is the address to which IBM service
representatives are dispatched for the repair and service of the
appliance.
customer.ICN
Specify the IBM customer number, which is a unique 7-digit ID
assigned to each customer and is used in the IBM ticketing and
tracking systems.
contact<n>.events
Specify the types of callhome events, if any, for which the related
contact<n>.name should be used. Note that the Hardware and DBA
filtering is not currently supported. Make sure that only one of your
contacts is set to ALL.
Hardware
Use the specified contact name for callhome generated
hardware service calls.
DBA Use the specified contact name for callhome generated service
calls (other than hardware).
ALL Use the specified contact name for all callhome generated
service calls. You cannot specify this value combined with
either DBA or Hardware.
none (or null)
Do not use the specified contact name for any service calls.
system.MTM
Specify the machine-type and model for the Netezza appliance type.
For a new system, the IBM system installers obtain this data from the
bar code label on the system. For existing systems on which you are
enabling the callhome service, contact the IBM Client Care team at
tsmail@us.ibm.com for assistance in obtaining the number.
system.serial
Specifies the unique 7-character serial number for the system. The serial
numbers for systems typically starts with the two characters NZ or 78,
depending upon the manufacturing location of the appliance. Older
Netezza systems may use a different format for the serial number. For a
new system, the IBM system installers obtain this data from the bar
code label on the system. For existing systems on which you are
enabling the callhome service, contact the IBM Client Care team at
tsmail@us.ibm.com for assistance in obtaining the number.
system.CC
Specifies the 2-character ISO country code where the appliance is
Chapter 9. About the callhome service 9-3

located. You can obtain an online reference of the ISO country codes at
https://www.iso.org/obp/ui/#search.
dedup.minAppendMinutes
After an event triggers call home to open a PMR, specifies a time limit
in minutes for any subsequent events on the system to be reported on
the same PMR. IBM Support can see which events are likely to be
related to the same root cause. By default, call home uses a value of 30
minutes.
dedup.maxAppendHours
Specifies a time range in hours for a new event to be evaluated as a
duplicate of an event that has already been reported. By default, call
home uses a value of 25 hours. For example, after the
minAppendMinutes window expires, the system evaluates the next
event that triggers call home to see if that problem has already been
reported.
v If the event is a new problem, call home opens a new PMR.
v If the event is a duplicate of an event that occurred previously within
the maxAppendWindow range, the new event is ignored as a
duplicate and call home does not open or append to a PMR.
After the maxAppendHours time limit expires, any new event is
compared to previous events. If the event is a duplicate of one that
caused call home to open a PMR, the same PMR is updated with
information about the new event. If the PMR is closed, call home opens
a new PMR for the problem. If the event is a new problem and there is
no existing PMR, call home opens a new PMR.
proxy.location
Specifies the IP address or fully qualified host name of the proxy server
in your environment. This field does not appear in the callHome.txt file
by default, but if your environment requires HTTPS applications such
as call home to route traffic through a proxy server, specify the server
name in this field. You omit this field and the proxy.port if your
environment does not use a proxy for HTTPS traffic.
proxy.port
Specifies the listen port number for the proxy server in your
environment.
6. Save your changes to the callHome.txt file and close the file.
Example
An example of a completed callHome.txt file follows.

# callHome.txt
#
# Call home attachment file containing installation-specific attributes.
# One contact block must be completed with:
# Customer Name, Phone or Cell, Email and Events set to ALL.
# The system block must have all entries other than modemNumber completed.
customer.company = Acme Corporation

customer.address1 = 26 Main St
customer.address2 = Anytown, MA
customer.address3 =
customer.ICN = 1234567
contact1.name = John Smith

contact1.phone = 123 456-7890

contact1.email = jsmith@acme.com
contact1.cell =
contact1.events = ALL
contact2.name =
contact2.phone =
contact2.email =
contact2.cell =
contact2.events = ALL
system.description = Acme Analytics System

system.location = 1st Floor Data Center, row 2, rack 5
system.model = N2001-010
system.MTM = 3565/EG1
system.serial = NZ30123
system.CC = US
# 2014-09-09 22:49:38 -0400 (EDT): Successful transition from 7.0.4.4 to 7.2.0.0
What to do next
As a best practice, you can confirm that the changes to the callHome.txt file are
correct and complete by using the nzcallhome -validateConfig command. The
command checks the callHome.txt file and logs any problems such as fields that
are incorrectly specified or if required fields are missing. You can then correct any
problems in the file, save the file, and retry the status command. For example, if
the configuration file is complete, the command logs the following message:
[nz@nz10065 ~]$ nzcallhome -validateConfig -debug
CallHome configuration is good.
If the validation process finds an issue in the callHome.txt file, it logs an error
message. For example:
[nz@nz10065 ~]$ nzcallhome -validateConfig -debug
Tue Aug 19 10:41:58 EDT 2014 INFO: NzCallHome called with args: -validateConfig
Tue Aug 19 10:41:58 EDT 2014 SEVERE: The required field "system.MTM" is missing
or not configured with a
valid machine type and model. Valid format should be "MACH/MOD".
The required field "system.serial" is missing or not configured with a

valid serial number. Valid format should be "NZ12345"
or for new Striper systems"7812345".
Please correct the errors in /nz/data/config/callHome.txt and continue.
Review the messages in the /nz/kit/log/nzCallHome/nzCallHome.0.log file to

identify issues with the file format or contents that must be resolved to enable
callhome support.
Custom callhome email subject fields

You use two custom fields in the callHome.txt file to specify custom subject
strings in the callhome email notifications.
Within the callHome.txt file, you can define optional custom.field1 and
custom.field2 values to create unique strings within the callhome notification
emails. These fields can help users to filter the notification emails using email rules
that they have defined, or to include more easily identifiable information in the
email subject, such as a hostname for the source IBM Netezza system that reported
the problem.

To add the custom fields, you must log in the Netezza active host as the nz user
and edit the /nz/data/config/callHome.txt file using any test editor. You should
first make a backup copy of the callHome.txt file before you change it to protect
against unintended edits or changes to the file.
You can specify up to 10 characters in the custom fields. Insert the fields after the
system.* fields and before the comment history at the bottom of the file. An
example of a callHome.txt file with the custom fields follows:
system.description = Acme Analytics System
system.location = 1st Floor Data Center, row 2, rack 5
system.model = N2001-010
system.MTM = 3565/EG1
system.serial = NZ30123
system.CC = US
custom.field1 = nz80533-h1
custom.field2 = Shared
# 2014-09-09 22:49:38 -0400 (EDT): Successful transition from 7.0.4.4 to 7.2.0.0
If you do not define custom fields, the email subject includes the first 10 characters
of the hostname and system.description field, if defined, from the callHome.txt
file.
Set up the sendMail.cfg File

To support the callhome service, the sendMail.cfg file must include a mail server
name and port number, and the email sender name and address for the automated
emails that are sent to IBM Netezza Support.
Before you begin
Make sure that you have the required information for your email server and the
source email address. You may need to contact your data center IT team to obtain
the email server information for your environment. Most data centers have strict
policies about email access and use. If your environment has policies that prevent
email from the data center, you may not be able to use the callhome service.
Contact IBM Netezza Support for more information about the email policies and
options.
Procedure
2. Change to the /nz/data/config directory. Use caution when working in the
/nz/data directory or its subdirectories. Any unintentional changes or deletions
in this directory area can impact the performance and data on your system.
3. Using a text editor such as vi, edit the sendMail.cfg file.
A sample of a default, empty sendMail.cfg file follows. Your file could have
some content already if it was previously updated by IBM installers or Support,
or an administrator at your site.
# sendMail.cfg
#
# Configuration parameters for sendMail program.
# Mail server name and port
mailServer.name = mail1.netezza.com
mailServer.port = 25

# Note: Uncomment and set the entries below to enable authentication based on
username, password and authentication method.
# Login information
#login.username =
#login.password =
# Login method of mail server

# Enter value as
# 1 for CRAM MD5
# 2 for AUTH LOGIN
# 3 for LOGIN PLAIN
# Note: User authentication will not be done, if none of the above value is
provided
#login.method =
# Sender information
sender.name = "NPS Event Manager"

sender.address = eventsender@netezza.com
# Other
# Note: Valid separators between multiple mail addresses are ’,’ or ’;’
cc =
4. Type the information for your mailServer.name and mailServer.port, and the
sender.name and sender.address. For the sender.name, specify a unique client
or system name to clearly identify the email that is sent from your system. You
could include the system hostname or other unique client name. Do not include
any punctuation marks or special characters in the sender.name because they
could be interpreted incorrectly by the mail handler. The sender.address value
must point to a valid internet domain. The sender might not exist, but the
internet domain in the address (for example, mycomp.com) must be reachable
through SMTP on the internet. The address cannot be an internal (private)
domain within the customer intranet. Internal addresses that are not reachable
by SMTP could be rejected by spam filters.
5. Save your changes to the sendMail.cfg file and close the file.
Results
The callhome service now has a configured email server and information for
sending the notification emails.
Example
An example of a completed sendMail.cfg file is as follows.

# Mail server name and port
mailServer.name = mymailsrv.corp.com
mailServer.port = 25
# Sender information
sender.name = "nzhost EventMgr"

sender.address = nzhostname@mycomp.com

Configure access to the IBM Support servers
If you use callhome to open PMRs, make sure that your IBM PureData System for
Analytics appliance can communicate with the IBM Support servers.
If you configure callhome to use the email/SMTP option for triggering

notifications to IBM Support to open PMRs, your IBM PureData System for
Analytics appliance must be able to send email to ibm.com® hosts.
When callhome uses Hypertext Transfer Protocol Secure (HTTPS)/Simple Object

Access Protocol (SOAP) access method for events that trigger on your IBM
PureData System for Analytics appliance, the appliance uses port 443 (HTTPS) to
send those messages to IBM Support servers. The following table lists the available
IBM Support servers and their IP addresses. Make sure that your Netezza
appliance can send outgoing messages via port 443 to any of these addresses. It is
recommended that you open the 129.42.0.0/18 subnet for the most flexibility if
your IT security policies permit that.
Table 9-1. IBM Support servers for call home PMR access
Host name IP address
eccgw01.boulder.ibm.com 207.25.252.197
eccgw02.rochester.ibm.com 129.42.160.51
www-945.ibm.com 129.42.26.224
129.42.42.224
129.42.50.224
www.ecurep.ibm.com 192.109.81.20
www-03.ibm.com 204.146.30.17
www.ibm.com 129.42.56.216
129.42.58.216
129.42.60.216
esupport.ibm.com 129.42.54.189
129.42.56.189
129.42.60.189
The HTTPS/SOAP method for callhome also sends email to your customer
contacts when a PMR has been created. Make sure that you consult with your IT
security and networking team about the corporate firewall support for the
outbound SMTP and port 443 HTTPS traffic. If there are questions about the
callhome support, or if the callhome test messages do not appear to be working,
contact IBM Support for assistance.
Enable the callhome service

You use the nzcallhome command with the -on option to enable the IBM Netezza
callhome service.
Before you begin
Before you enable the callhome service, make sure that the callHome.txt file and
sendMail.cfg file are configured with your system, contact, and email information.

Procedure
2. Run the following command to enable the callhome service.
[nz@nzhost nz]$ nzcallhome -on -debug
NzCallHome: enabled operation
Results
The command checks the callHome.txt file to verify that the required information
is complete and then enables the callhome service. If there are errors or missing
information in the callHome.txt file, the command logs error messages to the
/nz/kit/log/nzCallHome/nzCallHome.0.log that you can use to fix the file and then
re-try the -on command. For example, if the callHome.txt file does not include a
complete customer contact block, the command logs the following error:
A completely configured customer contact block was not found. At least one contact
needs to be configured with phone, email and one of the event levels to notify that
contact on - ( Hardware | DBA | ALL ).
The next step is to configure the Netezza event rules used for the callhome
monitoring. If the callhome event rules are already present on the system and
enabled, the monitoring processes are activated.
nzcallhome verbose output

You can display more information for the nzcallhome commands by using the
-debug option.
The nzcallhome commands typically display no information on the command line.

To increase the messages that appear on the console, use the -debug option with
the command. For example:
[nz@nzhost ~]$ nzcallhome -enableStatus
The command returns no information or messages on the command line. However,

if you include the -debug option, the command displays more information about
the command operation:
[nz@nzhost ~]$ nzcallhome -enableStatus -debug
NzCallHome: enabled Status operation
The topics in this section frequently use the -debug to show more verbose output
messages.
Enable callhome debug logging

You can increase the amount of information written when the nzcallhome
command runs. The command writes messages and status to the callhome log file
in /nz/kit/log/nzCallHome/nzCallHome.0.log.
To increase the debug logging information, use the nzcallhome -enableDebug

command to enable debug mode. For example:
[nz@nzhost ~]$ nzcallhome -enableDebug
After callhome is running and operating as expected, you can disable the extra
debug logging information if you no longer require the details. To disable the
debug mode, use the nzcallhome -disableDebug.

Enable PMR creation
The callhome service can open a PMR automatically with IBM Support when a
callhome-related event triggers on the IBM Netezza system.
The callhome service contacts the automated IBM Support servers, which open a
PMR for your system that is then assigned to a Support engineer for investigation.
To activate the PMR notifications, you must enable the service using the
nzcallhome -enablePmr command.
By default, callhome uses the HTTPS/SOAP protocol to contact the servers and
open the PMR. If you cannot or do not want to use the HTTPS/SOAP protocol to
open PMRs, you must run an additional nzcallhome -enableEmailOnly command
to configure callhome to open the PMR via email notifications. For more
information, see “Enable email-only PMR notification” on page 9-11.
You can disable the PMR notifications using nzcallhome -disablePmr.
Note: When you use the nzcallhome -enablePmr command, the callhome service
configures and enables the callhome event rules and then enables the PMR
notification feature. When you use the -disablePmr option, the callhome service
removes the callhome event rules.
To generate a test PMR, see “Generate callhome events” on page 9-15.
Enable status reporting

The callhome service supports the ability to send on-demand status and appliance
health updates for the IBM Netezza system to IBM Support.
The callhome service can collect and report health and status of the IBM Netezza
system and send it to IBM Support. The information consists of non-confidential
details such as the following:
v Performance status
v Capacity status
v Disk duty cycles
v I/O rates and capacities
v Client success metrics such as the number of queries completed
To activate the status reporting feature, you must enable the service using the
nzcallhome -enableStatus command. You can disable the service using nzcallhome
-disableStatus.
To generate a status report, use the nzcallhome -generateStatus command.
Note: If you have enabled status reporting and your IBM Netezza system is
running the System Health Check v2.3 or later software, the health check services
automatically collect and report status on a daily basis.
Enable inventory reporting

The callhome service supports the ability to send on-demand inventory reports for
the IBM Netezza system to IBM Support.

The callhome service can collect and report inventory information about the IBM
Netezza system and send it to IBM Support. The information consists of
non-confidential details such as the following:
v Upgrade history
v Maintenance changes
v Service work or updates
To activate the inventory reporting feature, you must enable the service using the
nzcallhome -enableInventory command. You can disable the service using
nzcallhome -disableInventory.
To generate an inventory report, use the nzcallhome -generateInventory

command.
Note: If you have enabled inventory reporting and your IBM Netezza system is
running the System Health Check v2.3 or later software, the health check services
automatically collect and report the inventory on a weekly basis.
Enable email-only PMR notification

If you cannot or do not want to use the default HTTPS/SOAP protocol for opening
PMRs, you can configure callhome to send PMR notifications using email from the
IBM Netezza system.
To activate the email-only PMR reporting feature, use the nzcallhome

-enableEmailOnly command after you run the nzcallhome -enablePmr command.
You can disable the email PMR notification and return to HTTPS/SOAP protocols
using nzcallhome -disableEmailOnly.
Display callhome service status

You can use the nzcallhome command to display whether the callhome service is
enabled or disabled. The command also displays information about debug mode
and the PMR, inventory, and status generation processes.
Procedure
2. Run the following command to display the callhome status.
[nz@nzhost nz]$ nzcallhome -status -debug
NzCallHome: operational state is ’enabled’
NzCallHome and in debug mode
NzCallHome: PMR generation enabled
NzCallHome: Status generation enabled
NzCallHome: Inventory generation enabled
Results
The command output states whether callhome is enabled or disabled, whether

debug mode is enabled, and whether the PMR, inventory, or status generation
processes are enabled. If the callhome service is disabled, the command displays a
message that you can enable the service using nzcallhome -on. For example:
NzCallHome called with args: -status -debug
NzCallHome: operational state is ’disabled’
NzCallHome and in debug mode
NzCallHome: PMR generation disabled

NzCallHome: Status generation disabled
NzCallHome: Inventory generation disabled
NzCallHome operational state is disabled.
Run nzcallhome -on to enable.
Callhome event rules

The callhome service creates and uses event rules to monitor important conditions
on the IBM Netezza system and to send notifications when those conditions occur.
When you configure the callhome monitoring rules, the command creates the
following rules in the event manager. When a problem condition triggers the rule,
the rule calls the nzcallhome command to send the automatic notifications to IBM
Support.
Table 9-2. Callhome event rules
Event rule name Description
diskMonitorPredictive The Disk Monitor Predictive event is a custom event that
reports issues found in disks based on the predictive
monitoring rules in System Health Check. These errors
usually indicate a disk that is failing or requires investigation
or replacement.
hwNeedsAttentionAuto The Hardware Needs Attention event reports problems that
include replacement disks with invalid firmware, storage
configuration changes, unavailable/unreachable components,
disks that reach a grown defects early warning threshold,
Ethernet switch ports that are down, and other conditions
that are early warnings of problems that affect system
behavior or the ability to manage devices within the system.
hwPathDownAuto The Path Down event reports situations where the path
between an S-Blade/SPU and its disks has failed. Failed
paths adversely affect system and query performance
because the storage processing workloads are not balanced
within the system. It is important to identify and resolve the
issues that are causing path failures to return the system to
optimal performance as soon as possible.
hwServiceRequestedAuto The Service Requested event triggers when a hardware
component fails so that IBM Support can notify service
technicians that can replace or repair the component. Many
components are redundant, so a failure typically activates a
spare component or redistributes work to the remaining
healthy components. It is important to replace a failed
component quickly so that you restore normal operation and
performance, and so that the system has its full complement
of spares and component redundancy.
hwVoltageFaultAuto The Voltage Fault event monitors the voltages and power for
the SPUs and disk enclosures, and reports cases when the
voltage is outside the normal operating range.
regenFaultAuto The Regen Fault event reports hardware problems that occur
when the system is setting up or performing a disk
regeneration. This event is an important warning because the
system could have a situation where user data is stored on
only one disk and there is no redundant copy of the data. If
the one primary disk is lost to failure, the user data stored
on that disk could be lost.

Table 9-2. Callhome event rules (continued)
Event rule name Description
scsiDiskErrorAuto The SCSI Disk Error event notifies you when a disk has
failed. The disk should be replaced as soon as possible to
restore the normal number of spare disks in the system.
scsiPredictiveFailureAuto The SCSI Predictive Failure event notifies you when a disk
has exceeded its Self-Monitoring Analysis and Reporting
Technology (SMART) thresholds. Exceeding these thresholds
might indicate that the disk has started to run poorly (that is,
it reads or writes data more slowly than it should) and
affects the speed at which queries are processed. It can also
indicate that the disk might fail soon.
spuCoreAuto The SPU core event notifies you when the system detects a
SPU core file, which could indicate that a query or other
process running on the SPU failed and created a core file for
diagnostics.
sysStateChangedAuto The System State Changed event notifies you when the
system state changes, or when a state change exceeds a
specified timeout.
topologyImbalanceAuto The Topology Imbalance event reports when the system
detects a disk topology imbalance after a disk regeneration
or when the system transitions to the online state after a
rebalance. This problem can lead to query performance
issues if not corrected.
Callhome event severities

The callhome events for the IBM PureData System for Analytics appliances use the
default IBM appliance PMR severity settings.
Table 9-3. Callhome event conditions and severities
Problem area Corresponding Netezza events Severity
Blade and hwNeedsAttention 3
disk issues
hwServiceRequested 3
hwVoltageFault 4
Disk issues diskMonitorPredictive 3
regenFault 2
scsiPredictiveFailure 3
scsiDiskError 4
SPU cores spuCore 4
Cluster sysStateChanged 2
failover
The severity is the expected problem severity level for this type of condition. If the
Distributed Replicated Block Device (DRBD) cluster status indicates that the
Netezza system is not in a healthy cluster mode, the severity level increases to 2
because the Netezza appliance could go offline if it encounters any problem
condition that requires a host failover. In addition, if the current system state is
Down at the time of the failure, the severity increases to 1 because the system is
offline.

For a description of the Netezza events, see the IBM Netezza System Administrator’s
Guide. For a description of the problem severity levels, see the IBM Passport
Advantage Problem Support Handbook at http://public.dhe.ibm.com/software/
server/applhandbook/ApplianceSupportHandbook.pdf.
Blocking callhome events

You can configure the callhome service to ignore certain event conditions and to
suppress the reporting of the problems that triggered those event rules.
You can filter the events that trigger a callhome notification by defining rules in
the /nz/data/config/eventBlacklist.txt file. The filter rules define event
conditions that should not be processed by callhome, which can help to reduce
undesired notifications to IBM Support and to your configured customer contacts
list.
When a callhome event rule is triggered, the callhome service checks the
eventBlacklist.txt file to verify that the event is problem condition that should
be processed and sent as a notification to IBM Support. You can create filter rules
that use any of the following formats:
v rule1.eventType = spuCore
v rule1.hwType = SPU
v rule1.errString = my error string
For the eventType filter, specify one of the nzEvent types which are configured for
Call Home such as hwNeedsAttention, hwServiceRequested, hwPathDown,
hwVoltageFault, regenFault, scsiDiskError, scsiPredictiveFailure, spuCore,
sysStateChanged, or topologyImbalance.
For the hwType filter, you can specify any of the hardware type values. To list the
hardware type values, use the nzhw listTypes command.
For the errString value, you can specify a unique string as it would appear in the
errString output of the event rule.
To create the blocking list of filters, define the rules in a text file and save the file
as /nz/data/config/eventBlacklist.txt. After you create the file, callhome checks
the filter rules before it processes notifications for any of the events that trigger on
the appliance.
If callhome ignores an event because of a matching filter, the callhome service logs
a message in the /nz/kit/log/nzCallHome/nzCallHome.0.log file to capture
information about the event that was skipped. You can edit the filter rules at any
time, and you can rename or delete the eventBlacklist.txt file to stop applying
all of the defined filter rules during callhome processing.
Information collected by callhome

When a monitored problem condition occurs on an IBM PureData System for
Analytics appliance, the callhome service gathers important related logs and files
for the notification that it sends to IBM Support.
When one of the problem conditions that callhome monitors is triggered, the
callhome service gathers the following types of information from the appliance.
The information is compressed into a .tgz file that has the name convention

eventType-hexStamp-hwType-hwID.tgz, where hexStamp is a unique identifier and
hwType might be truncated. The .tgz file typically includes only a subset of the
following information for the details specific to the problem category.
v callHome.txt and log files
v sysmgr.log and eventmgr.log files
v topology logs
v DRBD logs for host status
v SMART logs for disk errors
v Stack traces for SPU/S-Blade crashes (core dumps)
v Network configuration output
v nzhw output
v nzhwinfo output
Testing the callhome services

The nzcallhome command includes several options that you can use to test and
validate the callhome services.
Generate callhome events

You use the nzcallhome command with the -generatePmr option to test the
callhome behavior by triggering one or more of the monitored callhome events,
and if the rules are enabled, to notify the IBM Support servers and you customer
contacts.
Before you begin
The callhome service must be enabled to run the command, and PMR service must
also be enabled. The event rules must be configured and enabled to test the event
notification process. If the event rules are not configured or enabled, the command
runs and displays event information, but notifications are not sent for the tests.
Procedure
2. Run the nzcallhome -generatePmr <options> command.
If you specify -generatePmr without any options, the command triggers a test
of all the monitored event rules. You can specify one or more of the following
options in a space-separated list:
diskMon
Generate disk_monitorPredictive events.
clusterSsc
Generate Cluster Fail Over event from a sysStateChanged event.
scsiDISKA
Generate scsiDiskError for DISK 'A'
spuCore
Generate spuCore (will evaluate last core present, if any.)
scsiPredDISKB
Generate scsiPredictiveFailure for DISK 'B'
hwVoltSPU
Generate hwVoltageFault for SPU.

scsiPredDISKBDup
Generate scsiPredictiveFailure for DISK 'B' (duplicate of previous.)
hwAttnSPU
Generate hwNeedsAttention for SPU.
regenSPUDISKA
Generate regenFault for SPU with Disk 'A'.
sscOnline
Generate a sysStateChanged event.
hwSPU
Generate hwServiceRequested for SPU.
hwDISKB
Generate hwServiceRequested for DISK 'B'.
Results
The command triggers the requested event or events as a test. The command
requires a minute or two to complete, especially if you supply more than one event
rules to generate as tests.
If callhome is not enabled when you run the -generatePmr command, the
command displays the following message:
NzCallHome: operational state is disabled.
If the PMR service is not enabled when you run the -generatePmr command, the
command displays the following message:
PMR generation is disabled.
Example
The following example command triggers a test SPU hardware voltage event.
[nz@nzhost nz]$ nzcallhome -generatePmr hwVoltSPU
invoked [HwVoltageSpu: /nz/kit/bin/nzevent generate -eventType hwVoltageFault
-eventArgs label=AC/IN,hwType=spu,hwId=1017,location=spa1.spu1,devSerial=8273649817,
curVolt=104,errString=’THIS_is_ONLY_a_TEST.’]
The following example command triggers a test SCSI disk and hardware disk
event.
[nz@nzhost nz]$ nzcallhome -generatePmr scsiDISKA hwDISKB
invoked [ScsiDiskError: /nz/kit/bin/nzevent generate -eventType scsiDiskError
-eventArgs spuHwId=1017,diskHwId=1022,location=,errType=5,errCode=69,oper=4,
dataPartition=0,lba=1234124,tableId=102456,dataSliceId=23,block=12345,fpgaEngineId=4,
fpgaBoardSerial=98234fwe133,devSerial=ThisIsOnlyATEST,diskModel=someModel,
diskMfg=IBM-EXSX,errString=’THIS_is_ONLY_a_TEST.’]
invoked [HwDISKB: /nz/kit/bin/nzevent generate -eventType hwServiceRequested
-eventArgs hwType=disk,hwId=1023,location=spa1.diskEncl1.disk3,devSerial=
ThisIsOnlyATEST,errString=THIS_is_ONLY_a_TEST]
See “Sample callhome email” on page 9-17 for an example of the email that is
created when you generate events for an enabled event rule.
See “Callhome processing verification (email only)” on page 9-17 for more
information about confirming that the callhome event completed successfully and
how to troubleshoot problems.

Callhome processing verification (HTTPS only)
If you configured the call home service to use HTTPS notifications, review these
steps to verify the callhome notification process.
To test the call home processing, generate a test PMR to verify that the services are
working:
[nz@nzhost nz]$ nzcallhome -generatePmr hwSPU
If call home is working and the connections to the IBM servers are open, you
should see a message similar to the following in the log file:
Tue Feb 24 09:57:17 EST 2015 INFO: srid = xxxxxyyyzzz
Tue Feb 24 09:57:49 EST 2015 INFO: The NzCallHome forensics and report generation
has completed
The xxxxxyyyzzz value is the number of the PMR (service request) created by the
command.
Callhome processing verification (email only)

If you configured the call home service to send email only, review these steps to
verify the callhome notification process.
When the callhome events detect a condition that triggers an event, the callhome
feature sends an email to IBM Support and to the contacts listed in callHome.txt.
After the PMR is opened, the IBM Support server sends an automatic email to
your designated administrators in callHome.txt. You can use the emails for the
problem report and the resulting PMR number as indicators that the callhome
processes are reporting problems detected on your system.
If you are enabling the callhome feature, but you are not a member of that
callHome.txt notification list, it might be difficult to confirm that the email
notifications are working as expected. Follow these steps to review the common
error logs for indications of possible problems. If you do not see any issues in the
log files, the callhome notification process completed. Otherwise, use the messages
to identify the problems and troubleshooting steps.
v Review the sendMail logs in the /nz/kit/log/sendMail directory that are time
stamped with the time of the generate command. Confirm that the log file
messages indicate that the email was sent.
v Review the nzOpenPmr log in the /nz/kit/log/nzOpenPmr directory. Verify that
there are no errors in the log file messages.
v As the root user, confirm that there are no related errors or issues posted to
/var/log/messages file.
Important: As a best practice, do not generate a test event on a scheduled or

regular basis. Frequent test events can create a large number of service requests
(PMRs) as well as distracting email traffic to your administrators.
Sample callhome email

When a callhome event triggers a notification, or when you generate a callhome
event, the callhome service sends an email to report the condition.
A sample email follows. The sample was edited to be generic for the
documentation.

From: nzhost EvtMgr <nzhost@nzlab.ibm.com>
To: Netezza Appliance Call Home/Marlborough/Contr/IBM@IBMUS,
Cc: jsmith@acme.com
Date: 11/20/2013 10:16 PM
Subject: NzCallHome TEST_UI_spuCore SPU 1017 @ spa1.spu1 TEST
Appliance Location
----------------------------------------------------------------------
ICN: 1234567 CC US
Company: Acme Corporation
Address: 26 Main St
Marlborough, MA
Client Contact for ALL issues

----------------------------------------------------------------------
Name: John Smith
e-Mail: jsmith@acme.com
Phone: 123 456-7890
Mobile:
Appliance Identification
----------------------------------------------------------------------
MTM: 3563/GDO N1001-020 IBM PureData System for Analytics N1001-020
Serial#: NZ8012345
NzId: NZ8012345
HostName: nzhost.acme.com
Use: Acme Analytics System
Location: 1st Floor Data Center, last row rack
Appliance Status
----------------------------------------------------------------------
Nz State: online
Up Time: 22:38:1 sec
Host DRBD: 0 issues (of 2)
Hardware 0 issues:
Compliment SPAs 4, SPUs 24, Disks 192
DataSlices: 0 issues (of 184)
Topology: ok
Regens: 0 issues
Appliance Software Versions

----------------------------------------------------------------------
HPF: 5.3.2
FDT: 2.6.1
NPS: 7.1
nzOpenPmr: 2013-10-02 NPS 7.1
SW Support: support-IBM_Netezza-7.0.3.0-130408-1457
GNU/Linux: Red Hat Enterprise Linux Server release 5.7 (Tikanga)
Disc Stamp: Netezza OS ISO RHEL5.5 v1.2;Fri May 13 14:02:10 EDT 2011
x86_64: kernel 2.6.18-274.3.1.el5
Device: SPU 1017 spa1.spu1 Active Online

----------------------------------------------------------------------
Diagnostic Attempt to identify operation which caused SPU core.
hwid 1017
Sys.Mgr.# 13 for 1017 0
Event.Mgr# 3 for 1017 0
Events 0 system initiated User 0
Incident:
09:44:16 est\neventargs: hwid = 1017
coreData = HASH(0x1a310a0)
crash-version = 4.1.2-8.el5 WARNING!
detailtext = eventType:_spuCore
eventTimestamp:_04-Dec-13
errstring = THIS_is_ONLY_a_TEST.
eventts = 04-Dec-13

pgdate = 2013-12-04 09:44:16
remains = eventSrc=User initiated,eventTS=04-Dec-13,
detailText=eventType: spuCore
eventTimestamp: 04-Dec-13, 09:44:16 EST
eventArgs: hwId=1017, errString=THIS_is_ONLY_a_TEST.
eventSource: User initiated event
,errString=THIS_is_ONLY_a_TEST.
Context:
eventmgrlines = 3
regenStatus = 0
sysmgrlines = 13
Generate callhome reports

You use the nzcallhome command with the -generateInventory or
-generateStatus option to test the inventory and status reporting.
The callhome service must be enabled to run the command, and the inventory
and/or status reporting services must also be enabled. The following example
commands generate test reports:
[nz@nzhost nz]$ nzcallhome -generateInventory
[nz@nzhost nz]$ nzcallhome -generateStatus
The command could take a few minutes to complete.
If you want to generate sample reports for your review, but do not want to send
the reports to IBM Support, you can use the additional -dataInspection option to
skip the transmission of the report. For example:
[nz@nzhost nz]$ nzcallhome -generateInventory -dataInspection -debug
Generate a system upgrade request

You can use the nzcallhome command to request a software upgrade on your
system.
About this task
The request is sent to IBM Support and directed to the team that schedules
software upgrades. The request includes basic information about your appliance
that Support typically requests for upgrade services.
Procedure
2. Run the nzcallhome command with the -requestUpgrade option.
[nz@nzhost nz]$ nzcallhome -requestUpgrade
Disable the callhome service

You can disable the callhome service to stop the automatic monitoring and
reporting of events on the IBM Netezza appliance during service or other
maintenance windows.
About this task
Typically, you disable the callhome service only during software upgrades, service
operations, or troubleshooting tasks when it is possible that the system state could

change or when you are manually failing over the HA hosts or performing tasks
like component replacements or other steps. If callhome remains enabled during
these service operations, the service could detect the routine system state changes
or issues and trigger the callhome event rules, which would result in "false alarms"
to the IBM Support services.
Procedure
2. Run the nzcallhome command with the -off option.
[nz@nzhost nz]$ nzcallhome -off -debug
NzCallHome: disabled operation
NzCallHome operational state is disabled.
Results
The callhome service is stopped, which means that the monitored problem
conditions no longer trigger automatic notifications to IBM Support. The callhome
service stops sending notifications for problems. When you complete the upgrades
or service steps, re-enable the callhome service monitoring using the nzcallhome
-on command to resume normal monitoring and automatic notifications for
problems.
Disable callhome event rules

You can use the nzcallhome -disable command to turn off or disable all of the
callhome event rules and stop the notifications to your configured customer
contacts and IBM Support.
Before you begin
When you disable an event rule, the system does not raise or trigger that event
when the associated condition occurs. You typically disable a rule when you are
debugging system conditions that might cause events to trigger as false alarms and
you want to temporarily stop any notifications. The -disable option turns off all of
the callhome-related events. You could also use the nzEvent command to turn off a
specific event rule that you are testing or for which you want to stop notifications.
Procedure
2. Run the nzcallhome command with the -disable option.
[nz@nzhost nz]$ nzcallhome -disable -debug
Disable nzevent rule: /nz/kit/bin/nzevent add -on no -name disk_monitorPredictiveAuto
Disable nzevent rule: /nz/kit/bin/nzevent modify -on no -name hwNeedsAttentionAuto
Disable nzevent rule: /nz/kit/bin/nzevent modify -on no -name hwServiceRequestedAuto
Disable nzevent rule: /nz/kit/bin/nzevent modify -on no -name sysStateChangedAuto
Disable nzevent rule: /nz/kit/bin/nzevent modify -on no -name regenFaultAuto
Disable nzevent rule: /nz/kit/bin/nzevent modify -on no -name scsiDiskErrorAuto
Disable nzevent rule: /nz/kit/bin/nzevent modify -on no -name scsiPredictiveFailureAuto
Disable nzevent rule: /nz/kit/bin/nzevent modify -on no -name spuCoreAuto
Disable nzevent rule: /nz/kit/bin/nzevent modify -on no -name hwVoltageFaultAuto
Disable nzevent rule: /nz/kit/bin/nzevent modify -on no -name topologyImbalanceAuto
Disable nzevent rule: /nz/kit/bin/nzevent modify -on no -name hwPathDownAuto
disabled 11 nzevents.

Results
The command disables or turns off all of the callhome event rules, but the rules are
still defined in the event rule tables. If any of the event conditions occur or if you
generate an event for testing using nzcallhome -generate, the callhome service
does not take any action to collect information about the problem and open a PMR
with the IBM Netezza Support server. After your testing is complete, you can turn
on the event rules using the nzcallhome -enable command.
Remove callhome event rules

If you no longer want to monitor any of the callhome event rules, you can remove
the event rules from the IBM Netezza system. As a best practice, remove the
current callhome event rules before configuring and enabling the new rules after
upgrading to a new Netezza Platform Software release.
Before you begin
The callhome service must be enabled before you can remove the event rules. See
“Enable the callhome service” on page 9-8.
Procedure
2. Run the nzcallhome -remove command.
[nz@nzhost nz]$ nzcallhome -remove -debug
Remove nzevent rule: /nz/kit/bin/nzevent delete -force -name disk_monitorPredictiveAuto
Remove nzevent rule: /nz/kit/bin/nzevent delete -force -name hwNeedsAttentionAuto
Remove nzevent rule: /nz/kit/bin/nzevent delete -force -name hwServiceRequestedAuto
Remove nzevent rule: /nz/kit/bin/nzevent delete -force -name sysStateChangedAuto
Remove nzevent rule: /nz/kit/bin/nzevent delete -force -name regenFaultAuto
Remove nzevent rule: /nz/kit/bin/nzevent delete -force -name scsiDiskErrorAuto
Remove nzevent rule: /nz/kit/bin/nzevent delete -force -name scsiPredictiveFailureAuto
Remove nzevent rule: /nz/kit/bin/nzevent delete -force -name spuCoreAuto
Remove nzevent rule: /nz/kit/bin/nzevent delete -force -name hwVoltageFaultAuto
Remove nzevent rule: /nz/kit/bin/nzevent delete -force -name topologyImbalanceAuto
Remove nzevent rule: /nz/kit/bin/nzevent delete -force -name hwPathDownAuto
remove 11 nzevents.
Results
The command deletes the event rules that were added to monitor the callhome
problem conditions. After the events are removed, the callhome service is not
monitoring any event conditions.
Even if there are no callhome event rules defined when you run the -remove
command, the command displays the same messages in debug mode. To verify
that there are no callhome events rules configured on your system, you can use a
command such as nzevent | grep nzcall to list any callhome-related events. The
command should not return any results after the -remove operation.
If callhome is not enabled when you run the -remove command, the command
displays the following message:
NzCallHome called with args: -remove -debug
NzCallHome: operational state is disabled.

Note: When you run the nzcallhome -disablePmr option, the command also
removes the callhome event rules. You must run nzcallhome -configure or
nzcallhome -enablePmr to define the event rules in the system again.

Chapter 10. Enhanced cryptography support
Starting in IBM Netezza release 7.1, you can enable support for cryptographic
standard SP 800-131a.
Special Publication 800-131a (SP 800-131a) is an information security standard of

the National Institute of Standards and Technology (NIST). SP 800-131a is a
recommendation that provides guidance for the use of stronger cryptographic keys
and connection settings. IBM Netezza offers the ability to configure an appliance to
support the SP 800-131a recommendations. If you enable enhanced cryptography
support, you must adhere to specific requirements for the host keys that you use
for cryptography, for the authentication modes that are used for all connections to
the Netezza databases, and for the digitally signing the audit history configuration
and database (if you use the audit history feature).
Netezza Host Prerequisites
Your IBM Netezza appliance must have the correct revision of the Red Hat
operating system with more libraries and RPMs, and the system must be running
NPS Release 7.1 or later.
v For an IBM PureData System for Analytics N3001 rack appliance (models
N3001-002 through N3001-080), the system must be running NPS release
7.2.0.0-P1 or later, Red Hat 6.5 and Host Management 5.4 or later, which enables
support for the cryptographic libraries and runtimes.
v For an IBM PureData System for Analytics N3001-001 appliance, the system
must be running NPS release 7.2.0.1 or later, Red Hat 6.5 and Host Management
5.4.1 or later, which enables support for the cryptographic libraries and
runtimes.
v For an IBM PureData System for Analytics N200x appliance, the system must be
running Red Hat 6.4 and Host Management 5.2 or later, which enables support
for the cryptographic libraries and runtimes.
v For an IBM PureData System for Analytics N100x appliance (or the earlier
models that are called IBM Netezza 1000 or Netezza TwinFin), the system must
be running Red Hat 5.9 and Host Management 5.2 or later, which enables
support for the cryptographic libraries and runtimes.
Note: The SP 800-131a cryptographic support is not offered on other IBM Netezza
appliance models.
If your system is not running the minimum levels of the NPS, Red Hat, or Host
Management software, contact IBM Netezza Support for more information about
upgrading your system.
Client Prerequisites
If you install and use the NPS client packages to connect to IBM Netezza
appliances that are configured to support the SP 800-131a cryptography standards,
note the following requirements:
v If you use JDBC to access the IBM Netezza appliance, your JDBC client must
have Java Runtime Environment v1.7 or later, which includes SP 800-131a
cryptography support.

v If you connect to the IBM Netezza appliance using Secure Shell (SSH) protocols,
you must obtain and install an SP 800-131a-compliant SSH client program. IBM
does not provide the SSH client libraries. Refer to the operating system vendor
and product information for more details on the available SSH clients and how
to install the client.
v If your client system uses an older Red Hat release such as 4.0, you must obtain
and install GLIBC 2.4 or later to support the v7.1 NPS clients. This is a
requirement for the v7.1 Red Hat clients regardless of whether the IBM Netezza
system is configured to use SP 800-131a support.
As a best practice, upgrade your client systems to the latest NPS client packages.
Older clients can connect to the IBM Netezza SP 800-131a compliant host using any
security level setting except onlySecured. The preferredUnSecured,
preferredSecured, or onlyUnSecured security levels are supported. If the IBM
Netezza appliance is not using SP 800-131a support, all four levels are supported.
NPS requirements for enhanced cryptography support

If you configure your IBM Netezza system to support the SP 800-131a
cryptography standard, familiarize yourself with the following important
requirements for connecting to and using the system.
v To support the enhanced cryptography standards, the NPS system now supports
stronger cryptographic controls for passwords and connections and for
encrypting data within an audit history database. You can use the
DSA_KEYPAIR_2048 data type to create SP 800-131a-compliant cryptography
keys.
v You must set the system host key to a cryptography key that uses AES-256
encoding to ensure that the system uses a strong cryptography when encrypting
all of the passwords that are stored on the appliance.
v All connections to the Netezza database must use SHA256 authentication. The
MD5 and CRYPT authentication connections are not allowed for an NPS system
that uses enhanced cryptography. You will have to drop the MD5 and CRYPT
connections and redefine them using SHA256 authentication.
v If you use Kerberos authentication, work with your Kerberos administrator to
ensure that the Kerberos Key Distribution Center (KDC) confirms with
SP800-131a. Verify that the Kerberos netezza principal uses only the
des3-cbc-sha1, aes128-cts-hmac-sha1-96, or aes256-cts-hmac-sha1-96 encryption
types.
v If you use an audit history database on your system, the audit history
configuration must be digitally signed with an SP 800-131a compliant key of
type DSA_KEYPAIR_2048.
How to enable SP 800-131a support

You use the nzconfigcrypto -enable command to enable enhanced cryptography
SP 800-131a support on your IBM Netezza appliances.
The nzconfigcrypto -enable command checks the system to ensure that it meets
the software and operating system prerequisites to support the SP 800-131a
changes, as described in Chapter 10, “Enhanced cryptography support,” on page
10-1. If the prerequisites are complete, the command does the following tasks:
v Sets the enable_crypto_srd_v1 postgresql.conf registry setting to true to enable
support for enhanced cryptography.

v Checks and if needed sets the supplied AES-256 host key as the default host key
for the enhanced cryptographic support.
v Updates the authentication for the connection settings to use the stronger
encryption methods.
v Disables the LDAP or Kerberos configuration, if either LDAP or Kerberos is
configured. You must re-enable the LDAP or Kerberos configuration after
enhanced cryptography support is enabled to ensure that the authentication
enforces the strong cryptography standards.
v Disables the current audit history configuration if the current audit configuration
does not conform to SP 800-131a support. You must update the audit history
configuration to use a digitally signed cryptography key of type
DSA_KEYPAIR_2048 and make it the current configuration.
After you run the nzconfigcrypto command, you must stop and restart the NPS
software using the nzstop and nzstart commands to activate the SP 800-131a
compliant operation.
Enabling SP 800-131a support

You use the nzconfigcrypto command to enable support for the SP 800-131a
enhanced cryptography on an IBM Netezza appliance.
Before you begin
Your system must be running the required levels of the NPS, Red Hat, and Host
Management releases, and the NPS software must be started. See Chapter 10,
“Enhanced cryptography support,” on page 10-1 for more information. The
nzconfigcrypto script fails if these prerequisites are not met. When you run the
command, you must specify an existing host key of type AES-256 as input to the
command. If gthe system default host key is already an AES-256 key, you can
specify that key name. For more information about creating and setting a host key,
see the IBM Netezza Advanced Security Administrator's Guide.
Procedure
1. Log in to the active host of the Netezza system as the nz user. In these
examples, the active host name is nzhost1.
2. Run the nzconfigcrypto -enable command and specify the host key name. The
host key must already be defined in your NPS system and must be of type
AES-256. An example command follows:
[nz@nzhost1 ~]$ nzconfigcrypto -HK ks1.key1 -enable
Checking support for crypto standard in NPS
Checking support for crypto standard in OS
Checking for required library
All required libraries found installed
Checking NPS system state
Checking and updating Host Key
Host Key already set
Checking and updating LDAP connection
No LDAP configuration found
Checking and updating Kerberos connection
No Kerberos configuration found
Checking and updating Authentication type
Checking and updating Audit History Configuration
No audit history configuration found
Checking and updating postgresql.conf file
Chapter 10. Enhanced cryptography support 10-3

Successfully updated parameter enable_crypto_std_v1
Crypto mode successfully enabled

You may now restart NPS
The script checks the system and sets the system default host key to the
specified one (if it is not already the default key). In the example, the system
was not configured to use either LDAP or Kerberos authentication, or an audit
history configuration. However, if you use either LDAP, Kerberos, or audit
history, the command disables those features if they are currently
non-compliant with the enhanced cryptography support.
If Kerberos was enabled on the system, the command also displays the
following messages. Note the SET AUTHENTICATION command in the
output. You will supply that command in a future step to enable Kerberos
authentication again.
Restore Kerberos configuration with following command
SET AUTHENTICATION kerberos kdc ’mykdc.com’ realm ’MYREALM.COM’
WARNING:
Kerberos conformance with SP800-131a cannot be controlled by the NPS.
Verify that the Kerberos netezza principal will use only the des3-cbc-sha1,
aes128-cts-hmac-sha1-96, or aes256-cts-hmac-sha1-96 encryption types.
This must be configured on your Kerberos KDC.
3. Stop and re-start the NPS software by using the nzstop and nzstart
commands.
4. After the NPS software starts, type the nzsql command to log in to the system
database as the admin user
[nz@nzhost1 ~]$ nzsql
Welcome to nzsql, the IBM Netezza SQL interactive terminal.
Type: \h for help with SQL commands

\? for help on internal slash commands
\g or terminate with semicolon to execute query
\q to quit
SYSTEM.ADMIN(ADMIN)=>
5. Confirm that the host key is now set to the stronger key that you specified in
the nzconfigcrypto command:
SYSTEM.ADMIN(ADMIN)=> SHOW SYSTEM DEFAULT HOSTKEY;
NOTICE: ’HOST KEY’ = ’KS1.KEY1’
SHOW VARIABLE
6. If you use LDAP authentication for your database user accounts, type the
following command to restore the LDAP configuration with the enhanced
cryptographic support:
SYSTEM.ADMIN(ADMIN)=> SET AUTHENTICATION ldap ssl ’on’ attrname ’cn’
base ’dc=netezza,dc=com’ namecase ’lowercase’ server ’yourldapsvr.company.com’
version ’3’
7. If you use Kerberos authentication for your database user accounts, type the
command that was displayed in the message output from the nzconfigcrypto
-enable command earlier in this procedure to enable the Kerberos configuration:
SYSTEM.ADMIN(ADMIN)=> SET AUTHENTICATION kerberos kdc ’mykdc.com’ realm ’MYREALM.COM’;
Updating /nz/data.1.0/config/krb5.conf and other files.
Re-log-in or open a new shell for changes to take effect.
SET VARIABLE
8. If you had an audit history configuration that was disabled by the script, you
can update the history configuration to digitally sign it using a
DSA_KEYPAIR_2048 key as in the following sample configuration named
audit1:
SYSTEM.ADMIN(ADMIN)=> ALTER HISTORY CONFIG audit1 KEY ks1.seckey;
After you alter the audit configuration, you can make it the current
configuration to enable that history collection. After you change a history
configuration, you must set the new configuration to be the current one, and
then stop and restart the NPS software by using the nzstop and nzstart
commands to fully enable the audit configuration.
Results
The nzconfigcrypto -enable command verifies that the system can support
enhanced cryptography and enables the SP 800-131a support on the Netezza
appliance. The command creates a log file named /tmp/crypto_date_time.log to
capture the messages and information for later review and troubleshooting.
Updating connections for crypto support

If you use the SP 800-131a cryptography support on your IBM Netezza appliance,
check your connection definitions and make sure that they all use SHA256
authentication.
IBM Netezza appliances does not allow connections that use the MD5 or CRYPT
authentication types. You must drop these non-compliant connections and redefine
them to use SHA256 authentication.
Checking the connection types

Procedure
1. Log in to the Netezza system as the nz user.
2. Connect to a database and run the SHOW CONNECTION command to review
the current connection definitions. Sample command output follows:
SYSTEM.ADMIN(ADMIN)=> SHOW CONNECTION;
CONNID | CONNTYPE | CONNDB | CONNIPADDR | CONNIPMASK | CONNAUTH
--------+----------+--------+------------+-----------------+----------
1 | local | all | | | trust
2 | host | all | 0.0.0.0 | 0.0.0.0 | md5
3 | host | all | 127.0.0.1 | 255.255.255.255 | sha256
(3 rows)
As shown in the sample output, connection 2 uses md5 connection
authentication, which is not supported in an enhanced cryptography
environment, You must change the connection to use SHA256 authentication.
3. To change the authentication for connection 2, use the following command:
SYSTEM.ADMIN(ADMIN)=> SET CONNECTION HOST DATABASE ’all’ IPADDR ’0.0.0.0’
IPMASK ’0.0.0.0’ AUTH ’SHA256’;
SET VARIABLE
4. Repeat for each connection definition that uses md5 or crypt authentication.
Results
After you updated your connections, you can enable the crypto support with the
nzconfigcrypto command and start the NPS software by using the nzstart
command. If you have any md5 or crypto connections defined, the nzstart
command fails. You must disable crypto support and use the procedure in this
topic to update your connections, then re-enable crypto support, and restart the
NPS software.

Disabling enhanced cryptography support
Follow these steps to disable the enhanced cryptography support on your IBM
Netezza appliance.
About this task
Typically, you would not disable cryptography support unless you were evaluating
and testing the enhanced cryptography support and have decided not to use it, or
if you are troubleshooting a configuration problem that is preventing you from
starting the NPS software. You can disable cryptography support temporarily to
start the NPS software, investigate and debug the problem, and then you can
re-enable the cryptography support and restart the NPS software.
Procedure
1. Log in to the Netezza appliance as the nz user.
2. Run the following command:
[nz@nzhost1 ~]$ nzconfigcrypto -disable
Checking support for crypto standard in NPS
Checking and updating postgresql.conf file
Successfully updated parameter enable_crypto_std_v1
Crypto mode successfully disabled

You may now restart NPS
Results
The script disables cryptography support by setting the enable_crypto_srd_v1

variable to false in the /nz/data/config/postgresql.conf file. You must stop and
restart the NPS software for the change to take effect and to fully disable the
enhanced cryptography support.
Optionally, you can verify that the support is disabled by running the following
command to confirm that the variable has a value of false:
[nz@nzhost1 ~]$ grep crypto /nz/data/postgresql.conf
# enable (crypto) keys
enable_crypto_std_v1 = false
If the value is true, run the nzconfigcrypto -disable command again to disable
the support.
You should verify that the host key value for your system is still correct. The
enhanced crypto support is disabled, but the command does not change the host
key from its current value, which is the AES_256 key that you used for the
enhanced crypto support. To display the current key, connect to a database and run
the following command:
NEWDB.MYUSR(MYUSR)=> SHOW SYSTEM DEFAULT HOSTKEY;
NOTICE: ’HOST KEY’ = ’KS1.KEY1’
SHOW VARIABLE
If you want to change the host key to another value, use the SET SYSTEM
DEFAULT HOSTKEY TO name command.

Enhanced cryptography troubleshooting
After you use the nzconfigcrypto command to enable enhanced cryptography
support on your IBM Netezza system, you could encounter errors when starting
the NPS software.
Table 10-1. Troubleshooting nzstart errors
Message Problem Corrective Action
nzstart: Error: Hostkey is An administrator might have If you know the correct host
not set. Cannot start the changed the host key to one key to use, use the
system in SP800-131a mode that is not compliant with nzconfigcrypto -HK
the enhanced crypto support keystore.keyname -enable
before stopping the NPS command to set the host key
software. and then re-run the nzstart
command. Otherwise, you
can use this process:
1. Use the nzconfigcrypto
-disable command to
disable crypto support.
2. Restart NPS by using the
nzstart command.
3. Connect to a Netezza
database and use the
SHOW SYSTEM
DEFAULT HOSTKEY
command to see the
current host key. You can
also view the current
keystores and keys to
locate the host key, or
you can create a new
AES-256 host key for the
crypto support.
4. Close the database
connection and as the nz
user, use the
nzconfigcrypto -HK
keystore.keyname -enable
command to enable
crypto support with the
correct host key.
5. Stop and restart the NPS
software using the nzstop
and nzstart commands.
nzstart: Error: Connection Starting NPS in crypto mode See “Updating connections
Authentication types MD5 with MD5/CRYPT for crypto support” on page
and CRYPT are not allowed authentication type. 10-5.
in SP800-131a mode. MD5/CRYPT authentication
type is not allowed in crypto
mode.

Table 10-1. Troubleshooting nzstart errors (continued)
nzstart: Error: Please Starting NPS in crypto mode 1. Use the nzconfigcrypto
drop the current LDAP without dropping old LDAP -disable command to
configuration and restart connection. Old LDAP disable crypto support.
NPS with a new LDAP connection/configuration is
configuration. not compatible with crypto
nzstart command.
mode and must be dropped
and recreated. 3. Connect to a Netezza
database and drop the
current LDAP
authentication by using
the SET
AUTHENTICATION
LOCAL command.
4. Use the nzconfigcrypto
-enable command to
enable crypto support.
6. Connect to a Netezza
database and restore the
LDAP configuration by
using the SET
AUTHENTICATION
LDAP command

Table 10-1. Troubleshooting nzstart errors (continued)
nzstart: Error: The DSA Starting NPS in crypto mode 1. Use the nzconfigcrypto
key used for audit signing but the current audit history -disable command to
must be of type configuration is not digitally disable crypto support.
DSA_KEYPAIR_2048 in signed and compatible with
SP800-131a mode. crypto mode. An
nzstart command.
administrator could have
changed the history 3. Connect to a Netezza
configuration to one that is database and use the
not digitally signed with a SHOW HISTORY
key of type CONFIGURATION
DSA_KEYPAIR_2048. After command to review the
stopping the NPS software, current configuration.
the NPS software could not Look for values in the
be restarted with the new KEYSTORE_NAME and
audit configuration. KEY_ALIAS fields, and
use the SHOW
KEYSTORE
<keystore_name>
VERBOSE command to
determine whether the
host key is of type
DSA_KEYPAIR_2048.
4. If the key is of a different
type, you can change the
audit history
configuration to specify a
different
DSA_KEYPAIR_2048 key.
To alter the current
history configuration, you
must set the history
configuration to another
value, stop and restart
the NPS software, then
re-connect to a database
and use the ALTER
HISTORY
CONFIGURATION
<name> KEY
<keystore.keyname>
command. You can then
set the history
configuration to the
altered audit
configuration.
5. Close the database
connection and as the nz
user, use the
nzconfigcrypto -HK
keystore.keyname -enable
command to enable
crypto support.

Downgrading an SP 800-131a crypto NPS system
If you must downgrade the NPS software on your system, and you configured the
system to use SP 800-131a crypto support, review the following steps and
precautions to ensure a successful downgrade.
Downgrades are typically performed by IBM Netezza Support in cases where there
is a need to return to a release that ran previously on your IBM Netezza appliance.
If you are downgrading to a release before 7.1, those releases do not support the
enhanced cryptography for SP 800-131a compliance. The nzupgrade command,
which upgrades and downgrades the current release on the Netezza system,
checks for enhanced crypto support and returns an error if the command detects
any crypto-related objects that are not supported on the release to which you are
downgrading.
To clear your system of the crypto-related objects and settings before a downgrade,
do the following:
v Run the nzconfigcrypto -disable command to disable the crypto support. Stop
and restart the NPS software using the nzstop and nzstart commands to start
the system in a non-SP 800-131a mode.
v Identify and drop any keys that are defined with DSA_KEYPAIR_2048
authentication type. You can use the SHOW KEYSTORE ALL VERBOSE
command to list all the keys. Identify the keys that are of key type
DSA_KEYPAIR_2048 and use the DROP CRYPTO KEY <keystore>.<keyname>
command to drop each of those keys.
v Identify and drop any audit history configurations that are digitally signed with
a DSA_KEYPAIR_2048 key. You can use the SHOW HISTORY
CONFIGURATION ALL command to list all the configurations. Look for audit
history configuration that are digitally signed with a DSA_KEYPAIR_2048 key,
and use the DROP HISTORY CONFIGURATION <histname> command to
remove those configurations. If you loaded audit history data using this stronger
DSA_KEYPAIR_2048 key, that audit database is not viewable after the
downgrade to a release that does not support SP 800-131a cryptography.
v If your system uses LDAP authentication for the Netezza database user
accounts, use the SET AUTHENTICATION LOCAL command to drop the
current LDAP configuration, which is encrypted using the SP 800-131a enhanced
support. You can then re-enable LDAP authentication, which will use the current
host key and authentication levels, and the downgrade will proceed.
v If your system uses Kerberos authentication for the Netezza database user
accounts, use the SET AUTHENTICATION LOCAL command to disable
Kerberos support. NPS releases before 7.1 do not support Kerberos
authentication.
After you make these changes on your system, you can re-try the nzupgrade
command to proceed with the downgrade to the previous release.

Chapter 11. Security and access control
This section describes how to manage IBM Netezza database user accounts, and
how to apply administrative and object permissions that allow users access to
databases and capabilities. This section also describes user session controls such as
row limits and priority that help to control database user impacts on system
performance.
You can control access to the Netezza system itself by placing the appliance in a
secured location such as a data center. You can control access through the network
to your Netezza appliance by managing the Linux user accounts that can log in to
the operating system. You control access to the Netezza database, objects, and tasks
on the system by managing the Netezza database user accounts that can establish
SQL connections to the system.
Note: Linux users can log in to the Netezza server at the operating system level,
but they cannot access the Netezza database by SQL. If some of your users require
Linux accounts to manage the Netezza system and database accounts for SQL
access, you can use identical names and passwords for the two accounts to ease
management. Throughout this section, any references to users and groups imply
Netezza database user accounts, unless otherwise specified.
Related concepts:
“Managing access to a history database” on page 14-9
“Resource minimums and maximums” on page 15-10
Related reference:
Appendix B, “Linux host administration reference,” on page B-1
The IBM Netezza appliance has a host server that runs the Linux operating system.
Netezza database users and user groups

To access the IBM Netezza database, users must have Netezza database user
accounts.
When a user accesses a Netezza database, by means either of a nzsql

command-line session or of another SQL interface, the database account determines
the access privileges to database objects and the administrative permissions to
various tasks and capabilities.
You can assign privileges to a specific database user account as needed. If you
have several users who require similar privileges, you can create user groups to
organize those users and thus simplify access management.
Note: A Netezza group can be one or both of the following types:

User group
A group with one or more members is a user group. Each member of a user
group inherits its privileges and other settings, with the exception of its
resource minimum, resource maximum, and job maximum settings. User
groups are used to simplify access management.

Resource group
A group that specifies a nonzero minimum resource percentage is a resource
group. Each resource group also specifies a resource maximum and job
maximum, either explicitly or by default. These three settings are called the
group's resource settings. Each user is assigned to exactly one resource
group. Resource groups are used for workload management.
A group can be both a user group and a resource group, but its user group and
resource group aspects, including user group membership and resource group
assignment, are completely separate:
v A user might be assigned to a resource group but not be a member of that
group. That user is unaffected by any privileges or settings of that group, except
for the resource settings.
v A user might be a member of a user group but be assigned to a different
resource group. That user is unaffected by the user group's resource settings.
If a user is a member of more than one group, the user inherits the union of all
privileges from those groups, plus any privileges that were assigned to the user
account specifically. If you remove a user from a user group, the privileges that
were provided by that group are removed from the user. For example, if you
remove a user from a group that has the Create Table privilege, the user loses that
privilege unless the user is a member of another group that grants that privilege or
the user account was granted that privilege directly.
As a best practice, use groups to manage the privileges of your database users
rather than managing user accounts individually. Groups are an efficient and a
time-saving way to manage privileges, even if a group has only one member. Over
time, you typically add new users, drop existing users, and change user privileges
as roles evolve. New Netezza software releases often add new privileges that you
might need to apply to your users. Rather than manage these changes on an
account-by-account basis, manage the privileges with groups and group
membership.
You can create and manage Netezza database accounts and groups by using any
combination of the following methods:
v Netezza SQL commands, which are the most commonly used methods
v Netezza Performance Portal, which provides a web browser interface for
managing users, groups, and privileges
v NzAdmin tool, which provides a windows interface for managing users, groups,
and privileges
This section describes how to manage users and groups by using the SQL
commands. The online help for the Netezza Performance Portal and NzAdmin
interfaces provide more information about how to manage users and groups
through those interfaces.
Related concepts:
Chapter 15, “Workload management,” on page 15-1
The workload of an IBM Netezza system consists of user-initiated jobs such as SQL
queries, administration tasks, backups, and data loads, and system-initiated jobs
such as regenerations and rollbacks. Workload management (WLM) is the process
of assessing a system's workload and allocating the resources used to process that
workload.
Related reference:

“Linux accounts” on page B-1
You can create Linux user accounts to manage user access to the IBM Netezza
system.
Access model
Develop an access model for your IBM Netezza appliance. An access model is a
profile of the users who require access to the Netezza system and the permissions
or tasks that they need.
Typically, an access model begins modestly, with a few users or groups, but it often
grows and evolves as new users are added to the system. The model defines the
users, their roles, and the types of tasks that they perform, or the databases to
which they require access.
Access models can vary widely for each company and environment. As a basic
example, you can develop an access model that defines three initial groups of
database users:
Administrators
Users who are responsible for managing various tasks and services. They
might manage specific databases, manage user access, create databases,
load data, or back up and restore databases.
General database users
Users who are allowed access to one or more databases for querying, and
who might or might not have access to manage objects in the database.
These users might also have lower priority for their work.
Power database users
Users who require access to critical databases and who might use more
complex SQL queries than the general users. These users might require
higher priority for their work. They might also have permissions for tasks
such as creating database objects, running user-defined objects (UDXs), or
loading data.
The access model serves as a template for the users and groups that you create,
and also provides a map of access permission needs. By creating Netezza database
groups to represent these roles or permission sets, you can easily assign users to
the groups to inherit the various permissions, you can change all the users in a
role by changing only the group permissions, and move users from one role to
another by changing their groups, or by adding them to groups that control those
permissions.
Default Netezza groups and users

The IBM Netezza system has a default Netezza database user named admin and a
group named public.
The admin database user is the database super-user account. The admin user has
all privileges and access to all database objects. Therefore, use that account
sparingly and only for the most critical of tasks. For example, you might use the
admin account to start creating a few Netezza users and groups; afterward, you
can use another administrative-level account for tasks such as user management,
database maintenance, and object creation and management.
The admin user account has the following characteristics:

v The default password is password.
Chapter 11. Security and access control 11-3

Important: Be sure to change the password as soon as possible for security.
v You cannot delete the admin user.
v You cannot change the name or the owner of the admin account.
v Unlike all other objects, the admin user has no owner.
v The admin user is not included in a list of users, except in the administrator's
list.
Note: The admin user also has special workload management priority. Because of
the presumed critical nature of the work, it automatically takes half of the system
resources, which can impact other concurrent users and work.
The public group is the default user group for all Netezza database users. All users
are automatically added as members of this group and cannot be removed from
this group. The admin user is the owner of the public group. You can use the
public group to set the default set of permissions for all Netezza user accounts.
You cannot change the name or the ownership of the group.
Related concepts:
“Resource allocations for the admin user” on page 15-15
The admin user account is treated as if it belongs to a resource group that receives
50% of net system resources. Consequently, the admin user has a unique and
powerful impact on resource availability.
“Security model” on page 11-9
The IBM Netezza security model is a combination of administrator privileges that
are granted to users and groups, plus object privileges that are associated with
specific objects (for example, table xyz) and classes of objects (for example, all
tables).
User authentication method

By default, when you create an IBM Netezza database user, you specify a
password for that account. The password is saved with the user account in the
Netezza database. When the user logs in to the database or runs a command and
specifies the Netezza user account and password, Netezza verifies that password
against the string that is stored in the Netezza database. This method is called local
authentication. The admin database user always uses local authentication.
Netezza also supports the option to authenticate database users (except admin) by
using one of the following trusted authentication sources:
v You can use LDAP authentication to authenticate database users, manage
passwords, and manage account activations and deactivations. The Netezza
system then uses a Pluggable Authentication Module (PAM) to authenticate
users on the LDAP name server. Microsoft Active Directory conforms to the
LDAP protocol, so it can be treated like an LDAP server for the purposes of
LDAP authentication.
v You can use Kerberos authentication to authenticate database users, manage
passwords, and manage account activations and deactivations. The Netezza
system uses Kerberos configuration files to connect with the Kerberos key
distribution center (KDC) to authenticate database users before they are allowed
to connect to a database.
The Netezza host supports LDAP or Kerberos authentication for database user
logins only, not for operating system logins on the host. You cannot use both
LDAP and Kerberos to authenticate database users on the Netezza appliance.

If you use LDAP or Kerberos authentication, you do not have to specify a
password for the database user accounts when you create them, but it is a good
practice to specify one. If you switch to local authentication, a database user cannot
connect to a database if their password is null.
Authentication is a system-wide setting, but if you choose LDAP or Kerberos

authentication, you can create database users who are locally authenticated as
exceptions.
Related concepts:
Password content controls and reuse

The IBM Netezza system uses pam_cracklib utilities to enforce database user
account passwords, which provides a strong set of rules to help users avoid
weaker or more easily guessed passwords.
You can configure system-wide policies for the minimum requirements for
password length and content. These system-wide controls do not apply to the
default admin database user, only to the other database user accounts that you
create. You can also tailor the pam_cracklib dictionary to establish policies within
your Netezza environment. The pam_cracklib dictionary does not allow common
words, passwords that are based on user names, password reversal, and other
shortcuts that can make passwords more vulnerable to hacking.
You can also configure the Netezza system to check for and enforce new
passwords that do not match a specified number of previous passwords for that
account.
Password content controls

For your database user accounts, you can specify requirements such as length and
character formats to ensure that your users select passwords that meet your
security policies. The system calculates and enforces the strength of a password by
using a credit-based algorithm that evaluates the complexity of the characters that
are used in the password and its length.
To set the content requirements for passwords, use the SET SYSTEM DEFAULT
SQL command as follows:
SYSTEM.ADMIN(ADMIN)=> SET SYSTEM DEFAULT PASSWORDPOLICY TO conf;
SET VARIABLE
The conf value is a string of parameters that specify the content requirements and
restrictions:
minlen
Specifies the minimum length in characters (after it deducts any credits) for
a password. The default is the minimum value of 6; that is, even with
credits, you cannot specify a password that is less than six characters. If
you specify 10, for example, the user must specify at least nine lowercase
characters (with the lowercase letter default credit of 1) to meet the
minimum length criteria.
Note: There is a relationship between the minimum length of a password

and its strength (that is, the use of mixed-case letters, digits, and
non-alphanumeric characters that increase the complexity of the password
string). If a user specifies only lowercase letters, which are considered
weak passwords, the minimum length of the password is minlen. If the
user includes uppercase and lowercase letters, digits, and symbols, the
minlen requirement can be reduced with credits for the number and type
of those additional characters. You can also use the credit values to require
the presence of a minimum number of characters in the password.
dcredit
Specifies the maximum credit for including digits in the password. The
default is one credit; if you specify a credit of 3, for example, the user
receives one credit per digit up to the maximum of three credits to reduce
the minlen requirement. If you specify a negative value such as -2, your
users must specify at least two digits in their password.
ucredit
Specifies the maximum credit for including uppercase letters in the
password. The default is one credit; if you specify a credit of 2, for
example, the user receives one credit per uppercase letter up to the
maximum of two credits to reduce the minlen requirement. If you specify a
negative value such as -1, your users must specify at least one uppercase
letter in their password.
lcredit Specifies the maximum credit for including lowercase letters in the
password. The default is one credit; if you specify a credit of 2, for
example, the user receives one credit per lowercase letter up to the
maximum of two credits to reduce the minlen requirement. If you specify a
negative value such as -1, your users must specify at least one lowercase
letter in their password.
ocredit
Specifies the maximum credit for including non-alphanumeric characters
(often referred to as symbols such as #, &, or *) in the password. The
default is one credit; if you specify a credit of 1, for example, the user
receives one credit per non-alphanumeric character up to the maximum of
one credit to reduce the minlen requirement. If you specify a negative
value such as -2, your users must specify at least two non-alphanumeric
characters in their password.
For example, the following command specifies that the minimum length of a weak
password is 10, and it must contain at least one uppercase letter. The presence of at
least one symbol or digit allows for a credit of 1 each to reduce the minimum
length of the password:
SYSTEM.ADMIN(ADMIN)=> SET SYSTEM DEFAULT PASSWORDPOLICY TO ’minlen=10,
lcredit=0 ucredit=-1 dcredit=-1 ocredit=1’;
SET VARIABLE
As another example, the following command specifies that the minimum length of
a weak password is 8, it must contain at least two digits and one symbol; and the
presence of lowercase characters offers no credit to reduce the minimum password
length:
SYSTEM.ADMIN(ADMIN)=> SET SYSTEM DEFAULT PASSWORDPOLICY TO ’minlen=8,
lcredit=0 dcredit=-2 ocredit=-1’;
SET VARIABLE
The pam_cracklib dictionary

In the IBM Netezza implementation, the pam_cracklib dictionary is in the
/usr/lib64 directory. You cannot change the dictpath configuration setting to point
to a different dictionary file with the Netezza implementation. However, you can

customize the dictionary file (cracklib_dict.pwd) for your environment and
policies. For details about customizing the dictionary files, see the Red Hat 5.0
documentation.
Password history and reuse

A database user can change an account password by issuing the ALTER
PASSWORD SQL command or by using tools such as NzAdmin or Netezza
Performance Portal. By default, the system does not ensure that a new account
password is different from any previous passwords for that account. However, the
system keeps an encrypted history of all passwords for each account. If you have
security policies that specify when a password can be reused, you can configure
the system to enforce that policy.
To do this:
2. Open the /nz/data/postgresql.conf file in any text editor.
3. Search for a entry similar to password_history=n in the file.
v If the file already contains such an entry, ensure that the entry is not
commented out (that is, that # is not the first character in the line) and that
the specified value is a positive integer.
v If the file does not already contain such an entry, create one. The value n
must be greater than or equal to 0.
The specified integer determines the number of the most recent passwords that
cannot be reused.
Note: Be careful not to change other entries, because doing so can have a
negative impact on database operation.
4. Save and exit the postgresql.conf file.
5. Issue the nzstop command to stop the system.
6. Issue the nzstart command to restart the system. This usually requires several
minutes to complete.
After the system restarts and is online, any request to change an account password
will be checked to ensure that the new password has not recently been used for
that account.
Create Netezza database users

To create an IBM Netezza database user, log in to the Netezza database by using
an account that has Create User administrative privilege. For a new Netezza
system, you would most likely log in as admin and connect to the system database
to create users. For example, the following command adds a user to a system that
uses local authentication:
SYSTEM.ADMIN(ADMIN)=> CREATE USER dlee WITH PASSWORD ’jw8s0F4’;
CREATE USER
If you are using LDAP or Kerberos authentication, you do not have to specify a
password for the account. The CREATE USER command has a number of options
that you can use to specify timeout options, account expirations, rowset limits (the
maximum number of rows a query can return), and priority for the user session
and queries. The resulting user account is owned by the user who created the
account.

When you create users and groups, you can also specify session access time limits.
The access time limits specify when users can start database sessions. User might
be permitted to start sessions at any time on any day, or they might be given
restricted access to certain days or certain hours of the day. If a user attempts to
start a session during a time when they do not have access, the system displays an
error message that they are outside their access time limits. Also, if a user attempts
to run an nz command that creates a database session, the command also returns
the error if the user is not within the allowed access time window. For more
information, see the access time information in the IBM Netezza Advanced Security
Administrator's Guide.
Remember: Session settings such as access time restrictions, session timeouts,

priority, rowset limits, and password expiration, can be set on a per-user,
per-group, and in some cases a system-wide level. The Netezza system checks the
settings for a user first to find the values to use; if not set for the user, the system
uses the most restrictive setting for any of the groups to which the user belongs; if
not set for the group, the system uses the system-wide settings.
Alter Netezza database users

You can use the ALTER USER command to change the name, password, expiration,
owner, and session settings of an existing database user account.
You can also unlock an account if it was configured to lock after a specified
number of failed login attempts. To change the account, log in to the IBM Netezza
database by using an account that has Alter administrative privilege. For example,
the following command assigns a user to the group named silver:
SYSTEM.ADMIN(ADMIN)=> ALTER USER dlee WITH IN RESOURCEGROUP silver;
ALTER USER
Delete Netezza database users

You can use the DROP USER command to delete or drop a database user account.
To drop the account, log in to the IBM Netezza database by using an account that
has Drop administrative privilege. For example, the following command drops the
dlee user account:
SYSTEM.ADMIN(ADMIN)=> DROP USER dlee;
DROP USER
The command displays an error if the account that you want to drop owns objects;
you must change the ownership of those objects or drop those objects before you
can drop the user.
Create Netezza database groups

To create an IBM Netezza database group, log in to the Netezza database by using
an account that has Create Group administrative privilege. The following are some
example commands:
SYSTEM.ADMIN(ADMIN)=> CREATE GROUP engineering;
CREATE GROUP
SYSTEM.ADMIN(ADMIN)=> CREATE GROUP qa WITH USER dlee;

CREATE GROUP
SYSTEM.ADMIN(ADMIN)=> CREATE GROUP execs WITH MAXPRIORITY CRITICAL;

CREATE GROUP

The CREATE GROUP command also includes options that you can use to specify
timeout options, rowset limits (the maximum number of rows a query can return),
account expiration, and priority for the sessions and queries of the group members.
The resulting group is owned by the user who created the group.
Remember: Session settings such as timeouts, priority, expiration, and rowset

limits, can be set on a per-user, per-group, and system-wide level. The Netezza
system checks the settings for a user first to find the values to use; if not set for the
user, the system uses the group settings (the most restrictive of the settings for all
of the groups to which the user belongs); if not set for any group, the system uses
the system-wide settings.
Alter Netezza database groups

You can use the ALTER GROUP command to change the name, membership,
session settings, account expiration, or owner of an existing database group.
To change the group, log in to the IBM Netezza database by using an account that
has Alter administrative privilege. For example, the following command removes
the member dlee from the group named qa:
SYSTEM.ADMIN(ADMIN)=> ALTER GROUP qa DROP USER dlee;
ALTER GROUP
Delete Netezza database groups

You can use the DROP GROUP command to delete or drop a database group.
To drop the group, log in to the IBM Netezza database by using an account that
has Drop administrative privilege. For example, the following command drops the
qa group:
SYSTEM.ADMIN(ADMIN)=> DROP GROUP qa;
DROP GROUP
Security model
The IBM Netezza security model is a combination of administrator privileges that
are granted to users and groups, plus object privileges that are associated with
specific objects (for example, table xyz) and classes of objects (for example, all
tables).
As part of the model, any privilege that is granted to a database group is

automatically granted to (that is, inherited by) all the users who are members of
that group. Privileges are additive, which means that you cannot remove a
privilege from a user who is granted that privilege as a consequence of being a
member of a group.
Each object has an owner. Individual owners automatically have full access to their
objects and do not require individual object privileges to manage them. The
database owner, in addition, has full access to all objects within the database. The
admin user owns all predefined objects and has full access to all administrative
permissions and objects. For systems that support multiple schemas in a database,
the schema owner has full access to all objects within the schema.
Related concepts:
“Default Netezza groups and users” on page 11-3
group named public.

Administrator privileges
Administrator privileges give users and groups permission to execute global
operations and to create objects.
When you grant a privilege, the user you grant the privilege to cannot pass that
privilege onto another user by default. If you want to allow the user to grant the
privilege to another user, include the WITH GRANT OPTION when you grant the
privilege.
The following table describes the administrator privileges. The words in brackets
are optional.
Table 11-1. Administrator privileges
Privilege Description
Backup Allows the user to perform backups. The user can run the nzbackup
command.
[Create] Aggregate Allows the user to create user-defined aggregates (UDAs) and to
operate on existing UDAs.
[Create] Database Allows the user to create databases. Permission to operate on
existing databases is controlled by object privileges.
[Create] External Allows the user to create external tables. Permission to operate on
Table existing tables is controlled by object privileges.
[Create] Function Allows the user to create user-defined functions (UDFs) and to
operate on existing UDFs.
[Create] Group Allows the user to create groups. Permission to operate on existing
groups is controlled by object privileges.
[Create] Index For system use only. Users cannot create indexes.
[Create] Library Allows the user to create user-defined shared libraries. Permission
to operate on existing shared libraries.
[Create] Materialized Allows the user to create materialized views.
View
[Create] Procedure Allows the user to create stored procedures.
[Create] Scheduler Allows the user to create scheduler rules and to show, drop, alter,
Rule or set (deactivate or reactivate) any rule, regardless of who created
or owns it.
[Create] Sequence Allows the user to create database sequences.
[Create] Synonym Allows the user to create synonyms.
[Create] Table Allows the user to create tables. Permission to operate on existing
tables is controlled by object privileges.
[Create] Temp Table Allows the user to create temporary tables. Permission to operate
on existing tables is controlled by object privileges.
[Create] User Allows the user to create users. Permission to operate on existing
users is controlled by object privileges.
[Create] View Allows the user to create views. Permission to operate on existing
views is controlled by object privileges.
[Manage] Hardware Allows the user to do the following hardware-related operations:
view hardware status, manage SPUs, manage topology and
mirroring, and run diagnostic tests. The user can run the nzds and
nzhw commands.

Table 11-1. Administrator privileges (continued)
[Manage] Security Allows the user to run commands and operations that relate to the
following advanced security options such as: managing and
configuring history databases; managing multi-level security objects
and specifying security for users and groups; managing database
key stores and keys and key stores for the digital signing of audit
data.
[Manage] System Allows the user to do the following management operations: start,
stop, pause, or resume the system, abort sessions, and view the
distribution map, system statistics, logs, and plan files from active
query or query history lists. The user can use the following
commands: nzsystem, nzstate, nzstats, and nzsession priority.
Restore Allows the user to restore the system. The user can run the
nzrestore command.
Unfence Allows the user to create an unfenced user-defined function (UDF)
or user-defined aggregate (UDA), or to unfence an existing fenced
UDF or UDA if the user has permission to create or alter it. For
more information, see the IBM Netezza User-Defined Functions
Developer's Guide.
Object privileges
Object privileges apply to individual object instances (a specific user or a single
database).
Because object privileges take effect after an object is created, you can only change
privileges on existing objects. Like administrator privileges, object privileges are
granted to users and groups. But where administrator privileges apply to the
system as a whole and are far reaching, object privileges are more narrow in scope.
When an object is created, there are no object privileges that are associated with it.
Instead, the user who creates the object becomes the object owner. Initially, only
the object creator, the schema owner (if the object is defined in a schema), the
database owner, and the admin user can view and manipulate the object. For other
users to gain access to the object, either the owner, database owner, schema owner,
or the admin user must grant privileges to it.
The following table describes the list of available object privileges. As with
administrator privileges, specifying the with grant option allows a user to grant
the privilege to others.
Table 11-2. Object privileges
Abort Allows the user to abort sessions. Applies to groups and users. For more
information, see “Abort sessions or transactions” on page 12-24.
All Allows the user to have all the object privileges.
Alter Allows the user to modify object attributes. Applies to all objects.
Delete Allows the user to delete table rows. Applies only to tables.
Drop Allows the user to drop all objects.
Execute Allows the user to execute UDFs and UDAs in SQL queries.
Execute Allows the user to change the name of the current user of their session.
As

Table 11-2. Object privileges (continued)
GenStats Allows the user to generate statistics on tables or databases. The user can run
the GENERATE STATISTICS command.
Groom Allows the user to do general housekeeping and cleanup operations on tables
by using the GROOM TABLE command. The GROOM TABLE command runs
reclaim operations to remove deleted rows and also reorganizes tables that are
based on the clustered base table's organizing keys.
Insert Allows the user to insert rows into a table. Applies only to tables.
Label Allows the user to view the label column.
Access
Label Allows the user to update a label to a less restrictive value.
Expand
Label Allows the user to update a label to a more restrictive value.
Restrict
List Allows the user to display an object name, either in a list or in another
manner. Applies to all objects.
Select Allows the user to select (or query) rows within a table. Applies to tables and
views.
Truncate Allows the user to delete all rows from a table. Applies only to tables.
Update Allows the user to modify table rows, such as changing field values or
changing the next value of a sequence. Applies to tables only.
Object privileges by class

Use the IBM Netezza system to define privileges on classes of objects (such as
table, view). These privileges allow access to all objects of the class that exist now
or will exist in the future. The list of classes available for use in a Grant or Revoke
statement are:
DATABASE, SCHEMA, GROUP, SEQUENCE, SYNONYM, TABLE, EXTERNAL TABLE, FUNCTION,
AGGREGATE, PROCEDURE, USER, VIEW, MATERIALIZED VIEW, LIBRARY
Scope of object privileges

All objects are either global (for example, a database, user, or group) or local (that
is, they exist within a database; for example, a table or view). You can assign an
object privilege so that it applies globally (to all objects within all databases) or
locally (to a single object within a single database).
The following example starts as a local definition and moves to a more global
definition.
If you use SQL commands to manage account permissions, the database to which
you are connected has meaning when you issue a GRANT command. If you are
connected to the system database (this database has the name SYSTEM), the
privilege applies to all databases. If you are connected to a specific database, the
privilege applies only within that database.
Starting in release 7.0.3, you can use a fully-qualified object notation to set the
scope of object privileges from any database. The fully-qualified object notation has
the format:
database.schema.object

where:
database
A specific database name or the keyword ALL to grant the privilege across all
databases.
schema
A specific schema name or the keyword ALL for all schemas in the specified
database value.
object
An object class such as TABLE, VIEW, and so on, or a specific object name.
For example, to assign a privilege to an object in a particular database and a

particular schema, sign on to the database and grant the privilege on the object to
a user or group. For this type of privilege, the object must exist, and this privilege
overrides any other defined privilege.
MYDB.SCH1(USER1)=> GRANT LIST ON testdb TO user1;
Similarly, you could sign into any database to which you have access and grant the
permission using a fully qualified name:
DEV.TEST(USER2)=> GRANT LIST ON mydb.sch1.testdb TO user1;
To assign a privilege to a class of objects in a particular database and a particular

schema, sign on to the database and grant the privilege on the class to a user or
group. When you assign a privilege to a class (such as table), the system allows the
user or group that privilege on all the objects of that class whether the object
existed at the time of the grant.
MYDB.SCH1(USER1)=> GRANT SELECT ON TABLE TO user1;
DEV.TEST(USER2)=> GRANT SELECT ON MYDB.ALL.TABLE TO user1;
To assign a privilege to a class of objects in all databases, sign on to the system

database and grant the privilege on the class to a user or group. When you define
privileges for user object classes within the system database, the system assumes
you are requesting a global scope.
SYSTEM.ADMIN(ADMIN)=> GRANT SELECT ON TABLE TO user1;
DEV.TEST(USER2)=> GRANT SELECT ON ALL.ALL.TABLE TO user1;
Note: When you use the GRANT command to grant privileges at a database level
and at the system level, the grant issued for the database overrides the grant
issued at the system level.
Privilege Precedence: IBM Netezza uses the following order of precedence for
permissions:
1. Privileges granted on a particular object within a particular database and a
particular schema, for systems that support multiple schemas
2. Privileges granted on an object class within a particular database and a
particular schema, for systems that support multiple schemas
3. Privileges granted on a particular object within all schemas of a particular
database

4. Privileges granted on an object class within all schemas of a particular database
5. Privileges granted on an object within the system database
6. Privileges granted on an object class within the system database
You can assign multiple privileges for the same object for the same user. The
Netezza system uses the rules of precedence to determine which privileges to use.
For example, you can grant users privileges on a global level, but user privileges
on a specific object or database level override the global permissions. For example,
assume the following three GRANT commands:
Within the system database, enter:

system.admin(admin)=> GRANT SELECT,INSERT,UPDATE,DELETE,TRUNCATE ON
TABLE TO user1
Within the dev database, enter:

dev.schema(admin)=> GRANT SELECT,INSERT,UPDATE ON TABLE TO user1
Within the dev database, enter:

dev.schema(admin)=> GRANT SELECT, LOAD ON customer TO user1
By using these grant statements and assuming that customer is a user table, user1
has the following permissions:
v With the first GRANT command, user1 has global permissions to SELECT, INSERT,
UPDATE, DELETE, or TRUNCATE any table in any database.
v The second GRANT command restricts user1 permissions specifically on the dev
database. When user1 connects to dev, user1 can run only SELECT, INSERT, or
UPDATE operations on tables within that database.
v The third GRANT command overrides privileges for user1 on the customer table
within the dev database. As a result of this command, the only actions that user1
can perform on the customer table in the dev database are SELECT and LOAD.
The following table lists the slash commands that display the privileges for users
and groups:
Table 11-3. Slash commands to display privileges
Command Description
\dg List groups (both user and resource groups) except _ADMIN_.
\dG List user groups and their members.
\dp <user> List the privileges that were granted to a user either directly or
by membership in a user group.
\dpg <group> List the privileges that were granted to a user group.
\dpu <user> List the privileges that were granted to a user directly and not
by membership in a user group.
\du List users.
\dU List users who are members of at least one user group and the
groups of which each is a member.
When you revoke privileges, make sure you sign on to the same database (and, for
a multiple schema system, the same schema) where you granted the privileges, or
use the fully qualified name forms that match the locations in which you granted
the privileges. Then, you can use these slash commands to verify the results.

Revoke privileges
You can revoke administrative and object privileges by using the REVOKE
command.
When you revoke a privilege from a group, all the members of that group lose the
privilege unless they have the privilege from membership in another group or
through their user account.
For example, to revoke the Insert privilege for the group public on the table films,
enter:
SYSTEM.ADMIN(ADMIN)=> REVOKE INSERT ON films FROM PUBLIC;
REVOKE
Privileges by object
A privilege applies only to the object for which it was granted. For example, when
you grant a user the Drop privilege for a database, that privilege does not apply to
any of the objects within that database, but only to the database itself.
The following table describes the list of privileges by object.

Table 11-4. Privileges by object
Object Privilege Description
Aggregate Alter Change the name or ownership of a UDA.
Drop Drop a UDA.
Execute Execute a UDA in a query.
List List UDAs.
Database Alter Change the name of a database.
Drop Drop a database.
List Connect to and display a database.
Function Alter Change the name or ownership of a function.
Drop Drop a function.
Execute Execute a function in a query.
List List functions.
Group Abort Abort a session.
Alter Change the name of a group.
Drop Drop a group.
List List groups.
Procedure Alter Change the name or ownership of a stored procedure.
Drop Drop a procedure.
Execute Execute a procedure in a query.
List List procedures.
Schema Alter Change the name or ownership of a schema.
Drop Drop a schema.
List List schemas.

Table 11-4. Privileges by object (continued)
Object Privilege Description
System table Delete Delete rows from a system table.
Insert Insert rows into a system table.
List View a system table.
Select Select rows in a system table.
Update Update rows from the system table.
Sequence Alter Alter a sequence.
Drop Drop a sequence.
List List a sequence.
Select Select a sequence.
Update Use next value of a sequence.
System view List See a system view.
Select Select rows in a system view.
Synonym Alter Alter a synonym.
Delete Delete rows (if the synonym represents a table).
Drop Drop a synonym.
Insert Insert rows (if the synonym represents a table).
List List a synonym.
Select Select a synonym.
Update Update rows (if the synonym represents a table).
Table or Alter Change the name of a table.
external
Delete Delete rows from a table.
table
Drop Drop a table.
GenStats Generate statistics for the table.
Insert Insert rows into a table.
List View a table.
Select Select rows in a table.
Truncate Delete all rows from a table.
Update Update rows from the table.
User Abort Abort a session or a transaction.
Alter Change the name of a user.
Drop Drop a user.
List Display a user.
View or Alter Alter a view.
materialized
Drop Drop a view.
view
List See a view.
Select Select rows in a view.

Inherited connection privileges
For Netezza systems that support multiple schemas in a database, a user who is
granted access to a database automatically inherits access to the default schema of
that database.
There is an exception on systems where the enable_user_schema setting is TRUE.

In that case, the user always connects to a schema that matches their user name,
not the database default schema.
If you change the default schema for a database, the user automatically inherits
access to the new default schema and loses access to the previous default. If a user
requires access to the previous default schema, that user must be explicitly granted
access to that schema.
Indirect object privileges

The IBM Netezza system controls some objects that are indirectly based on the
privileges that are associated with the object. Objects in this category include user
sessions, transactions, load sessions, and statistics.
The following table describes the rules for each of these objects.
Table 11-5. Indirect object privileges
Object type Access rule
Client session Users can see a session's user name and query if that user object is
viewable. Users can see the connected database name if that
database object is viewable. Users must have the Abort privilege on
another user or be the system administrator to abort another user's
session or transaction.
Database statistic The system displays operational statistics for database-related objects
if the corresponding object is viewable. For example, you can see the
disk space statistics for a table if you can see the table.
Related tasks:
“Viewing record distribution” on page 12-9
Functions that are always available

Some functions are available to all users and cannot be altered through access
controls. These functions include:
Log on attempt
Anyone can try to log on.
List client sessions
See restrictions in Table 11-5.
Creating an administrative user group

About this task
As described in “Default Netezza groups and users” on page 11-3, the default
admin user account is a powerful database super-user account. Use that account
rarely, such as for documented maintenance or administrative tasks, or when you
first set up an IBM Netezza system.

For continuing administration tasks, create an administration group that reflects an
appropriate set of permissions and capabilities. You might decide to give your
admin users an equivalent set of permissions as admin, or only a subset of
permissions. You can then assign users to that group to grant them their
administrative permissions. Additionally, this group can also be used as a resource
group to specify how much of the resources these administrative users should
receive compared to the users in other resource groups. If you do not use resource
management, then the administrative users are considered equal to the other users
(except admin) when they compete for resources. If you use resource management,
you can use GRA to allocate a percentage of system resources for them compared
to the other resource groups.
To create an administrators group that provides similar object and administrative

privileges as the admin user, complete the following steps:
Procedure
1. Connect to the System database as the admin user. For example:
[nz@nzhost ~]$ nzsql -d system -u admin -pw password
Welcome to nzsql, the Netezza SQL interactive terminal.
2. Create a group for your administrative users. For example:
SYSTEM.ADMIN(ADMIN)=> CREATE GROUP administrators;
CREATE GROUP
3. Grant the group all administrative permissions. For example:
SYSTEM.ADMIN(ADMIN)=> GRANT ALL ADMIN TO administrators WITH GRANT
OPTION;
GRANT
4. Grant the group all object permissions. For example:
SYSTEM.ADMIN(ADMIN)=> GRANT ALL ON DATABASE, GROUP, SCHEMA, SEQUENCE,
SYNONYM, TABLE, EXTERNAL TABLE, FUNCTION, AGGREGATE, USER, VIEW, PROCEDURE,
LIBRARY TO administrators WITH GRANT OPTION;
GRANT
5. Add users to the group to grant them the permissions of the group. For
example:
SYSTEM.ADMIN(ADMIN)=> ALTER USER jlee WITH IN GROUP administrators;
ALTER USER
or
SYSTEM.ADMIN(ADMIN)=> ALTER GROUP administrators WITH USER jlee, bob;
ALTER GROUP
Related concepts:
“Resource allocations for the admin user” on page 15-15
Logon authentication
The IBM Netezza system offers several authentication methods for Netezza
database users:
Local authentication
Netezza administrators define the database users and their passwords by
using the CREATE USER command or through the Netezza administrative
interfaces. In local authentication, you use the Netezza system to manage

database accounts and passwords, and to add and remove database users
from the system. This method is the default authentication method.
LDAP authentication
You can use an LDAP name server to authenticate database users and
manage passwords and database account activations and deactivations.
The Netezza system then uses a Pluggable Authentication Module (PAM)
to authenticate users on the LDAP name server. Microsoft Active Directory
conforms to the LDAP protocol, so it can be treated like an LDAP server
for the purposes of LDAP authentication.
Kerberos authentication
You can use a Kerberos distribution server to authenticate database users
and manage passwords and database account activations and
deactivations.
Authentication is a system-wide setting; that is, your users must be either locally
authenticated or authenticated by using the LDAP or Kerberos method. If you
choose LDAP or Kerberos authentication, you can create users with local
authentication on a per-user basis. You cannot use LDAP and Kerberos at the same
time to authenticate users. Netezza host supports LDAP or Kerberos authentication
for database user logins only, not for operating system logins on the host.
Related concepts:
“Encrypted passwords” on page 2-13
“User authentication method” on page 11-4
“Configure the Netezza host authentication for clients” on page 11-31
Local authentication
Local authentication validates that the user name and password that are entered
with the logon match the ones that are stored in the IBM Netezza system catalog.
The manager process that accepts the initial client connection is responsible for
initiating the authentication checks and disallowing any future requests if the
check fails. Because users can make connections across the network, the system
sends passwords from clients in an opaque form.
The Netezza system manages user names and passwords. It does not rely on the
underlying (Linux) operating system user name and password mechanism, other
than on user nz, which runs the Netezza software.
Note: When you create a user for local authentication, you must specify a
password for that account. You can explicitly create a user with a NULL password,
but the user is not allowed to log on if you use local authentication.
LDAP authentication
The LDAP authentication method differs from the local authentication method in
that the IBM Netezza system uses the user name and password that is stored on
the LDAP server to authenticate the user.
Following successful LDAP authentication, the Netezza system also confirms that
the user account is defined on the Netezza system. The LDAP administrator is
responsible for adding and managing the user accounts and passwords and
deactivating accounts on the LDAP server.

The Netezza administrator must ensure that each Netezza user is also defined
within the Netezza system catalog. The Netezza user names must match the user
names that are defined in the LDAP server. If the user names do not match, the
Netezza administrator should use the ALTER USER command to change the user
name to match the LDAP user name, or contact the LDAP administrator to change
the LDAP user name.
Keep in mind the following characteristics of LDAP authentication:

v After the LDAP authentication process completes successfully, the Netezza
system looks up the user in the system catalog. The system displays an error
message if it does not find the user, and it terminates the session.
v If authentication fails, you see the message LDAP authentication failed. The
system notes the reason for the failure in the /nz/kit/log/postgres/pg.log file.
v Netezza users should not notice any difference between LDAP and local
authentication.
v When you CREATE or ALTER a user account, a password is not required if you
use LDAP authentication. (Local authentication continues to require a password
for user accounts.)
To use LDAP authentication, you use the SET AUTHENTICATION command to

select LDAP authentication and specify the necessary configuration parameters.
The command requires some information about the LDAP server, such as server
name or IP address and some LDAP server configuration settings. The SET
AUTHENTICATION command is described in detail in the IBM Netezza Database
User’s Guide.
LDAP configuration file

When you use the SET AUTHENTICATION command to change from local to
LDAP authentication, the command does the following tasks:
v The command creates a backup copy of the ldap.conf file and saves it as
ldap.conf.orig. In general, do not manually edit or modify the ldap.conf file,
as changes can affect LDAP authentication and user access to IBM Netezza.
v The command then updates the /etc/ldap.conf file for the settings that are
specified in the SET AUTHENTICATION command.
You can issue the SET AUTHENTICATION command as often as necessary to

specify the correct configuration options for your LDAP server. The backup copy
ldap.conf.orig is only created when you change from local to LDAP
authentication.
After you use the SET AUTHENTICATION command or make any manual
changes to the ldap.conf file, restart the Netezza system by using the nzstop and
nzstart commands. This ensures that the Netezza system uses the latest settings
from the ldap.conf file.
The command does not use any of the settings from previous command instances;
make sure that you specify all the arguments that you require when you use the
command. The command updates the ldap.conf file for the configuration settings
that are specified in the latest SET AUTHENTICATION command.
Note: After you change to LDAP authentication, if you later decide to return to
local authentication, you can use the SET AUTHENTICATION LOCAL command
to restore the default behavior. When you return to local authentication, the
command overwrites the ldap.conf file with the ldap.conf.orig file (that is, the
ldap.conf file that resulted after the first SET AUTHENTICATION LDAP
command was issued). The Netezza system then starts to use local authentication,
which requires user accounts with passwords on the Netezza system. If you have
Netezza user accounts with no passwords or accounts that were created with a
NULL password, use the ALTER USER command to update each user account
with a password.
Configuring SSL security for LDAP authentication

If you use LDAP authentication, you can also use Secure Sockets Layer (SSL)
protocols to manage the security of the communication between the IBM Netezza
system and the LDAP server.
About this task
With SSL, the Netezza system and LDAP server use additional protocols to
confirm the identity of both servers by using digital certificates. You must obtain
certificate authority (CA) files from the LDAP server and save them in a directory
on the Netezza system. You need three files: a root certificate, the CA client
certificate, and the CA client keys file. These files typically have the extension .pem.
Important: During this procedure, you must manually edit the ldap.conf file to
specify the locations of the CA cert files. When you edit the file, do not delete any
existing lines, even those lines that display as comments, as they are often used by
the LDAP configuration commands. Add the new configuration settings for the
LDAP CA certificates.
To configure SSL security for your LDAP server communications, complete the
following steps:
Procedure
1. Obtain the three CA certificate files from the LDAP server, and save them on a
location on the Netezza system. For Netezza high availability (HA) systems,
save the files in a location on the shared drive, such as a new directory under
/nz. Both HA hosts must be able to access the certificate files by using the same
path name.
2. Use the SET AUTHENTICATION LOCAL command to temporarily restore
local authentication. The command overwrites the ldap.conf file with the
ldap.conf.orig backup file.
3. With any text editor, append the following three lines to the /etc/ldap.conf
file and save the file:
tls_cacertfile pathname_to_cacert.pem_file
tls_cert pathname_to_clientcrt.pem_file
tls_key pathname_to_clientkey.pem_file
For example:
tls_cacertfile /nz/certs/cacert.pem
tls_cert /nz/certs/clientcrt.pem
tls_key /nz/certs/clientkey.pem
4. Use the SET AUTHENTICATION LDAP SSL ON command and any additional
configuration arguments (based on your LDAP server configuration) to restore
the LDAP authentication. Since the server transitions from local to LDAP
authentication, it copies the ldap.conf file with your new certificate path names
to ldap.conf.orig, and enables LDAP authentication.

What to do next
After you use the SET AUTHENTICATION command or make any manual
changes to the ldap.conf file, restart the Netezza system by using the nzstop and
nzstart commands. This ensures that the Netezza system uses the latest settings
from the ldap.conf file.
Kerberos authentication
If your environment uses Kerberos authentication to validate users, you can use
Kerberos instead of local or LDAP authentication to validate your Netezza
database user accounts.
With Kerberos authentication, users are first validated against the user name and
password that is stored on the Kerberos server. After successful Kerberos
authentication, the IBM Netezza system then confirms that the user account is
defined as a Netezza database user.
The Kerberos administrator is responsible for adding and managing the user
accounts and passwords and deactivating accounts on the Kerberos server. The
Netezza administrator must ensure that each Netezza database user is also defined
within the Netezza system catalog.
Important: The Kerberos and Netezza user names must match. When you
configure the system to use Kerberos authentication, you can specify
USERCASE=MATCHDB to convert unescaped Kerberos names to the Netezza
system letter case, which is uppercase by default. If you specify
USERNAME=KEEP, the Kerberos names are not converted, and the Kerberos and
Netezza names must match exactly, including letter casing. If the user names do
not match, the Netezza administrator can use the ALTER USER command to
change the Netezza user name to match the Kerberos user name, or contact the
Kerberos administrator to change the Kerberos name to match the Netezza user
name.
If you choose to use Kerberos authentication, then all database user accounts
except admin are authenticated by Kerberos. You can configure database user
accounts to be locally authenticated as an exception. This implementation does not
support mixed Kerberos and LDAP authentication modes; that is, you cannot
authenticate some users by LDAP authentication and some by Kerberos.
About the Kerberos software
The Netezza implementation of Kerberos support uses MIT Kerberos 5 Release

1.12.1. (Kerberos is a trademark of the Massachusetts Institute of Technology
(MIT).) The Netezza software kit includes all the required libraries and binaries to
run Kerberos on the Netezza hosts. The NPS client kits include the libraries
required to use the NPS clients, ODBC, JDBC, and OLE DB connectors with
Kerberos authentication of the database user accounts. Your IT or system
administrators are responsible for the setup of the Kerberos environment on your
client systems including the configuration files and the tools for managing tickets.
If your environment is using an earlier or different release of Kerberos, note that

Netezza requires a minimum of Kerberos 1.10. It is recommended that you
upgrade to the latest Kerberos 1.12.1 release for compatibility. The Netezza
Kerberos support has not been tested with other Kerberos releases and may not
function correctly with Kerberos releases before 1.12.1. If your Kerberos

environment uses an earlier release, you may not have the support for
multi-user/concurrent database connections from the same client (which is used by
the ODBC, JDBC, OLE DB, and IBM Netezza Performance Portal clients, for
example), or for the ability to connect to the Netezza appliance using its floating
host name and IP address. Both of these features are in release 1.12.1 and later.
The following table lists the supported operating systems and revisions for the
Netezza CLI clients.
Table 11-6. Netezza supported platforms for Kerberos authentication
Windows
Windows 2008, Vista, 7 Intel / AMD Intel / AMD
Windows Server 2012 N/A Intel / AMD
Linux
Red Hat Enterprise Linux 5.3, 5.5, 5.7, 5.9, 6.1, Intel / AMD Intel / AMD
6.2, 6.4, 6.5 (see note below table)
Red Hat Enterprise Linux 6.2+ N/A PowerPC
SUSE Linux Enterprise Server 11 Intel / AMD Intel / AMD
SUSE Linux Enterprise Server 10 and 11, and IBM System z IBM System z
Red Hat Enterprise Linux 5.x
UNIX
IBM AIX 6.1 with 5.0.2.1 C++ runtime libraries, N/A PowerPC
7.1
HP-UX 11i versions 1.6 and 2 (B.11.22 and Itanium Itanium
B.11.23)
Oracle Solaris 9, 10, 11 SPARC SPARC
Oracle Solaris 10 x86 x86
Note: For many client platforms, Kerberos 1.12 support might not be available
from the operating system vendor. In these cases, you must download the Kerberos
source code from the MIT Kerberos website and build it on your local systems. A
minimum of release 1.10 is required for full support of features, but version 1.12 is
recommended.
On Windows platforms, you must use MIT Kerberos for Windows 4.0.1 to enable
multiple-user support.
Set up Kerberos support for Netezza

To use Kerberos authentication, there are several setup steps that are required to
establish the system as a client to the Kerberos server and to configure Kerberos
authentication in the Netezza environment.
In many environments, the Kerberos administrator defines specific setup and

configuration settings that clients must use. It is recommended that you discuss the
process at your site with your Kerberos administrator. The Kerberos administrator
may have a default configuration file and keytab process so that a Netezza
administrator can copy the files to the Netezza appliance. However, other
environments might not have a highly customized environment, and the only
information that you might require is the Kerberos realm and Key Distribution
Center (KDC) server information. If necessary, you can create your configuration

and keytab files manually based on the input information from your Kerberos
administrator. The following topics describe both of these setup methods.
Kerberos configuration file

The Netezza appliance requires a Kerberos configuration file to establish Kerberos
authentication support. The krb5.conf file specifies configuration parameters that
are required for Kerberos authentication.
There are two methods for creating a configuration file:

v Use a site-wide configuration file that is supplied by your Kerberos
administrator.
v Obtain specific information and create a basic Kerberos configuration file.
In many Kerberos environments, the krb5.conf file is already available for the
Kerberos client support. Consult with your Kerberos administrator to see if a copy
of the krb5.conf file is available that you can store on the Netezza appliance.
Optionally, a Netezza administrator can generate a minimal version of the file, or
update the file, for a simple configuration setup using the SET
AUTHENTICATION command.
Use a site-wide configuration file
If your Kerberos administrator supplies a krb5.conf file for each client that is
added into the Kerberos authentication environment, follow these steps to add that
configuration file to the Netezza appliance and enable Kerberos authentication.
1. Log in to the Netezza active host as the nz user.
2. Change to the $NZ_DATA/config directory (usually /nz/data/config).
3. Save your Kerberos configuration file as krb5.conf in the config directory.
4. Connect to the NPS database as the admin user or any database user who has
Manage System privileges.
5. Type the following command to enable system-wide Kerberos authentication:
SYSTEM.ADMIN(ADMIN)=> SET AUTHENTICATION KERBEROS;
NOTICE: Updating /nz/data.1.0/config/krb5.conf and other files.
NOTICE: Re-log-in or open a new shell for changes to take effect.
SET VARIABLE
The SET AUTHENTICATION KERBEROS command adds the KRB5_CONFIG

environment variable to the nz user's .bashrc file. The variable is set to the
location of the krb5.conf file (/nz/data/config/krb5.conf). Log out of the database
connection and the nz user account, then log in again as nz to ensure that your
session adopts the new Kerberos environment settings. The change does not affect
users who are currently logged in to the Netezza database until they log out and
open a new connection to the database.
Create a Kerberos configuration file
If your environment does not have a specific Kerberos configuration file, you can
create one for the Netezza system with the basic required information. Before you
begin, make sure that you obtain the name of the Kerberos realm and KDC from
your Kerberos administrator.
2. Connect to the NPS database as the admin user or any database user who has
Manage System privileges.
3. Type the following command:

SYSTEM.ADMIN(ADMIN)=> SET AUTHENTICATION KERBEROS REALM ’myrealm’ KDC ’mykdc’;
NOTICE: Updating /nz/data.1.0/config/krb5.conf and other files.
NOTICE: Re-log-in or open a new shell for changes to take effect.
SET VARIABLE
In the sample command, the myrealm value is the Kerberos realm for your
environment, which is typically the domain name for the Kerberos domain. The
mykdc value is the Kerberos authentication server, usually called the Key
Distribution Center (KDC).
This command creates a basic /nz/data/config/krb5.conf configuration file with

the realm and KDC information, and enables Kerberos authentication for your
system.
The SET AUTHENTICATION KERBEROS command adds the KRB5_CONFIG

environment variable to the nz user's .bashrc file. The variable is set to the
location of the krb5.conf file (/nz/data/config/krb5.conf). Log out of the database
connection and the nz user account, then log in again as nz to ensure that your
session adopts the new Kerberos environment settings. The change does not affect
users who are currently logged in to the Netezza database until they log out and
open a new connection to the database.
Kerberos keytab file

The Netezza appliance requires a Kerberos keytab file krb5.keytab to define the
keys that define the Netezza appliance as a Kerberos client.
The Kerberos administrator adds the Netezza host as three service principals to the
Kerberos database. The three definitions represent the two host names for the
Netezza HA hosts and the Netezza floating host name.
The Kerberos administrator can run these commands on the Kerberos server or any
client in the Kerberos realm where the Netezza appliance will be a member. The
Kerberos administrator could also run these commands from the Netezza host 1
after the Kerberos configuration file (krb5.conf) has been added to the Netezza
host.
Note: To use kadmin on the Netezza host, the nz user must have the
KRB5_CONFIG variable set in the .bashrc file. The variable is added by the SET
AUTHENTICATION KERBEROS command, but if you have not yet run that
command, you might need to set the variable manually to point to the
/nz/data/config/krb5.conf file.
The Netezza appliance uses the "netezza" service name. The following sample
commands show how to configure the service principals for Netezza host 1
(mynpshost-ha1), Netezza host 2 (mynpshost-ha2), and the floating host name
(mynpshost-pri).
% kadmin –p KerberosAdmin/admin
kadmin: ktadd –k /nz/data/config/krb5.keytab
netezza/mynpshost-ha1.mycompany.com
netezza/mynpshost-ha2.mycompany.com
netezza/mynpshost-pri.mycompany.com
kadmin: quit
The Kerberos keys are extracted to a file named krb5.keytab.
If the krb5.keytab file was created on another system and must be copied to the
Netezza appliance, do the following steps:

2. Change to the $NZ_DATA/config directory (usually /nz/data/config).
3. Save your Kerberos keytab file as krb5.keytab.
Note: If you place your keytab file in a location other than /nz/data/config, set
the KRB5_KTNAME environment variable to define the custom location. You could
set it in the .bashrc file for the nz user account. After you set the variable, stop
and restart NPS so that the software can find the keytab file.
Test the Kerberos authentication

After you add the Netezza appliance as a Kerberos client, test the Kerberos
authentication to verify that users can connect to the Netezza database.
To fully test the Kerberos authentication, it is recommended that you do the

following steps:
v Confirm that a database user account other than admin can connect to a Netezza
database, Make sure that you test the nzsql command line, and also a data
connectivity client connection such as ODBC, JDBC, or OLE DB. You could use
the nzodbcsql test program as a connection example.
v Fail over the active NPS NPS host to the standby host, and repeat the login and
database connection tests to verify that non-admin database users can connect
when host 2 is the active host.
Kerberos configuration updates

If your Kerberos environment requires configuration changes, you can update the
Netezza Kerberos configuration to ensure that authentication continues to operate
as expected.
If you receive new Kerberos configuration (krb5.conf) or keytab (krb5.keytab) files,

you can replace the ones in /nz/data/config with the latest versions. The new files
are used for the next user authentication request.
If the Kerberos realm or KDC information changes, you can run the SET
AUTHENTICATION command and specify the new values to make those values
take effect.
After you change the Kerberos configuration, you should create a new host backup
using the nzhostbackup command to capture the latest configuration.
Kerberos ticket caching

If your Kerberos environment uses ticket caching, be sure to cache tickets in a
location that is accessible in a shared mount location on the Netezza hosts.
For a Netezza appliance, the ticket cache location must be on the shared mount
points (either /nz or /export/home) so that tickets can be accessed after a host
failover from the active Netezza host to the standby host.
For configurations where single user tickets that are stored in a cache file, by
default, Kerberos caches the tickets in the /tmp directory. The /tmp directory is not
a shared mount area for the HA hosts. You can use the KRB5CCNAME
environment variable to specify the location for the tickets. You should set the
variable in the nz user's .bashrc file for the nz user account. After you set the
variable, export the variable so that Kerberos uses the new location for the ticket
cache. A sample setting follows:
KRB5CCNAME=FILE:/nz/krb5cc_500

For configurations where multiple user tickets are stored in a cache directory, you
must set the KRB5CCNAME environment variable to specify the location for the
tickets. You should set the variable in the nz user's .bashrc file for the nz user
account. After you set the variable, export the variable so that Kerberos uses the
new location for the ticket cache. Be sure to create a new empty directory (for
example, /nz/krb5cc_500) on the shared mount point before you set the variable. A
sample setting follows:
KRB5CCNAME=DIR:/nz/krb5cc_500
Kerberos errors and troubleshooting

This topic describes some common Kerberos-related problems and troubleshooting
steps.
If you use Kerberos authentication, note that detailed messages and error
conditions are written to the /nz/kit/log/postgres/pg.log file.
Kerberos setup issues
If you are encountering login problems after enabling Kerberos authentication, be

sure to check that the krb5.keytab file includes the correct information for both of
the Netezza hosts and the floating host name. You use the Kerberos ktutil
command to examine the contents of a keytab file.
In addition, make sure that the name of the NPS service machine was added
correctly to the KDC server by the Kerberos administrator.
Kerberos is enabled, but the database user is configured for local

authentication
After you enable Kerberos authentication, the database users that you create
should use Kerberos authentication as well. (You can create locally authenticated
users as an exception.) If a Netezza administrator creates a local authentication
user account without the AUTH "local" exception syntax, and the user attempts to
start a database connection, the connection fails with the error Password
authentication failed for user 'user_name'. Make sure that your Kerberos users
are configured to use DEFAULT authentication when you enable Kerberos as your
authentication method for the database system. You must have a matching
Kerberos user for every database user except the admin user.
Commands related to authentication methods

The following table lists the commands that are related to local, LDAP, and
Kerberos authentication methods. For more information about these commands,
including command syntax, see the IBM Netezza Database User’s Guide.
Table 11-7. Authentication-related commands
Command Description
SET AUTHENTICATION Sets the authentication method, either Local, LDAP, or
Kerberos.
SHOW AUTHENTICATION Displays the current authentication configuration.
CREATE USER Creates a Netezza user, including an optional password.
When you create users and use local authentication, you
must specify a password. If you use LDAP or Kerberos
authentication, the password specified with the account is
ignored. The password will be specified at and controlled
by the third-party authentication server.

Table 11-7. Authentication-related commands (continued)
Command Description
ALTER USER Modifies a Netezza user account. If you change from
LDAP or Kerberos to local authentication, you might need
to alter user accounts to ensure that they have a password
that is defined on the Netezza system.
Passwords and logons

Login authentication validates against the system catalog. The 64-bit DES
encryption converts passwords to alphanumeric characters.
As administrator, you can do the following to ensure security:

v Specify a minimum password length. As database administrator, you can change
the minimum password length from four characters to a maximum of 31
characters.
v Limit the number of invalid login attempts.
By default, there is no limit to the number of times a user can attempt to log on
to the IBM Netezza system. As database administrator, you can set a limit on the
number of invalid logon attempts and when the limit is reached have the system
lock the account.
After the Netezza system locks an account, you must manually unlock the
account for the user to be able to access it again.
When users are locked out of their accounts, the system displays the same error
message even if users enter the correct password.
nzsql: Password authentication failed for user ’bob’
v Limit the authentication timeout for LDAP authentication.
v Use the nzpassword command to create locally stored encrypted passwords. For
more information, see “Encrypted passwords” on page 2-13.
The following information about passwords and logons applies regardless of the
authentication method.
Changing the number of logon attempts

About this task
To change the number of logon attempts, complete the following steps:
Procedure
1. Use a standard editor and open the configuration file /nz/data/
postgresql.conf.
2. Locate the line that contains invalid_attempts.
3. Copy the line, paste the copy after the current line, remove the comment
character (#), and change the value for invalid_attempts.
4. Save your changes.
5. Restart the IBM Netezza system for your changes to take effect.
Resetting a locked account

About this task
To reset a locked account, complete the following steps:

Procedure
1. Log in to the IBM Netezza SYSTEM database as the admin user or any
database user who is granted Alter privilege on User objects or the locked user
account.
Note: If you created an administrative user group, as described in “Creating an

administrative user group” on page 11-17, you can log in as any database user
who is a member of that group to unlock the user account.
2. Use the ALTER USER RESET ACCOUNT command:
SYSTEM.ADMIN(ADMIN)=> ALTER USER username RESET ACCOUNT
Results
If the admin user is locked, you can unlock it by using one of the administrative
group of users. If you do not have any users who are granted Alter privileges on
user objects or the admin account, contact Netezza Support to unlock the admin
account.
Specifying an authentication timeout

By default, LDAP authentication requests have a timeout of 300 seconds. If the
LDAP server requires more time to respond to requests in your environment, you
can change the timeout settings for your system by using a postgresql.conf
setting.
About this task
To change the authentication timeout, complete the following steps:
Procedure
1. Use a standard editor and open the configuration file /nz/data/
postgresql.conf.
2. Search for an existing definition for the auth_timeout variable.
3. If the auth_timeout variable is defined in the file, change the value to the
number of seconds that you want to use for the timeout. Otherwise, you can
define the variable by adding the following line to the file. Add the line to the
Security Settings section of the file.
auth_timeout = number_of_seconds
4. Save your changes.
5. Restart the IBM Netezza system for your changes to take effect.
Netezza client encryption and security

The IBM Netezza system supports SSL for encrypting communication with Netezza
client users and peer authentication between the client and Netezza host. The
encryption protects the communication for the Netezza client users who access
their data by using ODBC, JDBC, nzsql, or the command-line interfaces. The peer
authentication uses a digital certificate from the Netezza system to confirm the
identity of the clients and host (the Netezza system).
Note: Encrypted communications have a performance impact because of the time

and processing that is required for the encryption and decryption. For Netezza
client users who are within a secure network environment, consider the use of
unsecured connections for best performance.

If you use secure communications to the Netezza, there are some optional
configuration steps for the Netezza host:
v Define SSL certification files in the postgresql.conf file for peer authentication
v Create connection records to restrict and manage client access to the Netezza
system
The Netezza client users must specify security arguments when they connect to
Netezza systems. The nzsql command arguments are described in the IBM Netezza
Database User’s Guide. For a description of the changes that are needed for the
ODBC and JDBC clients, see the IBM Netezza ODBC, JDBC, OLE DB, and .NET
Installation and Configuration Guide.
Configuring the SSL certificate

About this task
By default, the IBM Netezza system and clients do not use peer authentication to
verify each other's identity. If you want to authenticate connection peers, you must
create or obtain from a CA vendor the server certificate and keys file and the CA
root certificate for the client users. The Netezza system has a default set of server
certificates and keys files (server-cert.pem and server-keys.pem) in the
/nz/data/security directory. Netezza supports files that use the .pem format.
If you use your own CA certificate files, make sure that you save the server CA
files in a location under the /nz directory. If you have an HA Netezza system, save
the certificates on the shared drive under /nz so that either host can access the files
by using the same path name. You must also edit the /nz/data/postgresql.conf
file to specify your server certificate files.
To edit the postgresql.conf file to add your own CA server certificate and keys
files, complete the following steps:
Procedure
1. Log in to the Netezza system as the nz user account.
2. With any text editor, open the /nz/data/postgresql.conf file.
Important: Use caution when you edit postgresql.conf. It contains important

configuration parameters for the Netezza system operation.
3. Locate the following section in the file:
#
# Connection Parameters
#
#tcpip_socket = false
ssl = true
# Uncomment the lines below and mention appropriate path for the
# server certificate and key files. By default the files present
# in the data directory will be used.
#server_cert_file=’/nz/data/security/server-cert.pem’
#server_key_file=’/nz/data/security/server-key.pem’
4. Delete the number sign (#) character at the beginning of the server_cert_file
and server_key_file parameters and specify the path name of your CA server
certificate and keys files where they are saved on the Netezza host.

Client users must install a copy of the CA root certificate file on their client
systems. The client users specify the location of the CA root certificate when
they run commands such as nzsql, nzhw, and others.
Important: Make sure that the keys file is not password protected; by default,
it is not.
5. Save and close the postgresql.conf file.
Results
Any changes that you make to the postgresql.conf file take effect the next time
that the Netezza system is stopped and restarted.
Configure the Netezza host authentication for clients

By default, the IBM Netezza system is configured to accept either secured or
unsecured SSL connections from Netezza clients. The client connection request
specifies the user name, password, database access, connection type (either secured
or unsecured), and the IP address of the client. The Netezza system confirms the
account information, then accepts the connection as either secured or unsecured
(based on the client request and the Netezza host configuration) if the account
information is valid.
If your users are located within the secure firewall of your network or they use a
protocol such as ssh to securely connect to the Netezza system, you might require
them to use unsecured communications, which avoids the performance overhead
of secured communications. If you have one or more clients who are outside that
firewall, you might require them to use secured connections. The Netezza system
provides a flexible way to configure access security and encryption for your client
users.
To configure and manage the client access connections, you use the SET
CONNECTION, DROP CONNECTION, and SHOW CONNECTION commands.
These commands manage updates to the /nz/data/pg_hba.conf file for you, and
provide mechanisms for remote updates, concurrent changes from multiple
administrators, and protection from accidental errors when you edit the file.
Important: Never edit the /nz/data/pg_hba.conf file manually. Use the Netezza
SQL commands to specify the connection records for your Netezza system.
A connection record has the following syntax:

type dbName ipAddress addressMask authType
The field descriptions follow:

type Specifies a connection record type. The type field can have one of the
following values:
host Specifies the access permission for users who connect to Netezza
databases by using IP connections. Users in the specified IP range
might use secured or unsecured connections; the Netezza host
accepts either.
hostssl
Specifies the access permission for only those users who connect to
Netezza databases by using SSL secured IP connections. Users in
the specified IP range who request unsecured connections are
rejected.
hostnossl
Specifies the authentication for users who request to connect with
unsecured IP connections. Users in the specified IP range who
request secured connections are rejected.
local Specifies the authentication for users who connect over a UNIX
socket; that is, they are logged in locally to the Netezza system,
such as at the administration console.
dbName
Specifies the name of the DB to which the user might request a connection.
The value can be ALL to allow connections to any database on the Netezza
system (if their user account has object permissions to that database) or a
specific database name.
ipAddress
Specifies an IP address in standard decimal notation for one or more client
users who might connect to the Netezza system. This field is used only for
host, hostssl, and hostnossl connection types.
addressMask
Specifies an IP address mask in standard decimal notation to identify a
range of one or more client users who might connect to the Netezza
system. This field is used only for host, hostssl, and hostnossl connection
types. For details about subnet masks, see any general TCP/IP
documentation. For example, a mask of 0.0.0.0 indicates that the record is
for a connection request from the specific ipAddress value. An ipAddress
of 1.2.3.4 and a mask of 255.255.255.0 indicates that the record defines
connection attempts for any client that has an IP address in the range of
1.2.3.1–255.
authType
Specifies the authentication method for the Netezza system. Specify this
value when you create a connection record for local authentication. (You
cannot specify an authentication type for LDAP or Kerberos
authentication.) The values are trust, md5, crypt, password, and SHA_256.
For information about local values, see the IBM Netezza Database User’s
Guide.
Related concepts:
Show connection records

IBM Netezza has a set of predefined connection records. To list the current set of
connection records, use the SHOW CONNECTION command.
The command displays a connection ID to uniquely identify each connection

record. A sample command follows:
--------+-----------+--------+-------------+-----------------+--------
2 | host | all | 127.0.0.1 | 255.255.255.255 | md5
3 | host | all | 0.0.0.0 | 0.0.0.0 | md5
(3 rows)
In the sample output, the connection requests define the following capabilities:
v Connection ID 1 specifies that the Netezza host accepts connection requests from
any local user (someone that is logged in directly to the Netezza) to all
databases.

v Connection ID 2 specifies that the host accepts either secured or unsecured
connection requests from any local user (connecting through IP) to all databases.
v Connection ID 3 specifies that the host accepts either secured or unsecured
connection requests from any remote client user (connecting through IP) to any
database.
Important: The host might accept a connection request, but the user must still pass
account authentication (user name and password verification), and have
permissions to access the requested database.
The first record that matches the client connection information is used for
authentication. If the first chosen record does not work, the system does not look
for a second record. If no record matches, access is denied. With the default records
previously shown, any client user who accesses the Netezza system and has correct
user account and password credentials is allowed a connection; they can request
either secured or unsecured connections, as the Netezza host accepts either type.
Create connection records

Use the SET CONNECTION command to add a connection record for your client
users.
For example, if you have one user who connects from outside the network firewall
from an IP address 1.2.3.4, you might want to require that client to use secured SSL
connections. You can create a connection record for that user by using the
following sample command:
SYSTEM.ADMIN(ADMIN)=> SET CONNECTION HOSTSSL DATABASE ’ALL’ IPADDR ’1.2.3.4’
IPMASK ’255.255.255.255’ -AUTH SHA256;
SET CONNECTION
This command adds a connection record to the database. A sample SHOW

CONNECTION command follows, with the new record added as ID 3:
--------+-----------+--------+-------------+-----------------+--------
2 | host | all | 0.0.0.0 | 0.0.0.0 | md5
3 | hostssl | all | 1.2.3.4 | 255.255.255.255 | SHA256
(3 rows)
This example shows the importance of record precedence. Record ID 2 is the first
match for all of the users who remotely connect to the IBM Netezza system.
Because it is set to host, this record allows either secured or unsecured connections
that are based on the connection request from the client. To ensure that the user at
1.2.3.4 is authenticated for a secure connection, drop connection record 2 and add
it again by using a new SET CONNECTION record to place the more general
record after the more specific record for 1.2.3.4.
Drop connection records

To drop a connection record, use the DROP CONNECTION command and specify
the connection ID.
Use the following sample command to drop a connection record:

SYSTEM.ADMIN(ADMIN)=> DROP CONNECTION 4;
DROP CONNECTION

Commands related to Netezza client connection methods
The following table lists the commands that are related to IBM Netezza client
connection methods. For more information about these commands, including
command syntax, see the IBM Netezza Database User’s Guide.
Table 11-8. Client connection-related commands
Command Description
SET CONNECTION Defines a connection record for client access.
SHOW CONNECTION Displays the current set of connection records for client
access.
DROP CONNECTION Drops or deletes a connection record for client access.
CREATE USER Creates a Netezza user, including an optional password.
When a client user attempts to connect to the Netezza,
they must have a valid user account and password.
User and group limits

You can place limits on the resources that users and groups can use. You can limit
the number of rows that a query can return (rowset limit), the amount of time a
session can remain idle before it is terminated (session timeout), the amount of
time a query can run before the system notifies you, the session priority, and the
number of days before the account password expires.
The IBM Netezza system calculates the limit for each user based on the following
rules:
v If the attribute is set for the user account, use that value.
v If the attribute is not set for the USER, use the MOST RESTRICTIVE value set
for any of the groups of which that user is a member.
v If the attribute is not set for the user or any of the user’s groups, use the system
default value.
The following table describes these settings.

Table 11-9. User and group settings
Default
Setting Scope Valid range value Description
Rowset limit User, 1 - 2,147,483,647 or Unlimited Maximum rowset limit
group, and unlimited (zero) (zero) per query. For more
system information, see “User
rowset limits” on page
11-36.
Query User, 1 - 2,147,483,647 Unlimited Maximum time that is
timeout group, and minutes or (zero) allocated to a query. For
system unlimited (zero) more information, see
“Query timeout limits” on
page 11-37.
Session limit User, 1 - 2,147,483,647 Unlimited When a SQL session is
group, and minutes or (zero) idle for longer than the
system unlimited (zero) specified period, the
system terminates the
session. For more
information, see “Session
timeout” on page 11-38.

Table 11-9. User and group settings (continued)
Default
Setting Scope Valid range value Description
Session User, Critical, high, None Defines the default and
priority group, and normal, or low maximum priority for the
system user or group.
Password User, 0 or any positive 0 (password Defines how many days
expiration group, and int value does not that the password for the
system expire) account is valid. Used
only for local
authentication accounts.
For more information, see
“Password expiration.”
When you change these values, the system sets them at session startup and they
remain in effect for the duration of the session.
You specify the system defaults with the SET SYSTEM DEFAULT command. To
display the system values, use the SHOW SYSTEM DEFAULT command.
v To set a system default, use a command similar to the following, which sets the
default session timeout to 300 minutes:
SYSTEM.ADMIN(ADMIN)=> SET SYSTEM DEFAULT SESSIONTIMEOUT TO 300;
SET VARIABLE
v To show the system default for the session timeout, use the following syntax:
SYSTEM.ADMIN(ADMIN)=> SHOW SYSTEM DEFAULT sessiontimeout;
NOTICE: ’session timeout’ = ’300’
SHOW VARIABLE
Password expiration
You can specify the number of days that an IBM Netezza database user account
password is valid as a system-wide setting. You can also specify the password
expiration rate on a per-user and per-group basis. You can also expire an account
password immediately.
To set a system-wide control for expiring database user account passwords, use the
SET SYSTEM DEFAULT SQL command:
SYSTEM.ADMIN(ADMIN)=> SET SYSTEM DEFAULT PASSWORDEXPIRY TO days;
SET VARIABLE
The days value specifies the number of days that the password is valid, since the
last date when the password changed. If you do not want passwords to expire,
specify a value of 0. The default system setting is 0.
You can specify the account password expiration by using the PASSWORDEXPIRY
option of the [CREATE|ALTER] USER and [CREATE|ALTER] GROUP SQL
commands. Some example commands follow.
v To create a group that has a password expiration rate of 45 days:
MYDB.SCH1(USER)=> CREATE GROUP staff WITH PASSWORDEXPIRY 45;
v To change the expiration setting for the user sales_user to 30 days:
MYDB.SCH1(USER)=> ALTER USER sales_user WITH PASSWORDEXPIRY 30;

When a database user account expires, the user has limited access to the IBM
Netezza system. The user can connect to the Netezza database, but the only query
that the user is allowed to run is the following ALTER USER command, where
newPassword represents the new account password:
SYSTEM.ADMIN(myuser)=> ALTER USER myuseracct WITH PASSWORD ’newPassword’;
ALTER USER
The admin user, the owner of the user, or a user who has Alter privilege for the
user can immediately expire the user account password by using the following
command:
SYSTEM.ADMIN(ADMIN)=> ALTER USER myuseracct EXPIRE PASSWORD;
ALTER USER
If the user is connected to a database, the expiration does not affect the current
session. The next time that the user connects to a database, the user has a
restricted-access session and must change the password by using the ALTER USER
command.
User rowset limits

You can place a limit on the number of rows a query can return and thus restrict
resources for large result sets. Specifying a rowset limit when you create a user or
a group automatically limits the rows that are returned so that users do not have
to append a limit clause to their SQL queries.
Note: Rowset limits apply only to user table and view queries, not to system
tables and view queries.
You can also impose rowset limits on both individual users and groups. In
addition, users can set their own rowset limits. The admin user does not have a
limit on the number of rows a query can return.
If rowset limits were applied to the results of a query, the nzsql command displays
a message and the system writes a notice to the /nz/kit/log/postgres/pg.log file.
An example follows, but note that the 100 records are not shown in the example:
MYDB.ADMIN(MYUSR)=> select * from ne_orders;
NOTICE: Rowset limit of 100 applied
O_ORDERKEY | O_CUSTKEY | O_ORDERSTATUS
------------+-----------+---------------
96 | 32333333 | F
128 | 22186669 | F
...
A sample pg.log message follows:

2015-08-10 07:53:02.534444 EDT [13417] DEBUG: QUERY: select * from ne_orders;
2015-08-10 07:53:02.534949 EDT [13417] NOTICE: Rowset limit of 100 applied
Client users who access the NPS host can use APIs such as the ODBC
SQLGetDiagRec() or JDBC getwarning to capture the rowset limit message.
Rowset limit syntax

You can specify a rowset limit when you create a user or group. You can also alter
the rowset limit of a user or a group. You can specify any number up to
2,147,483,647 or zero, which means unlimited.
v To create a user with a rowset limit, use the following syntax:
CREATE USER username WITH ROWSETLIMIT [number | UNLIMITED]
v To create a group with a rowset limit, use the following syntax:

CREATE GROUP name WITH ROWSETLIMIT [number | UNLIMITED]
v To modify a user's rowset limit, use the following syntax:
ALTER USER username WITH ROWSETLIMIT [number | UNLIMITED]
v To modify a group's rowset limit, use the following syntax:
ALTER GROUP name WITH ROWSETLIMIT [number | UNLIMITED]
Overriding the rowset limit for a session

About this task
For commands that perform INSERT TO ... SELECT FROM or CREATE TABLE AS
... SELECT operations, the rowset limit can affect the results by limiting the
number of rows that are inserted to the resulting table. If you are using these
commands to create user tables, you can override the rowset limit within your user
session to ensure that those queries complete with all the matching rows. This
override does not change the limit for other SELECT queries, or for INSERT TO ...
SELECT FROM or CTAS queries that write to external table destinations.
To override the rowset limit for INSERTS and CTAS operations in a session,
complete the following table:
Procedure
1. Open a session with the IBM Netezza database and log in by using your
database user account.
2. Use the following command to set the session variable.
MY_DB.MYSCHEMA(NZUSER)=> SET ROWSETLIMIT_LEVEL=0;
SET VARIABLE
3. Use the following command to show the status of the rowset limit for the
session:
MY_DB.MYSCHEMA(NZUSER)=> SHOW ROWSETLIMIT_LEVEL;
NOTICE: ROWSETLIMIT_LEVEL is off
Results
When the rowset override is enabled (rowsetlimit_level=0), keep in mind the

following behaviors for your INSERT and CTAS queries:
v A CTAS operation to a user table destination is not subject to the rowset limit.
v A CTAS operation to an external table is subject to the rowset override.
v An INSERT INTO <table> SELECT FROM operation, where <table> is a user
table, is not subject to the rowset limit override.
v An INSERT INTO <table> SELECT FROM operation, where <table> is an
external table, is subject to the rowset limit override.
To disable the override and restore the limit to all queries, set the value of the
rowsetlimit_level session variable to 1 (on).
Query timeout limits

You can place a limit on the amount of time a query is allowed to run before the
system notifies you by using the runaway query event. The event email shows
how long the query has been running, and you can decide whether to terminate
the query.
Note: To receive a message, you must enable the runawayQuery event rule.

You can impose query timeout limits on both individual users and groups. In
addition, users can set their own query timeouts.
Related reference:
“Runaway query notification” on page 8-24
You can use the RunAwayQuery event type to monitor queries that exceed
configured query timeout limits.
Query timeout syntax

You can specify a query timeout when you create a user or group. You can also
alter the query timeout of a user or a group. Specify the query timeout in minutes.
Changes to the query timeout for the public group do not affect the admin user's
settings.
v To create a user with a query timeout, use the following syntax:
CREATE USER username WITH QUERYTIMEOUT [number | UNLIMITED]
v To create a group with a query timeout, use the following syntax:
CREATE GROUP name WITH QUERYTIMEOUT [number | UNLIMITED]
v To modify a user's query timeout, use the following syntax:
ALTER USER username WITH QUERYTIMEOUT [number | UNLIMITED]
v To modify a group's query timeout, use the following syntax:
ALTER GROUP name WITH QUERYTIMEOUT [number | UNLIMITED]
Session timeout
You can place a limit on the amount of time a SQL database session is allowed to
be idle before the system terminates it. You can impose timeouts on both
individual users and groups. In addition, users can set their own timeouts.
Session timeout syntax

You can specify a session timeout when you create a user or group. You can also
alter the session timeout of a user or a group. Specify the timeout in minutes.
Changes to the session timeout for the public group do not affect the admin user's
settings.
v To create a user with a session timeout, use the following syntax:
CREATE USER username WITH SESSIONTIMEOUT [number | UNLIMITED]
v To create a group with a session timeout, use the following syntax:
CREATE GROUP name WITH SESSIONTIMEOUT [number | UNLIMITED]
v To modify a user's session timeout, use the following syntax:
ALTER USER username WITH SESSIONTIMEOUT [number | UNLIMITED]
v To modify a group's session timeout, use the following syntax:
ALTER GROUP name WITH SESSIONTIMEOUT [number | UNLIMITED]
Session priority
You can define the default and maximum priority values for a user, a group, or as
the system default. The system determines the value to use when the user connects
to the host and executes SQL commands.
The possible priorities are critical, high, normal, low, or none.
The default priority for users, groups, and the system is none. If you do not set
any priorities, user sessions run at normal priority.

v The syntax to set system the default and maximum priority is:
SET SYSTEM DEFAULT [DEFPRIORITY | MAXPRIORITY ] to [CRITICAL |
HIGH | NORMAL | LOW | NONE]
v The syntax to create a group and set the default priority is:
CREATE GROUP group_name WITH DEFPRIORITY TO HIGH;
Related concepts:
Chapter 15, “Workload management,” on page 15-1
workload.
Logging Netezza SQL information

You can log information about all user or application activity on the server, and
you can log information that is generated by individual Windows clients.
Related reference:
Logging Netezza SQL information on the server

About this task
To log information on the server, complete the following steps:
Procedure
1. Using any text editor, modify the file /nz/data/postgresql.conf.
2. Add or change the following parameter: debug_print_query = true
Results
The system writes log information to the /nz/kit/log/postgres/pg.<date>.log file.

Related reference:
Logging Netezza SQL information on the client

About this task
To log information on the client Windows system, complete the following steps:
Procedure
1. Click Start > Settings > Control Panel > Data sources (ODBC).
2. In the ODBC Data Source Administration screen, click the System DNS tab.
3. Select NZSQL > Configure.
4. In the NetezzaSQL ODBC Datasource Configuration screen, enter information
about your data source, database, and server.
5. Select Driver Options.
6. In the Netezza ODBC Driver Configuration, select the CommLog check box.
This action causes the system to create a file that contains the following
information:
v The connection string

v The SQL commands that executed
v The first tuple of data returned
v The number of tuples returned
Results
The system writes log information to the file specified in the Commlog check box
(for example, C:\nzsqlodbc_xxxx.log).
Group public views

About this task
During database initialization, IBM Netezza grants the group public list and select
privileges for system views that retrieve information about users.
The following table describes some common system views and the type of
information that the view provides. In some cases, the view returns more than the
information listed in the table.
Table 11-10. Public views
View name Data returned
_v_aggregate Objid, aggregate name, owner, and create date
_v_database Objid, Database name, owner, and create date
_v_datatype Objid, data type, owner, description, and size
_v_function Objid, function name, owner, create date, description, result
type, and arguments
_v_group Objid, Group name, owner, and create date
_v_groupusers Objid, Group name, owner, and user name
_v_operator Objid, operator, owner, create date, description, opr name, opr
left, opr right, opr result, opr code, and opr kind
_v_procedure Objid, procedure, owner, create date, object type, description,
result, number of arguments, arguments, procedure signature,
built in, procedure source, proc, executed as owner
_v_relation_column Objid, object name, owner, create date, object type, attr number,
attr name, attr type, and not null indicator
_v_relation_column_def Objid, object name, owner, create date, object type, attr number,
attr name, and attr default value
_v_relation_keydata Database owner, relation, constraint name, contype, conseq, att
name, pk database, pk owner, pk relation, pk conseq, pk att
name, updt_type, del_type, match_type, deferrable, deferred,
constr_ord
_v_sequence Objid, seq name, owner, and create date
_v_session ID, PID, UserName, Database, ConnectTime, ConnStatus, and
LastCommand
_v_table Objid, table name, owner, and create date
_v_table_dist_map Objid, table name, owner, create date, dist attr number, and dist
attr name
_v_user Objid, user name, owner, valid until date, and create date
_v_usergroups Objid, user name, owner, and group name

Table 11-10. Public views (continued)
View name Data returned
_v_view Objid, view name, owner, create date, rel kind, rel checks, rel
triggers, has rules, unique keys, foreign keys, references, has p
keys, and number attributes
The following table describes some views that show system information. You must
have administrator privileges to display these views.
Table 11-11. System views
View name Output
_v_sys_group_priv GroupName, ObjectName, DatabaseName, Objecttype, gopobjpriv,
gopadmpriv, gopgobjpriv, and gopgadmpriv
_v_sys_index objid, SysIndexName, TableName, and Owner
_v_sys_priv UserName, ObjectName, DatabaseName, aclobjpriv, acladmpriv,
aclgobjpriv, and aclgadmpriv
_v_sys_table objid, SysTableName, and Owner
_v_sys_user_priv UserName, ObjectName, DatabaseName, ObjectType, uopobjpriv,
uopadmpriv, uopgobjpriv, and uopgadmpriv
_v_sys_view objid, SysViewName, and Owner

Chapter 12. Manage user content on the Netezza appliance
Unlike other database solutions, the IBM Netezza appliance does not require a
database administrator (DBA) to manage and control user databases. Instead, there
are a few system administration tasks that relate to the creation and management
of the user content that is stored on the system.
This section describes some basic concepts of Netezza databases, and some
management and maintenance tasks that can help to ensure the best performance
for user queries.
You can manage Netezza databases and their objects by using SQL commands that
you run through the nzsql command and by using the IBM Netezza Performance
Portal, NzAdmin tool, and data connectivity applications like ODBC, JDBC, and
OLE DB. This section focuses on running SQL commands (shown in uppercase,
such as CREATE DATABASE) from the nzsql command interface to perform tasks.
Databases and user tables

On a new IBM Netezza system, there is typically one main database, system, and a
database template, master_db. Netezza uses the master_db as a template for all
other user databases that are created on the system. In the Netezza design, the
terms database and catalog are synonyms. Netezza uses the term database to
define a collection of entities such as schemas, tables, views, synonyms, and other
objects.
Initially, only the admin user can create databases, but the admin user can grant
other users permission to create databases as described in Chapter 11, “Security
and access control,” on page 11-1 You cannot delete the system database. The
admin user can also make another user the owner of a database, which gives that
user admin-like control over that database and its contents.
The database creator becomes the default owner of the database. The owner can
remove the database and all its objects, even if other users own objects within the
database.
Starting in Release 7.0.3, Netezza supports the ability to define multiple schemas
within each database. You can use schemas to organize the objects, as well as to
give users areas within the database for development and testing. For example,
within the database Prod, you could have different schemas for different users,
where they can define different objects such as tables, views, and so on. Each
schema has an owner, who has full privileges to all objects in the schema. Users
can be granted access to schemas of the database, and they can view or manage
objects in that schema, but they will not see or be able to manage objects in other
schemas unless they are explicitly granted privileges to that schema and its objects.
In addition, schemas allow you to reuse object names. For example, you could
have a table tab1 in schema1 and table tab1 in schema2. Although they share the
same name, those two tab1 tables are different tables.
Note: The word schema has several definitions. The most common usage in a
database management system refers to the definition of a database, its objects, and
the rules for how those objects are related and organized in the database.
Throughout the Netezza documentation, the word schema can be found in both

contexts. The surrounding text will help to clarify if the term schema means an
object definition or the schema object type.
Netezza database schema overview

The Netezza system does not support multiple schemas by default. Starting in
release 7.0.3, you can configure the system for multiple schema support.
In previous releases, the Netezza system supported one default schema per
database. The default and only schema matched the name of the database user
who created the database. If the ownership for the database changed, the schema
name would also change to match. If users specified a schema for objects, the
Netezza system ignored the schema and used the default schema for all operations.
For Netezza systems running release 7.0.3 or later, you can configure the system to
support schemas within a database. If you enable this support, the admin user and
privileged users can create and manage schemas. The system also validates the
schema information, and you can configure whether invalid schemas return a
warning or an error. For example, you can configure the system to return an error
for any queries that specify an invalid or non-existent schema, or you can
configure the system to return a warning message for queries that use an invalid
schema and to use the default schema for a database.
Enable multiple schema support

To enable multiple schema support, use the following procedure:
Procedure
2. Using a text editor, open the /nz/data/postgresql.conf file.
3. Locate the enable_schema_dbo_check variable and uncomment it by deleting the
# character at the beginning of the line.
4. Change the value of the variable to one of the following values:
v 0 (the default) places the system in legacy behavior where users cannot
create, manage, set, or drop schemas. The system ignores any schema
information and uses the current schema for the database to which the client
is connected.
v 1 enables multiple schema support in limited mode. Users can create, alter,
set, and drop schemas. If a query references an invalid schema, the system
displays a warning message and uses the current schema for the database
session or a database’s default schema for cross-database queries.
v 2 enables enforced support for multiple schemas. Users can create, alter, set,
and drop schemas. If a query references an invalid schema, the query returns
an error.
5. Save the changes to the postgresql.conf file and close the file.
6. Run the nzstop and then the nzstart commands to restart the Netezza software
for the change to take effect.
Results
After restarting the systems, permitted users can create and manage schemas
within a database.

Disable multiple schema support
If your IBM Netezza system supports multiple schemas in a database, you can
disable support by changing the enable_schema_dbo_check variable and restarting
the software.
Following the steps in “Enable multiple schema support” on page 12-2, change the
value of the enable_schema_dbo_check variable to 0 and restart the Netezza
software. Use caution when you disable the multiple schema support, because the
schemas still exist in the databases but users cannot create, alter, drop, or use the
SET SCHEMA command to change to any schemas that are not the database
default schema. Users can still reference the schemas in object names within their
queries.
In most cases, disabling schema support is usually done only if you must
downgrade a Netezza system to a release before 7.0.3 where multiple schemas per
database are not supported.
Table size and storage space

When you create a table, the table does not consume any space on the data slices
until you insert one or more rows. As you insert each row to the table, the IBM
Netezza system allocates a minimum of one extent, which is defined as 3 MB of
storage space, on each data slice that stores a row of the table. Each extent is
divided into 24 128-KB pages (also called a block). The system uses each 128-KB
page as needed to store the table rows. When all 24 pages of an extent are used,
the system allocates another 3-MB extent to hold more rows for the table on that
data slice.
Note: The extent and page sizes maximize the performance of read operations
within the Netezza system. The extent size maximizes the performance of the disk
scan operations, and the page size maximizes the performance of the FPGA as it
reads the data that streams from disk.
For example, assume that you create a table and insert only one row to the table.
The system allocates one 3 MB extent on a data slice to hold that row. The row is
stored in the first 128-KB page of the extent. If you view the table size by using a
tool such as the NzAdmin interface, the table shows a Bytes Allocated value of 3
MB (the allocated extent for the table), and a Bytes Used value of 128 KB (the used
page in that extent).
For tables that are well distributed with rows on each data slice of the system, the
table allocation is a minimum of 3 MB x <numberOfDataSlices> of storage space. If
you have an evenly distributed table with 24 rows on an IBM PureData System for
Analytics N1001-002 or IBM Netezza 1000-3 system, which has 24 data slices, the
table allocates 3 MB x 24 extents (72 MB) of space for the table. That same table
uses 128 KB x 24 pages, or approximately 3 MB of disk space.
The Bytes Allocated value is always larger than the Bytes Used value. For small
tables, the Bytes Allocated value might be much larger than the Bytes Used value,
especially on multi-rack Netezza systems with hundreds of data slices. For larger
tables, the Bytes Allocated value is typically much closer in size to the Bytes Used
value.
Chapter 12. Manage user content on the Netezza appliance 12-3

Disk space usage in tables
As a best practice, design your tables to use only the disk space you require. For
example, use the fewest digits of precision in numerics to save space, and do not
set user-controllable sizes to their maximum values when smaller sizes are
sufficient.
The following table describes the amount of disk space the following data types
use.
Table 12-1. Data type disk usage
Data type Usage
big integers (INT8) 8 bytes
integers (INT4) 4 bytes
small integers (INT2) 2 bytes
tiny integers (INT1) and bools 1 byte
numerics of more than 18 digits of precision 16 bytes
numerics with 10 - 18 digits 8 bytes
numerics of 9 or fewer digits 4 bytes
float8s 8 bytes
float4s 4 bytes
times with time zone and intervals 12 bytes
times and timestamps 8 bytes
dates 4 bytes
char(16) 16 bytes
char(n*) and varchar(n) N+2, or fewer, bytes, depending on
actual content
The char data types of more than 16 bytes are
represented on disk as if they were varchar data
types of the same nominal size.
char(1) 1 byte
nchar(n*) and nvarchar(n) N+2 to (4 * N) + 2
The nchar and nvarchar characters are always

stored as if they were nvarchars.
Keep in mind the following characteristics of IBM Netezza tables:

v In all tables, every record also includes three 8-byte special fields that represent
a rowid, the transaction ID of the transaction that created the row, and the
transaction ID of the transaction that deleted the row (which is 0 if the row is
not deleted). These columns are referred to as the special columns or specials.
v Every varchar data type whose declared size is greater than 16 and whose actual
content is an odd number of bytes gets a pad byte.
v Most records also include a header that consists of a length (2 bytes) and a null
vector (N/8 bytes, where N is the number of columns in the record). The system
rounds up the size of this header to a multiple of 4 bytes. The only time a record
does not contain a header is if there are no nullable columns and no
variable-sized columns (varchar and char data types over 16 bytes).
v Because every record begins on a 4-byte boundary, round up your overall record
size accordingly.

v The smallest unit of allocation on a data slice is an extent, which currently is 3
MB of disk space. This number could change in future releases of the software.
Database and table guidelines

When you are working with database tables, keep in mind the following
guidelines:
v Pick the right data type or pick the right size. For example:
– Use date (4 bytes) rather than datetime (8 bytes).
– Use int1 (1 byte) or INT2 (2 bytes) rather than integer (4 bytes).
v Use the same data type and size for columns that you join against.
v Specify NOT NULL for columns, whenever possible.
– NOT NULL requires less processing/instructions.
– NOT NULL requires (slightly) less storage.
v Select a good distribution key, as described in “Distribution keys” on page 12-6.
v If necessary, specify organizing keys to improve queries on large fact tables, as
described in “Clustered base tables” on page 12-12.
v Periodically generate statistics for the tables. See “Database statistics” on page
12-15.
Row IDs in tables

The rowid is a common feature in most databases. It identifies a specific record in
the database. The rowid is guaranteed to be unique within a table and unique
across the entire system, but not necessarily sequential within a table.
When you run the nzload command, the IBM Netezza host creates records and
assigns rowids. The SPUs can also create records and assign rowids, which
happens when you use the command CREATE TABLE <tablename> AS SELECT.
The system gives the host and each of the SPUs a block of sequential rowids that
they can assign. When they use up a block, the system gives them another block,
which explains why the rowids within a table are not always sequential.
The system stores the rowid with each database record. It is an 8-byte integer
value.
You can use the rowid keyword in a query to select, update, or delete records. For
example:
SELECT rowid, lname FROM employee_table;
UPDATE employee_table SET lname = 'John Smith' WHERE rowid = 234567;
Querying by some other field, such as name, might be difficult if you have ten
John Smiths in the database.
In a new installation, the initial rowid value is 100,000. The next available rowid
value is stored in the /nz/data/RowCounter file.
Transaction IDs
Transaction IDs (xids) are sequential in nature. Each database record includes two
xid values:
v A transaction ID that created the record
v A transaction ID that deleted the record (which is set to 0 if it is not deleted)

When the system updates a record, it deletes the original record, inserts a new
record, and preserves the rowid.
Because the system does not update records in place on the disk, data integrity is
preserved (write once), and rollback and recovery operations are simplified and
accelerated.
When you run a query (or backup operation), the system allows the query to
access any record that was created, but not deleted, before this transaction began.
Because xid values are sequential, the system compares the create xid and delete
xid values to accomplish this.
The exception is that when a transaction begins, it generates an invisibility list of

any other active transactions (which would thus have a lower xid value). The
transaction ignores any records with a matching create xid value, and includes any
records with a matching delete xid value.
An xid is an 8-byte integer value, of which 48 bits are significant. In new

installations, the initial xid value is 1,024. The system stores the next available xid
value in the /nz/data/xid file.
The size of the xid allows for over 100 trillion transaction IDs, which would take
over 4000 years to use up at the rate of one transaction per millisecond. In actual
practice, transaction IDs in a IBM Netezza system are likely to be generated at a
slower rate and would take longer to exhaust.
Distribution keys
Each table in an IBM Netezza database has only one distribution key. The key can
consist of one to four columns of the table.
Important: You cannot update the columns that you select as distribution keys.
You can use the following Netezza SQL command syntax to create tables and
specify distribution keys:
v To create an explicit distribution key, the Netezza SQL syntax is:
CREATE TABLE <tablename> [ ( <column> [, ... ] ) ]
DISTRIBUTE ON [HASH] ( <column> [ ,... ] ) ;
The phrase DISTRIBUTE ON specifies the distribution key, the word HASH is
optional.
v To create a table without specifying a distribution key, the Netezza SQL syntax
is:
CREATE TABLE <tablename> (col1 int, col2 int, col3 int);
The Netezza system selects a distribution key. There is no way to guarantee
what that key is and it can vary depending on the Netezza software release.
v To create a random distribution, the Netezza SQL syntax is:
CREATE TABLE <tablename> [ ( <column> [, ... ] ) ]DISTRIBUTE ON RANDOM;
You can also use the NzAdmin tool to create tables and specify the distribution
key. For more information about the CREATE TABLE command, see the IBM
Netezza Database User’s Guide.

Select a distribution key
When you are choosing the columns as the distribution keys for a table, choose
columns that result in a uniform distribution of the rows and optimal access to the
data.
Consider the following factors:

v The more distinct the distribution key values, the better.
v The system distributes rows with the same distribution key value to the same
data slice.
v Parallel processing is more efficient when you distribute table rows evenly
across the data slices.
v Tables that are used together should use the same columns for their distribution
key. For example, in an order system application, use the customer ID as the
distribution key for both the customer table and the order table.
v If a particular key is used largely in equijoin clauses, then that key is a good
choice for the distribution key.
Criteria for selecting distribution keys

Use the following rules when you are selecting a unique or non-unique column as
the distribution key for the table:
v Use columns for the distribution key that distribute table rows evenly across the
data slices. The more singular the values for a column, the more optimal their
distribution.
v Use columns for the distribution key that is based on the selection set that you
use most frequently to retrieve rows from the table.
v Select as few columns as possible for the distribution key to optimize the
generality of the selection.
v Base the column selection on an equality search because if both tables distribute
on the equality columns, the system can perform the join operation locally.
v Do not use boolean keys, for example, True/False, I/0, or M/F, because the
system distributes rows with the same hash value to the same data slices; thus,
the table would be divided across only two data slices.
Related concepts:
“Specify distribution keys” on page 12-10
Choose a distribution key for a subset table

When you run a query, the results flow from the data slices to the SPUs to the host
to the application. A query can create a table (rather than return results to the
application). If you create a subset/summary table, your subset table inherits the
parent table distribution key, and the subset records are created and stored locally
on each data slice.
For example, perhaps you have a large table with many records and columns, and
want to create a summary table from it, maybe with just one day of data, and with
only some of the original columns. If the new table uses the same distribution key
as the original table, then the new records will reside on the same data slices as the
original table records. The system has no need to send the records to the host (and
consume transmission time and host processing power). Rather, the SPUs create
the records locally. The SPUs read from the same data slices and write back out to
same data slices. This way of creating a table is much more efficient. In this case,
the SPU is basically communicating with only its data slices.

Choosing the same distribution key causes the system to create the table local to
each data slice (reading from the original table, writing to the new table).
create [ temporary | temp ] TABLE table_name [ (column [, ...] ) ]
as select_clause [ distribute on ( column [, ...] ) ];
When you create a subset table or temp table, you do not specify a new
distribution key or distribution method. Instead, allow the new table to inherit the
distribution key of the parent table. This avoids the extra data distribution that can
occur because of the non-match of inherited and specified keys.
Distribution keys and collocated joins

If you have tables that are usually joined, distribute them on the same column that
you use to join the tables. The IBM Netezza system can then perform a collocated
join that minimizes data movement and provides optimal performance.
The Netezza architecture distributes processing across many individual SPUs each
with its own dedicated memory and data slices. These individual processors
operate in a “shared nothing” environment that eliminates the contention for
shared resources which occurs in a traditional SMP architecture. In a collocated
join, each SPU can operate independently of the others without network traffic or
communication between SPUs.
Dynamic redistribution or broadcasts

If your database design or data distribution precludes you from distributing certain
tables on the join key (column), the IBM Netezza system dynamically redistributes
or broadcasts the required data.
When the system redistributes data, it sends each record in the table to a single
SPU, but, which SPU depends on the record. Each SPU scans its own portions of
the table and extracts only the needed columns, determines the destination SPU,
and transmits the records across the internal network fabric. The system performs
these operations in parallel across all SPUs.
When the system broadcasts data, it sends every record in the table to every SPU.
Depending on the size of the table and the way the data is distributed, one method
might be more cost-effective than the other.
Related concepts:
“Execution plans” on page 12-28
Verify distribution
When the system creates records, it assigns them to a logical data slice based on
their distribution key value. You can use the datasliceid keyword in queries to
determine how many records are stored on each data slice and thus, whether the
data is distributed evenly across all data slices.
To check your distribution, run the following query:

select datasliceid, count(datasliceid) as “Rows”
from table_name group by datasliceid order by “Rows”;
You can also view the distribution from the NzAdmin tool. To view record
distribution for a table, you must have the following object privileges:
v List on the database
v List on the table

v Select on the table
Viewing record distribution

About this task
To view record distribution, complete the following steps:
Procedure
1. Click the Database tab on the NzAdmin tool main window.
2. In the left pane, click Databases > a database > Tables.
3. In the right pane, right-click a table, then click Record Distribution.
The Record Distribution window displays the distribution of data across all the
data slices in your system for the specific table. The Records column displays
the total number of records, the minimum number of records, the maximum
number of records, the average records per data slice, and the standard
deviation (population computation). The Distribution Columns Section displays
the distribution key columns for the table.
4. To see the specific record count for a data slice, place your cursor over an
individual data slice bar. The system displays the record count and the data
slice identifier in the status bar.
Figure 12-1. Record Distribution window
Related reference:
“Indirect object privileges” on page 11-17
The IBM Netezza system controls some objects that are indirectly based on the
privileges that are associated with the object. Objects in this category include user
sessions, transactions, load sessions, and statistics.

Data skew
The performance of the system is directly linked to uniform distribution of the
user data across all of the data slices in the system. When you create a table and
then load the data into the system, the rows of the table should be distributed
uniformly among all the data slices. If some data slices have more rows of a table
than others, the data slices with more data and the SPUs that manage them work
harder, longer, and need more resources and time to complete their jobs. These
data slices and the SPUs that manage them become a performance bottleneck for
your queries. Uneven distribution of data is called skew. An optimal table
distribution has no skew.
Skew can happen while you are distributing or loading the data into the following
types of tables:
Base tables
Database administrators define the tables within databases for the user
data.
Intra-session tables
Applications or SQL users create temp tables.
Related reference:
“Disk space threshold notification” on page 8-22
Specify distribution keys

IBM Netezza uses the table distribution key to determine how to distribute (or
stripe) the table data across all active data slices in the system. The Netezza system
requires that all tables have a distribution method, either hash or random.
When you use the commands CREATE TABLE or CREATE TABLE AS, you can
either specify the method or allow the Netezza to select one.
v With the DISTRIBUTE ON (hash) command, you can specify up to four columns
as the distribution key.
v If there is no obvious group of columns that can be combined as the distribution
key, you can specify random distribution. Random distribution means that the
Netezza distributes the data randomly across the data slices.
Random distribution results in the following:
– Reducing skew when you are loading data.
– Eliminating the need to pick a distribution key when you are loading a large
database that has many tables with few rows. In such cases, picking a good
distribution key might have little performance benefit, but it gains the
advantage of a dispersed distribution of data.
– Allowing you to verify a good distribution key by first loading the data
randomly, then by using the GENERATE STATISTICS command, and running
selects on the database columns to get the min/max and counts. With this
information, you can better choose which columns to use for the distribution
key.
– If you do not specify a distribution when you create a table, the system
chooses a distribution key and there is no way to control that choice.
Related concepts:
“Criteria for selecting distribution keys” on page 12-7

View data skew
The easiest way to check for Table Skew is to use the NzAdmin tool. To view table
skew on all tables in the system, you must have global LIST privileges on
databases and tables. If you have LIST privileges on a subset of databases, tables,
or both, then you are only able to view the skew results for those databases or
tables.
To view table skew, the IBM Netezza system must be online.
The following table displays the table skew information.

Table 12-2. Table skew
Column Description
Database The database in which the table resides.
Table The name of the table that meets or exceeds the specified skew threshold.
Skew The size difference in megabytes between the smallest data slice for a table
and the largest data slice for the table.
Min/Data The size of the smallest portion of the table on a data slice in MB.
slice
Max/Data The size of the largest portion of the table on a data slice in MB.
slice
Avg/Data The average data slice size in MB across all the data slices.
slice
Total The total table size in MB.
Finding skewed tables

About this task
With NzAdmin open and while connected to the IBM Netezza system, follow these
steps to locate tables that have a skew greater than a specific threshold:
Procedure
1. Select Tools > Table Skew.
2. In the Table Skew window, specify a threshold value in megabytes and click
OK. The skew threshold specifies the difference between the size of the
smallest data slice for a table and the size of the largest data slice for that table.
As the system checks the tables, NzAdmin displays a wait dialog that you can
cancel at any time to stop the processing.
If any table meets or exceeds the skew threshold value, the NzAdmin tool
displays the table in the window. You can sort the columns in ascending or
descending order.
Results
If no tables meet the skew threshold, the system displays the message: No tables
meet the specified threshold.

Figure 12-2. Table Skew window
Clustered base tables

A clustered base table (CBT) is a user table that contains data that is organized by
using one to four organizing keys. An organizing key is a column of the table that
you specify for clustering the table records; IBM Netezza uses the organizing keys
to group records within the table and save them in the same or nearby extents.
Netezza also creates zone maps for the organizing columns to accelerate the
performance of queries on that table that restrict using the organizing keys.
The following figure shows a simple model of a table, such as a transaction table.
In its unorganized form, the data is organized by the date and time that each
transaction occurred, and the color indicates a unique transaction. If your queries
on the table most often query by date/time restrictions, those queries run well
because the date/time organization matches the common restrictions of the
queries.
However, if most queries restrict on transaction type, you can increase query
performance by organizing the records by transaction type. Queries that restrict on
transaction type will have improved performance because the records are
organized and grouped by the key restriction; the query can obtain the relevant
records more quickly, whereas they would have to scan much more of the table in
the date/time organization to find the relevant transactions. By organizing the data
in the table so that commonly filtered data is located in the same or nearby disk
extents, your queries can take advantage of zone maps to eliminate unnecessary
disk scans to find the relevant records.

Figure 12-3. Organizing tables with CBTs
CBTs are most often used for large fact or event tables that can have millions or
billions of rows. If the table does not have a record organization that matches the
types of queries that run against it, scanning the records of such a large table
requires a lengthy processing time as full disk scans can be needed to gather the
relevant records. By reorganizing the table to match your queries against it, you
can group the records to take advantage of zone maps and improve performance.
CBTs offer several benefits:

v CBTs support “multi-dimension” lookups where you can organize records by
one, two, three, or four lookup keys. In the example that is shown in the
previous figure, if your queries commonly restrict on transaction type and store
ID, you can organize records by using both of those keys to improve query
performance.
v CBTs improve query performance by adding more zone maps for a table because
the organizing key columns are also zone mapped (if the organizing column
data type supports zone maps).
v CBTs increase the supported data types for zone-mapped columns to improve
performance for queries that restrict along multiple dimensions.
v CBTs incrementally organize data within your user tables in situations where
data cannot easily be accumulated in staging areas for pre-ordering before
insertions/loads. CBTs can help you to eliminate or reduce pre-sorting of new
table records before a load/insert operation.
v CBTs save disk space. Unlike indexes, materialized views and other auxiliary
data structures, CBTs do not replicate the base table data and do not allocate
more data structures.
Organizing keys and zone maps

Organizing keys and zone maps work together to improve the IBM Netezza
system's ability to identify the data that is saved within specific extents of the
database.
Zone maps summarize the range of data inside the columns of the records that are
saved in a disk extent; organizing keys help to narrow the range of data within the
extent by grouping the columns that you most often query. If the data is well
organized within the extent and the zone maps have smaller “ranges” of data,
queries run faster because Netezza can skip the extents that contain unrelated data
and direct its resources to processing the data that matches the query.

Select organizing keys
With IBM Netezza, you can specify up to four organizing keys when you create or
alter a CBT; however, it is rare that you would use four keys. Most CBTs typically
use one, two, or three keys at most.
As a best practice, review the design and columns of your large fact tables and the
types of queries that run against them. If you typically run queries on one
dimension, such as date, you can load the data by date to take advantage of the
zone maps. If you typically query a table by two dimensions, such as by storeId
and customerID for example, CBTs can help to improve the query performance
against that table.
The organizing keys must be columns that can be referenced in zone maps. By
default, Netezza creates zone maps for columns of the following data types:
v Integer (1-byte, 2-byte, 4-byte, and 8-byte)
v Date
v Timestamp
In addition, Netezza also creates zone maps for the following data types if
columns of this type are used as the ORDER BY restriction for a materialized view
or as the organizing key of a CBT:
v Char, all sizes, but only the first 8 bytes are used in the zone map
v Varchar, all sizes, but only the first 8 bytes are used in the zone map
v Nchar, all sizes, but only the first 8 bytes are used in the zone map
v Nvarchar, all sizes, but only the first 8 bytes are used in the zone map
v Numeric, all sizes up to and including numeric(18)
v Float
v Double
v Bool
v Time
v Time with timezone
v Interval
You specify the organizing keys for a table when you create it (such as using the
CREATE TABLE command), or when you alter it (such as using ALTER TABLE).
When you define the organizing keys for a table, Netezza does not automatically
reorganize the records; you use the GROOM TABLE command to start the
reorganization process.
You can add to, change, or drop the organizing keys for a table by using ALTER
TABLE. The additional or changed keys take effect immediately, but you must
groom the table to reorganize the records to the new keys. You cannot drop a
column from a table if that column is specified as an organizing key for that table.
Reorganize the table data

After you specify the organizing key or keys for a table, records are inserted into
the CBT as they would be for a non-CBT table. When you run the GROOM TABLE
command, IBM Netezza reorganizes the records that are based on the specified
keys.

The GROOM TABLE command performs two operations that are important to the
user tables on your system:
v It organizes the records for a table so that your related records are relocated to
the same extents.
v It removes the deleted and outdated records in user tables to reclaim disk space
on your system.
The GROOM TABLE command processes and reorganizes the table records in each
data slice in a series of steps. Users can do tasks such as SELECT, UPDATE,
DELETE, and INSERT operations while the online data grooming is taking place.
The SELECT operations run in parallel with the groom operations; the INSERT,
UPDATE, and DELETE operations run serially between the groom steps. For CBTs,
the groom steps are slightly longer than for non-CBT tables, so INSERT, UPDATE,
and DELETE operations might pend for a longer time until the current step
completes.
Note: When you specify organizing keys for an existing table to make it a CBT, the
new organization can affect the compression size of the table. The new
organization can create sequences of records that improve the overall compression
benefit, or it can create sequences that do not compress as well. Following a groom
operation, your table size can change somewhat from its size compared to the
previous organization.
Copy clustered base tables

If you copy a CBT by using a command similar to CREATE TABLE AS, the target
table does not inherit the organizing keys of the base table. You must use an
ALTER TABLE ORAGNIZE ON command to apply the organizing keys that you
want to use for the target table.
Database statistics
For the system to create the best execution plan for a query, it evaluates what it
knows about the database tables that it accesses. Without up-to-date statistics, the
system uses internal, default values that are independent of the actual table and
which result in suboptimal queries with long run times.
The following table describes the statistics information.

Table 12-3. Database information
Element Description
Per table Number of records
Per column v Minimum value
v Maximum value
v Null counts (per column)
v Number of distinct values (also called dispersion)
The system uses statistics for many purposes:

v Based on the number of records, the number of distinct values for a column, and
assuming uniform distribution between the min and max values, the optimizer
estimates the number of relevant rows and determines which is the smaller of
two join tables.

v Based on the min and max values, the optimizer determines what type of math
needs to be done (for example, 64-bit or 128-bit).
v If there are nulls in the database tables, then during code generation the system
must generate more code to test and check fields for null values. Extra code
means extra CPU cycles during execution time.
The GENERATE STATISTICS command collects this information. If you have the
GenStats privilege, you can run this command on a database, table, or individual
columns. By default, the admin user can run the command on any database (to
process all the tables in the database) or any individual table.
The admin user can assign other users this privilege. For example, to give user1
privilege to run GENERATE STATISTICS on one or all tables in the DEV database,
the admin user must grant user1 LIST privilege on tables in the system database,
and GENSTATS from the dev database, as in these sample SQL commands:
SYSTEM(ADMIN)=> GRANT LIST ON TABLE TO user1;
DEV(ADMIN)=> GRANT GENSTATS ON TABLE TO user1;
For more information about the GenStats privilege, see Table 11-1 on page 11-10.
The following table describes the nzsql command syntax for these cases.
Table 12-4. Generate statistics syntax
Description Syntax
A database (all tables) GENERATE STATISTICS;
A specific table (all columns) GENERATE STATISTICS ON table_name;
Individual columns in a table GENERATE STATISTICS ON my_table(name, address,
zip);
The GENERATE STATISTICS command reads every row in every table to

determine dispersion values (no sampling). It provides the most accurate and best
quality statistics.
Related concepts:
“Execution plans” on page 12-28
“Database statistics after restore” on page 13-30
After a restore, use the GENERATE STATISTICS command to update your
database statistics. When you use the nzhostrestore command to restore host data,
you do not have to regenerate statistics because the command restores the
statistics.
Maintain table statistics automatically

The IBM Netezza system automatically maintains database statistics and estimated
dispersion statistics, which are not as accurate as the statistics that the system
maintains when you run the GENERATE STATISTICS command. These statistics
are, however, generally better than no statistics.
The Netezza system maintains certain statistics when you perform database
operations.
v When you use the CREATE TABLE AS command, the system maintains the
min/max, null, and estimated dispersion values automatically.
v When you use the INSERT or UPDATE commands, the system maintains the
min/max values for all non-character fields.

v When you use the GROOM TABLE command to reclaim deleted records, the
system leaves the min/max, null, and estimated dispersion values unchanged,
and updates the zone map.
Because the groom process merely physically removes records that were
logically deleted, their removal has no effect on any statistics, though it does
affect where in the table the remaining records are, hence the effect on zone
maps.
The following table describes when the Netezza automatically maintains table
statistics.
Table 12-5. Automatic Statistics
Dispersion
Command Row counts Min/Max Null (estimated) Zone maps
CREATE TABLE AS yes yes yes yes yes
INSERT yes yes no no yes
DELETE no no no no no
UPDATE yes yes no no yes
GROOM TABLE no no no no yes
GENERATE STATISTICS command

Although the IBM Netezza system automatically maintains certain statistics, you
might want to run GENERATE STATISTICS command periodically, or in the
following cases:
v When you have significantly changed the nature of your database, that is,
increased or decreased the number of distinct values, expanded or reduced the
min/max values on joinable or groupable fields, or increased or decreased the
size of your database.
v When you have static tables that you intend to keep for a long time
v When you have queries that involve three or more joins
v When you change your tables and observe slower performance when querying
the updated tables
v When you have columns that are used in WHERE, SORT, GROUP BY, or
HAVING clauses
v When you have temporary tables that contain many rows and that are used in
JOIN clauses
For more information about the GENERATE STATISTICS command, see the IBM
Related concepts:
“Groom tables” on page 12-20
Just in Time statistics

Transparently to users, the system automatically generates Just in Time (JIT)
statistics on user tables to help the optimizer refine planning.
JIT statistics are not run on system tables, external tables, or virtual tables. JIT
statistics improve selectivity estimations when a table contains data skew or when
there are complex column/join restrictions. The system also uses JIT statistics to
avoid broadcasting large tables that were estimated to be small based on available

statistics. The overhead of these on-the-fly statistics is negligible when compared to
the overall improved query performance and total query time.
JIT statistics use sampler scan functionality and zone map information to
conditionally collect several pieces of information:
v The number of rows that are scanned for the target table
v The number of extents that are scanned for the target table
v The number of maximum extents that are scanned for the target table on the
data slices with the greatest skew
v The number of rows that are scanned for the target table that apply to each join
v The number of unique values for any target table column that is used in
subsequent join or group by processing
This information is conditionally requested for and used in estimating the number
of rows that result from a table scan, join, or “group by” operation.
Note: JIT statistics do not eliminate the need to run the GENERATE STATISTICS
command. While JIT statistics help guide row estimation, there are situations
where the catalog information calculated by GENERATE STATISTICS is used in
subsequent calculations to complement the row estimations. Depending on table
size, the GENERATE STATISTICS process does not collect dispersion because the
JIT statistics scan estimates it on-the-fly as needed.
The system automatically runs JIT statistics for user tables when it detects the
following conditions:
v Tables that contain more than 5,000,000 records.
v Queries that contain at least one column restriction.
v Tables that participate in a join or have an associated materialized view. JIT
statistics are integrated with materialized views to ensure that the exact number
of extents is scanned.
The system runs JIT statistics even in EXPLAIN mode. To check whether JIT
statistics were run, review the EXPLAIN VERBOSE output and look for cardinality
estimations that are flagged with the label JIT.
Zone maps
Zone maps are automatically generated internal tables that the IBM Netezza
system uses to improve the throughput and response time of SQL queries against
large grouped or nearly ordered date, timestamp, byteint, smallint, integer, and
bigint data types.
Zone maps reduce disk scan operations that are required to retrieve data by
eliminating records outside the start and end range of a WHERE clause on
restricted scan queries. The IBM Netezza Storage Manager uses zone maps to skip
portions of tables that do not contain rows of interest and thus reduces the number
of disk pages and extents to scan and the search time, disk contention, and disk
I/O.
Column-oriented and table-oriented zone maps

Starting with NPS release 7.2.1, you can use column-oriented or table-oriented zone
maps.

For releases before 7.2.1, Netezza appliances use a column-oriented zone map
structure where all zone map statistics for the same column number across all
tables are stored together in the dataslice.
In release 7.2.1, Netezza adds the table-oriented zone map feature that organizes
the zone maps such that the zone map statistics for all columns from the same
table are stored together in the dataslice. Table-oriented zone maps are optimized
for improved performance of incremental (or trickle) loads. Table-oriented zone
maps also minimize interactions between concurrent loads to a subset of tables in
the system, from queries running against a different subset of tables. The zone map
data remains the same, so table-oriented zone maps provide the same benefit for
query performance.
The zone map format is a system-wide setting. For new systems that are initialized
with NPS 7.2.1, the default is to use table-oriented zone maps for new user tables.
When you upgrade an NPS appliance to release 7.2.1, the existing column-oriented
zone maps are preserved.
To change column-oriented zone maps to table-oriented zone maps, run the

nzzonemapformat -table command. You must pause the system by using the
nzsystem pause command, run the conversion command, and then resume the
system by using the nzsystem resume command. The conversion process could take
from a few minutes to an hour, depending on the amount of data stored on the
appliance. Take that time into account when scheduling the service window to
perform the conversion to minimize the impact on database users and applications.
You can convert back to column-oriented zone maps using the command
nzzonemapformat -column. You must pause the system to convert back to
column-oriented zone maps as well.
If your system uses table-oriented zone maps, you cannot downgrade to a release
before 7.2.1 until you convert the zone maps back to column-oriented format. The
downgrade process stops with a message that zone maps must be converted back
to column-oriented zone maps if table-oriented zone maps are present. After
performing the zone map conversion using the nzzonemapformat utility, run the
downgrade again.
Zone maps and rolling history

Zone maps take advantage of the inherent ordering of data and are beneficial for
large grouped or nearly ordered data. This type of data is common in call records,
web logs, and financial transaction databases.
Ordered table data might contain rolling history data that represents many months
or years of activity. A rolling history table typically contains many records. Each
day, the new data is inserted and the data for the oldest day is deleted. Because
these rows are historical in nature, they are rarely, if ever, modified after insertion.
Typically, users run queries against a subset of history such as the records for one
week, one month, or one quarter. To optimize query performance, zone maps help
to eliminate scans of the data that is outside the range of interest.
Zone maps automatic vertical partitioning

The IBM Netezza system automatically creates zone maps and refreshes existing
zone maps on each data slice when you insert, update, load data into tables, or
generate statistics.

For every column in a table that has a date, timestamp, byteint, smallint, integer,
bigint data type, the system determines the minimum and maximum values per
page and extent and updates the zone map table. When a user truncates or drops a
database user table, the system updates the zone map and removes all records in
the zone map that are associated with the table.
Groom tables
As part of your routine database maintenance activities, plan to recover disk space
that is occupied by outdated or deleted rows. In normal IBM Netezza operation, an
update or delete of a table row does not remove the old tuple (version of the row).
This approach benefits multiversion concurrency control by retaining tuples that
can potentially be visible to other transactions. Over time however, the outdated or
deleted tuples are of no interest to any transaction. After you capture them in a
backup, you can reclaim the space that they occupy by using the SQL GROOM
TABLE command.
Note: Starting in Release 6.0, you use the GROOM TABLE command to maintain
the user tables by reclaiming disk space for deleted or outdated rows, and to
reorganize the tables by their organizing keys. The GROOM TABLE command
processes and reorganizes the table records in each data slice in a series of steps.
Users can do tasks such as SELECT, UPDATE, DELETE, and INSERT operations
while the data grooming is taking place. The SELECT and INSERT operations run
in parallel with the groom steps; any UPDATE and DELETE operations run serially
between the groom steps. For details about the GROOM TABLE command, see the
Keep in mind the following when you groom tables to reclaim disk space:
v Groom tables that receive frequent updates or deletes more often than tables that
are seldom updated.
v If you have a mixture of large tables, some of which are heavily updated and
others that are seldom updated, you might want to set up periodic tasks that
routinely groom the frequently updated tables.
v Grooming deleted records has no effect on your database statistics because the
process physically removes records that were already “logically” deleted. When
you groom a table, the system leaves the min/max, null, and estimated
dispersion values unchanged.
v Reclaiming records does affect where the remaining records in the table are
located. The system updates the zone map accordingly.
v If you truncated a table and there are in-flight transactions that started before
the TRUNCATE query, note that the groom process does not reclaim the
truncated rows until after the last in-flight transaction has committed or aborted.
Tip: When you delete all the contents of a table, consider using the TRUNCATE
command rather than the DELETE command, which eliminates the need to run the
GROOM TABLE command.
Related concepts:
“GENERATE STATISTICS command” on page 12-17
GROOM and the nzreclaim command

When you run the GROOM TABLE command, it removes outdated and deleted
records from tables while allowing you access to all tables in the system.

In previous releases, the nzreclaim command was used to perform reclaims.
Starting in Release 6.0, the nzreclaim command is deprecated, although it is still
available for compatibility with an earlier version. You should use the GROOM
TABLE command. If you have scripts that use the nzreclaim command, migrate
them to use GROOM TABLE as well. The nzreclaim command syntax has changed
in Release 6.0. For example, the -scanblocks and -scanrecords options are not
supported and return an error.
Several examples follow:

v To use the GROOM TABLE command in a SQL session:
MYDB.SCHEMA(USER1)=> GROOM TABLE ORDERS;
NOTICE: Groom processed 25 pages; purged 9 records; scan size
shrunk by 9 pages; table size shrunk by 9 extents.
GROOM RECORDS ALL
v If you created scripts to run nzreclaim from the command line as in the
previous example, you can update those scripts to use the new SQL GROOM
TABLE command as in the following example:
[nz@nzhost ~]$ nzsql mydb -u user1 -pw password -c "groom table
mynation"
v If you use the nzreclaim command to groom a table:
[nz@nzhost ~]$ nzreclaim -db mydb -u user1 -pw password -t mynation
nzsql -u user1 -pw password mydb -c"groom table mynation " 2>&1
NOTICE: Groom processed 25 pages; purged 9 records; scan size
shrunk by 9 pages; table size shrunk by 9 extents.
GROOM RECORDS ALL
As shown in the example, the nzreclaim command calls the GROOM TABLE
command to update and reclaim the table. As a best practice, use the GROOM
TABLE command instead of nzreclaim.
Related reference:
“The nzreclaim command” on page A-45
Use the nzreclaim command to recover disk space that is used by updated or
deleted data by using the GROOM TABLE command.
Identify clustered base tables that require grooming

The /nz/kit/bin/adm/tools/cbts_needing_groom script identifies CBTs in one,
several, or all databases that require grooming. CBTs that have many ungroomed
or empty pages can slow the performance of queries that use those tables.
The script lists any CBTs in the specified databases that have 960 or more
ungroomed or empty pages in any one data slice. The script outputs the SQL
commands that identify the databases and the GROOM TABLE commands for any
CBTs that meet the groom threshold.
You can run these commands from a command line, or output the command to a
file that you can use as an input script to the nzsql command. You can use script
options to specify the databases to search and the threshold for the number of
ungroomed pages in a data slice.
The script has the following syntax:

/nz/kit/bin/adm/tools/cbts_needing_groom [-h] {-alldbs | -db db_name
[db_name ...]} [-th threshold]

Table 12-6. The cbts_needing_groom input options
Option Description
-h Displays the usage for the script.
-alldbs Checks all the databases in the system for CBTs that require
grooming.
-db db_name Checks the specified database in the system for CBTs that require
[db_name...] grooming. You can specify one or more database names to check
only those databases.
-th threshold Specifies the minimum number of empty or deleted pages in at
least one data slice for CBTs to be designated as needing groom.
The default is 960. Although the valid values are 0 - 2147483647,
the practical maximum is about 24,000 pages. Keep in mind that a
value that is too high causes the command to ignore CBTs that
would benefit from a groom operation, while a number that is too
low can report CBTs for which a groom is not required.
A sample script follows:

[nz@nzhost tools]$ ./cbts_needing_groom -alldbs -th 400
\c "my_db"
groom table "lineitem2"; -- 505 / 4037
The script can take a few minutes to run, depending on the number of databases
and tables that it checks. If the command finds no CBTs that meet the groom
threshold criteria, the command prompt displays with no command output. As the
sample shows, one CBT meets the user-supplied threshold criteria.
If the script reports any CBTs that would benefit from a groom, you can connect to
each database and run the GROOM TABLE command manually for the specified
table. Or, you can also direct the output of the command to a file that you can use
as an input script to the nzsql command. For example:
[nz@nzhost tools]$ ./cbts_needing_groom -alldbs -th 400 >/export/home/nz/testgrm.sql
[nz@nzhost tools]$ nzsql -f /export/home/nz/testgrm.sql
You are now connected to database "my_db".
nzsql:/export/home/nz/testgrm.sql:2: NOTICE: Groom processed 4037
pages; purged 0 records; scan size shrunk by 1 pages; table size shrunk
by 1 extents.
GROOM ORGANIZE READY
Related concepts:
“Organization percentage”
Organization percentage
When you view the status information for tables, such as using the NzAdmin
interface or various system views, the information contains an organization
percentage. For clustered base tables (CBTs), the organization percentage shows the
percentage of the table data that is organized based on the specified organizing
keys for that table. Organized tables typically have a 100% organization
percentage, while tables that are not yet organized have a 0% percentage. The
organization percentage does not apply to tables which are not CBTs.
After you specify the organizing keys for the table and load its data, you typically
run a GROOM TABLE RECORDS ALL command to reorganize the data according
to the keys. After you insert any new data in the table, update the organization by
using the GROOM TABLE RECORDS READY command to ensure that the
organization is up-to-date.

Related concepts:
“Identify clustered base tables that require grooming” on page 12-21
Groom and backup synchronization

By default, the system synchronizes your GROOM TABLE request with the most
recent backup set to avoid reclaiming rows that are not yet captured by
incremental backups. In other words, GROOM TABLE does not remove any data
that has been deleted or is outdated but which has not been saved in a backup.
For example:
1. Run a full backup.
2. Delete data B.
3. Run an incremental backup, which captures data B marked as deleted.
4. Delete D.
5. Run GROOM TABLE, which removes B but not D, because D was not captured
in the last backup.
If you maintain two backup sets for a database and you do not want the GROOM
TABLE command to use the default backup set, you can use the backupset option
to specify another backup set. Run the backup history report to learn the ID of the
backup set you want to specify.
Note: If you disable this synchronization and a subsequent incremental backup

needs information that you removed with a reclaim, nzbackup performs a full
backup instead of the incremental you requested for any reclaimed tables.
Related concepts:
“Backup History report” on page 13-20
Use the Backup History report to view information about the recent backups. You
can use the report to display information about all of the backups that were run
from the host system.
Session management
A session represents a single connection to an IBM Netezza appliance.
Sessions begin when users do any of the following actions:

v Run the nzsql command; the session ends when they enter \q (quit) to exit the
session.
v Run the nzload command, the NzAdmin tool, or other client commands; the
session ends when the command completes, or when the user exits the user
interface.
The nzsession command

You can use the nzsession command to view and manage sessions.
You must be the administrator or have the appropriate permissions to show and
manage sessions and transactions. Also, you cannot use a Release 5.0 nzsession
client command to manage sessions on an IBM Netezza system that is running a
release before 5.0.
Related reference:
“The nzsession command” on page A-49
Use the nzsession command to view and manage sessions.

View sessions
You can use the nzsession command to display the list of current user sessions
and to list the session types.
You can be logged in as any database user to use the nzsession show command;
however, some of the data that is displayed by the command can be obscured if
your account does not have correct privileges. The admin user can see all the
information.
To list all active sessions, enter:

nzsession show -u admin -pw password
ID Type User Start Time PID Database Schema State Priority

Client IP Client Command
Name
PID
----- ---- ----- ----------------------- ----- --------- ------ ------ --------
--------- ------ ------------------------
43826 sql ADMIN 24-Feb-13, 16:49:18 EST 14840 TPCH_HUGE ADMIN active normal
127.0.0.1 14839 select * from lineitem
43827 sql ADMIN 24-Feb-13, 16:49:31 EST 15093 SYSTEM ADMIN active normal
If you are a database user who does not have any special privileges, information
such as the user name, database, client PID, and SQL command display only as
asterisks:
nzsession show -u user1 -pw pass
Name
PID
----- ---- ----- ----------------------- ----- --------- ------ ------ --------
--------- ------ ------------------------
43826 sql ***** 24-Feb-13, 16:49:18 EST 14840 ***** ***** active normal
***** *****
43876 sql iser1 24-Feb-13, 16:54:27 EST 17257 SYSTEM ***** active normal
To list session types, enter: nzsession listSessionTypes

Related reference:
Abort sessions or transactions

You can use the nzsession command to abort sessions or transactions. You can
abort a transaction if you are the user admin, the owner of the session, or you
have Abort privileges for that user or group.
To abort a session, enter: nzsession abort -u admin -pw password -id 7895
Important: Do not abort system sessions because it can cause your system to fail
to restart.
You can abort SQL, client, load, backup, and restore sessions. To abort transaction
SID 31334, enter the following command:
nzsession abortTxn -u admin -pw password -id 31334

The transaction has been aborted but the session remains active. You can also use
the NzAdmin tool to abort a transaction.
Transactions
A transaction is a series of one or more operations on database-related objects,
data, or both.
Transactions provide the following benefits:

v Ensure integrity among multiple operations by allowing all or none of the
operations to take effect. You accomplish this by starting a transaction,
performing operations, and then executing either a commit or a rollback (also
called an abort).
v Provide a means of canceling completed work for a series of operations that fail
before finishing.
v Provide a consistent view of data to users, in the midst of changes by other
users. The combination of create and delete transaction IDs associated with each
data row plus IBM Netezza internal controls ensure that after a transaction
begins, new transactions or ones that have yet to be committed do not affect the
view of the data.
Transaction control and monitoring

From a management/administrative perspective:
v Using the nzsql command (or any other SQL front end), privileged users can
start, commit, and abort a transaction. User must have list object privileges on
the database to which they are connected.
v Using the nzsession command, privileged users can list and abort currently
running SQL transactions.
If the system encounters a deadlock as it is processing transactions, it aborts one of

the deadlocked transactions and displays Deadlock detected, resubmit your
request.
Transactions per system

IBM Netezza has a limit of 63 read/write transactions per system. The following
activities count against the transaction limit:
v Using a BEGIN statement or starting a transaction through ODBC, not followed
by SET TRANSACTION READ ONLY, even if you have not submitted a query
v UPDATES, DELETES, and INSERTS, even if they have not begun execution
v An update that has not finished rolling back or is being recovered after a restart
counts against the limit until the rollback completes
v Loading data with the nzload command
The following activities do not count against the read/write transaction limit:
v Committed transactions
v Transactions that have finished rolling back
v SELECT statements that are not inside a multi-statement transaction
v Transactions that create or modify temporary tables only, or modify only tables
that are created within the same transaction (for example, CREATE TABLE ...AS
SELECT...)

v Multi-statement read-only transactions (BEGIN ...SET TRANSACTION READ
ONLY)
Transaction concurrency and isolation

The ANSI/ISO SQL standard defines four levels of transaction isolation:
uncommitted read, committed read, repeatable read, and serializable. The IBM
Netezza system implements serializable transaction isolation, which provides the
highest level of consistency.
With concurrent transactions, this isolation level prevents the following:

v Dirty reads where a transaction reads data that is written by concurrent
uncommitted transactions
v Non-repeatable reads where a transaction rereads data it previously read and
finds that the data was modified by another transaction
v Phantom reads where a transaction re-executes a query that returns a set of rows
that satisfy a search condition and finds that the set of rows has changed
because of another recently committed transaction
The Netezza system does not use conventional locking to enforce consistency
among concurrently running transactions, but instead uses a combination of
multi-versioning and serialization dependency checking.
v With multi-versioning, each transaction sees a consistent state that is isolated
from other transactions that have not been committed. The Netezza hardware
ensures that the system can quickly provide the correct view to each transaction.
v With serialization dependency checking, nonserializable executions are
prevented. If two concurrent transactions attempt to modify the same data, the
system automatically rolls back the youngest transaction. This is a form of
optimistic concurrency control that is suitable for low-conflict environments such
as data warehouses.
Concurrent transaction serialization and queueing, implicit

transactions
An implicit transaction is a single SQL statement that is not framed by a BEGIN
statement.
When an implicit transaction fails serialization
The system responds as follows for an implicit transaction that fails serialization:
v The system waits for the completion of the transaction that caused the
serialization conflict.
v After that transaction finishes, either by commit or abort, the system resubmits
the waiting requests.
When the number of implicit transactions exceeds the limit
If the system reaches a limit of 63 concurrent read/write transactions and an

implicit transaction is issued that attempts to modify data, the system saves and
queues the transaction until the number of concurrent read/write transactions falls
below the limit.

Modify the default time limit
The system saves and queues implicit transactions for up to 360 minutes (the
default). If an implicit transaction waits for more than 360 minutes (or six hours),
the transaction fails and returns the error message ERROR: Too many concurrent
transactions. You can modify this default timeout setting in two ways:
v To set the value for the current session, issue the following command:
SET serialization_queue_timeout = <number of minutes>
v To make the setting global, set the variable serialization_queue_timeout in
postgresql.conf.
Concurrent transaction serialization and queueing, explicit

transactions
An explicit transaction is one that is framed within a BEGIN statement. If the
system reaches a limit of 63 concurrent read/write transactions, new transaction
requests framed by a BEGIN statement queue until the concurrent transactions falls
below 63, at which time data modification operations are permitted.
A read-only explicit transaction that issues only SELECT statements also queues
unless a SET SESSION READ ONLY is executed in the session before the BEGIN
statement.
This queuing behavior is a change from previous IBM Netezza releases, where a
BEGIN that encounters 63 concurrent read/write transactions is accepted by
Netezza but the client transaction is forced to be read-only. If you want to continue
using the previous behavior, issue SET begin_queue_if_full = false in the session
before you issue the BEGIN statement. Keep in mind that if a statement that
modifies non-temporary data is issued by such a transaction, the statement fails
and is not queued.
The following table summarizes the differences in system response in queueing

implicit and explicit transactions when the number of read/write transactions
reaches 63. In the table, note the following symbol meanings.
v X = starts executing
v E = error message
v Q = request queues
Table 12-7. The 64th read/write transaction queueing
Explicit Explicit
begin_queue_if_full=T begin_queue_if_full=T Explicit
Implicit (default) set session read only begin_queue_if_full=F
BEGIN Not Q X (read only) X (read only)
applicable
SELECT X X (after BEGIN proceeds) X X
CREATE X X E E
CREATE TABLE AS X X E E
DROP X X E E
TRUNCATE X X E E
INSERT Q X E E
DELETE Q X E E
UPDATE Q X E E

Table 12-7. The 64th read/write transaction queueing (continued)
Explicit Explicit
begin_queue_if_full=T begin_queue_if_full=T Explicit
Implicit (default) set session read only begin_queue_if_full=F
CREATE/MODIFY X X X X
TEMPORARY
TABLE
Netezza optimizer and query plans

IBM Netezza uses a cost-based optimizer to determine the best method for scan
and join operations, join order, and data movement between SPUs (that is,
redistribute or broadcast operations).
The system might redistribute data for joins, grouping aggregates, create tables, or
when loading. Decisions about redistribution are made by the planner and are
based on costs like expected table sizes. (The planner tries to avoid redistributing
large tables because of the performance impact.)
Note: Review the plan if you want to know whether the planner redistributed or
broadcast your data. The EXPLAIN VERBOSE command displays the text:
download (distribute or broadcast).
The optimizer can also dynamically rewrite queries to improve query performance.
Many data warehouses use BI applications that generate SQL that is designed to
run on multiple vendors' databases. The portability of these applications is often at
the expense of efficient SQL. The SQL that the application generates does not take
advantage of the vendor-specific enhancements, capabilities, or strengths. Hence,
the optimizer might rewrite these queries to improve query performance.
Execution plans
The optimizer uses the following statistics to determine the optimal execution plan
for queries:
v The number of rows in the table
v The number of unique or distinct values of each column
v The number of NULLs in each column
v The minimum and maximum of each column
For the optimizer to create the best execution plan that results in the best
performance, it must have the most up-to-date statistics.
Related concepts:
“Dynamic redistribution or broadcasts” on page 12-8
If your database design or data distribution precludes you from distributing certain
tables on the join key (column), the IBM Netezza system dynamically redistributes
or broadcasts the required data.
“Database statistics” on page 12-15
Display plan types

You can use EXPLAIN, HTML (also known as bubble), and text plans to analyze
how the IBM Netezza system executes a query.
To obtain these plans, do the following tasks:

v To obtain an EXPLAIN plan, add the EXPLAIN VERBOSE keyword before the
SQL statement. The system displays the output to stdout unless you redirect it
to a file.
EXPLAIN VERBOSE SELECT * FROM foo;
v To obtain an HTML plan, use either the EXPLAIN or SET command.
– The following is an example that uses EXPLAIN PLANGRAPH.
EXPLAIN PLANGRAPH SELECT * FROM foo;
With EXPLAIN PLANGRAPH, the system displays the output to the nzsql
terminal. You can copy and paste the output into a file that you can open in
your browser.
– The following is an example that uses SET.
SET enable_print_plan_html=1;
SELECT * FROM FOO;
The SET command saves the output to a file on the host. You can specify the
location for the file. For example:
SET print_plan_path = '/tmp';
In this case, the output would be saved to /tmp/plan#.html (The system
begins with the number 1 and names subsequent output sequentially.)
– Whether you use EXPLAIN PLANGRAPH or SET, the output displays the
query plan pictorially as a tree of nodes (ovals), representing how joins are
processed. Use the following characteristics to interpret the representations.
- Ovals with unbroken single lines and clear backgrounds (not shaded) are
nodes that ran on the SPUs.
- Shaded ovals represent nodes that the host (DBOS) executed.
- Ovals with dashed lines represent virtual nodes (typically subquery scans).
- Ovals with double lines represent fabric joins, which are streaming nodes
that are either broadcast or distributed.
v To obtain a text plan, use either the EXPLAIN or SET command. The system
displays the output to the nzsql terminal unless you redirect it to a file.
EXPLAIN PLANTEXT SELECT * FROM foo;
OR
SET enable_print_plan_text=1;
SELECT * FROM foo;
You can also use the NzAdmin tool to display information about queries.
Analyze query performance

To evaluate query performance, use the NzAdmin tool to determine what is
running on your system.
v View the active sessions.
v View active queries.
v Check whether any queries are queued.
v Check whether there are any long-running queries.
v Use the EXPLAIN command to display the execution plan for specific queries.
– Analyze the query plan.
– Review the estimated costs. Do they seem reasonable?
– Is the system performing table broadcasts or distributes? If there is a
broadcast, is it on a small table or small result set? If there is a distribute,
validate the distribution for the tables.
– Review the scan and join order. Is the largest table scanned last?

v Make sure that the optimizer has current statistics. If not, generate statistics.
v Evaluate table distributions. Is there a more optimal distribution strategy? If so,
change the distribution method.
v Run the query again after you have updated the statistics and changed the
distribution.
v Use EXPLAIN VERBOSE or the NzAdmin tool to review any changes in the
query plan.
Query status and history

You can use the system views, _v_qrystat and _v_qryhist, to view the status of
queries that are running and the recent query history.
Note: This version of the query history and status feature is provided for
compatibility with earlier releases and will be deprecated in a future release.
You do not need to be the administrator to view these views, but you must have
been granted List permission for the users who ran the queries and the database
objects to see the history records.
For example, to grant admin1 permission to view bob’s queries on database emp,
use the following SQL commands:
GRANT LIST ON bob TO admin1;
GRANT LIST ON emp TO admin1;
You can also use the nzstats command to view the Query Table and Query
History Table. For more information, see Table 16-12 on page 16-8 and Table 16-13
on page 16-9.
The following table lists the _v_qrystat view, which lists active queries.
Table 12-8. The _v_qrystat view
Columns Description
Session Id The ID of the session that initiated this query.
Plan Id The internal ID of the plan that is associated with this query.
Client Id The internal client ID associated with this query.
Client IP address The client IP address.
SQL statement The SQL statement. (Note that the statement is not truncated as it is
when you view a statement using the nzstats command.)
State The state number.
Submit date The date and time the query was submitted.
Start date The date and time the query started running.
Priority The priority number.
Priority text The priority of the queue when submitted (normal or high).
Estimated cost The estimated cost, as determined by the optimizer. The units are
thousandths of a second, that is, 1000 equals one second.
Estimated disk The estimated disk usage, as determined by the optimizer.
Estimated mem The estimated memory usage, as determined by the optimizer.
Snippets The number of snippets in the plan for this query.
Current Snippet The current snippet the system is processing.

Table 12-8. The _v_qrystat view (continued)
Columns Description
Result rows The number of rows in the result.
Result bytes The number of bytes in the result.
The following table describes the _v_qryhist view, which lists recent queries.
Table 12-9. The _v_qryhist view
Columns Description
Client Id The internal client ID associated with this query.
Client IP address The client IP address.
DB name The name of the database the query ran on.
User The user name.
SQL statement The SQL statement. (Note that the statement is not truncated as it is
when you view a statement using the nzstats command.)
Submit date The date and time the query was submitted.
Start date The date and time the query started running.
End date The date and time that the query ended.
Priority text The priority of the queue when submitted (normal or high).
Estimated cost The estimated cost, as determined by the optimizer.
Estimated disk The estimated disk usage, as determined by the optimizer.
Estimated mem The estimated memory usage, as determined by the optimizer.
Snippets The number of snippets in the plan for this query.
Snippet done The number of snippets that have completed.
Result rows The number of rows in the result.
Result bytes The number of bytes in the result.
Related concepts:
Chapter 14, “History data collection,” on page 14-1
A Netezza system can be configured to capture information about user activity
such as queries, query plans, table access, column access, session creation, and
failed authentication requests. This information is called history data. Database
administrators can use history data to gain insight to usage patterns.

Chapter 13. Database backup and restore
This section describes how to back up and restore data on the IBM Netezza
system. It provides general information about backup and restore methods, and
also describes how to use the third-party storage solutions that are supported by
the Netezza system.
Important: As a best practice, make sure that you schedule regular backups of
your user databases and your system catalog to ensure that you can restore your
Netezza system. Make sure that you run backups before and after major system
changes so that you have “snapshots” of the system before and after those
changes. A regular and current set of backups can protect against loss of data that
can occur because of events such as disaster recovery, hardware failure, accidental
data loss, or incorrect changes to existing databases.
General information about backup and restore methods

IBM Netezza provides several backup and restore methods to cover various data
storage and transfer needs.
v Create full and incremental backups of databases in compressed internal format
external tables by using the nzbackup command and restore them to a Netezza
system by using nzrestore command.
v Unload individual tables data in compressed internal format external tables by
using the CREATE EXTERNAL TABLE command. You load the data by using
the nzload command.
v Unload individual table data in text format external tables by using the CREATE
EXTERNAL TABLE command. You load the data by using the nzload command
on a Netezza system, but you can also load it to any database that supports text
format files.
v Create backups of the system catalog (the /nz/data directory) on the Netezza
host by using the nzhostbackup command. If the Netezza host fails, you can
reload the system catalog and metadata by using the nzhostrestore command
without a full database reload.
The following table lists the differences among the backup and restore methods.
Table 13-1. Choose a backup and restore method
nzbackup and Compressed Text format
Feature nzrestore external tables external tables
Object definition backup U - -
Full automatic database backup U - -
Manual per-table backup - U U
Manual per-table restore U U U
TM TM
Veritas NetBackup U - -
IBM Spectrum Protect (formerly U - -
Tivoli® Storage Manager)
® ®
EMC NetWorker U - -
Automatic incremental U - -
Compressed internal format U U -

Table 13-1. Choose a backup and restore method (continued)
nzbackup and Compressed Text format
Feature nzrestore external tables external tables
Non-proprietary format - - U
a a
Machine-size independent U U U
Rowid preserved U U -
Transaction ID preserved - - -
Upgrade safe U U U
Downgrade safe - - U
a
This method usually takes more time to complete than the compressed internal
format backups and loads.
Note: The backup and restore processes and messages often use the term schema
in the context of a definition, that is, the definition of database, its objects, and the
access privileges granted within the database. In these sections, the term schema
does not mean the schema object inside a database (for systems that support
multiple schemas in a database). The Netezza backup and restore features do not
support the ability to back up a database schema (that is, the object).
The CREATE EXTERNAL TABLE command and the procedures for using external
tables are described in detail in the IBM Netezza Data Loading Guide.
Veritas and NetBackup are trademarks or registered trademarks of Symantec

Corporation or its affiliates in the US and other countries. EMC and NetWorker are
registered trademarks or trademarks of EMC Corporation in the US and other
countries.
Backup options overview

The IBM Netezza system contains data that is critical to the operation of the
system and to the user databases and tables that are stored within Netezza. The
data includes the Netezza catalog metadata, the user databases and tables, and
access information such as users, groups, and global permissions. Netezza provides
a set of commands to back up and restore this information, as described in the
following table.
Table 13-2. Backup and restore commands and content
Information Backup Restore
Netezza host data (catalog metadata) nzhostbackup nzhostrestore
User databases nzbackup nzrestore
Netezza users, groups, and permissions nzbackup nzrestore
The Netezza backup processes do not back up host software such as the Linux
operating system files or any applications that you might install on the Netezza
host, such as the IBM Netezza Performance Portal client. If you accidentally
remove files in the IBM Netezza Performance Portal installation directories, you
can reinstall the IBM Netezza Performance Portal client to restore them. If you
accidentally delete Linux host operating system or firmware files, contact Netezza
Support for assistance in restoring them.

The nzbackup and nzrestore commands do not back up the analytic executable
objects that are created by the IBM Netezza Analytics feature. If you use IBM
Netezza Analytics on your Netezza system, be sure to back up the Netezza
databases, users, and global objects (by using nzbackup), the host metadata (by
using nzhostbackup) and the analytic executable objects (by using inzabackup). For
more information about backup and restore commands for the IBM Netezza
Analytics, see the User-Defined Analytic Process Developer's Guide.
The Netezza backup and restore operations can use network file system locations
and several third-party solutions such as IBM Spectrum Protect (formerly Tivoli
Storage Manager), Veritas NetBackup, and EMC NetWorker as destinations.
Note: Throughout these topics, the guide uses the terms Tivoli Storage Manager
and TSM to refer to the applications, clients, and features of the IBM Spectrum
Protect product family.
Database completeness
The standard backup and restore by using the nzbackup and nzrestore commands
provide transactionally consistent, automated backup and restore of the definitions
and data for all objects of a database, including ownership and permissions for
objects within that database. You can use these commands to back up and restore
an entire database, and to restore a specific table in a database.
The nzrestore command requires the database to be dropped or empty before you
restore the database. Similarly, before you restore a table, you must first drop the
table or use the -droptables option to allow the command to drop a table that is
going to be restored.
Portability
Before you run a backup, consider where you plan to restore the data. For
example, if you are restoring data to the same IBM Netezza system or to another
Netezza system (which can be a different model type or have a later software
release), use the compressed internal format files that are created by the nzbackup
command. The compressed internal format files are smaller and often load more
quickly than text external format files. You can restore a database that is created on
one Netezza model type to a different Netezza model type, such as a backup from
an IBM Netezza 1000-6 to a 1000-12, if the destination Netezza has the same or
later Netezza release. A restore runs slower when you change the destination
model type because the host on the target system must process and distribute the
data slices according to “data slices to SPU” topology on the target model.
When you are transferring data to a new Netezza system or when you are
restoring row-secure tables, use the nzrestore -globals operation to restore the
user, groups, and privileges (that is, the access control and security information)
first before you restore the databases and tables. If the security information
required by a row-secure table is not present on the system, the restore process
exits with an error. For more information about multi-level security, see the IBM
Netezza Advanced Security Administrator's Guide.
If you plan to load the Netezza data to a different system (that is, a non-Netezza
system), the text format external tables are the most portable. Data in text external
tables can be read by any product that can read text files, and can be loaded into
any database that can read delimited text files.
Chapter 13. Database backup and restore 13-3

Compression in backups and restores
Choosing to compress the data before a backup or unload can benefit performance
because less data travels through the fabric and less data is written to disk, which
saves space on the storage device. However, the compression process itself takes
some time, so typically the larger the table the greater the benefit from
compression.
Note: The term compression in the database backup and restore context refers to the
compressed internal format of external tables, which is different from the
compressed data blocks and tables that are created by the Compress Engine.
Throughout this section, compression refers to the compressed internal format.
A compressed binary format external table (also known as an internal format table)
is a proprietary format which typically yields smaller data files, retains information
about the IBM Netezza topology, and thus is often faster to back up and restore.
The alternative to compressed binary format is text format, which is a
non-proprietary external table format that is independent of the Netezza topology,
but yields larger files and can be slower to back up and restore.
The different backup and restore methods handle data compression in the
following manner:
v When you use the standard backup by using the nzbackup and nzrestore
commands, the system automatically uses compressed external tables as the data
transfer mechanism.
v When you use compressed external table unload, the system compresses the
data and only uncompresses it when you reload the data.
Use manually created external compressed tables for backup when you want
table-level backup or the ability to send data to a named pipe, for example,
when you use a named pipe with a third-party backup application.
v When you use text format unload, the data is not compressed. For large tables, it
is the slowest method and the one that takes up the most storage space.
Multi-stream backup
An IBM Netezza backup can be a multi-stream operation.
If you specify several file system locations, or if you use third-party backup tools
that support multiple connections, the backup process can parallelize the work to
send the data to the backup destinations. Multi-stream support can improve
backup performance by reducing the time that is required to transfer the data to
the destination.
Important: Make sure that you have information about your backup destinations.
If your Netezza database backup will be stored on multiple locations/directories
managed by different backup devices, multi-stream backups can help to improve
the data transfer rates to those different destinations. If you use multiple streams,
make sure that your storage device can accept multiple streams in parallel
efficiently so that you can avoid situations where multiple streams might contend
for a single shared resource. Consult with your backup storage administrator to
determine whether multi-stream backups are appropriate for your environment.
By default, a multi-stream nzbackup process waits up to five minutes for all of the
resources to become available to service all the requested streams. (The
host.bnrStreamInitTimeoutSec registry setting specifies the amount of time for the
nzbackup process to wait for resources to become active.) For example, a

multi-stream backup could exceed a server-side concurrency setting that controls
the number of concurrent operations that use the server. During the timeout
waiting period, if concurrent jobs finish, the required resources might then be
available for the nzbackup to proceed. If a multi-stream backup operation requests
more jobs than are allowed, or if the required resources are not available within the
timeout period, the nzbackup process exits with the following error message:
Stream unresponsive after 300 seconds, operation aborted. Check concurrency
limits on server.
If you use multi-stream backup to a supported third-party backup tool such as

IBM Spectrum Protect (formerly Tivoli Storage Manager), Veritas NetBackup, or
EMC NetWorker, make sure that you review the support for maximum jobs or
parallelism in that tool. For more information, see the later sections that describe
the support for each of these backup connectors.
Only backup operations that transfer table data support multiple destinations and
streams. These operations include full and incremental backups. Other operations
(for example, -noData backup, -globals backup, and the reports) use only a single
destination and a single stream, even if you specify multiple destinations.
Configuring a multi-stream backup
By default, nzbackup uses one stream for each specified filesystem destination, or
only one stream only for backups that do not specify the -dir option. If you set
the host.bnrNumStreamsDefault registry setting to a nonzero value, you can
specify a different streams default that will be used for all applicable nzbackup
operations. You can also specify an explicit stream count for an nzbackup command
by using the -streams parameter. If you specify a nonzero stream number for the
registry setting, you can use nzbackup -streams AUTO to explicitly specify that the
backup should use the default one stream per filesystem or one stream per
connector behavior.
For a description of how to set a system registry setting either temporarily or

permanently, see “Changing configuration settings” on page 7-19.
Multi-stream restore
Starting in NPS Release 7.2, the database restore can be a multi-stream operation.
A multi-stream restore can help to reduce the time required to restore from a
Netezza database backup archive. By default, nzrestore detects and uses the
stream count that was specified for the backup archive that you are restoring on a
per-increment basis.
To set a different default stream count for all applicable nzrestore operations, use
the host.bnrRestoreStreamsDefault registry setting and change it to a nonzero
value. You could also set an explicit stream count for a nzrestore command by
using the -streams parameter to override the registry setting. If you specify a
nonzero stream number for the registry setting, you can use nzrestore -streams
AUTO to explicitly specify that the backup stream count should be used.
For a description of how to set a system registry setting either temporarily or

permanently, see “Changing configuration settings” on page 7-19.

Only restore operations that transfer table data support multiple streams. These
operations include full and incremental backups. Other operations (for example,
-noData restores, -globals restores, and the reports) use only one stream even if
you specify multiple streams.
Special columns
The backup and restore method that you use affects how the system retains
specials. The term specials refers to the end-user-invisible columns in every table
that the system maintains. The specials include rowid, datasliceid, createxid, and
deletexid.
The following table describes how the backup method affects these values.
Table 13-3. Retaining specials
Compressed external Text format external
Special nzbackup and nzrestore tables tables
rowid Retain Retain Not unloaded
datasliceid Retain when the system Retain when the model Recalculate
model size stays the size stays the same,
same, otherwise otherwise recalculates.
recalculates.
createxid Receive the transaction ID Receive the transaction Receive the transaction
of transaction that ID of transaction that ID of transaction that
performs the restore. performs the restore. performs the restore.
deletexid Set to zero. Set to zero. Set to zero.
Upgrade and downgrade concerns

The backup method that you select also affects your ability to restore data after an
IBM Netezza software release upgrade or downgrade.
v Backups that are created with the nzbackup command can be safely
reloaded/restored after an upgrade of the Netezza software. Backups that are
created with the nzbackup command are not guaranteed to support
reload/restore after a Netezza software downgrade. These backup formats are
subject to change between releases.
v Starting in Release 7.0.3, the Netezza system can be configured to support
multiple schemas within a database. When you back up a database, the backup
includes the data for all the schemas in the database.
v When you restore a database that includes multiple schemas, the command
restores all of the schemas unless you are restoring to a system that does not
support schemas. In this case, the restore process attempts to restore all the
objects in the single, default schema for a database. If there are name conflicts,
such as tables in different schemas that use the same name, the restore reports
an error. If you are restoring a database created on a system that did not use
multiple schemas to a system that does support multiple schemas, the restore
should complete without error. The restore creates a schema that matches the
owner name of the database in the backup, and restores the objects to that new
schema.
v Compressed external table backups can be safely reloaded/restored after an
upgrade of the Netezza software. Compressed external table backups are not
guaranteed to support reload/restore after a Netezza software downgrade. These
backup formats are subject to change between releases.

v Text format external tables are insensitive to software revisions, and can be
reloaded to any Netezza software release.
Note: Starting in Release 6.0.x, the nzrestore process no longer supports the
restoring of backups that are created with NPS Release 2.2 or earlier.
Compressed unload and reload

To back up and restore tables when you are using named pipes, or to run your
own incremental or table-level backups, you can use the CREATE EXTERNAL
TABLE command. Use the command to insert compressed binary format records
into an external table from a source table that has the same table schema (table
definition).
You can then reload those records into the original source table or a new table that
has the same table schema. For more information, see the IBM Netezza Data Loading
Guide.
Encryption key management in backup and restore

When you create IBM Netezza database users, the account passwords are stored in
the database in encrypted form. The Netezza system has a default encryption
process. For more security, you can create and specify a host key for encrypting
passwords, as described in the key management section of the IBM Netezza
Advanced Security Administrator's Guide.
When you back up the user and group information, the backup set saves
information about the password encryption. If you use a custom host key, the host
key is included in the backup set to process the account passwords during a
restore. The backup process stores an encrypted host key by using the default
encryption process, or you can use the nzbackup -secret option to encrypt the
host key by using a user-supplied string. To restore that backup set, an
administrator must specify the same string in the nzrestore -secret option. To
protect the string, it is not captured in the backup and restore log files.
The -secret option is not required. If you do not specify one, the custom host key
is encrypted by using the default encryption process. Also, the -secret option is
ignored if you do not use a custom host key for encrypting passwords on your
system.
File system connector for backup and recovery

The IBM Netezza system provides backup connectors that you can use to direct
your backups to specific locations such as network file system locations or to a
third-party backup and recovery solution.
Related concepts:
“Third-party backup and recovery solutions support” on page 13-8
You can use the nzbackup and nzrestore commands to save data to and restore
data from network-accessible file systems, which is the default behavior for the
backup and restore commands. You can also use these commands with supported
third-party backup and recovery products.
File system connector backups

If you use the default file system connector option, make sure that you direct your
backups to one or more file systems that are large enough to hold your database
backups and which are accessible over reliable, fast, network connections to the
IBM Netezza system.

You can specify up to 16 file system locations for your backups. The backup
process uses the specified destinations concurrently to save the data by using one
stream for each destination. The backup process saves the metadata in one
location, but it saves the data across the specified locations.
If the backup process encounters the file-size limit of a backup destination, it

automatically splits the table file that it is writing into multiple files to avoid the
limit without loss of data. The backup process writes table files in 1 TB “portions”
by default. The limit is user-configured by using the registry setting
host.bnrFileSizeLimitGB.
If one of the destinations fills and has no free disk space, the backup process
automatically suspends write activity to that location and continues writing to the
other destinations without loss of data.
If you configure the destinations on unique disk devices that each offer good
performance and bandwidth, the database backups typically take less time to
complete than when you save the backup to only one of those file system
locations. It is important to choose your destinations carefully; for example, if you
choose two file system locations that are on the same disk, there is no performance
gain because the same disk device is writing the backup data. Also, differences in
the write-rate of each file system destination can result in varying completion
times.
You can specify the list of locations by using the nzbackup -dir option, or you can
create a text file of the locations and specify it in the nzbackup -dirfile command.
Similarly, when you restore backups that are saved on file systems, you specify the
locations where the backups are by using the nzrestore -dir option, or you can
create a text file of the locations and specify it in the nzrestore -dirfile
command. The restore can also be a multi-stream process to improve the
performance and time to restore.
File system backup practices

Never save your backups on the IBM Netezza host file systems because the host
does not have enough disk space for database backups.
As a best practice for disaster recovery procedures, store backups on systems that
are physically and geographically separated from the system that they are
designed to recover. Make sure that you have sufficient information about your
backup destinations so that you can choose locations that offer the best results for
capacity and data transfer rates of the backup archives.
Third-party backup and recovery solutions support

The IBM Netezza system currently offers support for the following backup and
recovery solutions:
v Veritas NetBackup
v IBM Spectrum Protect (formerly Tivoli Storage Manager)
v EMC NetWorker

If you have one of these backup and recovery solutions in your environment, you
can integrate the Netezza system with these solutions to manage the backup and
restoration services for your Netezza system and database. These backup and
recovery products have their own storage devices, file systems, and data clients.
They manage the backup and restoration of files and databases to and from these
managed storage devices.
To use these solutions, you typically install some client software for the solution
onto the Netezza host, and then configure some files and settings to create a
connection to the third-party server. You might also complete some configuration
steps on the third-party server to identify and define the Netezza host as a client to
that server. The installation and configuration steps vary for each solution.
You can use the NetBackup and IBM Spectrum Protect interfaces to schedule and
perform all supported Netezza backup and restore operations. You do not have to
log on to the Netezza host to perform a backup operation, or to write the backup
archive to the Netezza host disk or a Netezza mount.
The sections which describe the nzbackup and nzrestore commands also describe
how some of the command options work with the supported storage manager
solutions.
Related concepts:
“File system connector for backup and recovery” on page 13-7
The IBM Netezza system provides backup connectors that you can use to direct
your backups to specific locations such as network file system locations or to a
third-party backup and recovery solution.
“Veritas NetBackup connector” on page 13-34
The Veritas NetBackup environment includes a NetBackup server, one or more
media servers, and one or more client machines. The IBM Netezza host is a
NetBackup client machine.
“IBM Spectrum Protect (formerly Tivoli Storage Manager) connector” on page
13-42
You can use the IBM Netezza host to back up data to and restore data from
devices that are managed by an IBM Spectrum Protect server. This section
describes how to install, configure, and use the integration feature.
“EMC NetWorker connector” on page 13-61
This section describes how to back up and restore data on an IBM Netezza system
by using the EMC NetWorker connector for the Netezza appliance.
Host backup and restore

A host backup creates a copy of the IBM Netezza data directory and system
catalog on the host. The data directory contains system tables, catalog information,
configuration files, and special information for the user databases on the Netezza,
and query plans and cached executable code for the SPUs. The cache and plans
directories are not backed up.
In the rare situations when a Netezza host server or disk fails, but the SPUs and
their disks are still intact, you can restore the /nz/data directory (or the directory
you use for the Netezza data directory) from the host backup without the
additional time to restore all of the databases. This option works best when you
have a host backup that is current with the latest database content and access
settings.

Create a host backup
You use the nzhostbackup command to back up the files in the IBM Netezza data
directory.
The nzhostbackup command pauses the system while it runs; this allows it to
checkpoint and archive the current /nz/data directory. The command resumes the
system when it completes. The command typically takes only a few minutes to
complete. Run database and host backups during a time when the Netezza system
is least busy with queries and users.
Important: Keep the host backups synchronized with the current database and
database backups. After you change the catalog information, such as by adding
new user accounts, new objects such as synonyms or tables, altering objects,
dropping objects, truncating tables, or grooming tables, use the nzhostbackup
command to capture the latest catalog information. Also, update your database
backups.
The following is an example:

nzhostbackup /backups/nzhost_latest.tar.gz
Starting host backup. System state is ’online’.
Pausing the system ...
Checkpointing host catalog ...
Archiving system catalog ...
Resuming the system ...
Host backup completed successfully. System state is ’online’.
Related reference:
“The nzhostbackup command” on page A-24
Use the nzhostbackup command to back up the IBM Netezza data directory and
system catalog on the host.
Restore the host data directory and catalog

You use the nzhostbackup and nzhostrestore commands to back up and restore
the files in the IBM Netezza data directory.
The nzhostrestore command pauses the system before it starts the restore, and
resumes the system after it finishes.
The nzhostrestore command synchronizes the SPUs with the restored catalog on
the host; as a result, it rolls back any transactions that occurred after the host
backup. The host restore operation cannot roll back changes such as drop table,
truncate table, or groom operations. If these changes occurred after the host
backup was made, the host restore might cause those affected tables to be in an
inconsistent state. Inspect the data in those tables, and if necessary, reload the
tables to match the time of the host backup.
The following is an example:

nzhostrestore /backups/nzhost_latest.tar.gz
Starting host restore
Extracting host data archive ...
Restore host data archived Thu Dec 24 03:42:02 EST 2009? (y/n) [n] y
Stopping the system ...
Starting topology restore ...
Warning: The hardware ids will be reassigned.
The hardware id assignments from the archived system catalog have
been saved in ’/tmp/hwids-old.z.tar’
Reinitializing hardware metadata ...

Restoring the devmap / topology tables ...
Starting the system ...
Waiting for system to go online ...
Checking for orphaned SPU tables ...
Loading hardware ids ...
Topology recovery completed successfully.
Warning: The restore will now rollback spu data to Thu Dec 24 03:42:02
EST 2009.
This operation cannot be undone. Ok to proceed? (y/n) [n] y
Installing system catalog to ’/nz/data.1.0’ ...
StarSynchronizing data on spus ...
done.

Restore complete. You can now start the system using ’nzstart’.
After you use the nzhostrestore command, you cannot run an incremental backup
on the database; you must run a full backup first.
After the restore, the hardware IDs for the SPUs and disks typically change;
however, their location and roles remain the same as they were before the host
restore. A failed SPU can become active again after a host restore.
If any tables were created after the host backup, the nzhostrestore command
marks these tables as “orphans,” which means that they are inaccessible but they
consume disk space. The nzhostrestore command checks for orphaned tables and
creates a script that you can use to drop orphaned user tables. The nzhostrestore
command also rolls back the data on the SPUs to match the transaction point of
the catalog in the host backup.
Related reference:
“The nzhostrestore command” on page A-26
Use the nzhostrestore command to restore your IBM Netezza data directory and
metadata.
The nzbackup command

Use the nzbackup command to back up a database, including all schema objects
and all table data within the database.
You can pass parameters to the nzbackup command directly on the command line,
or you can set some parameters as part of your environment. For example, you can
set the NZ_USER or NZ_PASSWORD environment variables instead of specifying -u or
-pw on the command line.
To back up a database, you must have backup privilege. If you attempt to back up
a database in which tables are being reclaimed, the backup process waits until the
reclaim finishes.
While a backup is running on a database, users cannot drop a table in that

database until the backup completes. The DROP TABLE and GROOM TABLE
commands wait (and appear to hang) until the backup finishes. Operations such as
an insert or load, or creating or dropping other object types such as view, run
without waiting while the backup is in progress. If a GROOM TABLE VERSIONS
command runs on a table that is being backed up, the backup process exits with
an error and you must restart the backup process.

In rare cases, a system that has many schema objects can cause a backup to fail
with a memory limitation. In such cases, you might adjust how you back up your
database. For example, if you attempt to back up a database that includes a large
number of columns (such as 520,000), you would likely receive an error message
that indicates a memory limitation. The memory limitation error can result from a
large number or columns or other schema objects. You would likely need to
segment your database into multiple databases, each with fewer than 520,000 table
columns.
Related tasks:
“Specifying backup privileges” on page 13-15
Command syntax for nzbackup

The nzbackup command supports the following syntax:
nzbackup { [-h|-rev] |
[-v] [-db database] { [-dir directory list] | [-dirfile dir file] }
[-connector conname] [-connectorArgs "args"] [-differential]
[-cumulative] [-globals] [-u username] [-pw password] [-streams num]
[-noData] [-history] [-backupset ID] [-secret value] }
The following table describes the command parameters.

Table 13-4. nzbackup command parameters
Parameter Description Example
-h Displays the help for the command.
-rev Displays the software revision of the command.
-host Specifies the host name or IP address of the IBM Netezza host.
Default: Value of NZ_HOST

-v[erbose] Specifies the verbose mode, lists the objects that are being
backed up.
-db database Backs up the specified database and all its objects and the -db ttdev
users, groups, and permissions that are referenced by those
objects.
If you specify this option, you cannot specify -globals. For

more information, see “Back up and restore users, groups, and
permissions” on page 13-21.
Default: Value of NZ_DATABASE

-dir directory Specifies a list of one or more space-separated, full path names -dir /home/user/backups
of the directories where the data is to be stored. This option
applies to filesystem only. You can specify up to 16 directories. or
The directories that you specify are the root for all backups. -dir /home/backup1
The system manages the backups in the subdirectories within /home/backup2/
each root directory. /home/backup3/
-dirfile Specifies a file with a list of backup target directories, one per -dirfile
line. /home/
mybackuptargetlist

Table 13-4. nzbackup command parameters (continued)
-connector conname Names the connector to which you are sending the backup. -connector netbackup
Valid values are:
v filesystem (this is the default)
v tsm
v netbackup
v networker
If you have both the 32-bit and 64-bit clients installed for either
TSM, NetBackup or Networker, the system defaults to using
the 32-bit client. You can force the system to use the 64-bit
client by specifying the name (tsm6-64, netbackup7-64, or
networker7-64) in the -connector option. If only the 64-bit
client is installed, the system uses the 64-bit client to perform
the backup.
The system discovers the backup software that is based on the

connector name that you specify. If there are several versions of
a backup connector installed (for example, TSM 5 and TSM 6),
you can identify a specific version by using one of these
values:
v tsm5
v tsm6
v tsm6-64 (used for TSM 6 and TSM 7 64-bit clients)
v netbackup6
v netbackup7
v netbackup7-64
v networker7 (used for NetWorker 7 and NetWorker 8 32-bit
clients)
v networker7-64 (used for NetWorker 7 and NetWorker 8
64-bit clients)
-connectorArgs “args” Specifies a colon-separated list of pass-through arguments for “name=value[:name
the connector. The argument string must be enclosed in double =value:...]”
quotation marks.
-differential Specifies a differential backup (that is, only the data that
changed since the last backup).
-cumulative Specifies a cumulative backup (that is, the command backs up
only the changes since the last full backup).
-globals Backs up all users, groups, and global permissions. The -globals
command also backs up multi-level security objects such as
categories, cohorts, and levels (described in the IBM Netezza
Advanced Security Administrator's Guide).
If you specify this option, you cannot specify -db. For more
information, see “Back up and restore users, groups, and
-u username Specifies the Netezza user name to connect to the database. -u user_1
Default: Value of NZ_USER

-pw password Specifies the user password. -pw XXXXXX
Default: Value of NZ_PASSWORD

Table 13-4. nzbackup command parameters (continued)
-streams num Backs up the data by using the specified number of streams. -streams 3
For more information, see “Multi-stream backup” on page 13-4.
Default: Value of host.bnrNumStreamsDefault (see “Changing

configuration settings” on page 7-19)
-noData Saves only the definitions of the objects such as tables, views, -noData
synonyms and others, as well as the access privileges defined
in the specified database. The user data in tables or views is
not saved.
This option is an easy way to replicate an empty database with

all its object definitions and privileges in a Netezza system.
-history Prints the backup history report.
-backupset ID Specifies the backup set that you want to use for incremental -backupset
backup, rather than the default. 20060523200000
The default backup set is the most recent backup set of the
database you specify. You can override the default by using
this option.
Default: The most recent full backup set

-secret value Specifies a string value that is needed to generate a 256-bit -secret toplevel
symmetric key, which is used to encrypt the host key in the
backed up data.
Environment settings for backup
By default, the nzbackup command uses the values of the environment variables
NZ_DATABASE, NZ_USER, and NZ_PASSWORD, unless you specify values for -db for
NZ_DATABASE, -u for NZ_USER, and -pw for NZ_PASSWORD.
The following table lists the nzbackup command environment variables.

Table 13-5. Environment settings
Name Corresponding command-line parameter
NZ_DATABASE Same as -db
NZ_USER Same as –u
NZ_PASSWORD Same as –pw
Backup errors
The nzbackup command writes errors to the log file /nz/kit/log/backupsvr/

backupsvr.pid.date.log. For more information about the log files, see “System
logs” on page 7-12.
Related reference:
“The nzbackup command” on page A-4
Use the nzbackup command to back up your database.

Specifying backup privileges
Before you begin
You must have the Backup privilege to back up a database. The Backup privilege
operates at the database level.
About this task
You can grant a global Backup privilege for the user to back up any database, or
you can grant a Backup privilege for the user to back up a specific database.
Related concepts:
“The nzbackup command” on page 13-11
Use the nzbackup command to back up a database, including all schema objects
and all table data within the database.
Backing up a specific database

About this task
To grant a user privilege to back up a specific database, complete the following

steps:
Procedure
1. Run nzsql and connect to the database you want to allow the user to back up
by entering: nzsql db1.
2. Create a user user_backup with password password. For example:
DB1.SCHEMA(ADMIN)=> CREATE USER user_backup WITH PASSWORD ’password’;
3. Grant backup privilege to user_backup. For example:
DB1.SCHEMA(ADMIN)=> GRANT BACKUP TO user_backup;
Backing up all databases

About this task
To grant a user privilege to back up all databases, complete the following steps.
Procedure
1. Run nzsql and connect to the system database by entering: nzsql system
2. Create a user user_backup with password password: For example,
MYDB.SCH1(USER)=> CREATE USER user_backup WITH PASSWORD ’password’;
3. Grant backup privilege to user_backup:
MYDB.SCH1(USER)=> GRANT BACKUP TO user_backup;
Examples of the nzbackup command

The following are several examples of the nzbackup command:
v To back up the contents of the database db1 to disk in the /home/user/backups
directory, enter:
nzbackup -dir /home/user/backups -u user -pw password -db db1
The nzbackup command saves the schema of the database (its definition), data,
and access permissions for all the objects and user data in the database. Sample
output follows:
successfully.

You can use the -v (verbose) command option to display more detail about the
backup:
[Backup Server] : Starting the backup process
[Backup Server] : Backing up to base directory ’/home/user/backups’
[Backup Server] : Backing up libraries
[Backup Server] : Backing up functions
[Backup Server] : Backing up aggregates
[Backup Server] : Transferring external code files
[Backup Server] : Start retrieving the schema
[Backup Server] : Backing up metadata to
/home/user/backups/Netezza/hostid/DB1/20120319201402/1/FULL
[Backup Server] : Retrieving host key information
[Backup Server] : Retrieving user information
[Backup Server] : Backing up sequences
[Backup Server] : Backing up table schema.
[Backup Server] : Backing up External Tables.
[Backup Server] : Backing up External table settings.
[Backup Server] : Backing up External table zone settings.
[Backup Server] : Backing up Table Constraints
[Backup Server] : Backing up synonyms
[Backup Server] : Backing up stored procedures
[Backup Server] : Backing up materialized views
[Backup Server] : Backing up view definitions.
[Backup Server] : Retrieving group information
[Backup Server] : Retrieving group members
[Backup Server] : Backing up ACL information
[Backup Server] : Start retrieving the data.
[Backup Server] : Backing up table AAA
[Backup Server] : Backing up table BBB
[Backup Server] : Backing up table sales %
[Backup Server] : Operation committed
successfully.
v To back up the contents of the database db2 to file system locations in the
/export/backups1 and /export/backups2 directories, enter:
nzbackup -dir /export/backups1 /export/backups2 -u user -pw password
-db db2
The nzbackup command saves the schema of the database (its definition), data,
and access permissions for all the objects and user data in the database. The
database is saved in the two specified file system locations.
v To back up only the object definitions and access privileges of the database db1
to disk in the /home/user/backups directory, enter:
nzbackup -dir /home/user/backups -noData -u user -pw password
-db db1
The nzbackup command saves the schema, which is the definition of the objects
in the database and any access permissions that are defined in the database to a
file. The following is an example that also uses the -v option:
[Backup Server] : Backing up libraries
[Backup Server] : Backing up functions
[Backup Server] : Backing up aggregates
[Backup Server] : Transferring external code files
[Backup Server] : Backing up to
/home/user/backups/Netezza/hostid/DB1/20120319202016/1/SCHEMA/md
[Backup Server] : Backing up sequences
[Backup Server] : Backing up table schema.
[Backup Server] : Backing up External Tables.
[Backup Server] : Backing up External table settings.
[Backup Server] : Backing up External table zone settings.

[Backup Server] : Backing up Table Constraints
[Backup Server] : Backing up synonyms
[Backup Server] : Backing up stored procedures
[Backup Server] : Backing up materialized views
[Backup Server] : Backing up view definitions.
Backup of schema for database db1 completed successfully.
v To back up the global objects in the /home/user/backups directory, enter:
nzbackup -dir /home/user/backups -globals -u user -pw password
The nzbackup command saves the users, groups, global permissions, and security
categories, cohorts, and levels for multi-level security. It does not capture user
privileges that are granted in specific databases. Those permissions are captured
in database backups.
[Backup Server] : Backing up security metadata
[Backup Server] : Start retrieving the schema
[Backup Server] : Backing up metadata to
/export/home/nz/backups/Netezza/hostid/SYSTEM/20120319202355/1/USE
RS/md
Backup of global objects completed successfully.
Backup archive directory

The IBM Netezza system maintains a backup archive directory that records the
backup activity for each database.
For example, if you performed a full backup and then a differential backup on the
database Orders, the directory structure would look as follows:
Netezza/NPSProduction/Orders/20061120120000/1/FULL
Netezza/NPSProduction/Orders/20061121120000/2/DIFF
Backup and restore both use this directory structure. Backup uses it to find backup
sets with which to associate an incremental. Restore uses it to derive incremental
restore sequences.
The backup process finds the most recent backup set for a database for incremental
backup (unless you override the backup set). The restore process finds the most
recent backup set for -db or -sourcedb, and current host or -npshost. You can
override the most recent backup set by using the nzrestore command options
-sourcedb, -npshost, or -backupset.
The most recent backup set for backup or restore is the most recently begun
backup set, or the most recent full backup.
If you move the backup archives from one storage location to another, you must
maintain the directory structure. If you want to be able to run an automated
restore, all the backup increments must be accessible.

Incremental backups
Incremental backups are database backups that save only the data that changed
since the last backup. Because the system copies a small subset of the data,
incremental backups require less time to complete than full backups. Use
incremental backups to keep your backups current and reduce the frequency of
time-consuming full backups.
IBM Netezza supports two types of incremental backups:

Differential
Includes all the changes that are made to the database since the previous
backup (full, differential, or cumulative).
Cumulative
Includes all the changes that are made to the database since the last full
backup. Cumulative backups incorporate and replace any differential
backups that were run since the last full backup.
Use cumulative backups to consolidate differential backups so that if you
must restore data, the restoration requires fewer steps and less media.
The following figure shows sample backups, beginning with a full backup (shown
as the letter A), then a series of differential (C) and cumulative (B) backups.
Figure 13-1. Database backups timeline
The backups in the previous figure comprise a backup set, which is a collection of
backups that are written to a single location that consists of one full backup and
any number of incremental backups.
Differential backup
After you run a full backup on a database, you can run an incremental backup to
capture any changes made since the last backup. To run an incremental differential
backup on the IBM Netezza host, you use the nzbackup command and specify the
-differential option.
The following is the syntax for a differential backup:

nzbackup -db <db_name> -differential
The following is the syntax for a differential backup that is written to the
NetBackup application:
nzbackup -db <db_name> -differential -connector netbackup

Cumulative backup
After you run a full backup on a database, you can specify an incremental backup.
To run an incremental cumulative backup on the Netezza host, you use the
nzbackup command and specify the -cumulative option.
The following is the syntax for a cumulative backup:

nzbackup -db <db_name> -cumulative
The following is the syntax for a cumulative backup that is written to the
NetBackup application:
nzbackup -db <db_name> -cumulative -connector netbackup
Revert to a full backup

If you run an incremental backup, there are certain conditions that can trigger the
nzbackup command to run a full backup for a particular table, such as:
v Dropping and re-creating a table
v Truncating a table
v Using GROOM TABLE VERSIONS to resolve the versions of an altered table
If the nzbackup command performs a full backup of a table instead of an

incremental backup, it writes a message to verbose output and to the backup log.
Restriction: After you use the nzhostrestore command, you cannot run an
incremental backup on the database; you must run a full backup first.
Notes about backup-groom synchronization:

v The system keeps groom/reclaim and incremental backups synchronized.
GROOM TABLE uses information that is stored in the system catalog to identify
incremental backups by using the most recent incremental backup for guidance.
Groom limits its operation to transactions captured by that backup and its
predecessors. Groom avoids the reclaiming of rows that are not yet captured in
incremental backup.
v You can override the default backup set synchronization by specifying a
particular backup set on the GROOM TABLE command line.
v When you perform any backup of a database, you trigger the synchronization.
The system assumes that incremental backups follow a full backup.
To override the default groom behavior, use the backupset option.

v To reclaim all rows, use backupset NONE.
v You can also choose a specific backup set. For example, run the nzbackup
-history command to view the backup set IDs in the report:
Database Type Start Date Backup Set
---------------------------------------------------------------
dev Full 2006-06-01 20:00:00 20060601200000
dev Differential 2006-06-04 20:00:00 20060601200000
dev Full 2006-06-08 20:00:00 20060608200000
dev Differential 2006-06-11 20:00:00 20060608200000
From this backup history report, you can choose to use the June 1 backup set
rather than the June 8 backup set:
GROOM TABLE dev RECLAIM BACKUPSET 20060601200000
Release compatibility for incremental backups and restores

After you upgrade your IBM Netezza system, you can extend backup sets from the
earlier release with incremental backups from the newer release. You can restore

the backups and incrementals to the later release. However, if you downgrade to
the previous release, keep in mind the following restrictions:
v You cannot add increments to a backup set that was created on, or last
incremented by, a later Netezza release.
v You cannot restore backups or increments that are created by a later release. For
example, assume that you have backup sets that are created on the earlier
release, and following an upgrade, you add increments from the later release. If
you downgrade to the earlier release, you can restore the backups and
increments that are created on that earlier release, but you cannot restore any
increments that are created with the later release.
Backup History report

Use the Backup History report to view information about the recent backups. You
can use the report to display information about all of the backups that were run
from the host system.
You can access the Backup History report in several ways: by using the nzbackup
-history command, by using the NzAdmin tool, or the IBM Netezza Performance
Portal interface. This section describes how to use the nzbackup command; for
details on the interfaces, see the online help for NzAdmin and IBM Netezza
Performance Portal.
Your IBM Netezza user account must have appropriate permissions to view
backup history for databases:
v If you are the admin user, you can view all entries in the backup history list.
v If you are not the admin user, you can view entries if you are the database
owner, or if you have backup or restore privileges for the database.
The following is the syntax to display the backup history for a database:
nzbackup -history -db name
Database Backupset Seq # OpType Status Date Log File
-------- -------------- ----- ------- --------- ------------------- ----------------------
SQLEXT 20090109155818 1 FULL COMPLETED 2009-01-09 10:58:18 backupsvr.9598.2009-01-09.log
You can further refine your results by using the -db and -connector options, or use
the -v option for more information. You use the -db option to see only the history
of a specified database.
The command displays the following information:

Table 13-6. Backup history source
Column Description
Database The name of the backup database.
Backup Set The unique value that identifies the backup set.
Seq.No The sequence number that identifies the increment within the backup set.
Op Type The type of backup (full, differential, cumulative, globals, no data, or users).
Date The date and time that the backup was initiated.
Status The status (completed, failed, in-progress).
Log File The name of the log file.
Related concepts:

“Groom and backup synchronization” on page 12-23
By default, the system synchronizes your GROOM TABLE request with the most
recent backup set to avoid reclaiming rows that are not yet captured by
incremental backups. In other words, GROOM TABLE does not remove any data
that has been deleted or is outdated but which has not been saved in a backup.
Back up and restore users, groups, and permissions

When you back up a database by using nzbackup -db dbname, the backup includes
permissions on objects in the database, and any users and groups that are
referenced by those permissions. The database backup contains only the users,
groups, and privileges as saved in the specific database; it does not include global
privileges that are defined in the system catalog.
To back up all users, groups, global permissions, specify nzbackup -globals. The
nzbackup -globals command backs up all users and groups regardless of whether
they are referenced by any permission grants within a database, and any security
categories, cohorts, and levels for multi-level security. The system also backs up all
global-level permissions that are not associated with particular databases. The
system does not back up permissions that are defined in specific databases. Those
permissions are saved in the regular database backups for those databases.
For example, suppose that you have four users (user1 to user4) and you grant
them the following permissions:
nzsql
SYSTEM.ADMIN(ADMIN)=> GRANT CREATE TABLE TO user1;
SYSTEM.ADMIN(ADMIN)=> \c db_product
DB_PRODUCT.SCH(ADMIN)=> GRANT CREATE TABLE TO user2;
DB_PRODUCT.SCH(ADMIN)=> GRANT LIST ON TABLE TO user3;
DB_PRODUCT.SCH(ADMIN)=> GRANT LIST ON emp TO user4;
User1 has global Create Table permission, which allows table creation in all
databases on the IBM Netezza system. User2 and User3 have Create and List
permission to tables in the db_product database. User4 has List permission only to
the emp table in the database db_product.
The following table describes the results when you invoke the nzbackup and
nzrestore commands with different options.
Table 13-7. Backup and Restore Behavior
Method User backed up/restored Permission backed up/restored
nzbackup/nzrestore -db user2 CREATE tables in the
db_product db_product database.
user3 LIST on all tables in the
db_product database.
user4 LIST on the emp table in the
db_product database.
nzbackup/nzrestore user1 CREATE tables in the system
-globals database.
user2
user3
user4

v A regular backup of the db_product database does not include user1 or the
CREATE TABLE GRANT to user1 because those privileges are defined in the
system database (the system catalog).
v A -globals backup and restore includes all users (in this case, users1 - user4),
but it only includes the Create Table permission for user1, which is also defined
in the system database. The -globals backup and restore does not include the
privileges that are defined specifically in the db_product database.
v A -globals backup and restore does not include the admin user or the public
group.
By using the nzrestore -globals command, you can restore users, groups, and
permissions. The restoration of users and groups is nondestructive, that is, the
system only creates users and groups if they do not exist. It does not drop users
and groups. Permission restoration is also nondestructive, that is, the system only
grants permissions. It does not revoke permissions.
Remember: When you restore data and users from a backup, the process reverts
your system to a point in the past when the backup was made. Your user
community and their access rights might change, or if you are restoring to a new
system, a stale backup might not reflect your current user community. After you
make any significant user community changes, back up the latest changes. After
you restore from a backup, check that the resulting users, groups, and permissions
match your current community permissions.
The nzrestore command

You can use the nzrestore command to restore the contents of a database.
To use the restore command, you must have the Restore privilege. The nzrestore
command restores complete databases or specific tables.
Restriction: You cannot do a full database restore into an existing database.

Instead, specify a new database or drop the existing database first before you
proceed with the nzrestore command.
If you need to grant a user permission to restore a specific database (versus global
restore permissions), you can create an empty database and grant the user
privilege for that database. The user can then restore that database.
You can pass parameters to the nzrestore command directly on the command line,
or you can set parameters as part of your environment. For example, you can set
the NZ_USER or NZ_PASSWORD environment variables instead of specifying -u or -pw
on the command line.
When you do a full restore into a database, the nzrestore command performs the
following actions:
1. Verifies the user name that is given for backup and restore privileges.
2. Checks to see whether the database exists.
3. Re-creates the same schema for the new database, including all objects such as
tables, views, sequences, and synonyms.
4. Applies any access privileges to the database and its objects as stored in the
backup. If necessary, the command creates any users or groups that might not
currently exist on the system to apply the privileges as saved in the database

backup. The command also revokes any current user or group privileges to
match the privileges that are saved at the time of the backup.
5. Restores the data.
If you are performing a table-level restore and the table exists in the database, the
nzrestore command drops and re-creates the table if you specify -droptables. If
you do not specify -droptables, the restore fails.
The nzrestore -noData command does not restore the /nz/data directory; instead,
it creates a database or populates an empty database with the schema (definition)
from the backed-up database. The command creates the objects in the database,
such as the tables, synonyms, sequences, and views, and applies any access
permissions as defined in the database. It does not restore data to the user tables in
the database; the restored tables are empty.
In rare cases, when a schema (definition) has a large number of objects, the restore
could fail with a memory limitation. In such cases, you might adjust how you
restore your database. For example, if you attempt to restore a database that
includes many columns (such as 520,000), you would likely receive an error
message that indicates a memory limitation. The memory limitation error can
result from a large number of columns or other object definitions. You would likely
perform a no-data restore followed by two or more table-level restore operations.
Related tasks:
“Specifying restore privileges” on page 13-28
Related reference:
“The nzrestore command” on page A-47
Use the nzrestore command to restore your database from a backup.
The nzrestore command syntax

The nzrestore command supports the following command-line syntax:
usage: nzrestore [-h|-rev] [<options>]
[-v][-db database] [-dir directory list] [-dirfile dir file]
[-connector conname] [-connectorArgs "args"] [-backupset ID]
[-sourcedb dbname] [-npshost host] [-tables tablenames]
[-tablefile filename] [-sourceschema schema_name] [-droptables]
[-increment ID] [-increment NEXT] [-increment REST] [-lockdb] [-unlockdb] [-globals]
[-noUsers] [-noAcl] [-u username] [-pw password]
[-secret value] [-streams AUTO] [-streams N] [-noData] [-allincs]
[-contents] [-history] [-incrementlist] [-suspendMViews] [-disableGroom]
[-disableSecurityCheck] [-enableSecurityCheck][-disableSecurityRestore]
[-enableSecurityRestore] [-extract [file]] [-extractTo path]
The following table lists the nzrestore command options.

Table 13-8. The nzrestore command options
-rev Displays the software revision of the command.
-v[erbose] Specifies the verbose mode, lists the objects that are being restored.
-db database Restores the specified database and all its objects and the users,
groups, and permissions that are referenced by those objects.
If you specify this option, you cannot specify -globals. For more

Table 13-8. The nzrestore command options (continued)
-dir directory list For a restore from a file system, specifies the path names of the
backup directories. You can specify full path name or path names, or
the backup “root” directories. For example, if you used the root
directory /usr/backups when you created the backup, specify
/usr/backups when you restore from that backup.
If you saved the backup to multiple file system locations, specify the
roots of all the locations in this argument. For example, if a backup
was written to /home/backup1, /home/backup2, and /home/backup3,
you can restore the data in a single operation by specifying all three
locations.
-dirfile Specifies a file with a list of the backup source directories, one per
line.
-connector conname Names the connector to which you are sending the backup. Valid
values are:
v filesystem
v tsm
v netbackup
v networker
If you have both the 32-bit and 64-bit clients installed for either TSM,
NetBackup or Networker, the system defaults to using the 32-bit
client. You can force the system to use the 64-bit client by specifying
the name (tsm6-64, netbackup7-64, or networker7-64) in the
-connector option. If only the 64-bit client is installed, the system
uses the 64-bit client to perform the restore.
The system “discovers” the backup software that is based on the

connector name that you specify. If you have multiple versions of a
backup connector installed (for example, TSM 5 and TSM 6), you can
use a specific version by using one of these values instead of the
previous generic arguments:
v tsm5
v tsm6
v tsm6-64 (used for TSM 6 and TSM 7 64-bit clients)
v netbackup6
v netbackup7
v netbackup7-64
v networker7 (used for NetWorker 7 and NetWorker 8 32-bit clients)
v networker7-64 (used for NetWorker 7 and NetWorker 8 64-bit
clients)
v tsm5
v tsm6
v tsm6-64
v netbackup6
v netbackup7
v netbackup7-64
v networker7
v networker7-64

-connectorArgs Specifies a colon-separated list of pass-through arguments for the
“args” connector. The argument string must be enclosed in double quotation
marks.
-backupset ID Specifies the backup set, overriding the default.
-sourcedb dbname Specifies the backup set database, overriding the default.
The nzrestore command restores the most recent backup of -db

unless you specify a different backup set with the option -sourcedb.
-npshost host By default, restores look for backup sets that were created by the local
IBM Netezza host. If you use nzrestore to migrate databases,
schemas, or user backups that are made on a different Netezza host,
use this option to specify the host that created the backup set.
-tables table_list Restores the table or tables as specified in the table_list argument,
which is a space-separated list of tables. The table names are
case-sensitive, and you must specify a table name as it appears in the
backup set. You can use the nzrestore -contents option to display
the names of objects in the backup set.
-tablefile filename Restores the tables that are listed in the table file, which is a file that
contains a list of tables with one table per line. The table names are
case-sensitive, and you must specify a table name as it appears in the
backup set.
-sourceschema On systems that support multiple schemas, a database backup
schema_name contains all the objects in all the schemas in that database. Users
could create tables that have the same name in different schemas. To
uniquely identify the table that you want to restore in the -tables or
-tablefile argument, use the -sourceschema option to specify the
schema in the backup set where the table is defined.
The -sourceschema argument is optional, but the command returns an

error if it finds more than one table of that name in the backup set.
The schema name is case-sensitive, and you must specify a schema
name as it appears in the backup set. You can use the nzrestore
-contents option to display the names of objects in the backup set. If
the -tables or -tablefile argument contains a list of tables, the
-sourceschema value applies to all of the tables. To restore tables from
different schemas of the same backup set, use a separate nzrestore
command to restore the table or tables in each -sourceschema.
-droptables Drops the tables in the table list before it restores them during a
table-level restore.
-increment [ID | If you specify an increment ID, the command runs a partial restore
NEXT | REST] up to the user-specified increment number.
After you run a partial restore, you can specify NEXT to restore the
next increment from the backup set. If you specify REST, the
command restores the remaining increments from the backup set.

-lockdb Makes the database read-only to prevent modifications during the
restore.
Any of the following can represent “true”: 1, t, T, y, Y, true, TRUE,

yes, Yes, or YES.
Any of the following can represent “false”: 0, f, F, n, N, false, False,

FALSE, no, No, or NO.
If you do not specify this option, the database remains unlocked,

which does not allow subsequent incremental restore operations.
-unlockdb Unlocks the database without performing another restore. This option
is useful in cases where a restore is aborted or fails because the target
database could remain locked. Use this option to unlock the database.
-globals Restores the users, groups, and global permissions, and multi-level
security information such as categories, cohorts, and levels. For more
permissions” on page 13-21. You cannot specify -db when you specify
-globals.
The creation of the users, groups, and global permissions is

non-destructive; that is, if a user or group exists, the system does not
overwrite it. If you specify verbose mode, the nzrestore command
displays at least one user or group creation error message and directs
you to the restore log for details.
When you are transferring data to a new system, use nzrestore

-globals first to ensure that the users, groups, permissions, and
security information is present before you restore the data.
-noUsers Disables the restoration of users or groups.
-noAcl Disables the restoration of permissions.
-u username Specifies the user name for connecting to the database to perform the
restore.
-pw password Specifies the user password.
-secret value Specifies a string value that is needed to generate a 256-bit symmetric
key, which is used to decrypt the host key in the data.
-streams [AUTO | Specifies the number of streams to use when restoring the database
N] archive. For more information, see “Multi-stream restore” on page
13-5.
If you specify AUTO, the command chooses the number of streams

for the restore. The number of streams is typically the same number
of streams that were used by the nzbackup command that created the
backup archive.
You can specify a stream count for the command using the -stream N
option.
If you do not specify a -streams value, the restore process uses the
number of streams defined by the host.bnrRestoreStreamsDefault
registry setting.
-noData Restores only the database schema (the definitions of objects and
access permissions), but not the data in the restored tables.

-allIncs Used with -noData, restores the user-defined objects (functions,
aggregates) in every increment.
-contents Lists the name and type of each database object in a backup archive.
For file system backup locations, you must also specify -dir for the
location of the backup archive and -db for a specific database.
-history Prints a restore history report.
-incrementlist Prints a report of the available backup sets and increments.
You must specify -connector. You can also specify -npshost,

-sourcedb, or both.
-suspendMViews Leave materialized views suspended after a table-level or incremental
restore.
-disableGroom Disables the automatic groom of versioned tables at the end of the
restore operation.
-disableSe- For nzrestore -db operations, the command confirms that the target
curityCheck system has all the security metadata in the backup set. The target
must have a compatible MLS model with the levels, categories, and
cohorts that are defined in the backup set. In some instances, the
backup set can include older, unused metadata that is not present in
the target database; by default, nzrestore -db fails in this case. You
can use this switch to bypass the overall metadata check, but if the
backup set has data that includes a label that is not in the target
system, the restore fails and is rolled back.
-enableSe- Checks but does not restore any security metadata in the backup set.
curityCheck
-disableSe- When you use nzrestore -globals, this option ignores (does not
curityRestore restore) security metadata if the backup set contains any.
-enableSe- For nzrestore -db operations, restores the security metadata in the
curityRestore backup set to the target system.
-extract [file] Extracts the specified file from the specified backup set. If you do not
specify a file, the option lists all the files in the backup set.
With the -extract option, the restore command does not restore the
specified backup set or files. The -extract option causes the
command to skip the restore operation and output the requested file
or list.
-extractTo path Specifies the name of a file or a directory where you want to save the
extracted output. If you do not specify directory, the -extract option
saves the file in the current directory where you ran the nzrestore
command.
Environment settings for nzrestore
As an alternative to command-line options, you can specify the following inputs as

environment variables. The following table describes the environment settings.
Table 13-9. Environment settings
Name Corresponding command-line parameter
NZ_USER Same as -u.
NZ_PASSWORD Same as -pw.

Restore errors
The nzrestore command writes errors to the /nz/kit/log/restoresvr/

restoresvr.pid.date.log file. For more information about the log files, see
“System logs” on page 7-12.
Specifying restore privileges

Before you begin
You must have the Restore privilege to restore a database.
About this task
The Restore privilege operates at the database level. You can grant a global Restore
privilege for the user to restore any database, or you can grant Restore privilege to
allow the user to restore only a specific database.
Results
The restored database is owned by the original creator. If that user no longer exists,
the system displays a warning and changes the ownership to the admin user.
Related concepts:
“The nzrestore command” on page 13-22
Restoring a specific database

About this task
To allow a user to restore a specific database, complete the following steps.
Procedure
1. Run nzsql and connect to the database you want to allow the user to restore by
entering: nzsql db1
2. Create a user user_restore with password password. For example:
DB1.SCHEMA(ADMIN)=> CREATE USER user_restore WITH PASSWORD ’password’;
3. Grant restore privilege to user_restore. For example:
DB1.SCHEMA(ADMIN)=> GRANT RESTORE TO user_restore;
If the database does not exist, you must first create an empty database and then
assign the Restore privilege to the user. You must assign the Restore privilege
on an empty database.
Restoring all databases

About this task
To allow a user to restore all databases, complete the following steps.
Procedure
1. Run nzsql and connect to the system database by entering: nzsql system;
2. Create a user user_restore with password password. For example:
SYSTEM.ADMIN(ADMIN)=> CREATE USER user_restore WITH PASSWORD ’password’;
3. Grant restore privilege to user_restore. For example:

SYSTEM.ADMIN(ADMIN)=> GRANT RESTORE TO user_restore;
Examples of the nzrestore command

The following are several examples of the nzrestore command.
v To restore the database db1 from the /home/user/backups directory:
nzrestore -db db1 -u user -pw password -dir /home/user/backups -v
An example of the command output follows:
[Restore Server] : Starting the restore process
[Restore Server] : Reading schema from
[Restore Server] : Restoring schema
[Restore Server] : Start restoring the data, compressed format.
[Restore Server] : Restoring data from
[Restore Server] : Restoring AAA
[Restore Server] : Restoring BBB
[Restore Server] : Restoring sales %
[Restore Server] : Restoring views, users, groups, permissions
Restore of increment 1 from backupset 20090116125619 to database
’DB1’ committed.
v To restore the only the schema (objects and user permissions, but not the table
and view data) of db1 to a new, empty database that is named new_db1:
nzrestore -db new_db1 -sourcedb db1 -noData -u user -pw
password -dir /home/user/backups
v To restore the users, groups, and privileges in the system catalog:
nzrestore -globals -u user -pw password -dir /home/user/backups
This command restores the users, groups, and global privileges as defined in the
system catalog. If a user or group currently exists in the system catalog, the
command grants any additional privileges as defined in the backup. The
command does not revoke any current privileges that are not also defined in the
backup.
v To list all of the objects such as tables, synonyms, user-defined objects, and
others that were saved in a database backup, use the nzrestore -contents
command as follows:
nzrestore -contents -db dev -dir /net/backupsvr/nzbackups
Database: TPCH_TEST
List of relations
Oid | Type | Name
-----------+----------------+-----------------------------
210854 | SEQUENCE | MY_SEQ
203248 | TABLE | NATION
203264 | TABLE | REGION
203278 | TABLE | PART
203304 | TABLE | SUPPLIER
203326 | TABLE | PARTSUPP
203344 | TABLE | CUSTOMER
203368 | TABLE | ORDERS
203394 | TABLE | LINEITEM
210853 | SYNONYM | MY_ORDERS
217345 | FUNCTION | ORDERCONV(CHARACTER VARYING(ANY))
v If a restore operation fails or is canceled, the target database could remain in a
locked state. You can use the -unlockdb option of the command to unlock the
target database, for example:
nzrestore -db myrestoredb -unlockdb

Database statistics after restore
After a restore, use the GENERATE STATISTICS command to update your
database statistics. When you use the nzhostrestore command to restore host data,
you do not have to regenerate statistics because the command restores the
statistics.
Related concepts:
“Database statistics” on page 12-15
Restore tables
You can use the nzrestore command to identify specific tables in an existing
backup archive and restore only those tables to the target database.
Table-level restore
When you request a table-level restore, the system restores individual tables from
an existing full-database backup to a specific database. Table-level restore does not
drop the target database or affect objects in that database other than those objects
that you are explicitly restoring.
Table-level restore does the following:

v Restores regular tables, not external or temp tables, views, sequences, users, or
groups.
v Replaces tables with the same name if they exist (and you use the -droptables
option).
v Includes the permissions that directly reference the restored tables.
v Restores any foreign keys that are on or reference the tables.
v Returns all materialized views to their original state. (Leaves previously active
mviews suspended if you used the -suspendmviews option.)
Table-level restore has the following restrictions:

v You cannot rename tables during the restoration.
v You cannot append to an existing table.
v You cannot create users and groups during the restoration. If the owner of the
table does not exist, the admin user becomes the new owner. Permission grants
fail for any users or groups that do not exist during the restore.
v You are responsible for ensuring database integrity. If you have foreign keys
however, the system warns you of potential inconsistencies.
Table-level restore syntax

To run a table-level restore, use the following syntax:
nzrestore -db <dbname> -connector <filesystem> -dir <root dir>
[<opts>] -tables <table1> [ ...]
Note: If you specify multiple tables with the -tables option, separate the table
names with spaces.
As in a standard restore, by default the system restores the table's definition and
data. To skip the data restore, use the -noData option.
Keep in mind the following behaviors:

v You can specify the nzrestore command-line options in any order.
v If your table names contain spaces, enclose the names in double quotation
marks.

v If your table names begin with dashes (-), you can restore them by listing them
in a single file and by using the -tablefile option.
v You can restore to a different target database than the original backup (use the
-sourcedb option to find the backup).
v If the target database does not exist, the system creates it.
v Specify the table name in the letter case form (uppercase or lowercase) that
matches the name in the backup set.
v If the backup set for a database includes multiple schemas, and the table name
is not unique because it is used in more than one schema, the system displays
the message Error: More than one table having name 'TABLENAME' found in
the backup. Specify -sourceschema option. You must specify the schema
where the table is defined in the backup set to uniquely identify the table.
v If the table exists in the database with the same name as the table you are
restoring, both copies of the table exist until the transaction is complete. If there
is not enough disk space for both versions of the table, you must manually drop
the table before you run the table-level restore.
Transaction management during restore

As with a full-database restore, the system is available to all users during a
table-level restoration. Most of a table-level restoration occurs within a single
transaction. The system handles other concurrent operations on the same table in
the following manner:
v If a concurrent operation begins before the restore drops the table, it succeeds.
v If the concurrent operation begins after the restore table drop, the system
suspends the concurrent operation until the restore operation either is committed
or rolled back.
– If the restore transaction is committed, the concurrent operation fails and the
system displays an error.
– If the restore transaction is rolled back, the concurrent operation succeeds
against the original table.
v If a concurrent non-read-only transaction locks the same table, the system
suspends the restore operation.
v If you abort the table-level restore, the system returns the database to its original
state.
Incremental restoration
You can restore an entire backup set in a single operation. This type of restore is
called a full restore. You can also restore a subset of your backups by using an
incremental or partial restore. The granularity depends on the backup increment
(full, differential, or cumulative) that corresponds to the point in time to which you
want to return. For incremental restores, you must apply the increments in
sequence.
When you restore data, the restoration software reads the metadata to frame the
increment, validates the operation against the backup set, and performs the restore.
The restore software associates the increment with a backup set on either the
source IBM Netezza or the target Storage Management System (SMS) by finding
(by default) the most recent backup of the same database from the same source
system.
Increment list report

You can display all available backup sets on the target system by using the
-incrementlist option.

The following example displays the available backup sets and increments in a
source storage system:
nzrestore -incrementlist -connector netbackup

Table 13-10. Backup history target
Column Description
Op Type The type of backup (full, differential, cumulative, noData, or users).
Hostname The name of the source system.
Restore a full backup set

A full restore restores the entire contents of a backup set (one full plus all the
incrementals). By default the nzrestore command finds the most recent backup set
for the database.
For example, the following command line restores the database dev from the
backup set that is stored in a NetBackup system.
nzrestore -db dev -connector netbackup
You can override the default host and database. For example, to specify another
host use the -npshost option (where -npshost is the source IBM Netezza system
that created the backup), and to specify another database, specify the -sourcedb
option.
nzrestore -db dev -connector netbackup -npshost nps_dev -sourcedb
mydev
If you do not want to restore the most recent backup set, you can specify a specific
backup set with the -backupset option.
nzrestore -db dev -connector netbackup -backupset 20060623200000
Note: Use the -incrementlist option to view a report that lists all full and
incremental backups.
Restore an incremental backup

Restoring an incremental backup restores a subset of a backup set that includes a
full backup, and any number of incremental backups. An incremental restore
creates a database or appends to an existing database created through a previous
restore, depending on the incremental restore type. You can restore by using three
methods: up-to-x, step-by-step, or remainder incremental.
For the restore to return a database to a known state, the database must not be
allowed to change during multi-step restore operations. Specifying the -lockdb
option makes the database read-only and allows subsequent restore operations to
the database.
To restore another increment after you perform a restore, you must specify -lockdb
before an append restore operation. You cannot do an append restore operation
unless the database was locked in a previous restore operation.

After the restore is complete, you can unlock the database by using the nzrestore
command and specify the database, for example:
nzrestore -db dev -unlockdb
Up-to-x restore
Up-to-x restore restores a database from a full backup and then up to the specified
increment. You can follow the up-to-x restore with a step-by-step restore.
Issue the -incrementlist option to view a report that lists increment numbers.
For example, the following command restores the full backup of database dev and
then up to increment 4.
nzrestore -db dev -connector netbackup -increment 4
Step-by-step restore
Step-by-step restore restores single incrementals in chronological order. The

nzrestore command maintains a restore history system table on the target system
and queries this table to determine which increment to restore.
Remember: Lock the database with the first nzrestore command and to unlock it
with the last.
For example, the following command line restores the full backup and then up to a
specific incremental of the database dev, and then steps through the following
incrementals.
nzrestore -db dev -connector netbackup -increment 4 -lockdb true
nzrestore -db dev -connector netbackup -increment Next -lockdb true
nzrestore -db dev -connector netbackup -increment Next -lockdb false
To begin with the first increment when the database does not yet exist, specify the
-increment 1 option. You can then step through the increments by specifying
-increment Next.
Remainder restore
A remainder restore restores all the remaining increments from a backup set that
are not yet restored. For example, after you restore to an increment ID (and
possibly some step restores), the following command restores any remaining
increments in the backup set.
nzrestore -db dev -connector netbackup -increment REST
Restore History report

Use the Restore History report during a multistep restore to learn what restores
were run on the system.
The following example displays the restore history for a specific database:
nzrestore -history
Note: You can further refine your results by using the -db and -connector options,
or use the -v option for more information. You use the -db option to see only the
history of a specified database.

Table 13-11. Restore history source
Column Description
Restore DB The name of the restore database.
Backup DB The name of the source database.
OpType The type of restore (for example, users, full, Incr:upto, Incr:next, Incr:rest).
Db Locked Whether the database is locked.
Date The date and time that the restore was initiated.
Status The status (completed, failed, in-progress).
Log File The log file for the restore.
Veritas NetBackup connector

The Veritas NetBackup environment includes a NetBackup server, one or more
media servers, and one or more client machines. The IBM Netezza host is a
NetBackup client machine.
You install the 32-bit or 64-bit NetBackup Client for Linux software on the Netezza
host and the Netezza components communicate with the NetBackup client
software to perform backup and restore operations. The Netezza components do
not assume any specific media, but instead rely on the NetBackup Media Server
for configuration of the media server and storage devices. The Netezza solution
has been tested with NetBackup versions 6.5, 7.1, and 7.6.
If you plan to use multi-stream backup and multi-stream restore support, consult
with your NetBackup administrator to confirm that it is configured to support
your expected maximum stream count. NetBackup has multiple settings for
limiting concurrent stream counts. On the Master Server, there is a Maximum jobs
per client global attribute. There is also a Policy-level attribute, Limit jobs per
policy. The job limit is the minimum of the global setting and the policy setting.
There is also a Maximum concurrent jobs setting on disk storage units. See the
NetBackup documentation for more information.
Related concepts:
Installing the Veritas NetBackup license

To use the NetBackup-Netezza integration, you must install a license key on the
Veritas NetBackup server so that you can create a backup policy of type
‘DataStore.’
About this task
To add the license, complete the following steps.

Procedure
1. On the NetBackup Administration Console, select Help > License Keys.
2. Click New.
3. In the Add a New License Key dialog, enter the following key and then click
Add:
DEXW-PM9K-R38B-UZPN-OPPR-PPXP-PPCP-PPPP-PP6
Results
The new license key displays in the license list.
Configuring NetBackup for a Netezza client

About this task
To back up and restore from NetBackup, you must configure the NetBackup
environment. Complete the following steps.
Procedure
1. Make the IBM Netezza host network-accessible to the NetBackup Master
Server.
2. Confirm that at least one NetBackup Media Server and storage device is
connected to NetBackup, is operational, and is available to NetBackup policies.
3. Install the NetBackup Client for Linux on the Netezza host.
4. Create a NetBackup policy for Netezza backup.
NetBackup policy
A NetBackup policy contains the configuration settings for an IBM Netezza
database backup. It defines the rules that NetBackup uses when it backs up clients.
You use the NetBackup Administration Console to configure a NetBackup policy.
For a Netezza database backup, the NetBackup policy is a “DataStore” policy. The
following table describes the relevant policy settings.
Table 13-12. NetBackup policy settings
Category Setting Value
Attributes Policy Type DataStore
Attributes Storage Unit Previously configured NetBackup Storage Unit,
suitable for the Netezza database backup destination.
Attributes Keyword Phrase Optional user-supplied keyword phrase. Can be used
to help distinguish between backups in the Client
Backups Report in NetBackup. You might use the
database name.
Schedule Type of Backup Automatic for NetBackup-scheduled backups
Application for user-initiated backups

Schedule * A policy must include at least one schedule with
which you can set the valid time windows for
Netezza backups and the calendar or frequency
specifications for automatic NetBackup-initiated
backups. Because you can restore at any time, there is
no need for a schedule.
Client Name The Netezza host name

Table 13-12. NetBackup policy settings (continued)
Category Setting Value
Backup Sections Sections List The Netezza host-resident script file that starts the
appropriate Netezza database backup. Specify the full
path on the Netezza host.
Netezza backup policy

An IBM Netezza database backup policy is a script file that runs on the Netezza
system to perform the backup.
The script file consists of an nzbackup command line with the appropriate
arguments. Each scheduled, automated backup operation with a distinct nzbackup
command line must have its own policy.
For each database, your system should have a separate policy and script file for
each backup type. For one database, you can have three policy and script files,
representing the full, differential, and cumulative backup types. If you had three
databases, you would have nine policy and script files, plus possibly one for the
-globals option you specified.
Integrate Veritas NetBackup to Netezza

This section contains the procedures for integrating Veritas NetBackup with your
IBM Netezza system. This section also describes the procedures for backing up and
restoring your system by using the Netezza commands and utilities.
The following procedures describe in general how to use the UIs. The commands
and menus can change with updates or patches to the backup software; these
procedures are intended as a general overview.
Related concepts:
“Procedures for backing up and restoring by using Veritas NetBackup” on page
13-40
The procedures in this section describe how to perform backups and restores by
using the Veritas NetBackup utilities.
Preparing your system for integration

About this task
To prepare an IBM Netezza system for NetBackup integration, complete the

following steps.
Procedure
1. Obtain the following name information for your Netezza system:
v If your system is an HA system, ask your network administrator for your
floating IP address.
v If your system is a standard (non-HA) system, ask for the external DNS
name for the Netezza host.
Important: Do not proceed without the system name information.

2. In your /nz/data/config directory, open the file backupHostname.txt by using
any text editor and edit the file as follows:
v If your system is an HA system, replace the HOSTNAME value with the
ODBC name you obtained in the previous step.

v If your system is a non-HA model, replace the HOSTNAME value with the
external DNS name.
3. Install the Veritas NetBackup Client Software onto the Netezza host.
If your system is an HA system, install the software on both hosts.
4. To check the version and release date of the NetBackup software, view the
/usr/openv/netbackup/bin/version file.
5. Edit the /usr/openv/netbackup/bp.conf file by using any text editor.
The file includes the variables CLIENT_CONNECT_TIMEOUT and
CLIENT_READ_TIMEOUT. Set both variables to the value 18000. Add the variables if
they are not in the file:
CLIENT_CONNECT_TIMEOUT = 18000
CLIENT_READ_TIMEOUT = 18000
Note: The timeout settings are important. If a database restore fails with the
error:
Connector exited with error: ’ERROR: NetBackup getObject() failed with
errorcode (-1): Server Status: Communication with the server has not been
initiated or the server status has not been retrieved from the server
The problem can be that the CLIENT_READ_TIMEOUT set on the NetBackup server
expired before the restore finished. This error can occur when you are restoring
a database that contains many tables with small changes, such as frequent
incremental backups, or a database that contains many objects such as UDXs,
views, or tables. If your restore fails with this error, you can increase the
CLIENT_READ_TIMEOUT value on the NetBackup server, or you can take steps to
avoid the problem by specifying certain options when you create the database
backup. For example, when you create the database backup, you can specify a
multi-stream backup by using the nzbackup -streams num option, or you can
reduce the number of files that are committed in a single transaction by using
the nzbackup -connectorArgs "NBC_COMMIT_OBJECT_COUNT=n" option, or both, to
avoid the timeout error. This error message might display for other reasons, so
if this workaround does not resolve the issue, contact Netezza Support for
assistance.
6. Make sure that the backups done by one host are visible to another host. If you
have a Netezza HA environment, for example, the backups performed by Host
1 should be visible to Host 2.
There are many ways that you can make the backups from one host visible to
another. See the Veritas NetBackup Administrators Guide, Volume I for UNIX and
Linux, and specifically to the section on managing client restores. Two possible
methods follow:
v You can open access to all hosts by updating the timestamp on the following
file on the NetBackup Master Server.
touch /usr/openv/netbackup/db/altnames/No.Restrictions
If the touch command fails, make sure that the altnames directory exists. If
necessary, create the altnames directory and rerun the command.
v You can give Host1 access to all backups created by Host2 and vice versa. To
do this, update the timestamp on two files:
touch /usr/openv/netbackup/db/altnames/host1
touch /usr/openv/netbackup/db/altnames/host2
For example, if the names of your HA hosts are nps10200-ha1 and
nps10200-ha2 then you would create the following files:
touch /usr/openv/netbackup/db/altnames/nps10200-ha1
touch /usr/openv/netbackup/db/altnames/nps10200-ha2

Important: You must use one of the two previous methods to open access. If
you skip this step, your restore will not work correctly on an HA system. This
also applies to redirected restores.
Related concepts:
“Redirect a restore” on page 13-40
Creating a NetBackup policy

About this task
To create a Veritas NetBackup policy, complete the following steps.
Procedure
1. Start the NetBackup Administration Console.
2. In the right pane, select Create a Backup Policy. The Backup Policy
Configuration Wizard starts.
3. Click Next in the Welcome dialog.
4. In the Policy Name and Type dialog, type a policy name, then select
DataStore from the policy type list, and then click Next.
5. In the Client List dialog, complete the following steps.
a. Click Add.
b. Enter the floating IP address or the external DNS name (the value you
previously entered for HOSTNAME in the file backupHostname.txt) in the
Name field.
c. Click Next.
6. In the window, click the menu and select the RedHat Linux operating system
that is running on your IBM Netezza host. Most Netezza systems use Intel,
RedHat 2.4, but if you are not sure, run the uname -r command on your
Netezza host to display the kernel release number.
7. Click OK and then click Next in the Client List dialog.
The operating systems in the list are based on the client binaries that are
installed on the NetBackup master server. If you do not install the correct
client software on the NetBackup server, the list might be empty or might not
include the Red Hat Linux client software. For more information about
installing the client software, see the Veritas NetBackup Installation Guide.
8. In the Backup Type dialog, select Automatic Backup to enable it, then click
Next.
Restriction: Do not specify values for the full path script. You supply this
information in a later step.
9. In the Rotation dialog, select your time slot rotation for backups and how long
to retain the backups, then click Next.
10. In the Start Window dialog, select the time options for the backup schedule
and click Next. A dialog opens and prompts you to save or cancel the backup
policy that you created.
11. Click Finish to save the backup policy.
Initiating backups from the NetBackup Administration Console

About this task
After you create a backup policy, complete the following steps to initiate an
automatic backup from the NetBackup Administration Console.

Procedure
1. In the left-pane of the NetBackup Administration Console, expand the Policies
list.
2. Double-click the policy that you created in the previous procedure.
3. In the Change Policy dialog, click the Backup Selections tab.
4. Click New and specify the full path to the backup script that will be invoked
by NetBackup as part of scheduled automatic backups. The full path is the path
name on the IBM Netezza host. Usually the backup script contains a single
command line that runs nzbackup for a particular backup operation. You can
create the script manually by using a text editor.
For example, the following line in a text file would back up the database
named “sales” by using the Netezza user account “joe”:
/nz/kit/bin/nzbackup -db sales -connector netbackup -u joe -pw
password -connector netbackup -connectorArgs
"DATASTORE_SERVER=NetBackup_master_server:DATASTORE_POLICY=NetBack
up_policy_name"
Rather than specify the -connectorArgs argument, you can set the environment
variables DATASTORE_SERVER and DATASTORE_POLICY. If you set the environment
variables, and then use the command-line argument -connectorArgs, the
command-line argument takes precedence.
If you are concerned about using a clear-text password, you can run the same
nzbackup as follows:
a. Change user to root.
b. Cache the password for user “joe” by using the nzpassword command.
c. Run nzbackup without the password.
nzbackup -db sales -connector netbackup -u joe
After you cache the password, you can use nzbackup without the -pw option.
You only cache the password one time.
Backups that are initiated by using the nzbackup command on the Netezza
host use the schedule of type “Application Backup.” You can click the
Schedules tab and check that the schedule for allowing backups is set
appropriately.
Initiate backups from the Netezza CLI

To initiate backups from the IBM Netezza CLI, you must specify the NetBackup
datastore server and NetBackup Policy in the command. The following is sample
syntax.
nzbackup -db dbname -connector netbackup -connectorArgs
"DATASTORE_SERVER=NetBackup_master_server:DATASTORE_POLICY=
NetBackup_policy_name"
variables DATASTORE_SERVER and DATASTORE_POLICY. If you set the environment
variables, and then use the command-line argument -connectorArgs, the
command-line argument takes precedence.
Restore a database from an existing backup by using the

Netezza CLI
Restore a database by running nzrestore on the IBM Netezza host. The following
is a sample syntax.
nzrestore -db dbname -connector netbackup -connectorArgs
"DATASTORE_SERVER=NetBackup_master_server"

variable DATASTORE_SERVER. If you set the environment variable, and then use the
command-line argument -connectorArgs, the command-line argument takes
precedence.
The restore operation does not use a NetBackup policy or schedule.
Redirect a restore
Typically, you restore a backup to the same IBM Netezza host from which it was
created. If you want to restore a backup that is created on a different Netezza host:
v Configure Veritas NetBackup for a “redirected restore.” For more information,
see the Veritas NetBackup documentation.
v Use the -npshost option of the nzrestore command to identify the Netezza host
from which the backup was created. The following is sample syntax.
nzrestore -db dbname -connector netbackup -connectorArgs
"DATASTORE_SERVER=NetBackup_master_server" -npshost origin_nps
Related tasks:
“Preparing your system for integration” on page 13-36
NetBackup troubleshooting
The Activity Monitor in the NetBackup Administration Console shows the status of
all backups and restores. If the monitor shows that a backup or restore failed, you
can double-click the failed entry to obtain more information about the problems
that caused the failure.
Procedures for backing up and restoring by using Veritas

NetBackup
The procedures in this section describe how to perform backups and restores by
using the Veritas NetBackup utilities.
Related concepts:
“Integrate Veritas NetBackup to Netezza” on page 13-36
Creating a user-directed backup

You can create a user-directed backup by using NetBackup.
About this task
As an example, this procedure runs a host backup by using the nzhostbackup

command.
The nzhostbackup command creates a single file that is written to the local disk or
other storage accessible from the IBM Netezza host. You can send this file to
NetBackup by using the bpbackup command-line utility, which is included with the
NetBackup client software installed on the Netezza host. You can later transfer the
file back to its original location by using the bprestore command-line utility (also
a part of the NetBackup client software). You can then restore the file by using the
nzhostrestore command.
To create a user-directed backup, complete the following steps.
Procedure
1. Create a NetBackup policy of type Standard.
2. Edit the policy schedule to match your intentions for backup.

3. Specify the Netezza host as a client.
4. Set the storage unit or other policy attributes to your preferences.
5. Log on to the Netezza host.
6. Create the host backup based on your backup policy. For example:
nzhostbackup /nz/tmp/hostbackup.20070521
7. Transfer the file to NetBackup by using the bpbackup utility. For example:
bpbackup -p nzhostbackup -w -L /nz/tmp/hostbackup.log
/nz/tmp/hostbackup.20070521
Results
Keep in mind the following important points for the bpbackup utility and the
example:
v Specify the explicit path to the bpbackup command if it is not part of your
account's PATH setting. The default location for the utility is
/usr/openv/netbackup/bin.
v In the sample command, the -L option specifies the log file where the status of
the backup operation is written. Review the file because the utility does not
return error messages to the console.
v The -w option causes the bpbackup utility to run synchronously; it does not
return until the operation completes.
v The -p option specifies the name of the NetBackup policy, which you defined in
step 1 on page 13-40.
v You can display syntax for the bpbackup utility by running bpbackup without
options.
Note: An alternative to the bpbackup command is the bp interactive NetBackup

client utility. The utility steps you through a backup or a restore.
Perform a restore
Run the bprestore NetBackup utility to restore the host backup file. The following
is an example.
bprestore -p nzhostbackup -w -L /nz/tmp/hostrestore.log
/nz/tmp/hostbackup.20070521
Keep in mind the following important points for the bprestore utility and the
example:
v Specify the explicit path to the bprestore command if it is not part of your
account PATH setting. The default location for the utility is /usr/openv/
netbackup/bin.
v You can display syntax for the bprestore utility by running bprestore without
options. See the Veritas NetBackup Commands Reference Guide.
Note: An alternative to the bprestore command is the bp interactive NetBackup

client utility. The utility steps you through a backup or a restore.
Set up an automatic host backup

To set up an automatic host backup, create a script file and two NetBackup
policies.
v The script file runs a host backup to a file system accessible from the IBM
Netezza host, and then runs a user-directed transfer of that backup to
NetBackup by using the bpbackup utility.

v For the two NetBackup policies you create, one runs the user-directed backup
and the other creates an automatic schedule that runs the script.
The following contents are for the sample script, /nz/opt/backup/nphostbackup.sh.

#!/bin/bash
#
# nphostbackup.sh - perform backup of host catalog and send it
# to NetBackup.
#
# set up the user (password cached using nzpassword)
export NZ_USER=nzuser
# set up the backup filename

today='/bin/date +%Y%m%d'
filename=nzhostbackup.${today}
# path to NetBackup client utilities

nbbin="/usr/openv/netbackup/bin"
# host backup to disk

/bin/bash /nz/kit/bin/nzhostbackup /nz/tmp/${filename}
# transfer backup file to NetBackup using user-directed policy

# for NPS host file system
${nbbin}/bpbackup -p nzhostbackup -w /nz/tmp/${filename}
# return success/failure status to NetBackup for the Activity Monitor

exit $?
Keep in mind the following important points for the sample script:
v The bpbackup utility references the nzhostbackup policy, which is a NetBackup
policy of type Standard. The policy includes a schedule that allows for a
user-directed backup during the specified time period, and lists the Netezza host
as a client.
v To run the script, you create a NetBackup policy of type DataStore. You can set
this policy to have an automatic schedule for regular host backups. You set the
frequency and time period for the backups. Ensure that the policy lists the script
file in Backup Selections. The script file reference must include the full path to
the backup file as you would reference it on the Netezza host.
v Because the script runs as root on the Netezza host, the Netezza user must be
set inside the script by using the NZ_USER variable. The user's password must be
cached by using the nzpassword utility.
IBM Spectrum Protect (formerly Tivoli Storage Manager) connector

You can use the IBM Netezza host to back up data to and restore data from
devices that are managed by an IBM Spectrum Protect server. This section
describes how to install, configure, and use the integration feature.
Throughout these topics, the names IBM Spectrum Protect and Tivoli Storage
Manager (or TSM) are both used to refer to IBM's data protection platform of
solutions.
with your Tivoli Storage Manager administrator to confirm that it is configured to
support your expected maximum stream count. For Tivoli Storage Manager
backups, the maximum number of streams is controlled by the MAXSESSIONS option
in the Tivoli Storage Manager Admin console (dsmadmc):
v Display the value by using query option MAXSESSIONS.
v Set the value by using setopt MAXSESSIONS value.
If you specify more streams than allowed by the MAXSESSIONS value, the Tivoli
Storage Manager server displays the following error message and the backup ends:
Error: Connector init failed: 'ANS1351E (RC51) Session rejected: All server
sessions are currently in use
Related concepts:
Tivoli Storage Manager backup integration

If you have an IBM Spectrum Protect (formerly Tivoli Storage Manager) solution in
your environment, you can integrate Netezza data backup and restore operations
with that solution. By defining the Netezza host as a client of the Tivoli Storage
Manager server, you can use the standard Netezza backup solutions to create
backups on media devices that are managed by the Tivoli Storage Manager server.
Similarly, you can use Netezza restore utilities to retrieve and load data from the
backup locations. The Netezza solution has been tested with IBM Spectrum Protect
version 5.4, 5.5, 6.1, 6.2, and 7.1.
This guide does not provide details about the operation or administration of the
Tivoli Storage Manager server or its commands. For information about the Tivoli
Storage Manager operation and procedures, see your Tivoli Storage Manager user
documentation.
Tivoli Storage Manager encrypted backup support

If your Tivoli Storage Manager environment uses encryption, you can configure the
Netezza Platform Software backups to use encrypted backups.
To configure encrypted backups, you must specify some settings to the TSM
configuration files in the backup archive and API clients. For each TSM server in
your environment, you can specify that the TSM backup connector use encrypted
backups to store the files sent by the Netezza backup utilities.
Configuring the Netezza host

About this task
This section describes the procedures to make an IBM Netezza host a client to a
Tivoli Storage Manager server. The following procedure is overall process for
configuring a Netezza host.
Procedure
1. Prepare your system for the Tivoli Storage Manager integration.
2. Install the Tivoli Storage Manager client software on the Netezza host.
3. Set up the client configuration files.
Preparing your system for Tivoli Storage Manager integration

About this task
To prepare an IBM Netezza system for integration, complete the following steps.

Procedure
1. Log in to your Netezza system as the nz user.
2. Obtain the following name information about your Netezza system:
Restriction: Do not proceed without the name information.

external DNS name.
Setting up Netezza host client

About this task
You can install the 32-bit or 64-bit Tivoli Storage Manager client software on your
Netezza host system to enable the integration. You can obtain the Tivoli Storage
Manager client software from IBM. If you have an HA Netezza system, repeat
these installation steps on both Host 1 and on Host 2.
To install the Tivoli Storage Manager client software on the Netezza system,
complete the following steps.
Procedure
1. Log in to the Netezza system as the root user.
2. Place the Tivoli Storage Manager UNIX client disk in the drive.
3. Mount the CD/DVD by using either of the following commands:
v mount /media/cdrom
v mount /media/cdrecorder
If you are not sure which command to use, run the ls /media command to
display the path name (cdrom or cdrecorder) to use.
4. To change to the mount point, use the cd command and specify the mount path
name that you used in step 3. This guide uses the term /mountPoint to refer to
the applicable disk mount point location on your system, as used in step 3.
cd /mountPoint
5. Change to the directory where the packages are stored, for example:
cd /mountPoint/tsmcli/linux86
6. Enter the following commands to install the 32-bit Tivoli Storage Manager
ADSM API and the Tivoli Storage Manager Backup-Archive (BA) client. The BA
client is optional, but it is recommended because it provides helpful features
such as the ability to cache passwords for Tivoli Storage Manager access and
also to create scheduled commands.
rpm -i TIVsm-API.i386.rpm
rpm -i TIVsm-BA.i386.rpm

What to do next
Make sure that you use the default installation directories for the clients (which are
usually /opt/tivoli/tsm/client/api and /opt/tivoli/tsm/client/ba). After the
installation completes, proceed to the next section to configure the Netezza as a
client.
Configuring the Netezza client

About this task
Follow these steps to set up the IBM Spectrum Protect (formerly Tivoli Storage
Manager) configuration files, which make the Netezza system a client of the Tivoli
Storage Manager server. If you have an HA Netezza system, make sure that you
repeat these configuration steps on both Host 1 and on Host 2.
There are two sets of configuration files, one set for the API client and one set for
the B/A client. Follow these steps to configure the files for the API client. If you
also installed the B/A client RPM, make sure that the changes that you make to
the API client files are identical to the changes that you make for the BA client files
which are in the /opt/tivoli/tsm/client/ba/bin directory. You can either repeat
these steps for the B/A client files or copy the updated API client dsm.opt and
dsm.sys files to the B/A bin directory.
Procedure
1. Make sure that you are logged in to the Netezza system as root.
2. Change to the following directory:
cd /opt/tivoli/tsm/client/api/bin
3. Copy the file dsm.opt.smp to dsm.opt. Save the copy in the current directory.
For example:
cp dsm.opt.smp dsm.opt
4. Edit the dsm.opt file by using any text editor. In the dsm.opt file, proceed to
the end of the file and add the following line, which is shown in bold, where
server is the host name of the Tivoli Storage Manager server in your
environment:
******************************************************************
* IBM Tivoli Storage Manager *
* *
* Sample Client User Options file for UNIX (dsm.opt.smp) *
******************************************************************
* This file contains an option you can use to specify the TSM
* server to contact if more than one is defined in your client
* system options file (dsm.sys). Copy dsm.opt.smp to dsm.opt.
* If you enter a server name for the option below, remove the
* leading asterisk (*).
******************************************************************
* SErvername A server name defined in the dsm.sys file
SErvername server
If you have multiple Tivoli Storage Manager servers in your environment, you
can add a definition for each server. However, only one definition can be the
active definition. Any additional definitions should be commented out by
using the asterisk (*) character. The active dsm.opt entry determines which
Tivoli Storage Manager server is used by the Tivoli Storage Manager
connector for backup and restore operations. If there are multiple
uncommented SERVERNAME entries in dsm.opt, the first uncommented entry
is used.

If you plan to use Tivoli encryption for your backups, add the following
settings to the server definition. For the TRACEFILE setting, specify a location
on the Netezza host or on a connected filesystem where you can store a trace
file for more information about the backups. For details about the settings, see
the Tivoli documentation.
TRACEFILE /nzscratch/user/trace.txt
TRACEFLAGS API API_DETAIL ENCRYPT
5. Save and close the dsm.opt file.
6. Copy the file dsm.sys.smp to dsm.sys. Save the copy in the current directory.
For example:
cp dsm.sys.smp dsm.sys
7. Edit the dsm.sys file by using any text editor. In the dsm.sys file, proceed to
the end of the file and add the settings, which are shown in bold, where server
is the name of the Tivoli Storage Manager server in your environment,
serverIP is the host name or IP address of the Tivoli Storage Manager server,
and client_NPS is the node name for the Netezza host client:
******************************************************************
* IBM Tivoli Storage Manager *
* *
* Sample Client System Options file for UNIX (dsm.sys.smp) *
******************************************************************
* This file contains the minimum options required to get started

* using TSM. Copy dsm.sys.smp to dsm.sys. In the dsm.sys file,
* enter the appropriate values for each option listed below and
* remove the leading asterisk (*) for each one.
* If your client node communicates with multiple TSM servers, be

* sure to add a stanza, beginning with the SERVERNAME option, for
* each additional server.
******************************************************************
SErvername server
COMMMethod TCPip
TCPPort 1500
TCPServeraddress serverIp
NODENAME client_NPS
For the NODENAME value, use the naming convention client_NPS, where
client is the host name of the Netezza host, to help uniquely identify the client
node for the Netezza host system.
If you plan to use Tivoli encryption for your backups, add the following
settings to the server definition. For the ENCRYPTIONTYPE value, use the
encryption value specific to your Tivoli configuration (AES128 is an example).
For the include.encrypt setting, you can specify a setting such as /.../* to
encrypt all of the TSM Netezza backups, or you can specify a specific Netezza
backup object and backup type. For example, /FS1/MY_DB/FULL indicates that
the TSM server should encrypt the full backups of the MY_DB database stored
in the /FS1 location. For details about the settings, see the Tivoli
documentation.
ENCRYPTKEY GENERATE
ENCRYPTIONTYPE AES128
include.encrypt /.../*
If you have multiple Tivoli Storage Manager servers in your environment, you
can create another set of these definitions and append each set to the file. For
example:
SErvername server1
COMMMethod TCPip
TCPPort 1500

TCPServeraddress server1Ip
NODENAME client_NPS
SErvername server2
COMMMethod TCPip
TCPPort 1500
TCPServeraddress server2Ip
NODENAME client_NPS
If you specify more than one Tivoli Storage Manager server definition in the
dsm.sys file, you can create corresponding definitions in the dsm.opt file as
described in step 4 on page 13-45.
8. If you installed the Tivoli 5.4 client software on your hosts, you must also add
the following options in the dsm.sys file.
ENCRYPTIONTYPE DES56
PASSWORDACCESS prompt
Verify that there are no other uncommented lines for the ENCRYPTIONTYPE
and PASSWORDACCESS options.
The PASSWORDACCESS prompt option disables automatic, passwordless Tivoli
Storage Manager authentication. Each operation that uses the Tivoli Storage
Manager connector requires that you to enter a password. You can supply the
password in the nzbackup and nzrestore connectorArgs option as
TSM_PASSWORD=password or you can set TSM_PASSWORD as an environment
variable.
9. Save and close the dsm.sys file.
10. If you installed the BA client kit, do one of the following steps:
v Change to the /opt/tivoli/tsm/client/ba/bin directory and repeat steps 3
on page 13-45 through 9 to configure the BA client dsm.opt and dsm.sys
files. Make sure that the changes that you make to the API client files are
identical to the changes that you make for the BA client files.
v Copy the dsm.opt and dsm.sys files from the /opt/tivoli/tsm/client/api/
bin directory to the /opt/tivoli/tsm/client/ba/bin directory.
Tivoli Storage Manager transaction sizes: For Tivoli Storage Manager

configurations, the TXNGROUPMAX option specifies the number of objects that
can be transferred between a client and the server in one backup transaction. The
maximum value is 65000. The default value is 256 objects. If the value is too low,
your backups can fail with a start a new transaction session error.
If you encounter this error, review and increase the TXNGROUPMAX setting to a
value that is larger than the maximum number of objects that a single backup
operation will try to create. For example, if you are performing incremental
backups, then use a value that is at least twice the table count. Also, add a small
number (such as five) of additional objects for backup metadata files. If your
database has UDXs, add an additional two objects for each UDX. If you are using
multi-stream backups, then use the maximum value of either double the UDXs, or
double the tables divided by the stream count, and add the additional five objects
for metadata objects.
To set the TXNGROUPMAX value by using the GUI, go to the Policy Domains
and Client Nodes > Your client node > Advanced Settings > Maximum size of a
transaction. The options are Use server default or Specify a number (4-65,000). Be
sure to repeat this process on each node (Host 1 and Host 2), and to use the same
setting for each node. If you choose Specify a number, the setting cannot be

changed from the client. If you chose Use server default, you can specify the value
from the clients by using the dsmadmc application, 'setopt txngroupmax <value>' or
'update node txngroupmax=<value>'.
Caching a password
About this task
Optionally, you can use the IBM Spectrum Protect (formerly Tivoli Storage
Manager) connector to cache user passwords on their client system. If you cache
the password, you do not have to specify the password for commands to the Tivoli
Storage Manager connector (as described in “The nzbackup and nzrestore
commands with the Tivoli Storage Manager connector” on page 13-57).
Restriction: If you use the Tivoli Storage Manager 5.4 client, you cannot use the
cached password support. You must use PASSWORDACCESS prompt for the connector
to work correctly.
If you have an HA Netezza system, make sure that you repeat these steps on Host
1 and on Host 2.
To cache a password for authentication, complete the following steps.
Procedure
1. Change to the following directory:
cd /opt/tivoli/tsm/client/ba/bin
2. Edit the dsm.sys file by using any text editor and add the following line:
PASSWORDACCESS generate
Review the file to make sure that there are no other lines that contain the
PASSWORDACCESS parameter. If there are lines, comment them out.
3. Save and close the dsm.sys file.
4. As a test, log in as root and run the dsmc query session command to be
prompted for the client password.
5. Repeat steps 1 through 3 to edit the /opt/tivoli/tsm/client/api/bin/dsm.sys
API client file. This allows nzbackup to run by using the Tivoli Storage Manager
connector without specifying the Tivoli Storage Manager password.
Results
The dsmc command is in the /opt/tivoli/tsm/client/ba/bin directory. The client

installation also creates symbolic links to the Tivoli Storage Manager commands in
the /usr/bin directory. If /usr/bin is included in your PATH variable, you need not
specify a full path name to the command.
After the client authentication is successful, subsequent logins will not prompt for
a password until the password changes at the Tivoli Storage Manager server.
Configure the Tivoli Storage Manager server

Although there are several interfaces and methods for configure the IBM Spectrum
Protect (formerly Tivoli Storage Manager) server, the ISC Console is one simple
way to set up the backup connector configuration.

The following sections describe how to use the ISC Console for configuration. The
procedures describe in general how to use the UIs. The commands and menus can
change with updates or patches to the backup software; these procedures are
intended as a general overview.
Access the Tivoli Storage Manager ISC Console

To access the ISC Console on the IBM Spectrum Protect (formerly Tivoli Storage
Manager) server, open a web browser and point to the following URL:
http://tsm_server:8421/ibm/console
The tsm_server value is the host name or IP address of the Tivoli Storage Manager
server. Log in by using an account that is created for the Tivoli Storage Manager
server.
For a Tivoli Storage Manager 6 system, use the following URL:

https://tsm_administration_console:16311/ibm/console/
The tsm_administration_console value is the host name or IP address of the Tivoli

Storage Manager administration center, which might be different from the Tivoli
Storage Manager server. Log in by using an account that is created for the Tivoli
Storage Manager administration center.
If you cannot access the web interface, the interface might be stopped on the
server. For more information about accessing the Tivoli Storage Manager server by
using a command shell or SSH session and starting the TSM server or ISC Console,
see your Tivoli Storage Manager documentation.
The following procedures assume that you use a web browser to connect to the
ISC Console and are logged in successfully.
Overview of the Tivoli Storage Manager server configuration

process
The process to configure the IBM Spectrum Protect (formerly Tivoli Storage
Manager) server for Netezza database backups has these steps:
1. Create a storage pool to define the location or locations where the Netezza
backups are saved by the Tivoli Storage Manager server.
2. Define a policy domain that specifies the backup policy for a group of client
nodes, such as one or more Netezza systems. A policy specifies such
information as where the backup data is stored, how many backup versions to
keep, and the amount of time to keep archive copies. Create one policy domain
to manage all of your Netezza systems.
3. Register each Netezza host that has the Tivoli Storage Manager client software
as a client node of a Tivoli Storage Manager server.
4. Create a proxy node to represent the Netezza system and grant the Netezza
client node proxy authority over the proxy node.
The instructions are specific to Tivoli Storage Manager 5. The steps are similar for
Tivoli Storage Manager 6, but there might be minor changes in the names of
menus and dialogs in the later release.
Creating a storage pool

About this task
To create a storage pool on the IBM Spectrum Protect (formerly Tivoli Storage
Manager) server, complete the following steps.

Procedure
1. In the left navigation frame of the ISC Console, click Tivoli Storage Manager.
2. Click Storage Devices.
3. Select the Tivoli Storage Manager server from which you will be managing
your Netezza systems, and then select View Storage Pools from the Select
Action list.
4. In the Storage Pools section, select Create a Storage Pool from the Select
Action list.
5. Type a name for the storage pool and make sure that the storage pool type is
Random access, then click Next.
6. If you are creating a pool select Create a new disk volume and enter a volume
name and size. The volume name should be an absolute path name. For
example, if you want to create a volume named vol under the /home/backups
directory, type /home/backups/vol, then click Next. A Summary window opens
to display messages about the successful creation of the storage pool and its
information.
7. Click Finish.
Creating a policy domain

About this task
To create a policy domain on the IBM Spectrum Protect (formerly Tivoli Storage
Manager) server, complete the following steps.
Procedure
2. Click Policy Domains and Client Nodes.
3. Select the Tivoli Storage Manager server from which you will manage your
Netezza systems, and then select View Policy Domains from the Select Action
list.
4. Select Create a Policy Domain from the Select Action list.
5. Type a name for the new policy domain and click Next.
6. Select a storage pool for backup data from the list, such as the one you created
in “Creating a storage pool” on page 13-49, then click Next.
7. In the Assign Client Nodes Now page, the application prompts you to assign
client nodes at this time. If you already registered the client node/nodes on
your Tivoli Storage Manager server, select Yes and click Next to proceed. (The
Assign Client Nodes page opens where you can list and select client nodes to
add to the domain.) Otherwise, select No and click Next to proceed. A
Summary window opens to display messages about the successful creation of
the policy domain and its information.
8. Click Finish.
Registering a Netezza client on a Tivoli Storage Manager server

About this task
To register an IBM Netezza system on the Tivoli Storage Manager server, you
create a client node that represents the Netezza host. For an HA Netezza system,
you must create two client nodes, one for Host1 and one for Host2; complete these
steps for Host 1, then repeat them for Host 2.

To register a Netezza system as a client on a Tivoli Storage Manager server,
Procedure
your Netezza systems, and then select View Policy Domains from the Select
Action list.
4. Select a policy domain and select Modify Policy Domain from the Select
Action list.
5. Click the arrow to the right of Client Nodes to expand the client nodes list.
6. Select Create a client node from the Select Action list.
7. Type a name for the Netezza host. The name must match the name that is
specified in the dsm.sys file on the client system.
8. Enter and confirm a password for client authentication, and choose an
expiration for the password. Click Next to continue.
9. You can either select Create administrator and assign it owner authority to
node or Assign owner authority to selected administrator, then click Next.
The administrator of a node can use the owner authority to perform
administrative tasks such as changing the client properties. A Summary
window opens to display messages about the successful creation of the client
node.
10. Click Finish. The newly created client node now displays in the Client Nodes
list.
11. Select the newly created client node and select Modify Client Node from the
Select Action list.
12. Click the Communications tab on the left.
13. Type in the TCP address and port in the fields. You can specify the host name
of the client (the Netezza system host name) and any unused port value (for
example, 9000). To list the used ports on the system, use the netstat
command.
14. Click the Advanced Settings tab on the left.
15. Change the maximum size of transaction value to a value such as 4096. The
maximum number of objects in a transaction cannot exceed 65000. Use caution
when you are selecting a maximum for the number of objects per transaction;
larger numbers can impact performance. Try to estimate the maximum
number of objects in the database and set the value accordingly. You could
begin with an estimate of three times the number of tables in the database.
16. Click OK to save the settings.
Creating a proxy node

About this task
You must create a proxy node on the IBM Spectrum Protect (formerly Tivoli
Storage Manager) server for each Netezza system (HA or standard), and then grant
the client node for the Netezza system proxy authority over the proxy node. The
client node can use proxy authority to use the proxy node to represent itself; that
is, the proxy node can represent the client node.

Procedure
Action list.
Action list.
6. Select Create a client node from the Select Action list.
7. Type a name for the proxy node. The name must match the name that is
specified in the /nz/data/config/backupHostname.txt file on the Netezza
client system.
8. Enter and confirm the password for client authentication (which was defined
in step 7 on page 13-51 of “Registering a Netezza client on a Tivoli Storage
Manager server” on page 13-50), and choose an expiration for the password.
Click Next to continue.
9. You can either select Create administrator and assign it owner authority to
node or Assign owner authority to selected administrator, then click Next. A
Summary window opens to display messages about the successful creation of
the client node.
10. Click Finish.
Results
The newly created client node now displays in the Client Nodes list.
Granting client authority:

About this task
To grant the client node or nodes proxy authority over the new proxy node,
Procedure
Action list.
Action list.
6. Select the proxy node and then select Modify Client Node from the Select
Action list.
7. Select the Proxy Authority tab on the left, and then select Grant Proxy
Authority from the Select Action list on the right.
8. Select the client node that represents the Netezza host. If the Netezza system is
an HA system, select both client nodes.
9. Click OK to complete the proxy assignment.

Changing backup expiration settings
About this task
When you perform a full backup of a database to IBM Spectrum Protect (formerly
Tivoli Storage Manager) by using nzbackup, any previous backups of that database
are marked as inactive. The Tivoli Storage Manager server configuration settings
specify how it manages inactive files. The Tivoli Storage Manager default is to
make all inactive files immediately unavailable. If you want the ability to restore
from backup sets other than the most recent, review and adjust the Tivoli Storage
Manager configuration setting for Number of days to keep inactive versions. The
default is zero, which means that only the latest backup set is available for use in
restores.
To change the backup expiration setting, complete the following steps.
Procedure
2. Click Policy Domains and Client Nodes. In Tivoli Storage Manager 6, this
menu is Policy Domains.
your Netezza systems.
4. Select the policy domain which has the Netezza host machine as a client node.
5. In the Properties section, select the Management Class which governs the
Netezza host client node.
6. In the left pane of the Class Properties page, select Backup settings.
7. Review the Number of days to keep inactive versions field to specify how
long you want to keep inactive (that is, older than the latest) backup sets.
Set this value to a positive number to keep and use inactive backup sets for
that period of days. For more information about the range of values and
possible impacts to the Tivoli Storage Manager server, see the Tivoli Storage
Manager documentation.
Redirect a restore
Typically, you restore a backup to the same IBM Netezza host from that it was
created. If you want to restore a backup that was created on one Netezza host to a
different Netezza host, you must adjust the proxy settings.
For example, assume that you have a Netezza host named NPSA, for which you
defined a client node named “NPSA NPS” and a proxy node named NPSA on the
Tivoli Storage Manager server. Assume also that there is a backup file for the
NPSA host on the Tivoli Storage Manager server.
If you want to load the backup file onto a different Netezza host named NPSB,
then you must first ensure that NPSB is registered as a client to the Tivoli Storage
Manager server. Assume that there is a client node for “NPSB NPS” and a proxy
node named NPSB for this second host.
To redirect the restore file from NPSA to NPSB, you must grant the client node
“NPSB NPS” proxy authority over the proxy node NPSA. After you grant the
proxy authority to “NPSB NPS”, you are able to restore the backup for NPSA to
the NPSB host by using a command similar to the following command:
nzrestore -db database -connector tivoli -npshost NPSA

The value database is the name of the database that was backed up from the
Netezza host NPSA.
Special considerations for large databases

If your IBM Netezza system has large databases (that is, databases which are
greater than several hundred GB in size), the default configuration settings for the
Tivoli Storage Manager server might not be sufficient to manage the backup and
restores of those large databases. If the database is too large for the default
configuration settings, the database backups might terminate and return errors
similar to the following error:
Error: Connector exited with error: ’ANS1017E (RC-50) Session
rejected: TCP/IP connection failure’
The server does not have enough recovery log space to continue the
current operation
The server does not have enough database space to continue the current
operation
There are some configuration settings changes that can help to avoid these errors
and complete the backups for large databases. These configuration settings depend
on factors such as network speed, Tivoli Storage Manager server load, network
load, and other factors. The following values are conservative estimates that are
based on testing, but the values for your environment can be different. If you
encounter errors such as timeouts and space limitations, try these conservative
values and adjust them to find the right balance for your server and environment.
v COMMTIMEOUT
Specifies the time in seconds that the Tivoli Storage Manager server waits for an
expected client response. The default is 60 seconds. You can obtain the current
value of the setting by using the QUERY OPTION COMMTIMEOUT command.
For large databases, consider increasing the value to 3600, 5400, or 7200 seconds
to avoid timeout errors, which can occur if the complete transfer of a database
does not complete within the time limit:
SETOPT COMMTIMEOUT 3600
v IDLETIMEOUT
Specifies the time in minutes that a client session can be idle before the Tivoli
Storage Manager server cancels the session. The default is 15 minutes. You can
obtain the current value of the setting by using the QUERY OPTION
IDLETIMEOUT command. For large databases, consider setting the value to 60
minutes:
SETOPT IDLETIMEOUT 60
v The default size of the Tivoli Storage Manager server database, 16 MB, might be
inadequate for large Netezza databases. Depending on the size of your largest
Netezza database, you can increase the default Tivoli Storage Manager database
size to a value such as 500 MB.
v The size of the recovery log might be inadequate for large Netezza databases or
those databases that have many objects (tables, UDXs). An increased value such
as 6 GB might be more appropriate. The recovery log should be at least twice
the size in GB as your largest table in TB. For example, if your largest table is 2
TB, the recovery log must be at least 4 GB. In addition, you might need a larger
log file if you run multiple concurrent backup jobs on the same Tivoli Storage
Manager server, such as several Netezza backups or a combination of Netezza
and other backups within the enterprise.

Increasing server database size
There are two ways to increase the IBM Spectrum Protect (formerly Tivoli Storage
Manager) server database capacity: you can manually add more database volumes,
or you can automatically grow the capacity with a space trigger.
Manually adding space to database volume:

About this task
To manually add database volume, complete the following steps.
Procedure
2. Click Server Maintenance.
3. Select the Tivoli Storage Manager server for which your Netezza system is a
client.
4. On the Select Action list, select Server Properties.
5. Select the Database and Log tab from the left navigation frame of the Server
Properties area.
6. In the Database area on the Select Action list, select Add Volume.
7. In the Volume name field, type the absolute path of the new volume that you
want to create.
8. In the New volume size field, type an appropriate size for the new volume. If
you are not sure, use the value 500.
9. To use the new volume immediately, select When adding the new volume,
expand the database capacity by and in the field, enter a value that is smaller
than the value specified for the New volume size field.
10. Click OK to create the volume.
Automatically adding space to database volume:

About this task
To add space automatically with a space trigger, complete the following steps.
Procedure
1. Repeat steps 1 through 5 of the previous procedure to display the Database
and Log area.
2. In the Database area on the Select Action list, select Create Space Trigger.
3. Specify values for the field for the automatic database expansion trigger. Use
the online help to obtain details about the operation of each field and setting.
The key fields to set for your environment are the Begin expansion at this
percentage of capacity, Expand the database by this amount, and Maximum
size fields.
4. Click OK to create the trigger.
Results
You can also create a database space trigger by using the define spacetrigger db
command. For example, the following command creates a trigger that increases the
size of database by 25% when it hits 85% of its capacity with no limit on
maximum size:
define spacetrigger db fullpct=85 spaceexpansion=25 maximumsize=0

Increasing recovery log volume
There are two ways to increase the server's recovery log capacity: you can
manually add more log volumes, or you can automatically grow the capacity with
a space trigger.
Manually adding space to log volume:

About this task
To manually add space to the log volume, complete the following steps.
Procedure
1. Repeat steps 1 on page 13-55 through 5 on page 13-55 of the previous
procedure to get to the Database and Log area.
2. In the Log area on the Select Action list, select Add Volume.
3. In the Volume name field, type the absolute path of the new volume that you
want to create.
4. In the New volume size field, type an appropriate size for the new volume. If
you are not sure, use the value 500.
5. To use the new volume immediately, select When adding the new volume,
expand the recovery log capacity by and in the field, enter a value that is
smaller than the value specified for the New volume size field.
6. Click OK to create the volume.
Automatically adding space to log volume:

About this task
To automatically add space with a space trigger, complete the following steps.
Procedure
1. Repeat steps 1 on page 13-55 through 5 on page 13-55 of the previous
procedure to display the Database and Log area.
2. In the Log area on the Select Action list, select Create Space Trigger.
3. Specify values for the field for the automatic log expansion trigger. Use the
online help to obtain details about the operation of each field and setting. The
key fields to set for your environment are the Begin expansion at this
percentage of capacity, Expand the log by this amount, and Maximum size
fields.
4. Click OK to create the trigger.
Results
You can also create a log space trigger by using the define spacetrigger log
command. For example, the following command creates a trigger that increases the
size of the recovery log by 25% when it reaches 85% of its capacity with no limit
on maximum size:
define spacetrigger log fullpct=85 spaceexpansion=25 maximumsize=0

The nzbackup and nzrestore commands with the Tivoli
Storage Manager connector
After you successfully configure the client (the IBM Netezza host) and the server
(the Tivoli Storage Manager server) for the backup and restore connections, you
can run the nzbackup and nzrestore commands and specify options for the Tivoli
Storage Manager connector.
For example, the following sample command backs up the Netezza database by
using Tivoli Storage Manager:
nzbackup -db myDb -connector tivoli -connectorArgs
"TSM_PASSWD=password"
In the command, the Tivoli Storage Manager server password is passed as a

connector argument. The TSM_PASSWD is the client password as defined in step 7
on page 13-51 of the “Registering a Netezza client on a Tivoli Storage Manager
server” on page 13-50.
For example, the following sample command restores the Netezza database by
using Tivoli Storage Manager:
nzrestore -db myDb -connector tivoli -connectorArgs
"TSM_PASSWD=password"
Host backup and restore to the Tivoli Storage Manager server

You can perform a backup and restore of the IBM Netezza host metadata by using
the Tivoli Storage Manager connector. You create scripts for the Netezza host,
which runs a host backup and sends the backup to the Tivoli Storage Manager
server, and scripts that retrieve and restore a backup. The nzhostbackup and
nzhostrestore commands do not directly support the Tivoli Storage Manager
connector.
For example, the following sample script uses the nzhostbackup command to create
a host backup in the specified /tmp archive and then sends the backup to the Tivoli
Storage Manager server:
#!/bin/bash
#
# nzhostbackup_tsm - back up the host catalog and send it to TSM server
archive="/tmp/nzhostbackup.tar.gz"
# Main script execution starts here
(
nzhostbackup "${archive}"
echo
echo "Sending host backup archive ’${archive}’ to TSM server ..."
dsmc archive "${archive}"
)
exit 0
Similarly, you can create a script to retrieve and reload a host backup from the
Tivoli Storage Manager server:
#!/bin/bash
#
# nzrestore_tsm - restore host backup from TSM using nzhostbackup_tsm

if [ "$#" -eq 0 ]; then
archive="’/tmp/nzhostbackup*’"
echo "Querying for backups in ${archive} for host ${hostname} ..."
echo
dsmc query archive "${archive}"
exit 0
fi
if [ "$#" -eq 1 ]; then

archive_name="${1}"
archive="${archive_name}"
echo "Restoring the specified backupset ’${archive}’ ..."
echo
(
dsmc retrieve "${archive}"
echo
echo "Archive ’${archive}’ retrieved, restoring it..."
nzhostrestore "${archive}"
)
fi
exit 0
Backing up and restoring data by using the Tivoli Storage

Manager interfaces
About this task
You can use the IBM Spectrum Protect (formerly Tivoli Storage Manager)
commands and interfaces to create a client node schedule, which is a record that
defines a particular client operation such as a backup or a restore. By using client
schedules, you can automate the backups of data from your Netezza host without
any user operator intervention. You can also automate the restore of data from one
Netezza system to another if you load data to a backup Netezza system regularly.
To use the client scheduler to automate tasks for the Netezza host client, you must
install the BA client package on the Netezza host as described in “Configuring the
Netezza host” on page 13-43.
Tivoli Storage Manager offers two ways to manage client scheduling: the client
acceptor daemon-managed services, and a Tivoli Storage Manager traditional
scheduler. You can use either method to manage client schedules. For details about
configuring and managing the Tivoli Storage Manager client scheduler, see the IBM
Tivoli Storage Manager for UNIX and Linux Backup-Archive Clients: Installation and
User's Guide, which is available from the IBM Support Portal at
http://www.ibm.com/support.
If you create more than one scheduled operation, the Tivoli Storage Manager
scheduler does not support overlapping schedules for operations; that is, one
operation must start and complete before a new operation is allowed to start. If
you create operations with overlapping schedules, the second operation is likely
skipped (does not start) because the first operation is still running. Make sure that
you allow enough time for the first operation to complete before a new operation
is scheduled to run.
To create a client schedule, complete the following steps.

Procedure
Action list.
4. Select the policy domain that you created for your Netezza host (as described
in “Creating a policy domain” on page 13-50) and select Modify Policy
Domain from the Select Action list.
5. Select the Client Node Schedules list to expand it.
6. From the Select Action list, select Create a Schedule.
7. In the Create Schedule area, complete the following steps:
a. Enter a name for the schedule in the Schedule name field. You can also
supply an optional description for the schedule.
b. Select the option Command - run a command on a client node machine.
c. Click Next.
8. In the Command to run field, specify the absolute path of the script that you
want to run and click Next. The following is an example path name:
’sh /nz/scripts/mybackup.sh’
The path name is the absolute path of the script file that is on the Netezza
host and must be preceded by the command sh and enclosed in single
quotation marks when it has spaces, as shown in the example. In most cases,
the script is an nzbackup or nzrestore command operation. For a backup
client schedule, the backup script usually contains a single command line that
runs nzbackup for a particular backup operation. You can create the script
manually by using a text editor.
9. In the Select Repetition Options area, select the data and time and the
frequency for the client schedule, then click Next.
The Tivoli Storage Manager scheduler does not support overlapping schedules
for operations; that is, one operation must start and complete before a new
operation is allowed to start. Make sure that you allow enough time for the
first operation to complete before a new operation is scheduled to run.
10. You can accept the defaults on the Advanced Schedule Options area and click
Next.
11. Select the client nodes (one or more Netezza hosts) that you want to associate
with this schedule. Make sure that you select the client node for the Netezza
host, not its proxy node, then click Next.
Typically, you would select only one client node (that is, one Netezza host) to
run this operation at one time. However, if you want to schedule the
operation for multiple hosts to occur at the same time, it is possible to select
multiple client nodes.
12. Review the information in the Summary and click Finish to create the client
schedule.
Results
Because the script runs as root on the Netezza host, the Netezza user must be set
inside the script by using the NZ_USER variable or specified with the -u user
argument. The user password must be cached by using the nzpassword utility, set
inside the script by using NZ_PASSWORD, or specified by using the -pw password
argument.

You can use the backup history to check the status of a backup operation. For
more information, see “Backup History report” on page 13-20.
Troubleshooting
The following topics describe some common problems and workarounds.
Client/server connectivity
You can check the network connections and configuration settings to ensure that
the IBM Netezza host (the client) can connect to the Tivoli Storage Manager server.
To check connectivity, use the dsmc query session command.
The command prompts for the client user password, and after a successful
authentication, it shows the session details.
Client version error

If you have installed multiple versions of the Tivoli Storage Manager clients in
your environment, you could encounter version errors when restoring backups that
were created using different APIs.
During a TSM restore, the following error could occur: Connector exited with
error: 'ANS1245E (RC122) The file has an unknown format. This error indicates
that an administrator had created a backup using a later TSM client (using a newer
TSM API) and tried to restore it using an older TSM client. This is a case where the
older TSM API cannot process backups that were created with the later TSM API,
and there might be compatibility issues. If your restore process fails with this error,
update the TSM client to a newer version and re-run the restore.
Basic file backup and restore

You can verify that the IBM Spectrum Protect (formerly Tivoli Storage Manager)
connector is configured properly with a simple backup and restore process for a
file.
To back up a single file, use the dsmc archive file command.
The file value specifies the path name of a file on the Netezza system. As a result
of the command, the file is saved in the configured storage pool for the Netezza
client. For the test, you can rename the test file to ensure that the subsequent
retrieval test works.
To restore the single file, use the dsmc retrieve file command:
As a result of the command, the file is retrieved from the storage pool archive and
saved on the Netezza system. For complete descriptions of the Tivoli Storage
Manager commands, arguments, and operations, see the Tivoli Storage Manager
documentation.
Session rejected
An error such as Session rejected: Unknown or incorrect ID entered is probably
a result of one of the following problems:
v The IBM Netezza host is not correctly registered on the Tivoli Storage Manager
server.
v The dsm.sys file on the Netezza host is not correct.
Confirm the information in both configurations and try the operation again.

Not enough database space
The error The server does not have enough database space to continue the
current operation usually occurs when the server runs out of database space. You
can correct this problem (or avoid it in the first place) by adding more database
volume or creating a space trigger as described in “Special considerations for large
databases” on page 13-54.
Connector initialization failed

An error can occur during connector initialization because of any of the following
reasons:
v Options file '*' cannot be found
This error indicates that the dsm.opt file was not found at the default location.
To resolve this problem, verify that the file exists at the specified location.
v An invalid option was found during option parsing
This error can occur if you misspell one or more options in the configuration
files dsm.opt, dsm.sys, or both. Review the options that are specified in the
configuration files and correct any errors.
v Unable to open message text file
This error can occur if one or more files are missing, particularly the
dsmclientV3.cat file in the /opt/tivoli/tsm/client/lang/en_US directory.
Reinstall the IBM Spectrum Protect (formerly Tivoli Storage Manager) API and
BA client kits on the Netezza host system to resolve this problem.
v Access to the specified file or directory is denied
This error typically occurs when the log file dsierror.log is not writable by the
user who started the nzbackup or nzrestore operation. Check the permissions on
the file and on the directory where it resides (the backupsvr/restoresvr log
directory).
EMC NetWorker connector

This section describes how to back up and restore data on an IBM Netezza system
by using the EMC NetWorker connector for the Netezza appliance.
The Netezza solution has been tested with EMC NetWorker version 7.6 and 8.2.1.
The NetWorker environment includes:

v A NetWorker server
v One or more storage nodes
v One or more client machines (Netezza hosts). For Netezza non-HA systems such
as the IBM Netezza 100, there is one client. For an HA system, there are three
clients: one for each HA host name and one client that represents the common
name of the Netezza system.
You install the 32-bit or 64-bit NetWorker Client for Linux software on the Netezza
host. The Netezza components communicate with the NetWorker client software to
perform backup and restore operations.
The primary interface for administering the NetWorker server is the NetWorker
Management Console (NMC), a browser-based GUI.

with your NetWorker administrator to confirm that it is configured to support
your expected maximum stream count. For more information, see “Parallelism
settings” on page 13-63.
Related concepts:
Preparing your system for EMC NetWorker integration

About this task
To prepare an IBM Netezza system for integration, complete the following steps.
Procedure
1. Log in to your Netezza system as the nz user.
2. Obtain the following name information about your Netezza system:
Restriction: Do not proceed without the name information.

external DNS name.
NetWorker installation
Complete instructions for installing the NetWorker Connector client on the IBM
Netezza host are included in the EMC NetWorker Release Installation Guide. The
section “Linux Installation” provides details about installing the NetWorker client
on the Netezza host, which runs a Red Hat operating system. If your Netezza
system is an HA system, install the software on both hosts.
Before you install the NetWorker client, ensure that the NetWorker server
components are installed and configured.
NetWorker configuration
The following topics describe the basic steps that are involved in configuring
NetWorker server and client software for IBM Netezza hosts. In addition to these
steps, ensure that appropriate storage devices and media pools are configured.
NetWorker server configuration

The console package provides a NetWorker Management Console (NMC), which is
a browser-based GUI that can be used to manage NetWorker servers. The
following procedures describe in general how to use the UIs. The commands and

menus can change with updates or patches to the backup software; these
procedures are intended as a general overview.
Adding the Netezza host NetWorker client:

About this task
To add the IBM Netezza host NetWorker client to the NetWorker server, complete
the following steps.
Procedure
1. Open a browser and log in to the NMC.
2. Click the Enterprise icon.
3. Choose the applicable server from the list of servers in the left pane.
4. Start the NetWorker Managed Application from the right pane.
5. Click the Configuration icon from the new window.
6. Right click Clients from the left pane and select New from the menu.
7. In Create Client window, type the name of the Netezza host (such as,
hostname.company.com) in the Name text box.
8. Select an appropriate browse and retention policy for the client.
9. Confirm that the Scheduled backup check box is checked. You will provide
further information about scheduled backups later in the configuration.
10. Check the groups to which you are adding the client. You will be creating
more groups later in the configuration.
11. From the Globals (1 of 2) tab, set appropriate value for the Parallelism field.
This parameter controls how many streams the NetWorker client can
simultaneously send in one or more backup operations. For help about
selecting values for this setting, see “Parallelism settings.”
12. Under the Globals (2 of 2) tab, add an entry of form user@client in the
Remote access list for any other client that is allowed to restore backups that
are created by this client.
For example, to allow a backup that is created on Netezza host1
(Netezza-HA-1.netezza.com) to be restored on Netezza host2
(Netezza-HA-2.netezza.com), ensure that the entry nz@Netezza-HA-
2.netezza.com is present in the Remote access list of Netezza host1
(Netezza-HA-1.netezza.com).
13. Click OK to create the Netezza host NetWorker client.
14. If you have a Netezza HA system, also define Netezza host2
(Netezza-HA-2.netezza.com) as a client, and also allow the backups to be
restored on Netezza host1 (Netezza-HA-1.netezza.com). Return to 6 and repeat
the instructions to add host2 as a client and ensure that the entry
nz@Netezza-HA-1.netezza.com is present in the Remote access list of Netezza
host2 (Netezza-HA-2.netezza.com).
Additionally, if you have more than one Netezza system, you might want to
add your other Netezza systems as clients.
Parallelism settings:
Performance might be tuned in the NetWorker environment, depending on the
client/server configurations and usage. Parallelism settings on the client and server
might be set to optimize backup performance (they do not affect restore/recovery
performance).

To affect parallelism, adjust the settings of the server and client parallelism
parameters:
v Server parallelism
Configuration > Server_Name > File > Properties > Parallelism
This parameter controls how many total streams from all its clients a NetWorker
server allows to be simultaneously active for the purposes of backup.
v Client parallelism
Configuration > Server_Name > Clients > Client_Name > File > Properties >
Globals (1 of 2) > Parallelism
This parameter controls how many streams a NetWorker client can
simultaneously send in one or more backup operations. The setting for each
client is set individually and might vary according to the particular environment
of the client.
v Media Pool parallelism
Media > Media Pools > Media_Pool_Name > File > Properties > Configuration
> Max parallelism
This parameter controls how many total streams that are writing to a media pool
can be simultaneously active for the purposes of backup.
NetWorker client configuration

By default, a client can access services that are provided by any NetWorker server
physically accessible to the client. To restrict the servers that a client can access,
you must create a file that contains the list of servers a particular client is allowed
to access on the client. For more information, see the NetWorker Administration
Guide.
NetWorker backup and restore

The are two methods available to use nzbackup, command line and scheduled
backup.
Whether you use the command line or a template file for scheduled backups,
NetWorker requires NSR_SERVER as a mandatory argument. Specify this argument
either as a part of -connectorArgs in the nzbackup command or as an environment
variable. In instances where both are specified, the command-line argument takes
precedence over the environment variable for NSR_SERVER. When you use the
NSR_SERVER environment variable, always include the name of the NetWorker
server.
There are also optional arguments which the NetWorker Connector supports:
v NSR_DATA_VOLUME_POOL
v NSR_DEBUG_LEVEL
v NSR_DEBUG_FILE
Command-line backup and restore

After the IBM Netezza host is properly configured for backup and restores with
NetWorker, you can run nzbackup and nzrestore at any time from the Netezza
host.
For example, if a NetWorker Server is named "server_name.company.com," the

database is named “test”. The following is a sample command line for backup by
using the NetWorker connector.
/nz/kit/bin/nzbackup -db test -connector networker -connectorArgs
"NSR_SERVER=server_name.company.com"

The following is an example of a restore command:
/nz/kit/bin/nzrestore -db test -connector networker -connectorArgs
"NSR_SERVER=server_name.company.com"
Scheduled backups
This section provides the steps necessary to create and configure backup groups
that are needed to schedule backups. The NetWorker server runs the nzbackup
command automatically after it creates the following objects:
v At least one backup group
v At least one backup command file
v A schedule
A separate command file and associated backup group is required for each
scheduled backup operation. The data from the backup operations that are run by
using one specific command file form a backup group. For example, if you have
two databases, DBX and DBY, and you want to schedule weekly full backups plus
nightly differential backups for each, you must create four command files, one for
each of four backup groups.
Adding a backup group:

About this task
You must add a backup group, specifically associated with each nzbackup
operation, to the list of groups in the NMC. To add a backup group to a given
server, complete the following steps.
Procedure
1. Open a browser and log into the NMC.
5. On the Configuration page, right click Groups from the left pane and select
New from the menu.
6. Type a name for the new group (such as nz_db1_daily) in the Name text box.
You can also enter text in the Comment text box.
7. To enable automatic scheduled backups for the group, supply the values for
Start time and Autostart.
8. Click OK to create the group.
Command file:
For each nzbackup operation, you must create a specific command file that contains
the backup command instructions. Logged in as the root user, create the command
files under the directory /nsr/res, and name each file [backup_group].res by
using any text editor. Include content like that in the following example. Content
varies depending on backup operation instructions:
type: savepnpc;
precmd: "/nz/kit/bin/nzbackup -u <userid> -pw <password> -db <name_
of_database_to_backup> -connector networker -connectorArgs NSR
_SERVER=server_name.company.com -v”;
pstcmd: "echo bye", "/bin/sleep 5";
timeout: "12:00:00";
abort precmd with group: No;
The entire precmd entry, up to the semi-colon, must be on a single line.

Enabling scheduled backups:
About this task
To enable scheduled IBM Netezza backup operations for a Netezza host, complete
the following steps.
Procedure
1. Open a browser and log in to the NMC.
5. From the Configuration page, select Clients in the left pane, which populates
the right pane with a list of clients.
6. Right-click the applicable client and select Properties from the menu.
7. Ensure that the Scheduled backup check box is checked.
8. In the Group section, ensure that only the group for this backup operation is
checked (such as nz_db1_daily).
9. Select the schedule from the Schedule list.
10. On the Apps and Modules tab, type savepnpc in the Backup command text
box.
11. Click OK to create the scheduled backup.
Redirect an nzrestore:
To redirect restore operations from one IBM Netezza host to another (that is to
restore a backup set that is created by one Netezza host to a different Netezza
host), you must configure Remote access as described in step 12 on page 13-63 of
“Adding the Netezza host NetWorker client” on page 13-63. By default, NetWorker
server does not allow a client access to objects created by other clients.
To restore a backup set onto host2 that was created on host1, log in to host2 and
/nz/kit/bin/nzrestore -db database -npshost host1 -connector networker
The database value is the name of the database that was backed up from the
Netezza host host1.
Host backup and restore

To perform a backup and restore of the IBM Netezza host metadata by using the
NetWorker connector, you can create scripts for the Netezza host, which run a host
backup and send the backup to the NetWorker server, and scripts that retrieve and
restore a backup. The nzhostbackup and nzhostrestore commands do not directly
support the NetWorker connector.
For example, the following sample script uses the nzhostbackup command to create
a host backup in the specified /tmp archive and then sends the backup to the
NetWorker server:
#!/bin/bash
#
# nzhostbackup_nw - back up the host catalog and send it to NetWorker server
(
nzhostbackup "${archive}"
echo

echo "Sending host backup archive ’${archive}’ to NetWorker server ..."
save -s $NSR_SERVER "${archive}"
)
exit 0
You can also create a script to retrieve and reload a host backup from the
NetWorker server:
#!/bin/bash
#
# nzrestore_tsm - restore host backup from TSM using nzhostbackup_tsm
(
echo "Restoring the specified backupset ’${archive}’ from NetWorker Server ..."
recover -a -s $NSR_SERVER "${archive}"
echo "Performing Host restore"
nzhostrestore "${archive}"
)
exit 0
NetWorker troubleshooting
This section contains troubleshooting tips to solve common problems.
For other help, see the troubleshooting section of the NetWorker Administration
Guide and the NetWorker Error Message Guide.
Basic connectivity
For problems with basic connectivity, first check that the server and client are
correctly set up and configured. Also, confirm that the clocks on both the server
and client are synchronized to within a few seconds.
Use the save and recover NetWorker commands to back up and restore a normal
file. If either command fails, the basic configuration is incorrect.
Connector initialization errors
If you get the following error, verify that the correct host name or IP value is
specified in NSR SERVER and that the NetWorker service is running on the
specified host.
nwbsa is retryable error: received a retryable network error (Severity 4
Number 12): Remote system error or nwbsa set option: an entry in the environment
structure is invalid (NSR SERVER=[server]) during connector initialization
If you get the following error, the client might not be added to the server or might
not be correctly configured on the server.
nwbsa is retryable error: received a network error (Severity 5 Number 13):
client '[client]' is not properly configured on the NetWorker Server

Chapter 14. History data collection
A Netezza system can be configured to capture information about user activity
such as queries, query plans, table access, column access, session creation, and
failed authentication requests. This information is called history data. Database
administrators can use history data to gain insight to usage patterns.
History data helps you to answer such questions as:

v What are the longest and shortest running queries on the system?
v Which queries were submitted by specific users or user groups?
v What are typical or the most common types of queries (selects, inserts, deletes,
drops, truncates)?
v What are the most or least frequently accessed tables or columns?
v Which queries were in progress at the time of or just before a system event such
as an SPU reset or a DBOS restart?
The system saves history data in a history database. You can create any number of
history databases, but only one history databases can be written to at a time.
Note: All dates and times stored in a history database use the GMT timezone.
What type of data is to be collected, which user account is to be used for data
collection, how often the collected data is to be loaded to the database, and other
criteria are specified by a history configuration. Only one history configuration is
active at a time.
Related concepts:
“Query status and history” on page 12-30
You can use the system views, _v_qrystat and _v_qryhist, to view the status of
queries that are running and the recent query history.
Types of history databases

A history database can be of either of two types.
Query A query database collects and stores the data that is most commonly
needed to monitor and report on the query activity of a system.
Audit An audit database collects the same data as a query database, but stores
the data in row-secured tables and digitally signs the data to prevent it
from being changed.
An audit database is more secure than a query database, but this improved
security comes at a cost:
v With an audit database, queries on the history tables are subjected to row-level
security checks. This decreases performance compared to a query database.
v Because an audit database uses row-secure tables, you must configure
multi-level security. A query database does not use row-secure tables and so
does not require multi-level security.
v If an audit database is used and the history data staging area exceeds its
STORAGELIMIT value, the system stops, and the administrator must free up

space and restart the system before users can resume activity. If a query
database is used and the history data staging area exceeds its STORAGELIMIT
value, the system continues to run.
Therefore, if you do not require the enhanced security or other features provided
by an audit database, use a query database. For more information about how to
configure an audit database and multi-level security, see the IBM Netezza Advanced
Security Administrator's Guide.
History database versions

Sometimes a new version or release of Netezza introduces a new version of the
history database to reflect changes to database schemas.
History Available
database since
version release Changes
1 4.6 None. This is the original version.
2 7.0.3 Several of the history tables and views were updated to include
schema information and a timezone offset. For history tables and
views that use the GMT timezone, the tzoffset field was added
to record the timezone offset, in minutes, for the source system
relative to GMT. For example, Eastern Daylight Time (EDT) is
four hours earlier than GMT, so the timezone offset is +240
minutes.
3 7.1 Several of the history tables and views were updated to include
fields to record client information:
User ID
The user ID under which the client is running.
Application name
The name of the client.
Workstation name
The host name of the workstation on which the client
runs.
Accounting string
The value of the accounting string from the client
information that is specified for the session.
If you upgrade to a new release, you can continue to use an earlier version of the
history database, or you can create a new version of the history database to take
advantage of the new fields and records.
History-data staging and loading processes

There are separate processes for history-data staging and loading.
History data is collected continually in a staging area. It is loaded from the staging
area into the history database at intervals determined by settings of the active
history configuration.
History-data staging
After you enable history-data collection, the Netezza system starts the
history-data collection process (alcapp). This process captures history-data
and saves it in a staging area, which is in the $NZ_DATA/hist/staging

directory. This directory can have one or more subdirectories with names
of the form alc_$TIMESEQUENCE. Each of these subdirectories contains:
v One or more history-data files, each of which contains captured history
data and is saved as an external table in text format
v One CONFIG-INFO file that identifies which history configuration was
active when the history-data files were created
History-data loading
The load settings specified in the history configuration determine when the
history-data files in the staging area are transferred to the loading area.
From the loading area, the history-data loader process (alcloader) loads the
external tables into the history database. The current history configuration
specifies the loading frequency, the target history database, and the user
account to access that database.
The loading area is in the $NZ_DATA/hist/loading directory. This directory
can have one or more subdirectories with names of the form
alc_$TIMESEQUENCE. Each of these subdirectories contains the history-data
files that are to be loaded.
After the history-data files are successfully loaded, the system deletes them
to free disk space.
Error handling
An error might occur that prevents history-data files from being loaded.
For example:
v Someone might deactivate and drop the active history configuration
before the corresponding history-data files are loaded.
v The user password specified in the history configuration and used to
access the history database might have changed.
v The history database might be dropped or locked.
If the history-data files cannot be loaded, the loader moves the history-data
files to the $NZ_DATA/hist/error directory. The nzvacuumcat process
checks the files in the error directory and deletes any files that are older
than 72 hours. To retry to load any files that were moved to the error
directory:
1. Resolve the problem that caused the load attempt to fail.
2. Move the directories in $NZ_DATA/hist/error to $NZ_DATA/hist/loading.
3. Issue the nzstop and nzstart commands to stop and restart the system.
History-data files
Each history-data directory (that is, the staging, loading, or error directory)
contains zero or more batch directories. Each batch directory typically contains a
set (or batch) comprising the following files:
v One file with the name CONFIG-INFO, which is a text file that contains the name
of the history configuration that was active when the history data was collected.
v Several files with names of the form alc_id_$TIMESEQUENCE, where id is a
two-letter code that indicates the type of history data in the file:
co Column access data.
fa Failed authentication data.
le Log entry data.
pe Plan epilog data.
pp Plan prolog data.
qe Query epilog data.
Chapter 14. History data collection 14-3

qo Query overflow data.
qp Query prolog data.
se Session epilog data.
sp Session prolog data.
tb Table access data.
History log files

The system creates log files in which it records the error and informational
messages that are issued during the operation of the history-data collection and
history-data loader processes.
These log files are stored in the following directories:

/nz/kit/log/alcapp
This directory contains log files for the history-data collection process
(alcapp). Each log file records such events as the starting and stopping of
the alcapp process, the transfer of batch files from the staging to loading
directory, and the cleanup of existing captured data in the staging area
after the process restarts.
/nz/kit/log/alcloader
This directory contains log files for the history-data loader process
(alcloader). Each log file records such events as the starting and exiting of
the alcloader process, schema check verifications, and the loading of batch
files from the loading area.
History event notifications

There are two event notifications that alert you to issues with history monitoring:
histCaptureEvent
This event is triggered when there is a problem that prevents the current
history collection from writing files to the staging area.
histLoadEvent
This event is triggered when there is a problem loading the history files in
the staging area to the target history database.
Related reference:
“History-data events” on page 8-30
Setting up the system to collect history data

The system does not automatically collect history data, but must be configured to
do so:
1. Plan for the history data needs of your organization.
2. Create a history database to hold the data.
3. Create history configurations.
4. Give the users who are to use the history data access to the history database.
Planning for history-data collection

Consider the needs of your organization, such as which users require access to
history data, and the types of questions they will have.
Before you begin to configure your system to collect history data:

1. Decide which version of history database to use. Use the most recent version
possible. Use an older version only if both:

v You already have a database at that level and want to continue to use it.
v You do not need to use the new data fields provided by newer versions.
2. Decide which type of history database (query or audit) to use.
3. Decide which user is to be the owner of the history database.
4. Decide which user account is to be used to load history data into the history
database.
This information will be required later when you create history databases and
history configurations.
Creating a history database

You can create any number of history databases, but the system can write to only
one at a time.
To create a history database, issue the nzhistcreatedb command as described in

“The nzhistcreatedb command” on page A-21. This command can take several
minutes to complete, depending on how busy the IBM Netezza system is.
For example, the following command creates a history database with the name
histdb:
[nz@nzhost ~]$ nzhistcreatedb -d histdb -t query -v 1 -u jones
-o smith -p password123
This operation may take a few minutes. Please wait...
Creating tables .................done
Creating views .......done
Granting privileges ....done
History database histdb created successfully !
Related reference:
“The nzhistcreatedb command” on page A-21
Use this command to create a history database including all the tables, views, and
other objects needed to collect history data.
Creating history configurations

A history configuration specifies such things as whether history-data collection is
enabled, the name of the history database, the user account that is to be used to
access it, and how frequently to load captured data. Only one history configuration
is active at a time.
History data always includes information about:

v Login failures
v Session creation
v Session termination
v The startup of the history-data collection process.
The history configuration specifies whether the system is also to collect one or
more of the following types of data:
query data
Information about general query parameters such as data about log entries
for the operations that run on the system, session creations, failed
authentications, session completions, user queries, and query status.
plan data
Information about the query plans for the system. This information is
obtained at the start of the plan (prolog data) and at the end of the plan

execution (epilog data). This information provides insight into plan
priority, start and finish times, snippet counts, completed snippet counts,
and result data sizes.
table data
Information about table access attempts such as the table being accessed
and the type of operation being run against the table (create, insert, select,
drop, delete, update, or lock).
column data
Information about column access attempts such as the column being
accessed and the type of operation being run against the column (select,
set, where, group by, having, order by, or alter).
service data
CLI commands such as nzbackup, nzrestore, and nzstate.
state data
The state (ONLINE, PAUSED, OFFLINE, STOPPED) of the system.
You can define several history configurations, each of which collects a different set
of history data. For example, you might have a different configuration to collect
each of the following types of information:
v All possible history data. You might record this level of information when you
introduce a new application or a new group of users, or when troubleshooting
service issues.
v Basic history information that you use during routine operational periods.
v Detailed information about a specific area, such as table access. You can use this
information to identify tables that might be unused and are candidates for
cleanup.
To create a history configuration, either:

v Issue the CREATE HISTORY CONFIGURATION command, as described in the
v Use the NzAdmin tool (see “Managing history configurations by using
NzAdmin” on page 14-13).
To create, show, and manage history configurations, your user account must have
the Manage Security privilege. The specified history database must already be
created on the system.
For example, the following command creates a history configuration named

hist_plancol:
SYSTEM.ADMIN(ADMIN)=> CREATE HISTORY CONFIGURATION hist_plancol HISTTYPE QUERY
DATABASE histdb USER loaduser PASSWORD ’loaduserpw’ COLLECT PLAN,COLUMN
LOADINTERVAL 5 LOADMINTHRESHOLD 4 LOADMAXTHRESHOLD 20 STORAGELIMIT 25
LOADRETRY 1 VERSION 3;
The configuration name, user name, and database name are identifiers and can be
enclosed in double quotation marks. For example: "sample configuration",
"sample user", and "sample qhist db" are all valid names.
Important: The following history configuration settings must match the

corresponding settings for the history database; otherwise, the loader process fails:

Parameter in the history Parameter in the
Setting configuration nzhistcreatedb command
History database type HISTTYPE (if either QUERY -t or --db-type
or AUDIT)
Load user USER -u or --user
Version number VERSION -v or --schema
For each history database, create at least one history configuration that specifies
the parameter HISTTYPE NONE. Setting this configuration to be the active
configuration disables the collection of history data and automatically sets the
following default values:
v CONFIG_LEVEL to HIST_LEVEL_NONE
v CONFIG_TARGETTYPE to HIST_TARGET_LOCAL
v CONFIG_COLLECTFILTER to COLLECT_ALL
For example, the following command creates a history configuration named
hist_disabled that can be used to disable history collection:
SYSTEM.ADMIN(ADMIN)=> CREATE HISTORY CONFIGURATION hist_disabled HISTTYPE
NONE;
Configuring the loading of history data

Each history configuration specifies when the loading process is to load history
data from the staging area into the database. You can specify thresholds that are
based on time intervals, the amount of data in the staging area, or both. Each
history configuration also specifies a maximum size for the staging area.
The following history configuration settings determine when the loading process
loads history data from the staging area into the database:
LOADINTERVAL
A loading timer that can range from 1 - 60 minutes. Specify 0 to disable the
timer. When the load interval timer expires, the system checks for captured
data in the staging area. Based on the values of the staging size threshold
values, LOADMINTHRESHOLD and LOADMAXTHRESHOLD, and
whether the loader is idle, the data in the staging area might or might not
be transferred to the loader.
LOADMINTHRESHOLD
The minimum amount of history data, in megabytes, to collect before it
transfers the batch to the loading area. Specify 0 to disable the minimum
threshold check.
LOADMAXTHRESHOLD
The maximum amount of history data to collect in the staging area before
it is automatically transferred to the loading area. Specify 0 to disable the
maximum threshold check.
These settings, called loader settings, can have zero or non-zero values, but at least
one setting must be non-zero. The following table describes the valid value
combinations:

Table 14-1. History loading settings
Load Min Max Loader
interval threshold threshold state Operation
0 0 Non-zero Idle Transfer the captured data in the staging area to the loading
area, regardless of the staging size.
This combination is typically used for test/demonstration

environments. Because of the continuous loading of data, this
setting can cause a performance impact on IBM Netezza systems.
Busy When the captured data in the staging area meets or exceeds the
max threshold, transfer it to the loading area.
0 Non-zero 0 Idle When the captured data in the staging area meets or exceeds the
min threshold, transfer it to the loading area.
Busy Continue collecting data in the staging area until the loader is
idle, then transfer the data to the loading area.
0 Non-zero Non-zero Idle When the captured data in the staging area meets or exceeds the
min threshold, transfer it to the loading area.
Busy Continue collecting data in the staging area until the max
threshold is reached or until the loader is idle, then transfer the
data to the loading area.
Non-zero 0 0 N/A Transfer any captured data in the staging area to the loading
area when the timer expires, regardless of amount of data or
loader state.
Non-zero 0 Non-zero N/A Transfer captured data in the staging area to the loader when the
timer expires, or when the data meets or exceeds the max
threshold.
Non-zero Non-zero 0 N/A When the timer expires, transfer the captured data in the staging
area to the loading area if it meets or exceeds the min threshold.
Non-zero Non-zero Non-zero Idle When the timer expires, transfer the captured data in the staging
area to the loading area if it meets or exceeds the min threshold
or the max threshold.
Use this combination for a production Netezza system. You can

“tune” the values of the three loading settings for your
environment as described in the text that follows this table.
Busy If the staging area meets or exceeds the max threshold, transfer
the captured data in the staging area to the loading area.
Otherwise, continue collecting data until the next timer
expiration.
Choose loader settings that balance the need for current history data with the need
avoid unduly affecting the system. History data that is still in the staging area is
stored in external text files. If necessary, users can review those files to obtain
information about recent activity before that information is loaded into the history
database.
Depending on the loader settings, how much history data is collected, and the
overall utilization of the system, the alcloader process might become busy loading
history data. If there are several batch directories in the loading area, this might
indicate queued and waiting load requests. You can experiment with different
loader settings to tune it for optimal operation.

To ensure that the staging area does not grow indefinitely, use the STORAGELIMIT
parameter to set its maximum size, in MB. If the staging area reaches or exceeds
this size limit, the system stops collecting history data. An administrator must free
up disk space in the storage area to free up disk space so that history collection
can resume. This is usually done by adjusting the loader settings, The
STORAGELIMIT value must be greater than the LOADMAXTHRESHOLD value.
Managing access to a history database

As with any user database, database access permissions determine who can access
a history database. By default, the following users have access to a history
database:
v The admin user
v The database owner
v The load user
The database owner and load user are specified in the corresponding
nzhistcreatedb command.
The password for the load user is specified in a CREATE HISTORY

CONFIGURATION or ALTER HISTORY CONFIGURATION command. If this
password changes, you must update the history configuration with the new
password or the loader process will fail.
Users who run reports against the history data require List and Select privileges
for the history database. Users who create their own tables and views also require
Create Table or Create View privileges.
If you have several users who require access, consider creating a user group to
manage the necessary privileges.
Important notes for Kerberos environments
CAUTION:
If your NPS system uses Kerberos authentication for database user accounts,
note that you could encounter problems with loading query or audit history. The
load user account must be active and authenticated with a valid Kerberos ticket
for the loads to run. Kerberos tickets typically expire daily, and the history loads
will fail if the load user's ticket is expired. As a possible workaround, you could
create a scheduled job (such as a cron job) to automatically renew the ticket for
the load user each day to keep an active ticket in place on the system.
Related concepts:
Chapter 11, “Security and access control,” on page 11-1
performance.
Managing the collection of history data

You can manage many aspects of history-data collection.
Changing the owner of a history database

Each database has an owner. To change the owner of a history database, alter both
the database and the history configuration to reflect the new ownership.

About this task
To change the ownership of a history database:
Procedure
2. If the new owner does not already have a user account, create one. For
example:
nzsql -c "create user sam with password ’sk3nk’"
3. Grant the List permission to the new owner for the history database. For
example:
nzsql -c "grant list on histdb1 to sam"
4. If you are changing the owner of the database referred to by the active history
configuration:
a. Switch to a different history configuration that disables history-data
collection or that specifies a different history database. For example:
nzsql -c "Set history configuration histdb1_off"
b. Activate the newly set history configuration by stopping and restarting the
system, that is, by issuing the nzstop and nzstart commands.
5. Change the owner of the history database. For example:
nzsql c "alter database histdb1 owner to sam"
6. In each of the non-active history configurations for the database, change the
database owner and password. For example:
nzsql -c "alter history configuration histdb1_plan user sam password ’sk3nk’"
nzsql -c "alter history configuration histdb1_col user sam password ’sk3nk’"
7. To activate a changed history configuration:
a. Set the changed history configuration to be the active configuration. For
example:
nzsql -c "set history configuration histdb1_plan"
b. Activate the changed history configuration by stopping and restarting the
Dropping a history database

As with any user database, you can drop a history database to remove it from
your system. When you drop the database, all of its tables and views and all of the
collected history information it contains are also dropped.
To drop a history database:

1. Issue the SHOW HISTORY CONFIGURATION command to ensure that the
active history configuration does not load data to the database that is to be
dropped. If you drop the active history database, subsequent operations that
attempt to load data to that database will fail.
2. Log in to the system database as a user who has the Drop privilege for the
database that is to be dropped.
3. Issue a DROP DATABASE command, as described in the IBM Netezza Database
User’s Guide. For example:
SYSTEM.ADMIN(ADMIN)=> DROP DATABASE qhist1;

Starting the collection of history data
To start the collection of history data, issue the SET HISTORY CONFIGURATION
command to change to a history configuration that collects data.
To start the collection of history data:

1. Issue the SET HISTORY CONFIGURATION command for a history
configuration that specifies the value QUERY or AUDIT for its HISTTYPE
parameter, as described in “Creating history configurations” on page 14-5
2. Activate the new history configuration by stopping and restarting the system,
that is, by issuing the nzstop and nzstart commands.
For example:
SYSTEM.ADMIN(ADMIN)=> SET HISTORY CONFIGURATION hist2_on;
SYSTEM.ADMIN(ADMIN)=> \q
nzstop
nzstart
Stopping the collection of history data

To stop the collection of history data, issue the SET HISTORY CONFIGURATION
command to activate a history configuration that does not collect history data.
To stop the collection of history data:

1. If you have not already done so, create a history configuration that specifies the
value NONE for its HISTTYPE parameter, as described in “Creating history
configurations” on page 14-5.
2. Issue the SET HISTORY CONFIGURATION command for the new history
configuration.
3. Activate the new history configuration by stopping and restarting the system,
that is, by issuing the nzstop and nzstart commands.
For example:
SYSTEM.ADMIN(ADMIN)=> SET HISTORY CONFIGURATION hist2_off;
SYSTEM.ADMIN(ADMIN)=> \q
nzstop
nzstart
Changing history configuration settings

Issue the ALTER HISTORY CONFIGURATION command to change the settings for
a history configuration.
The ALTER HISTORY CONFIGURATION command, as described in the IBM

Restriction: You cannot change the settings for the active configuration. For
example, if the active configuration is histdb1_plan:
1. Switch to a different history configuration. For example:
nzsql -c "set history configuration histdb1_col"
2. Activate the new history configuration (histdb1_col) by stopping and restarting
the system, that is, by issuing the nzstop and nzstart commands.
3. Change the settings for the formerly active history configuration (histdb1_plan)
using the ALTER HISTORY CONFIGURATION command.
4. Set the changed history configuration to be the active configuration again. For
example:
nzsql -c "set history configuration histdb1_plan"

5. Reactivate the changed history configuration by stopping and restarting the
Displaying history configuration settings

Issue the SHOW HISTORY CONFIGURATION command to display information
about the active configurations or about all configurations.
The SHOW HISTORY CONFIGURATION command is described in the IBM

Netezza Database User’s Guide. For example, the following command shows
information about the current configuration:
SYSTEM.ADMIN(ADMIN)=> SHOW HISTORY CONFIGURATION;
CONFIG_NAME | CONFIG_NAME_DELIMITED | CONFIG_DBNAME | CONFIG_DBNAME_DELIMITED | CONFIG_DBTYPE |

CONFIG_TARGETTYPE | CONFIG_LEVEL | CONFIG_HOSTNAME | CONFIG_USER | CONFIG_USER_DELIMITED |
CONFIG_PASSWORD | CONFIG_LOADINTERVAL | CONFIG_LOADMINTHRESHOLD| CONFIG_LOADMAXTHRESHOLD |
CONFIG_DISKFULLTHRESHOLD | CONFIG_STORAGELIMIT | CONFIG_LOADRETRY | CONFIG_ENABLEHIST |
CONFIG_ENABLESYSTEM | CONFIG_NEXT | CONFIG_CURRENT | CONFIG_VERSION
-------------+-----------------------+---------------+-------------------------+---------------
+-------------------+--------------+-----------------+-------------+-----------------------+---
--------------+---------------------+-------------------------+-------------------------+------
--------------------+---------------------+------------------+-------------------+-------------
--------+-------------+----------------+----------------
DISABLEQHIST | f | | f | 3
| 1 | 1 | localhost | | f |
| -1 | -1 | -1 |
-1 | -1 | -1 | f | f
| f | f | 1
(1 row)
Dropping history configurations

You can use the DROP HISTORY CONFIGURATION command to remove a
history configuration. You can drop a configuration that is not active.
About this task
The following sample command drops the basic_hist history configuration:

SYSTEM.ADMIN(ADMIN)=> DROP HISTORY CONFIGURATION basic_hist;
If you want to drop the active configuration, you must first set to a new
configuration and restart the IBM Netezza software, then you can drop the
non-active configuration. As a best practice, you should not drop the configuration
until the loader has finished loading any captured data for that configuration.
To verify whether there are any batches of history data for the configuration that
you want to drop, complete the following steps.
Procedure
1. Open a shell window to the Netezza system and log in as the admin user.
2. Change to the /nz/data/hist directory.
3. Use a command such as grep to search for CONFIG-INFO files that contain the
name of the configuration that you want to drop. For example:
grep -R -i basic .

4. Review the output of the grep command to look for messages similar to the
following messages:
./loading/alc_20080926_162803.964347/CONFIG-INFO:BASIC_HIST
./staging/alc_20080926_162942.198443/CONFIG-INFO:BASIC_HIST
Results
These messages indicate that there are batches in the loading and staging areas
that use the BASIC_HIST configuration. If you drop that configuration before the
batch files are loaded, the loader classifies them as errors when it attempts to
process them later. If you want to ensure that any captured data for the
configuration is loaded, do not drop the configuration until after the command in
step 3 on page 14-12 returns no output messages for the configuration that you
want to drop.
For details about the command, see the DROP HISTORY CONFIGURATION
command syntax in the IBM Netezza Database User’s Guide.
Managing history configurations by using NzAdmin

Database users who have the Manage Security privilege can use the NzAdmin tool
to create, alter, and set history configurations for an existing history database.
To access the Query History Configuration dialog, select Tools > Query History
Configuration in the menu bar. The Configuration Name list lists all history
configurations:
v To display the settings for a configuration, select the configuration from the list.
v To change which configuration is the current (active) configuration, select a
configuration and click Set as Current. This change will not take effect until you
restart the Netezza system.
v To create a new history configuration, enter a new configuration name and
supply the information for the required fields. These fields correspond to the
parameters described in the CREATE HISTORY CONFIGURATION command.
v To edit a configuration, select it and modify its settings as needed.
v To edit the current configuration, you must first select a different configuration
and set it to be the current configuration. After editing the former current
configuration, set it to be the current configuration again. Changes made in this
way will not take effect until you restart the Netezza system.
Maintaining a history database

A history database grows as it accumulates history information. Plan for routine
maintenance of the history database. Determine the amount of time that you need
to keep the history data before you can archive or delete it (for example, keep only
data for the current and previous month, or the current and previous quarter, or
for the current year only).
To dispose of outdated history data:

1. Issue the nzhistcleanupdb command and specify a date and time threshold (see
“The nzhistcleanupdb command” on page A-19). All data recorded before this
date and time is deleted. The user you specify for this command must both be
able to access the history database and must have the Delete privilege for the
history database tables.
2. To completely remove the deleted rows in the history database, issue the
nzreclaim command (see “The nzreclaim command” on page A-45).

For example:
v The following command removes from the history database with the name
histdb any history data that was collected before October 31, 2013, and
automatically grooms the history tables afterward:
[nz@nzhost ~]$ nzhistcleanupdb -d histdb -u smith -pw password
-t "2009-10-31" -g
About to DELETE all history entries older than 2013-10-31 00:00:00
(GMT) from histdb.
Proceed (yes/no)? :yes
BEGIN
DELETE 0
DELETE
. 98
.
.
DELETE 503
COMMIT
v The following command completely removes the deleted rows in the history
database:
[nz@nzhost ~]$ nzreclaim -db histdb -u smith -pw password -alltbls
-records
Related reference:
“The nzhistcreatedb command” on page A-21
History views and tables

A history database provides views that users can use to access a subset of the
history data. These views have names of the form $v_hist_* (for query history
data) or $v_sig_hist_* (for audit history data). Users can access the remaining
history data directly in the history tables. These tables have names of the form
$hist_*.
Restriction: Do not change, drop, or modify these views or tables, because doing
so can cause history-data collection to stop working.
Description View or table View for audit history data

The names of all columns, collected during $v_hist_column_access_stats
table access.
Queries that were not captured completely. $v_hist_incomplete_queries
Information about events that occurred. $v_hist_log_events
Information about completed queries. $v_hist_queries
The same information as in $v_hist_queries, $v_hist_successful_queries
but only for successful queries.
The names of all the tables that are captured in $v_hist_table_access_stats
table access
The same information as in $v_hist_queries, $v_hist_unsuccessful_queries
but only for unsuccessful queries.
The column access history for a query. $hist_column_access_n $v_sig_hist_column_access_n
The failed authentication attempts for every $hist_failed_authentication_n $v_sig_hist_failed_authentication_n
authenticated operation.
The log entries for all history operations. $hist_log_entry_n $v_sig_hist_log_entry_n
The systems that story history data in the $hist_nps_n
history database.

Description View or table View for audit history data
Plan history information collected at the end of $hist_plan_epilog_n $v_sig_hist_plan_epilog_n
the plan execution.
Plan history information collected at the $hist_plan_prolog_n $v_sig_hist_plan_prolog_n
beginning of plan execution.
Data collected at the end of the query. $hist_query_epilog_n $v_sig_hist_query_epilog_n
The remaining characters of the query string $hist_query_overflow_n $v_sig_hist_query_overflow_n
that was stored in the querytext column of the
$hist_query_prolog_n table.
Initial data collected at the start of a query. $hist_query_prolog_n $v_sig_hist_query_prolog_n
Information about CLI usage from the localhost $hist_service_n $v_sig_hist_service_n
or remote client.
Information about each session, collected $hist_session_epilog_n $v_sig_hist_session_epilog_n
during session termination.
Information about each created session. $hist_session_prolog_n $v_sig_hist_session_prolog_n
The state changes in the system. $hist_state_change_n $v_sig_hist_state_change_n
The table access history for a query. $hist_table_access_n $v_sig_hist_table_access_n
The version number and type of the history $hist_version
database.
Note:
v Views have names that begin with $v; tables have names that begin with $hist.
v The variable n represents the version number of the database.
The audit history views use row-level security to restrict access to the audit
information. Each has a name of the form $v_sig_hist_*. Each has the same
columns as its corresponding $hist_* table, but also has an additional security label
(sec_label) column that contains the security descriptor string.
The views _v_qryhist, _v_qrystat, _v_querystatus, and _v_planstatus were

provided in early Netezza releases but are now deprecated. They are provided for
compatibility, but whenever possible, use the other history data views and tables
instead.
Remember: The history user table names use delimited (quoted) identifiers. When
you query these tables, you must enclose the table name in double quotation
marks. For example:
MYDB.SCHEMA(USER)=> select * from "$hist_version";
$v_hist_column_access_stats
The $v_hist_column_access_stats view lists the names of all columns that are
captured during table access and provides some cumulative statistics.
Table 14-2. $v_hist_column_access_stats
Name Description
dbname The name of the database to which the session is connected
schemaname The schema name as specified in catalog.schema.table
tablename The table name of the table
columname The name of the column

Table 14-2. $v_hist_column_access_stats (continued)
Name Description
refs The number of times that this column was referenced
num_selected The number of times this column was referenced in the following
num_updated clauses
num_where v SELECT
num_grouped
v UPDATE
num_having
num_ordered v WHERE
num_altered v GROUP BY
num_genstats v HAVING
v ORDER BY
v ALTER
v GENERATE STATISTICS
$v_hist_incomplete_queries
The $v_hist_incomplete_queries view lists the queries that were not captured
completely. The problem might be that there was a system reset at the time of
logging or because some epilog/prolog is not loaded into the database yet.
Table 14-3. $v_hist_incomplete_queries
Name Description
npsid A unique ID for the IBM Netezza system (This value is
generated as a sequence on the target database where this view
is defined.)
npsinstanceid The instance ID of the nzstart command for the source Netezza
system
opid Operation ID, which is used as a foreign key from query epilog,
overflow and plan, table, column access tables.
logentryid This ID and the NPS ID (npsid) and instance ID (npsinstanceid)
form a foreign key into the hist_log_entry_n table.
sessionid The session ID (which is NULL for a failed authentication).
dbname The name of the database to which the session is connected.
queryid The unique checksum of the query.
query The first 8 KB of the query text.
submittime The time the query was submitted to Postgres.
client_user_id The user ID of the application that submitted the query. This
field is available only in database version 3 or later.
client_application_name The name of the application that submitted the query associated
with the plan. This value is specified for the session, and is
usually set by an application. This field is available only in
database version 3 or later.
client_workstation_name The host name of the workstation on which the application that
submitted the query associated with the plan runs. This value is
specified for the session, and is usually set by an application.
This field is available only in database version 3 or later.
client_accounting_string The value of the accounting string. This value is specified for
the session, and is usually set by an application. This field is
available only in database version 3 or later.

$v_hist_log_events
The $v_hist_log_events view shows information about the events that occurred on
the system.
Table 14-4. $v_hist_log_events
Name Description
npsid A unique ID for the IBM Netezza system. This value is generated as
a sequence on the target database where this view is.
system.
logentryid This ID and the NPS ID (npsid) and instance ID (npsinstanceid) form
a foreign key into the hist_log_entry_n table.
sessionid The session ID. This ID is NULL for a failed authentication.
time The timestamp when the operation occurred.
op The integer code and text string that describes the actual operation.
The valid values are one of the following values:
op_type v 1 = session create
v 2 = session logout
v 3 = failed authentication
v 4 = query prolog
v 5 = query epilog
v 6 = plan prolog
v 7 = plan epilog
checksum These are the checksum and query for query prolog entries,
signature, and plan information for plan prolog entries. For other log
details entries, checksum is NULL and details have other information like
status for epilogs.
dbid The OID of the database where the table is defined.
dbname The name of the database where the table is defined.
userid The user ID that ran the command.
username The user name for the user ID.
client_type The client type, such as none, nzsql, odbc, jdbc, nz(un)load, cli, bnr,
reclaim, old-loader (deprecated), or internal.
$v_hist_queries, $v_hist_successful_queries, and

$v_hist_unsuccessful_queries
The $v_hist_queries view shows information about the completed queries and their
status, runtime seconds (for total, cumulative queued, prep time and GRA time),
and number of plans. The $v_hist_successful_queries and
$v_hist_unsuccessful_queries views show the same information as $v_hist_queries,
but filters that information depending on whether each query was successful.
Table 14-5. $v_hist_queries, $v_hist_successful_queries, and $v_hist_unsuccessful_queries
Name Description
npsid A unique ID for the IBM Netezza system. This value is
generated as a sequence on the target database where this view
is defined.

Table 14-5. $v_hist_queries, $v_hist_successful_queries, and
$v_hist_unsuccessful_queries (continued)
Name Description
system.
logentryid This ID and the NPS ID (npsid) and instance ID (npsinstanceid)
form a foreign key into the hist_log_entry_n table.
sessionid The session ID. This ID is NULL for a failed authentication.
queryid The unique checksum of the query.
query The first 8 KB of the query text.
submittime The time the query was submitted to Postgres.
finishtime The time when the query execution finished and Postgres has
the results. The query could still be returning the results to the
client after this time.
runtime The total query run time (as interval and in seconds).
runtime_seconds
status The Query Completion status (as integer and text string).
verbose_status
queuetime The amount of time the query was queued (as interval and in
queued_seconds seconds).
preptime The amount of time the query spent in "prep" stage (as interval
prep_seconds and in seconds).
gratime The amount of time that the query spent in GRA (as interval
gra_seconds and in seconds).
numplans The number of plans generated.
numrestarts The cumulative number of times the plans were restarted.
client_user_id The user ID under which the application that submitted the
query. This field is available only in database version 3 or later.
client_application_name The name of the application that submitted the query associated
with the plan. This value is specified for the session, and is
usually set by an application. This field is available only in
client_workstation_name The host name of the workstation on which the application that
submitted the query associated with the plan runs. This value is
specified for the session, and is usually set by an application.
This field is available only in database version 3 or later.
client_accounting_string The value of the accounting string. This value is specified for
the session, and is usually set by an application. This field is
$v_hist_table_access_stats
The $v_hist_table_access_stats view lists the names of all the tables that are
captured during table access and provides some cumulative statistics.

Table 14-6. $v_hist_table_access_stats View
Name Description
dbname The name of the database to which the session is connected
schemaname The schema name as specified in catalog.schema.table
tablename The table name of the table
refs The number of times that this table was referenced
num_selected The number of times that this table was referenced in the following
num_inserted types of clauses:
num_deleted v SELECT
num_updated v INSERT
num_truncated v DELETE
num_dropped v UPDATE
num_created v TRUNCATE
num_genstats v DROP
num_locked v CREATE
num_altered v GENERATE STATISTICS
v LOCK
v ALTER
$hist_column_access_n
The $hist_column_access_n table records the column access history for a query.
This table becomes enabled whenever history type is Column.
Table 14-7. $hist_column_access_n
Name Type Description
npsid integer This value along with the npsInstanceId and opid
form the foreign key into the operation table.
npsinstanceid integer Instance ID of the source IBM Netezza system
opid bigint Operation ID. This ID is used as a foreign key
from query epilog, overflow and plan, table,
column access tables to query prolog.
logentryid bigint This ID and the NPS ID (npsid) and instance ID
(npsinstanceid) form:
v A foreign key into the hist_log_entry_n table
v A primary key for this table
seqid integer A plain sequence number of the entry. It starts at
zero for every npsid, npsinstanceid, and opid. It
increments monotonically for table access records
for each query.
sessionid bigint Session ID. This ID with NPS ID (npsid) and
instance ID (npsinstanceid) form the foreign key
from query, plan, table, and column access tables
into session tables.
dbid bigint OID of the database where the table is defined
dbname nvarchar(128) The name of the database where the table is
defined
schemaid bigint The OID of the schema as specified in
catalog.schema.table
schemaname nvarchar(128) The schema name as specified in

Table 14-7. $hist_column_access_n (continued)
tableid bigint The table ID of the table.
tablename nvarchar(128) The table name of the table.
columnid integer The column position as it displays in the logical
table definition, starting with 1.
columnname nvarchar(128) The name of the column.
usage integer The following bits are set to true if the column
appears in:
v (usage & 1) <> 0 = in_select
v (usage & 2) <> 0 = in_set
v (usage & 4) <> 0 = in_where
v (usage & 8) <> 0 = in_groupby
v (usage & 16) <> 0 = in_having
v (usage & 32) <> 0 = in_orderby
v (usage & 64) <> 0 = in_alter
$hist_failed_authentication_n
The $hist_failed_authentication_n table captures only the failed authentication
attempts for every operation that is authenticated. A successful authentication
results in a session creation. A failed authentication does not result in a session
creation, but it instead creates a record with a unique operation ID in this table.
Table 14-8. $hist_failed_authentication_n
npsid integer IBM Netezza ID for the source system whose
data is captured in this table.
npsinstanceid integer Instance ID of the nzstart command for the
source Netezza system.
logentryid bigint A foreign key into the hist_log_entry_n table with
the IBM Netezza ID (npsid) and instance ID
(npsinstanceid).
clientip char(16) IP address of the client that made the connection
attempt.
sessionusername nvarchar(512) The name string for the session user ID
(sessionUserId).
time timestamp The GMT timestamp that indicates when the
operation occurred.
failuretype integer One of the following codes that represent the
authentication failure type:
v 1 = failed authentication because of bad
username, password, or both
v 2 = failed authentication because of
concurrency
v 3 = failed authentication because of user access
time limits
v 4 = user account that is disabled after too
many failed password attempts
failure varchar(512) The text message for the failure type code.

Table 14-8. $hist_failed_authentication_n (continued)
tzoffset integer The timezone offset in minutes. This field is
$hist_log_entry_n
The $hist_log_entry_n table captures the log entries for the operations performed.
It shows the sequence of operations that are performed on the system. This table is
not populated if history collection is never enabled or if hist_type = NONE.
Table 14-9. $hist_log_entry_2
npsid integer Netezza ID for the source system whose data is
captured in this table
npsinstanceid integer The instance ID of the nzstart command for the
source Netezza system
logentryid bigint Sequential ID of the operation in the source
Netezza system. This ID and the NPS ID (npsid)
and instance ID (npsinstanceid) form the primary
keys for this table.
sessionid bigint The session ID. This is NULL for a failed
authentication.
op integer An operation code, which can be one of the
following codes:
v OP_SESSION_CREATE = 1
v OP_SESSION_LOGOUT = 2
v OP_FAILED_AUTH = 3
v OP_QUERY_PROLOG = 4
v OP_QUERY_EPILOG = 5
v OP_PLAN_PROLOG = 6
v OP_PLAN_EPILOG = 7
time timestamp The GMT timestamp for this operation.
$hist_nps_n
The $hist_nps_n table describes each source IBM Netezza system for which history
is captured in the target database. When a Netezza system connects to a history
database for the first time, a record is added to this table.
Table 14-10. $hist_nps_n
npsid integer A unique ID for the Netezza system, and the
primary key for this table (This value is
generated as a sequence on the target database
where this table is defined.)
uuid char(36) UUID of the Netezza system, which is a unique
ID (generated on the source Netezza system)
serverhost varchar(256) Host name of the source Netezza system
serverip char(16) IP address of the source Netezza system

Table 14-10. $hist_nps_n (continued)
npsinstanceid integer Instance ID of the source Netezza system when
this record was inserted
$hist_plan_epilog_n
The $hist_plan_epilog_n table records the plan history information. This data is
collected at the end of the plan execution. This table becomes enabled whenever
history type is Plan.
Table 14-11. $hist_plan_epilog_n
form the foreign key into the query table.
npsinstanceid integer Instance ID of the source IBM Netezza system.
opid bigint Operation ID. Used as a foreign key from query
epilog, overflow and plan, table, column access
tables to query prolog.
logentryid bigint This ID is a foreign key into the hist_log_entry_n
table with the npsid and npsinstanceid. This ID
with npsid and npsinstanceid is also a primary
key for this table.
sessionid bigint Session ID. This ID with npsid and npsinstanceid
is the foreign key from query, plan, table, and
column access tables into session tables.
planid integer The plan ID (used to make an equi join in
addition to npsid, npsinstanceid, and opid to
match a plan prolog to a plan epilog record).
endtime timestamp The ending time of the plan execution.
donesnippets integer The number of snippets that are done.
resultrows bigint The number of rows affected by the SQL query.
This field shows the row count for SELECT,
INSERT, UPDATE, DELETE, and CTAS queries
on user tables, and SELECT, INSERT, UPDATE,
and DELETE queries on system tables or bridge
queries. For all other queries, the value is 0.
resultbytes bigint The number of result bytes.
status integer A status for the success or failure of the plan. The
value is 0 for a successful completion, or a
non-zero error code for a failure.
$hist_plan_prolog_n
The $hist_plan_prolog_n table records the plan history information. This data is
collected at the beginning of the plan execution. This table becomes enabled
whenever history type is Plan.

Table 14-12. $hist_plan_prolog_n
npsid integer This value along with the instance ID
(npsInstanceId) and operation ID (opid) form
the foreign key into the query table.
logentryid bigint This ID is a foreign key into the
hist_log_entry_n table with the NPS ID (npsid)
and instance ID (npsinstanceid). This ID with
npsid and npsinstanceid is also a primary key
for this table.
sessionid bigint Session ID. This ID, together with the NPS ID
(npsid) and instance ID (npsinstanceid) form the
foreign key from query, plan, table, and column
access tables into session tables.
planid integer Plan ID. This is used to make an equi join in
addition to NPS ID (npsid), instance ID
(npsinstanceid), and operation ID (opid) to
match a plan prolog to a plan epilog record.
xid bigint DBOS transaction ID.
gkpriority integer This field is deprecated and is no longer used.
submittime timestamp Submit time of the plan.
queuetime timestamp This field is deprecated and is no longer used.
preptime timestamp Date and time when the first snippet is
prepared.
gratime timestamp Time when the plan is queued to GRA.
starttime Start time of plan execution.
ismainplan Flag for the main plan of a query.
estimatedcost The estimated cost of the plan.
estimateddisk bigint The estimated disk space of the plan.
estimatedmem bigint The estimated memory of the plan.
totalsnippets integer The total number of snippets.
signature bigint The signature of the plan, which is stored as a
checksum value. If two plans have the same
signature, especially for the same query, the
plans are most likely identical.
qcrestart integer The count of query restart after a state change.
The value is zero if a restart has not occurred.
$hist_query_epilog_n
The $hist_query_epilog_n table contains the final data that is collected at the end
of the query.

Table 14-13. $hist_query_epilog_n
npsid integer NPS ID. This ID and the instance ID
(npsinstanceid) and operation ID (opid) form the
foreign key into the operation table.
sessionid bigint Netezza session ID. This ID and the NPS ID
(npsid) and instance ID (npsinstanceid) form the
foreign key from query, plan, table, and column
access tables into session tables.
finishtime timestamp The GMT time when the query finished.
resultrows bigint The number of rows affected by the SQL query.
This field shows the row count for SELECT,
INSERT, UPDATE, DELETE, and CTAS queries
on user tables, and SELECT, INSERT, UPDATE,
and DELETE queries on system tables or bridge
queries. For all other queries, the value is 0.
status integer Completion status of the query:
0 QUERY_EXECUTION_SUCCESS. Query
executed successfully.
-1 QUERY_ABORTED. Query execution
aborted. nzsession abort or SIGTERM.
-2 QUERY_CANCELLED. Query canceled
by the user who is using Control-C. This
is recorded in QueryCancelHandler()
(postgres.c).
-3 QUERY_FAILED_PARSING. Query
failed with parsing error.
-4 QUERY_FAILED_REWRITE. Query
failed during Postgres rewrite.
-5 QUERY_FAILED_PLANNING. Query
failed during planning.
-6 QUERY_FAILED_EXECUTION. Query
failed during execution.
-7 Reserved for future use.
-8 QUERY_FAILED_ACLCHECK. Query
failed ACL check.
-9 QUERY_FAILED_GENERIC. Query
failed by other generic errors.

$hist_query_overflow_n
The $hist_query_overflow_n table stores the remaining characters of the query
string that was stored in the querytext column of the $hist_query_prolog_n table.
For performance reasons, each row of this table stores approximately 8 KB of the
query string; if the query text overflow cannot fit in one 8 KB row, the table uses
multiple rows that are linked by sequenceid to store the entire query string.
Table 14-14. $hist_query_overflow_n
npsid integer This value along with the instance ID
(npsInstanceId) and operation ID (opid) form the
foreign key into the operation table.
sessionid bigint Session ID. This ID and the NPS ID (npsid) and
sequenceid integer This ID is the sequence ID of each entry. There is
one for each query text fragment. The first
overflow record has sequenceid 0.
next integer This is the pointer to next ID record (the next
8-KB portion of the querytext) in the sequence.
The last record has a next value of -1.
querytext nvarchar(8192) Up to 8 KB of the overflow part of the query
string.
$hist_query_prolog_n
The $hist_query_prolog_n table contains the initial data that is collected at the start
of a query.
A query with a plan, a query without a plan, and a plan without a query all result
in the creation of a record with an operation ID (opid) in the $hist_operation_n
table. The query prolog and epilog, plan prolog and epilog, table access, and
column access for that query or plan all share the same operation ID.
Consequently, this operation ID can be used as a key for joining all query-related
data. The session-related data is retrieved by using the foreign key session ID
(sessionid).
Table 14-15. $hist_query_prolog_n
npsid integer NPS ID. This ID and the instance ID
(npsinstanceid) and operation ID (opid) form
the foreign key into the operation table.

Table 14-15. $hist_query_prolog_n (continued)
npsinstanceid integer Instance ID of the source IBM Netezza
system.
logentryid bigint This ID and the NPS ID (npsid) and instance
ID (npsinstanceid) form:
v A foreign key into the hist_log_entry_n
table
sessionid bigint The Netezza session ID. This ID and the NPS
ID (npsid) and instance ID (npsinstanceid)
form the foreign key from query, plan, table,
and column access tables into session tables.
parentopid bigint Operation ID of the parent stored procedure.
For Release 4.6, this value is null.
userid bigint User ID used for execution of this query. For
Release 4.6, this value is null.
username nvarchar(128) User name that is used for the execution of
this query. For Release 4.6, this value is null.
submittime timestamp Submit time of the query.
checksum bigint The checksum of the entire query string,
which can help to identify identical queries.
querytext nvarchar(8192) Up to the first 8 KB of the query text. Any
remaining text in the query is stored in the
$hist_query_overflow_n table.
dbid bigint The OID of the database connected to at the
time of the query execution. For SET
CATALOG and SET SCHEMA queries, it is
the database connected to at the time when
those commands ran.
dbname nvarchar(128) The name of the database to which the query
is connected.
schemaid bigint The OID of the database connected to at the
time of the query execution.
schemaname nvarchar(128) The name of the schema to which the query
is connected.
client_user_id nvarchar(1024) The user ID under which the application that
submitted the query. This field is available
only in database version 3 or later.
client_application_name nvarchar(1024) The name of the application that submitted
the query associated with the plan. This value
is specified for the session, and is usually set
by an application. This field is available only
in database version 3 or later.

Table 14-15. $hist_query_prolog_n (continued)
client_workstation_name nvarchar(1024) The host name of the workstation on which
the application that submitted the query
associated with the plan runs. This value is
specified for the session, and is usually set by
an application. This field is available only in
client_accounting_string nvarchar(1024) The value of the accounting string. This value
is specified for the session, and is usually set
by an application. This field is available only
in database version 3 or later.
$hist_service_n
The $hist_service_n table records the CLI usage from the localhost or remote client.
It logs the command name and the timestamp of the command issue. This
information is collected in the history when COLLECT SERVICE is enabled in the
history configuration.
For more information, see the IBM Netezza Advanced Security Administrator's Guide.
Table 14-16. $hist_service_n
sessionid bigint Session ID. This ID is a foreign key into session_n
and is generated by the source Netezza system.
This ID and the NPS ID (npsid) form the foreign
key into session_n.
servicetype bigint The code for the command, which is one of the
following integer values:
v 1 = nzbackup
v 2 = nzrestore
v 3 = nzevent
v 4 = nzinventory (obsoleted in 5.0)
v 5 = nzreclaim
v 6 = nzsfi (obsoleted in 5.0)
v 7 = nzspu (obsoleted in 5.0)
v 8 = nzstate
v 9 = nzstats
v 10 = nzsystem
service varchar(512) The text string of the servicetype value
$hist_session_epilog_n
The $hist_session_epilog_n table stores details about each session when the session
is terminated. Each session completion creates an entry in this table with a unique
operation ID.

Table 14-17. $hist_session_epilog_n
npsid integer Unique ID of the source IBM Netezza system.
npsinstanceid integer Monotonically increasing nzstart instance ID of
the source Netezza system.
sessionid bigint Netezza session ID. This value is not unique for
more than one nzstart command. This ID with
the NPS ID (npsid) and instance ID
(npsinstanceid) form the foreign key from query,
plan, table, and column access tables.
endtime timestamp GMT timestamp of the session termination.
$hist_session_prolog_n
The $hist_session_prolog_n table stores details about each created session. Every
successful authentication or session creation adds an entry to this table with a
unique operation ID.
Table 14-18. $hist_session_prolog_n
npsid integer Unique ID of the source IBM Netezza system.
npsinstanceid integer Monotonically increasing nzstart instance ID of
the source Netezza system.
sessionid integer Netezza session ID. This value is not unique for
more than one nzstart command. This ID with
the NPS ID (npsid) and instance ID
(npsinstanceid) form the foreign key from query,
plan, table, and column access tables.
pid integer Process ID of Postgres on source Netezza system.
connecttime timestamp Connection time on the source Netezza system.
priority integer Session priority on the source Netezza system.
maxpriority integer Maximum priority for this session.
sessionuserid bigint User ID that created this session.
currentuserid bigint Current user ID for this session. This ID can be
different from the sessionUserId.
operatinguserid bigint The operating user ID for whom the ACL and
permission is used for validating permissions.
sessionusername nvarchar(128) The session user name that corresponds to
sessionUserId.

Table 14-18. $hist_session_prolog_n (continued)
currentusername nvarchar(128) The user name that corresponds to currentUserId.
operatingusername nvarchar(128) The user name that corresponds to
operatingUserId.
dbid bigint The OID of the database to which the session is
connected.
dbname nvarchar(128) The name of the database to which the session is
connected.
clienthost varchar(256) The host name of the client that established the
session.
clientip char(16) The IP address of the client that made the
connection.
clientpid integer The process ID of the client.
clienttype integer The type of the client such as:
v 0 = None
v 1 = LibPq client (for example, nzsql)
v 2 = ODBC client
v 3 = JDBC client
v 4 = nzload / nzunload
v 5 = Client of the client manager
v 6 = nzbackup / nzrestore
v 7 = nzreclaim
v 8 = Unused
v 9 = Internal Netezza tool
v 10 = OLE DB client
npsclientid integer Netezza client ID of the client.
rowsetlimit integer The value of the session variable for
sessionUserId.
sessiontimeout integer The value of the session variable for
sessionUserId.
querytimeout integer The value of the session variable for
sessionUserId.
srqueuetimeout integer The value of the session variable for
sessionUserId.
qcmaxrestarts integer The value of the session variable for
sessionUserId.
resourcegroupid bigint The value of the session variable for
sessionUserId.
resourcegroupname nvarchar The value of the session variable for
sessionUserId.
resourcepercentage integer The value of the session variable for
sessionUserId.
$hist_state_change_n
The $hist_state_change_n table logs the state changes in the system. It logs Online,
Paused, Offline, and Stopped.

For the Online state change, the logging occurs after the system goes Online. In
other cases, the logging occurs before the state transition is made to the respective
state. This information is collected in the history when COLLECT STATE is
enabled in the history configuration. For more information, see the IBM Netezza
Table 14-19. $hist_state_change_n
changetype bigint The code for the change type, which is one of the
following integer values:
v 1 = The system is Online.
v 2 = The system is going into the Paused state.
v 3 = The system is going into the Offline state.
v 4 = The system is going into the Stopped state.
change varchar(512) The text string for the change code as described
in changetype
$hist_table_access_n
The $hist_table_access_n table records the table access history for a query. This
table becomes enabled whenever history type is Table.
Table 14-20. $hist_table_access_n
seqid integer A plain sequence number of the entry. It starts at
zero for every npsid, npsinstanceid, and opid. It
increments monotonically for table access records
for each query.
sessionid bigint Session ID. This ID with NPS ID (npsid) and
dbid bigint OID of the database where the table is defined
dbname nvarchar(128) The name of the database where the table is
defined

Table 14-20. $hist_table_access_n (continued)
schemaid bigint The OID of the schema as specified in
schemaname nvarchar(128) The schema name as specified in
tableid bigint The table id of the table
tablename nvarchar(128) The table name of the table
usage integer The following bits are set to true if table appears
in:
v (usage & 1) <> 0 = selected
v (usage & 2) <> 0 = inserted
v (usage & 4) <> 0 = deleted
v (usage & 8) <> 0 = updated
v (usage & 16) <> 0 = truncated
v (usage & 32) <> 0 = dropped
v (usage & 64) <> 0 = created
v (usage & 128) <> 0 = statsgenerated
v (usage & 256) <> 0 = locked
v (usage & 512) <> 0 = altered
$hist_version
The $hist_version table shows information about the schema version number of the
history database.
Table 14-21. $hist_version
hversion integer Schema version of the history database (see
“History database versions” on page 14-2).
dbtype char(1) Type of the history database:
q A query history database.
a An audit history database.
History table helper functions

Within the history tables, several of the columns contain data that use mapped
values and bit masks. You can use the following helper functions within your
history queries to return more readable text values and strings for those internal
values:
Function Description Return value

FORMAT_QUERY_STATUS() Use this function to display text One of the following status values:
string versions of the v success
$hist_query_epilog.status column v aborted
data. v canceled
v failed parsing
v failed rewrite
v failed planning
v failed execution
v permission denied
v failed
v transaction aborted

Function Description Return value
FORMAT_PLAN_STATUS() Use this function to display text One of the following status values:
string versions of the v success
$hist_plan_epilog.status column data. v aborted
FORMAT_TABLE_ACCESS() Use this function to display text A comma-separated list of one or
string versions of all bits set in the more of the following values:
$hist_table_access.usage column data. v sel
v ins
v del
v upd
v drp
v trc
v alt
v crt
v lck
v sts
FORMAT_COLUMN_ACCESS() Use this function to display text A comma-separated list of one or
string versions of all bits set in the more of the following values:
$hist_column_access.usage column v sel
data. v set
v res
v grp
v hav
v ord
v alt
v sts
The following sample query shows how you can use these helper functions.
SELECT
substr (querytext, 1, 50) as QUERY,
format_query_status (status) as status,
tb.tablename,
format_table_access (tb.usage),
co.columnname,
format_column_access (co.usage)
from "$hist_query_prolog_3" qp
inner join
"$hist_query_epilog_3" qe using (npsid, npsinstanceid, opid)
inner join
"$hist_table_access_3" tb using (npsid, npsinstanceid, opid)
inner join
"$hist_column_access_3" co using (npsid, npsinstanceid, opid)
where
exists (select tb.dbname
from "$hist_table_access_3" tb
where tb.npsid = qp.npsid and
tb.npsinstanceid = qp.npsinstanceid and
tb.opid = qp.opid and
tb.tablename in (^nation^, ^orders^, ^part^,
^partsupp^, ^supplier^, ^lineitem^,
^region^))
and tb.tableid = co.tableid;

Chapter 15. Workload management
workload.
An IBM Netezza system attempts to run all of its jobs as fast as possible. If only
one job is active on the system, the system devotes all of its resources to
completing that job. If two jobs of equal priority are active, the system gives half of
its available resources to each job. Similarly, if 40 jobs of equal priority are active,
each job receives 1/40th of the available resources. This form of resource allocation
is called a fair-sharing model.
However, when running jobs concurrently you might want the system to prioritize
certain jobs over others. WLM involves classifying jobs and specifying resource
allocation rules so that the system assigns resources based on a predetermined
service policy.
Some Netezza service policies are predefined and cannot be modified. For
example:
v The admin user account has special characteristics that prioritize its work over
the work of other users.
v Certain types of system jobs have a higher priority than user jobs or other,
less-important system jobs.
Related concepts:
“Netezza database users and user groups” on page 11-1
accounts.
“Session priority” on page 11-38
You can define the default and maximum priority values for a user, a group, or as
the system default. The system determines the value to use when the user connects
to the host and executes SQL commands.
WLM techniques
IBM Netezza offers several techniques for managing resource allocations:
Table 15-1. Workload management feature summary
Technique Description
Scheduler rules Scheduler rules influence the scheduling of plans. Each scheduler rule
specifies a condition or set of conditions. Each time the scheduler
receives a plan, it evaluates all modifying scheduler rules and carries
out the appropriate actions. Each time the scheduler selects a plan for
execution, it evaluates all limiting scheduler rules. The plan is executed
only if doing so would not exceed a limit imposed by a limiting
scheduler rule. Otherwise, the plan waits. This provides you with a way
to classify and manipulate plans in a way that influences the other
WLM techniques (SQB, GRA, and PQE).

Table 15-1. Workload management feature summary (continued)
Technique Description
Guaranteed You can assign a minimum share and a maximum percentage of total
resource system resources to entities called resource groups. The scheduler ensures
allocation (GRA) that each resource group receives system resources in proportion to its
minimum share. A resource group receives a larger share of resources
when other resource groups are idle, but never receives more than its
configured maximum percentage. Each plan is associated with a
resource group, and the settings of that resource group settings
determine what fraction of available system resources are to be made
available to process the plan.
Short query bias Resources (that is, scheduling “slots”, memory, and preferential
(SQB) queuing) are reserved for short queries. A short query is a query for
which the cost estimate is less than a specified maximum value (the
default is 2 seconds). With SQB, short queries can run even when the
system is busy processing other, longer queries.
Prioritized query Based on settings that you configure, the system assigns a priority
execution (PQE) (critical, high, normal, or low) to each query. The priority can be made
to depend on factors such as the user, group, or session associated with
the query. The system can then use the priority as a basis for allocating
resources and scheduling work.
Use any combination of these techniques as required by the methodology that you
employ to manage queries.
Important: Work with your Netezza sales or support representative to assess

which WLM techniques are appropriate for your situation. Changes can affect
system behavior in unintended ways and must be carefully planned for and
implemented.
Scheduler rules
A plan is a unit of work that is created by the optimizer to handle a query. Each
plan is based on the content of a query and on statistics regarding the tables on
which the query acts. A single query usually results in a single plan, but
occasionally additional, auxiliary plans are generated also.
The scheduler places each plan that it receives into a pool of candidates for
execution. When the scheduler detects that there is capacity to execute a plan (for
example, because it was notified that the execution of another plan has completed),
it selects a plan from this pool. Which plan the scheduler selects is determined by
the system's SQB, GRA, and PQE settings, and by the attributes of each plan, for
example:
v Whether it is flagged as being short
v The resource group with which it is associated
v Its priority
A scheduler rule is an object that influences the scheduling of plans. Each scheduler
rule specifies:
v Zero or more conditions
v One action
v Whether it is to apply to admin plans as well as plans submitted on behalf of
other users

The action is carried out for each plan that meets all the specified conditions. If no
condition is specified, the action is carried out for all plans.
A scheduler rule can be of one of the following types:

Modifying
A modifying scheduler rule modifies the attributes of or aborts a plan. For
example, the following rule changes a plan with normal priority to a plan
with low priority:
IF PRIORITY IS NORMAL THEN SET PRIORITY LOW
Each time the scheduler receives a plan, it evaluates all modifying

scheduler rules and carries out the appropriate actions.
Limiting
A limiting scheduler rule limits the number of plans that can run
concurrently. For example, the following rule prevents more than one plan
associated with a query on tables or objects in the database with the name
DB1 from running at a time:
IF DATABASE IS DB1 THEN LIMIT 1
Each time the scheduler selects a plan for execution, it evaluates all
limiting scheduler rules. The plan is executed only if doing so would not
exceed a limit imposed by a limiting scheduler rule. Otherwise, the plan
waits.
By deft use of scheduler rules, you can exert a high level of control over plan
execution. A scheduler rule does not apply to admin plans unless you explicitly
specify otherwise when you create the rule.
Scheduler rule conditions
The conditions of a scheduler rule determine whether it applies to a particular

plan:
RESOURCEGROUP
The plan's resource group. Usually, this is the resource group of the user
who submitted the corresponding query; however, it can be changed by a
modifying scheduler rule. The specified resource group must already exist.
PRIORITY
The priority of the plan:
v CRITICAL
v HIGH
v NORMAL
v LOW
TYPE The plan type:
LOAD
The plan loads (reads) data from an external table.
UNLOAD
The plan unloads (writes) data to an external table.
GENERATE STATISTICS
The plan generates or updates database statistics
GROOM
The plan removes outdated and deleted records from tables.
Chapter 15. Workload management 15-3

UDX The plan runs a user-defined object.
DATABASE
The database that is to be accessed by the plan. This is the database to
which the session is connected. The specified database must already exist.
USER The user who submitted the query that corresponds to the plan. The
specified user must already exist. The specified user cannot be Admin. To
include plans associated with Admin jobs, specify the INCLUDING
ADMIN option.
TABLE
A user table accessed by the plan. The specified table must already exist. If
the database name or schema name are needed to uniquely identify the
table, they must be specified as part of the table name.
TAG A string that is to be associated with and can be used to reference the plan
(see “Tags” on page 15-6).
CLIENT_USER_ID
The user ID under which the application that submitted the corresponding
query is running. This value is specified for the session, and is usually set
by an application. The value must be specified in single quotes.
CLIENT_APPLICATION_NAME
The name of the application that submitted the corresponding query. This
value is specified for the session, and is usually set by an application. The
value must be specified in single quotes.
CLIENT_WORKSTATION_NAME
The host name of the workstation on which the application that submitted
the corresponding query runs. This value is specified for the session, and is
usually set by an application. The value must be specified in single quotes.
CLIENT_ACCOUNTING_STRING
The value of the accounting string. This value is specified for the session,
and is usually set by an application. The value must be specified in single
quotes.
ESTIMATE
The lower bound, upper bound, or both of the estimated cost of the plan,
in seconds:
v Specify a lower bound using the > or >= operator.
v Specify an upper bound using the < or <= operator.
If a scheduler rule specifies both a lower and an upper bound, the lower
bound must be less than the upper bound.
Actions of a modifying scheduler rule
A modifying scheduler rule can specify the following actions:

SET SHORT
Set the SQB flag for the plan, regardless of its cost estimate and the
threshold set by the host.schedSQBNominalSecs registry setting.
SET NOT SHORT
Do not set the SQB flag for the plan, regardless of its cost estimate and the
threshold set by the host.schedSQBNominalSecs registry setting.

ADD TAG
Add a tag to this plan. Each plan can have any number of tags associated
with it.
SET PRIORITY
Change the priority of the plan. This action ignores user and group limits
on priority.
SET ESTIMATE
Set the cost estimate of the plan, in seconds. This action overrides the
estimate calculated by the planner. It does not affect the SQB flag.
INCREASE PRIORITY
Increase the priority of the plan by one level, for example from NORMAL
to HIGH. It ignores an attempt to increase a CRITICAL priority, and
ignores user and group limits on priority.
DECREASE PRIORITY
Decrease the priority of the plan by one level, for example from NORMAL
to LOW. It ignores an attempt to decrease a LOW priority, and ignores user
and group limits on priority.
EXECUTE AS RESOURCEGROUP
Execute the plan as if it belonged to the specified resource group.
ABORT
Abort the plan. This provides a way to temporarily disallow jobs that
involve particular tables, database, or users, for example, during
maintenance. The specified message is passed to the user who issued the
corresponding query.
Using scheduler rules with SQB, GRA, and PQE
A scheduler rule can modify the following plan attributes:

v Resource group
v Priority
v Cost estimate
v Whether it is short
v Tags
This provides you with a way to classify and manipulate plans in a way that
influences the SQB, GRA, and PQE mechanisms:
SQB You can specify whether a plan is short. For example, the following
scheduler rule causes all plans that run user-defined objects to be regarded
as being short, regardless of their cost estimates:
IF TYPE IS UDX THEN SET SHORT
GRA You can associate plans with particular resource groups. For example, the
following scheduler rules associate plans with resource groups based on
the databases that they access:
IF DATABASE IS DB1 THEN EXECUTE AS RESOURCEGROUP RSG_A
IF DATABASE IS DB3 THEN EXECUTE AS RESOURCEGROUP RSG_B
IF DATABASE IS DB5 THEN EXECUTE AS RESOURCEGROUP RSG_B
By configuring resource groups RSG_A and RSG_B appropriately, you can

make resource allocation dependent on which databases are being

accessed. Note that the resource groups RSG_A and RSG_B do not have to
have any users assigned to them, but can be used exclusively as a means
to allocate system resources.
PQE You can modify plan priority. For example, the following scheduler rules
modify the priority of plans based on the tables that they access:
IF TABLE IS T1 THEN SET PRIORITY LOW
IF TABLE IS T7 THEN DECREASE PRIORITY
Scheduler rule evaluation order
Scheduler rules are evaluated in alphanumeric order (a-z, A-Z, 0-9) according to
their names. For example, the following rules might both be defined:
Rule name Rule

r2_decrease_normal IF PRIORITY IS NORMAL THEN DECREASE PRIORITY
r3_low_to_normal IF PRIORITY IS LOW THEN SET PRIORITY NORMAL
When a plan with normal priority is processed, the rule with the name
r2_decrease_normal, which is processed first, causes the priority of the plan to be
decreased from NORMAL to LOW. Then, the rule with the name r3_low_to_normal
causes the priority of the plan to be set back to NORMAL.
Tags
A tag is a string that is associated with and used to refer to a particular session or
plan:
Session tag
A session tag applies to a particular session and to all the plans that are
within the scope of that session. It is set by specifying the ADD TAG
parameter for an ALTER SESSION command.
Plan tag
A plan tag applies to a particular plan. It is set by specifying the ADD
TAG parameter for a CREATE SCHEDULER RULE command.
A condition (but no more than one) of a scheduler rule can refer to a tag to
influence plan scheduling. For example:
v To prevent an end-of-month test from sapping performance, you might add a
tag with the name eom_test to the corresponding session, and create a scheduler
rule with a condition that refers to that tag and that automatically decreases the
priority of any plan that originates from that session:
IF TAG IS eom_test THEN DECREASE PRIORITY
v To prevent a session in which extract, transform, and load (ETL) jobs run from
sapping performance, you might add a tag with the name etl to that session,
and create a scheduler rule with a condition that refers to that tag and that
automatically set the priority of any plan that originates from that session to
LOW:
IF TAG IS etl THEN SET PRIORITY LOW
A scheduler rule can be used to add a tag to each plan that meets the conditions it
specifies. For example, a scheduler rule might add the tag user_is_jill to each
plan for which the associated user is jill:
IF USER IS jill THEN ADD TAG user_is_jill

This tag can then be referenced by subsequent scheduler rules. This is helpful
when you have a long or complex condition that is employed by several scheduler
rules.
By creating several scheduler rules each of which adds the same tag to each plan
that meets its conditions, you can specify a series of conditions that behave as if
linked by a logical OR operator. For example, the following three rules, when
evaluated in the order shown, cause the limit to be set to 2 for all plans for which
either the database is reportdb or the user is joe:
IF DATABASE IS reportdb THEN ADD TAG no_more_than_2
IF USER IS joe THEN ADD TAG no_more_than_2
IF TAG IS no_more_than_2 THEN LIMIT 2
Client information
The application that submitted the query that is associated with a plan is called the
plan's client. The following information about the client can be specified for a
session and referenced by a scheduler rule condition:
User ID
Application name
Workstation name
The host name of the workstation on which the client runs.
Accounting string
The value of the accounting string from the client information that is
specified for the session.
These information fields can be set by either:

v An administrator, by issuing the nzsql SET command
v An application program, by means of the ODBC API (see IBM Netezza ODBC,
JDBC, OLE DB, and .NET Installation and Configuration Guide)
Each value can be up to 1024 characters.
Scheduler rule security
To create a scheduler rule, you must either be the admin user or your user account
must have the Scheduler Rule privilege. The admin user and a user with the
Scheduler Rule privilege can also list, drop, alter, deactivate, or reactivate any rule,
regardless of who created or owns it.
The owner of a scheduler rule is, by default, the user who created it; however,
ownership can be reassigned to a different user. The owner of a scheduler rule can
list, drop, alter, deactivate, or reactivate that rule, regardless of which privileges
that user has been granted.
Scheduler rules tasks

You create a scheduler rule by issuing the CREATE SCHEDULER RULE nzsql
command.
After you create a scheduler rule, it is active. You can temporarily deactivate an
active scheduler rule, or reactivate a deactivated scheduler rule, by issuing the SET
nzsql command.

To display a list of all scheduler rules, issue the SHOW SCHEDULER RULE nzsql
command.
To rename a scheduler rule or to change the owner of a scheduler rule, issue the
ALTER SCHEDULER RULE nzsql command.
To delete a scheduler rule, issue the DROP SCHEDULER RULE nzsql command.
Other tasks that affect scheduler rules are:

v Adding a tag to a session using the ALTER SESSION command
v Showing the tags for the current session using the SHOW TAGS command
v Setting values for client information for a session using the SET command
When you drop a database or resource group that is defined in a schedule rule, the
system also drops the rule. If a scheduler rule references a resource group that is
altered to remove its resource settings, the scheduler rule is dropped.
The SQL commands are described in the IBM Netezza Database User’s Guide
Guaranteed resource allocation (GRA)

You can use scheduler rules or resource group assignments to classify plans into
different groups, then use guaranteed resource allocation (GRA) to arrange for each
group to receive a different portion of system resources.
The net system resources are the system resources that are available to process user
(including admin) jobs, that is, the total system resources minus those resources
that are needed to process special, high-priority system jobs.
A resource group is a Netezza group whose resource settings (that is, its resource
minimum, resource maximum, and job maximum) determine what portion of the
net system resources are to be allocated to plans that are associated with that
group. For example, you might create three different resource groups for the plans
of data analysts, users who produce query reports, and all other users, then
arrange for each of these groups to receive a different fraction of the net system
resources.
Each Netezza system has at least one resource group. This group has the name
Public and cannot be dropped. When a user is created, if the user is not explicitly
assigned to a resource group, the user is assigned to the Public group by default.
You can change a user's resource group assignment.
Each plan that is processed by a Netezza system is associated with exactly one
resource group. If no other resource groups are created for a system, all plans are
associated with the Public group. However, you can create additional resource
groups and associate plans with these groups based on any combination of the
following criteria:
Which user submitted the corresponding job
Each user is assigned to exactly one resource group. Each time a user
submits a job, the plans for that job are automatically associated with the
user's resource group.
You can use scheduler rules to override a plan's resource group association
based on the submitting user. For example, the following scheduler rule

associates all plans for jobs submitted by the user bob with the resource
group rsg42, regardless of the resource group to which bob is assigned:
IF USER IS bob THEN EXECUTE AS RESOURCEGROUP rsg42
The contents of the client information fields
An administrator or application program can set the following client
information fields in a query:
User ID
Application name
Workstation name
Accounting string
The value of the accounting string from the client information that
is specified for the session.
You can use scheduler rules to associate plans with different resource
groups based on the contents of these fields (see “Client information” on
page 15-7). For example, the following scheduler rule associates all plans
for jobs submitted by the application named Cognos with the resource
group rsg12:
IF CLIENT_APPLICATION_NAME IS Cognos THEN EXECUTE AS RESOURCEGROUP rsg12
Cost estimates
For each plan, the optimizer calculates the expected cost of processing that
plan. You can use scheduler rules to associate plans with different resource
groups based on their calculated cost estimates. For example, the following
scheduler rules associate plans with the resource groups with the names
"short", "medium", and "long" based on the plans' cost estimates:
IF ESTIMATE < 4 THEN EXECUTE AS RESOURCEGROUP short
IF ESTIMATE >= 4 ESTIMATE < 30 THEN EXECUTE AS RESOURCEGROUP medium
IF ESTIMATE >= 30 THEN EXECUTE AS RESOURCEGROUP long
The database that is to be accessed
groups based on which databases the plans access. If different tenants
access different databases exclusively, you can use this capability to
manage resource allocation based on tenancy. For example, the following
scheduler rules associate plans with different resource groups based on
which database they access:
IF DATABASE IS dbx1 THEN EXECUTE AS RESOURCEGROUP x1
IF DATABASE IS dbx2 THEN EXECUTE AS RESOURCEGROUP x2
The table that is to be accessed
groups based on which tables the plans access. In this way, a database
administrator can influence resource allocation to applications without
changing the applications themselves. For example, the following scheduler
rule associates a plan with resource group x2 if it accesses table tab1 or
tab2:
IF TABLE IN (tab1,tab2) THEN EXECUTE AS RESOURCEGROUP x2
Custom tags
You can add any number of tags to sessions (see “Tags” on page 15-6). All
the plans that are within the scope of that session receive the same tag.

You can also create scheduler rules that add tags directly to all plans that
meet the conditions specified by the rule. You can then use scheduler rules
to associate plans with different resource groups based on these tags. For
example, the following scheduler rule associates a plan with a resource
group based on whether one or more of the specified tags have been set
for the plan or its session:
IF TAG IN (eod,eom,eoy) THEN EXECUTE AS RESOURCEGROUP endjobs
Resource minimums and maximums

For each resource group, you specify parameters that determine which fraction of
the net system resources are used to process the plans associated with that
resource group:
resource minimum
This determines the smallest fraction of net system resources that are to be
made available to the group. The value can be from 0-100, but a group is
considered to be a resource group only if a nonzero value is specified. A
resource group for which at least one job is pending is said to be active.
Tip: Although the resource minimum is a number from 0-100, it is not a

percentage; it is a number of shares that is used to determine a proportion.
For example, if the sum of the resource minimums of all active resource
groups is 120, and if one resource group has a resource minimum of 40,
that resource group is entitled to a minimum of 40/120 or 33% of net
system resources. The NzAdmin interface and the IBM Netezza
Performance Portal prevent you from specifying resource minimums that
add up to more than 100. However, when you use the CREATE GROUP
and ALTER GROUP nzsql commands, there is no limit to the total number
of resource minimum shares you can allot.
resource maximum
This specifies the largest percentage of net system resources that the
resource group is to receive, regardless of how many other resource groups
are using the system. The value can be from 1-100 and can be configured
only for a resource group. The default is 100. A resource group with a
resource maximum of 100 is said to be unlimited.
Tip: The resource maximum is a percentage. For example, if the resource

maximum of a resource group is set to 70 and its resource minimum is set
to 40, and if the sum of the resource minimums of all active resource
groups is 50, even though the resource group is entitled to 40/50 or 80% of
net system resources, it would receive only 70%.
Note: A group can be one or both of the following types:

User group
A group with one or more members is a user group. Each member of a user
group inherits its privileges and other settings, with the exception of its
resource minimum, resource maximum, and job maximum settings. User
groups are used to simplify access management.
Resource group
A group that specifies a nonzero minimum resource percentage is a resource
group. Each resource group also specifies a resource maximum and job
maximum, either explicitly or by default. These three settings are called the
group's resource settings. Each user is assigned to exactly one resource
group. Resource groups are used for workload management.

A group can be both a user group and a resource group, but its user group and
resource group aspects, including user group membership and the assignment of
users to a resource group, are completely separate:
v A user might be assigned to a resource group but not be a member of that
group. That user is unaffected by any privileges or settings of that group, except
for the resource settings.
v A user might be a member of a user group but be assigned to a different
resource group. That user is unaffected by the user group's resource settings.
The resource percentage of a resource group is the percentage of the net system
resources that are made available to that resource group, and is determined by the
resource group's resource minimum and maximum. The system applies the
resource minimum and maximum of each resource group in such a way that the
resource group receives its apportioned share of net system resources.
A resource minimum applies only when the corresponding resource group has a
job pending. When a resource group is idle, its system resources can be used by
other, active resource groups. An active resource group might receive more than its
resource minimum when other resource groups are idle; however, a resource group
cannot receive more than its configured resource maximum.
The system applies the following rules in the order shown to determine how to
assign system resources to the active resource groups:
Table 15-2. Assign resources to active resource groups
Condition Resource allocation rule
The sum of the RESOURCE MAXIMUM The system allocates resources based on the
settings for all active resource groups is <= RESOURCE MAXIMUM settings.
100.
The sum of the RESOURCE MINIMUM The system allocates resources in proportion
settings for all active resource groups is to the RESOURCE MINIMUM settings for
<=100. each resource group, but the allocations are
limited by the RESOURCE MAXIMUM
settings. Any excess resources are allocated in
proportion to the difference between the
allowed resources and the RESOURCE
MAXIMUM settings.
The sum of the RESOURCE MINIMUM The system allocates resources in proportion
settings for all active resource groups is > to the normalized RESOURCE MINIMUM
100. settings for each resource group.
Related concepts:
performance.
Resource group example

As an example of how to use resource groups to partition system resources,
imagine a system that is used by three types of users:
v Data analysts
v Users who produce query reports
v All other users
You can create a resource group for each type of user, and then either:
v Assign each user to the appropriate resource group.
v Create a scheduler rule to reassociate the plans of each user with the appropriate
resource group.
Table 15-3. Example of resource groups
User type Resource Group Resource Minimum Resource Maximum
Data analysts analysts 50 100
Users who produce query rptquery 30 60
reports
All other users public 20 80
You can create the analysts and rptquery groups and can alter the resource
maximum of the public group either by using the NzAdmin tool or by issuing the
following nzsql commands:
CREATE GROUP analysts WITH RESOURCE MINIMUM 50;
CREATE GROUP rptquery WITH RESOURCE MINIMUM 30 RESOURCE MAXIMUM 60;
ALTER GROUP public WITH RESOURCE MAXIMUM 80;
You can then either:

v Assign user accounts to each resource group. For example, the following
command assigns the user bob to the analysts resource group:
ALTER USER bob IN RESOURCEGROUP analysts;
v Create a scheduler rule to reassociate the plans of each user with the appropriate
resource group. For example, the following command creates a rule that causes
all plans for jobs submitted by bob to be assigned to the analysts resource group:
CREATE SCHEDULER RULE bob1 AS IF USER IS bob THEN EXECUTE AS
RESOURCEGROUP analysts;
When all three resource groups are running jobs on the system, the GRA scheduler
works to balance resource utilization as shown in Figure 15-1 on page 15-13:

A User requests
B Request queues
C Minimum resource guarantees
Figure 15-1. GRA usage sharing
The system ensures that members of the analysts resource group get at least 50%
of the net system resources when all the resource groups are active. At the same
time, the system ensures that the member of the rptquery and public resource
groups are not starved for resources.
Guaranteed resource allocation example

Guaranteed resource allocation (GRA) helps to ensure that a resource group
receives its resource minimum when all resource groups are active. When some
resource groups are idle, an active resource group receives additional resources, up
to its configured resource maximum. If only a few of the resource groups are busy,
the system has more resources to give to the active resource groups, but it applies
the resource minimums and maximums to ensure fair allocations. For example:
v If the analysts resource group is the only active group, it can use up to 100% of
the system resources for its work (its resource maximum).
v If the rptquery resource group is the only active group, it can use up to 60% of
the net system resources (its resource maximum). The remaining 40% of the net
system resources remain unallocated.
v If the analysts and public resource groups are the only active groups, their
resource minimums total 70%. The system determines their resource percentages
based on their relative resource minimums. The result for each resource group
does not exceed its resource maximum.
min max resource percentage
public 20 80 20 / (20 + 50) = 29
analysts 50 100 50 / (20 + 50) = 71
v If the rptquery and public resource groups are the only active groups, their
resource minimums total 50%. The system determines their allowed resource
percentages based on their relative resource minimums. Because the result for
the rptquery resource group exceeds its resource maximum, the excess is
assigned to the public resource group.

min max resource percentage
rptquery 30 50 30 / (20 + 30) = 60, but 50 is maximum
public 20 80 20 / (20 + 30) = 40 plus 10 that rptquery cannot use = 50
The system frequently adjusts the resource percentages that are based on the
currently active resource groups and their plans. Because work is often submitted
and finished quickly, at any one time it might appear that a particular resource
group is not receiving resources (because it is inactive) while other resource groups
are monopolizing the system (because they are continually active). However, over
time, and especially during peak times when all resource groups are active, the
actual resource percentage of a resource group usually averages out to its
calculated resource percentage. The measure of whether a resource group is
receiving its resource percentage is called compliance. The system provides several
reports that you can use to monitor compliance.
Related concepts:
“Monitoring resource utilization and compliance” on page 15-17
Allocations for several plans associated with the same group

Within a resource group, the number of concurrently active plans affects the
resources that are applied to each plan. The allocated resources for a resource
group are shared among the active plans for that group.
For example, if all three of the resource groups described in Figure 15-1 on page
15-13 are busy, and if the analysts group has:
v One active plan, that plan receives all the resources allocated to that group (50%)
v Two active plans that have the same priority, they each get half of the resources
allocated to that group (25% each)
v Ten active plans that all have the same priority, each plan gets one-tenth of the
resources allocated to that group (5% each)
If the concurrent plans have different priorities, the system allocates the resources
within the group by using priority weighting factors as described in “Priority
weighting and resource allocation” on page 15-25.
The following figure illustrates how a busy analysts users group can result in its
plans being given fewer overall system resources per plan than a single active plan
in either the rptquery or public groups, even though those groups have lower
overall resource minimums.
Figure 15-2. Several plans in a group share the group's resources

As you plan the resource percentages for each resource group, be sure to consider
the number of plans that are likely to run concurrently for that group. You might
need to adjust the resource allocation percentages to ensure that busy groups have
enough resources to complete the expected number of concurrent plans in a timely
manner. You can also configure a limit for the number of active plans from a
resource group to ensure that a specific number of active plans have reasonable
resource allocations; any additional plans wait until the active plans finish.
Configuring limits for resource groups

By controlling the number of concurrent plans, you can help to improve
performance for the active plans and avoid situations in which too many active
plans result in inadequate performance for all of them.
To control the number of actively running plans associated with a particular

resource group, create a limiting scheduler rule for that resource group. For
example:
IF RESOURCEGROUP IS public THEN LIMIT 2
Any additional plans associated with that resource group are queued until the
active plans finish.
The JOB MAXIMUM attribute of a resource group also controls the number of
actively running plans that are submitted by that group, but this attribute is
deprecated. The JOB MAXIMUM attribute can have the following values:
v A value of 0 (or OFF) specifies that the group has no maximum for the number
of concurrent plans. The group is restricted by the usual system settings and
controls for concurrent plans.
v A value of 1 - 48 to set the job maximum to the specified integer value.
v A value of -1 (or AUTOMATIC) specifies that the system calculates a job
maximum value that is based on the group's resource minimum multiplied by
the number of GRA scheduler slots (default 48). For example, if a group has a
resource minimum of 20%, the job maximum is (.20 * 48) or approximately 9.
Resource allocations for the admin user

For example, when a plan for a job submitted by the admin user is active, the
resource allocations described in Figure 15-1 on page 15-13 change as shown in
Figure 15-3 on page 15-16.

Figure 15-3. Effects of the admin user on GRA. The admin user receives 50% of net system resources. The resource
percentages of the other resource groups are half of what they would be if no admin plans were active.
The admin user account is a superuser account that is intended for emergency
actions only and not for everyday use. Few users should ever run jobs as the
admin user, and they should do so infrequently and only for urgent operations. As
an alternative to allowing users to use the admin user account, create a resource
group that has some or all of the object and administrative privileges of the admin
user and add the appropriate users to it. The resource minimum and maximum of
this resource group will determine its impact on resource availability.
Related concepts:
“Default Netezza groups and users” on page 11-3
group named public.
Related tasks:
“Creating an administrative user group” on page 11-17
Disabling, enabling, and configuring GRA

GRA is enabled by default. “Changing configuration settings” on page 7-19
describes how to disable or re-enable GRA and how to modify the GRA scheduler
horizon and compliance settings, if necessary.
GRA compliance
The GRA scheduler tracks resource usage to ensure that each resource group
receives its minimum allocation of resources when all groups are actively using the
system. The measurement of how well a group receives its configured resource
allocation is called compliance.
The IBM Netezza measures compliance by measuring the work statistics for each
job that is completed on the system. The GRA scheduler tracks the work statistics
for each resource group and divides the amount of resources used by a resource
group over the total amount of resources used by all of the resource groups during
that time. The GRA scheduler uses the resulting actual use percentage to determine
whether a group is in compliance or whether it is overserved or underserved. The
resource percentage is the amount of resources that a group is allocated, based on its
minimum and maximum resource settings and the activity of other resource
groups on the system.

v An overserved group is one that receives more resources than its allowed
percentage. This often happens when one group is busy but the others are not.
Because of the volume of the activity when other groups are idle, the group
receives more than its allowed share of the resources.
v An underserved group is one that has receives less than its allowed percentage.
Typically, this occurs because a group is idle. If users are not submitting any
work, the group does not require or use the resources apportioned to it.
The GRA scheduler uses the compliance values to rank the groups from very
underserved to very overserved. If a group is underserved, the GRA scheduler
chooses the underserved group's work ahead of an overserved group's work.
The GRA scheduler calculates compliance over a horizon value; the horizon is 60
minutes by default. The horizon is a moving time window of the last hour's
activity to show compliance. Netezza moves the window every 1/60th of the
horizon (every minute for GRA, and every 10 seconds for the snippet scheduler).
Monitoring resource utilization and compliance

IBM Netezza has several methods for monitoring GRA usage and compliance, and
the workload itself.
v You can use several system views and virtual tables to display information
about resource group utilization and history, and system utilization.
v You can use the NzAdmin interface to display information about how the
system is allocating resources.
v You can use the Netezza Performance Portal interface to monitor query activity
and workload on your Netezza systems. For details, see the IBM Netezza
Performance Portal User's Guide.
The following sections describe the resource views and NzAdmin reports. For
details on the Netezza Performance Portal reports, see the IBM Netezza Performance
Portal User's Guide or the online help available from the portal interface.
Related concepts:
“Guaranteed resource allocation example” on page 15-13
GRA views and reporting

For each active resource group, the system provides information about how busy
each group is, and how the scheduler is managing the GRA resources and
scheduler resources.
You can use the following views to monitor GRA and snippet scheduling data:
_v_sched_gra_ext and _v_sched_sn_ext
These views display information about how busy the system is and how
GRA and snippet resources are being allocated and used by the recent jobs
on the system. After each report interval, the system adds a row for each
active group with its resource compliance totals for that period. If a group
is not active, the system does not create a row for that group. For a system
with few resource groups, the _v_sched_gra_ext view typically contains
records for about a week of activity, and the _v_sched_sn_ext view
typically contains a few hours of data. These views are reset when the
system stops and restarts.

Note: The deprecated _v_sched_gra view is still provided for compatibility
reasons. However, the _v_sched_gra_ext view contains more information,
such as the maximum resource allocations and job limit information, and
should be used whenever possible.
_v_gra_sched_ext_latest and _v_sched_sn_ext_latest
These views display information about the previous 10-minute update of
scheduling information.
Note: The deprecated _v_sched_gra_latest view is still provided for

compatibility reasons. However, the _v_gra_sched_ext_latest view contains
more information, such as the maximum resource allocations and job limit
information, and should be used whenever possible.
_v_plan_resource
This view shows resource usage over time to assist with WLM
troubleshooting and capacity planning. It keeps at least 2000 records of
query plan activity.
_v_system_util
This view shows system utilization for certain resources such as host and
SPU CPU, disk, memory, and fabric (communication) resources. The
displayed values are normalized between 0 (no utilization) and 1 (full
utilization).
_v_sched_sys
This view shows information about the numbers of queued and running
plans and about resource availability and usage for the host and SPUs.
The update intervals for the following views are specified by configuration settings
that you can adjust as described in “Changing configuration settings” on page
7-19:
v _v_sched_gra_ext
v _v_sched_sn_ext
v _v_system_util
v _v_sched_sys
To display the information shown by a view, issue a SQL command for the form:
SELECT * FROM viewname;
Note: The view output might refer to an _ADMIN_ resource group. This is the
default group for the admin user account and cannot be modified.
NzAdmin GRA reports

The NzAdmin tool offers three reports that display information about how the
system is allocating resources:
Summary
Displays the GRA performance status for the last 60 minutes. For more
information, see “Resource Allocation Performance summary” on page
15-19.
History
Displays all available table information from summary data that is
captured in 10-minute intervals. For more information, see “Resource
Allocation Performance History window” on page 15-19.
Graph Displays the resource allocation history for specific days. For more
information, see “Resource Performance History graph” on page 15-20.

Resource Allocation Performance summary
The Resource Allocation Performance summary displays the active resource
allocation groups, their requested versus granted allocation percentages, plus the
number of jobs that are running and the number of short and long queued jobs.
To view the resource allocation performance summary status, on the NzAdmin

toolbar click Tools > Workload Management > Performance > Summary.
The system displays the Resource Allocation Performance window.
Figure 15-4. Resource Allocation Performance window
Resource Allocation Performance History window

The Resource Allocation Performance History window displays the summary for
the hourly horizon with the most recent hour first.
The previous horizon summaries display in descending order. Review this window
to see the actual resource percentages for that hour, and a snapshot of the job
summary status at the conclusion of that hour.
To view the resource allocation performance history, on the toolbar click Tools >
Workload Management > Performance > History.
The following figure shows the Resource Allocation Performance History window.

Figure 15-5. Resource Allocation Performance History window
Resource Performance History graph

The Resource Allocation Performance graph compares the allocation percentages
for up to 14 groups on a daily basis, along with a summary of the active jobs
throughout the day.
To view the resource allocation performance history graph, on the toolbar click
Tools > Workload Management > Performance > Graph.
The following figure system displays the Resource Allocation Performance graph.

Figure 15-6. Resource Allocation Performance graph
v The lines for each group show the resource usage trends through the day with
the usage percentage on the left vertical axis.
v The blue shaded background shows the number of jobs that are running at each
time interval with the job count on the right side vertical axis.
v You can use the list to select a different day of resource usage to display.
Resource group assignments

Each user is assigned to exactly one resource group. When GRA is used, this
resource group determines the amount of resources that are to be made available
to process a query that was submitted by that user.
In addition to being assigned to a resource group, each user can be a member of

any number of user groups. However, a user's membership in a user group, even a
user group that is itself a resource group, does not affect that user's resource group
assignment. The resource group assignment is determined solely by the nzsql
CREATE USER and ALTER USER commands; it is not affected by assignments
made during a CREATE GROUP or ALTER GROUP command. A user can even be
assigned to a resource group of which that user is not a member. For example:
v The following command creates a user account with the name bob and assigns
bob to the rptusers resource group:
CREATE USER bob WITH PASSWORD ’test96’ IN RESOURCEGROUP rptusers;
If no resource group were specified for this CREATE USER command, bob
would be assigned to the public resource group.
v The following CREATE GROUP command creates the analysts user group,
specifies a nonzero resource minimum (which means that the user group is a
resource group), and assigns bob to that group:
CREATE GROUP analysts WITH RESOURCE MINIMUM 50 USER bob;
However, this command does not change bob's resource group assignment,
which remains to the rptusers resource group.
v The following ALTER GROUP command drops bob from the rptusers user
group:
ALTER GROUP rptusers DROP USER bob;

However, this command does not change bob's resource group assignment,
which remains to the rptusers resource group.
v The following command changes bob's resource group assignment to the
analysts resource group:
ALTER USER bob IN RESOURCEGROUP analysts;
For each of these commands, the specified resource group must already exist; that
is, there must be a user group with that name and it must have a nonzero resource
minimum.
After you assign a user to a resource group, you cannot change the resource
minimum of that resource group to 0. If you drop a resource group, users who are
assigned to it are reassigned to the public resource group.
To remove a user assignment, assign the user to the public resource group. For
example:
ALTER USER bob IN RESOURCEGROUP public;
Short query bias (SQB)

Within each resource group, you can reserve scheduling and memory resources for
short queries. When the standard scheduler queues become full, short queries can
take advantage of additional resources reserved especially for them. This enables
the system to run short queries even while it is busy running long queries.
The cost of a query is the number of seconds required to run it. The optimizer uses
internal mechanisms such as prep snippets to estimate the cost of each query
before it is run. A query is regarded as being a short query if its cost estimate is less
than or equal to the threshold specified by the host.schedSQBNominalSecs setting.
The default setting is two seconds.
Typical short queries are "pick list" queries, dimensional data lookups, and other
quick data lookups. They are often submitted by a business intelligence application
when populating selection lists, or are entered on a SQL command line by a user
who then waits for the results. Typical long queries are complex business
intelligence queries that can return gigabytes or terabytes of results, or queries that
perform complex joins, comparisons, or user-defined analysis. They typically take
many seconds, minutes, or even hours to run. A long query can be entered on a
command line, but is more commonly issued by a business intelligence application
that creates scheduled reports for deep-dives into databases.
When the Short Query Bias (SQB) function is enabled, the system reserves
scheduling and memory resources for short queries. When SQB is disabled, a user
who runs a short query while the system is busy running long queries might
experience a significant delay.
SQB is enabled by default. “Changing configuration settings” on page 7-19

describes how to disable or re-enable SQB and how to modify the configuration
settings that control SQB, if necessary.
When SQB is enabled and the optimizer determines that a particular query is
short, it sets the SQB flag of each of the plans that is associated with that query to
true. You can use scheduler rules to override the setting of an SQB flag based on
any combination of the following criteria:

Which user submitted the corresponding query
You can use scheduler rules to override a plan's SQB flag based on the
submitting user. For example, for each plan for a query submitted by the
user bob, the following scheduler rule sets the SQB flag to false, regardless
of the plan's cost estimate or the threshold set by
host.schedSQBNominalSecs:
IF USER IS bob THEN SET NOT SHORT
User ID
Application name
Workstation name
Accounting string
You can use scheduler rules to set SQB flags to true or false based on the
contents of these fields (see “Client information” on page 15-7). For
example, the following scheduler rule sets the SQB flag to false for all
plans of jobs submitted by the application named Cognos:
IF CLIENT_APPLICATION_NAME IS Cognos THEN SET NOT SHORT
Cost estimates
You can use scheduler rules to set SQB flags to true or false based on the
calculated cost estimate, regardless of the plan's cost estimate or the
threshold set by host.schedSQBNominalSecs. For example, for each plan for
a query submitted by the user sam, the following scheduler rule effectively
changes the short query threshold to 60 seconds:
IF USER IS sam ESTIMATE < 60 THEN SET SHORT
You can use scheduler rules to set SQB flags to true or false based on
which databases the plans access. For example, the following scheduler
rule effectively changes the short query threshold to 40 seconds for all
plans that access the database dbx1 or dbx3:
IF DATABASE IN (dbx1,dbx3) ESTIMATE < 40 THEN SET SHORT
You can use scheduler rules to set SQB flags to true or false based on
which tables the plans access. For example, the following scheduler rules
sets the SQB flag to true for all plans that access the table tab1:
IF TABLE IS tab1 THEN SET SHORT
Custom tags
to set SQB flags to true or false based on these tags. For example, the
following scheduler rule sets the SQB flag of a plan to false based on
whether one or more of the specified tags have been set for the plan:

IF TAG IN (eod,eom,eoy) THEN SET NOT SHORT
Figure 15-7 illustrates the queues and settings used for SQB. In this example:
v The GRA scheduler reserves 10 slots for short queries.
v The snippet scheduler reserves 6 slots for short queries.
v The SPU reserves 50 MB for short query execution.
v The Netezza host reserves 64 MB for short query execution.
Figure 15-7. SQB queuing and priority
A Netezza host
B GRA scheduler
C Snippet scheduler
D Snippet processing unit (SPU)
Priority query execution (PQE)

Within each resource group, use priority query execution (PQE) settings to
prioritize more important jobs over less important jobs. A job's priority is used as a
weighting factor to allocate resources for its corresponding plans.
When you use PQE:

v For running jobs, the system assigns more resources to higher priority jobs.
v For jobs that are waiting to run, the system schedules higher priority jobs to run
before lower priority jobs.
Related concepts:
“Specifying priorities” on page 15-26
When a user opens a database session, that session is assigned a priority. The
session priority determines the priority of all jobs that are submitted during the
session. For example, if a session is assigned the priority HIGH, all jobs submitted
during that session also have the priority HIGH, as will their corresponding plans.

Priority levels
Each job can have one of the following priority levels:
Critical
Highest priority user jobs.
High High priority user jobs.
Normal
Normal priority user jobs.
Low Low priority user jobs such as background loads and jobs that should not
affect other activity.
Note: There are two additional priorities, but these are used exclusively by internal
processes and are not visible to and cannot be set by users:
System critical
This priority is ranked higher than critical.
System background
This priority is ranked lower than low.
Priority weighting and resource allocation

Priorities are used as weighting factors to allocate resources for plans.
Similar to the way the system allocates resources among resource groups based on
their GRA resource minimums, the system allocates resources among the plans in a
resource group based on their priorities. The fraction of the resource group's
resources that are made available to a plan are weighted based on the priority of
the corresponding job:
v Low priority plans have a weight of 1
v Normal priority plans have a weight of 2
v High priority plans have a weight of 4
v Critical priority plans have a weight of 8
Figure 15-8 on page 15-26 illustrates an example of how job priority affects the
distribution of resources within resource groups. In this example, the system uses
the default weighting setting of 1,2,4,8.

Figure 15-8. GRA and priority
Legend:
C Plan for a critical job.
H Plan for a high priority job.
L Plan for a kow priority job.
N Plan for a normal priority job.
Table 15-4. Example of a distribution of resources within resource groups
Per resource group Per plan
Resource Net system Job priority
group resources (weight) Resource group resources Net system resources
Analysts 50% Normal (2) 2÷(8+2) = 20% 50% × 20% = 10%
Critical (8) 8÷(8+2) = 80% 50% × 80% = 40%
RptQuery 30% High (4) 4÷(8+4+4) = 25% 30% × 25% = 7.5%
High (4) 4÷(8+4+4) = 25% 30% × 25% = 7.5%
Critical (8) 8÷(8+4+4) = 50% 30% × 50% = 15%
Public 20% Low (1) 1÷(1+1) = 50% 20% × 50% = 10%
Low (1) 1÷(1+1) = 50% 20% × 50% = 10%
Specifying priorities
When a user opens a database session, that session is assigned a priority. The
session priority determines the priority of all jobs that are submitted during the
session. For example, if a session is assigned the priority HIGH, all jobs submitted
during that session also have the priority HIGH, as will their corresponding plans.
The priority of a particular session (and its jobs and their plans) is determined by
several factors:
v System settings
v Settings for the user who submitted the corresponding job
v Settings for the user groups to which that user belongs, if any
v Settings for the session used to submit the corresponding job

In addition, scheduler rules can change plan priorities when certain conditions are
satisfied by the attributes of the corresponding job.
The following settings determine the default and maximum priorities for a session:
v Issue the SET SYSTEM DEFAULT command to set the following parameters:
DEFPRIORITY
The system default priority, which is the priority that is assigned to any
job for which a priority is not set by other means. The default is
NORMAL.
MAXPRIORITY
The system maximum priority, which is the highest level priority that
can be set for any job. The default is CRITICAL.
v For each user, you can issue the CREATE USER or ALTER USER command to
set the following parameters:
DEFPRIORITY
The user's default priority, which is the priority that is assigned to any
job that is submitted by the user.
MAXPRIORITY
The user's maximum priority, which is the highest level priority that the
user can set for any submitted job.
v For each user group, you can issue the CREATE GROUP or ALTER GROUP
command to set the following parameters:
DEFPRIORITY
The group's default priority, which is the priority that is assigned to any
job that is submitted by a member of the user group.
MAXPRIORITY
The group's maximum priority, which is the highest level priority that a
member of the user group can set for any submitted job.
The first of the following rules to apply determines which priority is assigned to a
session:
1. Was a default priority other than NONE assigned to the user? If so, that
priority is assigned to the session.
2. Is the user a member of at least one user group for which a default priority
other than NONE was specified? If so, the lowest of those default priorities is
assigned to the session.
3. The system default priority is assigned to the session.
If the determined priority would exceed the maximum priority for the user, the
maximum priority is assigned instead. The first of the following rules to apply
determines the maximum priority for a particular user:
1. Was a maximum priority other than NONE assigned to the user? If so, that
priority or the system maximum priority, whichever is lower, is the user's
maximum.
2. Is the user a member of at least one user group for which a maximum priority
other than NONE was specified? If so, the lowest of those default priorities and
of the system maximum priority is the user's maximum.
A user can issue the ALTER SESSION command to change the session priority.
This affects all jobs that are currently running and that are submitted during the
remainder of the session.

In addition, a scheduler rule can change the priority of the plans of a job when
certain conditions are met. The priority that is set by a scheduler rule is not subject
to any of the maximum-priority restrictions that are imposed upon a particular
user or user group, or by the system maximum priority. You can create scheduler
rules that use any combination of the following criteria to override the priority
determined by other means:
Which user submitted the corresponding job
You can use scheduler rules to override a plan's priority assignment based
on the submitting user. For example, the following scheduler rule sets the
priority of all plans for jobs submitted by the user bob to CRITICAL,
regardless of any priority restrictions imposed upon bob directly, by means
of a user group, or by the system maximum priority:
IF USER IS bob THEN SET PRIORITY CRITICAL
User ID
Application name
Workstation name
Accounting string
You can use scheduler rules to assign a priority based on the contents of
these fields (see “Client information” on page 15-7). For example, the
following scheduler rule increases the priority of all plans for jobs
submitted by the application named Cognos:
IF CLIENT_APPLICATION_NAME IS Cognos THEN INCREASE PRIORITY
Cost estimates
For each plan, the optimizer calculates the expected cost of processing that
plan. You can use scheduler rules to assign a priority based on the
calculated cost estimate. For example, the following scheduler rules modify
plans' priorities based on the plans' cost estimates:
IF ESTIMATE < 4 THEN SET PRIORITY NORMAL
IF ESTIMATE >= 4 ESTIMATE < 30 THEN SET PRIORITY HIGH
IF ESTIMATE >= 30 THEN SET PRIORITY LOW
You can use scheduler rules to assign or change plan priorities based on
which database each plan accesses. For example, the following scheduler
rules decreases the priority of all plans that access database dbx1:
IF DATABASE IS dbx1 THEN DECREASE PRIORITY
You can use scheduler rules to assign or change plan priorities based on
which table each plans accesses. For example, the following scheduler rule
decreases the priority of all plans that access table tab1 or tab2:
IF TABLE IN (tab1,tab2) THEN THEN DECREASE PRIORITY

Custom tags
to assign or change plan priorities based on these tags. For example, the
following scheduler rule increases the priority of all plans for which the
specified tags have been set:
IF TAG IS eom THEN INCREASE PRIORITY
Important: Use caution when you are assigning the critical and high priority. If
you assign too many jobs to the high or critical priority, you can bring normal and
low priority work to a standstill.
Related concepts:
“Priority query execution (PQE)” on page 15-24
Within each resource group, use priority query execution (PQE) settings to
prioritize more important jobs over less important jobs. A job's priority is used as a
weighting factor to allocate resources for its corresponding plans.
Changing the priority of all jobs in a session

The admin user and users with the Manage System privilege can set the priorities
of all jobs in a session to a single priority.
For example, to change the priority of all jobs of the session with the ID 21664 to
HIGH:
v By issuing the nzsession priority command, enter:
nzsession priority -high -u user -pw password -id 21664
v By issuing the ALTER SESSION command, enter:
MYDB.SCHEMA(USER)=> ALTER SESSION 21664 SET PRIORITY TO HIGH;
v By using the NzAdmin tool, display the Database > Sessions list, right-click
session ID 21664 and select Change Priority > High.
Use the nzsession show command or the NzAdmin tool to show information about
the current sessions and their priorities.

Chapter 16. Netezza statistics
The nzstats command displays operational statistics about system capacity, faults,
and performance. Operational statistics provide you with a high-level overview of
how your system is running in a context of recent system activity. Also, operational
statistics provide details so that you can diagnose problems, understand
performance characteristics, and interface to system management software.
Netezza stats tables

You can use the nzstats command to view sets of related operational information.
These sets are organized as groups of related statistics or tables that contain rows
of related statistics.
Note: The terms group and table are based on Simple Network Management
Protocol (SNMP) concepts and are not associated with IBM Netezza database
groups or tables.
The following table lists the Netezza core groups and tables that you can view by
using the nzstats command.
Table 16-1. Netezza Groups and Tables
Group/Table Description See
Database Table Provides information about “Database Table” on page 16-2.
databases.
DBMS Group Provides information about the “DBMS Group” on page 16-2.
database server.
Host CPU Table Provides information about each “Host CPU Table” on page 16-3.
host processor.
Host Filesystem Provides information about each “Host File System Table” on page
Table local host file system. 16-3.
Host Interface Provides information about the “Host Interface Table” on page
Table host's interface. 16-4.
Host Mgmt Provides information about the “Host Mgmt Channel Table” on
Channel Table system's management channel page 16-4.
from the host viewpoint.
Host Network Provides information about the “Host Network Table” on page
Table system's main UDP network layer 16-5.
from the host viewpoint.
Host Table Provides information about each “Host Table” on page 16-6.
host.
HW Mgmt Provides information about each “Hardware Management Channel
Channel Table SPU management channel from Table” on page 16-7
the SPU's viewpoint.
Per Table Per Data Provides information about tables “Per Table Per Data Slice Table”
Slice Table on a per-data slice basis. on page 16-8.
Query Table Provides information about active “Query Table” on page 16-8.
queries as obtained from the
_v_qrystat view.

Table 16-1. Netezza Groups and Tables (continued)
Group/Table Description See
Query History Provides a list of the last 2000 “Query History Table” on page
Table queries that completed as 16-9.
recorded in the _v_qryhist view.
SPU Partition Table Provides information about a “SPU Partition Table” on page
SPU's disk partitions. 16-10.
SPU Table Provides information about each “SPU Table” on page 16-10.
SPU's memory.
System Group Provides information about the “System Group” on page 16-10.
system as a whole.
Table Table Provides information about “Table Table” on page 16-11.
database tables and views.
Database Table
If you are the user admin, you can use the nzstats command to display the
Database Table, which displays information about the databases.
The Database Table has the following columns:

Table 16-2. Database Table
Column Description
DB Id A unique value for each DBMS database.
DB Name The name of the database.
Create Date The date and time this database was created.
Owner Id The user ID for the user that owns this database.
Num Tables The number of user tables that are associated with this database.
Num Views The number of user views that are associated with this database.
Num Active Users The number of users that are currently attached to this database.
DBMS Group
The DBMS Group displays information about the database server.
The DBMS Group has the following columns:

Table 16-3. DBMS Group
Column Description
Num Databases The total number of user databases.
Num Groups The total number of groups.
Num Users The total number of database users.
Num Schemas The total number of schemas in the database.
Num Tables The total number of user tables.
Num Views The total number of user views.
Num SQL Sessions The total number of current SQL sessions/connections.
Num Queries The total number of queries that have been submitted, but not
completed.

Table 16-3. DBMS Group (continued)
Column Description
Num Queries Running The total number of currently running queries.
Num Queries Waiting The total number of currently queries waiting to be run.
Num Transactions The total number of open and recent transactions that are
maintained by the Transaction Manager.
Host CPU Table

The Host CPU Table displays information about each host's processors.
The Host CPU Table has the following columns:

Table 16-4. Host CPU Table
Column Description
Host ID The index into the host table.
CPU ID A unique value for each CPU within a host.
Ticks The number of CPU ticks that have occurred. A tick is 1/100th of a
second. Linux uses the term jiffy for this amount of time.
Idle Ticks The number of ticks where the CPU is not doing anything (that is,
running the idle task).
Non-idle Ticks Non-idle ticks represent time that the CPU is either in user or system
mode.
Avg Load The average, as calculated over the last minute, of the utilization
percentage for the processor. Commands such as top show the average
utilization for shorter periods of time, such as only the last three
seconds.
Host File System Table

The Host File System Table displays information about each local host file system.
The Host File System Table has the following columns:

Table 16-5. Host File System Table
Column Description
Host ID The index into the host table. Always 1.
FS ID A unique value for each local file system within a host.
Device Name The name of the file system's device.
Mount Point The directory name on which the file system is mounted.
Space The total size in KB.
Free Space The amount of free space in KB.
Used Space The amount of used space in KB.
% Used Space The percentage of used space.
Chapter 16. Netezza statistics 16-3

Host Interface Table
The Host Interface Table displays information about the host's physical interfaces.
Host Interface Table has the following columns:

Table 16-6. Host Interfaces Table
Column Description
If ID A unique value for each interface within a host.
Name The operating system name for the interface (eth1).
State The current state of the host interface. Up is 1 and down is 2.
State Text The textual description of the interface state.
MTU The size of the largest datagram that can be sent or received on the
interface, which is specified in bytes.
MAC Address The interface address at the protocol layer immediately below the
network layer in the protocol stack.
IP Address The interface IP address.
In Bytes The total number of bytes received on the interface, including framing
characters.
In Bytes-64 A 64-bit version of the In Bytes managed object, which is updated every
15 seconds.
In Byte Rate The previous 1-minute average rate of bytes received (15-seconds
granularity).
In Pkts The total number of packets that are received on the interface.
In Pkt Rate The previous 1-minute average rate of packets received (15-seconds
granularity).
In Errors The number of inbound packets that contain errors that prevent them
from being delivered to a higher-layer protocol.
Out Bytes The total number of bytes transmitted out of the interface, including
framing characters.
Out Bytes-64 A 64-bit version of the Out Bytes managed object, which is updated
every 15 seconds.
Out Byte Rate The previous 1-minute average rate of bytes sent (15-seconds
granularity).
Out Pkts The total number of packets that are sent on the interface.
Out Pkt Rate The previous 1-minute average rate of packets sent (15-seconds
granularity).
Out Errors The number of outbound packets that cannot be transmitted because of
errors.
Host Mgmt Channel Table

The Host Mgmt Channel Table displays information about the system's
management channel from the host's viewpoint.
Host Mgmt Channel Table has the following columns:

Table 16-7. Host Management Channel Table
Column Description
Host ID The index into the host table. Always 1.
In Bytes The total number of bytes received.
In Bytes-64 A 64-bit version of the In Bytes managed object, which is
updated every 15 seconds.
granularity).
In Pkts The total number of packets received.
In Acks The total number of ACK packets received.
In Msgs The total number of messages received.
In Msg Rate The previous 1-minute average rate of messages received
(15-seconds granularity).
In Msg Q Len The length of the receive packet queue for messages that are
being assembled.
In Errors The number of inbound errors encountered.
Out Bytes The total number of bytes sent.
Out Bytes-64 A 64-bit version of the Out Bytes managed object, which is
granularity).
Out Pkts The total number of packets sent.
Out Unicasts The total number of unicast packets sent.
Out Broadcasts The total number of broadcast packets sent.
Out Acks The total number of ACK packets sent.
Out Msgs The total number of messages sent.
Out Msg Rate The previous 1-minute average rate of messages sent (15-seconds
granularity).
Out Msg Q Len The length of the send packet queue.
Out Errors The number of outbound errors encountered.
Out Retransmits The total number of outbound retransmissions.
Out Retransmit Rate The previous 1-minute average rate of retransmissions
Out Retransmit Q Len The number of entries in the retransmit queue.
Host Network Table

The Host Network Table displays information about the system's UDP network
layer from the host's viewpoint.
Host Network Table has the following columns:

Table 16-8. Host Network Table
Columns Description
In Bytes-64 A 64-bit version of In bytes, updated every 15 seconds.

Table 16-8. Host Network Table (continued)
Columns Description
In Byte Rate The previous 1-minute average rate of bytes received
granularity).
Out Msg Rate The previous 1-minute average rate of messages sent
Out Retransmit Q Len The number of entries in the retransmit queue.
Host Table
The Host Table displays information about each host on the system.
The Host Table has the following columns:

Table 16-9. Host Table
Column Description
Host ID A unique value for each host in the system (always 1).
OS Type The type of the host's operating system (Linux).
OS Version The version of the Linux operating system on the host.
Num CPUs The number of processors in the host.
Num File Systems The number of file systems in the host.
Swap Space The total swap size in KB.
Free Swap Space The amount of free swap space in KB.
Used Swap Space The amount of used swap space in KB.
% Used Swap Space The percent of used disk space.
Real Memory The total real memory in KB.
Free Real Memory The amount of free real memory in KB.
Used Real Memory The amount of used real memory in KB.

Table 16-9. Host Table (continued)
Column Description
% Used Real Memory The percent of used real memory.
Shared Memory The total shared memory in KB.
Free Shared Memory The amount of free shared memory in KB.
Used Shared Memory The amount of used shared memory in KB.
% Used Shared Memory The percent of used shared memory.
Hardware Management Channel Table

The Hardware Management Channel Table displays information about the system
management channel from the viewpoint of each SPU.
Hardware Management Channel Table has the following columns:

Table 16-10. Hardware Management Channel Table
Column Description
HW ID The index into the hardware inventory table
In Bytes-64 A 64-bit version of In Bytes, updated every 15 seconds.
granularity).
In Acks The total number of ACK packets received.
In Msg Q Len The length of the receive packet queue for messages that are
being assembled.
granularity).
Out Acks The total number of ACK packets sent.
Out Msg Rate The previous 1-minute average rate of messages sent (15-seconds
granularity).
Out Msg Q Len The length of the send packet queue.

Table 16-10. Hardware Management Channel Table (continued)
Column Description
Out Retransmit Q Len The number of entries in the transmit queue.
Per Table Per Data Slice Table

The Per Table Per Data Slice Table displays information about tables on a per-data
slice basis.
Per Table Per Data Slice Table has the following columns.
Table 16-11. Per Table Data Slice Table
Column Description
Table Id The ID corresponding to a table.
DS Id The ID corresponding to a data slice.
Disk Space The amount of disk space that is used for this table in this data slice.
Query Table
If you are the admin user, you can use the nzstats command to display the Query
Table, which displays information about the queries currently 'running/executing'
on the IBM Netezza server. Those queries which have completed execution and
whose results sets are being returned to a client user are not listed in this table.
You can use the system view _v_qrystat to view the status of queries that are
running. For more information, see Table 12-8 on page 12-30.
This query table uses the _v_qrystat view for compatibility with an earlier release
and will be deprecated in a future release. For more information, see Chapter 14,
“History data collection,” on page 14-1.
The Query Table has the following columns:

Table 16-12. Query Table
Column Description
Query Id The ID of the query.
Client Id The internal client ID associated with the query's session.
Client IP Addr The client's IP address.
SQL Statement The SQL statement. You can see the entire string by increasing the
width of the column.
State The state of the query in integer form.
State Text The state of the query in text form. Possible states are pending,
queued, running.
Submit Date The date and time that the query was submitted.
Start Date The date and time that the query started running.
Elapsed Time The estimated elapsed time, as determined by the optimizer.

Table 16-12. Query Table (continued)
Column Description
Priority Text The priority text string.
Estimated Cost The estimated seconds, as determined by the optimizer.
Estimated Disk The estimated disk usage, as determined by the optimizer.
Estimated Memory The estimated memory usage, as determined by the optimizer.
Snippets The number of snippets (steps) in the plan for this query.
Snippets Done The number of snippets that have finished.
Snippets Done Pct The percentage of snippets that have finished.
Result Rows The number of rows in the result.
Result Bytes The number of bytes in the result.
Query History Table

If you are the user admin, you can use the nzstats command to display the Query
History Table, which displays information about the last 15000 completed queries.
You can use the system view _v_qryhist to view recent history data. For more
information, see Table 12-9 on page 12-31.
The Query History Table uses the _v_qrystat view for compatibility with an earlier
release and will be deprecated in a future release. For more information, see
Chapter 14, “History data collection,” on page 14-1.
The Query History Table has the following columns:

Table 16-13. Query History Table
Column Description
Query Id The ID of the query.
Plan Id The internal ID of the plan that is associated with this query
Client ID The internal client ID associated with the query's session.
Db Id The database ID from which this query is running.
User Id The user name.
Client IP Addr The client IP address.
SQL Statement The SQL statement. You can see the entire string by increasing the
width of the column.
Submit Date The date and time that the query was submitted.
Start Date The date and time that the query started running.
End Date The date and time that the query completed.
Elapsed Time The estimated elapsed time, as determined by the optimizer.
Priority Text The priority text string.
Estimated Cost The estimated seconds, as determined by the optimizer.
Estimated Disk The estimated disk usage, as determined by the optimizer.
Estimated Mem The estimated memory usage, as determined by the optimizer.

Table 16-13. Query History Table (continued)
Column Description
Snippets The number of snippets (steps) in the plan for this query.
Snippets Done The number of snippets processed.
Result Rows The number of rows in the result.
Result Bytes The number of bytes in the result.
SPU Partition Table

The SPU Partition Table displays information about the SPU's disk partitions.
SPU Partition Table has the following columns:

Table 16-14. SPU Partition Table
Column Description
HW ID The index into the hardware table for the SPU containing this partition.
Partition Id A unique value (per SPU) for each disk partition within a SPU.
Disk Id The index into the SPU disk table for the disk on which this partition
resides.
Type The type of the partition (core, swap, primary, secondary).
Type Text A description of the partition.
Space The total partition size in KB.
Free Space The amount of free partition space in KB.
Used Space The amount of used partition space in KB.
% Used Space The percent of used partition space.
SPU Table
The SPU Table displays information about each SPU's processor and memory.
The SPU Table has the following columns:

Table 16-15. SPU Table
Column Description
HW ID The index into the hardware inventory table.
Memory The total memory in KB.
Free Memory The amount of free memory in KB.
Used Memory The amount of used memory in KB.
% Used Memory The percent of used memory.
System Group
The System Group displays information about the system as a whole.
The System Group has the following columns:

Table 16-16. System Group
Column Description
Name The administrator-assigned name of the system.
Description A description of the system.
Contact The name of the contact person for this system and contact
information.
Location The physical location of this node (for example, “telephone closet,
3rd floor.”)
IP Addr The primary IP address of the system.
Up Time The time in seconds since the management portion of the system
was last reinitialized.
Up Time Text The up time as a text value in minutes and seconds.
Date The system's local date and time of day.
State The current state of the system (from the nzstate command) as an
integer.
State Text The text description of the system state. This matches the display
from the nzstate command.
Model The IBM Netezza model number for this system. Used in the
callHome.txt file.
Serial Num The serial number for this system. Used in the callHome.txt file.
Num Data Slices The number of data slices.
Num SFIs Usually 0. (SFIs are a component in the legacy Netezza z-series
systems.)
Num SPUs The number of SPUs.
Num Failovers The number of failover tasks that are running.
Num Regen Tasks The number of regeneration tasks that are running.
Table Table
If you are the user admin, you can use the nzstats command to display the Table
Table, which displays information about database tables.
The Table Table has the following columns:

Table 16-17. Table Table
Column Description
DB ld The ID corresponding to the database for this table.
DB Name The name of the database.
Table Id A unique value for this table.
Table Name The name of this table.
Table Display Name The display name of this table.
Create Date The date and time that this table was created.
Type The type of this table (table, view) expressed as its type integer.
Num Columns The number of table columns.
Row Size The length of a table row.

Table 16-17. Table Table (continued)
Column Description
Disk Space The total disk space that is used to store this table in KB. You can
use the -allocationUnit option to show the disk space that is used
in extents or blocks.
Avg Space Per DS The average disk space that is used by each dataslice of the table in
KB.
Max Space Per DS The disk space that is used by the largest dataslice for the table in
KB.
Max Space DS Id The ID of the largest data slice.
Min Space Per DS The disk space that is used by the smallest dataslice for the table in
KB.
Min Space DS Id The ID of the smallest data slice.
Space Skew The ratio that shows how disparate the dataslice sizes are as
calculated by (maximum dataslice size - minimum dataslice size) /
average dataslice size.
System statistics
The nzstats command displays operational statistics about system capacity, system
faults, and system performance. They provide you with a high-level overview of
how your system is running and other details so that you can understand
performance characteristics. You can also use the NzAdmin tool to display
statistics.
The nzstats command

You can use the nzstats command to display the group and statistics tables. You
must be the user admin or have Manage System privileges to view IBM Netezza
statistics. You must also be the user admin to view the Database, Table, and the
Query tables.
Display table types and fields

You can use the nzstats command to display the group and table types. You can
also use the command to display specific fields within a group or table.
v To list the tables, enter:
nzstats listTypes
v To display specific fields of a table, enter:
nzstats listFields -type dataslice
Display a specific table

You can use the nzstats command to display the statistics of a specific group or
table.
To display the System Group table, enter: nzstats show -type system
The information in the output is obtained from the /nz/data/config/callHome.txt

file. If that file is not customized for your IBM Netezza system, the command
output might contain general placeholder text.
Related concepts:
“Callhome file” on page 5-19

Chapter 17. System Health Check tool
Netezza System Health Check tool is used to discover those issues in the system,
which might slow down the performance or result in system outage. The tool finds
the root cause of the problem, analyzes it, and suggests solution.
This documentation applies to System Health Check version 2.3.1.
This tool is installed together with the NPS software kit in the
/nz/kit/share/healthcheck folder. The tool is integrated with the failover and
upgrade processes.
The tool provides a daemon, which is a service that runs in the background. The
daemon can function in two different modes that define how it works. Regardless
of the mode, when you run the nzhealthcheck command, the daemon will produce
a health check report. The report generation may take up to several minutes.
The tool is based on a set of policy rules. The policy rules cover the most frequent
issues that were found by the support teams in the field. Based on these rules,
automatic analysis of the system health is performed, and a possible solution for
recovery is suggested.
Regardless of the mode in which the daemon works, you can run the
nzhealthcheck command which:
v Opens the monitoring database.
v Collects the most recent data from the system components.
v Requests the evaluation of rules.
v Generates and prints the Health Check Report.
Tool versioning
This topic lists all versions of the System Health Check tool and the corresponding
supported versions of NPS.
Table 17-1. Health check tool versions and the corresponding supported NPS versions
Health check tool version Supported NPS version
1.0 v 5.0.10 P19
v 6.0 P13
v 6.0.3 P9
v 6.0.5 P10
v 6.0.8 P1
1.1 v 5.0.10 P19
v 6.0 P13
v 6.0.3 P11
v 6.0.5 P12
v 6.0.8 P2
v 7.0 P1
1.2 v 6.0.5 P14

Table 17-1. Health check tool versions and the corresponding supported NPS
versions (continued)
Health check tool version Supported NPS version
1.2.1 v 5.0.10 P19
v 6.0 P13
v 6.0.3 P13
v 6.0.5 P15
v 6.0.8 P4
v 7.0 P2
v 7.0.2
2.0 v 6.0.8 P7
v 7.0 P6
v 7.0.2 P4
v 7.0.3 P1
2.1 v 6.0.8.P11
v 7.0.P10
v 7.0.2.P6
v 7.0.2.P7
v 7.0.4
2.2 v 6.0.8.15P1
v 7.0.2.11P1
v 7.0.4.3P1
v 7.1
2.3 v 7.1.0.4
v 7.2
Policy rules
Policy rules are troubleshooting rules that are used for automatic analysis of
system health and for proposing a relevant solution. These rules cover the most
frequent issues that are experienced in the field.
You can view a complete list of rules in a PDF document that is located on your
system in /nz/kit/share/nzhealthcheck/rules-doc.pdf.
Note: Rule evaluation depends on the platform, so not all rules may be evaluated
on your system. The rules-doc.pdf document provides detailed information about
which platforms are supported by particular rules.
All System Health Check rules provide problem description and advice. Some of
them involve complex logic, for example, identifying the correct
disk/SPU/enclosure balance. The rules may depend on one another.
All rules have severity assigned:

v High - Actionable issues that might be critical.
v Medium - Actionable issues.
v Low - The rules may help in problem investigation but they do not require
immediate action.

Rules have the following classification:
BOM/BOX
Rules verifying the existence of hardware components based on model.
DM Rules examining disk health. These rules are based on the disk_monitor
tool.
SHC General-purpose rules.
INT Internal rules. They verify that the heath check tool works properly, and
that the device managers do not return errors. Problems reported through
INT001 - One or more device manager failed might denote system
problems and they need to be verified. The health check report containing
such errors may not be complete as the tool is not able to verify all
possible problems.
Daemon modes
The System Health Check daemon can run in two different modes, depending on
how you want to use it.
Diagnostic
The System Health Check daemon by default runs in this mode. In this mode,
system data is collected only after you run the nzhealthcheck command and then
the rules are evaluated using this data. The advantage of the diagnostic mode is
that it produces no background workload because it does not collect any data in
the background.
You can run nzhealthcheck -I at any time to check in which of the modes the
daemon is running:
nzhealthcheck -I
Daemon status: active
Daemon mode: diagnostic
To switch back from the monitoring to the diagnostic mode, run nzhealthcheck -D.
Monitoring
Run the nzhealthcheck -M command to restart the daemon and switch it to the
monitoring mode. In this mode, data is constantly gathered in the background and
the rules are evaluated periodically.
When the daemon runs in the monitoring mode, it only evaluates the automatic
rules. Refer to the rules-doc.pdf document for information about which of the rules
are evaluated automatically and which are evaluated manually.
Note: When you run the nzhealthcheck command, both the automatic and manual
rules are processed, regardless of the mode in which the daemon runs.
The monitoring mode allows for enabling automatic notifications. See “Enabling
automatic notifications” on page 17-5.
Some rules are automatically integrated with the callhome service when the
daemon runs in this mode. See “Integration with the callhome service” on page
17-7.
Chapter 17. System Health Check tool 17-3

You can run nzhealthcheck -I at any time to check in which of the modes the
daemon is running:
nzhealthcheck -I
Daemon mode: monitoring
Using the health check tool

The system health check monitoring daemon is started automatically at system
startup. By default, it runs in the diagnostic mode and has no influence on the use
of resources. Regardless of the mode in which the tool works, you can run the
nzhealthcheck command at any time to generate a report on system health.
Running and analyzing the health check report

You run the nzhealthcheck command to view the system health check report.
When running the command, the Netezza system can be in any operational state.
Procedure
1. Log in as nz user.
2. Run the following command:
nzhealthcheck
No additional parameters are required.
Results
The output of the command presents general system information in the section
MINI SYSINFO and information about the issues found in the section Failures. It
may also contain a Non-failed section that informs about the rules that could not be
evaluated because of the lack of data. At the end of the report, you can find a path
to the text file that contains the full version of the health check report. You should
review this file every time you generate the report as it helps you perform the
following actions:
v In the section ISSUES, identify the failed components and find guidance on how
to solve them.
v In the section WARNINGS, identify all observed problems with rules evaluation,
for example lack of data, but also other problems, not listed in the command
output.
You can run the command with the -a parameter to invoke the output with all the
evaluated rules, including the Passed ones.
Sample output:
Netezza System Health Check 2.3
Preparing System Health Check Report
************************************************************************
********************** System Health Check Report **********************
************************************************************************
Report generation date: 2013-12-19 10:00:40

***************************** MINI SYSINFO *****************************

+ Product : IBM PureData System for Analytics N1001-010
+ Model : P100_A
+ HPF : 5.2
+ FDT : 2.6
+ NPS : 6.0.8.15-P1 [Build 34509]
+ NPS State : online
+ Online since: 2013-12-19 08:44:47
+ MTM(s) : MTM has not been set
+ NzId : NZ80826
+ NZ Owner : nz
+ OS : Red Hat Enterprise Linux Server release 5.5 (Tikanga)
+ Kernel : 2.6.18-194.26.1.el5
+ HealthCheck : 2.2 [20131218101238]
+ Hostname : NZ80826-H1
+ Up Time : 1 hr, 24 mins, 19 secs
+ Host Up Time: rack1.host1 : 25 days 22 hours 16 minutes 25 seconds
+ Host Up Time: rack1.host2 : 25 days 22 hours 15 minutes 11 seconds
+ CallHome : No address information
Failures (4):
L +- Rule --+-------- Issue ---------+---- Component ----+- Severity --
2 | BOM001 | Missing or incorrectly | rack1.chass (...) | High
| | inserted chassis | rack1.chass (...) |
| | component | |
2 | SHC012b | Not enough disk space | rack1.host1 (...) | High
| | on host | |
2 | SHC060 | Serial-Over-LAN is not | ...output omitted | High
2 | SHC012a | Not enough disk space | rack1.host1.fs[/] | Medium
| | on host | rack1.host1 (...) |
L +- Rule --+-------- Issue ---------+---- Component ----+- Severity --
Report stored in
/nz/kit.6.0.8.15-P1/log/nzhealthcheck/Netezza_System_Health_Check_Report_20131219_100040.txt
All done
What to do next
Analyze the issues that are reported:

1. Open the text report to view problem description and expert's advice.
2. Try to solve the problem as described in the advice.
3. If the advice is to contact support, send the report to IBM support. You can also
run the sysinfo command as described in “Running the sysinfo report” on
page 17-7 and attach the report returned by the command as well. Do not try
to fix the problem yourself, unless you are completely sure that you know how
to resolve the issue.
Note: If any INT001 issues are included in the report, the report might be
incomplete. For more information, see “Policy rules” on page 17-2
Enabling automatic notifications

You can integrate the System Health Check tool with the NPS nzevent functionality
to set up automatic notifications about problems.

Before you begin
1. To enable sending automatic emails, you must first make sure that the
/nz/data/config/sendMail.cfg file is updated with the current information
regarding your email server. For details, see “Set up the sendMail.cfg File” on
page 9-6.
2. This kind of configuration is only valid if the System Health Check daemon is
working in the monitoring mode. If the daemon is set to diagnostic mode,
notifications will not be sent, even if you properly enable them. If you
configure the notifications in the diagnostic mode, there is no need to configure
them again when switching to monitoring.
Remember: Only automatic rules are evaluated in the monitoring mode. Refer to
the rules-doc.pdf document for information about which of the rules are
evaluated automatically and which are evaluated manually.
About this task
nzevent is a tool which you can configure to receive notifications about the system
state. You can create and manage rules which then trigger sending notifications.
Procedure
1. Log in to your system as the nz user.
2. Run nzhealthcheck -I to make sure that the daemon is running in monitoring
mode:
nzhealthcheck -I
Daemon mode: monitoring
3. To enable notifications from the System Health Check tool, you must create a
custom event rule related to ShcReport:
nzevent add -eventType custom1 -name nzhealthcheck_event -notifyType email -dst <your@address>
-bodyText ’Nzhealthcheck rule triggered on $HOST $body’ -msg ’Nzhealthcheck found problem on $HOST’
-eventArgsExpr ’$originated==ShcReport’
For the notifications to be sent, the daemon must run for at least ten minutes.
By this time, a sufficient amount of data is collected and processed.
4. Optional: Edit the /nz/kit/share/nzhealthcheck/nzhealthcheck.cfg file to
configure the notification settings. Set the EVENTING_MODE parameter to one of
the following values:
EVENT
This is the default value. The notification is sent to the specified address
immediately after a problem is detected by the daemon. The email contains
a list of all failed components, excluding the ones that were already
reported in previous emails. It also includes a newly generated event
report. If the system is unable to send the notification immediately after the
problem is detected, it will reattempt to send it within an hour.
TIME
The notification is sent once a day, at a time specified in the
EVENTING_REPORT_TIME parameter. The time format must be specified as
hh:mm and the default value is 15:00. The notification contains a list of all

failed components and a full System Health Check report. If the system is
unable to send the notification, it will generate a new email at the specified
time on the next day.
Results
The notifications are now enabled and will be sent to the specified email address.
Integration with the callhome service

If the NPS callhome functionality is properly configured on your system, it is
automatically extended to the System Health Check tool.
Refer to the “Enable the callhome service” on page 9-8 section for information
about how to set up the callhome service in your system.
When callhome is enabled, three of the System Health Check rules are
automatically integrated with it. When problems related to these rules are detected,
IBM Netezza Support will be notified. The rules are:
v DM012 : Multiple SCSI Log page 0x15 events on disk head
v DM015 : Multiple SCSI Log page 0x15 events on disk
v DM030 : Bad sectors on disk
The callhome functionality requires the System Health Check daemon to work in
the monitoring mode. It is not necessary to enable automatic email notifications in
System Health Check for callhome to work properly.
Running the sysinfo report

You can run the sysinfo command to generate an additional report on the state of
the system. The sysinfo report contains data that is not evaluated by the system
health check tool, but the data might be of help to a system administrator who is
analyzing issues in the system.
Procedure
1. Log on as the nz user.
2. Run the command nzhealthcheck sysinfo.
Results
The output of the command is displayed on-screen, including a link to a full txt
report.
Sample output:
Netezza System Health Check 2.3
Collecting monitoring data
Preparing SysInfo Report
- Frontend Hosts Utilization and Statistics

--- Host DIMMs
--- Host Fans
--- Host Power
--- Host Power Supply
--- Host SAS Controllers
--- Host SAS Controllers Batteries

--- Host Disks
--- Host CPU Utilization
--- Host Memory Utilization
--- Host Network Interfaces Configuration
--- Host Network Interfaces - RX Stats
--- Host Network Interfaces - TX Stats
--- Host Cluster State
--- crmnode
--- drbd
--- Host Filesystem Utilization
--- Host Timeshift
--- Host Uptime
--- Host System
- Open files on host
- Chassis Network Subsystem State and Usage Statistics
--- Ports Configuration
--- Ports RX Stats
--- Ports TX Stats
--- Management Ports
- Management Network Subsystem State and Usage Statistics
--- Ports Configuration
--- Ports RX Stats
--- Ports TX Stats
--- Management Ports
- Chassis Components Configuration and State
--- Overall System Status
--- Blades
--- MMs
--- Fans
--- Blowers
--- PWRs
- Blade detailed configuration and usage statistics
--- CPU Information
--- Memory Usage (all values in kB)
--- Network Interfaces Configuration
--- Network Interfaces - RX Stats
--- Network Interfaces - TX Stats
--- SDR (reported via ipmitool)
- RPC and Outlets Configuration
- NPS SPUs
- NPS DACs
- NPS FPGAs
- Section Disk Enclosures
--- Disk Enclosure Slots
--- Disk Enclosure Fans
--- Disk Enclosure Management Modules
--- Disk Enclosure Power Units
--- Disk Enclosure Voltage
--- Disk Enclosure Temperature
- Disks in Enclosures
- Disks Logical Partitions
- SAS PHYs of ESMs
- SAS PHYs of HBAs
- SAS PHYs
- Switches Zonemaps
- SAS PHYs of Switches
- SAS PHYs Switches Errors
- SPU disk paths
--- Paths
- SAS Switch errors
- NPS version and state
- NPS Inventory (nzhw)
- NPS Data Slices (nzds)
- /nz/kit/bin/nzds -regenstatus results
- NPS Catalog Size
- NPS Catalog Files larger that 1M
- /nzlocal/scripts/hpf_health results

- Environment variables
- /opt/nz/fdt/sys_rev_check results
- /nz/kit/bin/nzstats results
- /opt/nz-hwsupport/pts/pts-check.pl results
- /nzlocal/scripts/hpf_ping.sh results
- Results of /nzlocal/scripts/diag_xs2/concheck.pl
- Disk error correction delay
- Number of operations transferred by disks compared to other disks present in appliance
- Disk resets
- CallHome information
Sysinfo Report stored in /nz/kit.7.2.0.0/log/nzhealthcheck/Netezza_System_Health_Check_Sysinfo_Report_20140811_055254.txt
All done
Managing the monitoring daemon

The daemon is started automatically after the upgrade process and it runs in the
background. There is no need to start or stop it manually, unless some issues
appear.
Note: The daemon is integrated with the HA cluster and will start only if the
cluster is active. This means that it will not start in the maintenance mode. The
start and stop commands are called by the nzinit command. The daemon migrates
as the cluster does.
Procedure
v To check the status of the daemon, use the following command:
service nzhealthcheck status
v If the daemon was stopped for some reason, you start it with the following
command:
service nzhealthcheck start
v If you must stop the daemon manually, run the following command:
service nzhealthcheck stop
The nzhealthcheck command

Use the nzhealthcheck command to run the Netezza System Health Check tool
and view the report on possible system issues.
Syntax
The nzhealthcheck command has the following syntax.

nzhealthcheck [OPTION...] [sysinfo]
Inputs
The nzhealthcheck command takes the following input options. The input options
have two forms for the option names.
Table 17-2. The nzhealthcheck input options. The table provides information about the
options that the nzhealthcheck command takes and their explanations.
Option Description
sysinfo Generates the Sysinfo Report.
-a, --detail Shows all rule results.
-d, --daemon Starts the System Health Check daemon.

Table 17-2. The nzhealthcheck input options (continued). The table provides information
about the options that the nzhealthcheck command takes and their explanations.
Option Description
-D, --mode=diagnostic Switches the daemon to the diagnostic
mode and restarts it. The daemon works in
this mode by default.
-M, --mode=monitoring Switches the daemon to the monitoring
mode and restarts it.
-I, --mode Display the current status of the daemon
and its mode.
-?, --help Displays detailed help on command usage.
--usage Provides a short usage message.
-V, -v, --version Provides the System Health Check version.
Description
You use the nzhealthcheck command to generate the System Health Check Report.
You can also generate the Sysinfo Report with additional data about the system
that might be of use when troubleshooting problems. When running the command,
the Netezza system can be in any operational state.
The nzhealthcheck tool is installed in /nz/kit/share/healthcheck.
Usage
The following provides some of the command uses and sample syntax:
v To generate the System Health Check Report with all the evaluated rules listed:
nzhealthcheck -a
v To generate the Sysinfo Report:
nzhealthcheck sysinfo

Appendix A. Netezza CLI
You can use the IBM Netezza CLI to manage the Netezza software, hardware, and
databases.
Netezza Support might also ask you to run specific low-level diagnostic commands
to investigate problems. This section provides information about the Netezza user
commands and the Netezza Customer Service commands.
Summary of command-line commands

The following table describes the commands that you can use to monitor and
manage the IBM Netezza system. These commands are in the /nz/kit/bin
directory on the Netezza host. A subset of these commands is also installed with
the Netezza client kits and can be run from a remote client system, as described in
“Command locations” on page 3-3.
To run these commands from the Netezza system, you must be able to log in as a
valid Linux user on the Netezza system. Most users typically log in as the nz user.
In addition, many commands require that you to specify a valid database user
account and password; the database user might require special privileges, as
described in “Command privileges” on page A-3. Throughout this section, some
command examples show the database user and password options on the
command line, and some examples omit them with the assumption that the user
and password were cached such as by using nzpassword.
Table A-1. Command-line summary
Command Description Reference
nzbackup Backs up an existing For command syntax and more information,
database. see “The nzbackup command” on page 13-11.
nzcontents Displays the revision For command syntax, see “The nzcontents
and build number of all command” on page A-9. For more
the executable files, plus information, see “Software revision levels” on
the checksum of page 7-1.
Netezza binaries.
nzconvert Converts character For command syntax, see “The nzconvert
encodings for loading command” on page A-10. For more
with the nzload information, see the IBM Netezza Database
command or external User’s Guide.
tables.
nzds Manages and displays For command syntax, see “The nzds
information about the command” on page A-10.
data slices on the
system.
nzevent Displays and manages For command syntax, see “The nzevent
event rules. command” on page A-14. For more
information, see Chapter 8, “Event rules,” on
page 8-1.
nzhistcleanupdb Deletes old history For command syntax, see “The
information from a nzhistcleanupdb command” on page A-19. For
history database. more information, see Chapter 14, “History
data collection,” on page 14-1.
© Copyright IBM Corp. 2001, 2015 A-1

Table A-1. Command-line summary (continued)
nzhistcreatedb Creates a history For command syntax, see “The nzhistcreatedb
database with all its command” on page A-21. For more
tables, views, and information, see Chapter 14, “History data
objects for history collection,” on page 14-1.
collection and reporting.
nzhostbackup Backs up the host For command syntax, see “The nzhostbackup
information, including command” on page A-24.
users and groups.
nzhostrestore Restores the host For command syntax, see “The nzhostrestore
information. command” on page A-26.
nzhw Manages system For command syntax, see “The nzhw
hardware components. command” on page A-28.
nzinventory This command is See the command “The nzhw command” on
obsolete in Release 5.0. page A-28.
nzkey Creates and manages For command syntax, see “The nzkey
authentication keys for command” on page A-34.
self-encrypting drives
(SEDs).
nzkeydb Creates and manages a For command syntax, see “The nzkeydb
key store for SED command” on page A-37.
authentication keys.
nzkeybackup Creates a backup of a For command syntax, see “The nzkeybackup
key store for SED command” on page A-39.
nzkeyrestore Restores from a backup For command syntax, see “The nzkeyrestore
of a key store for SED command” on page A-40.
nzload Loads data into For command syntax and more information,
database files. see the IBM Netezza Data Loading Guide.
nzpassword Stores a local copy of For command syntax, see “The nzpassword
the user password. command” on page A-43. For more
information, see “Encrypted passwords” on
page 2-13.
nzreclaim Grooms databases and For command syntax, see “The nzreclaim
tables to remove deleted command” on page A-45. For more
or outdated rows, and information, see “Groom tables” on page
also reorganizes the 12-20.
tables based on their
organizing keys.
nzrestore Restores the contents of For command syntax and more information,
a database backup. see “The nzrestore command” on page 13-22.
nzrev Displays the current For command syntax, see “The nzrev
software revision for command” on page A-47. For more
any Netezza software information, see “Software revision levels” on
release. page 7-1.
A-2 IBM Netezza System Administrator’s Guide

Table A-1. Command-line summary (continued)
nzsession Shows a list of current For command syntax, see “The nzsession
system sessions (load, command” on page A-49. For more
client, and sql). Supports information, see “Session management” on
filtering by session type page 12-23.
or user, aborting
sessions, and changing
the current job list for a
queued session job.
nzsfi This command is See the command “The nzhw command” on
nzspu This command is See the command “The nzhw command” on
nzspupart Shows a list of all the See the command “The nzspupart command”
SPU partitions and the on page A-54.
disks that support them.
nzsql Runs the SQL command For usage information, see “Databases and
interpreter. user tables” on page 12-1. For command
syntax, see the IBM Netezza Database User’s
Guide.
nzstart Starts the system. For command syntax, see “The nzstart
command” on page A-56. For more
information, see “Manage the system state” on
page 7-6.
nzstate Displays the current For command syntax, see “The nzstate
system state or waits for command” on page A-58. For more
a specific system state to information, see “Display the current system
occur before it returns. state” on page 7-2.
nzstats Displays system level For command syntax, see “The nzstats
statistics. command” on page A-60. For more
information, see Chapter 16, “Netezza
statistics,” on page 16-1.
nzstop Stops the system. For command syntax, see “The nzstop
command” on page A-63. For more
information, see “Manage the system state” on
page 7-6.
nzsystem Changes the system For command syntax, see “The nzsystem
state or displays the command” on page A-65. For more
current system information, see “Manage the system state” on
information. page 7-6.
nztopology This command is See the command “The nzds command” on
Command privileges
Some administrative privileges may be required for certain commands. The
database user account may require one or more of the privileges described in
Table 11-1 on page 11-10 to complete successfully. In addition, operations on objects
such as databases, tables, views, and others may require object privileges as
described in Table 11-2 on page 11-11. As with administrator privileges, specifying
the WITH GRANT option allows a user to grant the privilege to others.
Appendix A. Netezza CLI A-3

Commands without special privileges
The following commands do not require special privileges:
v You do not need special privileges to run some commands such as nzstate,
nzsystem showRev, or showState commands.
v You do not need special privileges to run the nzrev, nzcontents, nzstart,
nzhostbackup, nzhostrestore, and nzstop commands, but you must be able to
log on to the host.
v You do not need special privileges to run the nzsession show command,
however you can only see objects for which you have privileges.
Exit codes
An nz command that completes successfully returns either no exit code or the
number 0 as an exit code. A non-zero exit code indicates that the command failed
due to an error that affected either the command itself or a subcommand. If an nz
command fails, refer to the messages displayed in the command shell window for
more information about the cause of the failure.
Netezza CLI command syntax

All IBM Netezza CLI commands have the following top-level syntax options:
-h Displays help. You can also enter -help.
-rev Displays the software revision level. You can also enter -V.
-hc Displays help for the subcommand (if the command has subcommands).
For many Netezza CLI commands you can specify a timeout. This is the amount of
time the system waits before it abandons the execution of the command. If you
specify a timeout without a value, the system waits 300 seconds. The maximum
timeout value is 100,000,000 seconds.
The nzbackup command

Use the nzbackup command to back up your database.
For more information, see “The nzbackup command” on page 13-11

Related reference:
“Command syntax for nzbackup” on page 13-12
The nzcallhome command

Use the nzcallhome command to configure and manage the callhome service and
the automatic notifications for issues that are detected on the IBM PureData
System for Analytics appliances.
Syntax
The nzcallhome command has the following syntax.

nzcallhome [-configure] [-dataInspection] [-debug] [-disable]
[-disableDataReporting] [-disableDebug] [-disableEmailOnly]
[-disableInventory] [-disablePmr] [-disableStatus] [-enable]
[-enableDataReporting] [-enableDebug] [-enableEmailOnly]
[-enableInventory] [-enablePmr] [-enableStatus] [-generateInventory]
[-generatePmr <report name>] [-generateStatus] [-generateStatusFull]
[-off] [-on] [-remove][-requestUpgrade <args>] [-status] [-validateConfig]

[-verifyConnectivity]
nzcallhome -generatePmr [ diskMon clusterSsc scsiDISKA spuCore

scsiPredDISKB hwVoltSPU scsiPredDISKBDup
hwAttnSPU regenSPUDISKA sscOnline hwSPU
hwDISKB ]
Inputs
The nzcallhome command takes the following inputs:

Table A-2. The nzcallhome input options
Input Description
-configure Adds the callhome event rules to the event
manager for monitoring. Several of the
event rules are added with an "off" status,
and you must enable them using
nzcallhome -enable to activate the rules.
-dataInspection Creates the data that would be prepared for
a generated PMR, status, or inventory but
does not send the information. The
command saves the data locally and alerts
the user to the location so that the user can
review the data that is being collected. You
must specify either -generatePmr,
-generateStatus or -generateInventory
argument with the -dataInspection.
-debug Displays the debug output messages on the
console.
-disable Updates the callhome rules to disable them,
which means that those rules will not be
triggered nor take any action when the
associated problem occurs on the system.
-disableDataReporting Disables the data reporting when a PMR is
generated.
-disableDebug Disables debug logging.
-disableEmailOnly Disables the email-only PMR generation.
-disableInventory Disables the inventory reporting component.
-disablePmr Disables the PMR component.
-disableStatus Disables the status reporting component.
-enable Updates the callhome rules to enable them
for monitoring and automatic notifications.
-enableDataReporting Enables the data reporting when a PMR is
generated. This is the default.
-enableDebug Enables debug logging. This option controls
whether debug output appears when you
run the nzcallhome command. You enable
the debug output when you are working
with an IBM Support representative to
identify problems with the callhome
configuration or operations, and then
disable debug output when the problem is
corrected. In normal operations, do not
enable the debug output format.

Table A-2. The nzcallhome input options (continued)
Input Description
-enableEmailOnly Enables the email-only PMR generation.
-enableInventory Enables the inventory reporting component.
-enablePmr Enables the PMR component.
-enableStatus Enables the status reporting component.
-generateInventory Generates an inventory report.
-generatePmr <report name> Generates one or more test event conditions
for the callhome service. For the <report
name> value, you can specify one of the
following types. You could also specify
several values in a space-separated list
enclosed with quotation marks.
diskMon
Generate three
disk_monitorPredictive events.
clusterSsc
Generate Cluster Fail Over event
from a sysStateChanged event.
scsiDISKA
Generate scsiDiskError for DISK 'A'
spuCore
Generate spuCore (will evaluate
last core present, if any.)
scsiPredDISKB
Generate scsiPredictiveFailure for
DISK 'B'
hwVoltSPU
Generate hwVoltageFault for SPU.
scsiPredDISKBDup
Generate scsiPredictiveFailure for
DISK 'B' (duplicate of previous.)
hwAttnSPU
Generate hwNeedsAttention for
SPU.
regenSPUDISKA
Generate regenFault for SPU with
Disk 'A'.
sscOnline
Generate a sysStateChanged event.
hwSPU
Generate hwServiceRequested for
SPU.
hwDISKB
Generate hwServiceRequested for
DISK 'B'.
-generateStatus Generates a status report.
-generateStatusFull Generates a full status report using a more
extensive system information process.

Table A-2. The nzcallhome input options (continued)
Input Description
-h Displays detailed command usage. If you
issue the nzcallhome command without any
options, or with an incorrect option, the
command displays the syntax of the
command options.
-off Disables or stops the callhome service
monitoring. Typically used only to stop the
service before software upgrades or service
events such as hardware replacement.
-on Enables the callhome service monitoring.
-remove Deletes or drops the callhome-related event
rules.
-requestUpgrade <args> Creates a special callhome event email that
requests an appliance upgrade. You must
specify two arguments, version and
component, in the format version:7.2.1.0
component:NPS.
-status Displays the status of the callhome service.
enabled
The callhome service is on and, if
the event rules are configured and
enabled, the service is actively
monitoring for problem conditions.
disabled
The callhome service is off and no
notifications will take place if the
callhome-related events are
triggered.
-validateConfig Validates whether the callHome.txt file is
configured correctly.
-verifyConnectivity Verifies that the installed nzcallhome can
communicate with the IBM backend status,
inventory and PMR services.
Description
You use the nzcallhome command to enable and disable the callhome service,
configure and remove callhome-related event rules, and as the primary command
for managing the automated notifications to IBM Support for problem conditions
on the IBM Netezza appliance. You can also generate event conditions for testing
the callhome features and operations, and you can use the command to request
software or firmware upgrades of your appliance.
The nzcallhome command replaces the previous nzOpenPmr command, which is

deprecated in Netezza Platform Software release 7.2. If you used the nzOpenPmr
command previously, transition to use the nzcallhome command.
The nzcallhome command is installed in /nz/kit/bin/adm.

Usage
v To enable the callhome service:
nzcallhome -on
v To test that call home can reach the IBM servers:
nzcallhome -verifyConnectivity
Connectivity Verification: Alias: Edge_Gateway_1,
Host: stg-edge-cdt.eventsgslb.ibm.com, IP: 9.11.13.208 : SUCCESS
The IP address is one example of the IBM server address. The IP you use could
be different depending upon your location.
v To disable or stop the callhome service during service or upgrades:
nzcallhome -off
v To generate some test SPU event conditions:
nzcallhome -generatePmr hwSpu hwAttnSpu
The nzconfigcrypto command

Use the nzconfigcrypto command to enable or disable the enhanced cryptography
support on an IBM Netezza appliance.
Syntax
The nzconfigcrypto command has the following syntax:

nzconfigcrypto -HK <key_store.key_name>
[-LDPBNDPW <ldap_bind_password>]
[-enable | -disable]
Inputs
The nzconfigcrypto command takes the following inputs:

Table A-3. The nzconfigcrypto input options
Input Description
-HK <key_store.key_name> The -HK argument is required when you specify the
-enable option. Specifies an existing host key on the
system. You must specify a host key of type AES_256.
The command sets the default host key to this value
when you enable enhanced cryptography support. If
your system already uses a default AES-256 host key,
you can supply that keystore.keyname as input to the
command.
-LDPBNDPW <ldap_bind_password> If you use LDAP connections to access the Netezza
server, specifies the password for binding to the LDAP
server.
-enable Enables the enhanced cryptography support.
-disable Disables the enhanced cryptography support. The
-disable option is the default if you do not specify
either -enable or -disable with the command.

Description
Privileges required
You must log in to the Netezza system as the nz user to run this
command.
Common tasks
Use the nzconfigcrypto command to enable or to disable the enhanced
cryptography support on a Netezza system.
Error Messages
The nzconfigcrypto command can return the following errors for invalid
arguments or settings.
Table A-4. The nzconfigcrypto input options
Message Description
ERROR: LookupCryptoKey: The error message indicates that the supplied host key
object "key" not found was not found. Check the keystore and key name that
you entered to make sure that you specified them
correctly and retry the command with the correct
values. You can use the SHOW KEYSTORE keystore
VERBOSE command to display the names of the keys
and their types in the keystore.
ERROR: New Hostkey can’t be The error message indicates that the key name values
retrieved keystore.keyname are for a key that is not of type AES_256. An AES_256
type key is required for the nzconfigcrypto command.
The nzcontents command

Use the nzcontents command to display the IBM Netezza program names, the
revision level, the build level, and the checksum of binaries.
This command takes several seconds to run and results in multiple lines of output.
Programs with no revisions are either scripts or special binaries
Syntax
The nzcontents command uses the following syntax:

nzcontents [-h]
Description
The nzcontents command has the following characteristics.

Privileges required
You do not need special privileges to run the nzcontents command.
Common tasks
Use the nzcontents command to display the names of programs, and their
revision and build level.
Usage
The following provides some sample usage:

v To display the software programs and their revisions, enter:

[nz@nzhost ~]$ nzcontents
Program Revision Stamp Build Stamp CheckSum
-------------- ------------------------- --------------------------------- --------------
adm Directory
nzbackup 6.0.0-0.B-1.P-0.Bld-12478 2010-04-15.12478.dev.cm.12478 1821...
nzcontents ab685...
nzconvert 3a52...
nzds 6.0.0-0.B-1.P-0.Bld-12478 2010-04-15.12478.dev.cm.12478 d3f2...
Related reference:
“The nzrev command” on page A-47
The nzconvert command

Use the nzconvert command to convert between any two encodings, between these
encodings and UTF-8, and from UTF-32, UTF-16, or UTF-8 to NFC, for loading
with the nzload command or external tables.
Syntax
The nzconvert command uses the following syntax:

nzconvert [-h|-rev] [options]
Options
For information about the nzconvert options, see the IBM Netezza Database User’s
Guide.
Description
The nzconvert command has the following characteristics:

Privileges required
No special privileges are required to use this command.
Common tasks
Use the nzconvert command to convert character encoding before you load
Related reference:
“The nzload command” on page A-42
Use the nzload command to load ASCII data into database tables.
The nzds command

the system.
Syntax
The nzds command has the following syntax:

nzds [-h|-rev] [-hc] subcmd [subcmd_options]

Inputs
The nzds command takes the following inputs:

Table A-5. The nzds input options
Input Description
nzds show [options] Displays information about the data slice topology. The
show subcommand is the default and displays a list of
all the data slices on the system and information about
status, the SPU that manages the data slice, the
Primary Storage (that is, the disk ID where the primary
copy of the data slice resides), the Mirror Storage (that
is, the disk ID where the mirror copy of the data slice
resides), and % Used (the amount of space in the data
slice that contains data).
You can specify one or more options to show specific

output.
nzds show [-detail] Displays information about the data slice topology and
includes information about locations and disk space.
nzds show -spa id Displays information about the data slices which are
owned by a particular S-Blade in the SPA.
nzds show -dsId id Displays information about the specific data slice.
nzds show -id hwId Displays information about the data slices that are
assigned to the specified hardware.
nzds show -topology Displays the current storage topology. The output
shows how system resources such as SPUs, disks, SAS
switches, and HBA ports are used within the system to
support the storage paths. This command is not
supported on IBM Netezza High Capacity Appliance
C1000 appliances or on IBM Netezza Platform
Development Software.
nzds show -caCertFile path Specifies the path name of the root CA certificate file
on the client system. This argument is used by IBM
Netezza clients who use peer authentication to verify
the Netezza host system. The default value is NULL,

Table A-5. The nzds input options (continued)
Input Description
nzds show -securityLevel level Specifies the security level that you want to use for the
session. This option does not apply when you are
logged in to the Netezza system and running the
command. The argument has four values:
preferredUnSecured
This value is the default value. Specify this
option when you would prefer an unsecured
connection, but you accept a secured
connection if the Netezza system requires one.
preferredSecured
Specify this option when you want a secured
connection to the Netezza system, but you
accept an unsecured connection if the Netezza
system is configured to use only unsecured
connections.
onlyUnSecured
Specify this option when you want an
unsecured connection to the Netezza system.
If the Netezza system requires a secured
connection, the connection is rejected.
onlySecured
connection to the Netezza system. If the
Netezza system accepts only unsecured
connections, or if you are attempting to
connect to a Netezza system that is running a
release before 4.5, the connection is rejected.
nzds show -regenStatus Displays information about the status of any disk
[-detail] regenerations that are in progress. The command
displays information about the Data Slice being
regenerated, its SPU owner, the Source data slice ID, its
Destination data slice ID, the Start Time of the
regeneration, and % Done.
Include the -detail option for more information such

as the locations of the SPUs and storage areas.
nzds show -issues [-detail] Displays information about data slices that are
reporting problems. The command displays a list of
data slices to investigate and their Status, SPU, Primary
Storage, Mirror Storage, and % Used.
Include the -detail option for more information such

as location details and data slice size.
Note: The size of the data slice is reported in gibibytes,
which is in units of 10243 bytes.
Options
The nzds command takes the following options:

Table A-6. The nzds options
Option Description
-host hostname Specifies the host name or IP address of the Netezza system.

Table A-6. The nzds options (continued)
Option Description
-u user Specifies the database user name [NZ_USER].
-pw password Specifies the user password [NZ_PASSWORD].
-timeout secs Specifies the amount of time in seconds to wait for the command
to complete before it exits with a timeout error. Default is 300.
Description
The nzds command has the following description.

Privileges required
Your database user account does not require any special administrative
privileges to run the nzds show command.
Common tasks
Use the nzds command to manage and display information about the data
slices in the system. You can also use this command to create a balanced
topology for best performance of the system.
Usage

v To show information about regenerations that are in progress:
nzds show -regenstatus
Data Slice SPU Source Destination Start Time % Done
---------- ---- ------ ----------- ----------------------- --------
5 1092 1035 1014 09-Apr-09, 07:24:55 EDT 0.01
6 1092 1035 1014 09-Apr-09, 07:24:55 EDT 0.01
v To show the data slice information for the system, use the following command:
nzds show
Data Slice Status SPU Partition Size (GiB) % Used Supporting
Disks
---------- ------- ---- --------- ---------- ------ ---------------
1 Healthy 1017 2 356 58.54 1021,1029
2 Healthy 1017 3 356 58.54 1021,1029
...
The sample output that is shown for this command is truncated for the
documentation.
v To show the data slice issues reported for the system, use the following
command:
nzds show -issues
---------- -------- ---- --------- ---------- ------ ----------------
11 Degraded 1113 4 356 11.80 1091
12 Degraded 1113 5 356 11.79 1091
Related concepts:
“Manage data slices” on page 5-25
A data slice is a logical representation of the data that is saved in the partitions of
a disk. The data slice contains pieces of each user database and table. The IBM
Netezza system distributes the user data to all of the disks in the system by using
a hashing algorithm.
Related reference:
The nzevent command

You use the nzevent command to manage the alerts and triggers for problem and
condition reporting on the IBM Netezza appliances.
Use the nzevent command to do any of the following tasks:

v Show a list of event rules.
v Copy a predefined template event rule and use it as your source to add a rule.
v Modify an existing event rule or a copied predefined template.
v Add an event rule.
v Delete an event rule.
v Generate events.
Syntax
The nzevent command uses the following syntax:

nzevent [-h|-rev|-hc] subcmd [subcmd options]
Inputs
The nzevent command takes the following inputs:

Table A-7. The nzevent input options
Input Description
nzevent add options Adds an event rule.
nzevent copy options Copies a predefined template event rule or an existing
event rule.
nzevent delete options Deletes an event rule.
nzevent generate options Generates an event.
nzevent listEventTypes options Lists the valid event types.
nzevent listNotifyTypes Lists the notification types.
options
nzevent modify options Modifies an event rule.
nzevent show options Displays the event rules.

Options
The nzevent command takes the following options:

Table A-8. The nzevent options
Command Option Description
All nzevent -u user Specifies the database user name [NZ_USER].
commands
-host name Specifies the host name or IP address [NZ_HOST].
-timeout secs Specifies the time to wait before it exits with a
timeout error (default = 300). Does not apply to
listEventTypes and listNotifyTypes.
nzevent add -eventType type Specifies the event type for the event. For a list of
the event types, see Table 8-3 on page 8-7.
nzevendt copy
-eventArgsExpr Specifies the optional match expression for further
nzeventd modify expr filtering. For more information, see Table 8-4 on
page 8-12.
-name value If you are adding an event, specifies the event
rule name. If you are copying an event, specifies
the name of the event you are copying. If you are
modifying an event, specifies the name of the
event that you are changing.
-newname value If you are modifying or copying an event,
specifies the name of the new event.
-useTemplate If you are copying an existing event, uses the rule
that is specified with the -name option as a
template for this new rule.
-notifyType type Specifies the type of notification to generate for
this event. The notify types are email and
runCmd.
-dst value Specifies the notification destination (notify-type
specific). For email, it is the email address. For
runCmd, it is the full path of the command or
command file to run.
-ccDst value Specifies additional notification destinations
(email only).
-msg string Specifies the notification message to send. For
email, this is the subject string and cannot be
blank. For runCmd, this is the argument for -msg
parameter.
-bodyText string Specifies more text to send with the notification
message.
-callHome bool Specifies whether to append system information
to the notification message. For email, the system
sends /nz/kit/data/config/callHome.txt as an
attachment. This file contains customer
information such as company, address, contact,
and system information such as model number,
and serial number. For runCmd, the system
passes the file path to the command.
-on bool Enables or disables processing for this rule.

Table A-8. The nzevent options (continued)
-eventAggrCount Specifies the number of events to aggregate (email
int events only). You can specify a number from 1 -
1000.
nzevent delete -force Does not prompt for confirmation.
-name rule_name Deletes the event rule <rule_name>.
nzevent generate -eventType type Generates the specified type of event. For a list of
the event types, see Table 8-3 on page 8-7.
-eventArgs expr Specifies a list of one or more optional event
arguments (<tag>=<value>, ...).
-force Flushes all aggregate events and sends a
notification (email only).
nzevent show -name rule_name Displays only the event rule corresponding to the
rule_name. If you do not specify a name, the
command displays all event rules.
-syntax Displays the rule in CLI syntax.
-maxColW chars Specifies the maximum number of characters to
print in each output table column. The default is
24 characters.
-orient type You can specify the output display. The value
values are
Horizontal
Displays the event types in a table.
Vertical
Displays each event as a complete record.
Auto Selects the display that is based on the
number of rows.
-caCertFile path Specifies the path name of the root CA certificate
file on the client system. This argument is used by
Netezza clients who use peer authentication to
verify the Netezza host system. The default value
is NULL, which skips the peer authentication
process.

Table A-8. The nzevent options (continued)
-securityLevel Specifies the security level that you want to use
level for the session. This option does not apply when
you are logged in to the Netezza system and
running the command. The argument has four
values:
preferredUnSecured
This value is the default value. Specify
this option when you would prefer an
unsecured connection, but you accept a
secured connection if the Netezza system
requires one.
preferredSecured
Specify this option when you want a
secured connection to the Netezza
system, but you accept an unsecured
connection if the Netezza system is
configured to use only unsecured
connections.
onlyUnSecured
unsecured connection to the Netezza
system. If the Netezza system requires a
secured connection, the connection is
rejected.
onlySecured
system. If the Netezza system accepts
only unsecured connections, or if you are
attempting to connect to a Netezza
system that is running a release before
4.5, the connection is rejected.
Description
The nzevent command does the following:

Privileges required
Your database user account must have Manage System privilege.
Common tasks
Use the nzevent command to set the preconfigured event rules, and to
create your own event rules.
Usage

v To add an event rule, enter:
nzevent add -name Newrule -u admin -pw password -host nzhost -on
yes -eventType sysStateChanged -eventArgsExpr '$previousState ==
online && $currentState != online' -notifyType email -dst

jdoe@netezza.com -msg 'NPS system $HOST went from $previousState to
$currentState at $eventTimestamp.' -bodyText
'$notifyMsg\n\nEvent:\n$eventDetail\nEvent
Rule:\n$eventRuleDetail'
v To copy a template event rule from the template table to the user-modifiable
table, enter:
nzevent copy -u admin -pw password -useTemplate -name
HostNoLongerOnline -on yes -dst jdoe@netezza.com
v To delete an event rule, enter:
nzevent delete -u admin -pw password -host nzhost -name Newrule
v To generate an event rule, enter:
nzevent generate -u admin -pw password -host nzhost -eventtype
custom1 -eventArgs 'customType=tooManySessions, numSessions=<n>'
v To list event types, enter:
nzevent listEventTypes
v To list notification types, enter:
nzevent listNotifyTypes
v To modify an existing event rule, enter:
nzevent modify -u admin -pw password -host nzhost -name Newrule -on
yes -dst jdoe@netezza.com
v To display a specific event rule, enter:
nzevent show -u admin -pw password -host nzhost -name Newrule
v To display event rules vertically, enter:
nzevent show -u admin -pw password -host nzhost -orient vertical
Related reference:
The nzhealthcheck command

Use the nzhealthcheck command to run the Netezza System Health Check tool
and view the report on possible system issues.
Syntax
The nzhealthcheck command has the following syntax.

nzhealthcheck [OPTION...] [sysinfo]
Inputs
The nzhealthcheck command takes the following input options. The input options
have two forms for the option names.
Table A-9. The nzhealthcheck input options. The table provides information about the
options that the nzhealthcheck command takes and their explanations.
Option Description
sysinfo Generates the Sysinfo Report.
-a, --detail Shows all rule results.

Table A-9. The nzhealthcheck input options (continued). The table provides information
about the options that the nzhealthcheck command takes and their explanations.
Option Description
-d, --daemon Starts the System Health Check daemon.
-D, --mode=diagnostic Switches the daemon to the diagnostic
mode and restarts it. The daemon works in
this mode by default.
-M, --mode=monitoring Switches the daemon to the monitoring
mode and restarts it.
-I, --mode Display the current status of the daemon
and its mode.
-?, --help Displays detailed help on command usage.
--usage Provides a short usage message.
-V, -v, --version Provides the System Health Check version.
Description
You use the nzhealthcheck command to generate the System Health Check Report.
You can also generate the Sysinfo Report with additional data about the system
that might be of use when troubleshooting problems. When running the command,
the Netezza system can be in any operational state.
The nzhealthcheck tool is installed in /nz/kit/share/healthcheck.
Usage
v To generate the System Health Check Report with all the evaluated rules listed:
nzhealthcheck -a
v To generate the Sysinfo Report:
nzhealthcheck sysinfo
The nzhistcleanupdb command

Issue the nzhistcleanupdb command to delete outdated history information from a
history database.
Syntax
The command has the following syntax:

nzhistcleanupdb [options]

Inputs
The nzhistcleanupdb command takes the following input options:

Table A-10. The nzhistcleanupdb input options
Input Description
{-d | --db} dbname The name of the history database from which you want to
remove old data. If you want to specify a delimited name,
you must enclose the name in double quotation marks,
and you must escape the quotes with a backslash. For
example:
-d \"MyDbName\"
{-n | --host} NZ_HOST The host name of the system where the database resides.
The default and only value for this option is NZ_HOST.
{-u | --user} user The user account that permits access to the database. The
default is NZ_USER. The user must both be able to access
the history database and must have the Delete privilege for
the history database tables.
If you want to specify a delimited name, you must enclose

the name in double quotation marks, and you must escape
the quotes with a backslash. For example:
-u \"MyUserName\"
{-p | --pw} password The password for the user account that permits access to
the database. The default is NZ_PASSWORD.
{-t | --time} The date and time threshold. All data recorded before this
"<yyyy-mm-dd[,hh:mm[:ss] date and time is deleted. The date (year, month, and day)
]>" is required. The time (hours, minutes, and seconds) is
optional. The default time is 12:00 AM (midnight, start of
day).
-f | --force Do not prompt for confirmation.
-g | --groom Run a groom operation (that is, automatically issue the
GROOM TABLE command) after the cleanup operation
completes. This updates the zone maps for the history data
tables, which improves the performance of queries against
those tables.
-h | --help Display the usage and syntax for the command.
Description

history database.
Privileges required
You must be the nz user to run this command, and you must specify a
database user account who is either the owner or user of the history
database or who has administration privileges to update the history
database and its tables.
Usage
The following command removes from the history database with the name histdb
any history data that was collected before October 31, 2013, and automatically
grooms the history tables afterward:
[nz@nzhost ~]$ nzhistcleanupdb -d histdb -u smith -pw password -t
"2009-10-31" -g
About to DELETE all history entries older than 2013-10-31 00:00:00
(GMT) from histdb.
Proceed (yes/no)? :yes
BEGIN
DELETE 0
DELETE 98
DELETE 34
DELETE 0
DELETE 0
DELETE 188
DELETE 188
DELETE 62
DELETE 65
DELETE 0
DELETE 0
DELETE 0
DELETE 503
COMMIT
Related reference:
“The nzhistcreatedb command”
The nzhistcreatedb command

Syntax
The command has the following syntax:

nzhistcreatedb option [option ...]
Inputs
The nzhistcreatedb command takes the following options:

Table A-11. The nzhistcreatedb input options
Input Description
{-d | --db} dbname The name of the history database to be created. If you
want to specify a delimited name, you must enclose the
name in double quotation marks, and you must escape the
quotes with a backslash. For example:
-d \"MyDbName\"
{-n | --host} NZ_HOST The host name of the system on which the database
resides. The default and only possible value for this option
is NZ_HOST.

Table A-11. The nzhistcreatedb input options (continued)
Input Description
{-t | --db-type} The type of the database to be created:
[Q|query|A|audit]
Q | query
A query database collects and stores the data that
is most commonly needed to monitor and report
on the query activity of a system.
A | audit
An audit database collects the same data as a
query database, but stores the data in row-secured
tables and digitally signs the data to prevent it
from being changed. You can also specify that an
audit database is to log the activity of all users or
of specific users or groups. For more information
about audit history databases, see the IBM Netezza
Important: The specified type must match the history
database type specified in the CREATE HISTORY
CONFIGURATION command used to create the active history
configuration; otherwise, the loader process fails.
{-o | --owner}user The user account of the owner of the history database. The
specified user account must already be defined and must
have Create Database privilege. The default is NZ_USER.
You cannot specify the admin user to be the database
owner.
If the owner (-o parameter) and load user (-u parameter)

accounts are different, the owner account must also be
granted the List privilege for the load user account.

-o \"MyUserName\"
{-p | --pw} password The password for the owner user account. The default is
NZ_PASSWORD.
{-u | --user} user The load user, that is, the user account that is to be used to
load history data into the database. The load user is
automatically granted the privileges that are needed to
perform the corresponding insert operations. The default
load user is the database owner. You cannot specify the
admin user to be the load user.
The password for the load user is not specified in this

command; instead, it is specified in the history
configuration.

-u \"MyUserName\"

Table A-11. The nzhistcreatedb input options (continued)
Input Description
{-v | --schema} number The number of the schema version that is to be used for
the history database that is to be created:
1 For Netezza Release 4.6 to 7.0.2.
2 For Netezza Release 7.0.3 to 7.0.4.
3 For Netezza Release 7.1.
For more information about the differences among these
versions, see “History database versions” on page 14-2.
Important: The specified version number must match the
version number specified in the CREATE HISTORY
CONFIGURATION command used to create the active history
configuration; otherwise, the loader process fails.
-h | --help Display the usage and syntax for the command.
Outputs
The nzhistcreatedb command has the following output messages.

Table A-12. The nzhistcreatedb output messages
Message Description
History database name The command completed successfully.
created successfully !
ERROR: History database The command failed because the specified user name did
qhist not created: not exist on the system.
ERROR: GrantRevokeCommand:
group/user "name" not found
ERROR: History database dev The command failed because the specified database name
not created: exists on the system.
ERROR: createdb: object

"hist1" already exists.
ERROR: History database The command failed because the password for the
hist1 not created: specified owner was not correct.
nzsql: Password
authentication failed for
user 'name'
ERROR: History database The command failed because the specified owner does not
hist1 not created: have Create Database privileges on the system.
ERROR: CREATE DATABASE:

permission denied.
ERROR: History database The specified owner account does not have the List
hist1 not created: privilege for the specified user account or the User object
class. The owner must have the List privilege to complete
ERROR: GrantRevokeCommand: the privilege assignments.
permission denied on "bug".
Description
The nzhistcreatedb command creates a history database and configures its

ownership and access permissions. It creates the history database object, all the

history tables and views, and grants the permissions for the owner and user
accounts that are specified in the command. The command can take several (four
to five) minutes to complete processing.
Privileges required
You must be the logged in as the nz user to run this command.
Usage
The following command creates a history database with the name histdb:
[nz@nzhost ~]$ nzhistcreatedb -d histdb -t query -v 1 -u jones
-o smith -p password123
This operation may take a few minutes. Please wait...
Creating tables .................done
Creating views .......done
Granting privileges ....done
History database histdb created successfully !
The command can take several minutes to complete, depending on how busy the
IBM Netezza system is.
Related concepts:
“Creating a history database” on page 14-5
You can create any number of history databases, but the system can write to only
one at a time.
“Maintaining a history database” on page 14-13
A history database grows as it accumulates history information. Plan for routine
maintenance of the history database. Determine the amount of time that you need
to keep the history data before you can archive or delete it (for example, keep only
data for the current and previous month, or the current and previous quarter, or
for the current year only).
Related reference:
“The nzhistcleanupdb command” on page A-19
history database.
The nzhostbackup command

In the rare situations when a Netezza host server or disk fails, but the SPUs and
their data are still intact, you can restore the /nz/data directory (or whatever
directory you use for the Netezza data directory) from the host backup without the
additional time to restore all of the databases. For more information, see “Host
backup and restore” on page 13-9.
Before you run the nzhostbackup command, you must do one of the following:
v Pause the system.
v Set the NZ_USER and NZ_PASSWORD environment variables to a user who has
permission to pause the system.
v Set NZ_USER to a user who has permission to pause the system, and cache that
user's password.
If you run the nzhostbackup command, then change a user's password and then
run the nzhostrestore command, the old password is replaced.

Syntax
The nzhostbackup command uses the following syntax:

nzhostbackup [-g GRACE_PERIOD] [-D DATA_DIR] [--nokeydb] [-sklm] FILE
nzhostbackup -h
Inputs
The nzhostbackup command takes the following inputs:

Table A-13. The nzhostbackup input options
Input Description
-h Displays online help for this command.
-g GRACE_PERIOD Specifies the maximum time to wait (in seconds) for
queries (or any system action, such as a load) to finish
before the system begins the backup. After the system
waits this amount of time, it cancels any remaining
queries and starts the backup. The default is 60 seconds.
-D DATA_DIR Specifies the path name of the system data directory to
back up. The default is the NZ_DATA_DIR, which is
usually /nz/data.
--nokeydb Specifies not to back up the keystore for self-encrypting
drives (IBM PureData System for Analytics N3001
systems).
--sklm If the host uses the IBM Security Key Lifecycle Manager
keystore to hold the SED key, retrieves the AEKs from
ISKLM and creates a GSKit keystore, which is included
in the host backup. Cannot be used in combination with
the --nokeydb option.
FILE Specifies the path name of the archive file that you want
to create. This file is a compressed tar file.
Description
The nzhostbackup command does the following:

Privileges required
You must specify a database user account that has Manage System
privileges.
Common tasks
You can run the nzhostbackup command when the system is online,
paused, offline, or stopped.
v If you run the nzhostbackup command while the system is online, the
nzhostbackup command pauses the system for the duration of the
backup.
v All currently running queries run to completion before the backup
begins, subject to the time_out value you specify, or 60 seconds if you do
not specify time_out. The system queues new queries until the backup
completes.
Determine the data directory
The nzhostbackup command uses the same logic as the nzstart command to
determine the data directory. The command uses the following settings in order:

1. -D on command line
2. NZ_DATA_DIR environment variable
3. NZ_DIR/data, where NZ_DIR is determined from NZ_KIT_DIR or relative to the
location of the script itself.
In addition, if you unset NZ_DIR and NZ_KIT_DIR and then run the nzhostbackup
backup_dir command, the command works because it internally determines the
location of NZ_KIT_DIR, NZ_DIR and NZ_DATA_DIR.
Usage
The following provides some same usage:

v To back up the default data directory, enter:
nzhostbackup /home/host/backup.tar.gz
v To specify a timeout period of 5 minutes, rather than the default 60 seconds,
enter:
nzhostbackup -g 300 /home/host/backup.tar.gz
v To specify a timeout period of 5 minutes, rather than the default 60 seconds,
enter:
nzhostbackup -g 300 /home/host/backup.tar.gz
Related concepts:
“Create a host backup” on page 13-10
You use the nzhostbackup command to back up the files in the IBM Netezza data
directory.
Related reference:
“The nzhostrestore command”
metadata.
The nzhostrestore command

metadata.
The nzbackup and nzrestore commands also back up the system catalog and host
data, but in situations where a Netezza host server fails but the SPUs and their
data are still intact, you can use the nzhostrestore command to quickly restore the
catalog data without reinitializing the system and restoring all of the databases.
For more information, see “Host backup and restore” on page 13-9.
Note: After you run nzhostrestore, the system reverts to the mirroring roles (that
is, topology) it had when it was last online.
After you use the nzhostrestore command, you cannot run an incremental backup
on the database; you must run a full backup first.
Syntax
The nzhostrestore command uses the following syntax:

nzhostrestore [-f] [-D DATA_DIR] [-catverok] FILE
nzhostrestore -h

Inputs
The nzhostrestore command takes the following inputs:

Table A-14. The nzhostrestore input options
Input Description
FILE Specifies the archive file that is created by the nzhostbackup
command that you want to restore.
nzhostrestore -h Displays online help for this command.
nzhostrestore -D Specifies the Netezza data directory to restore. The default is
DATA_DIR the data directory (NZ_DATA_DIR), which is usually
/nz/data.
Options
The nzhostrestore command uses the following options:

Table A-15. The nzhostrestore options
Option Description
-catverok Skips the catalog verification checks. By default, the command checks the
catalog version of the current /nz/data directory and the archived data
directory. If the catalog versions are not the same, or if the command
cannot detect the catalog version of the current data directory, the
command exits with an error message similar to the following message:
Unable to determine catalog version of data directory at
/nz/data.1.0, hence exiting. If you are sure that catalog
versions of current and that of the archived data
directory are same, use the command-line switch -catverok
to skip this check.
Use caution with this switch; if you are not sure that the catalog versions
are the same, do not bypass the checks. Contact Netezza Support for
assistance.
-D data_dir Specifies the data directory to restore (default /nz/data).
-f Specifies force, which causes the command to accept the defaults for
prompts and confirmation requests. The prompts displays at the
beginning and end of the program.
Restore host data archived Thu May 25 11:24:58 EDT 2006?
(y/n) [n]
Warning: The restore will now rollback spu data to Thu
May 25 11:24:58 EDT 2006. This operation cannot be
undone. Ok to proceed? (y/n) [n]
Description
The nzhostrestore command does the following:

Privileges required
You must specify a database user account that has Manage System
privileges.
Common tasks
The nzhostrestore command pauses the system before it starts the restore.

After a restoration, any SPUs that previously had a role other than active,
spare, or failed are assigned to the role mismatched. The previous roles
include assigned, inactive, or mismatched.
For more information about SPU roles, see “Hardware roles” on page 5-8.
Notes
If tables are created after the host backup, the nzhostrestore command marks
these tables as “orphaned” on the SPUs. They are inaccessible and consume disk
space. The nzhostrestore command checks for these orphan tables and creates a
script that you can use to drop orphaned user tables.
For example, if you ran the nzhostrestore command and it found orphaned tables,
you would see the following message:
Checking for orphaned SPU tables...
WARNING: found 2 orphaned SPU table(s).
Run 'sh /tmp/nz_spu_orphans.18662.sh' after the restore has completed
and the system is Online to remove the orphaned table(s).
To drop the orphan tables, run the script /tmp/nz_spu_orphans.18662.sh.
Usage
The following provides sample usage:

v To restore the default data directory, enter:
nzhostrestore /home/host/backup.tar.gz
Related concepts:
“Restore the host data directory and catalog” on page 13-10
You use the nzhostbackup and nzhostrestore commands to back up and restore
the files in the IBM Netezza data directory.
Related reference:
“The nzhostbackup command” on page A-24
“The nzhw command”
The nzhw command

The nzhw command replaces the nzspu and nzsfi commands. Use this command to
show information about the system hardware and activate or deactivate
components, locate components, or delete them from the system.
Syntax
The nzhw command has the following syntax:

nzhw [-h|-rev] [-hc] subcmd [subcmd options]

Inputs
The nzhw command takes the following inputs:

Table A-16. The nzhw input options
Input Description
nzhw activate -id hwId Makes a specified hardware component such as a SPU or a
disk available as a spare from a non-Active role (such as
Failed or Mismatched). Specify the hardware ID of the SPU
or disk that you want to activate.
Note: In some cases, the system might display a message
that it cannot activate the disk yet because the SPU has not
finisedh an existing activation request. Disk activation
usually occurs quickly, unless there are several activations
taking place at the same time. In this case, later activations
wait until they are processed in turn.
nzhw deactivate -id hwId Changes the role of a spare SPU to Inactive, which makes
[-force] the component unavailable to the system. Attempting to
deactivate an active component that has a role other than
Spare results in an error.
Specify the hardware ID of the spare SPU that you want to

deactivate. Include the -force option if you do not want to
be prompted with a confirmation.
nzhw failover -id hwId Changes the role of a SPU or disk to Failed, which makes
[-force] the component unavailable to the system. If you fail a SPU,
the system reassigns the data slices that are managed or
owned by that SPU to the other active SPUs in the chassis.
Failing a disk causes the system to use the disk mirror
partition as the primary partition. For more information
about the processing of a failover, see “Failover information”
on page A-32.
Specify the hardware ID of the spare SPU or disk that you

want to fail. Include the -force option if you do not want to
be prompted with a confirmation.
nzhw locate [-id hwId | Identifies a component and its location in the system.
-all] [-off]
When used with -id, the command displays a string for the
physical location of the hardware component identified by
the hwid value. For SPUs, disks, and disk enclosures, the
command also turns on its indicator LED so that a
technician at the IBM Netezza system can find the
component in the rack.
When used with -all, the command turns on the indicator

LEDs of all the SPUs and disks in the system.
The -off option turns off the indicator LED for the specified
component or all SPUs and disks.
Note: If the hardware type specified for the command does
not have an LED, the command only displays the location
string for that component.

Table A-16. The nzhw input options (continued)
Input Description
nzhw reset {-id hwId | Resets the specified hardware component. Currently, only a
-all | -spa spaId } SPU is supported as a reset target by using this command.
[-force]
You can specify one of the following target options:
v -id hwid to reset a particular SPU designated by its
hardware ID
v -all to reset all SPUs in the system
v -spa spaId to reset all the SPUs in the specific SPA
identified by its SPA ID.
Include the -force option if you do not want to be

prompted with a confirmation.
nzhw delete -id hwId Deletes the specified hardware component from the system
[-force] database. The hardware component must have a role of
Mismatched, Failed, or Inactive. A hardware component in
any other role results in an error. A SPU or disk can be
identified by its unique hardware ID.
Specify the hardware ID of the component that you want to

delete. Include the -force option if you do not want to be
prompted with a confirmation.
nzhw listTypes Displays a list of the valid hardware types that you can
input for the nzhw show -type hardwareType command.
nzhw show [options] Displays information about the specified hardware
components. If you do not specify any options, the
command displays a list of every component in the system
and its Type, Hardware ID (HW ID), Location, Role, and
State. You can specify one or more options (described as
follows) to show specific output.
nzhw show -caCertFile Specifies the path name of the root CA certificate file on the
client system. This argument is used by Netezza clients who
use peer authentication to verify the Netezza host system.
The default value is NULL, which skips the peer
authentication process.

Table A-16. The nzhw input options (continued)
Input Description
nzhw show -securityLevel Specifies the security level that you want to use for the
session. This option does not apply when you are logged in
to the Netezza system and running the command. The
argument has four values:
preferredUnsecured
This value is the default value. Specify this option
when you would prefer an unsecured connection,
but you accept a secured connection if the Netezza
system requires one.
preferredSecured
connection to the Netezza system, but you accept
an unsecured connection if the Netezza system is
configured to use only unsecured connections.
onlyUnsecured
Specify this option when you want an unsecured
connection to the Netezza system. If the Netezza
system requires a secured connection, the
connection is rejected.
onlySecured
connection to the Netezza system. If the Netezza
system accepts only unsecured connections, or if
you are attempting to connect to a Netezza system
that is running a release before 4.5, the connection
is rejected.
nzhw show -id hwId Displays information only about the component with the
[-detail] specified hardware ID. Include the -detail option for more
information such as serial number, hardware version, and
more details.
nzhw show -spa [spa id] Displays information about the hardware components which
are owned by a particular S-Blade in SPA.
nzhw show -type hwType Displays information only about the components of the
[-detail] specified hardware type. To display the supported hardware
types, use the nzhw listTypes command.
If the system has no hardware of the specified type, or if the

type is not supported, the command displays a message.
Include the -detail option for more information such as
serial number, hardware version, and more details.
nzhw show -issues Displays information about hardware components that are
[-detail] reporting problems. The command displays a list of
components to investigate and their Type, Hardware ID (HW
ID), Location, Role, and State. Include the -detail option for
more information such as serial number, hardware version,
and more details.

Options
The nzhw command takes the following options:

Table A-17. The nzhw options
Option Description
-host hostname Specifies the host name or IP address of the Netezza
system.
-timeout secs Specifies the amount of time in seconds to wait for the
command to complete before it exits with a timeout
error. Default is 300.
Description
The nzhw command has the following description.

Privileges required
For nzhw show operations, your database user account does not require any
special privileges. However, for nzhw commands to manage the hardware
such as activate, deactivate, and others, your database user account must
have Manage Hardware privilege.
Common tasks
Use the nzhw command is the primary command for managing and
displaying information about the Netezza system and its hardware
components.
Failover information
When you use the nzhw command to fail over a component, the command checks
the system and the affected component to make sure that the command is
appropriate before proceeding. Currently, the command operates only on SPUs and
disks.
For example, if you try to fail over an active component that does not have an
available secondary component (such as SPUs that can take ownership of the data
slices that are managed by the SPU that you want to failover, or an active mirror
for the disk that you want to fail over), the command returns an error. Similarly, if
you try to fail over a component that is not highly available, the command returns
an error.
Usage

v To activate a failed or mismatched SPU identified as ID 1003, use the following
command:
nzhw activate -id 1003 -u user -pw password
v To fail over the SPU identified by hardware ID 1084, use the following
command:
nzhw failover -id 1084
v To locate the SPU identified by hardware ID 1061, use the following command:

nzhw locate -id 1061
Turned locator LED ’ON’ for SPU: Logical Name:’spa1.spu5’ Physical
Location:’1st Rack, 1st SPA, SPU in 5th slot’.
v To light the locator LED of all the SPUs and disks, use the following command:
nzhw locate -all
Turned locator LED ’ON’ for all Spus and Disks.
v To reset the SPU identified by hardware ID 1084, use the following command:
nzhw reset -id 1084
v To reset all the SPUs in the SPA identified by ID 1002, use the following
command:
nzhw reset -spa 1002
v To delete the disk that is identified by hardware ID 1081, use the following
command:
nzhw delete -id 1081
v To show the hardware information for the system, use the following command:
nzhw show
------------- ----- --------------------- ------ ------ ----------
Rack 1001 rack1 Active None N/A
SPA 1002 spa1 Active None N/A
SPU 1003 spa1.spu7 Active Online N/A
DiskEnclosure 1004 spa1.diskEncl4 Active Ok N/A
Fan 1005 spa1.diskEncl4.fan1 Active Ok N/A
PowerSupply 1009 spa1.diskEncl4.pwr1 Active Ok N/A
PowerSupply 1010 spa1.diskEncl4.pwr2 Active Ok N/A
Disk 1011 spa1.diskEncl4.disk1 Active Ok N/A
Disk 1012 spa1.diskEncl4.disk2 Active Ok N/A
...
The sample output that is shown for this command is truncated for the
documentation.
v To show specific information for a component such as the SPUs, use the
following command:
nzhw show -type spu
----------- ----- ---------- ------ ------ --------
v To show the hardware issues that are reported for the system, use the following
command:
nzhw show -issues
Type HW ID Location Role State Security
---- ----- --------------------------- ------ ----- --------
Disk 1041 rack1.spa1.diskEncl2.disk12 Failed Ok N/A
v To list the supported hardware types for the nzhw show -type hwType command,
use the following command:
nzhw listTypes
Description Type
------------------- --------
rack rack
spa spa
spu spu

diskenclosure diskencl
disk disk
fan fan
blower blower
power supply pwr
mm mm
store group storeGrp
ethernet switch ethsw
host host
SAS Controller SASController
host disk hostDisk
database accelerator dac
Related concepts:
“Display hardware components” on page 5-2
You use the nzhw show command to display information about the hardware
components of your IBM Netezza system. You can also use the NzAdmin tool or
IBM Netezza Performance Portal interface to display hardware information and
status.
“Manage SPUs” on page 5-20
Snippet Processing Units (SPUs) or S-Blades are hardware components that serve
as the query processing engines of the IBM Netezza appliance.
“Manage disks” on page 5-23
The disks on the system store the user databases and tables that are managed and
queried by the IBM Netezza appliance. You can use the nzhw command to activate,
failover, and locate a disk, or delete disk information from the system catalog.
Related reference:
the system.
“The nzhostrestore command” on page A-26
metadata.
The nzkey command

Use the nzkey command to manage and apply the authentication keys to auto-lock
the SEDs for the host drives or the storage array drives that are managed by the
SPUs.
Syntax
The nzkey command has the following syntax.

nzkey [-h | -rev] [-hc] <subcmd> [<subcmd options>]
nzkey change {-spukey | -hostkey} -file <file> -backupDir <path>

nzkey check {-spukey | -hostkey} [-progress]
nzkey create {-spukey] -hostkey} -file <file> -backupDir <path>
nzkey extract -label <label> -file <file>
nzkey generate {-spukey | -hostkey} -file <file>
nzkey list [-spukey | -hostkey]
nzkey dump
nzkey resume [-backupDir <path>]

Inputs
The nzkey command takes the following inputs:

Table A-18. The nzkey input options
Input Description
change Changes the host or SPU AEK. The system
must be in the Paused or Offline state to
change a SPU key, or in the Stopped state to
change a host key.
check Checks the status of the keys on the host or
the SPUs or both. The command displays
messages about whether the system is
AEK-enabled or not, whether the AEKs for
the host or SPUs are set, and the progress of
the key enablement if keys are being set or
changed.
create Applies the host or SPU and/or host AEK
and auto-locks the SEDs. You should not
use this command option to auto-lock the
drives. If you want to auto-lock your drives,
contact IBM Support for assistance. There is
a process for auto-locking the SEDs and
ensuring that the keys and drives are locked
correctly.
extract Extracts the host or SPU keys defined in the
keystore. You can use this option to extract
a specific host key or SPU key to a file
specified in the -file option. This operation
can be performed at any time as long as a
key change operation is not in progress.
generate Generates a host or SPU key. The generate
-spukey option generates an AES256 key to
the file specified in -file and can be
performed as long as a key change
operation is not in progress. The result can
be used as a SPU key. The generate
-hostkey option generates a host key that
meets the constraints enforced by the host
RAID controller.
list Lists the host or SPU key labels to standard
output. The key values are not printed. This
operation can be performed as long as a key
change operation is not in progress.
dump When the system is configured to use IBM
Security Key Lifecycle Manager server to
manage the AEKs, saves the ISKLM keys
into a local GSKit keystore. You use this
option if you are planning to return to a
local GSKit keystore to manage the AEKs
for your N3001 appliance. This option
displays an error when the system is
configured to use a local GSkit keystore.

Table A-18. The nzkey input options (continued)
Input Description
resume Resumes an interrupted host key operation.
If the process to apply the host keys is
paused or interrupted for any reason, you
can use the resume option to restart the
process to apply the AEK.
If you run the command and the system

detects that there is no work to resume, the
command displays the message Nothing to
resume.
Options
The nzkey command takes the following options:

Table A-19. The nzkey input options
Input Description
-hostkey Performs the requested operation for the
host AEK.
-spukey Performs the requested operation for the
SPU AEKs.
-file <file> Specifies the file that you want to write a
host or SPU key to (in the case of generate
or extract) or from which you want to read
a key value (for create or change
operations).
-label <label> Specifies the label of the key to extract such
as spuaek, spuaekOld, hostkey1,
hostkey1Old, hostkey2 or hostkey2Old.
-backupDir <path> Specifies a pathname to save the current
keystore as a backup.
-progress When used with nzkey check -spukey, if a
key change is in progress, the command
displays and updates the progress
percentage until the key change completes.
Description
You use the nzkey command to create and manage the authentication keys (AEKs)
for the SED drives in the host and in the storage arrays of the IBM PureData
System for Analytics N3001 appliances. The command logs information when it
runs to the /nz/kit/log/keydb/keydb.log.
The nzkey command is installed in /nz/kit/bin/adm. You must be logged in to the

NPS system as the root user to run the command. You must either change to the
adm directory and run the command from that location or have that directory in
your root user's path to run the command.

Usage
v To generate a hostkey:
[root@nzhost-h1 ~]# /nz/kit/bin/adm/nzkey generate -hostkey -file /tmp/my_hostkey
Host key written to file
v To list the key labels:
[root@nzhost-h1 adm]# /nz/kit/bin/adm/nzkey list
hostkey1
hostkey1Old
hostkey2
hostkey2Old
spuaek
spuaekOld
The nzkeydb command

Use the nzkeydb command to create a keystore for securely storing the SED AEKs.
Syntax
The nzkeydb command has the following syntax.

nzkeydb create -pw <password> [-sklm]
nzkeydb changepw -new_pw <password> -pw <password> [-sklm]
nzkeydb validate [-sklm]
Inputs
The nzkeydb command takes the following inputs:

Table A-20. The nzkeydb input options
Input Description
create Creates a new local keystore in the /nz/var/keystore
directory. This command fails if there is already a keystore
present in the directory.
If you include the -sklm option, the command creates a

/nz/var/keystore directory if one does not already exist and
sets the correct permissions.
changepw Changes the password for accessing the local keystore. You
must specify the new password and the current password to
change the password.
If you include the -sklm option, the command does not take
any action since keystore passwords are not used when the
system is configured to use IBM Security Key Lifecycle
Manager (ISKLM) for managing AEKs.

Table A-20. The nzkeydb input options (continued)
Input Description
validate Performs a check for a local keystore to validate the
following:
v The keystore is empty if there are no keys currently
defined or in use.
v The keystore has keys to match the hardware components
that are configured to use keys.
v There keystore contains the correct set of labels for the
authentication keys. That is, there are labels for the host
keys as well as the SPU key. If a key has been changed,
the store also contains the previous key as well as the
current key.
Important: If the validation fails, contact IBM Support
immediately to troubleshoot the problems with the keystore.
The problem could prevent the disks from being read the
next time a disk or system is powered on.
If you include the -sklm option, the command checks to

make sure that the keystore directory is set up correctly.
Options
The nzkeydb command takes the following options:

Table A-21. The nzkeydb input options
Input Description
-new_pw <new_password> For the changepw option, specifies the new
password for the keystore.
-pw <password> Specifies the current password to the
keystore.
-sklm Indicates that the system uses an IBM
Security Key Lifecycle Manager (ISKLM)
server to manage AEKs. See the input
descriptions earlier in the topic for create,
changepw, and validate.
Description
You use the nzkeydb command to create a keystore that stores and manages the
current and previous host and SPU AEKs for the IBM PureData System for
Analytics N3001 appliances. The command logs information when it runs to
/nz/kit/log/keydb/keydb.log.
The nzkeydb command is installed in /nz/kit/bin/adm. You must be logged in to

the NPS system as the root user to run the command. You must either change to
the adm directory and run the command from that location or have that directory in
Usage
v To create a new keystore:

[root@nzhost-h1 ~]# /nz/kit/bin/adm/nzkeydb create -pw password
DB creation successful
v To validate the keystore:
[root@nzhost-h1 adm]# /nz/kit/bin/adm/nzkeydb validate
Validation succeeded
The nzkeybackup command

Use the nzkeybackup command to create a backup copy of the SED AEK key store.
Syntax
The nzkeybackup command has the following syntax.

nzkeybackup [-h]
nzkeybackup [-sklm] <file>
Options
The nzkeybackup command takes the following options:

Table A-22. The nzkeybackup input options
Input Description
<file> Specifies the file name for the compressed
tar file backup of the key store.
-sklm Obtains the keys from the IBM Security Key
Lifecycle Manager server to store them in
the specified file.
Description
You use the nzkeybackup command to create a compressed tar file backup of the
key store. The command validates the key store before it creates the backup to
alert you to any problems. You should create a backup of the key store after you
change the AEKs. As a best practice, you should store the backup tar file in a safe
location that is not on the NPS system as a precaution in the event of a disk
problem on your appliance. The command logs information when it runs to
/nz/kit/log/keydb/keydb.log.
The nzkeybackup command is installed in /nz/kit/bin/adm. You must be logged in

to the NPS system as the root user to run the command. You must either change to
the adm directory and run the command from that location or have that directory in
Important: Make sure that you control access to the nzkeybackup and the
nzhostbackup compressed tar files because they contain the key store. If access is
not restricted, the contents of the key store could be read by an authorized Netezza
operating system user. Although the key store is encrypted, users who have access
to the backup files could read the key store with the nzkey command.
Usage
To create a key store backup file:

[root@nzhost-h1 ~]# /nz/kit/bin/adm/nzkeybackup /nz/var/keybackup.tar.gz

The nzkeyrestore command
Use the nzkeyrestore command to restore a backup copy of the SED AEK key
store.
Syntax
The nzkeyrestore command has the following syntax.

nzkeyrestore [-h]
nzkeyrestore [-f] <file>
Options
The nzkeyrestore command takes the following options:

Table A-23. The nzkeyrestore input options
Input Description
<file> Specifies the file name for the backup key
store that you want to restore.
[-f] Does not prompt for confirmation before
restoring the key store from the backup tar
file.
Description
You use the nzkeyrestore command to replace or restore a key store from a
backup file. Typically you would use this command if your key store was
corrupted or deleted from the NPS host. The NPS system must be in the Stopped
state before you can restore the key store. The command logs information when it
runs to the /nz/kit/log/keydb/keydb.log.
The nzkeyrestore command is installed in /nz/kit/bin/adm. You must be logged

in to the NPS system as the root user to run the command. You must either change
to the adm directory and run the command from that location or have that directory
in your root user's path to run the command.
Usage
To restore a key store from a backup tar file:

[root@nzhost-h1 ~]# /nz/kit/bin/adm/nzkeyrestore /nz/var/keybackup.tar.gz
nzkeyrestore: Ready to restore /nz/var/keybackup.tar.gz: gzip compressed data,
from Unix, last modified: Mon Aug 11 16:02:55 2014
OK to proceed [y/n]? y
nzkeyrestore: ’/nz/var/keybackup.tar.gz’ restored correctly
The nzkmip command

Use the nzkmip command on IBM PureData System for Analytics N3001 appliances
to manage IBM Security Key Lifecycle Manager AEK configuration and setup.
Syntax
The nzkmip command has the following syntax.

nzkmip [-h | -rev] [-hc] subcmd [subcmd options]
nzkmip get {-label label | -uuid uuid} [-file file]
nzkmip populate [-keystore keystore]
nzkmip test -label label {-key key | -file file} [-updateDb]
Inputs
The nzkmip command takes the following inputs:

Table A-24. The nzkmip input options
Input Description
get Extracts the specified key defined in the ISKLM keystore.
You must specify a label or the ISKLM UUID for the key
that you want to extract. The command displays the AEK
on the screen, or you can use the -file option to store the
command output in a file.
populate Reads the keys from a local keystore and adds those keys
to the ISKLM keystore for management. The command
uses the default local keystore in the /nz/var/keystore
directory unless you specify an alternate location with the
-keystore option.
test Tests the ISKLM key storage and retrieval operations. You
must specify a label for the test key, and specify the key or
the file that holds the key. The command stores the input
label and key in the ISKLM server and then retrieves the
stored key by its ISKLM-supplied UUID for comparison
against the input key to confirm that they are the same. If
the key comparison fails, the problem may be an issue with
the processes that store and return the key at the ISKLM
server.
Options
The nzkmip command takes the following options:

Table A-25. The nzkmip input options
Input Description
-label label Specifies the label of the key to get or to test
such as spuaek, spuaekOld, hostkey1,
hostkey1Old, hostkey2 or hostkey2Old.
With the nzkmip test command, you could
specify any label name for the test
operations.
-uuid uuid Specifies the ISKLM-supplied UUID value
of the key to get/extract.
-file file For the get subcommand, specifies the file
to which you want to write the host or SPU
key. For the test subcommand, specifies the
file that contains the test key that you want
to use.
-keystore keystore Specifies the fully qualified pathname of the
local keystore from which you are obtaining
the keys to send to (populate) the ISKLM
server. The default is /nz/var/keystore.

Table A-25. The nzkmip input options (continued)
Input Description
-key key When used with the nzkmip test command,
specifies the key that you want to test for
the storage and retrieval from the ISKLM
server.
-updateDb When used with the nzkmip test command,
causes the test key to be inserted as a row
in the _t_kmip_mapping table to confirm
that the key is stored in the NPS database.
If you use this option, you should delete the
row from the table after the test is complete.
Description
You use the nzkmip command to extract, populate, and test the ISKLM server
connection and management for the authentication keys (AEKs) that are used for
the SED drives in the host and in the storage arrays of the IBM PureData System
for Analytics N3001 appliances.
The nzkmip command is installed in /nz/kit/bin/adm. You must be logged in to the

NPS system as the root user to run the command. You must either change to the
adm directory and run the command from that location or have that directory in
Usage
v To extract a key:
[root@nzhost ~]# /nz/kit/bin/adm/nzkmip get
-uuid KEY-70a07fcc-1a01-4628-979c-bd75fe5e4557
Key Value : t7Nº×nq¦CÃ<"*"ºìýGse»¤;|%
v To test a key:
[root@nzhost ~]# /nz/kit/bin/adm/nzkmip test -label spuaek
-file /tmp/new_spukey.pem
Connecting to SKLM server at tls://1.2.3.4:5696
Success: Connection to SKLM store succeeded
The nzload command

Use the nzload command to load ASCII data into database tables.
For a complete description of the nzload command and how to load data into the
IBM Netezza system, see the IBM Netezza Data Loading Guide.
Related reference:
“The nzconvert command” on page A-10
Use the nzconvert command to convert between any two encodings, between these
encodings and UTF-8, and from UTF-32, UTF-16, or UTF-8 to NFC, for loading
The nznpssysrevs command

Use the nznpssysrevs command to display revision information for the installed
IBM Netezza software and host information.

The nznpssysrevs command summarizes several important software revisions and
appliance revisions. You can use the command to quickly display the HPF, FDT,
NPS and Red Hat revisions, the host model, and the IP configuration settings for
the appliance.
Syntax
The nznpssysrevs command uses the following syntax:

nznpssysrevs [-h]
Inputs
The nznpssysrevs command has only a -h input option to display the usage for
the command.
Description
The nznpssysrevs command displays the following information

Privileges required
You must be able to log on to the Netezza system as the nz user account.
Common tasks
Use the nznpssysrevs command to display important revision information
about the system.
Usage

v To display the revision information for a system:
nznpssysrevs HPF Version : 5.1
FDT Version : FDT 4.1
NPS Version : Release 7.2.0.0 [Build 38013]
RedHat Ver : Red Hat Enterprise Linux Server release 6.2 (Santiago)
HOST TYPE : System x3650 M3 -[7945AC1]-
Config IP : Not set (address:10.0.0.2)
The nzpassword command

Use the nzpassword command to manage passwords. The primary use is to store
your password locally and thus use IBM Netezza CLI commands without having
to type your password on the command line.
Syntax
The nzpassword command uses the following syntax:

nzpassword subcmd [subcmd options]
Inputs
The nzpassword command takes the following inputs:

Table A-26. The nzpassword input options
Input Description
nzpassword add options Adds a locally cached password.
nzpassword delete options Removes the locally cached passwords.

Table A-26. The nzpassword input options (continued)
Input Description
nzpassword resetkey options In normal system operation and without any options,
this command creates a unique client key and
re-encrypts the user passwords with the new key.
If you have an existing password file that was created

by using older (pre-Release 6.0 or pre-Release 4.6.6
clients), this command also converts the old
Blowfish-encrypted passwords to AES-256-encrypted
passwords. The client key that is used for the encryption
is auto-generated. For more information about using
encrypted passwords, see “Encrypted passwords” on
page 2-13.
nzpassword show Displays cached passwords.
Options
The nzpassword command uses the following options:

Table A-27. The nzpassword options
nzpassword add -host name Specifies a host name or IP address
[NZ_HOST].
-u user Specifies the Netezza user name
[NZ_USER].
-pw password Specifies the user password
[NZ_PASSWORD].
-timeout secs Specifies how long to wait for the
command to time out (in seconds) before
returning an error. The default is 300.
nzpassword delete -u user Specifies the database user name
[NZ_USER].
-host name Specifies a host name or IP address
[NZ_HOST].
-all Deletes all cached passwords.
nzpassword resetkey -none If you must downgrade to a previous
release, or if your client users must
support mixed releases of clients, you
can use the nzpassword resetkey -none
command to convert AES-256-encrypted
passwords to Blowfish-encrypted
passwords. For more information about
using encrypted passwords, see
“Encrypted passwords” on page 2-13.
nzpassword show N/A Shows the cached passwords for the
current user. The command displays the
message No cached passwords if there is
none to display.
Description
The nzpassword command does the following:

Privileges required
You must be logged in as nz or any valid Linux account for the Netezza
system.
Common tasks
Use the nzpassword command to store a local version of your password.
Related commands
Use with the CREATE USER or ALTER USER command.
Usage

v To add a password, enter:
nzpassword add -u user -pw password -host nzhost
v To delete a password, enter:
nzpassword delete -u user -host nzhost
v To show the command options, enter:
nzpassword show
v To reset the client key and create new encryptions of the passwords, enter:
nzpassword resetkey
The nzreclaim command

Use the nzreclaim command to recover disk space that is used by updated or
deleted data by using the GROOM TABLE command.
Note: Starting in release 6.0, the SQL GROOM TABLE command replaces the
nzreclaim command. The nzreclaim command is now a “wrapper” that calls the
GROOM TABLE command to reclaim space. if you have existing scripts that use
the nzreclaim command, those scripts continue to run, although some of the
options might be deprecated since they are not used by GROOM TABLE. You
should use the GROOM TABLE command in your scripts.
Syntax
The nzreclaim command uses the following syntax:

nzreclaim [-h|-rev] [options]
Inputs
The nzreclaim command takes the following inputs:

Table A-28. The nzreclaim input options
Input Description
nzreclaim -backupset options Specifies the backup set to use to find the rows that can
be reclaimed. By default, nzreclaim uses the most recent
backup set, but you can use this option to specify a
different backup set for the reclaim-backup
synchronization. If you specify NONE, the command
reclaims all rows regardless of whether they were saved
in a backup set.
nzreclaim -blocks options Removes empty blocks at the beginning of the table.

Table A-28. The nzreclaim input options (continued)
Input Description
nzreclaim -records options Removes deleted records from a database or table.
nzreclaim -startEndBlocks Removes empty blocks from the beginning and the end
options of the table.
Options
The nzreclaim command takes the following options:

Table A-29. The nzreclaim options
Option Description
-host name Specifies host name or IP address [NZ_HOST].
-db database Grooms one or all tables in a specific database [NZ_DATABASE]. You
can use the -t option to specify a table, or -allTbls to groom all the
tables.
-allDbs Grooms all databases. You can use the -t option to specify a table to
groom in all databases, or -allTbls to groom all tables in all
databases.
-schema schema Specifies the schema in which to groom the tables if your Netezza
system supports multiple schemas. You can use this option with the
-db option, but not with the -allDbs option. If you specify -schema
and -allTbls, the command grooms all the tables in the schema. If
you do not specify a schema, the system uses NZ_SCHEMA to
identify the schema. If NZ_SCHEMA is not set, the system uses the
default schema for the database.
-t tbl Grooms the specified table name. You must specify the database
where the table resides. You can use the -db option to groom all the
tables in one database. Use this with the -db and -schema options to
groom the table in one schema. Use this with the-allDbs to groom
that table in all the databases.
-allTbls Grooms all the tables in the specified database or schema. You use
this with the -db option to groom all the tables in one database, or
-allDbs to groom all tables in all databases.
Description
The nzreclaim command does the following:

Privileges required
You must have the Groom object privilege for the tables that you want to
reclaim or reorganize.
Common tasks
Use the nzreclaim command to groom tables and recover disk space.
Specify either record-level or block-level reclamation.
v To remove all unused records throughout the table, specify nzreclaim
-records.
v To remove blocks from the beginning of the table, specify nzreclaim
-blocks.

v To remove unused blocks from the beginning and end of the table,
specify nzreclaim ⌂startEndBlocks.
Related commands
Use the TRUNCATE command to quickly delete all rows in a table without
requiring a GROOM TABLE afterwards.
Usage

v To run a record-level groom on all the tables in the emp database, enter:
nzreclaim -u admin -pw password -db emp -t mytable
nzsql -u admin -pw password emp -c"groom table mytable " 2>&1
NOTICE: Groom processed 392131 pages; purged 2342 records; scan
size unchanged; table size unchanged.
GROOM RECORDS ALL
v To run a block-level groom on all the tables in the emp database in schema
acme, enter:
nzreclaim -u admin -pw password -blocks -db emp -schema acme
v To run a block-level groom and remove blocks from the beginning and end of
the table, enter:
nzreclaim -u user -pw password -startEndBlocks -db emp
Related concepts:
“GROOM and the nzreclaim command” on page 12-20
The nzrestore command

Use the nzrestore command to restore your database from a backup.
Related concepts:
“The nzrestore command” on page 13-22
The nzrev command

On Linux systems, you can use the nzcontents command to display the revision
and build number of all the executable files, plus the checksum of binaries.
Syntax
The nzrev command uses the following syntax:

nzrev [-h|-rev] [options]

Inputs
The nzrev command takes the following inputs:

Table A-30. The nzrev input options
Input Description
nzrev -dirSuffix Displays the directory suffix form. For example, for
Release 5.0 Beta1, the output is:
5.0.B1
nzrev -rev Displays the entire revision string, which includes all
fields (such as variant and patch level). For example:
5.0.0-0.B-1.P-0.Bld-7581
Entering the nzrev -rev command on the host is the

same as entering the nzsystem showRev -u user -pw
password -host host command on the client system. If
you use only the nzrev command on the client, the
command displays the revision of the client kit.
nzrev -shortLabel Displays an abbreviated revision label. For example:
5.0.6
nzrev -buildType Displays the type of build. Typical values are opt or
dbg.
Description
The nzrev command does the following:

Privileges required
You do not need special privileges to run the nzrev command.
Common tasks
Use the nzrev command to display the revision level of Netezza software
components.
Usage

v To display the directory suffix form, enter:
nzrev -dirSuffix
5.0.6.P1
v To display the revision level, enter:
nzrev -rev
Release 5.0.6 (P-1) [Build 11294]
v To display the short form, enter:
nzrev -shortLabel
5.0.6
Related concepts:
“Display the Netezza software revision” on page 7-1
Related reference:
“The nzcontents command” on page A-9

The nzsession command
Syntax
The nzsession command uses the following syntax:

nzsession subcmd [subcmd options]
Inputs
The nzsession command takes the following inputs:

Table A-31. The nzsession input options
Input Description
nzsession abort options Abort a running user session.
nzsession abortTxn options Abort a user transaction.
nzsession listSessionTypes Lists the session types, which include the following
types:
v sql = database SQL session
v sql-odbc = database SQL session through ODBC
v sql-jdbc = database SQL session through JDBC
v load = data load session (nzload)
v client = client UI or CLI session
v bnr = Backup and restore session
v reclaim = database reclaim session (nzreclaim)
v loadsvr = data load session (deprecated loader)
nzsession priority options Changes priority of the current and all subsequent jobs
of this session.
nzsession show options Displays the list of current user sessions.

Options
The nzsession command takes the following options:

Table A-32. The nzsession options
All nzsession -u user Specifies the database user name [NZ_USER].
commands
Except listSessionTypes.
-caCertFile path Specifies the path name of the root CA certificate
file on the client system. This argument is used by
IBM Netezza clients who use peer authentication
to verify the Netezza host system. The default
value is NULL, which skips the peer
authentication process.
-securityLevel Specifies the security level that you want to use
level for the session. This option does not apply when
you are logged in to the Netezza system and
running the command. The argument has four
values:
preferredUnSecured
This value is the default value. Specify
this option when you would prefer an
unsecured connection, but you accept a
secured connection if the Netezza system
requires one.
preferredSecured
system, but you accept an unsecured
connection if the Netezza system is
configured to use only unsecured
connections.
onlyUnSecured
unsecured connection to the Netezza
system. If the Netezza system requires a
secured connection, the connection is
rejected.
onlySecured
system. If the Netezza system accepts
only unsecured connections, or if you are
attempting to connect to a Netezza
system that is running a release before
4.5, the connection is rejected.
-timeout secs Specifies the time to wait in seconds for the
command to complete. The default is 300.
nzsession abort, -id num Specifies the session ID.
and abortTxn
-force Does not prompt for confirmation.

Table A-32. The nzsession options (continued)
nzsession -id num Specifies the session ID.
priority
-high Changes the session priority to high.
-normal Changes the session priority to normal.
-low Changes the session priority to low.
-critical Changes the session priority to critical.
nzsession show -activeTxn Displays the active transactions for the system.
-maxColW chars Specifies the maximum number of characters to
print in a column. The default is 24.
Description
The nzsession command does the following:

Privileges required
The admin user has full privileges to display all session information, to
abort sessions and transactions, and to change the priority of a session.
Other database user accounts require no special privileges to use the
nzsession show command to see all the sessions that are currently active
on the system. However, non-admin users see asterisks instead of the user
name, client process Id (PID), database, and SQL command unless they
have List privilege on User (to see details about the user, client PID, and
SQL command) and List privilege on Database (to see the database name).
Users must have the Manage System privilege to change the priority of
sessions, and Abort privilege to abort sessions, transactions, or both.
Common tasks
Use the nzsession command to manage sessions. You cannot use a Release
5.0 nzsession client command to manage sessions on a Netezza system
that is running a release before 5.0.
How the command handles abort processing
When you run the nzsession abort command, the client manager uses the session
ID to abort the process.
For example, to abort an nzload session ID 2001, the system does the following:
1. The system sends the nzsession abort command to the client manager.
2. The client manager identifies which nzload session to abort.
3. The loadmgr sends the abort signal to the loadsvr and starts the timer.
4. The loadmgr waits the specified timeout value for the loadsvr to abort the
session. The command uses either the default value, or the timeout you specify
on the command line.
You can also abort active or idle nzsql sessions.

The nzsession show output
The following table describes the nzsession show output information. The admin
user can see all the data for sessions; other users can see all the sessions, but data
for user, database, client PID, and SQL command are hidden unless the user has
privileges to see that data.
Table A-33. Session information
Column Description
ID The ID of the session.
Type The type of session, which can be one of the following:
Client Client or UI session
SQL Database SQL session
Bnr Back up or restore session
Reclaim
Disk reclamation session.
User The name of the session owner.
Start Time The time the session was started.
PID The process identification number of the command you are running.
Database The name of the database.
Schema The name of the schema.
State The state of the session, which can be one of the following:
Idle The session is connected but it is idle and waiting for a SQL
command to be entered.
Active The session is running a command (usually applies to a SQL
session that is running a query).
Connect
The session is connected, but no commands have been issued.
Tx-Idle The session is inside an open transaction block (BEGIN
command) but it is idle and waiting for a SQL command to be
entered within the transaction.
Priority Name The priority of the session, which can be one of the following:
Critical The highest priority for user jobs.
High The session jobs are running on the high priority job queue.
Normal
The session jobs are running on the large or small job queue.
Low The lowest priority for user jobs.
Client IP The IP address of the client system.
Client PID The process identification number of the client system.
Command The last command executed.
Usage

v To show all sessions, enter:

nzsession show -u bob -pw password
Name
PID
----- ---- ----- ----------------------- ----- --------- ------ ------ --------
--------- ------ ------------------------
16049 sql ***** 24-Feb-13, 16:49:18 EST 14840 ***** ADMIN active normal
***** ***** *****
16054 sql bob 24-Feb-13, 16:49:31 EST 15093 SYSTEM ADMIN active normal
This sample output displays for a user (bob) who does not have permission to
see the details of the sessions on the system. Only the details for the sessions for
the user bob display. For a user who has List permission on user and database
objects, the output shows all the details:
nzsession show -u sysadm -pw password
Name
PID
----- ---- ----- ----------------------- ----- --------- ------ ------ --------
--------- ------ ------------------------
16049 sql DBUSR 24-Feb-13, 16:49:18 EST 14840 TPCH1 ADMIN active normal
127.0.0.1 14839 select * from lineitem
16054 sql bob 24-Feb-13, 16:49:31 EST 15093 SYSTEM ADMIN active normal
v To abort a session, enter:
nzsession abort -u user -pw password -host nzhost -id 1344
v To abort a transaction, enter
nzsession abortTxn -u user -pw password -host nzhost -id 437
v To list the types of sessions, enter:
nzsession listSessionTypes
v To change the session priority, enter:
nzsession priority -u user -pw password -host nzhost -id 437 -high
v To show all the active transactions, enter:
nzsession show -activeTxn
You can use the -activeTxn option to display the active sessions that will be
impacted by a state change (such as pausing -now) before you initiate the state
change.
Related concepts:
“The nzsession command” on page 12-23
You can use the nzsession command to view and manage sessions.
Related reference:
“View sessions” on page 12-24
You can use the nzsession command to display the list of current user sessions
and to list the session types.
“The nzevent command” on page A-14
“The nzstats command” on page A-60
Use the nzstats command to display statistics about system capacity, faults, and
performance.

The nzspupart command
Use the nzspupart command to display information about the SPU partitions on an
IBM Netezza system including status information and the disks that support the
partition.
Syntax
The nzspupart command has the following syntax:

nzspupart [-h|-rev] [-hc] subcmd [subcmd options]
Inputs
The nzspupart command takes the following inputs:

Table A-34. The nzspupart input options
Input Description
nzspupart show [options] Displays information about the specified partitions. If you do
not specify any options, the command displays a list of all
partition and their ID, type, status, size, percent that is used,
and supporting disks. You can specify one or more options
to show specific output.
nzspupart regen [options] Starts regeneration for SPU partitions. If you do not specify
[-force] any options, the command searches for degraded partitions
and starts regeneration processes to the available spare disks.
Optionally, you can use the options -spu spuId, -part
partId, and -dest diskHwId to specify source and target
information for a specific regeneration. Include the -force
option to start the regen without prompting you for a
confirmation. The regen option is not supported on Netezza
C1000appliances because the hardware controls
regenerations.
nzspupart listTypes Displays a list of the valid hardware types that you can
input for the nzspupart show -type spuPartitionType
command.
Options
The nzspupart command takes the following options:

Table A-35. The nzspupart options
Option Description
-host hostname Specifies the host name or IP address of the Netezza
system.
-caCertFile path Specifies the path name of the root CA certificate file on
the client system. This argument is used by IBM
Netezza clients who use peer authentication to verify
the Netezza host system. The default value is NULL,

Table A-35. The nzspupart options (continued)
Option Description
-securityLevel level Specifies the security level that you want to use for the
session. This option does not apply when you are
logged in to the Netezza system and running the
command. The argument has four values:
preferredUnSecured
This value is the default value. Specify this
option when you would prefer an unsecured
connection, but you accept a secured
connection if the Netezza system requires one.
preferredSecured
connection to the Netezza system, but you
accept an unsecured connection if the Netezza
system is configured to use only unsecured
connections.
onlyUnSecured
unsecured connection to the Netezza system. If
the Netezza system requires a secured
connection, the connection is rejected.
onlySecured
connection to the Netezza system. If the
Netezza system accepts only unsecured
connections, or if you are attempting to connect
to a Netezza system that is running a release
before 4.5, the connection is rejected.
-timeout seconds Specifies the amount of time in seconds to wait for the
command to complete before it exits with a timeout
error. Default is 300.
-id hwId Displays information about the partitions that are
supported by a disk with the specified hardware ID.
-spa id Displays information about the hardware components in
the SPA with the specified ID.
-detail Displays more information about the partitions.
-issues Displays information about partitions that have issues.
-type spuPartitionType Displays information about specific types of partitions.
The types include data, nzlocal, swap, and log.
-regenStatus Displays information about regenerations that are in
progress.
Description
The nzspupart command has the following description.

Privileges required
You must specify a database user account that has Manage Hardware
privilege.
Common tasks
Use the nzspupart command to display information about the SPU
partitions of a Netezza system, or to perform a partition regeneration when

th partition is degraded. You can use the command to obtain status about
the partitions and the space that is used within them, whether
regenerations are in progress, or if there are issues that require your
attention.
Related Commands
Use with other system commands, such as the nzhw and nzds commands.
Usage

v To display information about the SPU partitions, enter:
nzspupart
SPU Partition Id Partition Type Status Size (GiB) % Used Supporting Disks
---- ------------ -------------- ------- ---------- ------ -------------------------------
1255 0 Data Healthy 3725 0.00 1129,1151,1167
1255 1 Data Healthy 3725 0.00 1126,1148,1169
1255 2 Data Healthy 3725 0.00 1133,1150,1171
1255 3 Data Healthy 3725 0.00 1132,1145,1170
1255 4 Data Healthy 3725 0.00 1136,1137,1166
1255 5 Data Healthy 3725 0.00 1146,1149,1175
1255 6 Data Healthy 3725 0.00 1130,1153,1165
1255 7 Data Healthy 3725 0.00 1131,1155,1173
1255 8 Data Healthy 3725 0.00 1127,1152,1164
1255 100 NzLocal Healthy 11150 0.00 1134,1135,1147,1154,1168,1172,1174
1255 101 Swap Healthy 24 0.00 1134,1135,1147,1154,1168,1172,1174
1255 110 Log Healthy 1 0.00 1134,1135,1147,1154,1168,1172,1174
v To list the SPU partition types, enter:
nzspupart listTypes
Description Type
----------- -------
Data data
NzLocal nzlocal
Swap swap
Log log
v To start a partition regeneration:
nzspupart regen
Are you sure you want to proceed (y|n)? [n] y
Info: Regen Configuration - Regen configured on SPA:1 Data slice 2
and 1
If there are no degraded partitions, the command outputs the message No
degraded partitions. If the regen cannot proceed because there are no spare
disks on the system, the command outputs the message No spares disks
available.
The nzstart command

Note: You must run nzstart on the host. You cannot run it remotely.
Syntax
The nzstart command uses the following syntax:

nzstart [options]

Inputs
The nzstart command takes the following inputs:

Table A-36. The nzstart inputs
Input Description
nzstart -h Displays help.
nzstart -D dataDir Specifies the data directory to use. By default, it is
install_dir/data.
nzstart -log file Sends the daemon output to the log file instead of to
/dev/null.
nzstart -noWait Does not wait for the system to go online.
nzstart -timeout value Specifies the number of seconds to wait for the command to
complete before it exits with a timeout error. The default is 300.
nzstart -newSystem Start a new IBM Netezza system. (Used only the first time a
new system is started.)
Description
The nzstart command does the following:

Privileges required
You must be able to log on to the host system as the nz user.
Common tasks
Use the nzstart command to start system operation after you stop the IBM
Netezza system. The nzstart command verifies the host configuration to
ensure that the environment is configured correctly and completely; it
displays messages to direct you to files or settings that are missing or
misconfigured.
If the system is unable to start because of a hardware problem, the
command typically displays a timeout error message. You can review the
sysmgr.log file to identify the problems that might cause the nzstart
command to fail.
For IBM PureData System for Analytics N1001 and IBM Netezza 1000
systems, a message is written to the sysmgr.log file if there are any storage
path issues that are detected when the system starts. The log displays a
message similar to mpath -issues detected: degraded disk path(s) or
SPU communication error, which helps to identify problems within storage
arrays. For more information about how to check and manage path
failures, see “Hardware path down” on page 8-20.
Notes
The nzstart script has a default time out, which is 120 seconds + 3* the number of
SPUs. This default is subject to change in subsequent releases.
If the system is not started by this time, the nzstart command returns and prints a
warning message that indicates that the system failed to start in xxx seconds. The
system, however, continues to try to start. You can override the default time-out by
specifying a timeout.

Usage

v To specify a directory, enter:
nzstart -D /tmp/data
v To specify a log file, enter:
nzstart -log /tmp/startlog
v To start without waiting, enter:
nzstart -noWait
v To specify a timeout, enter:
nzstart -timeout 400
Related reference:
“Start the system” on page 7-6
command.
The nzstate command

Syntax
The nzstate command uses the following syntax:

nzstate [-h|-rev|-hc] subcmd [subcmd options]]
Inputs
The nzstate command takes the following inputs:

Table A-37. The nzstate inputs
Input Description
nzstate listStates Displays the system states and a description.
nzstate show options Displays the current state. This is the default if you type the
command without any arguments.
nzstate waitFor options Waits for the system to reach the specified state. You cannot
wait for a state that ends in -ing.
Options
The nzstate command takes the following options:

Table A-38. The nzstate options
nzstate listStates Takes no options.

Table A-38. The nzstate options (continued)
nzstate show -u user Specifies the database user name [NZ_USER].
-timeout secs Specifies the number of seconds to wait for the
command to complete before it exits with a
timeout error. The default is 300.
-terse Prints only the current state symbol.
-verbose Prints the expected state if it is different from the
current state.
-reason Displays more information about why the
system is in the Down state.
nzstate waitFor -type state_type Waits for the specified state to occur. Use the
listStates subcommand to display the state
types.
Description
The nzstate command does the following:

Privileges required
You do not need special privileges to run the nzstate listStates
command. You must specify a database user account to show or wait for
states.
Common tasks
Use the nzstate command to display the current state.
Usage
The following provides sample usage

v To list the states, enter:
nzstate listStates
------------ ------------------------------------------------------------
v To show the current state, enter:
nzstate show -u user -pw password -host nzhost -verbose

v To wait for the offline state until the state change occurs or the command timer
expires, enter:
nzstate waitFor -u user -pw password -host nzhost -type offline
v To display more information about a system that is in the down state, enter:
nzstate -reason
The system is DOWN because failing over SPUs results in invalid
topology
Related concepts:
“System states” on page 7-2
The IBM Netezza system state is the current operational state of the appliance.
Related reference:
The nzstats command

performance.
Syntax
The nzstats command uses the following syntax:

nzstats [-h|-rev|-hc] subcmd [subcmd options]]
Inputs
The nzstats command takes the following inputs:

Table A-39. The nzstats inputs
Input Description
nzstats listFields Displays a numbered list of the fields for the specified type of
-type type group or table. Possible types are shown in the description of
the nzstats listFields command. Each field in the list that is
displayed corresponds to a column that can be displayed for
the specified type of object by means of the nzstats show
command.

Table A-39. The nzstats inputs (continued)
Input Description
nzstats listTypes Lists the types of objects for which you can display
information:
dbms DBMS Group.
system System Group (this is the default).
database
Database Table.
host Host Table.
hostCpu
Host CPU Table.
hostFileSystem
Host File System Table.
hostIf Host Interface Table.
hostMgmtChan
Host Management Channel Table.
hostNet
Host Network Table.
hwMgmtChan
HW Management Channel Table.
query Query Table.
queryHist
Query History Table.
spu SPU Table.
spuPartition
SPU Partition Table.
table Table Table.
tableDataSlice
Per Table Per Data Slice Table.
nzstats show options Displays the statistics from the System Group table.
Options
The nzstats show command takes the following options:

Table A-40. The nzstats options
Option Description
-u user The database user name [NZ_USER].
-pw password The user password [NZ_PASSWORD].
-host name The host name or IP address [NZ_HOST].
-timeout secs The number of seconds to wait for the command to complete
before it exits with a timeout error. The default is 300.
-type type The type of group or table that you want to show. The default is
system. Possible types are shown in the description of the
nzstats listFields command.

Table A-40. The nzstats options (continued)
Option Description
-cols list A list of numbers that correspond to the columns that are to be
displayed (for example, 1,4,5). Each number corresponds to one
of the numbered fields listed by the nzstats listFields
command for the corresponding object type.
-colMatch str Display only the columns whose name contains the str string.
-orient type The output orientation (auto, horizontal, or vertical).
-fmtNum Format numbers in the output for improved readability.
-fmtMemFlds format Format memory fields with size options such as KB, MB, or GB
for improved readability.
-allocationUnit units For the type table, the units in which disk space used value is
displayed (usedbytes, extents, or usedblocks). The default is
usedbytes.
Description
The nzstats command does the following:

Privileges required
Your database user account must have the Manage System privilege to
show the actual system statistics. Any user can list the fields and types.
Common tasks
Use the nzstats command to display operational statistics. If you have a
Netezza Release 7.0.3 or later client, note that the command does not work
with Netezza systems that run a release earlier than 7.0.3 and which do not
support multiple schemas within a database.
Usage

v To list the types of objects for which statistics can be displayed:
nzstats listTypes
Group/Table Type Description
---------------- ------------------------------
dbms DBMS Group
system System Group
database Database Table
host Host Table
hostCpu Host CPU Table
hostFileSystem Host File System Table
hostIf Host Interface Table
hostMgmtChan Host Management Channel Table
hostNet Host Network Table
hwMgmtChan HW Management Channel Table
query Query Table
queryHist Query History Table
spu SPU Table
spuPartition SPU Partition Table
table Table Table
tableDataSlice Per Table Per Data Slice Table
v To list the fields (columns) of output that are generated for the system group:
nzstats listFields -type system
Col Field Name
--- --------------------
1 Name

2 Description
3 Contact
4 Location
5 IP Addr
6 Up Time
7 Up Time Text
8 Date
9 State
10 State Text
11 Model
12 Serial Num
13 Num SFIs
14 Num SPAs
15 Num SPUs
16 Num Data Slices
17 Num Hardware Issues
18 Num Dataslice Issues
v To display the first 9 columns of the system group:
nzstats show -type system -cols 1,2,3,4,5,6,7,8,9
Field Name Value
------------ --------------------------------
Name bbnzdev-blh
Description <sys description>
Contact <contact name>
Location
IP Addr 9.152.63.180
Up Time 1827020 secs
Up Time Text 21 days, 3 hrs, 30 mins, 20 secs
Date 19-Dec-13, 15:51:48 CET
State 8
v To display the columns that match the string Num Data Slices:
nzstats show -u user -pw password -host nzhost -colMatch "Num Data"
Field Name Value
-------------------- -----
Num Data Slices 3
Num Dataslice Issues 3
Related reference:
The nzstop command

command.
The nzstop command is a script that initiates a system stop by halting all
processing. Any queries in process are aborted and rolled back. Queries and
processes typically stop very quickly.
Note: You must run nzstop while logged in as a valid Linux user such as nz on
the host. You cannot run the command remotely.

Syntax
The nzstop command uses the following syntax:

nzstop options
Inputs
The nzstop command takes the following inputs:

Table A-41. The nzstop inputs
Input Description
nzstop -h Displays the help for the nzstop command.
nzstop -timeout secs Specifies the number of seconds to wait for the command to
complete before it exits with a timeout error. The default is 300.
Options
The nzstop command takes the following options:

Table A-42. The nzstop options
nzstop -h No options.
nzstop -timeout <time to wait> Specifies the timeout value.
Description
The nzstop command does the following:

Privileges required
You must be able to log on to the Netezza system as a valid Linux user
such as nz.
Common tasks
Use the nzstop command to stop the system.
Usage

v To display help, enter:
nzstop -h
v To specify a timeout of 300 seconds, enter:
nzstop -timeout 300
Related reference:
“Stop the system” on page 7-7

The nzsystem command
Syntax
The nzsystem command uses the following syntax:

nzsystem [-h|-rev|-hc] subcmd [subcmd_options]
Inputs
The nzsystem command takes the following inputs:

Table A-43. The nzsystem inputs
Input Description
nzsystem offline options Takes the system offline.
nzsystem pause options Pauses the system. Use this command to pause the
system for administrative work, but allow all current
transactions to complete.
nzsystem restart options Stops and then automatically restarts the system.
nzsystem resume options Returns the system to the online state.
nzsystem set options Configures a system setting.
Restriction: Do not change your system settings unless
directed to do so by IBM Netezza Support.
nzsystem showRegistry options Displays the system configuration registry.
nzsystem showRev options Displays the system software revision level.
nzsystem showState options Displays the system state. This is the default
subcommand if you type the nzsystem command without
any subcommands. It is also the same as the nzstate
show command.
nzsystem showIssues Displays any hardware or dataslice issues that are found
on the system.
nzsystem stop options Stops the system.
Options
The nzsystem command takes the following options:

Table A-44. The nzsystem options
All nzsystem -u user Specifies the database user name [NZ_USER].
commands
-host name Specifies the host name or IP address
[NZ_HOST].
offline, pause, -force Does not prompt for confirmation.
restart, set, stop

Table A-44. The nzsystem options (continued)
offline, pause, -now Aborts the transactions that cannot be restarted
restart, stop after the state transition.
-nowAfter seconds Specifies the time for the work to finish before it
resorts to -now. The default is 300 seconds.
set -regFile file_name Loads the registry configuration file.
-arg Specifies the configuration argument and its
value. Some configuration arguments take a
comma-separated list of multiple values.
(<tag>=<value[, value,...]>).
-ignoreErrors Skips unavailable or erroneous settings.
showRev -build Shows the build string for the IBM Netezza
software as set by the Configuration Manager
(CM).
-label Shows the label version of the build string.
Description
The nzsystem command does the following:

Privileges required
You can run a subset of the commands such as showRev and showState by
using any database user account. However, your database user account
must have the Manage System privilege to start or manage the system
states and to set or show the registry settings.
Common tasks
Use the nzsystem command to show and change system state.
Usage

v To take the system offline, enter:
nzsystem offline -u user -password password -host nzhost
To start the system again, use the nzsystem resume command.
v To pause the system, enter:
nzsystem pause -u user -password password -host nzhost
To start the system again, use the nzsystem resume command.
v To restart the system, enter:
nzsystem restart -u user -password password -host nzhost -now
v To resume the system, enter:
nzsystem resume -u user -password password -host nzhost
v To configure a system setting, enter:
nzsystem set -u user -password password -host nzhost -regFile
MaxReboot FreqPerHr
v To display the system registry settings, enter:
nzsystem showRegistry -u user -password password -host nzhost
v To display the revision level, enter:
nzsystem showRev -u user -password password -host nzhost

v To display the system state, enter:
nzsystem showState -u user -password password -host nzhost
v To display any system issues, enter:
[nz@nzhost ~]$ nzsystem showIssues
Hardware Issues :
Description HW ID Location Role State

----------- ----- -------------------- ------ --------
Disk 1030 spa2.diskEncl1.disk1 Failed Ok
PowerSupply 1113 spa1.diskEncl1.pwr1 Active Critical
Dataslice Issues :
Data Slice Status SPU Primary Storage Mirror Storage % Used

---------- ---------- ---- ---------------- --------------- -------
5 Unmirrored 1194 1139 95.90
6 Unmirrored 1194 1139 95.63
v To stop the system, enter:
nzsystem stop -u user -password password -host nzhost
To start the system again, use the nzstart command.
Related concepts:
“System configuration” on page 7-18
The behavior of an IBM Netezza system is determined by configuration settings
that are loaded from the configuration file, system.cfg, during system startup and
are stored in the configuration registry. These settings influence such things as
system management, workload management, host processes, and SPUs, and are
used to control and tune the system.
Related reference:
“Changing configuration settings” on page 7-19
There are some configuration settings that you can change yourself, without
involving your IBM Netezza support representative. These settings are referred to
in documented Netezza procedures elsewhere in this publication or elsewhere in
the Netezza product library.
“The nzcontents command” on page A-9
the system.
“The nzevent command” on page A-14
“The nzstate command” on page A-58
“The nzstats command” on page A-60
performance.

command.
The nzzonemapformat command

Use the nzzonemapformat command to display or change the type of zone maps
used on the IBM Netezza system.
You can use the nzzonemapformat command to convert a system to table-oriented

or column-oriented zone maps, or to show the format that is in use. The system
must be paused before you can convert the zone map format. For more
information about zone maps, see “Column-oriented and table-oriented zone
maps” on page 12-18.
Syntax
The nzzonemapformat command uses the following syntax:

nzzonemapformat [-h] {-table | -column | -show}
Inputs
The nzzonemapformat command takes the following inputs:

Table A-45. The nzzonemapformat input options
Input Description
-table Converts zone maps to table-oriented format.
-column Converts zone maps to column-oriented format.
-show Displays the zone map format used on the system.
Usage

v To display the zone map format in use on the system, enter:
[nz@nzhost ~]$ nzzonemapformat -show
System is configured for ’column’ zone maps
v To convert a system to table-oriented zone maps, enter:
[nz@nzhost ~]$ nzsystem pause
[nz@nzhost ~]$ nzzonemapformat -table

NOTE: The zonemap conversion process can take several minutes. Please do
not interrupt this script while it is performing the conversion.
Converting system to ’table’ based zone maps
System is configured for ’table’ zone maps

NPS can now be brought back online to resume normal operation
[nz@nzhost ~]$ nzsystem resume
Customer service troubleshooting commands

Occasionally, IBM Netezza Customer Service might ask you to use commands that
are in the /nz/kit/bin/adm directory. These commands are low-level diagnostic
commands that can be run only on the host and require administrative privileges.
CAUTION:
Do not run these commands unless explicitly directed to do so by Netezza
Customer Service. Running these commands without supervision can result in
system crashes, data loss, or data corruption.
The following table describes some of the more common commands in the bin/adm
directory. These commands are divided into the following categories:
Safe Running the command causes no damage, crashes, or unpredictable
behavior.
Unsafe
Running the command with some switches can cause no harm, but with
other switches can cause damage.
Dangerous
Running the command can cause data corruption or a crash.
These commands are unsupported commands and they have not been as
rigorously tested as the user commands.
Table A-46. Diagnostic commands
Command Usage Description
nzconvertsyscase Unsafe Converts the Netezza system to the opposite case,
for example, from upper to lowercase. For more
information, see “The nzconvertsyscase command”
on page A-70.
nzdumpschema Safe Dumps a database schema and some statistics
information. This command is useful when you are
attempting to understand a class of query
optimization issues. For more information, see “The
nzdumpschema command” on page A-71.
nzlogmerge Safe Merges multiple system log files in to a
chronological sequence. For more information, see
“The nzlogmerge command” on page A-73.
nzdbg Unsafe Enables system diagnostic messages. Although many
invocations of this command are safe, some
invocations can cause your system to crash.
nzdumpcat Unsafe Dumps the system catalog information. This
command can damage the system catalog if used
carelessly.
nzdumpmem Unsafe Dumps various database shared-memory data
structures. Although many invocations of this
command are safe, some invocations can cause your
system to crash.

Table A-46. Diagnostic commands (continued)
Command Usage Description
nzdumptxjournal Unsafe Dumps information about the transaction log used
by the database. Although many invocations of this
command are safe, some invocations can cause your
system to fail.
toporegen Unsafe Internal command that is used when system
recovery is required. Running this command results
in data loss.
nzpush Unsafe Provides low-level access to the Linux-based SPUs.
Running this command can cause the system to
crash or data to be lost.
client Dangerous Internal command that runs low-level diagnostic
tests.
cliqa Dangerous Internal command that runs low-level diagnostic
tests.
clitest Dangerous Internal command that runs low-level diagnostic
tests.
nzinitsystem Dangerous Reinitializes the system. Use this command only
when it is necessary to reset a system to a
factory-default level. Running this command on an
operational system results in data loss. For more
information, see “The nzinitsystem command” on
page A-73.
nzloadcat Dangerous Loads a database catalog. This command is used in
system recovery.
nzmakedatakit Dangerous Used internally by the system during upgrade and
downgrade. Running this command can produce
unexpected results.
nzresetxlog Dangerous Resets the database transaction log. Running this
command can cause data corruption.
nzsqa Dangerous Internal command that runs low-level diagnostic
tests.
nzlogmerge.info Documentation nzlogmerge uses some GPL components.
The nzconvertsyscase command

Use the nzconvertsyscase command to convert the IBM Netezza system to the
opposite case, for example from uppercase to lowercase or vice versa.
Your database must be offline when you use this command (that is, use nzstop
first to stop the system).
Syntax
The nzconvertsyscase command uses the following syntax:

nzconvertsyscase [-h |-rev] [options]

Inputs
The nzconvertsyscase command takes the following inputs:

Table A-47. The nzconvertsyscase input options
Input Description
nzconvertsyscase -D Specifies the data directory. Required.
nzconvertsyscase -l Converts the system to lowercase character strings.
nzconvertsyscase -u Converts the system to uppercase character strings
nzconvertsyscase -v Validates the conversion without making any changes.
Use this option to check for duplicate names.
nzconvertsyscase -L Logs the command message output to the
nzconvertsyscase log file. The default is
nzconvertsyscase.log.
Important: You must specify either -l or -u. If you do not specify either option,
the command displays an error. After you convert your system, you must rebuild
all views and synonyms in every database.
Description
The nzconvertsyscase command does the following:

Privileges required
You must be the system administrator.
Common tasks
Use the nzconvertsyscase command to convert from one default case to
another. The command uses the values in the objdelim and attdelim fields
in the system tables _t_object and _t_attribute to determine whether the
identifiers are converted or retained. The script converts only the names of
objects and attributes that are created as regular identifiers. It does not
convert delimited identifiers.
Note: If you want to convert the identifier case within a database to the
opposite of the default system case, contact Netezza Support.
Usage

v To convert to lowercase, enter:
nzconvertsyscase -l -D /nz/data
v To convert to uppercase, enter:
nzconvertsyscase -u -D /nz/data
v To validate the conversion, enter:
nzconvertsyscase -v -u -D /nz/data
The nzdumpschema command

Use the nzdumpschema command to generate a shell script with SQL statements that
duplicate a database by extracting its object definitions and statistics.
Note: Because no actual data is dumped, you cannot use this command to back up
a database.

Syntax
The nzdumpschema command uses the following syntax:

nzdumpschema [-h] [-R] database [outfile] [outdir]
[datadir][schemaList]
The nzdumpschema command takes the following inputs:

Table A-48. The nzdumpschema inputs
Option Description
-h Displays this help
-R Create a script by using the actual database name. Otherwise, the
script uses the placeholder name SHADOW.
database Specifies the name of a database for which you want statistics
and the schema.
outfile Specifies a file to which the command output is written. If you
do not specify an output file, the output is written to standard
output.
outdir Specifies the output directory where UDX object files registered
in the database are written.
datadir Specifies the location of the data directory, which is typically
/nz/data. The default is /nz/data. This option is used only when
outdir is specified.
schemaList For a Release 7.0.3 or later system, specifies one or more schemas
within the database. By default, the command dumps
information for all the schemas in a database. You can specify
one or more schemas in a space-separated list to dump only the
contents of the specified schemas.
Description
Privileges required
You must be the admin user to run the nzdumpschema command.
Common tasks
Use the nzdumpschema command to dump the table and view definitions,
the database statistical information, and optionally, any UDXs that are
registered within the database. It is a diagnostic tool that you can use to
troubleshoot various problems that relate to a query. The nzdumpschema
command is a troubleshooting tool and should not be used on a regular
basis in a production system. The command requires significant memory
resources to run, and if used at the same time as other memory-consuming
commands such as nzbackup, the host could run out of memory and
restart.
v You must run it from the host IBM Netezza system.
v You cannot use -u, -pw, -host, or other nz CLI options.
v You must set the NZ_USER and NZ_PASSWORD environment variables.
However, the command ignores the NZ_SCHEMA setting.
v You must specify a database.
v If the database includes registered user-defined objects (UDXs), you can
also dump copies of the object files that were registered for use with
those routines.

v If you do not specify an output file, the nzdumpschema command writes
to standard output.
v
Usage

v To dump table and view definitions to the file named empDBOut, enter:
nzdumpschema empDB empDBOut
v To dump the sales database to the file salesSchema and its user-defined objects
to the directory /tmp/UdxObjs, enter:
nzdumpschema sales salesSchema /tmp/UdxObjs
If you relocate the object files in /tmp/UdxObjs to another location, be sure to edit
the object path names that are used in the salesSchema file to reflect the new
location of the object files.
The nzinitsystem command

Use the nzinitsystem command only under the direction of Technical Support.
This is a dangerous command and must be used with extreme caution to avoid
loss of data and system behavior.
The nzinitsystem command re-initializes a system by overwriting the catalog

information on the host, which results in loss of data. Typically this command is
used to re-initialize a test system when you want to remove all existing database
information on that system. In extreme cases, this command might be used to
recover a system that has been altered beyond repair, and Support has identified
that reinitialization and restores are required for recovery.
The nzlogmerge command

Each system component produces a log file that is stored in a subdirectory of the
/nz/kit/log directory. Each entry in this file contains a timestamp. For
troubleshooting, it is often required to merge these entries in chronological order.
To merge all the log files, the nzlogmerge command syntax is:
nzlogmerge list of files to merge
Syntax
The nzlogmerge command takes the following options:

Table A-49. The nzlogmerge options
Option Description
-h or ? Displays this help
-v Verbose mode
-t hours Specifies the log messages in the last t hours
-a datetime Captures the log entries after the specified time and before the specified
time. The dattime value must be in the format YYYY-MM-DD HH:MM:SS.
-b datetime
files List of files to merge

Appendix B. Linux host administration reference
The IBM Netezza appliance has a host server that runs the Linux operating system.
The host manages the other Netezza components and provides support as an
administration monitor, which you can use to manage Netezza functions. The host
also converts queries into optimized execution plans, specifically by using the
strengths of the Netezza architecture.
Most Netezza models are high availability (HA) systems and have two hosts; one
host serves as the active host and one as the standby host, which takes over when
the active host encounters problems or is manually shutdown. Any changes that
you make to the Linux configuration of one host, such as adding Linux users or
groups, managing crontab schedules, or changing NTP settings, you must also
make to the second host to ensure that the hosts have identical configurations. It is
important to make these changes correctly on both hosts to ensure that the
environments are the same.
This section describes some of the common Linux procedures. For more
information, see the Red Hat documentation.
Related concepts:
performance.
Linux accounts
You can create Linux user accounts to manage user access to the IBM Netezza
system.
Accounts can refer to people (accounts that are associated with a physical person)
or logical users (accounts that exist for an application so that it can perform a
specific task). The system assigns a user ID to every file that a user account creates.
Associated with each file are read, write, and execute permissions.
Note: A Linux user or group does not have Netezza database access.
Related concepts:
“Netezza database users and user groups” on page 11-1
accounts.
Set up Linux user accounts

You use the useradd command to create a Linux user account on the IBM Netezza
host.
The syntax for the useradd command is:

/usr/sbin/useradd [-G list of groups] user_name
© Copyright IBM Corp. 2001, 2015 B-1

The -G switch specifies a comma-separated list of existing Linux groups to which
you are adding the user. Do not type any spaces in the comma-separated group
list. For example, to create an account that is called kilroy and to assign that
account to the staff, admin, and dev Linux user groups, run the following
command as root:
useradd -G staff,admin,dev kilroy
This useradd command creates a user that is called kilroy and also a user private
group called kilroy. It also adds user kilroy to the staff, admin, and dev Linux
groups.
For Netezza HA systems, after you add the Linux account on one host, you must
create exactly the same user account with the same userid value on the other host.
To create Linux users in a Netezza HA environment, use the following procedure:
1. Log in to Netezza host 1 as the root or super user.
2. Use the useradd command to create your new Linux user:
[root@nzhost-h1 ~]# useradd -p usr_test usr_test
3. Confirm the userid and groupid for the new user account:
[root@nzhost-h1 ~]# grep usr_test /etc/passwd
usr_test:x:501:501::/home/usr_test:/bin/bash
The first number after the x is the userid and the second number is the
groupid.
4. Connect to Netezza host 2 as the root or super user.
5. Use the useradd command to create your new Linux user with the same userid:
[root@nzhost-h2 ~]# useradd -p usr_test -u 501 usr_test
6. Confirm that the account on host 2 has the same user name, userid, and
groupid:
[root@nzhost-h2 ~]# grep usr_test /etc/passwd
usr_test:x:501:501::/home/usr_test:/bin/bash
Modify Linux user accounts

The syntax for the usermod command is:
/usr/sbin/usermod [-G list of groups] user_name
To modify an existing Linux user account, enter: usermod -G staff,admin kilroy
This usermod command changes the groups to which the kilroy user belongs.
Delete Linux user accounts

The syntax for the userdel command is:
/usr/sbin/userdel [-r] user_name
To delete an existing Linux user account, enter: userdel kilroy
This userdel command deletes the kilroy account, but does not delete kilroy's
home directory.
Change Linux account passwords

There are two ways to change passwords for Linux accounts. If you can log in as
the account, you can change its password. If you are logged on as root, you can
manage other user accounts to change passwords.
B-2 IBM Netezza System Administrator’s Guide

To change the password of your current account, enter:
passwd(current) UNIX password: (enter original password)
New UNIX password: (enter the new password)
Retype new UNIX password: (enter the new password again)
passwd: All authenticaton tokens updated successfully.
To change the password of a different account (you must be logged in as root),

enter:
passwd user_name
New UNIX password: (enter the new password)
Retype new UNIX password: (enter the new password again)
passwd: All authenticaton tokens updated successfully.
Linux groups
Groups are logical expressions of an organization. Groups relate certain users and
give them the ability to read, write, and execute files, which they might not
directly own. You can create and use Linux groups to associate certain users that
have similar permissions.
For more information, see the Red Hat documentation.
Add Linux groups

When you use the useradd command to create a Linux user, the command
automatically creates a Linux group with the same name. You can use the groupadd
command to create a Linux group.
The syntax for the groupadd command is:

/usr/sbin/groupadd [-G gid [-o][-r][-f] group
To add a group, enter: groupadd staff
This groupadd command adds the group named staff.
For Netezza HA systems, after you add the Linux group on one host, you must
create exactly the same group with the same groupid value on the other host. To
create Linux groups in a Netezza HA environment, use the following procedure:
1. Log in to Netezza host 1 as the root or super user.
2. Use the groupadd command to create your new Linux group:
[root@nzhost-h1 ~]# groupadd staff
3. Confirm the groupid for the new group:
[root@nzhost-h1 ~]# grep staff /etc/group
staff:x:501:
The first number after the x is the groupid.
4. Connect to Netezza host 2 as the root or super user.
5. Use the groupadd command to create your new Linux group with the same
groupid:
[root@nzhost-h2 ~]# groupadd -g 501 staff
6. Confirm that the group on host 2 has the same groupid:
[root@nzhost-h2 ~]# grep staff /etc/group
staff:x:501:
Appendix B. Linux host administration reference B-3

Modify Linux groups
The syntax for the groupmod command is:
/usr/sbin/groupmod [-G gid [-o][-n groupname] group
To modify a group, enter: groupmod -n exestaff staff
This groupmod command changes the group named staff to exestaff.
Delete Linux groups

The syntax for the groupdel command is:
/usr/sbin/groupdel <group>
To delete a group, enter: groupdel staff
This groupdel command deletes the staff group. You cannot remove a user's
primary group. You must first remove the user or change the user's primary group.
Linux Host system

The IBM Netezza host server offers a full-featured Linux operating system, with
many useful commands, but because you are using it solely to access the Netezza
appliance, the amount of system maintenance is less than if you were using it in a
general-purpose server environment.
The following sections explain some of the tasks you might perform.
Host name and IP address changes

Contact IBM Netezza Support when you want to change the host name, IP
address, or both of your Netezza system. Netezza Support can work with you to
change the information and ensure that the changes are propagated to the high
availability (HA) configuration files and related services.
CAUTION:
Do not follow the general Linux steps to change the host name or IP address
because the changes can result in split-brain or similar HA problems and system
downtime.
Rebooting the system

The correct way to reboot the host system is to have Linux close all its data files
and stop all running processes. Never simply turn off your machine. Use the
shutdown(8) command. You must be root to run the shutdown -r now command.
The -r switch causes a reboot. You can specify either the word now or any time
value. You can use the -h switch to halt the system. In that case, Linux also powers
down the host if it can.
If you have a IBM Netezza HA system, use caution when you are shutting down a
host. Shutting down the active host causes the HA software to fail over to the
standby host to continue Netezza operations, which might not be what you
intended.

Reformat the host disks
IBM Netezza host systems are pre-configured in manufacturing. The
factory-configured system includes preinstalled software and the Linux operating
system that is configured for Netezza services.
CAUTION:
Never reformat the host disks. Doing so results in loss of data and corruption of
the file system. If you are experiencing errors, see the following section and
contact Netezza Support.
Fix system errors

Normally the fsck (file system check) program runs automatically without
problems. If there are problems, it requests that you run it manually.
To run the fsck command manually, enter the following command, where x
specifies the disk partition number:
fsck /dev/hdax
Answer yes to all prompts. The goal is to recover metadata, but some data might
be lost. The fsck command should return your system to a consistent state; if not,
contact IBM Netezza Support.
Restriction: Do not use fsck to repair mounted partitions. If you are trying to
repair a mounted partition, you must first unmount the partition by using the
umount command, or you must boot the host from the emergency repair CD (the
installation has a repair mode) to fix a partition such as the root partition (/).
View system processes

To view the processes that are running on the IBM Netezza host, you can use the
ps command for a snapshot of the process status or use the top command to
display information about CPU processes.
v To display the pid, tty, and cmd of user procs, enter: ps -u <user name>
v To display the pid, tty, time, and cmd used by the command, enter: ps -C dbos
-<cmdname>
v To display the accumulated CPU time of a process, enter: ps p <process ID>
v To display a full process tree which shows parent-child process relationships,
enter: ps axf
v To display a full listing of all processes, enter: ps -ef
v To display the process tree hierarchy, enter: ps -efw --forest
The top command displays real-time information about CPU activity and lists the
most CPU intensive tasks on the system. The system updates the display every 5
seconds by default.
v To display system CPU utilizations, enter: top
v To update the display every 10 seconds, enter: top -d -10
Stop errant processes

Stopping a specific Linux process can vary for each process. The fail-safe way is to
stop the process with either the kill or killall command.
The difference between these two commands is that you run the kill command
with a process number, and you run the killall command with a process name.

The killall command finds every instance of the process you name and tries to
stop each one, whereas the kill command stops only the process that is specified
by the process number.
CAUTION:
Never use the Linux kill commands to stop an IBM Netezza database user
session or an nz command process. Killing sessions or Netezza processes can
cause unwanted results such as loss of data or Netezza software restarts. Instead,
use the nzsession abort command to about sessions, and use the documented
commands such as nzstop to stopNetezza services.
With both commands, you can specify which type of signal to send to stop the
task. An application can intercept various types of signals and keep running,
except for the kill signal (signal number 9, mnemonic SIGKILL). Any UNIX system
that receives a SIGKILL for a process must stop that process without any further
action to meet POSIX compliance (if you own the task or you are root). Both the
kill and killall commands accept the signal number as a hyphen argument.
To stop the loadmgr process (number 2146), you can use any of the following
commands:
v kill -9 2146
v killall -KILL loadmgr
v kill -SIGKILL 2146
v killall -9 loadmgr
Note: When you kill a process with the kill signal, you lose any unsaved data for
that process.
Change the system time

To set the system time or current date, as root use the date command
(MMDDhhmm[[CC]yy][.ss]). It is recommended that you use Network Time
Protocol (NTP) at your site. NTP synchronizes the system clock to that of the NTP
server and frees you from having to set the time independently.
To change your system time, enter: date --set=24:00:00EST
The sample date command sets the time to midnight EST.
To set the system date, enter: date -s "06/01/2009 01:30:00EST
The sample date command sets the date to June 1, 2009, 1:30 AM EST.
Determine the kernel release level

Use the uname command to learn the kernel version that the IBM Netezza host is
running. The command displays system information.
To display the kernel version, enter: uname -r
Linux system administration

There are some useful Linux commands that you can use for system admistration.

Display directories
You can use the ls command to display information about directories:
ls -l Displays the long listing.
ls -lt Sorts the listing by modification time.
ls -ltu
Sorts the listing by access time. This command is useful to find out who
accessed the file, when, and which files were used.
ls -l --full-time
Includes the full date and time in the listing.
Find files
You can use several commands to locate files, commands, and packages:
locate string
Locates any file on the system that includes the string within the name.
The search is fast because it uses a cache, but it might not show recently
added files.
find -name *string*
Finds any file in the current directory, or below the current directory, that
includes string within the name.
which command
Displays the full path for a command or executable program.
rpm -qa
Lists all the packages that are installed on the host.
Display file content

The Linux operating system offers several ways to display the content of files.
Common commands include more and editors such as vi. The less command
offers a powerful set of features for viewing file content, and can even display
non-text or compressed files such as the compressed upgrade logs. The view
command is a read-only form of the vi command and has many features for file
viewing.
As a best practice, do not use a file editor such as vi to view active log files such
as /var/log/messages or the pg.log file. Since vi opens the file for viewing or
editing, the locking process can block processes that are writing to the log file. Use
commands such as more or less instead.
Find Netezza hardware

If you are logged in as the nz user on the active host, you can use the nzhw
command with the egrep command to locate IBM Netezza hardware:
nzhw | egrep “Fan|Power”
Displays the lines that match Fan or Power.
nzhw | egrep -i “spu”
Displays all the lines that contain spu, ignoring case distinctions in the
pattern and the data.
nzhw | egrep -vi “fan|power”
Displays lines that do not match fan or power (not case-sensitive).

Time command execution
You can use the time command to time the execution of commands:
time command
Times the execution of a command.
time -p command
Displays the execution time in a portable output format.
Set default command line editing

You can use the set command to set the command line editing interface:
set -o emacs
Uses an emacs-style command-line editing interface and supports the use
of arrow keys. This option is enabled by default when the shell is
interactive.
set -o vi
Uses a vi-style command-line editing interface.
Miscellaneous commands
You can use the following commands for system administration:
nohup command
Runs a command immune to hangups and creates a log file. Use this
command when you want a command to run no matter what happens
with the system. For instance, use this command if you want to avoid
having a dialup, VPN timeout, or a disconnect network cable cancel your
job.
unbuffer command
Disables the output buffering that occurs when the program's output is
redirected. Use this command when you want to see output immediately.
UNIX systems buffer output to a file so that a command can seem hung
until the buffer is dumped.
colrm [startcol [endcol]]
Removes selected columns from a file or stdin.
split Splits a file into pieces.

Appendix C. Netezza user and system views
This section contains information about IBM Netezza user and system views.
User views
The following table describes the views that display user information. To see a
view, users must have the privilege to list the object.
Table C-1. User views
View name Description Output Ordered by nzsql
_v_aggregate Returns a list of all objid, Aggregate, Owner, Aggregate \da
defined aggregates CreateDate
_v_database Returns a list of all objid, Database, Owner, Database \l
databases CreateDate
_v_datatype Returns a list of all objid, DataType, Owner, DataType \dT
system data types Description, Size
_v_function Returns a list of all objid, Function, Owner, Function \df
defined functions CreateDate, Description, Result,
Arguments
_v_group Returns a list of all objid, GroupName, Owner, GroupName \dg
groups CreateDate
_v_groupusers Returns a list of all users objid, GroupName, Owner, GroupName, \dG
of a group UserName UserName
_v_index Returns a list of all user objid, IndexName, TableName, TableName, \di
indexes Owner, CreateDate IndexName
_v_operator Returns a list of all objid, Operator, Owner, Operator \do
defined operators CreateDate, Description,
oprname, oprleft, oprright,
oprresult, oprcode, and oprkind
_v_procedure Returns a list of all the objid, procedure, owner, Procedure
stored procedures and createdate, objtype, description,
their attributes result, numargs, arguments,
proceduresignature, builtin,
proceduresource, sproc, and
executedasowner
_v_relation_column Returns a list of all objid, ObjectName, Owner, ObjectName, and
attributes of a relation CreateDate, ObjectType, attnum, attnum
(table, view, index.) attname,
format_type(attypid,attypmod),
and attnotnull
_v_relation_column_def Returns a list of all objid, ObjectName, Owner, ObjectName, and
attributes of a relation CreateDate, Objecttype, attnum, attnum
that have defined attname, and adsrc
defaults
_v_sequence Returns a list of all objid, SeqName, Owner, and SeqName \ds
defined sequences CreateDate
_v_session Returns a list of all active ID, PID, UserName, Database, ID \act
sessions ConnectTime, ConnStatus, and
LastCommand
© Copyright IBM Corp. 2001, 2015 C-1

Table C-1. User views (continued)
_v_table Returns a list of all user objid, TableName, Owner, and TableName \dt
tables CreateDate
_v_table_dist_map Returns a list of all fields objid, TableName, Owner, TableName, and
that are used to CreateDate, DistNum, and DistNum
determine the table’s DistFldName
data distribution
_v_table_index Returns a list of all user T.objid, TableName, T.Owner, TableName, and
table indexes IndexName, CreateDate, IndexName
I.indkey, l.indisunique,
l.indisprimary, T.relhasrules,
and T.relnatts
_v_user Returns a list of all users objid, UserName, Owner, UserName \du
ValidUntil, and CreateDate
_v_usergroups Returns a list of all objid, UserName, Owner, and UserName, and \dU
groups of which the user GroupName GroupName
is a member
_v_view Returns a list of all user objid, ViewName, Owner, ViewName \dv
views CreateDate, relhasindex, relkind,
relchecks, reltriggers,
relhasrules, relukeys, relfkeys,
relhaspkey, and relnatts
System views
The following table describes the views that display system information. You must
have administrator privileges to display these views.
Table C-2. System views
_v_sys_group_priv Returns a list of all GroupName, ObjectName, DatabaseName, \dpg
defined group privileges DatabaseName, Objecttype, GroupName, and <group>
gopobjpriv, gopadmpriv, ObjectName
gopgobjpriv, and
gopgadmpriv
_v_sys_index Returns a list of all objid,SysIndexName, TableName, and \dSi
system indexes TableName, and Owner SysIndexName
_v_sys_priv Returns a list of all user UserName, ObjectName, DatabaseName, and \dp <user>
privileges. This list is a DatabaseName, aclobjpriv, ObjectName
cumulative list of all acladmpriv, aclgobjpriv, and
groups and user-specific aclgadmpriv
privileges.
_v_sys_table Returns a list of all objid, SysTableName, and SysTableName \dSt
system tables Owner
_v_sys_user_priv Returns a list of all UserName, ObjectName, DatabaseName, \dpu <user>
defined user privileges DatabaseName, ObjectType, UserName, and
uopobjpriv, uopadmpriv, ObjectName
uopgobjpriv, and
uopgadmpriv
_v_sys_view Returns a list of all objid, SysViewName, and SysViewName \dSv
system views Owner
C-2 IBM Netezza System Administrator’s Guide

Notices
This information was developed for products and services offered in the US. This
material might be available from IBM in other languages. However, you may be
required to own a copy of the product or product version in that language in order
to access it.
IBM may not offer the products, services, or features discussed in this document in
other countries. Consult your local IBM representative for information on the
products and services currently available in your area. Any reference to an IBM
product, program, or service is not intended to state or imply that only that IBM
product, program, or service may be used. Any functionally equivalent product,
program, or service that does not infringe any IBM intellectual property right may
be used instead. However, it is the user's responsibility to evaluate and verify the
operation of any non-IBM product, program, or service.
IBM may have patents or pending patent applications covering subject matter
described in this document. The furnishing of this document does not grant you
any license to these patents. You can send license inquiries, in writing, to:
IBM Director of Licensing

IBM Corporation
North Castle Drive, MD-NC119
Armonk, NY 10504-1785
US
For license inquiries regarding double-byte character set (DBCS) information,

contact the IBM Intellectual Property Department in your country or send
inquiries, in writing, to:
Intellectual Property Licensing

Legal and Intellectual Property Law
IBM Japan Ltd.
19-21, Nihonbashi-Hakozakicho, Chuo-ku
Tokyo 103-8510, Japan
INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS

PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER
EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS
FOR A PARTICULAR PURPOSE. Some jurisdictions do not allow disclaimer of
express or implied warranties in certain transactions, therefore, this statement may
not apply to you.
This information could include technical inaccuracies or typographical errors.

Changes are periodically made to the information herein; these changes will be
incorporated in new editions of the publication. IBM may make improvements
and/or changes in the product(s) and/or the program(s) described in this
publication at any time without notice.
Any references in this information to non-IBM websites are provided for

convenience only and do not in any manner serve as an endorsement of those
© Copyright IBM Corp. 2001, 2015 D-1

websites. The materials at those websites are not part of the materials for this IBM
product and use of those websites is at your own risk.
IBM may use or distribute any of the information you supply in any way it
believes appropriate without incurring any obligation to you.
Licensees of this program who wish to have information about it for the purpose
of enabling: (i) the exchange of information between independently created
programs and other programs (including this one) and (ii) the mutual use of the
information which has been exchanged, should contact:
IBM Director of Licensing

IBM Corporation
North Castle Drive, MD-NC119
Armonk, NY 10504-1785
US
Such information may be available, subject to appropriate terms and conditions,

including in some cases, payment of a fee.
The licensed program described in this document and all licensed material
available for it are provided by IBM under terms of the IBM Customer Agreement,
IBM International Program License Agreement or any equivalent agreement
between us.
Any performance data contained herein was determined in a controlled

environment. Therefore, the results obtained in other operating environments may
vary significantly. Some measurements may have been made on development-level
systems and there is no guarantee that these measurements will be the same on
generally available systems. Furthermore, some measurements may have been
estimated through extrapolation. Actual results may vary. Users of this document
should verify the applicable data for their specific environment.
Information concerning non-IBM products was obtained from the suppliers of

those products, their published announcements or other publicly available sources.
IBM has not tested those products and cannot confirm the accuracy of
performance, compatibility or any other claims related to non-IBMproducts.
Questions on the capabilities of non-IBM products should be addressed to the
suppliers of those products.
Statements regarding IBM's future direction or intent are subject to change or

withdrawal without notice, and represent goals and objectives only.
This information contains examples of data and reports used in daily business
operations. To illustrate them as completely as possible, the examples include the
names of individuals, companies, brands, and products. All of these names are
fictitious and any similarity to actual people or business enterprises is entirely
coincidental.
COPYRIGHT LICENSE:
This information contains sample application programs in source language, which

illustrate programming techniques on various operating platforms. You may copy,
modify, and distribute these sample programs in any form without payment to
IBM, for the purposes of developing, using, marketing or distributing application
programs conforming to the application programming interface for the operating
D-2 IBM Netezza System Administrator’s Guide

platform for which the sample programs are written. These examples have not
been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or
imply reliability, serviceability, or function of these programs. The sample
programs are provided "AS IS", without warranty of any kind. IBM shall not be
liable for any damages arising out of your use of the sample programs.
© (your company name) (year).

Portions of this code are derived from IBM Corp. Sample Programs.
© Copyright IBM Corp. _enter the year or years_.
Trademarks
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of
International Business Machines Corp., registered in many jurisdictions worldwide.
Other product and service names might be trademarks of IBM or other companies.
A current list of IBM trademarks is available on the web at "Copyright and
trademark information" at www.ibm.com/legal/copytrade.shtml.
Adobe is a registered trademark of Adobe Systems Incorporated in the United

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

countries, or both.
Microsoft, Windows, Windows NT, and the Windows logo are trademarks of
Microsoft Corporation in the United States, other countries, or both.
UNIX is a registered trademark of The Open Group in the United States and other
countries.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other
names may be trademarks of their respective owners.
Red Hat is a trademark or registered trademark of Red Hat, Inc. 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.
Terms and conditions for product documentation

Permissions for the use of these publications are granted subject to the following
terms and conditions.
Applicability
These terms and conditions are in addition to any terms of use for the IBM
website.
Personal use
You may reproduce these publications for your personal, noncommercial use
provided that all proprietary notices are preserved. You may not distribute, display
or make derivative work of these publications, or any portion thereof, without the
express consent of IBM.
Notices D-3
Commercial use
You may reproduce, distribute and display these publications solely within your
enterprise provided that all proprietary notices are preserved. You may not make
derivative works of these publications, or reproduce, distribute or display these
publications or any portion thereof outside your enterprise, without the express
consent of IBM.
Rights
Except as expressly granted in this permission, no other permissions, licenses or

rights are granted, either express or implied, to the publications or any
information, data, software or other intellectual property contained therein.
IBM reserves the right to withdraw the permissions granted herein whenever, in its
discretion, the use of the publications is detrimental to its interest or, as
determined by IBM, the above instructions are not being properly followed.
You may not download, export or re-export this information except in full
compliance with all applicable laws and regulations, including all United States
export laws and regulations.
IBM MAKES NO GUARANTEE ABOUT THE CONTENT OF THESE

PUBLICATIONS. THE PUBLICATIONS ARE PROVIDED "AS-IS" AND WITHOUT
WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING
BUT NOT LIMITED TO IMPLIED WARRANTIES OF MERCHANTABILITY,
NON-INFRINGEMENT, AND FITNESS FOR A PARTICULAR PURPOSE.
D-4 IBM Netezza System Administrator’s Guide

Index
Special characters accounts
Linux users B-1
booting (continued)
software 7-10
_v_aggregate view 11-40, C-1 unlocking 11-28 bootsvr, description 7-8
_v_database view 11-40, C-1 activating build number 7-1
_v_datatype view 11-40, C-1 scheduler rule 15-7
_v_function view 11-40, C-1 active hardware 5-8
_v_group view 11-40, C-1
_v_groupusers view 11-40, C-1
active host, identifying 4-5
admin
C
_v_index view C-1 CA client certificate 11-21
database user account 1-1
_v_operator view 11-40, C-1 CA client keys file 11-21
nzsession 12-24
_v_procedure view 11-40 CA server certificate, adding 11-30
object privileges 11-11
_v_qryhist 12-30 cache, directory 1-2
predefined user 11-3
_v_qrystat 12-30 callhome
privileges, user 12-1
_v_relation_column view 11-40, C-1 disabling 9-19
user characteristics 11-3
_v_relation_column_def view 11-40, C-1 disabling events 9-20
admin user
_v_relation_keydata, view 11-40 displaying status 9-11
creating group of 11-17
_v_sched_gra view 15-17 email-only reporting 9-11
resource allocations 15-15
_v_sequence view 11-40, C-1 enabling 9-8
administration interfaces
_v_session view 11-40, C-1 enabling PMR creation 9-10
about 3-1
_v_sys_group_priv view 11-40, C-2 event rules 9-12
list of 1-8
_v_sys_index view 11-40, C-2 event rules, removing 9-21
administration tasks 1-1
_v_sys_priv view 11-40, C-2 event testing 9-15
about 1-1
_v_sys_table view 11-40, C-2 inventory report testing 9-19
hardware 5-1
_v_sys_user_priv view 11-40, C-2 inventory reporting 9-11
administrator privileges
_v_sys_view view 11-40, C-2 log files and diagnostics 9-14
admin user 12-1
_v_table view 11-40, C-1 monitoring conditions 9-13
description of 11-10
_v_table_dist_map view 11-40, C-1 nzcallhome command A-4
security model 11-9
_v_table_index view C-1 requesting upgrades 9-19
alcapp 14-2
_v_user view 11-40, C-1 sample email 9-17
alcapp log file 14-4
_v_usergroups view 11-40, C-1 showing message output 9-9
alcloader 14-2
_v_view view 11-40, C-1 status reporting 9-10
alcloader log file 14-4
/etc/ldap.conf file 11-20 suppress events 9-14
alerts
/var/log/messages 4-2 callhome operational checks 9-17
displaying 8-36
$hist_column_access_n table 14-19 callhome service
allocation, resource 15-10
$hist_failed_authentication_n table 14-20 about 9-1
alter privilege 11-11
$hist_log_entry_n table 14-21 callHome.txt
AndExpr event rule 8-11
$hist_nps_n table 14-21 configuring 9-2
assigned hardware 5-8
$hist_plan_epilog_n table 14-22 custom subject fields 9-5
authentication methods 11-18
$hist_plan_prolog_n table 14-23 callHome.txt file, editing 5-19
authentication, clients 11-31
$hist_query_epilog_n table 14-24 cbts_needing_groom script 12-21
automatic host backup 13-41
$hist_query_overflow_n table 14-25 certificate, SSL 11-30
$hist_query_prolog_n table 14-25 certification authority (CA) 11-21
$hist_service_n table 14-27, 14-30 changing
$hist_session_epilog_n table 14-28 B configuration settings 7-19
$hist_session_prolog_n table 14-28 backup 13-32 settings, configuration 7-19
$hist_table_access_n table 14-30 archive directory 13-17 changing history configuration
$hist_version table 14-31 automatic host 13-41 settings 14-11
$HOME/.nzsql_history 3-9 examples 13-15 changing owner
$HOME/.nzsqlrc 3-9 Netezza CLI 13-39 scheduler rule 15-7
nzcallhome permissions 13-21 CIB
-debug option 9-9 privileges 11-10, 13-15 about 4-3
debug mode 9-9 syntax 13-12 avoiding incorrect modifications 4-3
testing callhome services 9-15 type 13-38 clear-text password 2-13
base, directory 1-2 CLI 3-1
batch, error handling 3-9 commands, running 2-6
A bigint, integer type 12-4
bin, directory 1-2
client
command description A-69
abort bin/admin, directory 1-2 session privilege 11-17
privilege 11-11 blocks, definition 12-3 sessions list 11-17
program 7-11 bnrmgr, description 7-8 client applications
absent device 5-10 booting about 2-1
access, controlling to Netezza 11-1 hardware 7-10 supported OS 2-1
© Copyright IBM Corp. 2001, 2015 X-1

client applications (continued) critical state 5-10 displaying (continued)
Unicode support 2-9 crm_mon command, displaying system components 3-13
UNIX, installing 2-2 status 4-5 distribute on
clientmgr, description 7-8 crm_resource command, identifying create table command 12-6
cliqa command, description A-69 active host 4-5 hash 12-6
clitest command, description A-69 crm_verify command 4-16 distribute on random, create table 12-6
Cluster Information Base (CIB). cryptographic standard SP 800-131a 10-1 Distributed Replicated Block Device
SeeCIB. 4-3 custom1 event type 8-7 (DRBD). SeeDRBD. 4-1
cluster status, checking 4-5 distribution key 12-6
clustered base table (CBT) 12-12 data skew 12-10
clustering mode, transitioning to 4-10
column-oriented zone maps 12-19
D distribute on 12-6
distribute on random 12-6
data skew
command line interface 3-1 random distribution 12-10
avoiding 12-10
commands, main menu 3-16 selection criteria 12-7
viewing 12-11
commands, proper format for subset tables 12-7
data slice status 5-26
identifiers 3-4 verifying 12-8
data slices
commands, timing B-8 DNS information
Per Table Per Data Slice Table 16-1
Commlog, ODBC property 11-39 appending 1-7
data types, disk space usage 12-4
compliance 15-16 changing 1-6
data, directory 1-2
monitoring 15-17 managing 1-5
database administration, about 1-1
component failure 7-11 overwriting 1-7
database super user account 1-1
components, displaying 3-13 showing 1-6
Database Table, nzstats 16-1, 16-2
compressed binary format, for external updating 1-6
database user account
table unload 13-4 DNS status
password reuse 11-7
compression, used with backup and displaying 1-8
databases
restore 13-4 down state 5-10
Netezza table 16-1
CONFIG-INFO file 14-3 down, system state 7-4
nzsql 3-5
config, directory 1-2 DRBD
privileges 11-15
configuration file 7-18 about 4-1
record header 12-4
configuration registry 7-18 administration 4-12
statistic privilege 11-17
configuration settings 7-18 protocol C 4-1
tuning 12-5
changing 7-19 replicated directories 4-1
databases, displaying 3-13
displaying 7-18 split-brain 4-14
date
connection methods, commands 11-34 states 4-13
command B-6
connection privileges status examples 4-14
disk usage 12-4
inherited 11-17 synchronous mode 4-1
DBMS Group, nzstats 16-1, 16-2
connection record DROP HISTORY CONFIGURATION
DBOS
creating 11-33 command 14-12
nzDbosSpill 7-17
dropping 11-33 drop privilege 11-11
dbosDispatch 7-8
precedence 11-33 dropping
dbosEvent 7-8
showing 11-32 scheduler rule 15-7
deactivating
syntax 11-31
scheduler rule 15-7
content of files, displaying B-7
default port numbers, changing 2-11
cost (query) 15-22
CPU usage, displaying B-5
delete, privilege 11-11 E
deleting e-mail for events 8-12
create database
scheduler rule 15-7 egrep command B-7
privilege 11-10, A-3
delimited identifiers, specifying in email-only reporting
create external table
commands 3-4 callhome 9-11
privilege 11-10
Designated Coordinator (DC) host 4-5 email-only verification 9-17
create external table privileges 11-10
digital certificates, for SSL 11-21 EMC NetWorker 13-61
create group
directories, displaying B-7 encrypted backups using TSM 13-43
privileges 11-10
disk space encrypted passwords 2-13
CREATE HISTORY CONFIGURATION
nzDbosSpill 7-17 enhanced cryptography
command, using 14-5
reclaiming 12-20 NPS requirements 10-2
create materialized view, privilege 11-10
threshold events 8-22 enhanced cryptography support A-8
create sequence, privilege 11-10
usage 12-4 enhanced cryptography support,
create table
disk status, monitoring disk errors 8-27 disabling 10-6
privilege 11-10, 13-21
diskError event type 8-7 environment
create temp table, privilege 11-10
dispersion failure 7-11
create user, privileges 11-10
automatic statistics 12-16 installer 2-8
create view
displaying NZ_DATABASE 13-12
privilege 11-10
configuration settings 7-18 NZ_HOST 2-13
create_databaseability_to 12-1
databases 3-13 NZ_PASSWORD 2-14
created session 14-28
registry settings 7-18 NZ_USER 2-13
creating
revision level 7-18 PATH variable 1-5
scheduler rule 15-7
settings, configuration 7-18 port numbers 2-10
creating a history database 14-5
software revision level 7-18 variables 2-8
X-2 IBM Netezza System Administrator’s Guide

EqualityExpr event rule 8-11 flag, SQB 15-22 hardware (continued)
errors FORMAT_COLUMN_ACCESS () online state 5-10
categories system 7-11 function 14-32 path down events 8-20
fixing system B-5 FORMAT_PLAN_STATUS () restart events 8-22
nzbackup 13-12 function 14-32 roles 5-8
regeneration 8-26 FORMAT_QUERY_STATUS () spare 5-8
session manager 7-16 function 14-31 state 5-10
startup server 7-16 FORMAT_TABLE_ACCESS() temperature events 8-28
statistics server 7-17 function 14-32 types 5-4
errors and troubleshooting 11-27 fsck, command B-5 unreachable state 5-10
estimate, cost 15-22 fwMismatch event type 8-7 warning state 5-10
estimatedcost 14-23 Hardware Management Channel Table,
estimateddisk 14-23 nzstats 16-7
estimatedmem 14-23
event
G hardware privileges 11-10
hardware, displaying 5-2
gate keeper
aggregation, time interval 8-15 hash, create table 12-6
nzsession command 15-29
attributes of 8-11 Heartbeat
generate statistics 11-11
event rule clustering mode 4-10
hints 12-17
actions 8-12 configuration 4-3
syntax 12-15
actions overview 8-1 daemon 4-1
tuning database tables 12-5
adding 8-7 failover timers 4-4
GenStats privileges 11-11
aggregating notifications 8-14 forcing shutdown 4-16
gkpriority 14-23
disabling 8-7 maintenance mode 4-9
GRA
disk errors 8-27 manually controlling 4-8
example 15-13
displaying alerts 8-36 required Linux users and
gratime 14-23
email notifications 8-12 groups 4-17
groom command 12-20
equality expressions 8-11 safe shutdown 4-8
GROOM command 12-20
hardware failed 8-18 startup 4-2
Groom privileges 11-11
hardware needs attention 8-20 helper functions
grooming tables 12-20
hardware path down 8-20 history 14-31
groupadd command B-3
hardware restarted 8-22 high availability (HA) solution 4-1
groups
hardware temperature 8-28 High-Availability Linux. See
adding Linux users B-3
history data 8-30 Linux-HA. 4-1
Linux B-3
regen failures 8-26 histCaptureEvent 14-4
methods for managing 11-1
runaway query 8-24 histCaptureEvent event type 8-7
Netezza database 11-1
runCmd arguments 8-12 histLoadEvent 14-4
privilege 11-15
See nzevent command 8-1 histLoadEvent event type 8-7
public 1-1, 11-3
sendMail.cfg 1-2 history
rowset limits 11-36
SPU cores 8-32 $hist_column_access.usage column,
setting privileges for members 11-1
substitution tags 8-12 displaying 14-32
using to simplify privilege
system changes 8-17 $hist_plan_epilog.status column,
management 11-1
system temperature 8-29 displaying 14-32
guaranteed resource allocation 15-8
template reference 8-17 $hist_query_epilog.status column,
templates 8-1 displaying 14-31
TopologyImbalance 8-35 $hist_table_access.usage column,
TransactionLimitEvent 8-33 H displaying 14-32
voltage faults 8-33 ha.cf file 4-3 batches to load, finding 14-12
eventmgr, description 7-8 haclient group 4-17 column data 14-5
Execute privilege 11-11 hacluster CONFIG-INFO file 14-3
exit code, description for nz group 4-17 configuration
commands A-4 user 4-17 creating 14-5
Extended Internet Services 1-8 hardware dropping 14-12
extent active 5-8 created session 14-28
disk usage 12-4 assigned 5-8 data files 14-3
extent, definition 12-3 critical state 5-10 database
external tables, compressed data 13-4 down state 5-10 access 14-9
failed 5-8 granting access to 14-9
failure events 8-18 managing access to 14-9
F inactive 5-8
incompatible 5-8
delays in loading data 14-7
event notifications 14-4
failed hardware 5-8
invalid state 5-10 FORMAT_COLUMN_ACCESS ()
failover
management channel table 16-1 function 14-32
criteria 4-7
mismatched 5-8 FORMAT_PLAN_STATUS()
error actions 7-11
missing state 5-10, 7-4 function 14-32
events 4-7
needs attention events 8-20 FORMAT_QUERY_STATUS()
Linux-HA 4-1
none state 5-10 function 14-31
timers 4-4
ok state 5-10
files, finding B-7
Index X-3
history (continued) host (continued) Kerberos tickets
FORMAT_TABLE_ACCESS() host table 16-1 cache location 11-26
function 14-32 installation directory 1-2 keystore for SEDs 6-4
helper functions 14-31 Host CPU Table, nzstats 16-1, 16-3 kill command B-5
load settings 14-7 Host Filesystem Table, nzstats 16-1, 16-3 killall command B-5
loading history data 14-7 Host Interfaces Table, nzstats 16-1, 16-4 kit
LOADINTERVAL 14-7 Host Mgmt Channel Table, nzstats 16-1, link 1-2
LOADMAXTHRESHOLD 14-7 16-4 optimized 1-2
LOADMINTHRESHOLD 14-7 Host Net Table, nzstats 16-1, 16-5 rev 1-2
plan data 14-5 Host Table, nzstats 16-1, 16-6 krb5.conf file 11-24
query data 14-5 HTTPS port 443, opening 9-8 krb5.keytab file 11-25
service data 14-5 HTTPS verification 9-17
state data 14-5 HW Mgmt Channel Table, nzstats 16-1
table data 14-5
tables 14-14
hwDiskFull event type 8-7
hwFailed event type 8-7
L
LD_LIBRARY_PATH 2-6
CLI usage 14-27 hwHeatThreshold event type 8-7
LDAP authentication 11-4, 11-18
column access history 14-19 hwNeedsAttention event type 8-7
about 11-19
end of query table 14-24 hwPathDown event type 8-7
commands 11-27
failed authentication hwRestarted event type 8-7
failures 11-19
attempts 14-20 hwServiceRequested event type 8-7
returning to local
log entries for operations 14-21 hwThermalFault event type 8-7
authentication 11-20
overflow of query string 14-25 hwVoltageFault event type 8-7
LDAP server
plan history at beginning of
managing 11-19
plan 14-23
required information for
plan history at end of plan
execution 14-22
I Netezza 11-19
IBM Security Key Lifecycle Manager, LDAP, configuring SSL security 11-21
schema version 14-31
setup 6-4 ldap.conf file, editing for SSL
session termination 14-28
IBM Support servers, accessing 9-8 configuration 11-21
source Netezza system 14-21
identifiers, in CLI 3-4 ldap.conf.orig file 11-20
start of query data 14-25
inactive hardware 5-8 less command B-7
state changes 14-30
incompatible hardware 5-8 limit clause 11-36
table access history 14-30
incremental backup restore 13-32 Linux
views 14-14
indirect object privileges 11-17 accounts B-1
history configuration
inherited privileges 11-17 adding groups B-3
altering 14-11
initial configuration 1-1 boot directories 1-2
changing 14-11
initialized, system state 7-4 changing passwords B-3
display settings 14-12
initializing, system state 7-4, 7-10 command line editing B-8
show settings 14-12
insert privilege 11-11 common procedures B-1
history data 14-1
installation, Netezza 1-1 deleting accounts B-2
database types 14-1
integer deleting groups B-4
database versions 14-2
nzDbosSpill file 7-17 directories, displaying B-7
files 14-3
transaction id 12-5 file content, displaying B-7
loading process 14-2
interfaces 1-8 files, finding B-7
log directories 14-4
invalid state 5-10 groups B-3
managing collection of 14-9
inventory reporting log files, viewing B-7
processes 14-2
callhome 9-11 miscellaneous commands B-8
setup 14-4
IP addresses, for HA system 4-15 modifying accounts B-2
staging process 14-2
ISKLM, setup 6-4 modifying groups B-4
starting collection of 14-11
ismainplan 14-23 passwords 11-19
stopping collection of 14-11
rebooting B-4
history database 14-1
release level B-6
changing ownership 14-10
creating 14-5 J remote access 1-8
setting up accounts B-1
dropping 14-10 job
statistics B-5
maintaining 14-13 examples 15-29
stopping processes B-5
ownership, changing 14-10
string matching B-7
history database types 14-1
system errors B-5
history database versions 14-2
history-data events 8-30
K system time B-6
Kerberos authentication 11-4, 11-18, timing commands B-8
history, sql sessions 3-9
11-27 user 1-1
home directory 1-2
about 11-22 viewing statistics B-5
host
commands 11-27 Linux users, adding B-1
host CPU table 16-1
configuring 11-23 Linux-HA
host filesystem table 16-1
testing 11-26 about 4-1
host interfaces table 16-1
updating 11-26 active host, identifying 4-5
host management channel table 16-1
Kerberos configuration file 11-24 administration 4-2
host net table 16-1
Kerberos keytab file 11-25 failover 4-1

Linux-HA (continued) Netezza NzAdmin Tool (continued)
failover criteria 4-7 security model 11-9 nzadmin program 2-7
IP addresses 4-15 starting 7-6 uninstalling 2-8
logging and messages 4-12 stopping 7-7 viewing, distribution 12-9, 12-11
resource groups 4-1 system states 7-4 nzbackup command A-4
resource migration 4-7 uninstalling Windows tools 2-8 command syntax 13-12
list privilege 11-11 users and groups 11-1 description 3-1, A-1
loading history data 14-7 Netezza clients examples 13-15
LOADINTERVAL 14-7 UNIX, installing 2-2 nzcallhome command A-4
LOADMAXTHRESHOLD 14-7 UNIX, removing 2-6 nzconfigcrypto command A-8
loadmgr, description 7-8 Netezza Clients media 2-1 nzcontents command
LOADMINTHRESHOLD 14-7 Netezza server, installing Windows description 3-1, A-1, A-9
local authentication 11-18 tools 2-6 example 7-1, A-47
authentication methods Netezza system administrator nzconvert command 3-1, A-1
about 11-4 account 1-1 nzconvertsyscase command A-70
commands 11-27 Netezza Tools folder 2-7 nzdbg command A-69
password requirements 11-19 Netezza Windows Client media 2-6 nzDbosSpill, description 7-17
log file Network Interface State Change nzds command 3-1, A-1
alcapp 14-4 event 8-36 description A-10
alcloader 14-4 NetWorker 13-61 nzdumpcat command A-69
log files NO_ROWCOUNT session variable 3-11 nzdumpmem command A-69
viewing B-7 non-default port numbers, specifying on nzdumpschema command A-69
log on clients 2-12 description A-71
authentication 11-18 none state 5-10 nzdumptxjournal command A-69
invalid attempts 11-28 nonrecoverable internal error 7-11 nzevent command
privilege 11-17 notifications for events 8-12 add example 8-7
log, directory 1-2 nps resource group adding 8-7
logentryid 14-23 cannot run 4-17 attributes 8-11
logs, types of 7-12 checking 4-5 creating custom events 8-16
actions 7-11 contents 4-5 deleting 8-7
client 11-39 relocating to standby node 4-8 description 3-1, A-1, A-14
server 11-39 running on active host 4-5 disabling 8-7
subdirectory 1-2 safe shutdown 4-8 environment tags 8-12
services 4-7 generating 8-6
NPS, downgrading after enabling crypto pre-installed event rules 8-1
M support 10-10
npsid 14-23
setting disk thresholds 8-22
substitution tags 8-12
main menu, NzAdmin 3-16
npsinstanceid 14-23 threshold example 8-22
maintenance mode, transitioning to 4-9
NTP server B-6 nzhealthcheck 17-1
major release 7-1
numCpuCoreChanged event 8-36 events 17-6
manage hardware privileges 11-10
numCpuCoreChanged event type 8-7 mode 17-3
manage system privileges 11-10
numerics, disk usage 12-4 policy rules 17-2
master_db_database_template 12-1
nwIfChanged event type 8-7 using 17-4
master_db, database template 12-1
nz versioning 17-1
maximum, resource 15-10
directory 1-2, 1-5 nzhealthcheck command 17-9, A-18
menu, NzAdmin 3-16
user 1-1, 1-5 nzhealthcheck report
migration, in HA 4-7
nz directory 1-2 running 17-4
min/max values 12-15
NZ_BNR_MGR_PORT environment nzhistcleanupdb command
minimum, resource 15-10
variable 2-10 description 3-1, A-1
minor release 7-1
NZ_CLIENT_MGR_PORT environment nzhistcleanupdb command
mismatched
variable 2-10 description A-19
hardware 5-8
NZ_DATABASE, environment nzhistcreatedb command 14-5, A-21
missing state 5-10, 7-4
variable 13-12 description 3-1, A-1
monitoring daemon 17-9
NZ_DBMS_PORT environment nzhw command, description A-28
mount commands 2-2
variable 2-10 nzhw show command, arguments 5-2
multi-stream backups 13-4
NZ_HOST, environment variable 2-13 nzinitsystem command
multi-stream restore 13-5
NZ_PASSWORD, environment description A-69
multiple schema support
variable 2-14 syntax A-73
disabling 12-3
NZ_TMP_DIR variable 1-2 nzkey command A-34
enabling 12-2
NZ_USER, environment variable 2-13 nzkeybackup command A-39
NzAdmin nzkeydb command A-37
status indicator 3-15 nzkeyrestore command A-40
N System view 3-14 nzkmip command A-40
net system resources 15-10 NzAdmin main menu 3-16 nzload command
NetBackup 13-34 NzAdmin Tool description 3-1, A-1, A-42
configuring policy 13-35 installing 2-6 nzloadcat command A-69
integrating 13-36 introduction 3-12
Index X-5
nzlogmerge command nzstats command (continued) policy, configuring NetBackup 13-35
description A-69 SPU Partition Table 16-10 ports, numbers 2-10
syntax A-73 SPU Table 16-10 postgres, description 7-8
nzlogmerge.info command A-69 System Group 16-10 postmaster, description 7-8
nzmakedatakit command A-69 Table Table 16-11 preonline, system state 7-4
nznpssysrevs command nzstop command preonlining, system states 7-10
description A-43 arguments 7-7 preptime 14-23
nzpassword command 2-13, 3-1, A-1 description 3-1, A-1, A-63 prioritized query execution 15-24, 15-25
nzpassword command, storing example 7-7 priority
passwords 2-14 nzsystem command assigning to jobs 15-24
nzpassword, command A-43 description 3-1, A-1 example 15-29
nzpush command, description A-69 system configuration file A-65 levels 15-25
nzreclaim command A-1 nzvacuumcat, description 7-8 nzadmin tool A-49
description 3-1 nzzonemapformat command A-68 plans 15-25
nzresetxlog command A-69 privileges
nzresolv service 1-5 about 11-9
nzrestore command
description 3-1, A-1, A-47
O backup 13-15
client session 11-17
object privileges
overview 13-22 create table 13-21
description of 11-11
syntax 13-23 database statistic 11-17
security model 11-9
nzrev command 7-1 displaying 11-12
ODBC
description 3-1, A-1, A-47 indirect 11-17
setting logs 11-39
rev 7-1 log on 11-17
offlining, system state 7-4
nzscratch directory 1-2 nzcontents A-4
ok state 5-10
nzsession command nzrev A-4
ON_ERROR_STOP 3-9
arguments 12-23 nzstart A-4
online state 5-10
changing priority 15-29 nzstop A-4
online, system state 7-4, 7-10
description 3-1, A-1, A-49 object privileges 11-11
operators, runaway query 8-24
examples 12-25 restore 13-28
opid 14-23
viewing 12-23 transaction 11-17
OrExpr event rule 8-11
nzspupart command, description A-54 procedure, privilege 11-15
organization percentage 12-22
nzsqa command A-69 processes
organizing key 12-12
nzsql command displaying B-5
overserved group 15-16
description 3-1, A-1, A-56 stopping on Linux B-5
managing database 3-5 ps command B-5
managing transactions 12-25 public group 1-1, 11-3
ON_ERROR_STOP 3-9 P public views, system 11-40
resource control file 3-9 pages, definition 12-3
session history 3-9 pam_cracklib dictionary 11-6
sessions 12-23
slash commands 3-10
pam_cracklib utilities 11-5
password
Q
qcrestart 14-23
nzstart command admin user 1-1
Query History Table
arguments 7-6 authentication, local 11-19
_v_qryhist 12-30
description 3-1, A-1, A-56 clear-text 2-13
nzstats 16-1, 16-9
nzstate command encrypted 2-13
Query Table
arguments 7-2 history 11-7
_v_qrystat 12-30
description 3-1, A-1 nz user 1-1
nzstats 16-1, 16-8
errors NZ_PASSWORD 2-14
queuetime 14-23
offline system 7-2 nzpassword command 2-13
nzstats command reuse 11-7
_v_qryhist 12-30 specifying length 11-28
_v_qrystat 12-30 storing for Netezza users 2-14 R
Database Table 16-2 password content controls 11-5 random distribution, benefits 12-10
DBMS Group 16-2 password expiration 11-35 rebooting Linux B-4
description 3-1, A-1 PASSWORDEXPIRY setting 11-35 recoverable internal error 7-11
Hardware Management Channel patch release 7-1 Red Hat 1-8
Table 16-7 paused, system state 7-4 redirecting restore 13-40
Host CPU Table 16-3 Per Table Per Data Slice Table, regen events 8-26
Host Filesystem Table 16-3 nzstats 16-1, 16-8 regeneration
Host Interfaces Table 16-4 permissions, backup 13-21 manual 5-27
Host Mgmt Channel Table 16-4 pingd command 4-2 regenError event type 8-7
Host Network Table 16-5 planid 14-23 regenFault event type 8-7
Host Table 16-6 plans, directory 1-2 registry settings
overview 16-1 Pluggable Authentication Module (PAM), changing 7-19
Per Table Per Data Slice Table 16-8 for LDAP 11-4, 11-18 displaying 7-18
Query History Table 16-9 PMRs registry, configuration 7-18
Query Table 16-8 enabling with callhome 9-10 release descriptions 7-1

release level 7-1, B-6 SED keys (continued) SQL command (continued)
remote access 1-8 managing with ISKLM A-40 UPDATE command 12-16
renaming SEDs 6-1 SSH, remote access 1-8
scheduler rule 15-7 changing host AEKs 6-12 SSL
resource group changing SPU AEKs 6-14 about 11-29
assigning users 15-21 checking AEKs 6-9 certificate 11-30
example 15-11 configuring for auto-lock mode 6-1 configuration steps for LDAP 11-21
settings 15-10 disabling auto-lock mode 6-3 using to secure LDAP
resource groups, about 4-1 extracting AEKs 6-12, 6-13 communications 11-21
resource migration 4-7 generating AEKs 6-8 stage release 7-1
resource percentage 15-16 keystore 6-4 standby host, identifying 4-5
restore listing AEKs 6-8 standby node, relocating to 4-8
examples 13-29 monitoring with nzevent rules 6-15 starttime 14-23
nzrestore 13-22 returning to secure erase mode 6-3 startupsvr, description 7-8
redirecting 13-40 select statistics
step-by-step 13-32 privilege 11-11 automatic statistics 12-16
syntax 13-23 self-encrypting drives 6-1 database tables 12-15
Restore sendMail.cfg file 8-12 dispersion 12-16
privilege 13-28 configuring 9-6 Linux B-5
restore privileges 11-10 sendMail.cfg, event rule 1-2 updating 12-15
restoring, backup 13-32 sequences statsmgr, description 7-8
resuming, system states 7-10 privilege 11-15 statsSvr, description 7-8
revision level sessionid 14-23 status indicator for NzAdmin 3-15
displaying 7-18 sessionmgr, description 7-8 status reporting
rlogin, remote access 1-8 sessions callhome 9-10
root certificate 11-21 definition 12-23 stopped, system state 7-4
row count information, suppressing 3-11 overview 13-20 storage design
rowid 12-5 viewing A-49 IBM Netezza models 5-12
rowset limit SET AUTHENTICATION command, Netezza C1000 5-13
specifying 11-36 using to set LDAP 11-19 stored procedures, privileges 11-15
values 11-36 settings, configuration 7-18 subminor release 7-1
rsh, remote access 1-8 changing 7-19 submittime 14-23
runaway query events 8-24 displaying 7-18 superuser, Netezza 11-3
runaway query, operators 8-24 share suppressing row count information 3-11
runawayQuery event type 8-7 directory 1-2 Synchronous mirroring 4-1
runCmd arguments 8-12 postgres-specific 1-2 sys, directory 1-2
short query bias 15-22 system configuration files 1-2
shutdown B-4 sys/init, directory 1-2
S signature 14-23
slash commands 3-10
sysHeatThreshold event type 8-7
sysinfo report
sbin directory, contents 1-2
smallint, integer type 12-4 running 17-7
scheduler rule
smartThreshold, event type 8-7 sysmgr, description 7-8
activating 15-7
software revision level sysStateChanged event type 8-7
changing the owner of 15-7
displaying 7-18 system
creating 15-7
software version 7-1, B-6 default directory 12-1
deactivating 15-7
SP 800-131a errors B-5
deleting 15-7
how to enable 10-2 logs 7-12
dropping 15-7
SP 800-131a enhanced cryptography system group table 16-1
renaming 15-7
enabling 10-3 views C-2
tasks 15-7
SP 800-131a support 10-1 system administration, about 1-1
scheduler rules 15-2
spare system administrator account 1-1
schema overview 12-2
hardware 5-8 system components, displaying 3-13
scsiDiskError event type 8-7
split-brain, recovering from 4-14 system configuration 7-18
scsiPredictiveFailure event type 8-7
SPU system configuration file
Secure Sockets Layer (SSL) protocols.
managing 5-21 nzsystem command A-65
SeeSSL. 11-21
power up 7-10 System Group, nzstats 16-1, 16-10
security
SPU partition table 16-1 system information views 11-40
invalid logons 11-28
SPU table 16-1 system resource
managing 11-1
SPU core events 8-32 allocation 15-10
model 11-9
SPU Partition Table, nzstats 16-1, 16-10 percentage 15-10
unlocking accounts 11-28
SPU Table, nzstats 16-1, 16-10 system state change events 8-17
SED key store
spuCore event type 8-7 system states
backing up A-39
SQB 15-22 down 7-4
managing A-37
SQB flag 15-22 initialized 7-4
restoring A-40
SQL command initializing 7-4, 7-10
SED keys
CREATE TABLE AS 12-16 nzstate command 7-2
about 6-7
INSERT command 12-16 offlining 7-4
managing A-34
Index X-7
system states (continued) troubleshooting views (continued)
online 7-4, 7-10 enhanced cryptography support 10-7 _v_sys_view C-2
paused 7-4 truncate _v_table C-1
pausing 7-4 privilege 11-11 _v_table_dist_map C-1
preonline 7-4 tzoffset 14-23 _v_table_index C-1
preonlining 7-10 _v_user C-1
resuming 7-10 _v_usergroups C-1
stopped 7-4
types 7-4
U _v_view C-1
system 11-40, C-2
uname command B-6
system temperature, events 8-29 voltage fault events 8-33
underserved group 15-16
system time, changing B-6
unfence privileges 11-10
System view 3-14
uninstalling Windows tools 2-8
systemStuckInState event type 8-7
UNIX Netezza clients W
installing 2-2 WildcardExpr event rule 8-11
removing 2-6 Windows tools 2-6
T unreachable state 5-10 WLM
table storage, about 12-3 update privilege 11-11 See workload management
Table Table, nzstats 16-1, 16-11 user accounts workload management 15-1
table-oriented zone maps 12-19 encrypting passwords for 2-13 compliance 15-16
tables passwords, storing 2-14 compliance reports 15-17
base tables 12-10, 12-11 user names, matching Netezza and GRA 15-8
grooming 12-20 LDAP 11-19 overserved and underserved
intra-session tables 12-10, 12-11 user privilege 11-15 groups 15-16
privilege 11-15 useradd command B-1 PQE 15-24
record header 12-4 users prioritized query execution 15-24
special fields 12-4 methods for managing 11-1 priority 15-25
table table 16-1 Netezza database 11-1 priority levels 15-25
tuning 12-5 rowset limits 11-36 resource
Telnet, remote access 1-8 superuser, Netezza 11-3 allocation 15-10
temperature events unlocking 11-28 maximum 15-10
hardware 8-28 minimum 15-10
system 8-29 percentage 15-10
template event rules 8-1
TFTP
V settings 15-10
short query bias 15-22
vacuum analyze, see generate
bootsvr 7-8 system resource allocation 15-10
statistics 12-15
power up 7-10 techniques 15-1
varchar, data type 12-4
threshold
variables, environment 2-8
disk space 8-22
variant release 7-1
example 8-22
time command B-8
Veritas NetBackup 13-34 X
version, software 7-1 xid 14-23
time with time zone, data type 12-4
versions of history database 14-2 xinetd, remote access 1-8
time, disk usage 12-4
view command B-7
timestamp, temporal type 12-4
View, privilege 11-15
Tivoli Storage Manager
encrypted backups 13-43
viewing
sessions A-49
Z
tls_cacertfile option 11-21 zone map format 12-19
system logs 7-12
tls_cert option 11-21 zone maps
views
tls_key option 11-21 automatic statistics 12-16
_v_aggregate C-1
tmp, directory 1-2 changing formats A-68
_v_database C-1
top command B-5
_v_datatype C-1
topology balance
_v_function C-1
monitoring 8-35
_v_group C-1
Topology Imbalance event 8-36
_v_groupusers C-1
TopologyImbalance event 8-35
_v_index C-1
toporegen command, description A-69
_v_operator C-1
totalsnippets 14-23
_v_qryhist 12-30
transaction ID, overview 12-5
_v_qrystat 12-30
transaction objects
_v_relation_column C-1
monitoring 8-33
_v_relation_column_def C-1
TransactionLimitEvent event 8-33
_v_sequence C-1
transactionLimitEvent event type 8-7
_v_session C-1
transactions
_v_sys_group_priv C-2
examples 12-25
_v_sys_index C-2
managing 12-25
_v_sys_priv C-2
nzsql 12-25
_v_sys_table C-2
privilege 11-17
_v_sys_user_priv C-2
system limit 15-29

IBM®
Part Number: 20282-24 Rev. 3
Printed in USA

Netezza System Admin Guide

Uploaded by

Document Informationclick to expand document information

Document Informationclick to expand document information

Copyright:

Available Formats

Netezza System Admin Guide

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Netezza System Admin Guide

Uploaded by

Copyright:

Available Formats

IBM Netezza

IBM Netezza System Administrator’s

Revised: December 4, 2015

© Copyright IBM Corp. 2001, 2015 iii

iv IBM Netezza System Administrator’s Guide

vi IBM Netezza System Administrator’s Guide

Chapter 15. Workload management 15-1 Appendix A. Netezza CLI . . . . .. A-1

Appendix B. Linux host administration Appendix C. Netezza user and system

viii IBM Netezza System Administrator’s Guide

© Copyright IBM Corp. 2001, 2015 ix

© Copyright IBM Corp. 2001, 2015 xi

xii IBM Netezza System Administrator’s Guide

Federal Communications Commission (FCC) Statement

Industry Canada Class A Emission Compliance Statement

This Class A digital apparatus complies with Canadian ICES-003.

Avis de conformité à la réglementation d'Industrie Canada

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

Australia and New Zealand Class A Statement

This product is a Class A product. In a domestic environment, this product might

European Union EMC Directive Conformance Statement

This product is in conformity with the protection requirements of EU Council

© Copyright IBM Corp. 2001, 2015 xiii

International Business Machines Corp.

European Community contact:

IBM Technical Regulations, Department M456

Germany Class A Statement

Deutschsprachiger EU Hinweis: Hinweis für Geräte der Klasse A EU-Richtlinie

Dieses Produkt entspricht den Schutzanforderungen der EU-Richtlinie

Um dieses sicherzustellen, sind die Geräte wie in den Handbüchern beschrieben zu

EN 55022 Klasse A Geräte müssen mit folgendem Warnhinweis versehen werden:

Deutschland: Einhaltung des Gesetzes über die

Dieses Produkt entspricht dem “Gesetz über die elektromagnetische Verträglichkeit

Zulassungsbescheinigung laut dem Deutschen Gesetz über die

xiv IBM Netezza System Administrator’s Guide

Der verantwortliche Ansprechpartner des Herstellers in der EU ist:

Generelle Informationen: Das Gerät erfüllt die Schutzanforderungen nach EN 55024

Japan VCCI Class A Statement

Japan Electronics and Information Technology Industries

Japan Electronics and Information Technology Industries Association (JEITA)

Japan Electronics and Information Technology Industries

Japan Electronics and Information Technology Industries Association (JEITA)

Electronic emission notices xv

Russia Electromagnetic Interference (EMI) Class A Statement

People's Republic of China Class A Electronic Emission

Taiwan Class A Compliance Statement

xvi IBM Netezza System Administrator’s Guide

Provide approved circuit breakers on all power sources.

Product might be powered by redundant power sources. Disconnect ALL power

© Copyright IBM Corp. 2001, 2015 xvii

If you need help

How to send your comments

We appreciate your suggestions.

© Copyright IBM Corp. 2001, 2015 xix

Initial system setup and information

© Copyright IBM Corp. 2001, 2015 1-1

Netezza software directories

Host software directory

1-2 IBM Netezza System Administrator’s Guide