Problem Occurred during Installation and Measures

Overview


This document introduces common installation errors and corresponding solutions. This document does not cover all possible errors, and the errors themselves may differ depending on the version of Altibase. For any issues not covered by this document, please contact customer support at support@altibase.com with a description of the error and any associated trace log files.

Common Errors and Solutions


This chapter outlines some of the most common errors encountered during the installation of Altibase. Suggested solutions are also provided.

Altibase Package and Server CPU Incompatibility

Installation errors will occur if the Altibase package is not compatible with the server’s CPU.

The altibase -v command can be used to confirm whether or not a compatible version has been installed. Other messages may be thrown in cases of similar errors such as library incompatibility. The following errors are the most common errors thrown by any incompatibility:

Example 1: Incompatibility between Altibase and the server CPU.

$ altibase –v

sh: altibase: cannot execute

Example 2: Example of incompatibility when attempting to install using an AIX 5.3 package on an AIX 5.2 server.

$ altibase -v

Could not load program altibase:

Symbol resolution failed for altibase because:

Symbol __fd_select (number 110) is not exported from dependent

module /usr/lib/libc.a[shr_64.o].

Symbol __pth_init (number 227) is not exported from dependent

module /usr/lib/libpthreads.a[shr_xpg5_64.o].

Examine .loader section symbols with the ‘dump -Tv’ command.

Solution: Reinstall Altibase with a package compatible with the server’s CPU.

Unregistered Environment Variable

To connect to Altibase in SYSDBA mode, Altibase’s installation path must be registered in the ‘ALTIBASE_HOME’ environment variable. If the ALTIBASE_HOME environment variable is not set, the error below will be displayed:

$ 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_HOME environment variable to Altibase’s installation path.

User File Permission Error

Users will encounter an error if they attempt to connect in SYSDBA mode while using a user account that does not own the Altibase installation directory.

$ isql -s 127.0.0.1 -u sys -p manager -sysdba -port 20300

—————————————————————–

Altibase Client Query utility.

Release Version 6.3.1.0

Copyright 2000, ALTIBASE Corporation or its subsidiaries.

All Rights Reserved.

—————————————————————–

ISQL_CONNECTION = UNIX, SERVER = 127.0.0.1, PORT_NO = 20300

[ERR-9100B : Privilege Error on user account for sysdba.]

Solution: To connect in SYSDBA mode, re-execute the command using the user who is the owner of Altibase’s installation path. Alternatively, the owner can be changed to the desired user.

altibase.properties File Error

The following error may occur if the altibase.properties file does not exist in the $ALTIBASE_HOME/conf directory.

iSQL(sysdba)> startup process

Connecting to the DB server………………………….Startup Failure. Check Your Environment.

The trace file (altibase_boot.log) located in the $ALTIBASE_HOME/trc directory can be reviewed to obtain more information. In the example below, the trace file explicitly identifies the absence of the altibase.properties file as the cause of the error.

[[[[[[ ALTIBASE STARTUP – Boot ]]]]]]

[2015/03/15 20:24:13] [Thread-1] [Level-0]

==> Check & Loading of Altibase Properties.

[2015/03/15 20:24:13] [Thread-1] [Level-0]

ERR-0109a(errno=2) idpreadConf() Error : Open File [/ALTIBASE/altibase_home/conf/altibase.properties] Error.

[2015/03/15 20:24:13] [Thread-1] [Level-0]

[FAILURE] idpreadConf() Error : Open File [/ALTIBASE/altibase_home/conf/altibase.properties] Error.

[2015/03/15 20:24:13] [Thread-1] [Level-0]

ERR-0109a(errno=2) idpreadConf() Error : Open File [/ALTIBASE/altibase_home/conf/altibase.properties] Error.

Solution: A sample properties file named ‘altibase.properties.sample’ is located in the $ALTIBASE_HOME/conf directory. The user can adjust the properties within this file to the desired values and then rename the file to ‘altibase.properties’ to rectify this error.

Missing License Key

An error will occur if a valid license key file does not exist. The following error message will be displayed:

TRANSITION TO PHASE : PROCESS

License File(/ALTIBASE/altibase_home/conf/license) does not exist

HostID->00000000

[FAILURE] License File does not exist.

Startup Failed….

[ERR-91015 : Communication failure.]

Solution: Obtain a valid license key and place the file in the $ALTIBASE_HOME/conf directory.

License Key Value Error

As of Altibase version 6.3, the license issuance method has been changed. License keys are now issued based on MAC addresses and not host IDs. This error may occur if an Altibase representative did not generate an appropriate license key based upon the client’s product version. The client should also verify that the host ID or MAC address provided to the Altibase representative was accurate.

  • For versions equal to or greater than Altibase 6.3.1
    License is issued based on Mac Address.
  • For versions prior to Altibase 6.3.1
    License is issued based on host ID.

Any changes to the device network card may cause the host id to change.

.TRANSITION TO PHASE : PROCESS

invlid MEM_MAX_DB_SIZE, Availible DB Size is 0

key : [current_license_key_value]

Invalid or expired license in License File(/ALTIBASE/altibase_home/conf/license)

HostID->00000000

[FAILURE] License is invalid or expired.

Startup Failed….

[ERR-91015 : Communication failure.]

Solution: Verify that MAC address or host ID information sent to Altibase was accurate. Request a valid license key from an Altibase representative.

License Key Expiration

The following error will be thrown if a user attempts to start Altibase with an expired license

TRANSITION TO PHASE : PROCESS

