4.8 Replacing HADB client with a revised version
This section describes how to replace HADB client with a revised version.
When the following condition is met, you can replace HADB client with a revised version instead of upgrading it.
-
You intend to perform an overwrite installation of HADB client with an edition that has the same version and revision number but a different code
- Note
-
The following explains how to identify the version number, revision number, and code.
As an example, consider a HADB client with the version information 03-02-/A:
-
03 is the version number.
-
02 is the revision number.
-
The underlined part (-/A) is the code.
-
The following shows examples that constitute replacement with a revised version of HADB client is possible, and examples that do not.
- ▪ Scenarios where HADB client is replaced with a revised version
-
For example, in the following scenarios, because the version numbers and revision numbers are the same, the process constitutes replacement with a revised version.
03-02 -> 03-02-/A
03-02-/B -> 03-02-/D
- ▪ Scenarios where HADB client is not replaced with a revised version
-
For example, in the following scenarios, because the version number or revision number differs, the process does not constitute replacement with a revised version.
03-02 -> 03-03-/A
03-02-/B -> 03-03-/D
This scenario is considered to be an upgrade of the HADB client. For details about how to upgrade an HADB client, see 4.6 Upgrading an HADB client.
- Note
-
-
Replace the existing HADB client with the updated HADB client that supports the updated HADB server version.
-
There are notes regarding the installation data. Before replacing the client, see the note in (1) Installing an HADB client of 4.2.1 HADB client for Windows for the Windows version of the HADB client. For the Linux version, see the note in (2) Installing an HADB client of 4.2.2 HADB client for Linux.
-
- Organization of this section