Skip to content

Troubleshooting Altibase Installation Problems#

Overview#

This document lists, by type, the problems that may occur when installing and starting Altibase, and describes how to resolve each of them.
This document applies to Altibase 6.5 or later.

Problems not covered in this document may occur, and the types of problems may differ depending on the Altibase version.
For problems not covered in this document, send a description of the situation along with the trace log files (the $ALTIBASE_HOME/trc directory) to support@altibase.com.

Info

For errors and improvements related to this document, please contact the technical support portal or technical support center.

Info

This document is provided for informational purposes only and is subject to change without prior notice. It may contain errors, and Altibase makes no express or implied warranties of any kind, including but not limited to warranties of merchantability or fitness for a particular purpose.

The development, release, and timing of any features or functionality described for Altibase products in this document are at the sole discretion of Altibase.

Altibase may hold patents, trademarks, copyrights, or other intellectual property rights related to the contents of this document.

Troubleshooting by Problem Type#

Package Cannot Be Executed (Binary Format Mismatch)#

Altibase packages are compiled and distributed for each CPU architecture. If you run a package that does not match the CPU of the target server, the following error occurs.
The message below is the most common one; depending on the environment, other messages such as library compatibility errors may be returned.

$ ./altibase-HDB-server-6.5.1.6.8-LINUX-POWERPC-64bit-release.run 
-bash: ./altibase-HDB-server-6.5.1.6.8-LINUX-POWERPC-64bit-release.run: cannot execute binary file

You can quickly check whether the installed executable works properly with the altibase -v command.

Solution

Download and install the package that matches the CPU architecture and OS of the server.

Environment Variable Not Set#

To connect to or start the Altibase server, the Altibase installation path must be set in the ALTIBASE_HOME environment variable. If this variable is not set, the following error occurs.

