...
| Code Block |
|---|
| title | Example 1: When the CPU of the device and the ALTIBASe package do not match |
|---|
| theme | DJango |
|---|
| language | bash |
|---|
|
$ ./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
|
...
- In order to connect ALTIBASE in sysdba mode, the path where ALTIBASe is installed must be registered in a variable named "ALTIBASE_HOME'.
- If this variable is not registered, the following error occurs.
| Code Block |
|---|
| theme | EmacsDJango |
|---|
| language | bash |
|---|
|
$ isql -s 127.0.0.1 -u sys -p manager -port 20300 -sysdbaISQL_CONNECTION = UNIX, SERVER = 127.0.0.1, PORT_NO = 20300
[ERR-91003 : Environment (ALTIBASE_HOME) does not exists. |
...
- When installing and creating a database, it must be connected in the sysdba.
- At this time access to sysdba mode is possible only with the user who installed ALTIBASE.
| Code Block |
|---|
|
$ 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.] |
...
- This problem occurs when there is no altibase.properfies file in the 'conf' directory under the ALTIBASE installation path.
| Code Block |
|---|
|
iSQL(sysdba)> startup process
idp readConf() Error : Open File [/hdb_home/651/conf/altibase.properties] Error. |
...
- This problem occurs when proceeding without creating a license file in the 'conf' directory under the ALTIBASE installation path.
| Code Block |
|---|
|
TRANSITION TO PHASE : PROCESSCommencing Server as Community Edition
DISK_MAX_DB_SIZE(Unlimited) exceeded limit 8192M
[FAILURE] License invalid or expired.
Startup Failed....
[ERR-91015 : Communication failure.] |
...
- MAC ADDRESS may be changed for reasons such as changing the network card of the device. Or, the wrong license may been issued because the license issuance information was incorrectly sent to ALTIBASE.
| Code Block |
|---|
| theme | EmacsDJango |
|---|
| language | bash |
|---|
|
TRANSITION TO PHASE : PROCESSInvalid or expired license in License File(/hdb_home/651/conf/license)
[FAILURE] License invalid or expired.
Startup Failed....
[ERR-91015 : Communication failure.] |
...
This problem occurs when the issued license has expired.
| Code Block |
|---|
|
TRANSITION TO PHASE : PROCESSInvalid or expired license in License File(/hdb_home/651/conf/license)
[FAILURE] License invalid or expired.
Startup Failed....
[ERR-91015 : Communication failure.] |
...
| Code Block |
|---|
| title | When the currently set value is out of range |
|---|
| theme | DJango |
|---|
| language | bash |
|---|
|
idp checkRange() Error : Property [property_name] [current_value] Overflowed the Value Range.(min_value~max_value) |
| Code Block |
|---|
| title | If the currently set value is impossible to convert the data type |
|---|
| theme | DJango |
|---|
| language | bash |
|---|
|
idp convertFromString() Error : The property [property_name] value [current_value] is not convertable. |
| Code Block |
|---|
| title | When the same property is duplicated |
|---|
| theme | DJango |
|---|
| language | bash |
|---|
|
idp insertBySrc() Error : Property [property_name] Can't Store Multiple Values. |
...
- Writing file error can be caused by a number of problem factors
- The disk may not have enough free space, or the directory may have omitted privileges.
| Code Block |
|---|
|
TRANSITION TO PHASE : PROCESSCommand 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]] |
...
- In order to start Altibase in service mode, the database creation procedure must be preceded.
- This problem occurs when the user omits this procedure and starts the server in a shell prompt, starts in iSQL, or starts ALTIBASE as a service in the WINDOWS environment.
- Usually, when ALTIBASE starts up, the loganchor file is retrieved for the first time, so an error message indicating that the file does not exist is returned.
| Code Block |
|---|
|
TRANSITION TO PHASE : CONTROL[FAILURE] The log anchor file does not exist or it is not valid.
Startup Failed....
[ERR-91015 : Communication failure.] |
...
- This problem occurs when the ALTIBASE process fails to bind the TCP port to be used.
| Code Block |
|---|
|
TRANSITION TO PHASE : SERVICE [CM] Listener failed : TCP on port 20300 [IPV4]
[FAILURE] Unable to bind the socket.
Startup Failed....
[ERR-91015 : Communication failure.] |
...
- This problem occurs when the ALTIBASE replication thread fails in the step of binding the port to be used.
| Code Block |
|---|
|
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.] |
...