- Altibase package installation and DB creation procedure
- Notes/Considerations on installation related to Altibase package
- Description of Altibase Database Creation
- Starting Altibase
- Shutting Altibase Down
- Explanation of Starting and Shutting Down Altibase
- Use-Cases of Altibase
This document describes how to install and start/stop Altibase.
The content to be referred after the basic installation is provided as a separate document and URL, so please refer to it.
- The OS user account for installing the server(system) clone Altibase package must be created.
- Download the Altibase package installer from support.altibase.com/en/ and upload the file to the system.
- For Altibase version information, OS type, OS Big information, and Mac address information, please receive a temporary license at support.altibase.com/en/ or contact Altibase Sales Department to confirm the agreement and issue a formal license.
Access the Altibase package installer file from the URL described below, sign up for the membership, log in, and download the package.
Users can download the package from http://support.altibase.com/en/ or from Altibase.
Since the OS information, compile bit, and product version information are described in the package, request or download an appropriate product package.
Example of Altibase package file name (Example of package file description of 6.5.1.XX, 7.1.0.XX based on Altibase package file for Linux)
Altibase package installation and DB creation procedure
This section describes how to create DB of versions supported according to Altibase's End of Service (EOS) policy.
As of this document , the latest Altibase version is 'Altibase ver. 7' and'Altibase ver. earlier than 6' are for EOS.
Since Altibase cannot be operated until the DB is created, the DB must be created as follows before starting.
How to download and install Altibase Package
Grant the execution permission to the Altibase package file.
Execute the Altibase package and set the absolute path to install the Altinbase engine in the installation directory.
Decide how to create DB. (Default = 1)
* Full package installation and patch selection option. Altibase package default installation selects Full option.
The user can check the kernel configuration guide. (The user can also check through pre_install.sh in the install directory under the installation path.)
Determine the DB name. (Default = mydb)
* When changing the DB name, it is necessary to reconfigure the DB.
Set the DB PORT. (Default = 20300)
Determine the MEM_MAX_DB_SIZE value. (Default = 2G)
* MEM_MAX_DB_SIZE refers to the 'maximum value' of data to be stored in memory, and refers to the limit value, not-pre-allocated.
Determine the total memory size of the buffer pool. (Default = 128M)
BUFFER_AREA_SIZE refers to the'maximum value' of the memory size to be used as a buffer area in relation to the disk table, and refers to the total value allocated in advance.
Decide whether to create DB. (Default = YES)
Determine the initial database size of the DB. (Default = 10M)
Determine the DB archive/no archive settings. (Default = No archivelog)
Determine the DB character set setting. (Default = UTF8)
Determine the DB's National Character Set setting (Default = UTF8)
Set the DB data file (disk tablespace data file, memory tablespace checkpoint image file), archive log file, log file, and log anchor file path.
* The path can be set to the path to be set, and the default value is set to the dbs, arch_logs, logs path of the directory where the Altibase engine is installed.
Show the property value to which the DB default setting is applied.
Install the package to proceed with DB creation.
Enter the issued license after completing the package installation to create the DB. (Default = 1)
Proceed to create DB. (Data file, checkpoint image file, log file, log anchor file required for DB configuration based on the above property setting value)
When the DB creation is completed, the configuration value is applied to the altibase.properties file in the directory called conf in the Altibase engine path. ($ALTIBASE_HOME/conf/altibase.properties)
When the DB creation is completed normally, data files, checkpoint image files, log anchor files, and log files should be created in the dbs and logs directories as follows.
When the DB creation is completed normally, $ALTIBASE_HOME and PATH are automatically set in the environment variable for the OS user account that installed the Altibase package.
Altibase directory components
When the Altibase package is installed, the following directory is created.
This section is about basic installation and operation, and describes only the main directories that the user will check after installation. (Refer to the manual for details.)
|Example SQL and View creation file directory for easy viewing of Altibase performance view|
Altibase execution file, utility (execution file) directory
Header file directory provided for Altibase application development
altibase_env.mk file and README file directory containing examples of macro settings for makefiles for Altibase application development.
|Library directory provided for Altibase application development|
|Example program source (CLI, APRE, JDBC, C/C++, etc.) directory that provided Altibase application as a sample|
|Trace log file location where Altibase operation status information is recorded|
Location of the Altibase configuration files (altibase.properties, aexport.properties), the property example file (sample), and the license file location directory
Altibase log anchor file and default path where log files are created
Default path where Altibase data files are created
|arch_logs||Backup directory to back up log files for Altibase recovery|
|altiComp||Utility directory that resolves data inconsistency caused by failures during replication operation between Altibase databases|
|msg||Directory containing files containing Altibase error messages|
Notes/Considerations on installation related to Altibase package
- Altibase does not officially offer a 32-bit package.
However, Altibase provides package products for the development and integration of client products (client-server).
The client product starts with the name "altibase-HDB-client-6.5.1.x.x" before the package name.
Since the product package includes compiler information, when using gcc/g++ as an example, check the version of the compiler in advance.
- For information on whether to use the Altibase client package and the available versions, additional information can be provided from technical inquiries at 02-2082-1114 or support.altibase.com.
Description of Altibase Database Creation
The following document describes how to create the Altibase database in detail.
The normal startup is possible only when the basic installation and DB creation of the Altibase package are completed as above.
This section explains how the user can start the DB.
- When the installation and DB creation of the Altibase package is completed, execute the environment variable file in the installed OS user account to start.
- Since the environment variable file is different for each OS type, check if $ALTIBASE_HOME and PAHT are properly configured in the environment variable for the corresponding version.
- For Linux, for example, execute the environment file after checking whether $ALTIBASE_HOME and PATH are properly set in the environment variable file. (Run $.$HOME/.bash_profile or source $HOME/.bash_profile)
In addition to the above method, Altibase can be started by connecting to iSQL and executing the "startup service" command.
Example of failure to start Altibase
Shutting Altibase Down
If the Altibase installation is completed and started normally, this section describes how to shut down the DB by the user.
Altibase Shutdown Procedure
Altibase can be stopped by executing the "server stop" command in the prompt window of the OS account. (This is provided to execute commands with a shell script called "server" so that users can easily terminate them.)
In addition to the above method, Altibase can be stopped by connecting to iSQL and executing the "shutdown immediate" command. (When executing the shutdown command, options can be shut down with abort, immediate, or normal.
* When the above shutdown is in progress, it can be shutdown(stopped) in three ways. please refer to the description below.
Option Description abort All the connected sessions (clients) are forcibly terminated and immediately stop running. Since Altibase is stopped, it is immediately shut down without a normal shutdown process. (After running, data recovery is performed and there is no problem.) immediate All the connected sessions (clients) are forcibly terminated and stopped with a normal shutdown process. normal After waiting for all the connected sessions (clients) to be terminated normally, it is stopped through a normal shutdown process.
If the "normal" option is used, it has to wait for the session (client) to terminate. If the Altibase is stopped without knowing this reason, it may be taken as a. mistake as if the shutdown process is not in progress.
Explanation of Starting and Shutting Down Altibase
- Details on starting and stopping Altibase are described in detail in the URL below.
- Understanding the Altibase Star/Shut down Process
Use-Cases of Altibase
- This chapter describes how to create a DB user, create a tablespace, and create a table simply as an example.
- Altibase complies with the SQL92 standard, so there is no significant difference in statements from other DBMSs.
- For more detailed information on SQL statements, refer to the manual provided by Altibase. (Go to Altibase.com or github.com/ALTIBASe to access and download the manual)
Altibase provides a utility program for users to use SQL statements in terminals and applications.
* When the DB is created, only the user with DBA authority called "SYS" exists, so only $ALTIBASE_HOME/bin/is can be executed and accessed. ("ls" is provided as a shell script made for easy access and use of iSQL.)
Each input option is as follows.
Input option Description -u Enter the DB user's account name. -p Enter the DB user's password. -s Enter the network IP address of the server where the target DB to be accessed is located, or 127.0.0.1 for the local server. -port Enter the PORT_NO set in the target DB to be connected. (PORT_NO can be checked in the $ALTIBASE_HOME/conf/altibase.properties file)
If the DB character set is not set to US7ASCII, the character set specified when creating the DB must be set as an environment variable.
* When the DB was created, if the character set is set to MS949 as an example, the session (client) that connects to the input and output of Korean data should also be set and applied to the character set of ALTIBASE_NLS_USE with MS949.
Creating and Deleting DB user account
In Altibase, a user with DBA authority called "SYS" account is created. New user accounts can be created by logging in with this account.
* In this part, commands for creating and deleting new users are explained as follows.
Each input part used is as follows.
Input Description After CREATE USER Describe the name of a new user to be used in Altibase. After IDENTIFIED BY Describe to designate the user's password (password). After DEFAULT TABLESPACE Users can create it without describing it from this part. However, it is a clause that specifies the accessible tablespace and can be changed through the “ALTER USER” statement. ACCESS ~ ON Authorize access to the tablespace described between ACCESS and ON.
Creating and Deleting Tablespace account
Altibase HDB (Hybrid DBMS) can use both memory tablespaces and disk tablespaces.
* In this part commands for creating and deleting user memory tablespaces and user disk tablespaces are explained as follows.
Creating and Deleting Tables
Altibase HDB (Hybrid DBMS) can use both memory tablespaces and disk tablespaces, so memory tables and disk tables can be created as well.
* In this part, commands that create and delete memory tables and disk tables are explained as follows.