Wiki Tutorials

cannot restore segment prot after reloc: Permission denied

2013-06-06T00:49:01-07:00

By default, CentOS 5 has the SE Linux feature set to enforcing. So, sometimes when you install CUBRID on CentOS and try to start the cubrid services using cubrid service start, you may encounter the following error:

[cubrid@localhost ~]$ cubrid service start
cubrid: error while loading shared libraries: /opt/cubrid/lib/libcubridsa.so.8: cannot restore segment prot after reloc: Permission denied

To temporarily disable enforcement on a running system, type

/usr/sbin/setenforce 0

To permanently disable enforcement during a system startup
change "enforcing" to "disabled" in ''/etc/selinux/config'' and reboot.

If this did not solve your problem, please check out the Permission Denied Error page for details on how to troubleshoot the problem:

http://www.cubrid.org/wiki_tutorials/entry/permission-denied-error

How to ... using CUBRID Tutorials

2012-10-29T01:17:39-07:00

Configuring CUBRID

[CUBRID Installation Instructions]
[Connecting to a remote CUBRID Database]
[How to Build CUBRID from Source on Fedora/Centos]
[How to Build CUBRID from Source on Ubuntu]
[How to Create a CUBRID Database]
[How to Start or Autostart a CUBRID Database]
[How to Start / Stop / Restart CUBRID Service]
[Getting started with demodb (CUBRID Demo Database)]
[How to Upgrade CUBRID Safely on Ubuntu]

CUBRID Specific Features

[CUBRID Database File Types and Their Meaning]
[CUBRID DATETIME Data Type]
[CUBRID iptables Firewall Configuration]
[CUBRID Log Files]
[How to Drop Some / All Tables]
[How to Enable/Disable AutoCommit Mode]
[How to Get Primary Keys]
[How to Get Foreign Keys]
[How to Insert Data into Tables with AUTO_INCREMENT Column(s)]
[How to Quote Reserved Keywords]
[How to Reduce Disk Space Occupied by CUBRID]
[How to Show Create Table Statement]

Error Handling

[Common Microsoft Errors]
[DLL Load Failed]
[Dropping Primary Key Error]
[Permission Denied Error]
[Unable to Resolve Host]
[Unique Constraint Violation Error]
[Update / Delete Operations Restriction Error]
[cannot restore segment prot after reloc: Permission denied]

Export/Import Database/Tables

[Copy / Clone Database]
[Exporting / Unloading a Database Using CUBRID Manager]
[How to Run a SQL Script / File]
[Importing / Loading a Database Using CUBRID Manager]
[Migrating Tables Using CUBRID Manager]

Troubleshooting Drivers

[How to Get PHP Version]

How to Create a CUBRID Database

2012-02-20T23:38:54-08:00

In this tutorial you will learn how to quickly create a database in CUBRID. If you use a Desktop version of the OS and prefer using GUI tools instead of a terminal, you may perform all of the commands below in CUBRID Manager.

To start with let's create a sample database. Type the following command in the terminal. This assumes that CUBRID is installed in your system (or see [CUBRID Installation Instructions|installation instructions]). If necessary, replace sample_db with your own database name.

cubrid createdb sample_db

This will create a database in your current working directory with a user dba and a blank password. If necessary, you can set a user password at this step or [Change database user password|change it later].

If you want to keep your databases in a certain directory, first navigate to that directory and then execute the above createdb command in that directory.

Once you have created a database, you need to start it before you try to connect to it.

cubrid server start sample_db

If you decided to use a command line terminal, you need to connect to a database to execute SQL queries. CUBRID provides CSQL command line SQL interpreter for this. Let's connect to a database.

csql sample_db -u dba

CSQL Interpreter

