8.8.1 Steps to take before swapping the HADB server with its revised version
The following describes the steps you must take before swapping the HADB server with its revised version.
- Important
-
Before swapping the HADB server with its revised version, do not change the values specified in the environment variables ADBLANG and ADBCLTLANG. If they are changed, you might not be able to correctly swap the HADB server.
The language code and nation code specified in the LANG environment variable can be changed as follows:
-
Change from ja_JP.UTF-8 to en_US.UTF-8
-
Change from en_US.UTF-8 to ja_JP.UTF-8
The encoding set (type of character encoding) cannot be changed.
Note that if you change the value of the LANG environment variable, you also need to change the value of the LANG environment variable for the HADB client.
-
- Organization of this subsection
(1) Checking the memory requirement
Swapping the HADB server with its revised version might increase the HADB server's memory requirement. For details, see the Release Notes.
(2) Checking whether environment variables need to be changed
If you swap the HADB server with its revised version, you might need to change environment variables. For details, see the Release Notes.
(3) Checking whether kernel parameters need to be changed
If you swap the HADB server with its revised version, you might need to change kernel parameters. For details, see the Release Notes.
(4) Checking whether the default values of operands in the server definition have been changed
Swapping the HADB server with its revised version might change the default values of operands in the server definition. For details, see the Release Notes.
(5) Checking whether reserved words have been added
Swapping the HADB server with its revised version might add reserved words. You cannot specify a reserved word in an SQL statement (for example, as a table or column name). If a character string that is the same as an added reserved word is specified in an SQL statement, the SQL statement will cause an error after the HADB server is swapped with its revised version. Therefore, check whether a character string that is the same as an added reserved word is specified in an SQL statement. If a character string that is the same as an added reserved word is specified, enclose it in double quotation marks ("). For details, see Reserved words in SQL Basics in the manual HADB SQL Reference.
(6) Terminating application programs and commands normally
Before you swap the HADB server with its revised version, terminate the application programs and commands normally.
(7) Terminating the HADB server normally
Before you swap the HADB server with its revised version, use the adbstop command to terminate the HADB server normally. If the HADB server has already stopped, use the following procedure to confirm that it terminated normally.
Procedure:
-
Execute the adbls -d srv command.
Confirm that the HADB server status, which is output to the output item STATUS, is STOP.
If it is STOP, proceed to step 2 or 3.
-
Check the server message log file.
Open the server message log file $ADBDIR/spool/adbmessageXX.log#) and confirm that the termination mode, output in the KFAA91154-I message, is normally.
#: XX is a sequential number in the range from 01 to 04.
-
Check syslog.
Open syslog and confirm that the termination mode, output in the KFAA91154-I message, is normally.
If the result in step 1 is STOP and the result in step 2 or 3 is normally, the HADB server has terminated normally.
If the HADB server has not terminated normally, use the adbstart command to start it, and then use the adbstop command to terminate it normally.
(8) Backing up the server directory
Before swapping the HADB server with its revised version, you need to back up the server directory.
If you swap the HADB server with the revised version while the HADB server is in abnormally terminated status, you will not be able to start the HADB server. To prevent such problems, make a backup of the server directory. Delete the backup after you finish swapping the HADB server with its revised version.
For details about the procedure for acquiring a backup, see (2) Backup procedure in 10.3.1 Backup acquisition method.
- Multi-node function
-
If you are using the multi-node function, make a backup of the server directory on the HADB servers on all nodes.