...
The following error description can be viewed with the AltiErr utility:
| Code Blockpanel |
|---|
$ altierr 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 message is written to altibase_boot.log when a client of a version incompatible with the server tried to establish a connection.
This error keeps a message history and has no does not adversely affect on the Altibase server.
Action
If this error persists, find the client that is attempting to connect and re-install , then reinstall it with a version compatible with the server.
Reference
If this error persists, find the client that is attempting to connect and reinstall it with a version compatible with the server.
- For ALTIBASE HDB 5.3.1 or below, the cm protocol version of the server and client must be identical for the client to connect to the server.
- For ALTIBASE HDB 5.3.3 or above, backward compatibility for the server and client is supported. The client can connect to a server of the same or newer version regardless of its cm protocol version whereas, connection fails if the client is of a newer version than the server.
- In this context, the first three numbers of a product version are denoted as the version (the fourth and succeeding numbers which indicate the patch versions are irrelevant).
# How to check the server/client version
- Server version
Code Blockpanel $
altibase
-v
version5.1.5.68
XEON_LINUX_redhat_Enterprise_AS4-64bit-5.1.5.68-release-GCC3.4.6
(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
- Client version
...
Panel 5.3.1
...
or below
...
...
$
...
sesc
...
-v
...
SES
...
C/C++
...
Precompiler
...
3
...
Ver
...
5.1.5.68
...
XEON_LINUX_redhat_Enterprise_AS4-64bit-5.1.5.68-release-GCC3.4.6
...
(xeon-redhat-linux-gnu)
...
Jan
...
5
...
2010
...
21:17:22
...
5.3.3
...
or above
...
...
$
...
apre
...
-v
...
Altibase
...
Precompiler2(APRE)
...
Ver.1
...
6.3.1.0.9
...
X86_64_LINUX_redhat_Enterprise_ES4-64bit-6.3.1.0.9-release-GCC3.4.6
...
(x86_64-unknown-linux-gnu)
...
Mar
...
20
...
2014
...
18:19:25
- Using the JDBC driver
Code Blockpanel $
java
-jar
$ALTIBASE_HOME/lib/Altibase.jar
JDBCDriver
Info
:
Altibase
Ver
=
6.3.1.0.9
for
JavaVM
v1.4,
CMP:7.1.1,
Mar
20
2014
17:07:25
- Using the ODBC library on Windows
Code Blockpanel Altibase
Installation
Directory
(e.g.,
C:\Program
Files
(x86)\Altibase\altibase-server-6.3.1)
->
lib
Directory
altiodbc.dll->
Properties
->
Details
->
Product
Version
Reference
1. For ALTIBASE HDB 5.3.1 and below, the cm protocol version of the server and client must be identical for the client to connect to the server.
2. For ALTIBASE HDB 5.3.3 and above, backward compatibility for the server and client is supported.
The client can connect to a server of the same or newer version regardless of its cm protocol version whereas, connection fails if the client is of a newer version than the server.
In this context, the first three numbers of a product version are denoted as the version (the fourth and succeeding numbers which indicate the patch versions are irrelevant).
# Examples of server and client compatibility for different versions
| Server Version | Client Version | Result | Remarks |
|---|---|---|---|---|
Server Version > Client Version | 6.3.1 | 5.3.3 | Succeeds | Backward compatibility is supported for 5.3.3 and or above. |
Server Version > Client Version | 6.3.1 | 4.3.9 | Fails | Backward compatibility is supported only if the version of both the server and client is 5.3.3 and or above. |
ServerVersion < Client Version | 6.1.1 | 6.3.1 | Fails | If the version of the client is newer than the server, connection fails regardless of the Altibase version. |