Type `;help' for help messages.

csql>

Now create a table to hold users' data. SQL in CUBRID is very much same to that of MySQL.

CREATE TABLE "tbl_users"(
    "id" integer AUTO_INCREMENT,
    "email" varchar(100) NOT NULL UNIQUE,
    "join_date" integer NOT NULL,
    CONSTRAINT pk_tbl_users_id PRIMARY KEY("id")
);

Copy and paste the above schema declaration in the CSQL and press Enter.

Now let's insert some data into the table using CSQL.

INSERT INTO tbl_users (email, join_date) VALUES
('7hyn6@peg30xmw1hcdrcg.gov', 1328523265),
('29ggzm3@cexbebaju9pkrq.net', 1328534265),
('4yn69iqqe@rh6c5b28xaw.gov', 1328528265),
('dyku2b8@wzfofw5aqymu7.biz', 1323423265),
('7au9hv1u@boi1ba1wowlfj3m.org', 1328523665);

At this point you have learnt how to create a database and a table as well as insert sample data.

Can't start your database?

There can be several reasons why your database may fail to start.

Make sure your hostname resolves (by editing hosts file) to the IP of your server (eg. localhost or 127.0.0.1). It is common that users forget to ensure this. Note that CUBRID doesn't support IPv6, which means your hostname should resolve to an IPv4 address.
Make sure your server has enough memory. By default CUBRID Server is configured (via data_buffer_size server parameter) to demand 512MB of memory to start a single database. Your options are either to increase your memory to satisfy the minimum requirements, or decrease the data_buffer_size parameter value.

Getting Started with CUBRID Database AMI (Amazon Machine Image)

2013-01-29T01:33:36-08:00

For those users looking to seamlessly deploy CUBRID Database on Amazon Web Services (AWS), we have created Amazon EC2 Machine Images (AMI) with CUBRID and its APIs installed. In this tutorial I will explain the key steps you need to perform in order to get everything started on AWS. We will:

Review available CUBRID AMIs.
Review the software stack of the CUBRID AMI.
Create an account on Amazon Web Services.
Launch your instances based on CUBRID AMI.
Configure your instance.

CUBRID AMI

The following is a list of CUBRID AMI we (owner ID: 024941853939) provide officially. We distribute CUBRID AMIs to all available regions (if a new region is available and we do not distribute there, let us know and we will add it as well). Shortly we will add AMIs based on other Linux distirbutions as well.

Owner ID	CUBRID Version	OS	Root Device	Image Size	AMI ID	EC2 Region
024941853939	CUBRID 8.4.3.1005 x64	Ubuntu 12.04.1 x64	EBS	8GB	ami-cd8713a4	us-east-1 (N. Virginia)
=	=	=	=	=	ami-5aea606a	us-west-2 (Oregon)
=	=	=	=	=	ami-6ae4c72f	us-west-1 (N. California)
=	=	=	=	=	ami-9ee3edea	eu-west-1 (Ireland)
=	=	=	=	=	ami-980c41ca	ap-southeast-1 (Singapore)
=	=	=	=	=	ami-77c14576	ap-northeast-1 (Tokyo)
=	=	=	=	=	ami-ee5accd4	ap-southeast-2 (Sydney)
=	=	=	=	=	ami-039c471e	sa-east-1 (São Paulo)

I will explain how to use these Amazon Machine Images below. First, let's see what software will be available for you in this Amazon Machine Image.

Software Stack

OS

Official Ubuntu 12.04.1 (precise) x64 LTS cloud AMI distributed by Canonical (AMI ID: ami-8e109ebe; note, this is not CUBRID AMI ID).

We will soon provide CentOS based CUBRID AMIs.

Default software

The following software is installed on Ubuntu 12.04.1 by default.

Python 2.7.3 with pip 1.0
Perl 5.14.2 with CPAN 1.57

Custom software

Now here we have installed the software necessary to work with CUBRID Database Server.

CUBRID Database Server 8.4.3.1005 x64
Python driver v8.4.3.0002
Perl driver 8.4.3.0001
PHP 5.3.10 with PECL/PEAR
PHP driver 8.4.3.0001
PDO driver 8.4.3.0001
Apache HTTP Server 2.2.22 (installed automatically by PHP)

These are all you need to get started with CUBRID Database on Amazon Web Services.

Getting Started

Create an account on Amazon Web Services

If you already have an AWS account, you can skip this step and continue. If you do not have one:

Go to http://aws.amazon.com, and click on the Sign Up button. Sign in to your existing AWS account or create a new one.
Go to http://aws.amazon.com/ec2 and clck on teh Sign Up Now button. If it is the first time you are signing up, you may be eligible for free 750 hours of Micro instance every month for one year.
1. Enter your credit card information and complete your signup for the Amazon EC2 service. It takes from several hours to couple of days for your EC2 account to set up. Eventually you should receive a confirmation email from Amazon Web Services.
Once you have your EC2 account set up, go to EC2 Web Console.
1. Create a key pair. You will need this key pair to launch EC2 instances and connect to them via SSH. The public key will remain in your EC2 account, while you will use the private key when establising an SSH connection to newly created instances.
  1. Click Key Pairs under Networking and Security in the Navigation pane and then click the Create Key Pair button (save it in e.g. ~/.ec2/ec2.pem). Download the private key. You will not be able to download it later. Do it now!
2. Set up your Amazon API credentials. For this you need to create a new certificate.
  1. On the top right corner of the EC2 page go to the menu displayed by your name, there choose Security Credentials.
  2. Under the Access Credentials click on the X.509 Certificates tab.
  3. Create a new certificate.
  4. Once created, download the private key and the certificate (save them in e.g. ~/.ec2/cert-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX.pem and ~/.ec2/pk-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX.pem).
  5. Make your credential files private. In your command line type:
    chmod go-rwx ~/.ec2/*.pem
  6. If at a later time you need to create a new certificate, you can come back here and create a new certificate again.

Congratulations! Now you are ready to create your first Amazon EC2 instance.

Launching CUBRID Instance

There are different ways you can find and launch CUBRID Amazon Machine Images. Below I will explain two ways:

From AWS site
From your EC2 Web Console

From AWS site

You can navigate to http://aws.amazon.com/amis/cubrid-8-4-3-sql-database-ebs-64-bit-ubuntu-12-04-1 public AMI listing and press the Launch Instance button from there. Then continue as described below.

From your EC2 Web Console

Go back to your EC2 Web Console.
At the top right corner of the page you will see a dropdown menu with a list of availability zones. Switch to the one you think is most suitable for your needs.
Once the Web Console is refreshed, you will see a Launch Instance button. Press it in order to see the Launch Wizard.
Select the Classic Wizard and press Continue.

Configure EC2 Instance

Now you need to choose one of CUBRID AMIs.ins
1. Press on the Community AMIs tab.
2. In the search box type cubrid or directly enter one of the CUBRID AMI IDs available in that region. The system will list matching AMIs as shown in the schreenshot below.
3. Make sure the owner ID is 024941853939. You can find it the Manifest field as shown above. This owner ID proves that the selected AMI is created by us, the CUBRID Team, and we will provide support. In case another owner ID is set for some of our CUBRID AMIs, we will mention so in the table above.
4. To select the desired CUBRID AMI, press the Select button on the right of that image.
5. Next, configure your instances.
  1. Choose the number of instances. In this tutorial we will choose to launch only 1 instance.
  2. Then choose the Instance Type you want to launch. Each type differs in CPU units, CPU cores, Memory, and Price. You may want to check out the EC2 Pricing to make the right decision. For this tutorial we will choose the smallest T1.Micro instance which provides 613MB of memory and up to 2 EC units (for short periodic bursts). Notice, though, that this Micro instance does not guarantee 2 EC units. In fact, it will provide only short periodic bursts of 2 EC units, and often it will fall way below the expectation. For more details and test results on this matter check out Greg Wilson's blog about Amazon EC2 Micro Instance and Stolen CPU.
  3. Next, you may choose between Launch Instances (the normal EC2 instances) and Request Spot Instances. If you are just beginning, I suggest you go with a common Launch Instances option. This is what we will do in this tutorial.
  4. Availability Zone: if you have no preference on where exactly in your current region should the instance launch, simply leave it as No Preference.
  5. Once done, press the Continue button.
6. Next, the Launch Wizard will show Advanced Options. You may leave everything with the default settings, and press Continue.
7. Storage Device Configuration: the defult configuration of the CUBRID AMI will attach an 8GB EBS volume storage device (default from Ubuntu by Canonical) to the newly launched instance. You may leave it with the default settings, or if necessary change it by pressing on the Edit button. When done, press on the Continue button.
8. Next, add tags to your instance. For example, you can give a Name to your instance such as My new instance with CUBRID 8.4.3 or something of that sort. Then press the Continue button.
9. Now you need to choose the Key Pairs to let the EC2 know which keys will allow users to access this instance via SSH. Now, you have already created your Key Pair above when you created your EC2 account, have not you? If you have previously created your Key Pair and you have the private key downloaded, then choose it from the given list as shown below. If you have not created the Key Pair before or want to create a new one now, then choose the Create a new Key Pair option, and create one. In this tutorial, I will use the previously created Key Pair. Remember, that once you set this Key Pair in this step, you will not be able to change it after the instance is launched.
10. Next, Configure the Firewall.
  1. If you have not created any Security Group before, you will be given a Default group as shown in the following screenshot. This default security group restricts any kind of access to this instance from outside. But we will not choose it. Instead, we will create a new Security Group specifically for CUBRID Database usage. So, continue reading.
  2. We will create a new Security Group to open CUBRID database related ports. So choose the Create a new Security Group option.
    1. For a Group Name enter CUBRID for you to know what this Security Group is related to.
    2. Group Description: Open CUBRID Database related ports.
    3. Choose Custom TCP rule.
    4. Enter 8001-8003 to a Port range.
    5. Leave Source as 0.0.0.0/0. This tells EC2 that the above specified port will listen to connections from any IP. If you want to limit only specific IP to have an access to this instance, enter the IP here.
    6. Once done, press the Add Rule button.
    7. Now repeat the last 3 steps to enter separate rules for 30000, 33000, 8282, 1523 ports as shown in the screenshot below.
    8. Finally open the SSH port 22. This time choose SSH from the Create a new rule dropdown box and press on the Add Rule button.
    9. We are done! Press the Continue button.
11. Now, Review the Summary. If necessary, you can go back and customize any option as you wish. Once ready, press the Launch button to take off.

Quite a long way but you have made it! So, congratulations with your new CUBRID Instance! In fact, you can apply the same process with any other AMI distributed by other vendors.

SSH Connection

Now let's connect to our CUBRID Amazon Server via SSH and have a sightseeing tour! For this we need two items:

A Private Key.
A Public DNS

Private Key

The first thing to remember is that we have opened SSH port 22 in our "CUBRID" Security Group (step 5.10 above). This means we can connect to the newly created instance right away with our private key. In fact, only those users who posess this private key that matches the public key assosiated with the newly launched instance can access this instance. Just to remind you, once you have set a Key Pair during the instance initialization step, you will not be able to change it.

Public DNS

In order to connect to our remote Amazon EC2 instance, we need to know either the IP address or the Public DNS attached to that instance. You can find the Public DNS of your instance if you go to https://console.aws.amazon.com/ec2->Instances->My new instance with CUBRID 8.4.3.

Once you select your instance a detailed description will be displayed below it. You can find your Public DNS there as shown below.

Establish SSH connection

So, we now have both the private key and the Public DNS. Let's establish an SSH connection.

$ ssh -i MY_PRIVATE_KEY_FILE.pem ubuntu@MY_PUBLIC_DNS
The authenticity of host 'MY_PUBLIC_DNS (MY_PUBLIC_IP)' can't be established.
RSA key fingerprint is dc:17:a9:ca:b8:c4:e5:59:f3:e4:8a:1a:03:cb:94:9e.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added 'MY_PUBLIC_DNS,MY_PUBLIC_IP' (RSA) to the list of known hosts.
Welcome to Ubuntu 12.04.1 LTS (GNU/Linux 3.2.0-31-virtual x86_64)

 * Documentation:  https://help.ubuntu.com/

  System information as of Tue Jan 29 08:33:09 UTC 2013

  System load:  0.08              Processes:           64
  Usage of /:   14.9% of 7.87GB   Users logged in:     0
  Memory usage: 8%                IP address for eth0: 10.248.26.17
  Swap usage:   0%

  Graph this data and manage this system at https://landscape.canonical.com/

80 packages can be updated.
35 updates are security updates.

Get cloud support with Ubuntu Advantage Cloud Guest
  http://www.ubuntu.com/business/services/cloud
ubuntu@ip-MY_INTERNAL_IP:~$

Thus, we are in!

Check CUBRID

Check CUBRID Server Status

The first thing you can do is check the status of CUBRID Database Server.

ubuntu@ip-MY_INTERNAL_IP:~$ cubrid service status
@ cubrid master status
++ cubrid master is not running.
@ cubrid server status
++ cubrid master is not running.
@ cubrid broker status
++ cubrid broker is not running.
@ cubrid manager server status
++ cubrid manager server is not running.

Since we have not yet started the CUBRID Service, everything is stopped.

Start CUBRID Server Status

Start the CUBRID Service status:

ubuntu@ip-MY_INTERNAL_IP:~$ cubrid service start
@ cubrid master start
++ cubrid master start: success
@ cubrid broker start
++ cubrid broker start: success
@ cubrid manager server start
++ cubrid manager server start: success

CUBRID Master, Broker and Manager Server services will start up.

Now, if you had created a database before and have set to auto start it, the CUBRID Server service would also start which would start the specified database.

Notice, that in case you restart your EC2 instance, you will need to start CUBRID Service manually each time as it is not set to start on system startup.

Conclusion

In this tutorial you have learnt how to find and launch Amazon EC2 instances based on CUBRID Amazon Machine Images. We provide CUBRID AMIs on all regions. Now go straight to CUBRID Tutorials and proceed to creating your first CUBRID database. For Driver related tutorials visit the CUBRID APIs wiki page.

If you ever need any help or have a question, feel free to comment below, ask a question at CUBRID Q&A site or forum, Facebook or Twitter, or at #cubrid Freenode Web Chat.

CUBRID Tutorials

2011-12-20T04:59:29-08:00

Quick Start

It is very easy to get started with CUBRID. Follow these step-by-step tutorials and you will see how fun it is to learn CUBRID.

Follow [CUBRID Installation Instructions] (Windows, Linux)
Start CUBRID Service
[Create a sample CUBRID Database from the command line]
[Start or Autostart CUBRID Database]
[Change database user password]
[Getting started with demodb (CUBRID Demo Database)]
[Create the demodb CUBRID Demo Database]
[Connecting to a remote CUBRID Database]
[Important Facts to Know about CUBRID]
[How to ... using CUBRID Tutorials|How to ... using CUBRID] - a set of HowTo tutorials.

Easy Database Administration

CUBRID Web Manager - the next generation SQL client with monitoring features - Blog article
Download CUBRID Manager (Windows, Linux, Mac OS X)
Run CUBRID Manager. This tutorial will show you how to:
- Add and Connect to a host
- Login to and Start a database
- Execute queries (SELECT, UPDATE, DELETE)
More details are available at CM Manual.

Install CUBRID Database Drivers

PHP Driver
PDO Driver
Python Driver
Perl Driver
Ruby Driver
ADO.NET Driver
ODBC Driver
OLEDB Driver
JDBC Driver
Node.js Driver
Interactive Connection String Builder - user blog

Have Questions?

So far so easy! But if you have questions, head to CUBRID Q&A site. If you run into issues, post them on CUBRID Forum. We will be very glad to help you out!

Going Further

[How to Contribute to CUBRID Project]
Growing in the Wild. The story by CUBRID Database Developers. - RIT++ 2012 Conference presentation
Database Sharding the Right Way: Easy, Reliable, and Open source - HighLoad++ 2012 Conference presentation
[CUBRID Configurations]
CUBRID – Open Source RDBMS Highly Optimized for the Web - M&T Magazine, Sprint 2012, Vol. 20, Issue 1.
How to Get the CUBRID Version Number

CUBRID SQL Tutorials

[CUBRID RDBMS Size Limits]
[Shared Query Plan Caching in CUBRID]
[Why prepare queries if auto-parameterization already does that?]
[Execute prepared SQL in CUBRID]
CUBRID Query Tuning
What is Covering Index in CUBRID 8.4.0?
CUBRID Click Counter
Comparison of Implicit Type Conversion in MSSQL, Oracle, MySQL, and CUBRID
CUBRID vs. MySQL vs. Oracle Data Type Mapping
Things to Understand When Moving from MySQL to CUBRID - blog article
How SQL UPDATE is performed in CUBRID - blog article.
CUBRID Serials
Database Information in CUBRID
CUBRID SQL Guide
Hierarchical Queries in CUBRID
- CUBRID Hierarchical Queries
- Hierarchical Query - Manual
- How to Concatenate Column Values from Different Rows
[Working with CUBRID BLOB / CLOB Data Types]
[Inserting a BLOB file to a CUBRID database]
Playing with CLOB data in CUBRID - user blog
CUBRID Transaction and Lock
Obtaining Basic Database Information
Best Way to Store IP Address in CUBRID

Advanced CUBRID Server Topics

CUBRID Architecture
- [CUBRID Source Code]
- CUBRID Inside - Architecture, Source & Management Components
- CUBRID Reference Architecture for Social Networking Service
- CUBRID Release Policy
- The Architecture of CUBRID
- Architecture of CUBRID - Blog article
- The CUBRID Broker Story - Blog article
- CUBRID Database Processes - Blog article
- Basic Operations of CUBRID Processes - Blog article
- [CUBRID Query Processing]
- All about Two-Phase Locking and a little bit MVCC - Blog article
- How data is stored in CUBRID RDBMS? Intro to Objects, Classes, OID and Inheritance - Blog article
CUBRID Performance
CUBRID Developer's Course
Introduction to CUBRID Security - Part I
Introduction to CUBRID Security - Part II
CSQL Interpreter
- How to Use CSQL (CUBRID SQL Interpreter)
- CSQL - Command Line SQL Interpreter - Blog article
Server Error Msg
[CUBRID Error Codes]
Data Structures
Connection Management and Threads in CUBRID Server
Server Startup/Shutdown Process
CUBRID Log Files
CUBRID HA
- How CUBRID HA Works?
- [Configure CUBRID HA with Vagrant and Chef Cookbook under 4 minutes]
- CUBRID HA Starting Guide
- CUBRID HA Guide Extended
- Overview of New High-Availability Features in CUBRID 8.4.0 - Blog article
- CUBRID HA - Guaranteed Way to Never-Die Web Services - OSCON 2011 Conference presentation
CUBRID SHARD
- Database Sharding the Right Way: Easy, Reliable, and Open source - HighLoad++ 2012 Conference presentation
- [Configure CUBRID SHARD with Vagrant and Chef Cookbook under 2 minutes]
- Easy MySQL Database Sharding with CUBRID SHARD - 2013 Percona MySQL Conference presentation
- Быстрый и простой способ шардирования MySQL с помощью CUBRID SHARD - 2013 RIT++
- CUBRID Database Sharding User Specifications
- Database Sharding with CUBRID - Blog article
- Database Sharding Platform at NHN - Blog article
- Getting started with CUBRID SHARD - Forum post
CUBRID Automated Scripts for DB Hosting Service
Backup & Restore
CUBRID Triggers
Java Stored Procedures
- CUBRID Java Stored Procedures
- Java Stored Procedure - Manual
- Emulate long running SQL queries in CUBRID - user blog

Working with Third-party Tools

CUBRID Service through CUBRID Manager
RCP Application
[Using Solr / Lucene for full text search with CUBRID Database on Ubuntu]
Install CUBRID with AutoSet
Use Apache DdlUtils and Scriptella to migrate databases to CUBRID
Apache DDLUtils & Scriptella: Migrating to CUBRID - Video Tutorial
Scriptella for CUBRID - Video Tutorial
How to Do Replication on UNIX & Linux
CUBRID Administration Tools - Blog article
CUBRID WebQuery Tutorial
Uniform Server - CUBRID Video Tutorial
phpMyEdit for CUBRID - Video Tutorial
SQL Buddy for CUBRID - Video Tutorial
Eclipse
- CUBRID Through SQuirrel SQL Client
- CUBRID Through Eclipse SQL Explorer
- CUBRID through QuantumDB Eclipse plugin
Using CUBRID in AquaDataStudio
Installing WordPress for CUBRID
Using Hibernate with CUBRID
Analyzing JDBC Logs with log4jdbc
Store Java Logs to Database Using log4j
Clj-DBCP Clojure Library for Connecting to CUBRID Database
Using CUBRID with PowerShell
[!Solved] Chef: NameError: Cannot find a resource for converge_by on centos

DLL Load Failed

2013-05-13T05:02:25-07:00

A common problem encountered when configuring drivers is the "Dll Load Failed" error. This error can occur when cascci.dll file is not found or when the file found is not the correct 32 bit or 64 bit version that we are expecting. For example, "ImportError: DLL load failed: %1 is not a valid Win32 application." error encountered in python (see example error message below), is caused when you install 32 bit version of python and 64 bit version of CUBRID on a 64 bit machine. The problem is CUBRID 64 bit comes with 64 bit version of cascci.dll which cannot be loaded by python.

C:\Program Files (x86)\Python266>python.exe
Python 2.6.6 (r266:84297, Aug 24 2010, 18:46:32) [MSC v.1500 32 bit (Intel)] on win32
Type "help", "copyright", "credits" or "license" for more information.
>>> import CUBRIDdb
Traceback:  File "<stdin>", line 1, in <module>
  File "C:\Program Files (x86)\Python266\lib\CUBRIDdb\__init__.py", line 9, in <module>
    import _cubrid
ImportError: DLL load failed: %1 is not a valid Win32 application.
>>>

The solution for this error is to download the cascci.dll driver for your CUBRID server version from here:

http://www.cubrid.org/?mid=downloads&item=cci_driver&os=detect&ostype=x86

And you must copy this file either in the same folder as your python installation (where the python.exe file is located) or into a location that is in the path. The idea we want here is to use our version of cci driver and not the one that comes with the CUBRID installation ($CUBRID\bin\cascci.dll). The same procedure is done for php driver also.

Note: From the archives in the link above, only cascci.dll is required for driver usage. If you wish to replace C:\CUBRID\bin\cascci.dll file, then you should replace C:\CUBRID\lib\cascci.lib also with the cascci.lib file from the archive.

If anything is unclear, don't hesitate to ask a question in our Q&A Site.

How to Unsubscribe From Newsletter

2013-05-02T03:22:18-07:00

Hello everyone,

This easy step by step tutorial will teach you how to unsubscribe from the CUBRID Newsletter.

1. First, you must login. If you do not have an account, click "Register" in the top right part of this page.

2. To enable the newsletter, go to your profile by clicking "My Profile" in the top right part of the screen.

3. In the profile page, click the Edit Profile button in the lower part of the page.

4. In the Edit Profile screen, uncheck the checkbox next to Newsletter and click Submit.

The direct link of the Edit Profile screen is http://www.cubrid.org/?act=dispMemberModifyInfo.

We wish you a great day and hope that you will return to our community in the future!

How to Subscribe to Newsletter

2013-05-02T03:17:48-07:00

Hello everyone,

This easy step by step tutorial will teach you how to subscribe to the CUBRID Newsletter. Before starting, you should know that we will send you one email per week with the latest news in the CUBRID Community.

1. First, you must login. If you do not have an account, click "Register" in the top right part of this page.

2. To enable the newsletter, go to your profile by clicking "My Profile" in the top right part of the screen.

3. In the profile page, click the Edit Profile button in the lower part of the page.

4. In the Edit Profile screen, check the checkbox next to Newsletter and click Submit.

The direct link of the Edit Profile screen is http://www.cubrid.org/?mid=wiki_tutorials&act=dispMemberModifyInfo.

Thank you for enabling the CUBRID newsletter and becoming part of the CUBRID Community!

Installing CUBRID on Ubuntu

2012-01-24T20:49:06-08:00

To install CUBRID using apt-get on Ubuntu, we need to add CUBRID's repository so that Ubuntu knows where to download the packages from, and then tell the OS to update its indexes.

sudo add-apt-repository ppa:cubrid/cubrid
sudo apt-get update

If add-apt-repository command is not recognized by your system, you must install the python-software-properties package. Once the Python packages are installed, perform the step 1 above again, then continue.

sudo apt-get install python-software-properties

Now install the latest version of CUBRID:

sudo apt-get install cubrid

To install an earlier version, indicate the version as:

sudo apt-get install cubrid-8.4.0

To complete the installation and set the CUBRID PATH variables, reboot your OS. Until you reboot, you can also run the command ". /etc/profile.d/cubrid.sh" every time you open up a terminal if cubrid command is not found.

Optional: If you want to install the demodb sample database, run the command:

 sudo apt-get install cubrid-demodb

Installation Notes

CUBRID is installed in /opt/cubrid.
The configuration files are placed in /etc/opt/cubrid.
Variable files (such as logs or databases) are stored in /var/opt/cubrid.
The path variables $CUBRID and $CUBRID_DATABASES are set in the file /etc/profile.d/cubrid.sh.
If you run a CUBRID service command, you can view its output in /var/opt/cubrid/tmp/service.cubrid.
CUBRID is set to automatically start on boot and the service file is located at /etc/init.d/cubrid.
Highly Important! cubrid or standalone csql commands can be only ran as cubrid user (which has no password). To connect as this user, use "sudo su -s $SHELL cubrid".

How to Enable/Disable AutoCommit Mode

2013-04-08T06:50:41-07:00

One thing anyone would want from a database is to use Transactions. In order to do so, one must know that CUBRID has autocommit enabled by default. In order to be able to use Transactions, this will need to be disabled and there are several ways to do this:

CSQL Interpreter

In CSQL, the command ;autocommit or ;au for short:

;au off

Here is an example: http://www.cubrid.org/manual/90/en/Transaction Commit

CUBRID Manager

In CUBRID Manager, autocommit can be disabled by clicking the autocommit icon in the upper part of the query editor tab.

Drivers

In various drivers, there are functions for each driver that allow enabling/disabling the autocommit mode:

PHP - http://www.php.net/manual/en/function.cubrid-set-autocommit.php

Python - http://www.cubrid.org/wiki_apis/entry/cubrid-python-api-documentation (autocommit in url)

Ruby - http://www.cubrid.org/wiki_apis/entry/cubrid-ruby-api-documentation

JDBC - http://www.cubrid.org/accessing_cubrid_with_jdbc_part2 (setAutoCommit function)

CCI - http://www.cubrid.org/manual/90/en/cci_set_autocommit

ADO.NET - http://www.cubrid.org/wiki_apis/entry/connection-options

Regardless of the approach chosen, 2 SQL commands can be used to commit or rollback a transaction:

COMMIT

in order to commit a transaction and

ROLLBACK

in order to perform a rollback. You can also perform rollbacks to a savepoint. A tutorial with an example can be found here: http://www.cubrid.org/manual/90/en/Savepoint and Partial Rollback

How to Build CUBRID from Source on Fedora/Centos

2013-04-03T02:28:31-07:00

Prerequisites

To install the required packages, simply run the command below:

sudo yum install libtool texinfo java-1.6.0-openjdk-devel flex gcc-c++ ant ncurses-devel gc-devel glibc-devel lzo-devel libedit-devel pcre-devel libaio-devel elfutils-libelf-devel chrpath

Note: java-1.7.0-openjdk-devel must be used on Fedora 17 and above instead of java-1.6.0-openjdk-devel.

Note: On Fedora 15 and above, you must also install systemd-units.

Set the JAVA Environment Path:

export JAVA_HOME=/usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0

Make sure the path corresponds to your installation.

Building CUBRID

Generate the configure script according to your environment:

./autogen.sh

Run configure with --prefix specifying the location where you want CUBRID to be built. On 64 bit systems, you must add --enable-64-bit parameter.

./configure --prefix=/usr/share/cubrid

(or ./configure --prefix=/usr/share/cubrid --enable-64-bit for 64 bit systems)

Run make and make install (for make install sudo access may be required to copy files to /usr/share/cubrid.

make
sudo make install

All the files are installed in the prefix directory (in this case /usr/share/cubrid).

The files are owned by root. If you want to edit the owner run:

sudo chown -R user:user /usr/share/cubrid

The username and group in our example is user.

In order to set the CUBRID enviroment variables, you can use this cubrid.sh file. If you install CUBRID in a different directory, replace /usr/share/cubrid in the file with the path where you have installed CUBRID.

You have 2 options on how to use the cubrid.sh file:

1. copy it to /etc/profile.d/cubrid.sh and this way it will be loaded automatically

2. copy it to any location you want and load it using the command:

. /home/user/cubrid.sh

Make sure to leave a space between the "." and the cubrid.sh file. We assumed that /home/user is the directory where you copied the cubrid.sh file.

Create the databases folder and databases.txt file:

mkdir -p /usr/share/cubrid/databases
touch /usr/share/cubrid/databases/databases.txt

Then, you can start and use cubrid:

cubrid service start

If you encounter any issue, post it on our forum or post a question in our Q&A section.

How to Build CUBRID from Source on Ubuntu

2013-04-02T23:37:01-07:00

Prerequisites

To install the required packages, simply run the command below:

sudo apt-get install openjdk-6-jdk ant texinfo make-doc libncurses5-dev libtool flex autoconf automake g++ libelf-dev

Note: openjdk-7-jdk must be used on Ubuntu 12.10 and above instead of openjdk-6-jdk.

Set the JAVA Environment Path:

export JAVA_HOME=/usr/lib/jvm/java-6-openjdk-i386

Make sure the path corresponds to your installation.

Building CUBRID

Generate the configure script according to your environment:

./autogen.sh

Run configure with --prefix specifying the location where you want CUBRID to be built. On 64 bit systems, you must add --enable-64-bit parameter.

./configure --prefix=/opt/cubrid

(or ./configure --prefix=/opt/cubrid --enable-64-bit for 64 bit systems)

Run make and make install (for make install sudo access may be required to copy files to /opt/cubrid.

make
sudo make install

All the files are installed in the prefix directory (in this case /opt/cubrid).

The files are owned by root. If you want to edit the owner run:

sudo chown -R user:user /opt/cubrid

The username and group in our example is user.

In order to set the CUBRID enviroment variables, you can use this cubrid.sh file. If you install CUBRID in a different directory, replace /opt/cubrid in the file with the path where you have installed CUBRID.

You have 2 options on how to use the cubrid.sh file:

1. copy it to /etc/profile.d/cubrid.sh and this way it will be loaded automatically

2. copy it to any location you want and load it using the command:

. /home/user/cubrid.sh

Make sure to leave a space between the "." and the cubrid.sh file. We assumed that /home/user is the directory where you copied the cubrid.sh file.

Create the databases folder and databases.txt file:

mkdir -p /opt/cubrid/databases
touch /opt/cubrid/databases/databases.txt

Then, you can start and use cubrid:

cubrid service start

If you encounter any issue, post it on our forum or post a question in our Q&A section.

How to Start or Autostart a CUBRID Database

2012-05-04T01:33:26-07:00

1. CUBRID Script for Autostart on Linux

1-1. We provide a cubrid script for auto start database processes.

Please get download a script file from :
http://svn.cubrid.org/websvn/filedetails.php?repname=cubridscripts&path=/cubrid_scripts/cubrid

#!/bin/bash
# 
# cubrid        This shell script takes care of starting and stopping
#               the CUBRID service
#
# chkconfig: 2345 98 05
# description: cubrid start/stop script  
#
# ts:4

### BEGIN INIT INFO
#
# Short-Description: CUBRID   
# Provides: CUBRID      
# Default-Start: 3 5
# Default-Stop: 0 6
### END INIT INFO


# Source function library.
. /etc/init.d/functions

# return code
CUBRID_SUCCESS=0
CUBRID_FAILED=1

US=`uname -n`
WHOAMI=`whoami`
RETVAL=0
prog=cubrid
_old_IFS=" $IFS"

### user specific environment ##################
CUBRID_USER=cubrid

if [ $WHOAMI = "root" ]; then
        CUBRID_DATABASES=`su - $CUBRID_USER -c 'printenv CUBRID_DATABASES'`
        CUBRID_HOME=`su - $CUBRID_USER -c 'printenv CUBRID'`
else
        CUBRID_USER=$WHOAMI
        CUBRID_HOME=$CUBRID
        export PATH=$PATH:$CUBRID_HOME/bin
fi

RFNAME=/tmp/.$prog.$CUBRID_USER
################################################

sudo_cubrid() {
        [ "$#" -ne 1 ] && return

        if [ $WHOAMI = "root" ]; then
                su - $CUBRID_USER -c "$1"  
        else
                sh -c "$1"
        fi
}
save_IFS() {
        _old_IFS=" $IFS" # save $IFS
}

restore_IFS() {
        if [ -z "$_old_IFS" ] # restore old $IFS
        then 
                unset IFS
        else 
                IFS="$_old_IFS"
        fi
}

check_config()
{
        # CHECK ha-mode
        cubrid_conf_file=$CUBRID_HOME/conf/cubrid.conf
        [ -r $cubrid_conf_file ] || exit

        eval "$(sed $cubrid_conf_file -n -e 's/\(.*\)\b.*=[\ ]*\(.*\)/\1="\2"/p')"
        if [ $ha_mode"x" != "x" ] && [ $ha_mode = "yes" -o $ha_mode = "on" -o $ha_mode = "role-change" ]; then
                return $CUBRID_FAILED
        fi

        return $CUBRID_SUCCESS
}


service_start() {
        sudo_cubrid "cubrid service start 2>&1 >$RFNAME"
        grep -wqs "fail" $RFNAME
        RETVAL=$?
        [ $RETVAL -ne 0 ] || return $CUBRID_FAILED
        return $CUBRID_SUCCESS
}

service_stop() {
        sudo_cubrid "cubrid service stop 2>&1 >$RFNAME"
        grep -wqs "fail" $RFNAME
        RETVAL=$?
        [ $RETVAL -ne 0 ] || return $CUBRID_FAILED
        return $CUBRID_SUCCESS
}

service_status()
{       
        sudo_cubrid "cubrid service status"
}

start() {
        check_config    
        RETVAL=$?
        if [ $RETVAL -eq $CUBRID_SUCCESS ]; then
                service_start
                RETVAL=$?
        fi

        if [ $RETVAL -eq $CUBRID_SUCCESS ]; then
                echo -n $"Starting $prog: "
                success
                echo
        else
                service_stop    

                echo -n $"Starting $prog: "
                failure
                echo
        fi      

        [ $WHOAMI = "root" ] && touch /var/lock/subsys/$prog
}

stop() {
        check_config    
        RETVAL=$?
        if [ $RETVAL -eq $CUBRID_SUCCESS ]; then
                service_stop
                RETVAL=$?
        fi

        if [ $RETVAL -eq $CUBRID_SUCCESS ]; then
                echo -n $"Stopping $prog: "
                success
                echo
        else
                echo -n $"Stopping $prog: "
                failure
                echo
        fi      
}

restart() {
        check_config    
        RETVAL=$?
        if [ $RETVAL -eq $CUBRID_SUCCESS ]; then
                service_stop

                service_start
                RETVAL=$?
        fi

        if [ $RETVAL -eq $CUBRID_SUCCESS ]; then
                echo -n $"Restarting $prog: "
                success
                echo
        else
                echo -n $"Restarting $prog: "
                failure
                echo
        fi      
}

status() {
        check_config    
        RETVAL=$?
        if [ $RETVAL -eq $CUBRID_SUCCESS ]; then
                service_status
                RETVAL=$?
        fi
}

case "$1" in 
  start)
        start   
        ;;
  stop)
        stop
        ;;
  restart)
        restart
        ;;
  status)
        status
        ;;      
  *)    
        echo $"Usage $0 {start|stop|restart|status}"
        exit 1
esac

exit 0

1-2. Copy cubrid file into /etc/init.d/

1-3. You should modify "CUBRID_USER= " part in the file if you install CUBRID with a different user(Default username: cubrid).

### user specific environment ##################
CUBRID_USER=cubrid

1-4. Grant a execution permission by a following command:

chmod a+x cubrid

1-5. Run chkconfig commans as follows:

chkconfig --add cubrid

chkconfig --level 0345 cubrid on

chkconfig --list | grep cubrid

1-6. If your configuration is correct, you will encounter followings on a prompt. Now your script will work on whenever your server starts-up.

 cubrid          0:on    1:off   2:on    3:on    4:on    5:on    6:off

1-7. Let's see if your script works correctly.

/etc/init.d/cubrid start

2. Configuration for Autostart when running CUBRID SERVICE START

CUBRID provides one more convenient feature. You can specify databases, brokers, manageer processes as CUBRID SERVICE. If so, your command "cubrid service start" or "cubrid service stop" will run each of process you specified in cubrid.conf .

To start a database process only, type the following command in the terminal. Remember that all these operations can also be performed in GUI based CUBRID Manager, if you prefer.

cubrid server start my_database

If you use particular databases very often, you may configure CUBRID to auto start them when CUBRID Server is started. The configuration file is located in $CUBRID/conf/cubrid.conf. The default locations are C:\CUBRID\conf\cubrid.conf on Windows and /opt/cubrid/conf/cubrid.conf on Linux. Find the line which is commented out like:

#server=foo,bar

Uncomment this line by removing the hash (#) sign, and instead of default foo,bar list your databases separated by commas like:

server=my_database,my_other_database

Next time you restart CUBRID Server, the configured database(s) will be automatically started for you. In fact, each database will be auto started with the same "cubrid server start" command you usually use to manually start the database.

As a side note, you should know that in order to start a database, the server process must be running (the "server" keyword in "cubrid server start" command). The server process is usually automatically started by CUBRID Service upon "cubrid service start". To make this sure, check if "server" keyword is listed in the following line in the same cubrid.conf configuration file.

service=server,broker,manager

CUBRID Source Code

2012-06-18T19:07:33-07:00

Overview

CUBRID uses Subversion to manage its source code at Sourceforge.net. Instructions on Subversion use can be found at http://svnbook.red-bean.com/.

Web access

You may browser the source repository using SF.net's interface at http://cubrid.svn.sourceforge.net or at http://svn.cubrid.org/websvn/.

Anonymous SVN access

The latest version of CUBRID source code can be checked out anonymously from SVN branch with the following command:

svn co http://cubrid.svn.sourceforge.net/svnroot/cubrid/cubrid/branches/RB-<CUBRID VERSION> cubrid

Replace <CUBRID VERSION> with the appropriate version number such as 8.4.1. Browse the repository at http://cubrid.svn.sourceforge.net/viewvc/cubrid/ to find available versions.

Download source code

Alternatively, you can simply download .tar.gz CUBRID source code from each version at the Downloads page or the CUBRID FTP.

How to Upgrade CUBRID Safely on Ubuntu

2013-03-08T05:10:05-08:00

In this tutorial, we will focus on users that have installed CUBRID from apt-get. If this is the case, then the databases should be located in /var/opt/cubrid/databases or /opt/cubrid/databases.

If you upgrade from 8.4.0 to 8.4.1 or 8.4.3 for example, you only need to save the databases folder, uninstall and reinstall CUBRID using the following commands:

mkdir -p /home/user/database_backup
cp -R /var/opt/cubrid/databases /home/user/database_backup
sudo apt-get remove cubrid
sudo apt-get update
sudo apt-get install cubrid
cp -R /home/user/database_backup/* /var/opt/cubrid/databases/

Make sure to adapt "home/user" to your user. You can remove the backup folder database_backup after you start CUBRID and check if the databases are running correctly.

Important! Make sure that /var/opt/cubrid/databases/databases.txt file contains the right paths to the database folders.

If you want to perform a completely safe upgrade indepent of the CUBRID version, instead of copying the databases folder like in the above approach, you should use cubrid unloaddb to export all databases in a backup folder, then uninstall CUBRID, update repository and install the new CUBRID version. Finally, you must import the databases into the new CUBRID instance by running cubrid loaddb.

CUBRID Installation Instructions

2012-01-24T21:27:25-08:00

There are several ways to install CUBRID Database Server. Based on your OS choose the right installation instructions.

[Installing CUBRID on Windows] - Presentation
[Installing CUBRID on Ubuntu]
[Installing CUBRID on Fedora/CentOS]
[Installing CUBRID on Linux using Shell and RPM] - Presentation
[Install CUBRID, PHP Driver, XE CMS on Fedora/CentOS]
Run CUBRID Manager on Mac OS X
[Create a CUBRID Database VM with Vagrant and Chef Cookbook under 5 minutes]
[Configure CUBRID HA with Vagrant and Chef Cookbook under 4 minutes]
[Configure CUBRID SHARD with Vagrant and Chef Cookbook under 2 minutes]
[Install CUBRID remotely with knife-solo and Chef Cookbook]
[Getting Started with CUBRID Database AMI (Amazon Machine Image)]
Download VMware/VirtualBox images with CUBRID installed

Full index of CUBRID Database using Solr DataImportHandler

2012-02-21T22:49:03-08:00

This tutorial will illustrate an example where a sample data is batch indexed from a CUBRID database and POST'ed into Solr using DataImportHandler. Often it is called a pull approach.

At this point we assume that you have already completed [Using Solr / Lucene for full text search with CUBRID Database on Ubuntu|previous steps] and have the [Create a sample CUBRID Database from the command line|sample data] in your database.

In this tutorial we will create a simple single core server which will be located in /home/solr/apache-solr-4.0.0/example/cubrid-solr-example directory.

If you do not want to copy/paste all of the following codes, you can download cubrid-solr-example.zip and extract it under example/ directory. The contents of this archive include all files from this tutorial. Make sure that the lib folder contains the JDBC driver corresponding to your CUBRID server.

First, we need to login to solr user we have created before and navigate to the example/ directory.

su - solr
cd apache-solr-4.0.0/example/

Now let's create the home directory structure for our example.

mkdir cubrid-solr-example
cd cubrid-solr-example
mkdir conf lib

This will create the following directory structure.

/home/solr/apache-solr-4.0.0/example/
-----cubrid-solr-example/
----------conf/
----------lib/

Considering that your are in the home cubrid-solr-example directory, create the main configuration file for solr.

touch solr.xml

Save the following into this file. This will instruct Solr to create a single core server.

<?xml version="1.0" encoding="UTF-8" ?>

<solr persistent="false">

  <cores adminPath="/admin/cores" defaultCoreName="cubrid-example-core">
    <core name="cubrid-example-core" instanceDir="." />
  </cores>
  
</solr>

Now create a schema file which reflects the database schema of our [Create a sample CUBRID Database from the command line|sample database].

cd conf/
touch schema.xml

Save the following contents into this file. The following instructs Solr to create a schema for a users table which has 3 columns (id, email, join_date).

<?xml version="1.0" encoding="UTF-8" ?>

<schema name="tbl_users" version="1.0">

 <types>
    <fieldType name="tint" class="solr.TrieIntField" precisionStep="8" omitNorms="true" positionIncrementGap="0"/>
    <fieldType name="string" class="solr.StrField" sortMissingLast="true" omitNorms="true"/>
 </types>

 <fields>
   <field name="id" type="tint" indexed="true" stored="true" multiValued="false" required="true" /> 
   <field name="email" type="string" indexed="true" stored="true" multiValued="false" required="true" />
   <field name="join_date" type="tint" indexed="true" stored="true" multiValued="false" required="true" />
 </fields>

 <uniqueKey>id</uniqueKey>
 <defaultSearchField>email</defaultSearchField>

 <solrQueryParser defaultOperator="OR"/>

</schema>

Now create a configuration file for this cubrid-example-core in the same directory.

touch solrconfig.xml

Add the following to this file. Most of the configurations you see below are default settings. But we will stop on DataImportHandler and explain it a little bit more.

DataImportHandler is used to perform batch indexing of an SQL database table. But it is not a native Solr library, therefore it is not loaded by default. We need to instruct Solr to load it by <lib ...> tag. This handler comes with Solr package by default and is located in the dist/ directory in the root of the package. Therefore the path should be relative to the home directory of your example (in our case cubrid-solr-example/) and not relative to this solrconfig.xml file.

Further below we create a separate requestHandler for our DataImportHandler which will respond when you navigate to http://localhost:8983/dataimport URL. We tell Solr that the configurations for DataImportHandler are located in the /home/solr/apache-solr-4.0.0/example/cubrid-solr-example/conf/data-config.xml file.

<?xml version="1.0" encoding="UTF-8" ?>

<config>

  <abortOnConfigurationError>${solr.abortOnConfigurationError:true}</abortOnConfigurationError>

  <luceneMatchVersion>LUCENE_40</luceneMatchVersion>

  <lib dir="../../dist/" regex="apache-solr-dataimporthandler-\d.*\.jar" />

  <directoryFactory name="DirectoryFactory" 
                    class="${solr.directoryFactory:solr.StandardDirectoryFactory}"/>

  <updateHandler class="solr.DirectUpdateHandler2" />

  <requestDispatcher handleSelect="true" >
    <requestParsers enableRemoteStreaming="false" />
  </requestDispatcher>

  <requestHandler name="standard" class="solr.StandardRequestHandler" default="true" />

  <requestHandler name="/update" 
                  class="solr.JsonUpdateRequestHandler" 
                  startup="lazy" />

  <requestHandler name="/admin/" 
                  class="solr.admin.AdminHandlers" />

  <requestHandler name="/admin/ping" class="solr.PingRequestHandler">
    <lst name="invariants">
      <str name="qt">search</str>
      <str name="q">solrpingquery</str>
    </lst>
    <lst name="defaults">
      <str name="echoParams">all</str>
    </lst>
  </requestHandler>
  
  <requestHandler name="/dataimport" class="org.apache.solr.handler.dataimport.DataImportHandler">
<lst name="defaults">
      <str name="config">data-config.xml</str>
    </lst>
  </requestHandler>

  <admin>
    <defaultQuery>solr</defaultQuery>
  </admin>

</config>

For DataImportHandler to connect and query a database, it requires a JDBC driver of that database server. CUBRID provides a native JDBC Driver. If you have already installed CUBRID in your system, you can find the JDBC driver in /jdbc directory. In case of Ubuntu apt-get installation, it is located in /opt/cubrid/jdbc.

If you have not installed CUBRID in your system and plan to connect to a remote CUBRID server, you can download the JDBC driver from the CUBRID downloads page.

Important: you need to download the right JDBC driver, i.e. if the version of your remote CUBRID server is 8.4.1, then download JDBC driver for 8.4.1.

Place CUBRID JDBC driver into /lib directory of cubrid-solr-example. Solr will automatically load any library located in this directory.

Now we need to create this data-config.xml file for DataImportHandler which tells the exact authentication information, the exact SELECT query to execute to retrieve the data from the database, etc.

touch data-config.xml

In this file we tell DataImportHandler that:

it should use CUBRID's JDBC driver;
in the connection URL we indicate that CUBRID server is installed in the localhost, the broker port is 33000 (default), and the database name is sample_db;
the user name is dba;
no password is needed.

Also we indicate:

the exact query which should be execute to obtain the data from our database.
name of fields we created before for our Solr server and the corresponding column names of the database table.

<dataConfig>
    <dataSource type="JdbcDataSource" driver="cubrid.jdbc.driver.CUBRIDDriver" url="jdbc:cubrid:localhost:33000:sample_db" user="dba" password=""/>
    <document name="users">
        <entity name="user" query="select * from tbl_users">
            <field column="ID" name="id" />
            <field column="EMAIL" name="email" />
            <field column="JOIN_DATE" name="join_date" />
        </entity>
    </document>
</dataConfig>

Finally, you should have the following file structure.

/home/solr/apache-solr-4.0.0/example/
-----cubrid-solr-example/
----------conf/
---------------schema.xml
---------------solrconfig.xml
---------------data-config.xml
----------lib/
---------------cubrid_jdbc.jar
----------solr.xml

To confirm if all the configurations are correct, we can now start our Solr instance.

cd /home/solr/apache-solr-4.0.0/example
java -Dsolr.solr.home="./cubrid-solr-example/" -jar start.jar

This should start Solr on port 8983. Navigate to http://localhost:8983/solr/dataimport. You should see an XML output which indicates that the configurations are correct. Otherwise, your Solr instance would not start in which case write to our CUBRID Forum. We will be glad to help you out.

To import your data from sample_db, first, make sure your database is running.

cubrid server start sample_db

Then navigate to http://localhost:8983/solr/dataimport?command=full-import to perform full import. If you see an XML output, Solr may have successfully imported all your data from CUBRID database. To confirm this, you can search for data in Solr admin panel at http://localhost:8983/solr/admin/. In the Query String field enter a string which exists in your database. Solr should display the related data if such entry exists.

At this point you have learnt how to perform batch index of CUBRID database using DataImportHandler. For more examples, see [Using Solr / Lucene for full text search with CUBRID Database on Ubuntu].

Create a CUBRID Database VM with Vagrant and Chef Cookbook under 5 minutes

2013-01-02T00:16:27-08:00

In this tutorial I will show how to create an Ubuntu/CentOS VirtualBox image with CUBRID Database under 5 minutes. In fact, you can use this solution to create multiple development environments (multiple VMs) with different versions of CUBRID installed on each of them, and all these under 5 minutes. It is as easy as:

$ vagrant up

Also I will show how to install PHP/PDO, Perl and Python drivers along the way. You will also see how to get CUBRID Web Manager working. Remember that all these is completed automatically without your intervention. If you want to see how to do the same and get CUBRID HA and SHARD configured, refer to:

[Configure CUBRID HA with Vagrant and Chef Cookbook under 4 minutes]
[Configure CUBRID SHARD with Vagrant and Chef Cookbook under 2 minutes]

Requirements

Before I explain how and why the above works, I would like to first introduce the tools that you will need for this tutorial:

VirtualBox - it is a powerful open source virtualization software similar to VMware Workstation.
Vagrant - this is the key ingredient, the tool which will provide us with a base "box" (a clean Linux OS with a minimal set of software installed) on top of which we will provision, i.e. install different versions of CUBRID Database, Apache Web Server, PHP, and necessary CUBRID drivers.

Install both of these tools in your OS (Linux, Windows, Mac OS X). This is all you will need to get started.

Vagrantfile

Vagrantfile is a configuration file used by Vagrant. It includes the instructions for Chef Solo (an open source systems integration framework) to install the necessary software on top of a base Vagrant box.

I have created this file as well as the whole directory structure for you. You can download cubrid-vagrant-1.8.0.tar.gz (234K) archive to have it (or check the latest version from Sf.net repo). It will provide you with a project directory structure to get started. When you extract it, you will see the following directory structure.

$ tar -zxf cubrid-vagrant.tar.gz
 $ ls cubrid-vagrant
 cookbooks/
     apache2/
     apt/
     build-essential/
     cubrid
     perl
     php
     python
 Vagrantfile

This project already includes seven cookbooks including the one for CUBRID (Github repo). You do not have to know how cookbooks work. They are for Chef Solo to know how to install CUBRID and other related software.

If you look into Vagrantfile, you will see the following configurations.

# -*- mode: ruby -*-
  # vi: set ft=ruby :
  
  Vagrant::Config.run do |config|
    # All Vagrant configuration is done here. The most common configuration
    # options are documented and commented below. For a complete reference,
    # please see the online documentation at vagrantup.com.
  
    # Every Vagrant virtual environment requires a box to build off of.
    config.vm.box = "precise64" # Ubuntu 12.04 x64
    #config.vm.box = "centos63" # CentOS 6.3 x64
  
    # Assign this VM to a host-only network IP, allowing you to access it
    # via the IP. Host-only networks can talk to the host machine as well as
    # any other machines on the same network, but cannot be accessed (through this
    # network interface) by any external networks.
    config.vm.network :hostonly, "10.11.12.13"
  
    # Enable provisioning with chef solo, specifying a cookbooks path, roles
    # path, and data_bags path (all relative to this Vagrantfile), and adding
    # some recipes and/or roles.
    #
    config.vm.provision :chef_solo do |chef|
      # This path will be expanded relative to the project directory
      chef.cookbooks_path = "cookbooks"
  
      # specify which version of CUBRID we would like to install
      chef.json = {
          "cubrid" => {
              #"version" => "8.4.3",
              #"new_dbs" => ["newtestdb"],
              #"ha_dbs" => ["ha_test_db"],
              #"ha_hosts" => {"node1" => "10.11.12.13", "node2" => "10.11.12.14"}
          }
      }
  
      # "apt" is necessary to perform "apt-get update" command on Ubuntu OS.
      # Comment it out if using CentOS.
      chef.add_recipe "apt"
  
      # "apache" Web server to run PHP apps
      chef.add_recipe "apache2"
      chef.add_recipe "apache2::mod_php5"
      chef.add_recipe "apache2::mod_rewrite"
  
      # install PHP
      chef.add_recipe "php"
  
      # install CUBRID Database
      chef.add_recipe "cubrid"
      chef.add_recipe "cubrid::demodb"
      #chef.add_recipe "cubrid::ha"
      #chef.add_recipe "cubrid::new_dbs"
      chef.add_recipe "cubrid::pdo_cubrid"
      chef.add_recipe "cubrid::perl_driver"
      chef.add_recipe "cubrid::php_driver"
      chef.add_recipe "cubrid::python_driver"
      #chef.add_recipe "cubrid::shard"
      chef.add_recipe "cubrid::web_manager"
    end
  end

All lines which precede with a hash (#) symbol are comments.

Our Vagrantfile says to Chef Solo to:

Use apt cookbook to update the Ubuntu OS, which is used as our base box. Comment that line out if creating a CentOS VM.
Use apache2 cookbook to install Apache Web Server and its mod_php5 and mod_rewrite modules.
Use php cookbook to install PHP 5.3.3.
Use cubrid cookbook to install CUBRID version 9.0.0, its demodb database, PDO/PHP, Perl and Python drivers, automatically create multiple database, and auto configure CUBRID HA on multi VM environment. Instead of default CUBRID 9.0.0 Database, you can also install other versions like 8.4.3 or 8.4.1. To learn more, refer to cubrid-cookbook Github repo.

If you do not want to install a particular package, simply comment it out.

If necessary, you can extend the above Vagrantfile by adding other cookbooks and their recipes. You can find cookbooks for most software at https://github.com/opscode-cookbooks. Simply download the necessary cookbook, and place it under cookbooks/ directory. Then refer to it by adding one of its recipes to a Vagrantfile. You can also search for cookbooks at the official community site at http://community.opscode.com/cookbooks.

Vagrant Box

Since we are ready to launch our VM and have Vagrant provision it, let's make our last stroke - indicate which OS to use. Vagrant community provides several base boxes:

http://files.vagrantup.com/lucid32.box (261MB) - Ubuntu Server 10.04 (Lucid) x86 LTS
http://files.vagrantup.com/lucid64.box (280MB) - Ubuntu Server 10.04 (Lucid) x64 LTS
http://files.vagrantup.com/precise32.box (299MB) - Ubuntu Server 12.04 (Precise) x86 LTS
http://files.vagrantup.com/precise64.box (323MB) - Ubuntu Server 12.04 (Precise) x64 LTS

There are dozens more community-made boxes at http://www.vagrantbox.es/. You can download other Linux distributions from there. For example, here is a CentOS box from the community.

https://dl.dropbox.com/u/7225008/Vagrant/CentOS-6.3-x86_64-minimal.box (310MB) - CentOS 6.3 x64 minimal

In order to indicate which box to use, you need to run the following command specifying the URL where to download the box. In this tutorial we will use Ubuntu Server 12.04 x64 and name it precise64. This is an arbitrary name that we chose to distinguish this box from other boxes which we may potentially install later. This name is used in our Vagrantfile as a value for config.vm.box configuration parameter.

vagrant box add precise64 http://files.vagrantup.com/precise64.box

You can add multiple boxes. They will be stored by Vagrant at ~/.vagrant/boxes directory for your later use.

Start Up Vagrant

Now, let's start Vagrant:

$ cd cubrid-vagrant
$ vagrant up
[default] VM already created. Booting if it's not already running...
[default] Clearing any previously set forwarded ports...
[default] Forwarding ports...
[default] -- 22 => 2222 (adapter 1)
[default] Creating shared folders metadata...
[default] Clearing any previously set network interfaces...
[default] Preparing network interfaces based on configuration...
[default] Booting VM...
[default] Waiting for VM to boot. This can take a few minutes.
[default] VM booted and ready for use!
[default] Configuring and enabling network interfaces...
[default] Mounting shared folders...
[default] -- v-root: /vagrant
[default] -- v-csc-1: /tmp/vagrant-chef-1/chef-solo-1/cookbooks
[default] Running provisioner: Vagrant::Provisioners::ChefSolo...
[default] Generating chef JSON and uploading...
[default] Running chef-solo...
....

This will continue for a while. On my computer it takes less than five minutes to provision everything from the ground up.

Host IP

As you can notice from Vagrantfile, we have set 10.11.12.13 as the IP address of our VM. You can use this IP to connect to CUBRID from CUBRID Query Browser or CUBRID Manager administration tools.

To test if Apache was successfully installed, navigate to http://10.11.12.13 in your browser. You should see Apache's default "It works!" message.

Connecting to a demodb database

Recipe: demodb

Since, in Vagrantfile we have asked Chef Solo to install the demodb database, you may want to test your first database connection with it. The default database username is dba with an empty ('') password.

Testing PHP and PDO drivers

Recipe: pdo_cubrid
Recipe: php_driver

Run the following command to see if CUBRID PHP and PDO driver have been successfully installed.

$ pecl list
Installed packages, channel pecl.php.net:
=========================================
Package    Version    State
CUBRID     9.0.0.0001 stable
PDO_CUBRID 9.0.0.0001 stable

Testing the Python driver

Recipe: python_driver

Run the following command inside your VM to see if CUBRID Python driver has been successfully installed.

$ pip freeze
CUBRID-Python==9.0.0.0001

Testing the Perl driver

Recipe: perl_driver

Run the following command inside your VM to see if CUBRID Perl driver has been successfully installed.

$ cpan -l
DBD::cubrid               9.0.0.0001 9.000000001  CUBRID/DBD-cubrid-9.0.0.0001.tar.gz

Testing CUBRID Web Manager

Recipe: web_manager

If you added web_manager recipe, you can access CUBRID Web Manager at https://10.11.12.13:8282. Notice HTTPS and 8282 port. The default username and password to connect to CUBRID Manager Server are admin/admin. Once you login for the first time, CWM will prompt you to change the password. Visit CWM Wiki for more information and tutorials.

Establish SSH connection

You can connect to this VirtualBox VM using a shortcut command like:

$ vagrant ssh

That's all! It will login under vagrant user automatically. You will have full access to the underlying OS, and can perform sudo operations with no password.

Stop VM

To gracefully power off the VM, run the following command:

$ vagrant halt

Start VM

To start the VM, run the same command we ran to bring up this VM.

$ vagrant up

Change Vagrantfile configurations

When you had enough time to play with this VM, you may now want to extend it by installing additional software, or changing the host IP, forwarding host ports to guest ports, or doing lots of other things. Once you have made changes, you need to reload your VM.

$ vagrant reload

This will simply reload your VM with the new configurations, new software, etc. If some of the software is already installed during the previous boot, Vagrant will not skip them. So, this process is relatively quick than building VM from scratch.

Delete VM

When you are done playing with this VM, you may finally decide to delete it. You can do this by running the following command:

$ vagrant destroy

Next time you hit vagrant up command, it will rebuild the VM from ground up.

Conclusion

Now you're ready to develop your applications based on CUBRID Database. At any time, you can clone this project, including the Vagrantfile and cookbooks directory, and start up a fresh VM with different versions of CUBRID.

We have create two more related tutorials where you can learn how to create multiple VMs automatically with CUBRID installed on each of them and configure CUBRID HA and CUBRID SHARD. Refer to these tutorials.

[Configure CUBRID HA with Vagrant and Chef Cookbook under 4 minutes]
[Configure CUBRID SHARD with Vagrant and Chef Cookbook under 2 minutes]

If you have questions, feel free to ask at CUBRID Q&A site, forum, our Facebook page, or Twitter.

If you have issues or feature requests to cubrid-cookbook, create a new issue at its Github repo.

Install CUBRID remotely with knife-solo and Chef Cookbook

2013-02-12T00:17:38-08:00

This tutorial is a part of CUBRID Chef Cookbook series where I show how to install CUBRID Database, its drivers and tools, and configure High-Availability and Database Sharding with a single command.

Unlike in previuos tutorials, in this tutorial I will not use Vagrant. Instead, I will show how to install CUBRID on a remote Linux server using knife-solo, another great command line tool which allows to cook (i.e. install) cookbooks on remote machines. It's really easy, you will see!

Requirements

A remote Linux server which you can SSH. It can be a local virtual machine.
knife-solo installed via gem or source code on your working machine.

Getting Started

I will assume that you have already created a remote Linux server which you can connect to via SSH. Therefore I will directly show how to install knife-solo on your local development machine.

Install knife-solo prerequisites

knife-solo is available in RubyGems repository, therefore it can be installed via gem. But in this tutorial we will install knife-solo from its source code because the knife-solo gem on RubyGems is old. Actually it's just because the latest code in Github has not been released yet.

To build and install knife-solo from the source code, we need gem and bundler programs. If they are already installed on your working machine, you can proceed to the next step. If they are not, you can install them as shown below.

Debian based Linux

sudo apt-get install rubygems libxslt-dev libxml2-dev unzip git
sudo gem install bundler rdoc-data
sudo rdoc-data --install

This will install gem program, XML libraries which bundler program depends on, unzip necessary to extract knife-solo source code from ZIP archive, git necessary to download cookbooks, bundler and rdoc-data gems.

RPM based Linux

sudo yum install rubygems ruby-devel libxslt-devel libxml2-devel unzip git wget
 sudo gem install bundler rdoc-data
 sudo rdoc-data --install

Build knife-solo

wget https://github.com/matschaffer/knife-solo/archive/master.zip
unzip master*
cd knife-solo-master
sudo bundle
sudo bundle exec rake install

This will download the source ZIP from knife-solo Github repo, etract it, build the source, and install the generated knife-solo gem.

Check knife-solo

Type the following command to check if knife-solo has been successfully installed. You should see something like:

~$ gem list | grep knife
knife-solo (0.2.0.pre2)

Prepare the working directory structure

Once knife-solo is ready, we go and create a directory structure where we will be working.

cd
mkdir cubrid-knife
cd cubrid-knife
knife solo init .

This will create a cubrid-knife directory in your user home directory where knife-solo will initialize the working directory. The directory structure that knife-solo will create looks as follows:

/cookbooks
/data_bags
/nodes
/roles
/site-cookbooks
solo.rb

Prepare the remote server

Once we have initialized the working directory on our local working machine, we need to prepare our remote server. For this run knife solo prepare command by specifying your remote server username and IP. In this case, my remote server username is user, and remote server IP is 192.168.85.138. By default SSH port number which knife-solo will use to connect to your remote server is 22. If it is different from the default value, you can specify it with additional -p option.

~$ knife solo prepare user@192.168.85.138
WARNING: No knife configuration file found
Bootstrapping Chef...
Enter the password for user@192.168.85.138: 
--2013-02-11 23:02:58--  https://www.opscode.com/chef/install.sh
Resolving www.opscode.com (www.opscode.com)... 184.106.28.83
Connecting to www.opscode.com (www.opscode.com)|184.106.28.83|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 6471 (6.3K) [application/x-sh]
Saving to: `install.sh'