$ isql -s 127.0.0.1 -u sys -p manager -port 20300 -sysdba
ISQL_CONNECTION = UNIX, SERVER = 127.0.0.1, PORT_NO = 20300
[ERR-91003 : Environment  (ALTIBASE_HOME) does not exists.

Solution

Set the Altibase installation path in the ALTIBASE_HOME environment variable. If you apply the $ALTIBASE_HOME/conf/altibase_user.env file created during installation in the user profile, PATH, LD_LIBRARY_PATH, and other variables are set as well.

sysdba Connection Privilege Error#

Administrative tasks such as creating, starting, and stopping the database are performed by connecting in sysdba mode, and only the OS user who installed Altibase can connect in sysdba mode. If you connect as a different OS user, the following error occurs.

$ isql -s 127.0.0.1 -u sys -p manager -port 26084 -sysdba
-----------------------------------------------------------------
     Altibase Client Query utility.
     Release Version 6.5.1.6.8
     Copyright 2000, ALTIBASE Corporation or its subsidiaries.
     All Rights Reserved.
-----------------------------------------------------------------
WARNING: A port number is not required when connecting via IPC or UNIX, so the -port option was ignored.
ISQL_CONNECTION = UNIX, SERVER = 127.0.0.1
[ERR-9100B : Privilege error for sysdba user account.]

Solution

Connect again as the OS user who installed Altibase. If you need to operate Altibase as the current user, change the owner of all files under the Altibase installation path to the current user.

altibase.properties File Missing#

If there is no altibase.properties file in the $ALTIBASE_HOME/conf directory, the following error occurs.

iSQL(sysdba)> STARTUP PROCESS
idp readConf() Error : Open File [/hdb_home/651/conf/altibase.properties] Error.

Solution

Copy the altibase.properties.sample file provided in the $ALTIBASE_HOME/conf directory to altibase.properties, and then modify it to suit your environment.

$ cp $ALTIBASE_HOME/conf/altibase.properties.sample $ALTIBASE_HOME/conf/altibase.properties

License File Missing#

If there is no license file in the $ALTIBASE_HOME/conf directory, the following error occurs.

TRANSITION TO PHASE : PROCESS
Commencing Server as Community Edition
DISK_MAX_DB_SIZE(Unlimited) exceeded limit 8192M
[FAILURE] License invalid or expired.
Startup Failed....
[ERR-91015 : Communication failure.]

Solution

Create the $ALTIBASE_HOME/conf/license file with the license key issued by Altibase.

Invalid License#

A license is generated based on the server information (hostid or MAC address) provided when it was issued. If the MAC address of the server has changed, for example because the network card was replaced, or if incorrect information was provided when the license was issued, the following error occurs.

TRANSITION TO PHASE : PROCESS
Invalid or expired license in License File(/hdb_home/651/conf/license)
[FAILURE] License invalid or expired.
Startup Failed....
[ERR-91015 : Communication failure.]

Solution

Check whether the hostid or MAC address used when the license was issued matches the current information of the server. If it does not match, have the license reissued.

License Expired#

If the validity period of the issued license has expired, the following error occurs. The error message is the same as for an invalid license, so check both the license information and the validity period.

TRANSITION TO PHASE : PROCESS
Invalid or expired license in License File(/hdb_home/651/conf/license)
[FAILURE] License invalid or expired.
Startup Failed....
[ERR-91015 : Communication failure.]

Solution

Request a new license from the Technical Support Portal, and apply it once it is issued.

Invalid Property Value#

If a property value specified in the altibase.properties file or through an environment variable is invalid, an error occurs. Typical error messages are as follows.

The value is out of the allowed range

idp checkRange() Error : Property [property_name] [current_value] Overflowed the Value Range.(min_value~max_value)

The value cannot be converted to the property's data type

idp convertFromString() Error : The property [property_name] value [current_value] is not convertable.

The same property is set more than once

idp insertBySrc() Error : Property [property_name] Can't Store Multiple Values.

Solution

Check the property shown in the error message and correct it to a valid value.

File Write Error#

If a database file cannot be created or written, the following error occurs. It can be caused by various factors, such as insufficient free disk space or directory permission problems.

TRANSITION TO PHASE : PROCESS
Command execute success.

DB Info (Page Size     = 32768)
        (Page Count    = 257)
        (Total DB Size = 8421376)
        (DB File Size  = 1073741824)

FAILURE of createdb.

[ERR-0103C : Unable to invoke create() function on [/ALTIBASE/altibase_home/dbs/dwfile0.dwf]]

Solution

Check the free disk space and the directory permissions for the path shown in the error message.

Database Not Created#

To start Altibase up to the service phase, the database must be created first. If you start Altibase with the server start command, the iSQL STARTUP command, or as a Windows service without creating the database, an error occurs.
Altibase reads the log anchor file first when it starts. If the database has not been created, this file does not exist, so the following error is returned.

TRANSITION TO PHASE : CONTROL
[FAILURE] The log anchor file does not exist or it is not valid.

Startup Failed....

[ERR-91015 : Communication failure.]

Solution

Create the database and start Altibase again. For details, refer to Creating an Altibase Database.

Port (PORT_NO) Bind Failure#

If Altibase fails to bind the port used for communication between clients and the server over TCP/IP (PORT_NO), the following error occurs.

TRANSITION TO PHASE : SERVICE
  [CM] Listener failed  : TCP on port 20300 [IPV4]
[FAILURE] Unable to bind the socket.
Startup Failed....
[ERR-91015 : Communication failure.]

Solution

Use netstat or a similar tool to check whether another process is using the port. If another application is using it, change that application's port or change PORT_NO in the altibase.properties file to a different value.

Replication Port Bind Failure#

If Altibase fails to bind the replication port of the local server used for replication connections (REPLICATION_PORT_NO), the following error occurs.

TRANSITION TO PHASE : SERVICE
  [CM] Listener started : TCP on port 20300 [IPV4]
  [CM] Listener started : UNIX
  [CM] Listener started : IPC
  [RP] Initialization : FAIL
[FAILURE] [Receiver] Failed to listen to a replication socket (Port No:30300)
Startup Failed....
[ERR-91015 : Communication failure.]

Solution

Use netstat or a similar tool to check whether another process is using the port. If another application is using it, change that application's port or change REPLICATION_PORT_NO in the altibase.properties file to a different value.