IBM Support

Changing time/date and timezone on PureData Systems for Analytics.

Question & Answer


Question

How do I change time/date and timezone on N100x N200x N300x appliance?

Answer

Please login to the appliance console using 'root' user and perform the following steps/commands:-

1. Changing the timezone ( Example : MST - EST )
[root@netezza ~]#cd /opt/nz-hwsupport/install_tools/

[root@netezza install_tools]# ./nz-timeset.pl

nz-timeset.pl rev 1.0.10

Determined that we are in a redundant environment.
Checking connectivity to the other host.
Connection to other host successful.


What do you want to do?

1: Set timezone on hosts
2: Set time/date on hosts
3: Display current settings
4: Exit
Select one : 1

Current date/time and timezone:
HA1: 16-01-27 09:44:41 AM MST
HA2: 16-01-27 09:44:42 AM MST

Select a Continent:

1: Africa
2: Americas
3: Asia
4: Europe
5: Indian Ocean
6: Pacific Ocean
7: GMT
8: Exit
: 2

1: Antigua & Barbuda
2: Anguilla
3: Argentina
4: Aruba
5: Barbados
6: St Barthelemy
7: Bolivia
8: Bonaire Sint Eustatius & Saba
9: Brazil
10: Bahamas
11: Belize
12: Canada
13: Chile
14: Colombia
15: Costa Rica
16: Cuba
17: Curacao
18: Dominica
19: Dominican Republic
20: Ecuador
21: Grenada
22: French Guiana
23: Greenland
24: Guadeloupe
25: Guatemala
26: Guyana
27: Honduras
28: Haiti
29: Jamaica
30: St Kitts & Nevis
31: Cayman Islands
32: St Lucia
33: St Martin (French part)
34: Martinique
35: Montserrat
36: Mexico
37: Nicaragua
38: Panama
39: Peru
40: St Pierre & Miquelon
41: Puerto Rico
42: Paraguay
43: Suriname
44: El Salvador
45: Sint Maarten
46: Turks & Caicos Is
47: Trinidad & Tobago
48: United States
49: Uruguay
50: St Vincent
51: Venezuela
52: Virgin Islands (UK)
53: Virgin Islands (US)
Select a Region :

Select a Region : 48

1: Eastern Time
2: Eastern Time - Michigan - most locations
3: Eastern Time - Kentucky - Louisville area
4: Eastern Time - Kentucky - Wayne County
5: Eastern Time - Indiana - most locations
6: Eastern Time - Indiana - Daviess, Dubois, Knox & Martin Counties
7: Eastern Time - Indiana - Pulaski County
8: Eastern Time - Indiana - Crawford County
9: Eastern Time - Indiana - Pike County
10: Eastern Time - Indiana - Switzerland County
11: Central Time
12: Central Time - Indiana - Perry County
13: Central Time - Indiana - Starke County
14: Central Time - Michigan - Dickinson, Gogebic, Iron & Menominee Counties
15: Central Time - North Dakota - Oliver County
16: Central Time - North Dakota - Morton County (except Mandan area)
17: Central Time - North Dakota - Mercer County
18: Mountain Time
19: Mountain Time - south Idaho & east Oregon
20: Mountain Time - Navajo
21: Mountain Standard Time - Arizona
22: Pacific Time
23: Alaska Time
24: Alaska Time - Alaska panhandle
25: Alaska Time - southeast Alaska panhandle
26: Alaska Time - Alaska panhandle neck
27: Alaska Time - west Alaska
28: Aleutian Islands
29: Metlakatla Time - Annette Island
30: Hawaii
Select a Timezone : 1
Update existing timezone to America/New_York? [y]: y

Changed /etc/sysconfig/clock

Updated local timezone file

Copied /etc/sysconfig/clock to other node.

Copied zonefile to other node.
Updated hwclock successfully
Updated hwclock successfully

Zone changes are immediately effective on the host(s) and no reboot is required.
Database must be restarted (nzstop/nzstart) in order to recognize time changes.

If no further changes are needed, stop and start NPS for the database to sync with the new timezone.


2. Setting time/date on the hosts:

[root@netezza ~]#cd /opt/nz-hwsupport/install_tools/

[root@netezza install_tools]# ./nz-timeset.pl

nz-timeset.pl rev 1.0.10

Determined that we are in a redundant environment.
Checking connectivity to the other host.
Connection to other host successful.


What do you want to do?

1: Set timezone on hosts
2: Set time/date on hosts
3: Display current settings
4: Exit

Select one : 2
Current date/time:
HA1: 16-01-27 11:49:55 AM EST
HA2: 16-01-27 11:49:55 AM EST
Enter Year [16]: 16
Enter Month [01]: 01
Enter Day [27]: 27
Enter Hour [11]: 11
Enter Minute [49]: 49
Enter AM/PM [AM]: AM
Setting date:
Wed Jan 27 11:49:00 EST 2016
Wed Jan 27 11:49:00 EST 2016

Updated hwclock successfully
Updated hwclock successfully

Time changes are immediately effective on the host(s) and no reboot is required.
Database must be restarted (nzstop/nzstart) in order to recognize time changes.

1: Set timezone on hosts
2: Set time/date on hosts
3: Display current settings
4: Exit
Select one : 4

[root@netezza install_tools]#

3. You needs to repeat the steps for the standby host also.

4. Applying time setting
After completing of time setting steps 1-3.
Please login as 'nz' user and perform a database restart.
(Restarting the database is required for the change to take effect.)

[nz@netezza ~]$ nzstop
[nz@netezza ~]$ nzstart

If the script fails for whatever reason then this technote describes how you can manually perform the change:
http://www.ibm.com/support/docview.wss?uid=swg21570589

If in-doubt, please contact IBM Support and we will assist you with the above.

[{"Product":{"code":"SSULQD","label":"PureData System for Analytics"},"Business Unit":{"code":"BU029","label":"Data and AI"},"Component":"IBM Netezza Analytics","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"1.0.0","Edition":""}]

Document Information

Modified date:
17 October 2019

UID

swg21975580