100%[======================================>] 6,471       --.-K/s   in 0s      

2013-02-11 23:02:59 (956 MB/s) - `install.sh' saved [6471/6471]


Downloading Chef  for ubuntu...
Installing Chef 
Selecting previously unselected package chef.
(Reading database ... 24087 files and directories currently installed.)
Unpacking chef (from .../tmp.Afy1f2L1/chef__amd64.deb) ...
Setting up chef (11.2.0-1.ubuntu.11.04) ...
Thank you for installing Chef!
Generating node config 'nodes/192.168.85.138.json'...

This will:

prepare the remote Linux server by installing a Chef Client;
generate a nodes/192.168.85.138.json configuration file for this particular remote server with an empty runlist which means no cookbook will be installed until we populate the runlist manually.
```
{"run_list":[]} 
```

Download necessary cookbooks

Now we can go and download all cookbooks we want to install on our remote Linux server. In this tutorial we will install the latest version of CUBRID Database Server, PHP, Python, and Perl drivers.

cd ~/cubrid-knife
git init
git submodule add https://github.com/kadishmal/cubrid-cookbook.git cookbooks/cubrid
git submodule add https://github.com/opscode-cookbooks/build-essential.git cookbooks/build-essential
git submodule add https://github.com/opscode-cookbooks/mysql.git cookbooks/mysql
git submodule add https://github.com/opscode-cookbooks/openssl.git cookbooks/openssl
git submodule add https://github.com/opscode-cookbooks/perl.git cookbooks/perl
git submodule add https://github.com/opscode-cookbooks/php.git cookbooks/php
git submodule add https://github.com/opscode-cookbooks/python.git cookbooks/python
git submodule add https://github.com/opscode-cookbooks/yum.git cookbooks/yum
git submodule add https://github.com/opscode-cookbooks/xml.git cookbooks/xml

This will clone each cookbook under cookbooks/ directory.

Choose which cookbook to install

Once we have downloaded the cookbook, we need to tell knife-solo that we want to cook a particular cookbook. For this we need to add the cookbook name to the runlist. Edit the nodes/192.168.85.138.json file as shown below.

{"run_list":[
  "cubrid",
  "cubrid::demodb",
  "cubrid::pdo_cubrid",
  "cubrid::perl_driver",
  "cubrid::php_driver",
  "cubrid::python_driver",
  "cubrid::web_manager"
]}

This will tell knife-solo, which will tell to Chef installed on the remote server, to install CUBRID Database, its demodb database, PHP/PDO, Perl, and Python drivers, as well as CUBRID Web Manager, all from cubrid cookbook that we have downloaded.

Cook the remote server

Now as we are ready to cook our remote Linux server, let's do it.

~$ knife solo cook user@192.168.85.138
Checking Chef version...
Enter the password for user@192.168.85.138: 
user@192.168.85.138's password: 
user@192.168.85.138's password: 
user@192.168.85.138's password: 

Starting Chef Client, version 11.2.0
Compiling Cookbooks...
Converging 58 resources
...
Chef Client finished, 48 resources updated

Bingo! You have installed CUBRID and all the necessary drivers and even a Web Manager on your remote server.

Testing CUBRID Web Manager

Let's access CUBRID Web Manager at https://192.168.85.138:8282. Notice HTTPS and 8282 port. The default username and password to connect to CUBRID Manager Server are admin/admin. Once you login for the first time, CWM will prompt you to change the password. Visit CWM Wiki for more information and tutorials.

Questions?

If you have questions, feel free to ask at CUBRID Q&A site, forum, our Facebook page, Twitter, or online chat.

If you have issues or feature requests to cubrid-cookbook, create a new issue at its Github repo.

Change database user password

2012-05-29T21:10:35-07:00

To change your database user password, execute the following SQL.

ALTER USER user_name PASSWORD 'any_password_here_in_single_quotes';

You may execute it using CSQL command line SQL Interpreter or CUBRID Manager.

CSQL Example

Before changing the password, make sure your database has been [Start or Autostart CUBRID Database|started].

~$ csql -u dba demodb
csql> ALTER USER dba PASSWORD 'my_new_pass';
Current transaction has been committed.
1 command(s) successfully processed.
csql>

Remember that in order to change a user password you need to be logged in as an admin user (or a user who has a permission to change a user password). In our case, dba is an admin user. Otherwise, you will get an error saying "UDPATE authorization failure".

Alternatively, you can set the database user password at the database creation time.

[Solved] Chef: NameError: Cannot find a resource for converge_by on centos

2013-02-05T23:57:05-08:00

I was testing CUBRID Chef Cookbook on CentOS 6.3 today using Vagrant tool when I encountered the following error with Chef 10.12.0:

FATAL: NameError: python_pip[virtualenv] (python::virtualenv line 23) had an error: NameError: Cannot find a resource for converge_by on centos version 6.3

Solution

The solution to this problem occured to be trivial: converge_by resource has been introduced quite recently in a newer version of Chef. Therefore a simple update to Chef solved this problem.

sudo gem update chef ohai --no-ri --no-rdoc

And the error is gone!

Error Messages and Troubleshooting

2012-04-12T04:45:07-07:00

No	error message	state	component	version	cause(extract posting)	solution
1	ERROR [CA001] [CUBRID][CUBRID ODBC Driver]Transaction(index1, dba@localhost\|20383) has been unilaterally aborted by the system.	During Inserting records	Engine	CUBRID 2008	Occurs when DB server is forcely terminated.	There are various reasons which terminated server or causes disconnection. (EX: deadlock) Please check the logs if a problem occurs at the moment.
2	-2003 Cannot communicate with broker	When CUBRID Manager's JDBC version is incompatible with DB server version.	CM	CUBRID 2008 R2.2	JDBC driver should be same as server version	choose aright version of JDBC driver in CUBRID Manager and retry to connect
3	A network read/write error occurred for socket 5 associated with your transaction (index 2, root@master\|17705)	Cannot start server after deleting 170,000 rows by DELETE ALL statement.	Engine	CUBRID 2008	When DB process is terminated abnormally, the previous logs remains still unclearly.	On the console, run the following commands. 1) csql -S DB_NAME 2) cubrid emergency_patchlog DB_NAME 3) cubrid emergency_patchlog -r DB_NAME
4	serial object delete error	Cannot DROP SERIAL when deleting a table.	Engine	CUBRID 2008 R3.0	A bug was found in CUBRID 8.3.0 or lower versions. SERIAL should be dropped with a table together.	A bug fixed. As long as you are an owner of objects, SERIALs drops when deleting a table.
5	Cannot connect to master server... bad file descriptor	On Windows7 32 bits, cannot start DB server.	Engine	CUBRID 2008	Among cubrid service, cub_master seems not running	On the console, 1) cubrid service stop 2) cubrid service start See if every process is on. 3) cubrid server start See if a process is not running, see the log file (_master) in CUBRID/log/ directory and server logs( DB_NAME) in CUBRID/log/server directory
6	C:\CUBRID\databases\\backup\_backup_lv0 is a backup of database created on Mon Apr 11 15:41:49 2011 instead of given database C:\CUBRID\DATABA~1\\ created on Wed Apr 20 16:13:47 2011	After DB backup in the old version, I removed CUBRID in the system. Then I installed CUBRID server and tried restoring.	Engine	CUBRID 2008 R3.1	The error occurs when restoring a backup file which cannot read in a new version.	Althugh you have only DB backup file without DB and other files, you can restore only when DB server version and file directory is as same as old environment.
7	ERROR -673 0 1 Your connection to the server has been closed since the server is going down immediately	After creating a DB, I cannot create a table even if I logged-in	Engine	CUBRID 2008 R3.1	This error occurs when the DB server is terminated.	On the console, run a command. cubrid server start
8	@ cubrid master start ++ cubrid master start: success @ cubrid broker start ++ cubrid broker is running. @ cubrid manager server start bind: Address already in use bind: Address already in use ++ cubrid manager server start: fail	I messed up installation. I installed CUBRID new version while curbid service is on runnning.	Engine	CUBRID 2008 R2.2	Linux account that you installed a old CUBRID is not same as that of a new version.	On the console, run a following command. ps -ef \| grep cub_ Then kill cubridrelated processes.
		.
10	Unable to mount disk volume "directory/file(lgar)"... . No such file or directory	lgar files are not deleted after cubrid backup -r option. The error occurs when trying backup after moving log files.	Engine	CUBRID 2008	In When DB process is terminated abnormally, the previous logs remains still unclearly.	On the console, 1) cubrid service stop 2) cubrid service start See if every process is on. 3) cubrid server start See if a process is not running, see the log file (_master) in CUBRID/log/ directory and server logs( DB_NAME) in CUBRID/log/server directory
11	SqlMapClient operation; uncategorized SQLException for SQL []; SQL state [null]; error code [-670]	When a specific method is executed, an error occurs	Framework	-	Error code: 670 is "Operation would have caused one or more unique constraint violations"	A certain SQL violates UNIQUE constraints. Search SQL causing -670 error under $CUBRID/log/broker/sql_log/
12	-2147467259 : Your transaction (index 23, dba@localhost\|28478) has been unilaterally aborted by the system.	Engine	CUBRID 2008 3.0	Occurs when DB server is forcely terminated.	There are various reasons which terminated server or causes disconnection. (EX: deadlock) Avoid deadlock with short transaction and low isolation level.
13	Attempt to execute the query when not all the parameters are binded	During SELECT execution, an error occurs.	Engine	CUBRID 2008	Occurs when the number of parameters are not matched to your binding values.	When binding values, it should one to one match to parameters in the SQL.
14	ERROR -33 5 47 Last out of space notification for volumes with temporary data as the main storage purpose. Total number of pages = 20480, total number of free pages = -25	I have found an error in the server log file. The fast query turns slower all of sudden.	Engine	-	DB temp volume is out of space.	Temp volume is mostly used to execute JOIN, Sorting. Run a following command on the console. cubrid addvoldb -p temp DB_NAME
15	Server no longer responding.... Resource temporarily unavailable *** Unable to mount log disk volume/file "/data/cubrid/db_svr2/db_lgat".... No such file or directory Your connection to the server has been closed since the server is going down immediately. CLIENT = svr1:copylogdb(21448), EID = 2 Has been interrupted. CLIENT = svr1:copylogdb(21448), EID = 3 Server communications error: connection status: CONN_CLOSING	After upgrading to 8.3.1, cannot connect to DB.	Engine, HA	CUBRID 2008 R3.1	In the conf, there is <common> section and <db> section. Your server conf file says log_page_buffer paraeter is located in <db> section however it is supposed to be <common> section. Since HA process cannot read <db> section parameters, they couldn't boot up and the master server stays as "to-be-active' state.	Edit cubrid.conf file. Put log_page_buffer parameter to <common> section and then restart server.
16	Can't start up the distributor database. ############ Stopped by error... ############ Cannot make connection to master server. getting local host by name for host "TEST-S". Host not found.	Engine, HA	CUBRID 2008 3.0	The host names belonging to HA nodes shouldbe configured correctly.	See the /etc/hosts file if host name is correctly registered.
17	This object is in a zombie state	Occurs in the ASP application having a logic of loop 1 loop 2 end end	Engine, ASP	CUBRID 2008 3.1 patch1	Error occurs when the 1st query is closed automatically when the 2nd query is running in the nested query.	Set AutoCommit=False and create 2 connections to execute a query on each.
18	cubrid.jdbc.driver.CUBRIDException: Attempt to access a closed ResultSet. at cubrid.jdbc.driver.CUBRIDResultSet.checkIsOpen(CUBRIDResultSet.java:1648) at cubrid.jdbc.driver.CUBRIDResultSet.findColumn(CUBRIDResultSet.java:670) at cubrid.jdbc.driver.CUBRIDResultSet.getString(CUBRIDResultSet.java:559) at jeemin.Test1.main(Test1.java:28)	Occurs in the JDBC application having a loop	Engine, Java	CUBRID 2008 R2	Error occurs when the 1st ResultSet is closed in the loop	When using a nested query, set connection.setAutoCommit(false)
19	-899 Stored procedure execute error: java.lang.NullPointerException	Occurs when executing Java Stored Procedure.	Engine, Java Store Procedure	CUBRID 2008	Procedure information should match to class file and function names.	Check if a simple typo exists in your procedure, comparing with class files and function names.
20	Java VM is not running	Occurs when executing Java Stored Procedure.	Engine, Java Store Procedure	CUBRID 2008	JAVA VM is not running. See if jvm.dll setting.	See JAVA_HOME and PATH settings if jvm.dll is in PATH. After setting, you should restart cubrid. cubrid service stop cubrid service start
21	Warning: Error: DBMS, 0, Unknown DBMS error	I can connect to DB via CUBRID Manager, but not my PHP application.	Engine, PHP	CUBRID 2008	Error occurs when cannot conenct to a DB.	Start a DB and see if your connection information9broker IP and port) is correct in your PHP.
22	Warning -> Current user(0) does not match CUBRID user(501). Server may have unpredictable behavior. Continuing... Warning -> Current user(0) does not match CUBRID user(501). Server may have unpredictable behavior. Continuing... Error : Server[pid=2546] already running. Error : Server[pid=2549] already running. ++ cubrid manager server start: fail	When I start cubrid manager, error occurred.	CM	CUBRID 2008 3.0	See the Linux account and CUBRID installation account with permission.	Check the user account info of "cub_" processes and set a right user permission.
23	. Failed to connect to database server, 'UPS', on the followiong host(s): localhost compactdb : Failed to connect to database server, 'UPS', on the following host(s):localhost.	When run compactdb via CUBRID Manager, it failed.	CM	CUBRID 2008 3.1 patch 1	Bug only in CUBRID Manager. You can run command on console.	If DB is offline, cubrid compactdb -S <DB_NAME> If DB is online, cubrid compactdb <DB_NAME>
24	Cannot get a connection. Check the status of broker and DB server.	After I upgraded DB server vesion, DB Log-in failed via CUBRID Manager	CM	CUBRID 2008 R3.1 1002	JDBC version used in CUBRID Manager should be same as DB server's version.	Find a right version of JDBC and set it in CM. http://ftp.cubrid.org/CUBRID_Drivers/JDBC_Driver/
25	Cannot get a connection. Check the status of broker and DB server.	I can log-in to DB via local CM however I cannot connect to the DB via a remote CM.	CM	CUBRID 2008	CM in a remote cannot get thru DB server. See the Firewall in CUBRID DB server host.	Disable or re-set the firewall and check CUBRID and CUBRD Manager using ports are all open.
26	PHP Startup: Unable to load dynamic library '/usr/lib/php/modules/cubrid.so' - libcascci.so.8: cannot open shared object file: No such file or directory in Unknown on line 0	I cannot load the PHP module successfully.	PHP	-	If you build PHP module, Linux user should be as same as CUBRID Installation user.	See the tutorial how to build PHP module, it is easy to use PECL http://www.cubrid.org/wiki_apis/entry/php_api_build_guide
27	NativeException: java.lang.ClassNotFoundException: cubrid/jdbc/driver/CUBRIDDriver	Class.forName("cubrid.jdbc.driver.CUBRIDDriver") cannot find a driver.	Java	CUBRID 2008 R2.2.3002	See if JAVA class path is correctly configured.	$ CUBRID / jdbc / cubrid_jdbc.jar should be set to CLASSPATH. See the manual.
28	PHP Warning: Unknown(): Unable to load dynamic library './cubird.so' - ./cubird.so: cannot open shared object file: No such file or directory in Unknown on line 0	Doesn't work with CUBRID PHP driver.	PHP	CUBRID 2008	1. See if extension_dir is correctly configured in the php.ini. 2. CUBRID php module should link with libcascci.so (CCI driver). Your PHP cannot find CCI in the system	1. extension_dir should address "cubrid.so" file. 2. cubrid.so refers to libcascci.so. See if cubrid.so links with libcascci.so by "ldd cubrid.so" command
29	main.c:(.text+0x69): undefined reference to `cci_connect_3_0'	When building the source, error occurs.	CCI	CUBRID 2008 R3.1	The option for CCI driver can be added	Use the option, -L$CUBRID/lib-lcascci
30	/usr/bin/ld: cannot find -lcascci	When running $ gcc -L$CUBRID/lib-lcascci a.c -o a, cannot find CCI library	CCI	CUBRID 2008 R3.1	Error occurs since the library was not found.	1) Check $CUBRID/lib directory if libcascci.so exists. 2) Check if CUBRID environment variables are correctly configured.
31	Attempt to access a closed ResultSet(PreparedStatement)	To keep using a ResultSet in the following queries, error occurs.	Engine	CUBRID 2008	ResultSet to fetch has been already closed.	The prior ResultSet was closed because cutoCommit is true. If you re-use the 1st ResultSet, change the setting to "False" and add Commit/Rollback in the end for each transaction.
32	PHP Startup: Unable to load dynamic library	I have already set php.ini, but I cannot execute queries.	PHP	CUBRID 2008 R4.0	*.dll file cannot be loaded.	Check your PHP version and OS version. In the directory, only a right version of PHP driver should exist. http://ftp.cubrid.org/CUBRID_Drivers/PHP_Driver/
33	Backup is already running. Backup cannot be run by two processes.	When trying DB backup in CURBID Manager, error occurs.	Windows 2008	CUBRID 2008 R2.2	While DB bakcup is already running, you cannot perform backup at the same time.	1. Check if other DBA or automated script has already run DB backup. 2. If not, kill a prior backup process.
34	Cannot create enough threads for 'max_clients=100'.	In cubrid.conf, I configured java_stored_procedure=yes to use Java stored procedure. Then, error occurs.	CentOS	CUBRID 2008 R4.0	In the 32bit server, it can possibly limit due to lack of memory.	1. Change the server to 64bit 2. Run a command to limit memory stack size: ulmit -s 5120 3. Set max_clients in cubrid.conf to lower value.
35	mktemp: invalid option -- p Usage: mktemp [-d] [-q] [-u] template tar: ../CUBRID-product.tar: Cannot open: tar: Error is not recoverable: exiting now	During CUBRID DB server installation, error occurs.	Linux	CUBRID 2008 R4.1	In your system, there is no mktemp library.	Check if the library is installed in your system with a command: pm -qa \| grep mktemp If not exists, add or upgrade your OS.
36	configure: error: /home/cubrid/CUBRID/lib/libcascci.so Please set CUBRID base install dir with --with-cubrid=DIR	During CUBRID PHP driver installation, error occurs.	CentOS	CUBRID 2008 R4.1	OS bit, CUBRID bit, PHP bit mismatches.	Chekc if the bit of OS / CUBRID / PHP is all same. http://ftp.cubrid.org/

