Skip to end of metadata
Go to start of metadata



All the versions of Altibase



The following error message is recorded in the Altibase trace log altibase_boot.log below and in $ALTIBASE_HOME/trc/altibase_boot.log.



The description of the error can be checked using the altierr utility as follows.

$ altierr 0x7101D
0x7101D ( 462877) cmERR_ABORT_PROTOCOL_HEADER_ERROR Protocol header error.(<0%s>)
# *Cause: Protocol header error
# *Action: Please send a bug report to the vendor.

This error is a message recorded in the server's altibase_boot.log when an incompatible version of the Altibase server attempts to connect to the server.

This message leaves history and does not affect the operation of the Altibase server.



If this error message continues to be logged, find the client trying to connect and reinstall the client with a version compatible with the server.



  • In the versions below Altibase version 5.3.3, the server and the client must have the same cm protocol version to connect from the client to the server.

  • From version 5.3.3 or higher of Altibase, backward compatibility between the server and the client is guaranteed, so that regardless of the cm protocol version, the client can connect to the server of the same version or higher version.

  • However, in the opposite case, that is, if the version of the client is higher than that of the server, the connection is not made.

  • The version referred to here means the first 3 digits of the product version. (The patch version of the 4th digit or less does not matter when checking the version.)

# Connection example according to server and client version


Server version

Client version

Connection result


Server Version> Client Version
(Version 5.3.3 or later)




Backward compatibility guaranteed in version 5.3.3 or later

Server Version> Client Version
(Versions earlier than 5.3.3)




Backward compatibility guaranteed when both server and client are version 5.3.3 or later.
Since the client is earlier than 5.3.3, backward compatibility is not guaranteed, and in the case of 4.3.9, the connection is only possible if the cm protocol version is the same.

Server version <client version




If the client version is high, the connection fails regardless of the Altibase version.
The client version must be the same as or earlier than the server version.


# How to check server and client version

  • How to check the server version

    $ altibase -v
    version XEON_LINUX_redhat_Enterprise_AS4-64bit- (xeon-redhat-linux-gnu) Jan 5 2010 21:17:22, binary db version 5.1.2, meta version 5.3.3, cm protocol version 5.4.5, replication protocol version 5.2.1
  • How to check the client version

    # 5.3.3 or earlier
    $ sesc -v
    SES C/C++ Precompiler 3 Ver XEON_LINUX_redhat_Enterprise_AS4-64bit- (xeon-redhat-linux-gnu) Jan 5 2010 21:17:22
    # 5.3.3 or later
    $ apre -v
    Altibase Precompiler2(APRE) Ver.1 X86_64_LINUX_redhat_Enterprise_ES4-64bit- (x86_64-unknown-linux-gnu) Mar 20 2014 18:19:25

  • How to check the version using JDBC Driver

    $ java -jar $ALTIBASE_HOME/lib/Altibase.jar
    JDBC Driver Info : Altibase Ver = for JavaVM v1.4, CMP:7.1.1, Mar 20 2014 17:07:25

  • How to check version using ODBC library in WINDOWS environment

    In the lib directory under the Altibase installation directory (e.g. C:\Program Files (x86)\Altibase\altibase-server-6.3.1)
    altiodbc.dll -> Properties -> Details -> Product version

  • No labels