invalid MEM_MAX_DB_SIZE, Available DB Size is 0

key :

To be expired at XXXX-XX-XX.

Invalid or expired license in License File(/ALTIBASE/altibase_home/conf/license)

HostID->00000000

[FAILURE] License is invalid or expired.

Startup Failed….

[ERR-91015 : Communication failure.]

Solution: Request a new license key from an Altibase representative and place it in the license file.

Invalid Property Errors

Invalid property errors may occur if properties located in the altibase.properties file are set to invalid values. The altibase_boot.log trace file can be reviewed to identify the specific property that is causing the error.

Example 1: A property is set to a value out of range.

ERR-0109a(errno=0) idpcheckRange() Error : Property [property_name] [current_value] Overflowed the Value Range.

Example 2: A property is set to a value that cannot be converted to the appropriate data type.

ERR-0109a(errno=0) idpconvertFromString() Error : The property [property_name] value [current_value] is not convertable.

Solution: Identify the invalid property value and set it to an appropriate value.

Property Value Error 2

If isql tool has valued which cannot be analyzed, the same problem occurs as the case of “altibase.properties file error”. This case also confirms the wrong contents in altibase_boot.log trace file.

iSQL(sysdba)> startup process

Connecting to the DB server………………………….Startup Failure. Check Your Environment.

altibase_boot.log contents

ERR-0109a(errno=0) idpcheckRange() Error : Property [property_name] [current_value] Overflowed the Value Range.

ERR-0109a(errno=0) idpconvertFromString() Error : The property [property_name] value [current_value] is not convertable.

Solution: Correct the invalid property after identifying the cause of the error through the altibase_boot.log trace file.

Property Value Error 3

The cause of this error is identical to the error outlined above. If a server script is used, the error cannot be identified intuitively. Generally, a port number is not supplied when a server script is executed. In the example below, a port number is a required input value. The appropriate value is read from the altibase.properties file. However, if the value set in the altibase.properties file is invalid, the following error will occur:

$ server create US7ASCII UTF8

—————————————————————–

Altibase Client Query utility.

Release Version 6.3.1.0

Copyright 2000, ALTIBASE Corporation or its subsidiaries.

All Rights Reserved.

—————————————————————–

Write PortNo (default:20300) : ISQL_CONNECTION = UNIX, SERVER = 127.0.0.1, PORT_NO = 0

[ERR-910FB : Connected to idle instance]

$ is

—————————————————————–

Altibase Client Query utility.

Release Version 6.3.1.0

Copyright 2000, ALTIBASE Corporation or its subsidiaries.

All Rights Reserved.

—————————————————————–

Write PortNo (default:20300) :

ISQL_CONNECTION = TCP, SERVER = 127.0.0.1, PORT_NO = 20300

[ERR-50032 : Client unable to establish connection.]

Solution: Correct the invalid property after identifying the cause of the error through the altibase_boot.log trace file.

File Write Errors

File write errors can occur for various reasons. Common reasons include insufficient disk space or insufficient privileges

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: Verify that sufficient disk space and file permissions exist.

Database Does Not Exist

An Altibase database must be created prior to starting the database. If the user attempts to start Altibase prior to creating a database, the following error will be thrown:

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 a database prior to attempting to start Altibase.

Listener Port Binding Failure

This error occurs if Altibase does not successfully bind the TCP port for the Altibase process.

TRANSITION TO PHASE : SERVICE

[CM] Listener failed  : TCP on port 20300

[FAILURE] Unable to bind the socket.

Startup Failed….

[ERR-91015 : Communication failure.]

Solution: Identify the cause of the binding error. A common cause for this error is the usage of the same port by a different application. Alternatively, Altibase’s port can be changed to a different value.

Replication Port Binding Failure

This error occurs if Altibase does not successfully bind the TCP port for Altibase’s replication thread.

TRANSITION TO PHASE : SERVICE

[CM] Listener started : TCP on port 20300

[CM] Listener started : UNIX

[RP] Initialization : FAIL

[FAILURE] [Receiver] Failed to listen to a replication socket (Port No:30300)

Startup Failed….

[ERR-91015 : Communication failure.]

Solution: Identify the cause of the binding error. A common cause for this error is the usage of the same port by a different application. Alternatively, Altibase’s replication port can be changed to a different value.

Common Errors and Solutions for Windows Environments


This chapter outlines some of the most common errors encountered during the installation of Altibase.  Suggested solutions are also provided. This chapter is specific to Windows environments.

License Key Value Error

If multiple network cards are installed, Altibase may change the MAC address to confirm the license key value in accordance with the OS setting. This problem may occur during both operation and installation.

TRANSITION TO PHASE : PROCESS

invalid MEM_MAX_DB_SIZE, available DB Size is 0

key : [current_license_key_value]

Invalid or expired license in License File(C:\altibase_home\conf\license)

mac->000000000000

[ERR-91015 : Communication failure.]

Solution: Issue a license for the MAC address specified in the error message. Additionally, if the network card is disabled by Windows, it may recognize the MAC address as ‘000000000000.’ In this case, a license key for both the network card’s MAC address and ‘000000000000’ can be applied.

Copyright ⓒ 2000~2016 Altibase Corporation. All Rights Reserved.

These documents are for informational purposes only. These information contained herein is not warranted to be error-free and is subject to change without notice. Decisions pertaining to Altibase`s product characteristics, features and development roadmap are at the sole discretion of Altibase. Altibase may own related patents, trademarks, copyright or other intellectual property rights of products and/or features discussed in this document.