Configure CUBRID HA with Vagrant and Chef Cookbook under 4 minutes

2013-01-04T00:19:00-08:00

This is a follow up tutorial for [Create a CUBRID Database VM with Vagrant and Chef Cookbook under 5 minutes]. Therefore I will assume you have read the previous tutorial as this one will be a continuation of it.

In this tutorial I will show how to create multiple VMs automatically with CUBRID installed on each of them and have them configured in one HA group. I will tell you that with Vagrant and Chef Cookbook it is as easy as running vagrant up and waiting for 4-5 minutes until everything gets set up.

Requirements

Requirements are the same as in the first tutorial. Refer to it for details. In short, you need VirtualBox and Vagrant installed.

Vagrantfile

If you have not already downloaded cubrid-vagrant-1.5.1.tar.gz (211KB), do it now (or check the latest version from Sf.net repo). You will find everything ready for you in that archive. Refer to the [Create a CUBRID Database VM with Vagrant and Chef Cookbook under 5 minutes |previous tutorial] for details on what is included.

Now for this tutorial to configure CUBRID HA on multiple VMs, we will add a few more configuration options to our Vagrantfile which comes by default in that archive.

# -*- mode: ruby -*-
# vi: set ft=ruby :

Vagrant::Config.run do |config|
  config.vm.box_url = "http://files.vagrantup.com/precise64.box"
  config.vm.box = "precise64" # Ubuntu 12.04 x64

  config.vm.define :node1 do |node1_config|
    node1_config.vm.host_name = "node1"
    node1_config.vm.network :hostonly, "10.11.12.13"
  end

  config.vm.define :node2 do |node2_config|
    node2_config.vm.host_name = "node2"
    node2_config.vm.network :hostonly, "10.11.12.14"
  end

  config.vm.customize ["modifyvm", :id, "--memory", 800]

  config.vm.provision :chef_solo do |chef|
    chef.cookbooks_path = "cookbooks"

    chef.json = {
        "cubrid" => {
            "version" => "8.4.3",
            "ha_dbs" => ["ha_test_db"],
            "ha_hosts" => {"node1" => "10.11.12.13", "node2" => "10.11.12.14"}
        }
    }

    chef.add_recipe "cubrid"
    chef.add_recipe "cubrid::ha"
  end
