Skip to end of metadata
Go to start of metadata

Overview

  • Patching means minor version changes.
    Altibase server version consists of 4 or 5 digits.
    The first three digits refer to the major version and the last one or two digits refer to the minor version.
    Changing the last three digits without changing the first three digits is called a 'patch', and changing the first three digits is called 'upgrade'.

  • This page describes the procedure for patching Altibase servers in Unix and Linux environments.
  • Since the Altibase server patch must be performed after the Altibase server is shut down, service downtime is required.
  • Therefore, the user must secure downtime before patching.

Preparation before patching

Check the following before proceeding.

  • Can Altibase server downtime be secured? (Confirmed with the client)
  • Does the meta version change after patching? (Confirm with Altibase engineer)
  • Are there any caveats if the patch version is different from the current version? (Confirm with Altibase engineer)
    Example: In order to patch from HDB 4.3.9.44 to Altibase HDB 4.3.9.233.

Patch Procedure

1. Check the current version

  • Make a note of the version check result below.

    How to check Altibase server version

2. Shutdown Altibase Server ** 

  • Shutdown the Altibase server.

    How to shutdown Altibase server

    After the shutdown, check the Altibase server process and service port LISTEN status. When the following two commands are executed, there should be no results to indicate a normal shutdown.

3. Backup existing installation files

  • Back up necessary directories so that problems can be recovered after patching.

    Example of directory backup

    If the size of the $ALTIBASE_HOME directory is not large, the user can make a full backup of the $ALTIBASE_HOME directory as shown below.

4. Upload patch package and change permissions

ALTIBASE HDB server version 5.5.1 or later (all versions since 5.5.1, 6.1.1, 6.3.1, and 6.3.1)

  • Log in as the ALTIBASE HDB server installation user.
  • Upload the patch package to a random path.
  • From ALTIBASE HDB server version 5.5.1, the Java-based installer was used, and the package name ends with .run as shown below.

  • Grant execute permission to run the package.

    How to change execution permission

ALTIBASE HDB server version 5.5.1 or earlier (all versions below 5.3.3 such as 4.3.9, 5.3.3, etc.)

  • Log in as the ALTIBASE HDB server installation user.
  • Upload the patch package under the $ALTIBASE_HOME directory.

  • ALTIBASE HDB Server versions earlier than 5.5.1 provide compressed files.

5. Perform the patch

ALTIBASE HDB server version 5.5.1 or later (all versions since 5.5.1, 6.1.1, 6.3.1, and 6.3.1)

  • After executing the executable file as shown below, the subsequent operation proceeds according to the message.

ALTIBASE HDB server version 5.5.1 or earlier (all versions below 5.3.3 such as 4.3.9, 5.3.3, etc.)

  • Move to the $ALTIBASE_HOME directory and extract the files as follows.

6. Check the patch version

  • After completing the patch execution, check the version to see if the patch is applied.

    How to check Altibase server version

7. Copy necessary files from the backup file

  • If the default password (manager) of the sys user is changed, the $ATLIBASE_HOME/bin/server, is, il scripts would have changed.

  • In this case, copy server, is, and il from the bin directory of the backup directory to $ALTIBASE_HOME/bin.

    $ cd $ALTIBASE_HOME
$ cp -p bin.bak/server bin/
$ cp -p bin.bak/is bin/
$ cp -p bin.bak/il bin/

8. STARTUP ALTIBASE HDB Server **

  • After starting the Altibase server process, check the process and service port listen status.

    After shutdown, check the Altibase server process and service port LISTEN status.

    When the following two commands are executed, there should be no results to indicate a normal shutdown.

Precautions

Check meta version before/after patch

  • If the meta version changes, the database cannot be reverted to a lower version.
  • After patching to a higher version, there may be cases where the user inevitably needs to revert to a lower version. If the meta version is changed, this cannot be done.
  • Therefore, if the meta version changes, the user should be aware of this and proceed with the patching, and if necessary, take an offline full backup before the patch.
  • Offline full backup targets include data files, log anchor files, log files, and configuration files.

When patching from ALTIBASE HDB 4.3.9.1 ~ 4.3.9.50 to 4.3.9.51 ~**

If the following conditions are satisfied, the replication will not work after patching.

  • When patching from ALTIBASE HDB 4.3.9.1 ~ 4.3.9.50 to 4.3.9.51 ~

  • Replication environment

Therefore, if the above conditions are satisfied, the user must follow the procedure below to apply the patch.

  1. Secure the Altibase server downtime

  2. Shutdown the Altibase server (Refer to step 2 of the patch procedure)

  3. Change the service port
    Temporarily change the service port during patching to ensure that access to Altibase is blocked.

  4. Startup the Altibase server (Refer to step 3 of the patch procedure)

  5. Check the replication gap**
    Must make sure it is 0.

    How to check replication cap

  6. Backup the replicated object creation syntax by performing aexport

  7. Drop replication object**

  8. Perform the checkpoint

  9. Shutdown the Altibase server (Refer to step 2 of the patch procedure)

  10. Perform the patch (Refer to step 2 to step 7 of the patch procedure)

  11. Add CHECK_LOGFILE property**

  12. Startup the Altibase Server (Refer to step 8 of the patch procedure)

  13. Delete CHECK_LOGFILE property**

  14. Insert data after creating temporary table
    This is to use up the log files created in the previous version and create a new log file.

    CREATE TABLE IMSI_T (C1 INTEGER, C2 INTEGER);

CREATE OR REPLACE PROCEDURE IMSI_PROC AS V1 INTEGER;
BEGIN
FOR V1 IN 1 .. 300000 LOOP
INSERT INTO IMSI_T VALUES (V1, V1);
END LOOP;
END;
/

  15. Perform the checkpoint

  16. Create replication object

  17. Start replication

  18. Shutdown Altibase server (Refer to step 2 of the patch procedure)
    Change the temporarily changed service port to the original.

     

  19. Change the service port
    Change the temporarily changed service port to the original.

  20. Startup the Altibase server (Refer to step 8 of the patch procedure)

  21. Check the service

 

 

  • No labels