Hitachi

Hitachi Advanced Database Setup and Operation Guide


8.6.2 Upgrading the server version

After you have taken the steps described in 8.6.1 Steps to take before upgrading the server version, upgrade the HADB server version using the following procedure.

Multi-node function

If you are using the multi-node function, perform steps 1. Log on to the OS from the HADB administrator's OS account through 9. Confirm that the HADB server has been swapped on the HADB servers on all nodes. After that, perform step 10. Upgrade the database version.

Procedure

  1. Log on to the OS from the HADB administrator's OS account.

    Log on to the server machine's OS from the HADB administrator's OS account that you have been using.

    Important

    Do not modify the HADB administrator's OS account. If you do, you might not be able to upgrade the HADB server version correctly.

  2. Create the directory for storing the installation data.

    Create a directory to store the HADB server installation data. To do this, enter the following OS command:

    mkdir path-name-of-desired-directory

    An example follows in which /home/adbmanager/vup is selected as the directory path name.

    ▪ Command execution example

    mkdir /home/adbmanager/vup
  3. Grant write privileges to the directory for storing the installation data.

    Grant write privileges to the directory for storing the installation data so that the HADB administrator can access the directory for write operations. To do this, enter the following OS command:

    chmod 755 path-name-of-desired-directory

    An example follows in which /home/adbmanager/vup is selected as the directory path name.

    ▪ Command execution example

    chmod 755 /home/adbmanager/vup
  4. Mount the file system CD-ROM.

    Allow the file system CD-ROM containing the installation data (tar.gz file) for the HADB server to mount automatically.

    If the file system CD-ROM does not mount automatically, you must mount it manually. To do so, enter the following operating system command:

    mount /dev/cdrom /media

    The underlined portion is the name of the mount directory for the file system CD-ROM. It varies depending on the environment.

    Important

    Depending on the machine being used, the directory and file names used on the CD-ROM might be different from those shown above. Enter the directory name that is displayed exactly as it is shown when you execute the ls operating system command.

  5. Copy the installation command (adbinstall command).

    Copy the HADB server installation command (adbinstall command), which is stored in the mounted file system CD-ROM, to a directory of your choice.

    Enter the following operating system command to copy the adbinstall command to the desired directory:

    cp /media/adbinstall path-name-of-desired-directory

    The underlined portion is the name of the mount directory for the file system CD-ROM. It varies depending on the environment.

    An example follows in which /home/adbmanager/vup is selected as the directory path name.

    • Command execution example

    cp /media/adbinstall /home/adbmanager/vup
  6. Copy the installation data (tar.gz file).

    Copy to a directory of your choice the HADB server installation data (tar.gz file) that is stored on the mounted file system CD-ROM.

    Enter the following operating system command to copy the tar.gz file to the directory of your choice:

    cp /media/hitachi_advanced_data_binder_server-$VR.tar.gz
       path-name-of-directory-of-your-choice

    The underlined portion is the name of the mount directory for the file system CD-ROM. It varies depending on the environment. $VR indicates the HADB version and release number.

    Important

    Copy the tar.gz file to the directory in which the adbinstall command was stored in step 5. Copy the installation command (adbinstall command). You can upgrade the HADB server only if the adbinstall command and the tar.gz file are stored in the same directory.

    An example follows in which /home/adbmanager/vup is selected as the directory path name.

    • Command execution example

    cp /media/hitachi_advanced_data_binder_server-$VR.tar.gz
       /home/adbmanager/vup
  7. Assign execution privileges to the installation command (adbinstall command).

    Assign execution privileges to the HADB server installation command (adbinstall command), which you copied to the directory of your choice, so that the HADB administrator has execution privileges.

    An example follows in which the installation command (adbinstall command) is stored in /home/adbmanager/vup.

    ▪ Command execution example

    chmod 777 /home/adbmanager/vup/adbinstall

    Execution privileges have now been assigned to the installation command (adbinstall command).

  8. Swap the HADB server.

    To swap the HADB server, execute the installation command (adbinstall command) that you copied to the directory of your choice.

    Execute the following HADB command to swap the HADB server:

    /vup/adbinstall -s server-directory-path-name

    For the -s option, specify the absolute path for the server directory being used. If you specify for the -s option a directory that cannot be written by the HADB administrator, an error occurs and the KFAA91553-E message is output.

    The KFAA91553-E message is also output if the HADB administrator does not have write privileges for the installation command (adbinstall command) and the installation data (tar.gz file).

    If the KFAA91553-E message is output, grant write privileges for the target directory.

    Note

    The underlined portion is the path name of the directory that was selected to copy and store the adbinstall command.

    When you execute the adbinstall command, the KFAA91554-Q message is output, asking whether you want to overwrite the directory. Press Y to overwrite it.

    In the following execution example, /home/adbmanager/vup is selected as the directory path name and /HADB/server is selected as the server directory path name.

    ■ Command execution example

    /home/adbmanager/vup/adbinstall -s /HADB/server

    If you execute the adbinstall command as root rather than using the HADB administrator's OS account, a warning message (KFAA91558-W message) is output. Normally, the HADB administrator's OS account is used to execute the adbinstall command. Therefore, if the KFAA91558-W message is output, make sure that executing the adbinstall command by root does not cause any problems.

    If a program exists, enter n or N in response to the input request in the KFAA91559-Q message that is output after the KFAA91558-W message. Then, execute the adbinstall command by using the HADB administrator's OS account.

    If you execute the adbinstall command as a superuser other than root, the KFAA91558-W message is not output.

    Note

    root indicates a user for which 0 is displayed by executing the OS's id -u command. This includes a case where a value of 0 is displayed when the OS's id -u command is executed after another OS user was changed to root by using the OS's su command.

  9. Confirm that the HADB server has been swapped.

    Confirm that swapping of the HADB servers performed in step 8. Swap the HADB server has been completed. Execute the following HADB command to check the HADB server version.

    Multi-node function

    If you are using the multi-node function, check the HADB server version information by executing the following command on all HADB servers on all nodes:

    adbls -d ver

    If no version information is displayed even when you execute the adbls -d ver command, there might be a specification error in one of the following environment variables:

    • The server directory swapped in step 8. Swap the HADB server has not been set in the ADBDIR environment variable.

    • The bin directory under the server directory that was swapped in step 8. Swap the HADB server has not been set in the PATH environment variable.

      Note

      For details about environment variables, see 8.4 Setting environment variables.

  10. Upgrade the database version.

    Execute the following HADB command to start the HADB server. Version upgrading starts.

    adbstart

    After execution of the adbstart command, the KFAA91107-Q message is output, asking whether you want to upgrade the database version. Press Y to upgrade it.

    If the adbstart command terminates normally, upgrading of the HADB server version is complete.

    Multi-node function

    If you are using the multi-node function, start the HADB servers in the multi-node configuration as explained in 16.4.1 Starting the HADB servers in the multi-node configuration. If you attempt to start the HADB server on the master node, the KFAA91107-Q message asking whether the database version is to be upgraded is displayed. Press Y to upgrade the database version.

    If the HADB servers on all nodes start successfully, the HADB server version has been upgraded.

    Important

    If the adbstart command does not terminate normally and the version upgrade of the HADB server fails , see 8.6.4 Steps to take when version upgrading fails.