end

I have removed the comments this time so that you can see the real code more prominently.

Number of VMs

The first thing to take care in this scenario is to define how many VMs (hosts) we would like to run in this HA environment. No matter how many, each host will run an independent CUBRID Server node. Later all these hosts will join in one HA group and provide auto failover between themselves.

In the above Vagrantfile you can notice the following lines:

config.vm.define :node1 do |node1_config|
   node1_config.vm.host_name = "node1"
   node1_config.vm.network :hostonly, "10.11.12.13"
 end

 config.vm.define :node2 do |node2_config|
   node2_config.vm.host_name = "node2"
   node2_config.vm.network :hostonly, "10.11.12.14"
 end

This means that we want Vagrant to build for us two VMs. The first VM should be distinguished by node1 name and should be assigned 10.11.12.13 IP address. The second VM will have a hostname node2 with an IP 10.11.12.14. In this example both hostname and IP are arbitrary, i.e. you can set your own, but you should remember to set IP within the same netmask (refer to Multiple Networks in Vagrant for details).

This is how you define the number of VMs to start up. The first VM which gets configured and started will become "master" in CUBRID HA, while other VM hosts will become "slaves".

VM memory size

In this example we set each VM to have 800MB RAM. This is enough, though you can set lower or higher values.

config.vm.customize ["modifyvm", :id, "--memory", 800]

