Installation Guide » Install on LINUX
This is the CUBRID Installation Guide for Linux User. If you have not downloaded CUBRID installation package for Linux, there are two versions available for users: one for Linux 32-bit, the other for Linux 64-bit. Please download the one suitable for your operating system.
The installation program consists of binary shells, therefore, can be installed automatically. In order to start the installation, transfer the CUBRID installation package file in binary mode to the Linux server via FTP (File Transfer Protocol).
Setup the program as shown in the following example:
- $ sh CUBRID-8.1.0.1162-linux.sh
Input the CUBRID install directory. [Default: /home/cubrid/CUBRID] :
Install CUBRID to /home/cubrid/CUBRID...
In case a different version of the CUBRID product is being used in other machines, please note that the CUBRID 2008 R1.0 servers are only compatible with the CUBRID 2008 R1.0 clients and vice versa.
Do you want to continue? (y/n) [Default: y] : y - At this point CUBRID should be successfully installed on your machine.
A demo database named demodb should also be successfully created. - If you want to start using CUBRID, run the following commands
% . /home/cubrid/.cubrid.sh
% cubrid service start
As shown in the example above, after installing the downloaded file (CUBRID-8.1.0.1162-linux.sh), the CUBRID related environment information must be set in order to use the CUBRID database. Such setting is applied automatically when logging in the terminal, therefore the following command is needed to be run once after the installation.
- $ . /home/cubrid/.cubrid.sh
Now, you can connect with CUBRID Manager to the CUBRID Manager Server. At any time if your server is stopped, you may start it with the following command:
- $ cubrid service start
In order to check whether the services are running after starting the CUBRID service, check that the cub_* processes have been started with a grep command (as shown below).
- $ ps -ef | grep cub_ cubrid 15200 1 0 18:57 ? 00:00:00 cub_master
cubrid 15205 1 0 18:57 pts/17 00:00:00 cub_broker
cubrid 15210 1 0 18:57 pts/17 00:00:00 query_editor_cub_cas_1
cubrid 15211 1 0 18:57 pts/17 00:00:00 query_editor_cub_cas_2
cubrid 15212 1 0 18:57 pts/17 00:00:00 query_editor_cub_cas_3
cubrid 15213 1 0 18:57 pts/17 00:00:00 query_editor_cub_cas_4
cubrid 15214 1 0 18:57 pts/17 00:00:00 query_editor_cub_cas_5
cubrid 15217 1 0 18:57 pts/17 00:00:00 cub_broker
cubrid 15222 1 0 18:57 pts/17 00:00:00 broker1_cub_cas_1
cubrid 15223 1 0 18:57 pts/17 00:00:00 broker1_cub_cas_2
cubrid 15224 1 0 18:57 pts/17 00:00:00 broker1_cub_cas_3
cubrid 15225 1 0 18:57 pts/17 00:00:00 broker1_cub_cas_4
cubrid 15226 1 0 18:57 pts/17 00:00:00 broker1_cub_cas_5
cubrid 15229 1 0 18:57 ? 00:00:00 cub_auto start
cubrid 15232 1 0 18:57 ? 00:00:00 cub_js start
Now you are done! Congratulations! If you come up with any kind of questions, post them at our CUBRID Forum. Our Developers Community will make sure your issue is addressed.
System Configuration
In order to change the system configuration, such as service ports to meet the user environment, change the parameter values of the following files in the directory $CUBRID/conf on UNIX/Linux platform.
Category | Description |
cm.conf | CUBRID Manager's configuration file. The default port number is set to 8001. |
cubrid.conf | Configuration file and is used to set the following: database memory, the number of threads due to the number of concurrent users, communication port between the Broker and Server, etc. |
cubrid_broker.conf | Broker configuration file and is used to set the following; the port used by the broker, the number of CAS, SQL LOGs, etc. The ports shown in drivers such as JDBCs are the concerned Broker's ports. |