If you need to have different memory on each VM, you can do so by specifying this same property when you define each VM.

Configure CUBRID HA

chef.json = {
    "cubrid" => {
        "version" => "8.4.3",
        "ha_dbs" => ["ha_test_db"],
        "ha_hosts" => {"node1" => "10.11.12.13", "node2" => "10.11.12.14"}
    }
}

chef.add_recipe "cubrid"
chef.add_recipe "cubrid::ha"

First of all, you need to add "cubrid::ha" recipe to have CUBRID HA configured.
Second, you need to provide a list of hosts and IPs which should join the same HA group. For this override ha_hosts attribute. These hosts and IPs must be identical to those you have defined for each VM above.
Then, optionally, you can override ha_dbs attribute by providing an array of database names to create and sync in HA. By default it will create one database called testdb.
Also, you can optionally override ha_group attribute which defaults to cubrid. This is the HA group all hosts will join. You can set any arbitrary value.

That is all you need to configure CUBRID HA. Now let's go and bring up CUBRID HA.

Vagrant Box

I will assume that you have already added precise64 (Ubuntu 12.04 LTS x64) Vagrant box. If you haven't, see the [Create a CUBRID Database VM with Vagrant and Chef Cookbook under 5 minutes|previous tutorial].

Start Up Vagrant

Run the following command to start Vagrant:

$ vagrant up

Wait some 4-5 minutes and you will have your VMs up and running in HA environment.

Test CUBRID HA

Validate CUBRID HA

Let's first validate and see if CUBRID HA has been properly configured.

Open SSH connection

For this we will open SSH connection and login to the first node1 VM. Remember, the first VM which got started becomes master while the rest become slaves.

$ vagrant ssh node1
Welcome to Ubuntu 12.04 LTS (GNU/Linux 3.2.0-23-generic x86_64)

 * Documentation:  https://help.ubuntu.com/

100 packages can be updated.
50 updates are security updates.

Welcome to your Vagrant-built virtual machine.
Last login: Thu Jan  3 06:46:49 2013 from 10.0.2.2
vagrant@node1:~$

To connect to other nodes, simply change the node name as:

$ vagrant ssh node2

Check CUBRID Service status

vagrant@node1:~$ cubrid service status
@ cubrid master status
++ cubrid master is running.
@ cubrid server status
 HA-Server ha_test_db (rel 8.4, pid 1423)
@ cubrid broker status
  NAME           PID  PORT  AS  JQ      REQ  TPS  QPS    LONG-T    LONG-Q  ERR-Q
================================================================================
* query_editor  1641 30000   5   0        0    0    0    0/60.0    0/60.0      0
* broker1       1651 33000   5   0        0    0    0    0/60.0    0/60.0      0
@ cubrid manager server status
++ cubrid manager server is running.
vagrant@node1:~$

We can notice that CUBRID Service is running and our ha_test_db database has been successfully started. You should see the same result if you execute this command on other nodes.

Check CUBRID Heartbeat status

vagrant@node1:~$ cubrid heartbeat status
@ cubrid heartbeat list

 HA-Node Info (current node1, state master)
   Node node2 (priority 2, state slave)
   Node node1 (priority 1, state master)


 HA-Process Info (master 1224, state master)
   Applylogdb ha_test_db@localhost:/opt/cubrid/databases/ha_test_db_node2 (pid 1559, state registered)
   Copylogdb ha_test_db@node2:/opt/cubrid/databases/ha_test_db_node2 (pid 1557, state registered)
   Server ha_test_db (pid 1230, state registered_and_active)

vagrant@node1:~$

Notice that our node1 states that it is master while node2 is slave.
We can also notice that Applylogdb and Copylogdb HA processes have been successfully started.

These are two main indicators that CUBRID Heartbeat is running.

If we run the same command on node2, we will see a little bit different picture:

vagrant@node2:~$ cubrid heartbeat status
@ cubrid heartbeat list

 HA-Node Info (current node2, state slave)
   Node node2 (priority 2, state slave)
   Node node1 (priority 1, state master)


 HA-Process Info (master 1257, state slave)
   Applylogdb ha_test_db@localhost:/opt/cubrid/databases/ha_test_db_node1 (pid 1592, state registered)
   Copylogdb ha_test_db@node1:/opt/cubrid/databases/ha_test_db_node1 (pid 1590, state registered)
   Server ha_test_db (pid 1263, state registered)

vagrant@node2:~$

Check HA mode

As a final stroke, let's check the HA mode of each node.

vagrant@node1:~$ cubrid changemode ha_test_db@localhost
The server `ha_test_db@localhost''s current HA running mode is active.

We can see that the master node1 is in active mode. For other options, refer to Servers in CUBRID HA.

When we run the same command on the slave node, we will see that it is in standby mode:

vagrant@node2:~$ cubrid changemode ha_test_db@localhost
The server `ha_test_db@localhost''s current HA running mode is standby.

Insert sample data

To confirm that replication works in CUBRID HA, let's create a sample table and insert some data.

CREATE TABLE ha_table(
    id INTEGER AUTO_INCREMENT PRIMARY KEY,
    f_name VARCHAR(20) NOT NULL
);

INSERT INTO ha_table (f_name) VALUES ('Zorro'), ('Guppy'), ('Watchman');

Execute these queries in your favorite tool. You can use CUBRID Manager, CUBRID Query Browser administration tools, or CSQL command line tool. In this example I will use CSQL on our master node1:

vagrant@node1:~$ csql -u dba ha_test_db@localhost

CUBRID SQL Interpreter


Type `;help' for help messages.

csql> CREATE TABLE ha_table(
csql>     id INTEGER AUTO_INCREMENT PRIMARY KEY,
csql>     f_name VARCHAR(20) NOT NULL
csql> );
SQL statement execution time:     0.002845 sec

Current transaction has been committed.

1 command(s) successfully processed.
csql> 
csql> INSERT INTO ha_table (f_name) VALUES ('Zorro'), ('Guppy'), ('Watchman');

3 rows affected.
SQL statement execution time:     0.001594 sec

Current transaction has been committed.

1 command(s) successfully processed.
csql> SHOW TABLES;

=== <Result of SELECT Command in Line 1> ===

  Tables_in_ha_test_db@localhost
======================
  'ha_table'          


1 rows selected.
SQL statement execution time:     0.018776 sec

Current transaction has been committed.

1 command(s) successfully processed.
csql> SELECT * FROM ha_table;

=== <Result of SELECT Command in Line 1> ===

           id  f_name              
===================================
            1  'Zorro'             
            2  'Guppy'             
            3  'Watchman'          


3 rows selected.
SQL statement execution time:     0.003838 sec

Current transaction has been committed.

1 command(s) successfully processed.
csql> ;ex
vagrant@node1:~$

We can notice that all queries have been successfully executed on master node1.

Now, let's see if these statements have been applied to slave node2.

vagrant@node2:~$ csql -u dba ha_test_db@localhost

CUBRID SQL Interpreter


Type `;help' for help messages.

csql> SHOW TABLES;

=== <Result of SELECT Command in Line 1> ===

  Tables_in_ha_test_db@localhost
======================
  'ha_table'          


1 rows selected.
SQL statement execution time:     0.016050 sec

Current transaction has been committed.

1 command(s) successfully processed.
csql> SELECT * FROM ha_table;

=== <Result of SELECT Command in Line 1> ===

           id  f_name              
===================================
            1  'Zorro'             
            2  'Guppy'             
            3  'Watchman'          


3 rows selected.
SQL statement execution time:     0.004936 sec

Current transaction has been committed.

1 command(s) successfully processed.
csql> ;ex
vagrant@node1:~$

We can see that all statements are successfully replicated on the slave node2.

Shutdown master node to initiate failover

Now, let's see if master role will successfully be delegated from node1 to node2 as a result of a failover. For this to work we will manually power off our node1 VM.

$ vagrant halt node1

Then check again the heartbeat status on node2.

vagrant@node2:~$ cubrid heartbeat status
@ cubrid heartbeat list

 HA-Node Info (current node2, state master)
   Node node2 (priority 2, state master)
   Node node1 (priority 1, state unknown)


 HA-Process Info (master 1190, state master)
   Applylogdb ha_test_db@localhost:/opt/cubrid/databases/ha_test_db_node1 (pid 1525, state registered)
   Copylogdb ha_test_db@node1:/opt/cubrid/databases/ha_test_db_node1 (pid 1523, state registered)
   Server ha_test_db (pid 1196, state registered_and_active)

vagrant@node2:~$

Bingo! Now node2 is master, while the state of node1 is unknown.

Revive node1 and put it to standby (slave)

Now let's revive node1 which was previously powered off, then check its heartbeat status.

~$ vagrant up node1
....
~$ vagrant ssh node1
....
vagrant@node1:~$ cubrid heartbeat status
@ cubrid heartbeat list

 HA-Node Info (current node1, state slave)
   Node node2 (priority 2, state master)
   Node node1 (priority 1, state slave)


 HA-Process Info (master 1613, state slave)
   Applylogdb ha_test_db@localhost:/opt/cubrid/databases/ha_test_db_node2 (pid 1948, state registered)
   Copylogdb ha_test_db@node2:/opt/cubrid/databases/ha_test_db_node2 (pid 1946, state registered)
   Server ha_test_db (pid 1619, state registered)

vagrant@node1:~$

Correct! node1 became slave in our HA group.

Conclusion

In this tutorial you have learnt how to create multiple VMs automatically with CUBRID installed on each of them and have them configured in one HA group. As you can see, Vagrant along with Chef cookbook allow us to work with CUBRID Database and other software very easily. It is so much convenient and saves so much of our time. Now creating a development environment is no more painful.

Now as you know how to setup CUBRID HA environment, you can proceed to configuring CUBRID SHARD multi VM environment. Refer to:

[Configure CUBRID SHARD with Vagrant and Chef Cookbook under 2 minutes]

If you have questions, feel free to ask at CUBRID Q&A site, forum, our Facebook page, or Twitter. If you have issues or feature requests to cubrid-cookbook, create a new issue at its Github repo.

Configure CUBRID SHARD with Vagrant and Chef Cookbook under 2 minutes

2013-01-15T00:23:23-08:00

This is the third tutorial in Vagrant/Chef series where I would like to show how to install CUBRID Database in multi VM environment and automatically configure the database sharding. If you haven't read the previous tutorials, at least read [Create a CUBRID Database VM with Vagrant and Chef Cookbook under 5 minutes] to learn about Vagrant and Chef cookbook we will be using in this tutorial.

In this tutorial you will learn how to create multiple VMs automatically with CUBRID installed on each of them and configured CUBRID SHARD for database sharding. I will tell you that with Vagrant and Chef Cookbook it is as easy as running vagrant up and waiting for less than 2 minutes until everything gets set up.

If you want to learn more about CUBRID SHARD refer to Database Sharding the Right Way: Easy, Reliable, and Open source we have presented at HighLoad++ 2012 conference.

Requirements

Requirements are the same as in the first tutorial. Refer to it for details. In short, you need VirtualBox and Vagrant installed.

Vagrantfile

If you have not already downloaded cubrid-vagrant-1.7.0.tar.gz (226KB), do it now (or check the latest version from Sf.net repo). You will find everything ready for you in that archive. Refer to the [Create a CUBRID Database VM with Vagrant and Chef Cookbook under 5 minutes |previous tutorial] for details on what is included.

Now for this tutorial to configure CUBRID HA on multiple VMs, we will add a few more configuration options to our Vagrantfile which comes by default in that archive.

# -*- mode: ruby -*-
# vi: set ft=ruby :

Vagrant::Config.run do |config|
  #config.vm.box_url = "http://files.vagrantup.com/precise64.box"
  config.vm.box = "precise64" # Ubuntu 12.04 x64

  config.vm.define :node1 do |node1_config|
    node1_config.vm.host_name = "node1"
    node1_config.vm.network :hostonly, "10.11.12.13"
  end

  config.vm.define :node2 do |node2_config|
    node2_config.vm.host_name = "node2"
    node2_config.vm.network :hostonly, "10.11.12.14"
  end

  config.vm.customize [!"modifyvm", :id, "--memory", 800]

  config.vm.provision :chef_solo do |chef|
    chef.cookbooks_path = "cookbooks"

    chef.json = {
        "cubrid" => {
            "version" => "8.4.3",

            "shard_db" => "sharddb",
            "shard_hosts" => [!
              {"node1" => "10.11.12.13"},
              {"node2" => "10.11.12.14"}
            ]
        }
    }

    chef.add_recipe "cubrid"
    chef.add_recipe "cubrid::shard"
  end
end

I have removed the comments this time so that you can see the real code more prominently. In the Vagrantfile inside the archive you can see all the comments.

Number of VMs

The first thing to take care in this scenario, just like when [Configure CUBRID HA with Vagrant and Chef Cookbook under 4 minutes|configuring HA] is to define how many VMs (hosts) we would like to run in this CUBRID SHARD environment. No matter how many, each host will run an independent CUBRID Server node and have a database which will serve as one of the shards of the "single logical" database.

In the above Vagrantfile you can notice the following lines:

config.vm.define :node1 do |node1_config|
   node1_config.vm.host_name = "node1"
   node1_config.vm.network :hostonly, "10.11.12.13"
 end

 config.vm.define :node2 do |node2_config|
   node2_config.vm.host_name = "node2"
   node2_config.vm.network :hostonly, "10.11.12.14"
 end

This is how you define the number of VMs to start up. Unlike with [Configure CUBRID HA with Vagrant and Chef Cookbook under 4 minutes|HA configuration] where the first VM which gets started becomes a "master" node, in CUBRID SHARD the last node to be configured will start the CUBRID SHARD Service and serve as a SHARD Broker. This is the case because in order to start the SHARD Service all shard nodes must be up. Thus, configuring starting the SHARD Service on the last node will ensure us that all previous nodes are up.

VM memory size

In this example we set each VM to have 800MB RAM. This is enough, though you can set lower or higher values.

config.vm.customize [!"modifyvm", :id, "--memory", 800]

If you need to have different memory on each VM, you can do so by specifying this same property when you define each VM.

Configure CUBRID SHARD

chef.json = {
    "cubrid" => {
        "version" => "8.4.3",

        "shard_db" => "sharddb",
        "shard_hosts" => [!
          {"node1" => "10.11.12.13"},
          {"node2" => "10.11.12.14"}
        ]
    }
}

chef.add_recipe "cubrid"
chef.add_recipe "cubrid::shard"

First of all, you need to add "cubrid::shard" recipe to have CUBRID SHARD configured.
Second, you need to provide a database name via shard_db attribute which you want to create and have it shared among all nodes.
Third, you need to provide a list of hosts and IPs where each database shard will be located. For this override shard_hosts attribute. These hosts and IPs must be identical to those you have defined for each VM above.
You can optionally override shard_broker_port attribute which defaults to 45011.
Also optionally you can specify shard_user and shard_user_password attributes if you want to create a specific database user for your sharded database. By default, a shard user will be created with shard123 password.

That is all you need to configure CUBRID SHARD. Now let's go and bring up our CUBRID SHARD.

Vagrant Box

Start Up Vagrant

Run the following command to start Vagrant:

$ vagrant up

Wait about 2 minutes and you will have your VMs up and running in CUBRID SHARD configured.

Test CUBRID SHARD

Validate CUBRID SHARD

Let's first validate and see if CUBRID SHARD has been properly configured.

Open SSH connection

For this we will open SSH connection and login to the last node2 VM because on this node the SHARD Broker is configured. Remember that the last VM which gets started will start the CUBRID SHARD Service.

$ vagrant ssh node2
Welcome to Ubuntu 12.04 LTS (GNU/Linux 3.2.0-23-generic x86_64)

 * Documentation:  https://help.ubuntu.com/

100 packages can be updated.
50 updates are security updates.

Welcome to your Vagrant-built virtual machine.
Last login: Tue Jan 15 06:47:07 2013 from 10.0.2.2
vagrant@node2:~$

To connect to other nodes, simply change the node name as:

$ vagrant ssh node1

Check CUBRID shard status

$ cubrid shard status -f
@ cubrid shard status
% shard  - shard_cas [!12366,45011] /opt/cubrid/log/broker//shard.err 
 JOB QUEUE:0, AUTO_ADD_APPL_SERVER:ON, SQL_LOG_MODE:ALL:100000, SLOW_LOG:ON
 LONG_TRANSACTION_TIME:60.00, LONG_QUERY_TIME:60.00, SESSION_TIMEOUT:300
 KEEP_CONNECTION:ON, ACCESS_MODE:RW, MAX_QUERY_TIMEOUT:0
----------------------------------------------------------------------------------------------------------------------------------------------------------
PROXY_ID SHARD_ID   CAS_ID   PID   QPS   LQS PSIZE STATUS          LAST ACCESS TIME               DB             HOST   LAST CONNECT TIME    SQL_LOG_MODE 
----------------------------------------------------------------------------------------------------------------------------------------------------------
       1        0        1 12374     0     0 55088 IDLE         2013/01/15 04:32:21    sharddb@node1            node1 2013/01/15 04:32:21               - 
       1        1        1 12375     0     0 55088 IDLE         2013/01/15 04:32:21    sharddb@node2            node2 2013/01/15 04:32:21               -

We can notice that CUBRID SHARD Service is running and our sharddb database has been successfully started on both node1 and node2. You can also notice that the SHARD Broker is listening on port 45011.

If you execute this command on other nodes, you will not see similar result because they are not configured to serve as a SHARD Broker, though they can be and in that case they can serve as a Broker failover solution.

Create a common database schema

If you have already read Database Sharding the Right Way: Easy, Reliable, and Open source, you should know that in order to insert and retrieve data from multiple shards, we need to have identical table schema on all shards. Those tables which are present only on some of the shards will not be sharded, in which case they will be just like any other ordinary tables.

So, let's create a common table on all our nodes to store our blog posts.

CREATE TABLE posts (
post_id INT PRIMARY KEY,
post_title VARCHAR(255) NOT NULL
);

Execute this query in your favorite tool. You can use CUBRID Manager, CUBRID Query Browser administration tools, or CSQL command line tool. In this example I will use CSQL on our node1. Remember that you need to execute this query on all nodes to have identical schema.

vagrant@node1:~$ csql -u shard sharddb@localhost
Enter Password : 

CUBRID SQL Interpreter


Type `;help' for help messages.

csql> CREATE TABLE posts (
csql> post_id INT PRIMARY KEY,
csql> post_title VARCHAR(255) NOT NULL
csql> );
SQL statement execution time:     0.008398 sec

Current transaction has been committed.

1 command(s) successfully processed.
csql> ;ex
vagrant@node1:~$

Update shard_key.txt configuration file

Since we have create a new table which we want to shard between multiple nodes, we need to specify which of the columns of this table must be used as shard_key to identify the shard_id. For this we need to update the shard_key.txt configuration file in /opt/cubrid/conf/ directory on node2 where our SHARD Service is started.

#
# Cookbook Name:: cubrid
# Templates:: shard_keys.txt
#
[!%post_id]
#min	max	shard_id
0	31	0
32	63	1
64	95	0
96	127	1
128	159	0
160	191	1
192	223	0
224	255	1

The above will instruct CUBRID to use post_id column as the shard_key for our table. You can define one shard key for each table.

By default CUBRID SHARD will use 256 modulus sharding strategy. You can define you own or even feed CUBRID SHARD with an external library which calculates the sharding id. In the above example, all records where post_id is between 0 and 31 inclusive will be stored in shard 0, in our case it's node1. All records where post_id is between 32 and 63 inclusive will be stored in shard 1, in our case it's node2. This goes on from 0 up to 255 (modulus - 1). These shard_id and host_name mappings are defined in shard_connection.txt configuration file in /opt/cubrid/conf/ directory in case you wonder.

Once we have updated the shard_key.txt configuration file, we need to restart our SHARD Service.

vagrant@node2:~$ cubrid shard restart
@ cubrid shard stop
++ cubrid shard stop: success
@ cubrid shard start
++ cubrid shard start: success

Insert sample data

Now, let's insert data by connecting to our SHARD Broker on port 45011. For this we will write a short Java program which will establish a database connection using CUBRID JDBC driver.

import cubrid.jdbc.driver.CUBRIDConnection;
import cubrid.jdbc.driver.CUBRIDPreparedStatement;
import cubrid.jdbc.driver.CUBRIDResultSet;

import java.sql.*;

public class SHARDBrokerInsertExample {
    static  {
        try {
            Class.forName("cubrid.jdbc.driver.CUBRIDDriver");
        } catch (ClassNotFoundException e) {
            throw new RuntimeException(e);
        }
    }

    public static CUBRIDConnection connect() {
        Connection conn = null;

        try {
            conn = DriverManager.getConnection("jdbc:cubrid:10.11.12.14:45011:sharddb:::?charSet=utf8", "shard", "shard123");
            System.out.println("Connected!");
        } catch ( Exception e ) {
            System.err.println("Error: " + e.getMessage());
        }

        return (CUBRIDConnection)conn;
    }

    public static void printdata(ResultSet rs) {
        try {
            ResultSetMetaData rsmd = null;

            rsmd = rs.getMetaData();

            int numberofColumns = rsmd.getColumnCount();
            System.out.println("Number of columns: " + numberofColumns);

            for(int j = 1; j <= numberofColumns; ++j ) {
                System.out.print(rsmd.getColumnName(j) + ", ");
            }

            System.out.println("");

            while (rs.next ()) {
                for(int j = 1; j <= numberofColumns; ++j ) {
                    System.out.print(rs.getString(j) + "  ");
                }

                System.out.println("");
            }

        } catch ( Exception e ) {
            System.err.println("SQLException : " + e.getMessage());
        }
    }

    public static void main(String[!] args) throws Exception {
        CUBRIDConnection conn = null;

        conn = connect();

        try {
            String sql = "INSERT INTO posts VALUES (/*+ shard_key */ ?, ?)";

            CUBRIDPreparedStatement preStmt = (CUBRIDPreparedStatement)conn.prepareStatement(sql);
            preStmt.setInt(1, 1);
            preStmt.setString(2, "SHARD 0: Post 1 Title");

            preStmt.executeInsert();

            preStmt.setInt(1, 32);
            preStmt.setString(2, "SHARD 1: Post 2 Title");

            preStmt.executeInsert();

            preStmt.setInt(1, 128);
            preStmt.setString(2, "SHARD 0: Post 3 Title");

            preStmt.executeInsert();

            preStmt.setInt(1, 224);
            preStmt.setString(2, "SHARD 1: Post 4 Title");

            preStmt.executeInsert();

            String selectSql = "SELECT * FROM posts WHERE post_id = /*+ shard_key */ 128";

            Statement stmt = conn.createStatement();
            ResultSet rs = stmt.executeQuery(selectSql);

            printdata(rs);

            stmt.close();

            conn.close();

            System.out.println("Connection is closed");
        } catch ( Exception e ) {
            System.err.println("SQLException : " + e.getMessage());
            System.err.println(e);
        } finally {
            if ( conn != null ) conn.close();
        }
    }
}

There are two important things in this code which relate to database sharding.

When inserting a record, give a hint to SHARD Broker which of the columns should be used as shard_key to identify the shard_id. This is done by adding /*+ shard_key */ SQL hint to the INSERT query before the value or the placeholder as shown above.
Likewise, when selecting a data, give a hint to SHARD Broker which of the columns should be used as shard_key. This is done by adding /*+ shard_key */ SQL hint to the SELECT query in WHERE clause before the value or the placeholder as shown above.

If you compile and run this program, you will see the following output:

Connected!
Number of columns: 2
post_id, post_title, 
128  SHARD 0: Post 3 Title  
Connection is closed

Conclusion

In this tutorial you have learnt how to create multiple VMs automatically with CUBRID installed on each of them and configured CUBRID SHARD. As you can see, Vagrant along with Chef cookbook allow us to work with CUBRID Database and other software very easily. It is so much convenient and saves so much of our time. Now creating a development environment is no more painful.

If you have questions, feel free to ask at CUBRID Q&A site, forum, our Facebook page, or Twitter. If you have issues or feature requests to cubrid-cookbook, create a new issue at its Github repo.

How to Get PHP Version

2012-10-31T06:21:25-07:00

If you don't know yet how you can obtain the PHP version, we will guide now by presenting a couple of approaches.

Method #1. Obtain the values from "php -info". If you have grep installed, you can simply run:

php -info | grep "PHP Version"
php -info | grep "Architecture"
php -info | grep "PHP Extension Build"

The first command returns the PHP version (ex. 5.3.6), the second returns the PHP architecture (x86 for 32 bit or x64 for 64 bit) and the last command returns the build type. You should look for TS or NTS and VC6 or VC9 on Windows.

If you do not have grep installed you can output the result into a file using the command:

php -info > phpinfo.txt

Then, just check the phpinfo.txt file created and look for PHP Version, Architecture and PHP Extension Build.

Now that you know the version, architecture and PHP Extension Build, all that remains is to download the CUBRID PHP driver that corresponds to your system and install it using the procedure below:

You will see a php_cubrid.dll file inside the archive on Windows. On Linux it is cubrid.so.

Copy this library to the default PHP extensions folder (usually located at C:\Program Files (x86)\PHP\ext).
Set your system environment. Check if the environment variable PHPRC is "C:\Program Files (x86)\PHP” and system variable path is added with “%PHPRC%” and “%PHPRC\ext”.
Edit php.ini (C:\Program Files (x86)\PHP\php.ini) and add the following two lines at the end of the php.ini file.

[!PHP_CUBRID]
extension=php_cubrid.dll

If you have installed CUBRID 64 bit version, but you are running PHP 32 bit version, then you must also copy the 32 bit version of cascci.dll available here to the location where PHP is installed (C:\Program Files (x86)\PHP). Only cascci.dll needs to be copied from the contents of the archive.
Restart your Web Server.

How to Run a SQL Script / File

2012-10-27T22:45:33-07:00

There are several ways to run queries from a SQL file. One of the easiest ways is run scripts directly using the CSQL command line interpreter. Assuming the script you want to run is named "insert_commands.sql", the following commands should be ran within csql:

;CL
;READ insert_commands.sql
;RU

The first command, clears the command line buffer (;CLear). The second reads the sql script into the command line buffer (;REAd). The last command executes the commands in the command line buffer (;RUn).

Note: If you want the script to run quicker, then you should set autocommit to off. To do this, before running the ;RU command, you should run:

;AU off

This command disables autocommit. Due to this reason, after you run the sql script, in order to commit your changes made, you MUST run:

;commit

;commit (or ;co) commits all changes made.

If you still encounter problems and you are not able to run a SQL script or import a SQL file, please contact us by posting a message in our Q&A site.

Important Facts to Know about CUBRID

2012-02-14T01:00:30-08:00

All database systems are different one way or another. But utilizing best practices and recommendations are equally important on all systems. To improve your experience with CUBRID, we would like to provide you with a list of important facts about CUBRID. Learning them will help you better understand CUBRID, better tune the server configurations, better optimize your SQL queries and therefore improve the performance of your applications.

The below list is not exhaustive. Gradually we will be adding more tips. If you have additional recommendations based on your experience which you think would be helpful to other CUBRID users, please write them in the comments below. We will add your recommendations to this list.

License

CUBRID is distributed under the terms of GPL v2+. However its APIs are available under New BSD. Reason? Give users complete freedom over how they use the APIs and their source code.

We want to ensure that the new features, fixes and other improvements made by third-party developers to the Core Engine are open so that all CUBRID community users could benefit, by distributing the client libraries under the terms of BSD we want to provide OEMs, VARs, and ISVs full control of their products. Developers embedding CUBRID APIs in their applications are required neither to open their source code nor to purchase the commercial license (actually we do not have one). This is one of the most essential benefits developers can experience with CUBRID.

SQL in CUBRID

SQL syntax in CUBRID is very similar to MySQL and even Oracle. In fact, there is over 90% SQL compatibility between CUBRID and MySQL. You can execute most of your existing SQL statements in CUBRID without any modifications. With every new release we add more functions and data types to increase MySQL compatibility.

Despite almost full SQL compatibility, there are some syntax elements which are different in CUBRID:

CREATE TABLE IF NOT EXISTS syntax is not supported yet.
Though CUBRID fully supports ALTER TABLE ... RENAME TO as does MySQL, you can use a much cleaner and easier syntax RENAME TABLE ....

An interesting note is that CUBRID supports Hierarchical Queries compatible with Oracle syntax.

CUBRID is not a fork

CUBRID is not a fork of MySQL (or any other DBMS, for that matters), therefore it does not have anything similar like Storage Engines, e.g. ENGINE=InnoDB part in CREATE TABLE statement. So, if your SQL includes it, just remove it.

Reserved Words

Take a quick look at the reserved words in CUBRID. If your project uses any of them as table or column names, you need to always quote them using backticks (``), double quotes ("") or square brackets ([]), whenever they are referenced.

Besides these, there are some unescapable reserved words. They are the data type name such as INT, VARCHAR etc. You cannot use these words as identifiers, i.e. as names of your tables. The reason lies behind CUBRID's architecture. As you know CUBRID is a relational database but it also supports objects. This allows users to create tables where columns' data type can be another table. See the following example:

create table t1 (a int);
create table t2 (b t1);

Here t1 table can be a column type of column b in table t2. So considering this feature, look at this example below:

create table "int" (a int);
create table "t2 (b int);

If we allow a table to have a name like "int", then we have a problem: what is the type of column b in t2? Is it the table "int", or just the basic type INT?

This creates an ambiguity. This is why in CUBRID data type names are not allowed to be table names.

Database in CUBRID

Every database in CUBRID must be explicitly started before working with them. By default they are stopped. See [Start or Autostart CUBRID Database] for more info.
As of version 8.4.3, database names in CUBRID should not exceed 17 characters.
CUBRID does not allow to create or drop a database from within the SQL query. Command line cubrid createdb, cubrid deletedb utilities or CUBRID GUI Tools should be used to accomplish this task.

Data Types

As of version 9.0.0 CUBRID does not support UNSIGNED, BOOL data types, if you want to use them. ENUM is supported since 9.0.0. The rest will be implemented in the future versions. See CUBRID vs. MySQL vs. Oracle Data Type Mapping for more information on recommended data type mapping.

In 8.4.1. if you set SYS_TIMESTAMP as a DEFAULT value of a TIMESTAMP column when creating a table, the TIMESTAMP value at the point of CREATE TABLE will be set as default, NOT the time at which the data is INSERTed. Therefore, in order to set the current time and not the time when the table was created, you must specify the SYS_TIMESTAMP value for the VALUES of the INSERT statement when entering data.

In 9.0.0 SYS_TIMESTAMP/ SYSDATE set as DEFAULT values will be based on the time/date of the query execution.

User Defined Data Types

In CUBRID users can create columns with custom data type. One table can be a data type for a column in another table. See an example given in the Reserved Words section above.

Data Type Boundaries

Also pay attention to permitted [CUBRID RDBMS Size Limits|maximum and minimum] values for data types.

Large Objects

In CUBRID [Working with CUBRID BLOB / CLOB Data Types|Large Objects (BLOB/CLOB)] are stored outside the database on the external storage while the references to those files are stored in database columns.
Since they are stored on the external disk, LOB data cannot be indexed. See the manual for more info.
Likewise, UNIQUE index cannot be created.
Columns with LOB data type cannot be NOT NULL and cannot have DEFAULT value.

Indexing in CUBRID

CUBRID uses B+tree indexes to improve search performance

Works great for equality operator (=).
Since indexes are represented as trees, Key range scan allows to significantly improve the search performance if WHERE clause contains range conditions (<, >, <=, >=, =). If Range conditions are not defined, the Optimizer will attempt to perform sequential table scan.
Try to avoid using irregular conditions such as <>, !=, or NULL, since the Optimizer will not be able to take the full advantage of the index tree, and instead will perform a sequential scan.
Covering Index is magic. Use it to improve the search performance.
If possible, utilize LIMIT clauses to take advantage of Key limit optimizations.
Learn about In-place Sorting feature in CUBRID to improve the performance of ORDER BY statements.
Use COUNT(*) instead of COUNT(col_name), unless you really know what you are doing.
Index names in CUBRID are unique per table. For better readability, you can indicate in an index name the name of the table the index belongs to like pk_tableName_col1Name_col2Name_etc.
LOB data cannot be indexed in CUBRID.
Avoid creating indexes on columns where values can exceed 16KB. For more information refer to Page Storage Structure section of How SQL UPDATE is performed in CUBRID RDBMS.
Try to avoid low-selectivity edges (eg. indexes on columns where there are very few distinct values like gender). Since in CUBRID indexes are stored in B+tree, in low-selectivity case, same value records (eg. records where gender = 'M') will be stored in the same index node. If there are too many records which cannot fit into one page, CUBRID will need to maintain Overflow OID page for them. If the number of separate overflow pages increase, it will affect the performance as there will be a burden to navigate between these additional links. For more, refer to Overflow OID section in the same How SQL UPDATE is performed in CUBRID RDBMS blog.
If you have created an index and would like to UPDATE/DELETE/INSERT a new data, try to use random inserts to avoid key locking. Refer to Key Lock section of How SQL UPDATE is performed in CUBRID RDBMS blog.

Click Counter

Take advantage of CUBRID’s unique Click Counter feature. For example, instead of executing two separate SQL statements like:

SELECT article FROM article_table WHERE article_id = 130,987;
UPDATE article_table SET read_count = read_count + 1 WHERE article_id = 130,987;

… in CUBRID you can execute only one:

SELECT article, INCR(read_count) FROM article_table WHERE article_id = 130,987

This will help you avoid expensive lock of the working record generated by UPDATE operation.

AUTO_INCREMENT

AUTO_INCREMENT in CUBRID is implemented as SERIALS which are not affected by transaction rollback. This is different from how it is implemented in MySQL. In practice, developers do not care about the implementation details. But with SERIALS implementation you can, for example, control the step of the increment or set the initial value. It is good to know what you can do in CUBRID. We have blogged about this in details in Things to Understand When Moving from MySQL to CUBRID. Please refer to this document.

Foreign Keys

Foreign keys in CUBRID must reference PRIMARY KEY columns of referenced tables. In other words, you cannot reference non-primary key columns. Also, if the parent table has a compound primary key, i.e. PK that consists of multiple columns, all these columns must be referenced in the FOREIGN KEY and in the same order. Referencing only some of them is not allowed. How can a child record have multiple referenced parent records after all?

User Management

In CUBRID, the smallest grant unit of authorization is a table. This means that CUBRID does not support authorizations at the column level. Refer to Introduction to CUBRID Security for more information.
Also, in CUBRID there is a concept of users and groups. Any user can represent a group which will mean that any group member will inherit all the privileges of this group. The parent user which became a group is still a user, i.e. you can use it to connect. Thus, grouping in CUBRID allows to delegate all the privileges of one user to other users.
To learn more, we recommend to look at user management related questions and answers.

Native High-Availability feature

Did you know that CUBRID has its own built-in High-Availability feature? Oh, yes, it does. In fact, CUBRID HA is one of the main reasons why Enterprise solution providers choose CUBRID over other open source RDBMS. It is based on transaction log replication, and provides very accurate and predictable fail-over and fail-back features based on CUBRID Hearbeat. You can configure HA environment in three copy modes for transaction log replication: synchronous, semi-synchronous, and asynchronous modes.

With CUBRID HA, it is possible to build multi Master:Slave services. There is also Master:Slave:Replica configuration. This configuration will provide much lower networking and disk I/O loads for heavy read loaded Web services, than the single master and multiple slaves configuration does.

For small size Web services whose primary goal is to lower the cost, developers can configure multiple slaves in a single server. This configuration will allow to gather all (or some) slave databases on a single host. Thus, it will be possible to allocate a single physical machine for multiple slave databases, each of which are separately replicated from their own master databases. Refer to OSCON conference presentation material to see how you can develop your service architecture.

To learn more about CUBRID HA, read Overview of New High-Availability Features in CUBRID 8.4.0 as well as How CUBRID HA Works? Also you are highly encouraged to view our OSCON and RIT++ conference presentation materials. You will find very interesting information about CUBRID there.

If you want to try CUBRID HA, see how to [Configure CUBRID HA with Vagrant and Chef Cookbook under 4 minutes].

Native Database Sharding feature

This is something no open source RDBMS can offer you for free. We have developed a native CUBRID SHARD feature which will be released with CUBRID 8.4.3 in October, 2012. All open source! All completely free!

Refer to Database Sharding with CUBRID to get a sneak peek of how will CUBRID SHARD work. We have also posted a blog about the difference between CUBRID SHARD and Spock Proxy for MySQL. We will publish the manual how to setup CUBRID SHARD along with the official announcement. Stay tuned!

Install Apache Solr on Ubuntu

2012-02-20T02:13:39-08:00

Installing Apache Solr on Ubuntu is quite easy. In fact, it does not require any installation. All you will need to do is just download and extract the package. But before you proceed, make sure you have already [Install Apache Tomcat on Ubuntu|installed Tomcat] which is necessary to access Solr from the browser.

To make further management of Solr server easy, we will first create a separate user for it.

sudo adduser solr

You will be asked to enter a password for solr user as well as additional information which you can ignore by simply pressing Enter. Once done, login to this user. When password is prompted, enter the password you have just created.

su - solr

Once you are logged in, you will be in /home/solr directory.

Now download the latest version of Apache Solr from the official site. On that site you will be given a list of mirror sites to download the installation package. Click on one of them. You will see a list of several versions of Solr. Choose the latest one. Copy the URL of the file (*.tgz) and download it from the terminal as shown below.

wget http://mirror.apache-kr.org/lucene/solr/4.0.0/apache-solr-4.0.0.tgz

Extract the package.

tar xzf apache-solr-4.0.0.tgz

All files will be extracted to apache-solr-4.0.0/ directory. This is all you need to continue to work with Solr. To configure Solr server to connect to a CUBRID Database, see the next tutorial.

Install Apache Tomcat on Ubuntu

2012-02-20T01:41:23-08:00

Apache Tomcat is a Web container that allows to serve Java Servlets (such as [Using Solr / Lucene for full text search with CUBRID Database on Ubuntu|Solr full-text search server]) and JSP (Java Server Pages) Web applications. More information can be found on Tomcat official site.

In this tutorial you will learn how to install Tomcat 7 on Ubuntu 11.10. To install Tomcat type the following command in the terminal.

sudo apt-get install tomcat7

This will install Tomcat on port 8080 (default) and autostart it (also it will be set to autostart on system reboot). To see if installation went successfully, navigate to http://localhost:8080 in your browser. You should see a default page which displays "It works!".

To have Apache Solr work with Tomcat, you do not need to configure anything. Default settings will work out of the box. If necessary, you can refer to Ubuntu Documentation for Tomcat.

Stop/Start Tomcat

If you need to stop or start Tomcat, run the following respectively:

~$ sudo service tomcat7 stop
~$ sudo service tomcat7 start

Installing CUBRID on Fedora/CentOS

2012-01-24T20:56:36-08:00

To install CUBRID on Fedora or Ce using yum command, we need to tell Yum where to look for CUBRID packages. First, visit one of the following links depending on your OS.

CentOS: http://www.cubrid.org/?mid=yum_repository&os=centos&cubrid=8.4.3
Fedora: http://www.cubrid.org/?mid=yum_repository&os=fedora&cubrid=8.4.3
Full Tutorial: http://www.cubrid.org/cubrid_yum_repositories

There choose CUBRID version. You will be given a list of links for your particular version.

CUBRID 8.4.3

Since CUBRID 8.4.3 there are only 2 repositories and you must choose according to your OS and version:

For Fedora 15 and above:

sudo rpm -ivh http://yumrepository.cubrid.org/cubrid_repo_settings/8.4.3/cubridrepo-8.4.3-1.fc15.noarch.rpm

For Fedora 13/14 and Centos 6.0 and above:

sudo rpm -ivh http://yumrepository.cubrid.org/cubrid_repo_settings/8.4.3/cubridrepo-8.4.3-1.el6.noarch.rpm

CUBRID 8.4.1 and below

For example, the following link is provided for Fedora 17 where fc17 means this OS version. Other versions will have fc16, fc15, etc.

sudo rpm -i http://yumrepository.cubrid.org/cubrid_repo_settings/8.4.1/cubridrepo-8.4.1-1.fc17.noarch.rpm

Or CentOS example where el6.2 means CentOS version 6.2:

sudo rpm -i http://yumrepository.cubrid.org/cubrid_repo_settings/8.4.1/cubridrepo-8.4.1-1.el6.2.noarch.rpm

Installing CUBRID

Executing the above command will tell Yum where to look for CUBRID packages.

Now, you can install CUBRID by running:

yum install cubrid

To complete the installation and set the CUBRID PATH variables, reboot your OS or logout and login again. Until rebooting you must run ". /etc/profile.d/cubrid.sh" to set the PATH variables every time you open a new terminal window.

Optional: If you want to install the demodb sample database, run the command:

 sudo yum install cubrid-demodb

Installation Notes

CUBRID is installed in /usr/share/cubrid.
The configuration files are placed in /etc/cubrid.
Variable files (such as logs or databases) are stored in /var/cubrid.
Binaries can be found in /usr/bin and /usr/sbin, while libraries in /usr/lib.
The path variables $CUBRID and $CUBRID_DATABASES are set in the file /etc/profile.d/cubrid.sh.
If you run a CUBRID service command, you can view its output in /var/cubrid/tmp/service.cubrid.
CUBRID is set to automatically start on boot and the service file is located at /etc/init.d/cubrid.
On Fedora 15+, there is also a systemd file located at /usr/lib/systemd/system/cubrid.service
Highly Important! cubrid or standalone csql commands can be only ran as cubrid user (which has no password). To connect as this user, use "sudo su -s $SHELL cubrid".