I would like to point out that I've tried to install today the CUBRID 8.3.1 from the YUM repo and seem to fail with some mirror error...

Using CentOS 6 x64.

1. Install the YUM repo using this tutorial http://yumrepository.cubrid.org/index_Centos_cubrid_3.1.html

2. [cristiroma@linux ~]$ sudo yum install cubrid

Loaded plugins: fastestmirror, refresh-packagekit

Loading mirror speeds from cached hostfile

 * base: ftp.halifax.rwth-aachen.de

 * extras: ftp.halifax.rwth-aachen.de

 * rpmforge: ftp-stud.fht-esslingen.de

 * updates: mirrors.ch-center.com

Setting up Install Process

Resolving Dependencies

--> Running transaction check

---> Package cubrid.x86_64 0:R3.1-r3 will be installed

--> Processing Dependency: lzo for package: cubrid-R3.1-r3.x86_64

--> Processing Dependency: cubrid-compat for package: cubrid-R3.1-r3.x86_64

--> Processing Dependency: cubrid-libs for package: cubrid-R3.1-r3.x86_64

--> Processing Dependency: gc for package: cubrid-R3.1-r3.x86_64

--> Processing Dependency: libcubridsa.so.0()(64bit) for package: cubrid-R3.1-r3.x86_64

--> Processing Dependency: libcascci.so.8()(64bit) for package: cubrid-R3.1-r3.x86_64

--> Processing Dependency: libcubrid.so.0()(64bit) for package: cubrid-R3.1-r3.x86_64

--> Processing Dependency: libcubridcs.so.0()(64bit) for package: cubrid-R3.1-r3.x86_64

--> Processing Dependency: libgc.so.1()(64bit) for package: cubrid-R3.1-r3.x86_64

--> Processing Dependency: liblzo2.so.2()(64bit) for package: cubrid-R3.1-r3.x86_64

--> Running transaction check

---> Package cubrid-compat.x86_64 0:R3.1-r3 will be installed

---> Package cubrid-libs.x86_64 0:R3.1-r3 will be installed

---> Package gc.x86_64 0:7.1-10.el6 will be installed

---> Package lzo.x86_64 0:2.03-3.1.el6 will be installed

--> Finished Dependency Resolution

Dependencies Resolved

===============================================================================================================================================================================================

 Package                                         Arch                                     Version                                           Repository                                    Size

===============================================================================================================================================================================================

Installing:

 cubrid                                          x86_64                                   R3.1-r3                                           cubridrepo                                   1.1 M

Installing for dependencies:

 cubrid-compat                                   x86_64                                   R3.1-r3                                           cubridrepo                                    68 k

 cubrid-libs                                     x86_64                                   R3.1-r3                                           cubridrepo                                   9.7 M

 gc                                              x86_64                                   7.1-10.el6                                        base                                         146 k

 lzo                                             x86_64                                   2.03-3.1.el6                                      base                                          55 k

Transaction Summary

===============================================================================================================================================================================================

Install       5 Package(s)

Total size: 11 M

Total download size: 11 M

Installed size: 35 M

Is this ok [y/N]: Y

Downloading Packages:

http://yumrepository.cubrid.org/cubrid3.1/Centos/6/x86_64/cubrid-R3.1-r3.x86_64.rpm: [Errno 14] PYCURL ERROR 22 - "The requested URL returned error: 404"

Trying other mirror.

http://yumrepository.cubrid.org/cubrid3.1/Centos/6/x86_64/cubrid-compat-R3.1-r3.x86_64.rpm: [Errno 14] PYCURL ERROR 22 - "The requested URL returned error: 404"

Trying other mirror.

http://yumrepository.cubrid.org/cubrid3.1/Centos/6/x86_64/cubrid-libs-R3.1-r3.x86_64.rpm: [Errno 14] PYCURL ERROR 22 - "The requested URL returned error: 404"

Trying other mirror.

Error Downloading Packages:

  cubrid-libs-R3.1-r3.x86_64: failure: cubrid-libs-R3.1-r3.x86_64.rpm from cubridrepo: [Errno 256] No more mirrors to try.

  cubrid-compat-R3.1-r3.x86_64: failure: cubrid-compat-R3.1-r3.x86_64.rpm from cubridrepo: [Errno 256] No more mirrors to try.

  cubrid-R3.1-r3.x86_64: failure: cubrid-R3.1-r3.x86_64.rpm from cubridrepo: [Errno 256] No more mirrors to try.

I want to alter the table schema and set the default value for join_date column to be the current timestamp in UNIX time. I tried the following SQL, but I keep getting "Syntax: syntax error, unexpected IdName" error.

How should I do?

Now install the latest version of CUBRID:

Supported CUBRID version

• CUBRID 8.2.2.x ~ CUBRID 8.4.1.0558

Improvement

• [TOOLS-95] - human readable/editable template file
• [TOOLS-96] - increase performance of MySQL dump file parsing
• [TOOLS-121] - support cancel migration task even which run on server side as standalone process
• [TOOLS-228] - CM server improvements
• [TOOLS-337] - There is error in migration, the migration progress bar isn't finished
• [TOOLS-355] - Please add one summary which is like step5 to migration history
• [TOOLS-358] - Goto step4, don't choose create new table and data migration for one table, goto report, the table will display error, please add some error infor
• [TOOLS-490] - Add charset in file repository.

Task

• [TOOLS-110] - Improve migration working engine
• [TOOLS-111] - Data transform engine
• [TOOLS-112] - Improve migration wizard UI
• [TOOLS-569] - To support CUBRID 8.4.1 and prepare release build
• [TOOLS-600] - It is needed a brandnew version string that it easily support for CUBRID compatibility.

Bug

• [TOOLS-306] - In step2, click off line, database should display offline database. But there is all database.
• [TOOLS-309] - After migration, the process bar isn't finished
• [TOOLS-310] - Offline migration to online database, it can do migration.
• [TOOLS-314] - In step2, connect one online server, then stop the server, do migration, the result is error
• [TOOLS-321] - XML to cubrid, datetime data type transfer error
• [TOOLS-322] - When there are two index which has same name in xml, one index will be error.
• [TOOLS-324] - XE template saved can't reproduce former step(that is step 2:select target database) when using the converting form: online->file repository.
• [TOOLS-341] - Migrate to file repository, the file hasn't override the target files
• [TOOLS-345] - After do offline migration, the target database hasn't data.
• [TOOLS-351] - Migrated FK from Mysql to CUBRID, if one table has primary key, the FK will became index
• [TOOLS-353] - When multitype in tables, the view hasn't multitype.
• [TOOLS-354] - Export migration report to excel. The sheet is ambiguous.
• [TOOLS-356] - The progress bar is not complete when converting database.
• [TOOLS-359] - the index of type "unique" can not be converted to type of "reverse unique" or "reverse index"
• [TOOLS-362] - Multiplication should be decided by the charset target database.
• [TOOLS-363] - Changed charset in step1, the index, PK migrated failed
• [TOOLS-368] - There is no effect for step 4 when be back to step 3 from step 4 to edit the "select statement" table name.
• [TOOLS-369] - There is no effect for "ok" button when selecting other charset from default.
• [TOOLS-371] - In step4,choose don't create table, goto migration report, display migrate table error.
• [TOOLS-377] - Bit(1) cannot migrate to target database.
• [TOOLS-378] - The time form in log is inconsistent.
• [TOOLS-379] - Only choose some fields to do migration, the cut is error
• [TOOLS-385] - After migration, binary(255) cannot be migrated
• [TOOLS-386] - After convert blob to bit, the target data is error.
• [TOOLS-388] - bool and boolean convert is error
• [TOOLS-389] - the index of type "unique" can not be converted to type of "reverse unique" or "reverse index"(mysql->offline db)
• [TOOLS-391] - In date data type migration, it will be error
• [TOOLS-392] - The form of time is 12h(I think it should be 24h) and the statement should not be ended ";".
• [TOOLS-393] - the hint in the status bar of help system is wrong.
• [TOOLS-397] - Migrated from online db view to file, the report and the file contents isn't consistent.
• [TOOLS-400] - Migrated decimal to numeric, it will be error in migration.
• [TOOLS-401] - When migrating from db to online database, stop db server. In migration
• [TOOLS-404] - Enum type can't migrated to target type successfully when changing target column name
• [TOOLS-405] - Longtext type can't be migrated to target type successfully when changing the target column name.
• [TOOLS-406] - Migrated float , it will be error.
• [TOOLS-410] - Save XE to one exist xml, it will pop failed.
• [TOOLS-413] - In migration from xml to file, datatime is error.
• [TOOLS-414] - Migrated from online db to cubrid, datetime convert is error.
• [TOOLS-415] - In sometime, the log will be combined.
• [TOOLS-419] - When migrate varbinary(65532) to bit varying, the big value cannot be migrated.
• [TOOLS-420] - When migrate the data type about int error, the report error.
• [TOOLS-422] - The function of "Data Migration" has no effect
• [TOOLS-425] - When do xml to cubrid migration, if change the source charset, it will migrate error.
• [TOOLS-428] - In report,click the canceled DB Objects, it hasn't display name.
• [TOOLS-429] - The view ddl in the file migrated display is not good
• [TOOLS-432] - there is an error when migrating a table of year type.
• [TOOLS-437] - When multiplicated in tables, the view hasn't been multiplicated.
• [TOOLS-440] - Choose the replace table in step3, haven't delete index.
• [TOOLS-441] - Migrated the table which has two fk will error
• [TOOLS-443] - In step4, can change view sql, but when migrate, it will be error
• [TOOLS-445] - the prompt of "Save current tab to file" is not exact and should be like another prompt "Save all tabs to an excel file"
• [TOOLS-448] - When choose something, it will pop nullpointerException.
• [TOOLS-451] - the parameter of "NULL" about time in migration parameters of Preferences has no effect
• [TOOLS-452] - the parameter of "Replace with" about time in migration parameters of Preferences has no effect
• [TOOLS-453] - the parameter of "NULL" about date in migration parameters of Preferences has no effect
• [TOOLS-455] - the parameter of "Replace with" about date in migration parameters of Preferences has no effect
• [TOOLS-456] - the parameter of "NULL" about timestamp in migration parameters of Preferences has no effect
• [TOOLS-457] - the parameter of "Replace with" about timestamp in migration parameters of Preferences has no effect
• [TOOLS-459] - The default XE template cannot be used
• [TOOLS-462] - the table of type converting can be edit to anything(please do some limit when editing them)
• [TOOLS-463] - Migrated datetime from xml and online database, it's different.
• [TOOLS-466] - Migrate xml charset is not utf8, it will be error.
• [TOOLS-467] - the "0"(zero) in the data(the "0" is in the end) will be lost when converting binary to bit.
• [TOOLS-469] - there is an error when two user migrate two different databases to the same target database concurrently
• [TOOLS-470] - In the new version, do migration from online db to new db, many tables cannot be migrated
• [TOOLS-471] - the negative number and zero will be converted to "0" and positive number will be converted to "1" when converting bool type to smallint type.
• [TOOLS-473] - the data is inconsistent when migrating date type to date type
• [TOOLS-474] - Migrate xml to online cubrid, bit data is error
• [TOOLS-475] - Migrate bit(1) from xml to online database, it doesn't work
• [TOOLS-476] - Migrate numeric to numeric,some data hasn't been migrated
• [TOOLS-477] - Do migration from loaddb, the blob content directory cannot found.
• [TOOLS-478] - the data is inconsistent when migrating datetime type to datetime type
• [TOOLS-479] - Migrated from xml to new DB and from mysql DB to new DB,the data of bool data type isn't same.
• [TOOLS-480] - the data is inconsistent when migrating double type to double type
• [TOOLS-481] - the window of "preferences" can not be closed when you click "close" icon first time under certain conditions.
• [TOOLS-482] - Migrated from xml to offline db, timezone from default to default, timestamp is error
• [TOOLS-483] - the data is inconsistent when migrating double unsigned type to double unsigned type
• [TOOLS-484] - Migrate xml to online cubrid, datetime,time,timestamp data is error
• [TOOLS-485] - the data is inconsistent when migrating float type to double type
• [TOOLS-486] - the data is inconsistent when migrating float unsigned type to double type
• [TOOLS-487] - the migration of converting longblob type to blob type is failed
• [TOOLS-489] - the data is not what we expects it to be when migrating numeric(20,10) type to numeric(20,8) type
• [TOOLS-491] - In step2, choose timezone in file repository. Save XE,
• [TOOLS-493] - Choose all in step3, save XE, the sequences cannot been saved
• [TOOLS-494] - the data is inconsistent when migrating year type to character type
• [TOOLS-496] - By some way, XE cannot be used.
• [TOOLS-503] - Use XE which is export mysql DB to online DB, delete online DB, it will pop "Failed to connect database server"
• [TOOLS-504] - Migrate online to file ,it will pop java.lang.NullPointerException
• [TOOLS-506] - When delete migration history, please give confirm info.
• [TOOLS-507] - Use XE, "add prefix to index names" doesn't work
• [TOOLS-508] - After some operation, it will pop NullPointerException
• [TOOLS-509] - the parameter of "Replace with" about time in migration parameters of Preferences has wrong effect
• [TOOLS-515] - There is some error about display in ubuntu 64 bit or windows
• [TOOLS-517] - There is an error after migrating a big xml(but having no error after migrating the same xml)
• [TOOLS-523] - The index name of target DB is not the same with the name in the field of "Target Index Name"
• [TOOLS-524] - The function of "Replace Existed Tables" has some errors when replacing table which have FKs(you must notice the order of deleting these tables)
• [TOOLS-527] - After extract the new version, login cmt, in the copyright of CUBRID Migration Toolkit, there are Chinese word.
• [TOOLS-529] - Migrate blob data type to file, it record the absolute path
• [TOOLS-533] - Migrate big xml (test.xml) to file, will have some index will be canceled.
• [TOOLS-534] - When do migration from big xml to offline, sometimes pop "listen:Address already in use <end> "
• [TOOLS-539] - Migrate bfile data type, the default glo is not defined
• [TOOLS-540] - When get data from source database, the waring word in Chinese is error
• [TOOLS-541] - When there are composite primary key, it will be error.
• [TOOLS-542] - Migrated from oracle to cubrid, there is clob data type, it cannot migrated.
• [TOOLS-544] - Migrate from oracle to cubrid, the migration from timestamp withe local time zone and time stamp with time zone to datetime is error
• [TOOLS-545] - Migrated from bfile to blob, it hasn't been migrated
• [TOOLS-546] - Migrate from blob to blob,clob to clob, nclob to nclob the data hasn't been migrated
• [TOOLS-548] - The data of the two type "INTERVAL YEAR TO MONTH" and "INT,INTERVAL DAY TO SECOND" will be converted to "NULL" when using the converting form Oracle DB->online
• [TOOLS-549] - The record of long type cannot be converted(oracle db->online)
• [TOOLS-550] - Migrate from date date type to date, it will lost time.
• [TOOLS-551] - Migrated date 0000-0-0 to date, it became 4713-01-01
• [TOOLS-553] - Migrate from urowid to varchar, the value is error
• [TOOLS-554] - Migrate long raw to bit varying(1073741823), it isn't same as raw to bit varying
• [TOOLS-556] - Migrate int to int, some data cannot be migrated.
• [TOOLS-558] - The record of number type cannot be converted(oracle db->online)
• [TOOLS-561] - The data migration from decimal, number to number is different in migration from oracle and mysql
• [TOOLS-563] - Migrate from interval_day_to_second to varchar, the data is not good
• [TOOLS-564] - Migrate interval to Varchar, the data type is constant , but it times 3.
• [TOOLS-565] - Migrate from real to float, the data cannot be migrated
• [TOOLS-566] - Migrate int to numeric(38,0), the data cannot be migrated.
• [TOOLS-568] - Migrate from date to datetime, the data is error
• [TOOLS-577] - In migration, there is pk and unique index, the unique constraint will be lost.
• [TOOLS-578] - Migrate FK on delete no action from oracle to cubrid, the action change from no action to restrict.
• [TOOLS-581] - Normal index cannot be migrated from oracle to cubrid.
• [TOOLS-583] - When there are procedure, trigger, function in oracle db, migrate from oracle to cubrid, the nonsupport objects is error
• [TOOLS-585] - SQL statement hasn't multiply.
• [TOOLS-586] - There is a help mark(?) in the interface of "Preferences"
• [TOOLS-587] - There is an extra word in the sentence "To File Repository Commit Count"
• [TOOLS-589] - Migrate date data type to offline db, datetime changed too.
• [TOOLS-590] - Oracle has change timezone to GMT+04:00, but in step5 in migration, it display GMT+08:00
• [TOOLS-591] - When do big xml migration, there are wait long time sometimes.
• [TOOLS-592] - There is a wrong word in "Preferences"
• [TOOLS-595] - In xe, the index hasn't be saved.
• [TOOLS-597] - The primary key can not be created when migrating mysql db to offline db..
• [TOOLS-598] - When do migration use XE, the sequence will be error

CUBRID Migration Toolkit 1.5.5

Bug

• [TOOLS-165] - Display referential ations on "FK" and apply that option a user chooses to tables by asking "you want to apply the option to all tables?"
• [TOOLS-212] - Migrate partition table to CUBRID8.4.0 successfully. But the table is migrated to CUBRID8.4.1 is error.
• [TOOLS-229] - Use XE to do migration, go to step5 , then back to step1, omit XE, goto step3, only display the table which in XE
• [TOOLS-255] - The csql error is occurred when click the Check Owner with no-inputted User name and Password form on the migration wizard step 4
• [TOOLS-267] - When using "Load Migration Script" menu, target table name is always empty in the SQL tab in the step 5.
• [TOOLS-268] - In step4, after choose "Skip Check of the exist database name and the owner name", then choose Create new database, the warning is error
• [TOOLS-273] - After migrate the source database to txt file, the import record count of migration statistic report display exported
• [TOOLS-274] - Migrate decimal data type to CUBRID, the target data type is error
• [TOOLS-282] - From mysql to CUBRID, the FK migration is not right.
• [TOOLS-286] - Migrated FK from Mysql to CUBRID, if one table has primary key, the FK will became index
• [TOOLS-291] - When we choose the XE, click next. It cannot goto step 2
• [TOOLS-292] - The same xml migrated to old version and new version, the result is not same.
• [TOOLS-293] - Use XE, do migration, goto step 6, the UI is error. The result of step 7 is error too.
• [TOOLS-296] - It occur a error sometimes when using customized XE template because it didn't create new database.
• [TOOLS-297] - After add the attention of alert of the no logging option using, has error.
• [TOOLS-298] - In some times, the import record count will display error
• [TOOLS-299] - Use XE, migrated xml, if the xml has fk, the fk become to index, and the index hasn't been choosed.

Improvement

• [TOOLS-166] - In the wizard 1, it should nitoce the user that CMT server should be installed in the CUBRID server
• [TOOLS-253] - A default values of a database volumn auto extends option is not same of CMT and CM (CMT와 CM 에서의 데이터베이스 생성시의 Default화면이 다릅니다)
• [TOOLS-264] - Improve a multibyte charset supports.
• [TOOLS-265] - Users difficult to know whether change to resize when a database has multi-bytes character set.
• [TOOLS-266] - For users convenience, some of the menu needs to be put on the toolbar.
• [TOOLS-295] - Need to show a alert dialog when using a --no-logging option in the migration step 6.
• [TOOLS-288] - Include a recent driver of CUBRID 8.4.0 in CMT 1.5.5

New Feature

• [TOOLS-262] - Can create the loaddb type data files without a database import
• [TOOLS-263] - Add to select a table method with a file of a table name list in wizard step 3

CUBRID Migration Toolkit 1.5.4

Bug

• [TOOLS-143] - In migration history, cannot choose any record, click delete button. It will prompt "Are you sure to delete the migration history"
• [TOOLS-144] - When new database connection, the JDBC driver hasn't display order by version desc
• [TOOLS-145] - In step1, when choose use default XE, click next. It will pop a process windows, but the cancel button is disable.
• [TOOLS-148] - Input a not available remote migration server ip , It can go next from step 1 to step 2 when you use an available IP to test connection before
• [TOOLS-163] - When loading table schem with default values, it quotes the values of some (randomly)
• [TOOLS-164] - CMT automatically increases the size to2X or 3X depending on CHARSET to handle the multi-byte characters.
• [TOOLS-167] - In migration, if import data is less than export, there isn't warning.
• [TOOLS-169] - CMT returns no error when checking the option "creating a new database" on the wizard 4 in the localhost without installing cubrid server
• [TOOLS-170] - When SELECT statement are entered to extract part of records only from the source DB, CMT doesn't work well.
• [TOOLS-189] - JDBC 드라이버 오류로 인한 오라클 삭제된 테이블 조회되는 오류
• [TOOLS-190] - In step1, input error ip, it will pop null
• [TOOLS-196] - Slowly sub-query issue while checking SQLs syntax
• [TOOLS-210] - When SELECT statement are entered to extract part of records only from the source DB, CMT doesn't work well.
• [TOOLS-216] - In migration report wizard,the load a xml file time error
• [TOOLS-222] - change the checkbox(change all the solumn size of char .....)in the migration wizard step 2,the step 5 page's content don't update.
• [TOOLS-223] - Do migration by XE template, migrate xml file, it will pop error sometimes.
• [TOOLS-226] - In windows64, there is a charset of cp1252 in step 4
• [TOOLS-227] - Use XE to create XE, found the table will be lost

Improvement

• [TOOLS-24] - CMT 용어 개선 및 설명
• [TOOLS-102] - CMT supports Mac OS

New Feature

• [TOOLS-23] - CMT 인댁스 수 Before/after 비교하기

CUBRID Migration Toolkit 1.5.3

Improvements and bug fixes

• [TOOLS-76] - CMT report improved
• [TOOLS-96] - There is a big improvement of parsing MySQL dump file .
• [TOOLS-97] - If data source is xml file, the condition input cell will be read-only.

CUBRID Migration Toolkit 1.5.0

• CUBRID Migration Toolkit 1.5.0 Release Note_en.pdf

CUBRID 데이터마이그레이션 전문 도구인 CUBRID Migration Toolkit 8.4.1 버전(빌드번호 0007)을 릴리스합니다.
CUBRID Migration Toolkit 8.4.1은 CUBRID 8.4.1을 지원하며 기존 1.5.5 버전 이후 안정성과 편의성을 보완한 제품 입니다.

8.4.1은 기존 1.5.5의 다음 버전으로 CUBRID 호환 버전 선택시 있을 혼란을 방지하기 위해
CUBRID와 동일한 버전 번호로 릴리스였으며 앞으로도 이와 같이 릴리스하겠습니다.

 
1. DB 서버 호환 버전 및 지원 OS
- CUBRID 8.2.2 버전 ~ CUBRID 8.4.1 버전의 DB 서버와 호환됩니다. (각 버전별 JDBC 드라이버 내장)
- 지원 OS: Windows, Linux, Mac
- 지원 DBMS: CUBRID, MySQL, Oracle (8.4.1부터 MS-SQL은 지원 대상에서 제외)

2. 요구 사항
-  JRE 1.6 버전 이상이 필요합니다.

3. 다운로드
- FTP 서버: ftp://ftp.cubrid.org/CUBRID_Tools/CUBRID_Query_Browser/4.1/
- 영문 커뮤니티: http://www.cubrid.org/?mid=downloads&item=cubrid_query_browser

4. 주요 개선 사항
- 기존 복잡하고 불편했던 UX를 직관적이면서 깔끔하게 전면 개편하였습니다.
- 인덱스 누락, 멀티바이트 오버플로우 문제를 수정하였습니다.
- 원격 데이터 이전시 CMT 서버를 별도 설치할 필요가 없습니다.
- Load DB 파일로 직접 내려받는 기능을 정식 지원합니다.
- CUBRID 8.4.1 서버를 지원하며 해당 버전의 JDBC 드라이버를 내장하였습니다.
- Mac에서 기존에 사용할 수 없었던 메뉴 <환경설정>과 <About>를 지원하였습니다.
 
5. 주의 사항 
- MySQL XML 마이그레이션시 데이터 내의 CR(Carrage Return)이 필히 유지되어야 하는 데이터는 이전시 문제가 발생할 수 있습니다.
  - 윈도우즈에서 작성된 데이터는 대부분 CR이 붙어 있으나 일반적인 경우에는 CR이 누락되어도 문제가 없습니다.
  - 단, XE 사이트 마이그레이션시 extra_vars 컬럼에서 문제가 발생하였습니다. php의 serialize/unserialize 관련 문제 입니다. 이 경우 JDBC 방식을 이용하거나 Release Candidate 1을 설치하셔서 마이그레이션 하시길 바랍니다.
(다운로드: http://sourceforge.net/projects/cubridtools/files/build/CUBRID%20Migration%20Toolkit/8.4.1-rc1/ )
  - 단, CR을 사용하지 않는 Unicode 문자로 대체를 하기 때문에 XML 태그 사이에 CR이 붙은 경우에는 XML 파싱 자체가 되지 않습니다.

6. 관련 문서 및 링크

- 다운로드: ftp://ftp.cubrid.org/CUBRID_Tools/CUBRID_Query_Browser/
- 릴리스노트: http://www.cubrid.org/wiki_tools/entry/cubrid-migration-toolkit-release-note_kr
- 매뉴얼: http://www.cubrid.org/wiki_tools/entry/cubrid-migration-toolkit-getting-started_kr
- 프로젝트: http://www.cubrid.org/wiki_tools/entry/cubrid-migration-toolkit
- 이슈트래커: http://jira.cubrid.org/browse/TOOLS/component/10002

• [CUBRID PHP Driver Installation Instructions]

Tutorials and Guides

• What is Tread-safe or Non-thread-safe in PHP? - Stackoverflow
• [Install CUBRID with Apache and PHP on Ubuntu]
• CUBRID vs. MySQL PHP API Functions Comparison
• CUBRID MySQL PHP Compatibility library
• [!Solved] PHP Warning: PHP Startup: Unable to load dynamic library '/usr/lib/php5/20060613+lfs/cubrid.so' - libcascci.so.8: cannot open shared object file: No such file or directory in Unknown on line 0. - Forum Thread

Video Tutorials

• PHP API for CUBRID

Questions and Answers

• PHP related Questions and Answers

Functionality added:

The following functions have been added:

• cubrid_pconnect
• cubrid_pconnect_with_url
• cubrid_set_query_timeout
• cubrid_get_query_timeout

Changed and Enhanced Features:

1. APIS-23 - Add persistent connection
   
   We add two functions, cubrid_pconnect and cubrid_pconnect_with_url, to provide persistent database connections. The parameters of cubrid_pconnect are same with cubrid_connect, and so do cubrid_pconnect_with_url and cubrid_connect_with_url.
   
   
2. APIS-43 - Add functions about getting and setting the query timeout time
   
   If database queries are taking too long to perform, and your application is becoming unresponsive, you can configure a timeout for database queries. We add two functions (cubrid_get_query_timeout and cubrid_set_query_timeout) to get and set the query timeout of database queries.
   
   
3.  APIS-41 - Reuse the connection established
   
   For mysql, if a second call is made to mysql_connect() with the same arguments, no new link will be established, but instead, the connect identifier of the already opened connection will be returned. The new_link parameter modifies this behavior and makes mysql_connect() always open a new connection, even if mysql_connect() was called before with the same parameters.
   
   To make compatibility with mysql, we add the new_link parameter in cubrid_connect and cubrid_connect_with_url.
   
   
4. APIS-45 - Add a form of the url parameter for cubrid_connect_with_url function
   
   Support the way without "cci:" in url parameter, that is the url become "CUBRID:host:db_name:db_user:......."

Fixed bugs:

• APIS-44 - Fix a bug in cubrid_fetch, cubrid_fetch_row, cubrid_fetch_arry and cubrid_fetch_assoc: Modified the return value when there are no more data

CUBRID 8.4.1 is available for download right now!

Thanks to all of those who have reported bugs, CUBRID developers have done really great job on improving both the performance and stability of the database server. While performing tests on large amount of transaction, performance of INSERT and UPDATE was improved over 70%.

Also, according to your requests we have added many new functions and SQL syntaxes to make CUBRID more compatible with MySQL. Moreover, regular expressions are now supported in conditional search, broker parameters are added, and monitoring features have been improved. In addition, approximately 50 major and minor bugs have been fixed.

Below I will list new features and major changes in this new release.

Improved Performance of INSERT and UPDATE more than 70%

(y-axis refers to the number of queries per second)

In CUBRID 8.4.1 we have improved the internal implementation of the Engine to enhance the performance during simultaneous processing of transaction logs, writing memory buffers to a disk, and performing replication for HA. Consequently, the performance of INSERT and UPDATE operations was dramatically improved over 70% in comparison with 2008 R4.0 Patch 2 version.

The following table illustrates the overall performance increase gained in CUBRID 8.4.1.

The test has been conducted on large amount of transactions based on YCSB (Yahoo Cloud Serving Benchmark). For more information on performance test, refer to section 2.2.2 in CUBRID 2008 R4.1 QA Completion Report.

New SQL Functions and Regular Expression Support

• In this version we have added new SQL functions: ADDTIME, ASCII, BIN, CONV, FIND_IN_SET, HEX, and SERIAL_NEXT_VALUE (serial_name, number) functions, which can be used to obtain multiple serial values with a single call.
• Added the REGEXP operator in order to allow conditions to be searched with regular expressions.
• DATE, DATETIME, and TIMESTAMP data types now support '0000-00-00', '0000-00-00 00:00:00' lower bound values. This provides more compatibility with MySQL's SQL syntax.

More Features

The full list of new features, improvements, and fixes can be found the in CUBRID 2008 R4.1 Release Note.

Software Requirements

Since CUBRID Manager is implemented in Java, it requires Java Runtime Environment or Java Development Kit version 1.6 or later.

• Download JRE or JDK from http://java.sun.com/javase/downloads/index.jsp.

Installation

CMT Installation is very easy. Just extract both archives (CMT Server and CMT Client) to the desired location.

• Prepare a source database in MySQL or other DBMS which you would like to migrate to CUBRID.
• Start the CMT Server:
• Open Command Line Terminal and navigate to the location where the CMT Server has been installed. In my case, I have installed it to C:/cubridmigration_server.
• Set CMT_HOME environment variable by typing the following command.
  set CMT_HOME=c:cubridmigration_server
• Start the CMT Server by typing the following command.
  cmt_server start
• Start the CMT Client:
• Open the directory where the CMT Client has been installed and run the cubridmigration application.
• When you launch CMT for the first time, you will be shown the BSD license, which prompts you to agree upon.

For more detailed documentation and guide see the CMT Release Note.

Support

If you have any difficulties working with CUBRID Migration Toolkit, post your questions to CUBRID Q&A site.

• Includes all versions of CUBRID JDBC Driver, thus you can connect to any CUBRID database.
• Provides very convenient authentication and host management by allowing to group hosts, save login information and auto-login.
• Provides improved customization. User can set the preferences for CQB exit behavior, adjust Query Editor options such as capitalization of keywords or function names.
• Provides all the capability of CM's Query Editor and Execution tools. Includes the list of new keywords and function names.
• Provides improved Data Import and Export functions. Now it can be executed in multiple threads based on user preferences for increased performance.
• Can run as a standalone application or as an Eclipse IDE plugin.

Edit and Execute SQL Statements: 

Users can connect to CUBRID databases, create, edit and execute SQL scripts, check their results through various CUBRID JDBC drivers. Here is a detailed list of operations you can run in the CQB.

Manage CUBRID Database Objects with UI:

The CQB includes serial UIs for creating/editing/dropping tables/views/triggers/serials/functions/procedures of CUBRID Databases. Here is a detailed list of operations on these objects.

• Includes all versions of CUBRID JDBC Driver, thus you can connect to any CUBRID database.
• Allows to create and manage unlimited number of databases and database volumes.
• Provides both powerful and convenient users and groups management. Users can create and manage both CM users and database users.
• Allows to create and manage tables, columns, and rows, create views, triggers, serials, and stored procedures.
• Provides the powerful Query Editor and Execution tools which allow to retrieve and enter data by using prepared SQL statements.
• Provides very convenient authentication and host management by allowing to group hosts, save login information and auto-login.
• Provides improved Data Import and Export functions to various formats.
• Provides the powerful Data Backup and Restore features.
• Provides a convenient way to manage Brokers and Logs.
• Provides a built-in HA (High-Availability) Monitoring feature.
• Provides improved operating convenience: error tracking based on logs,
• Provides improved customization. User can set the preferences for CQB exit behavior, adjust Query Editor options such as capitalization of keywords or function names.
• Provides enhanced settings for environment variables: Server, Broker, CM, HA related parameters.
• Provides improved hosts panel functions. Displays tooltips on hover, drag and drop feature, grouping, filter to hide desired items or search, display table schema as children nodes.
• Provides a plugin support for nLucene full-text search engine.

Build Steps

1. Download Eclipse version 3.6 from Eclipse.org

2. Download Eclipse Delta Pack version 3.6

3. Download Babel language pack for Helios (3.6)

• BabelLanguagePack-eclipse-ko_****
• BabelLanguagePack-rt.equinox.p2-ko_****
• BabelLanguagePack-tools.gef-ko_****

4. Extract Eclipse

5. Extract Eclipse Delta pack to eclipse/dropins/delta/

 6. Extract Babel language pack to eclipse/dropins/language/

7. Download and copy org.apache.log4j_1.2.13.v200806030600.jar into eclipse/plugin.

8. Checkout CUBRID Manager sources into src/.

• ex) branches/RB-8.4.0.3xxx/client

9. Execute Eclipse.app

10. Open projects

11. On the left panel choose com.cubrid.cubridmanager.dependence.feature/feature.xml. Then click Plug-ins tab, then press Versions… button.

12. Save file

13. Choose com.cubrid.common.update.feature/feature.xml. Click Plug-ins tab, click Versions... button.

14. Save file

15. Exit Eclipse

16. Copy buildProduct.sh into src/ on com.cubrid.cubridmanager.build/.

 17. Fix ECLIPSE_HOME path with eclipse directory in buildProduct.sh

18. Fix BUILD_DIR path for a source path

19. Remove SVN relation part

#!/bin/bash

TOP_DIR=${1}
if [ -z "$TOP_DIR" ];
then
BUILD_HOME=`pwd`
else
BUILD_HOME=`cd ${TOP_DIR} && pwd`
fi

ECLIPSE_HOME=/Users/pcraft/Dev/Build/eclipse
PRODUCT_NAME=CUBRIDManager
BUILD_DIR=${BUILD_HOME}/client/com.cubrid.cubridmanager.build

CUR_VER_DIR=`date +%Y%m%d`
OUTPUT_DIR=${BUILD_HOME}/${CUR_VER_DIR}
rm -rf ${OUTPUT_DIR}
mkdir -p ${OUTPUT_DIR}

chmod ugo+x ${BUILD_DIR}/installer/linux/*.sh

java -jar ${ECLIPSE_HOME}/plugins/org.eclipse.equinox.launcher_1.1.0.v20100507.jar -application org.eclipse.ant.core.antRunner -buildfile ${BUILD_DIR}/buildProduct.xml -Doutput.path=${OUTPUT_DIR} -Declipse.home=${ECLIPSE_HOME} distlinux

cd ${BUILD_HOME}/client
tar -czf ${OUTPUT_DIR}/${GZ_SOURCE_FILE} *
cd ${BUILD_HOME}

20. Execute the buildProduct.sh

21. When the build is finished, you will see binaries in a folder named as the current date.

1． Overview

2． Current Build

1.5.5.4401

3． Test Plan

      ■ CUBRID Migration 1.5.5

      Note:

QA schedule was delayed for 3 days as new feature requirement was added and bug fixing postpone.

4． Test Scope

[Bug-List]

5． Test Cases

6． Bug Status

         Note:

 The number of list verified includes the bugs in test scope and the bugs which has reported in the version.

7． Known issue

          Note:

          The issues of CUBRID Migration will be fixed in the future.

Supported CUBRID version

• CUBRID 8.2.2.x ~ CUBRID 8.4.1.0558

Compatibility fixes

• [TOOLS-569] - Supports CUBRID Manager Server of CUBRID 8.4.1.
• [TOOLS-431] - Supports default menus (Preferences, Application) on Mac.
• [TOOLS-600] - Changed the versioning policy to make easier to find the correct and compatible version for CUBRID DBMS.
  

CUBRID Query Browser 1.2.2(2011-11-09)

Improvements and bug fixes

• TOOLS-108 - Cannot install cubrid query browser on ubuntu natty from sh script
• TOOLS-195 - When creating a table with column in CM's UI menu, it displays column types with a random order

CUBRID Query Browser 1.2.1(2011-10-04)

New features

• TOOLS-35 - Import connection information from lower version of CM

Improvements and bug fixes

• TOOLS-104 - CM/CQB's conf file and log information file should be separately stored in a certain folder so that easily user can save it.
• TOOLS-119 - When importing file, the 2nd, 3rd file location should follow the 1st file location.
• TOOLS-49 - Selecting column values from the multiple tables and export the result into the EXCEL file at Once
• TOOLS-8 - Even when a database is OFF, Query Editor should not be started.
• TOOLS-14 - When AUTOCOMMIT=OFF in the query editor and executing CREATE TABLE, Commit icon becomes disable state
• TOOLS-13 - drag and drop table to query editor, generated SQL has syntax error when the table have no any columns
• TOOLS-101 - CQ cannot install in ubuntu linux which installed OpenJDK.
• TOOLS-100 - In CQB, JDBC doesn't display according some order.
• TOOLS-120 - In query editor, choose one database which has stopped, it pop Error Message:null.
• TOOLS-49 - Selecting column values from the multiple tables and export the result into the EXCEL file at once
• TOOLS-25 - When import data, cannot import the single quote directly

CUBRID Query Browser 1.2.0(2011-08-19)

New features

• TOOLS-4 - Auto update - Auto check new version when CUBRID Query Browser starting, and prompt user to update.
• TOOLS-6 - Bug report - Support bug reporting.
• Software install base on Eclipse framework - Can install other software to CUBRID Query Browser that developed as Eclipse plugins.

CUBRID Query Browser 1.1.0(2011-07-01)

• CUBRID-Query-Browser-1.1-Release-Note-en.pdf

CUBRID Query Browser 1.0.0

• CUBRID-Query-Browser-1.0.0-Release-Note-en.pdf

CQB is distributed under the terms of BSD open source license.

4. User Management

Like registering multiple users and managing their authorization in a single database, multiple users can be registered and their authorization can be managed in a single Manager server.

Information on the CUBRID Manager users is stored in the CUBRID Manager server. Therefore, to access the host, you must acquire the authorization to use the CUBRID Manager before connecting to the host.

Only the admin account and general user accounts registered by admin can connect to the CUBRID Manager. Only admin can perform CUBRID Manager user management. To do this, select [Tools] > [User Management].

In [User Management], you can set each user's authority as follows:

DB Creation Authority

• admin : Authorization to create a new database. Only the admin user is granted with this authorization.
• none : No authorization.
  

Broker Authority

• admin : Authorization to start/stop, add, edit, delete the Broker.
• monitor : Authorization to monitor the progress of the Broker with the view status function.
• none : No authorization.
  

Status Monitor Authority

• admin : Authorization to perform, add, edit, and delete status monitoring.
• monitor : Authorization to monitor the progress of a status monitor.
• none : No authorization.

4.1. Add User

To add a user, you need to specify the user account information and authorization, and database access authority.

Setting User Account and Authority

• User name : The length of a user name must be between 4 and 32 characters. A user name can contain only alphanumeric character. Do not use spaces. "admin" cannot be used as a user name, and it must be unique in the host.
• Password : The length of a password must be between 4 and 32 characters. Do not use spaces. "admin" cannot be used as a password.

• Connected : Select databases that the CUBRID Manager user being added can access. Only the databases with the [Yes] option selected are displayed in the host's navigation tree.
• Database User : Enter database account information that is used when the CUBRID Manager user being added accesses the database. You can enter values such as "dba" or "public."
• Broker IP : Enter the Broker IP that is used when connecting to the database. The default value is set to the address of the database server. If there is a separate Broker server, this value can be edited to provide access information.
• Broker Port : Specify a Broker port that is used when the CUBRID Manager user being added accesses the database. You can check the port information of the Broker through the Broker properties. The Broker information consists of "Broker name[Port/Status]."

4.2. Edit User

You can select a user from the user list and edit it as you add a user. However, editing the admin account is limited to changing its password. Other authorization for the admin account cannot be edited.

4.3. Delete User

To delete a user, select the user from the user list and then click the [Delete] button. Note that the admin account cannot be deleted.

5. Database

Connecting to Database

To run a database, you need to log into the database first. In the host navigation tree, right-click a database and select [Login Database] or double-click the database.

Enter a user name and password in the [Login Database] window. The default user name is dba; no password is required. If you want to save password at local machine, you can check the [Save Password] in order to log in this database by double-clicking this database node.

After user authorization is verified in the database login process, a tree corresponding to the user's authorization is displayed. To start the database, right-click the database in the left navigation tree and then sent [Start Database]. While the database is running, you can add a user or change the current password by right-clicking the [Users] node.

In the CUBRID Manager is not normally running, the following error message will be displayed: Cannot connect to a server. Please check the configuration environment of the CUBRID Manager server and other connection. In this case, you solve the problem by checking the following:

• Check whether the CUBRID Manager server is running.
• Open the configuration file of the CUBRID Manager server, and make sure that the value of the cm_port parameter is identical to the registered connection port. See Configuration the CUBRID Manager Server.
• If a firewall is installed on the system where the Manager client is running, allow all connection ports to be accessed to the Manager client connection (cm_port, cm_port+1). For example, if cm_port is 8001, the port 8002 must also be open.
• When the same operation is already being executed by the server, the message "Cannot execute the current operation because the previous operation is already running." is displayed. Then, retry the operation.
• When connecting Broker and a database in the CUBRID Manager client, the IP network between Broker and a database may be seperated. In that case, you must configure different addresses for the database and Broker in the Connection Information of the Database Property. To change connection information, right-click in the navigation tree and then select [Properties].

Starting Database

To execute a query in the CUBRID Manager, the database must start or be running. To start a database, select the database to start and click [Start Database] in the toolbar.

Creating Database

You can create a database by using the shortcut menu, or by clicking [Create Database] from the toolbar at the top. The Create Database wizard consists of 5 steps.

Step 1 : General Information
Enter the basic information such as database name, the generic and log volumes.

• Database name : The name of a database must be unique in the host. A warning message is displayed when the name already exists. The following rules apply to database names:
• • Only alphanumeric are allowed for the name of the database. Its maximum length is 16 characters.
  • Special characters that cannot be used in file names on Linux/UNIX are not allowed: space, *, &, %, $, |, ^, /, ~,
  • "." and ".." cannot be used in the name of the database.
• Page size : Select one of the following sizes: 1024, 2048, 4096, 8192, 16384. The default value is 4096. Select an appropriate size for the purpose of the database since the size cannot be changed once the database is created. It is recommended to use the default value unless it is an exceptional case.
• Generic Volume Information : When the size of generic volume is entered in Mbytes, the number of pages for the volume is automatically calculated and displayed. The default value of a generic volume path is specified in the database location file ($CUBRID_DATABASES/databases.txt). When the database is being created on the server as the CUBRID Manager server, you can select a directory by clicking [Browse].
• Log Volume Information : Enter the size and path of the log volume. The default log volume path is the same as generic volume path.

Step 2 : Additional Volume Information
Enter information of additional volume by type such as generic, data, index, temp. In order to use the Automation of adding volume function for each volume type, you must configure the data volume and index volume.

• Additional Volume Information : If an additional volume is expected during the database creation, set information about the volume to be added in this step. If you click [Add volume] after entering the name, path, type and size of the volume to be added, the new volume is added accordingly. You can specify a volume type for each purpose, such as data, index, temp, and generic. You must additionally enter the data volume and index volume of an additional volume.
• Add volume/Delete volume : If you click [Add volume], the volume to be added is displayed on the list. If you click [Delete volume] after selecting a volume from the list, the volume is not created.
• Current additional volume list : Displays the list of volumes to be added during database creation.

Step 3 : Automation of Adding Volume
Enter information used for the automatic addition feature when data or index volumes do not have enough space. The automatic addition functionality can be used for a data or an index volume.

• Using automatic addition volume : When it is selected, the automatic addition functionality is used for the selected volume type.
• Out of space warning rate : A volume is added automatically when the remaining volume equals to the value set by [Out of space warning rate]. For example, if this value is set to 15 % and the remaining space of the volume is 15 %, a data volume is added automatically. The minimum value is 15, and the maximum is 30.
• Volume size : Enter the size of the volume to be added automatically.

Step 4 : Set DBA Password
Enter the password for the DBA account of the database being created. The password cannot contain any spaces, and must be at least 4 characters.

Step 5 : Database Information
Confirm the information entered up to step 4 and create the database. If you need to make a change, click [Back] to go back to the previous step.

Load Database

To load the unloaded data into the currently selected database, perform one of the following after login to the database.

• Click [Load Database] from the toolbar.
• Right-click the database and then select [Load Database].
• Select [Action] > [Load Database] on the menu.

The load database operation can be performed only when the database server is not running; The [Restore Database] menu is deactivated while the database is running.

• Database Information : Displays the name of the target database into which the unloaded data is to be loaded, and the authority of the user who is logged in to the database. You must specify the name of currently logged-in user in the [User name] field.
• Unloaded Target : Enter information of the unloaded data. You can either select from the list or directly enter the path where the unloaded file is located.
• If the CUBRID Manager client and server are running on different systems, unloaded schema, object, index and trigger files must exist on the system running the CUBRID Manager server.If there is already any unloaded data from the CUBRID Manager, you can use unload information to load. Otherwise, manually enter unload information and then load it.
• Load Option : You can select whether to perform syntax checking before loading data, or perform syntax checking only. For more information, see "Loading Database."

To check the results of the database load operation, set options and then click the [OK] button in the [Database load] dialog box.

Unload Database

To unload data of the selected database, perform one of the following after login to the database.

• Click [Unload Database] from the toolbar.
• Right-click the database and then select [Unload Database].
• Select [Action] > [Unload Database] on the menu.

The unload operation can be performed even when the database server is running.

• Database Information : The name of the database to be unloaded is displayed. Specify the directory in which a file is to be created after the unload operation.
• Unload Target : Select the schema and data of the database to be unloaded.
• Unload Option : You can specify whether to use delimited identifiers (“”) or how many LO files are to be stored in a single directory. For more information, see "Unloading Database."

To check the results of the database unload operation, set options and then click the [OK] button in the [Unload Database] dialog box.

Backup Database

To backup a database, perform one of the following after login to the database.

• Click [Backup Database] from the toolbar.
• Right-click the database and then select [Backup Database].
• Select [Action] > [Backup Database] on the menu.

The backup operation can be performed even when the database server is running. For more information, see "Database Backup" in the CUBRID online manual.

• Database name : The name of the database to backup.
• Volume name : Specifies the name of the backup volume. The default volume name is in the form of [database name_backup_backup level]. However, you can change the name.
• Backup level : Specifies the backup level. Level0 is a full backup, Level1 is a backup that saves changes made only after the Level0 backup. Level2 is a backup that saves changes made only after the level 1 backup.
  For example, if there is a backup volume displayed as Level0, the administrator can choose only Level0 or Level1. If there are no previously performed backups, the administrator can choose only Level0.
• Backup directory : Specifies the directory where backup files are to be saved. The default is set to the CUBRID/databases/[DBNAME]/backup directory.
• Checking consistency of the database : Checks consistency of the database to backup before the backup process. It is recommended to select this option.
• Delete unnecessary log-archives : Deletes unnecessary archive log files while restoring a database. Note that archive log files might be required if database restore does not go well due to backup file errors. When this option is selected while the database is set to the master server in the replication environment, the Maintain replication log option is checked automatically.
• Number thread : Specifies the number of threads to be used concurrently during the database backup. It is recommended to set the maximum number of threads to be the same as the number of CPUs. The default value is 0, in which case the number of threads is automatically determined.
• Compress backup volumes : Compresses the database backup. It is recommended to select this option.

If a backup has been executed for the target database, you can check the backup history from the [Backup History Information] tab. You can also check information such as the backup level, last backup date, size of the backup file, backup file path as well as free space of the disk where the current database volume exists.

Restore Database

To restore a database, perform one of the following after login to the database.

• Click [Restore Database] from the toolbar.
• Right-click the database and then select [Restore Database].
• Select [Action] > [Restore Database] on the menu.

Loading data to restore database can be performed only when the database server is not running; The [Restore Database] menu is deactivated while the database is running.

For more information, see "Database Backup" in the CUBRID online manual.

• Database name : The name of the target database to be restored.
• Restored Date and Time : Specifies to which point of time the database is to be restored back to. If you select [Backup time], a restore is performed with the backuptime keyword in the restore utility. This means that the database is restored to the point when the backup was complete. If you select [Specify a restore date], you can enter date and time you want.
• Available Backup Information : You can select the restore level after checking which levels of backing up have been performed on the target database. The specified file path is the path to the directory where the files for the back up for the selected level are located.
• Perform partial restore if any log archive is absent : Performs a partial restore if the case of incomplete log information. That is, database restore can be performed even without archive or active logs created after the backup point.
• Restore to a path specified by the user : Restores the database to the path specified in the database location file (databases.txt).
• Show backup information : Shows the information of the file backed up to the selected backup level.

Rename Database

To rename a database, perform one of the following after login to the database.

• Right-click the database and then select [Rename Database].
• Select [Action] > [Rename Database] on the menu.

The rename database operation can be performed only when the database server is not running. Therefore, the [Rename Database] menu is deactivated while the database is running.

For more information about renaming databases, see "Renaming Database."

• New database name : Enter a new name for the database to be renamed.
• Force to delete backup volumes : Delete backup volumes of the database before the rename operation.
• Extended volume path : An option that specifies the path in which volumes to be added to the new database are stored.
• Rename individual volumes : If there are multiple volumes before renaming the database, you can rename individual database volumes and specify a new directory in which each database volume is stored.

Copy Database

To copy the database, perform one of the following after login to the database.

• Right-click the database and then select [Copy Database].
• Select [Action] > [Copy Database] on the menu.

The copy database operation can be performed only when the database server is not running. Therefore, the [Copy Database] menu is deactivated while the database is running.

• Source database : A database name to be copied and a directory path where the volume and log file saved are shown.
• Destination database : Enter a database name to be created and a directory path where the volume, extended volume, and log file to be stored.
• Copy individual volumes : If there is more than one volume of the source database, you can rename each database volume and specify a new directory path to which each database volume is to be copied.
• Replace an existing database : Overwrites an existing database of the same name as the destination database.
• Delete a source database : Deletes the source database after copying.

Optimize Database

To optimize the database, perform one of the following after login to the database.

• Click [Optimize Database] from the toolbar.
• Right-click the database and then select [Optimize Database].
• Select [Action] > [Optimize Database] on the menu.

In the [Optimize table] dialog box, you can perform optimization for all or some tables in the database. Select the target to optimize and click [OK] to start database optimization. If you select [See Detailed Progress], detailed information is displayed when the compact database operation is completed.

Compact Database

To compact the database, perform one of the following after login to the database.

• Right-click the database and then select [Compact Database].
• Select [Action] > [Compact Database] on the menu.

The compact database operation can be performed only when the database server is not running; The [Compact Database] menu is deactivated while the database is running.

Check Database

To check the database, perform one of the following after login to the database.

• Click [Check Database] from the toolbar.
• Right-click the database and then select [Check Database].
• Select [Action] > [Check Database] on the menu.

Database Lock Information

To view the lock information of the database, perform one of the following after login to the database.

• Click [Lock Information ] from the toolbar.
• Right-click the database and then select [Lock Information].
• Select [Action] > [Lock Information] on the menu.

Note that this function is activated only while the database server is running; this is deactivated while the server is not running.

The [Lock Information] dialog box consists of two tabs.

The [Lock setting/client information] tab provides information of the clients currently connected to the database.

In the [Object lock table] tab, you can check the lock information of the database objects.

You can view detailed lock information by clicking [Detail] in the [Object lock table] tab.

Database Transaction Information

To view the transaction information of the database, perform one of the following after login to the database.

• Click [Transaction Info] from the toolbar.
• Right-click the database and then select [Transaction Info].
• Select [Action] > [Transaction Info] on the menu.

Note that this function is activated only while the database server is running; this is deactivated while the server is not running.

• Refresh : Recollects and shows information of the transactions currently being performed by the CUBRID Manager server.
• Kill transaction : Forces termination of the transaction selected in the transaction list. One of the following four options can be selected.

Delete Database

To delete a database, perform one of the following after login to the database.

• Right-click the database and then select [Delete Database].
• Select [Action] > [Delete Database] on the menu.

The delete database operation can be performed only when the database server is not running; The [Delete Database] menu is deactivated while the database is running.

If you click [OK], the database is deleted after checking the dba password. Only the dba user can delete a database.

6. Database objects

6.1. User

You can add, edit or drop users by right-clicking [Users] in the navigation tree after login to the database. All users of the current database are displayed in the sub-node of [Users].

Create User

You can add a user by right-clicking [Users] in the navigation tree and then selecting [Create User] or by clicking [Create User] from the toolbar menu.

General User Information

• User name/Password : The name and password of the user to be added. The maximum length of the user name is 32 characters.
• All users : Lists the list of users that can be selected as the group for the user to be added.
• Authorization of this user : Displays the list of groups of users to be added. You can specify a group with which users to add from the [All users] list will join by using the arrow button. However, you cannot modify the authorization of dba and public accounts.
• Users that have this user's authorization : Displays the list of users that have this user's authorization.

User Authorization Information

In the [User authorization information] tab, you can grant or revoke authorization for each table. You can sort authorization grantees for each column and select multiple tables to grant authorization.

Edit User

You can edit the settings entered in the [Add User] dialog box. However, the user name cannot be modified.

Drop User

You can drop the selected database user account.

6.2. Table

When you log in to the database, you can see accessible tables and system tables and columns and index in the navigation tree.

If you right-click the [Table] in the navigation tree, you can view the [Create Table], [Create Like Table], and [Refresh] menus.

Create Table

Right-click [Tables] in the navigation tree and then select [Create Table] or click [Create Table] from the toolbar. Then, a wizard which makes you create a new table will appear.

• [General] tab : You can define the name of the table to be added and add, edit and drop columns. You can also set the primary key (PK) and, before the table is created, adjust the position of the selected column by using [↑] and [↓].
  Using the add column wizard, you can set the name, type, default value and constraints of the column to be added. You can also set to display a warning message when you enter something that is not grammatically correct, or to disable the selection of a grammatically incorrect entry.
• • Reuse_OID : If this option is selected, a table is created with the option REUSE_OID applied. For this kind of table, using with OID is restricted. For more information on OID reuse table, see "Table Options (REUSE_OID)" in the CUBRID online manual.
• [FK/Indexes] tab : You can set foreign keys and indexes.
• • Add Foreign Key : Using the add foreign key wizard, you can set the name of the foreign key, the name and primary key of the reference table and the trigger actions to maintain referential integrity. The ON UPDATE, ON DELETE and ON CACHE OBJECT options are provided.
  • Add Index : You can set index name, index type, a column to be indexed. Ascending (asc) and descending (desc) sorting can be selected within the supported range. For REVERSE indexes, only descending sorting is supported.
• [Partition] Tab : Supports partitioning setting and modification of the given table.
• • Add Partition : Using the add partition wizard, you can set the partition type and expression. The RANGE, LIST and HASH partitions are supported.
  • Edit/Delete Partition : You can edit or delete partition.
• [SQL Statement] Tab : You can check and copy SQL statements created according to the settings in [General], [Foreign Key/Index] and [Partition] tabs.

Adding Object Oriented Tables

To add a table with object-oriented properties, select [Show object oriented related properties]. When you select [Show object oriented related properties], the Inheritance tab is added.

• [General] tab : When you select [Show object oriented related properties], Shared, Inheritance and Table column are added as a column in the table. When adding or editing columns, you can choose the column type as shown in the figure below. You can choose OBJECT or a table in the database as the data type.
• [Inheritance] tab : You can define the super table to inherit from. If a column name conflict occurs, it can be adjusted.

Select All

Right-click a table in the navigation tree and select [Select All]. Or you can drag and drop the table into the editor results pane of the Query editor when it is open. Then, a new Query editor opens and retrieves the entire data.

Select Count

Retrieves a total data count of the table and performs the same functionality as the following syntax.

SELECT COUNT(*) FROM table_name

DELETE ALL

Deletes all records from the table and performs the same functionality as the following syntax.

DELETE FROM table_name

TRUNCATE TABLE

Deletes entire data in the table. It can delete all records including indexes and constraints in a table, so it is faster than [DELETE ALL]. The ON DELETE trigger is not activated when you use the [TRUNCATE TABLE]. It can perform the same functionality as the following syntax.

TRUNCATE TABLE table_name

Insert Records

You can insert values for each column while checking its type and constraints.

• When you add more than one instance, you can separate them by adding a line break character between each query and its result.
• You can move the cursor to the next field by pressing the [Enter] key when you enter a value for each field.
• When you click the [Clear] button, the value in the input box and the execution history are initialized.
• The execution history pane cannot be edited.
• For DATE, TIME, TIMESTAMP and DATETIME data types, you can enter different data for each type. For example, for a DATE type, you can enter data such as SYSDATE, SYS_DATE, CURRENT_DATE and DATE'2009-07-05'.

Import Data

You can import data from an Excel or CSV file into the database. You can use [File charset] to get data from a file, and use [JDBC charset] to specify charset for data to be stored in the database. To change the value for [JDBC charset], right-click the mouse and then select [Properties].

By selecting [Ignore] or [Break], you can change the way when an error occurs in the process of import.

Export Data

You can export data (usually in one or more tables) in Excel (.xls), CSV, SQL, or CUBRID load (.obs) format. A file name is created with a table name and it is saved in the path specified in [File path]. You can choose [File charset] when exporting data.

Drop Table

Drops the selected table. This is the same as the DROP TABLE statement.

Rename Table

You can change the name of the current table. It is the same as RENAME TABLE statement.

Create Like Table

Creates an empty table which has the same schema structure with an existing one. It works the same as CREATE TABLE LIKE. For more information, see "CREATE TABLE LIKE" in the CUBRID online manual.

Edit Table

You can use all functionalities of [Create Table] in [Edit Table] as well. However, you cannot adjust the order of columns in the table.

Table Information

You can check the schema information of the table by double-clicking it.

Execute Defined SQL

With [Execute Defined SQL] menu, you can execute "prepared statement," pre-saving a specific query statement and specifying a new parameter value for the statement whenever the query is executed.

You can execute the SELECT statement which meets specified conditions by entering a parameter value of defined "prepared statement" by using [Select by input value].

You can execute the INSERT statement by entering a parameter value of defined "prepared statement" by using [Insert by input value].

You can use [Select by read file] when repeating the execution of SELECT statement by inputting several parameter values in the defined "prepared statement." The data is saved in Excel (.xls) or CSV format. You can configure a  file charset where parameter values are saved, the number of concurrent threads to be executed, and commit cycle. To change the value for [JDBC charset], right-click the mouse in Explorer and then select [Properties].

You can use [Insert by read file] when repeating the execution of INSERT statement by inputting several parameter values in the defined "prepared statement." The data is saved in Excel (.xls) or CSV format. You can configure a  file charset where parameter values are saved, the number of concurrent threads to be executed, and commit cycle. To change the value for [JDBC charset], right-click the mouse in Explorer and then select [Properties].

Copy SQL to Editor

A convenient function is provided that allows you to copy DDL and DML in a selected table to the current editor. If there is no editor opened, a new editor will opened and show the DDL or DML in it. The text in menu item gives the format of the statement. You can modify it based upon your requirements. INSERT, SELECT, CREATE, UPDATE, DELETE and GRANT statements are included.

Copy SQL to Clipboard

Like [Copy SQL to Editor], you can copy DDL and DML in a selected table. But the difference is the object address is clipboard.

Copy SQL to File

You can copy DDL and DML in a selected table to a given file.

6.3. View

When you login to the database, you can see accessible views and system views in the navigation tree.

Right-click [Views] in the navigation tree and then select [Create View].

Specify the view name and the owner, click the [Add] button, and then enter the query for the view to be created. You can check the contents entered in the Create View wizard from the SQL statement in the [SQL Script] tab.

6.4. Trigger

When you login to the database, you can view accessible triggers in the navigation tree.

Right-click [Triggers] in the navigation tree and then select [Create Trigger].

• Trigger name : Enter the name of the trigger to be added.
• Target table/Column : Enter the target table and column information.
• Event Time : Select the point of time when the condition of the trigger is to be evaluated. You can select from BEFORE, AFTER, and DEFERRED.
• Event Type : Select the type of the event to be occurred. Event types are INSERT, DELETE, UPDATE, STATEMENT INSERT, STATEMENT DELETE, STATEMENT UPDATE, COMMIT and ROLLBACK.
• Event Condition : Enter the condition for the trigger action.
• Execution Time : Specify the point of time when the trigger is to be executed. If default is selected, the trigger fires based on the point of time when its condition is validated.
• Action Type : Select the type of the trigger action. If the type of the trigger action is PRINT, OTHER or STATEMENT, you can enter additional information in the [SQL statements or print messages] below.
• Trigger Status : You can specify whether to activate or deactivate the trigger to be added.
• Trigger Priority : You can set the priority of the trigger. The priority value is a FLOAT and can be between 00.00 and 9999.99.

6.5. Serial

When you login to the database, you can view accessible serials in the navigation tree.

Right-click [Serials] in the navigation tree and then select [Create Serial].

The name of the serial must be unique in the database.

6.6. Stored Procedure

When you login to the database, you can view accessible stored procedures.

A feature that registers a function or procedure written in Java in the database server with the loadjava command and adds a database function or procedure in order to use the given Java function.

Right-click [Stored procedure] in the navigation tree and then select [Create Function] or [Create Procedure].

Only Java types compatible with the selected SQL type are displayed so that the user does not make a mistake with type mapping.

For more information, see "Java Stored Function/Procedure" in the CUBRID online manual.

6.7. Automation

Backup Automation

When you login to the database, you can view [Backup plan] under [Job automation] in the navigation tree. The [Add Backup Plan] and [Auto Backup Logs] menus will appear when you right-click [Backup plan].

If you want to execute a backup periodically with the CUBRID Manager, configure the values of [Add Backup Plan]. The DBA can configure the backup automation while the Manager server is running. It is not affected by whether the database is running or not. That is, backup automation is executed only when the Manager server is running.

• Backup ID : Enter the name of the backup job. The backup ID must be unique in the database because multiple backup plans may exist in the same database.
• Backup level : You can choose from 0, 1, and 2. Level0 is a full backup. Level1 is the first incremental backup that backs up changes made only after Level0 backup. Level2 is the second incremental backup that backs up changes made only after the Level1 backup.
• Backup path : Specifies the directory of the backup volume.
• Period type : You can select a backup period from options of Monthly, Weekly, Daily and A specific day.
• Period detail : You can set details for the period type you selected.
• Backup hour : Enter the time when the automated backup is to be executed. You must enter the time in hour and minute.
• Options : You can specify an option for backup. For more information, see "Database Backup" in the CUBRID online manual.
• • Store old backup file : This option saves the current original backup volume file of the database in database_directory/backupold directory.
  • Delete archive volumes : An option that deletes archive log volumes after backup. When this option is selected while the database is set to master server in the replication environment, volumes do not affect the replication will be deleted automatically.
  • Update statistics information : Updates statistics information after backup.
  • Checking database consistency : Checks database consistency during backup.
  • Use compress : Uses compression during backup.
  • Number thread : Specifies the number of threads to be used concurrently during backup. It is recommended to configure the maximum number of threads to be the same as the number of CPUs. The default value is 0. If it is set to the default value, the number of threads is determined automatically by the system.
• Online backup : Automated backup is executed only when the database is running. If the database stopped, only error logs are recorded without backing up the database.
• Offline backup : Automated backup is executed only when the database stopped running. Forces the database to shut down if it is currently running, performs an automated backup, and then restarts the database.

Auto Backup Log

Provides the error logs created during backup automation.

Query Automation

When you login to the database, you can view [Query plan] under [Job automation] in the navigation tree. The [Add Query Plan] and [Auto Query Logs] menus will appear when you right-click [Query plan].

If you want to execute a backup periodically with the CUBRID Manager, configure the values of [Add Query Plan]. The DBA can configure the backup automation while the Manager server is running. It is not affected by whether the database is running or not. That is, backup automation is executed only when the Manager server is running.

• Query Plan ID : Enter the name of the query job. The query plan ID must be unique in the database because multiple query plans may exist in the same database.
• User name/password : Enter the user name, which will execute the registered query automatically,  and its password. If you enter wrong information, the query is not automatically executed. Therefore, you must change the user information in the [Edit Query Plan] in case of password change.
• Period type : You can select a query automation period from options of Monthly, Weekly, Daily and A specific day.
• Period detail : You can set details for the period type you selected.
• Query hour : Enter the time when the query is to be executed automatically. You must enter the time in hour and minute.
• Query Statement : Enter the query statement to be executed automatically. Note that the registered query is executed automatically at the specified time, but the execution results are not recorded.
• Check Query : Check query errors before registering the auto-executed query statement. It determines whether it is an error or not by creating query plan it does not actually execute the query. It is working like executing optimization level 514 in the CSQL Interpreter.

Auto Query Log

You can view a log about queries that are automatically executed in the [Auto Query Logs]. Information such as a database, user ID, query ID, query hour, and error code (success : 0, failure : -1) is recorded.

6.8. Database Space

View Database

When you login to the database, you can view [Database space] in the navigation tree. With this option, you can select shortcut menus, such as View Database, Set Auto Add Volume, or Add Volume.

If you double-click a sub-node of [Database space] in the navigation tree, the volume information appears.

Set Auto Add Volume

• Volume purpose : The automatic addition functionality can be used for a data or an index volume.
• Using automatic volume addition : Use the automatic volume addition functionality for the selected volume type.
• Out of Space warning rate : A volume is added automatically when the remaining volume equals to the value set by [Out of Space warning rate]. For example, if this value is set to 15 % and the remaining space of the volume is 15 %, a data volume is added automatically. The minimum value is 15, and the maximum is 30.
• Volume size : Enter the size of the volume to be added automatically.

Add Volume

• Path : Enter the directory where the added volume is to be saved. The default value is the directory where the database volume is created.
• Purpose : Specify the type of the volume to be added. You can select from data, generic, index and temp.
• Volume size : Enter the size of the volume to be added. Its unit is MB.
• Pages : When the size is entered in Volume size, the number of pages for the volume is automatically calculated and displayed.

7. Query Editor

7.1. Query Editor Structure

The CUBRID Manager's Query Editor is a query tool that supports execution of all DML, DDL, DCL statements, allowing users to edit and execute queries more easily. To run the Query Editor, select [Tools] > [New Query] or select [New Query] from the toolbar. You can also right-click a specific database and then select [New Query].

If you select [New Query] by right clicking on a database, the default query editor is run with the basic information provided upon login to the corresponding database.

However, if you select it on the menu or toolbar, you can specify your login information by yourself to connect the database. The character set displayed on the screen is the same one that is specified for the database connection. You can log in setting the information of the database login, character set, and JDBC driver version. Note that separate configuration for broker connection is enabled in case a Broker is running in another server.

The Query Editor window is divided into a query edit pane at the top and a query results pane at the bottom. In the query edit pane, you can type and edit queries to execute with a toolbar that contains icons for frequently used functions in the Query Editor. In the query results pane, you can see the query results in a tab format and check the query execution time.

When you use multiple editors at the same time, it could more convenient to check the connection information in the title bar (at top) and in the status bar (at bottom) of the CUBRID Manager. Information that will be displayed is as follows: database, user name, broker port, and charset.

7.2. Query Results Pane

The query results pane displays the results of the query executed. If there are multiple queries executed, the results of each query are displayed in a separate tab. You can check the query results by selecting the corresponding tab.

The query results pane is divided into areas where you can navigate the results, view information of the executed query, and check execution time and the number of results returned by the query.

• Results search : You can navigate the entire search results while moving by the value set in [Page unit of result instances] of [Query options].
• Query execution information : Shows from which query the current result comes.
• Execution time and Number of hits : Provides information about the execution time on the server to get the current query results and total search count.

7.3. Query Results Pane functions

• Copy : Copies an entire row. To copy a specific column of the row only, select [View detail].
• Modify : The information can be modified directly from the query results pane. Change data to a modifiable state by double-clicking it, and then modify it. This option is available when [Get OID info] is set in the given host's Properties > [Query] dialog box, or [OID info] is specified.
• Delete : You can delete data directly in the query results pane. Right-click the row to delete and then select [Delete]. This option is available only when [Get OID info] is set as the modify function does.
• OID navigator : This option can be activated by right-clicking an OID data. It provides a function that allows you to navigate the selected OID directly.
• View detail : If there are too long data to be displayed in a single row, or if its size is too big, it is very difficult to see column values on the query results pane. In this case, you can see column values in detail by right-clicking the row and then selecting [View detail]. You can also modify data directly in the [Detail] dialog box if [Get OID info] option is set. For BLOB or CLOB type data, you can import and export it with a separate file.
• Export all : Exports all data in the query results pane to an Excel or a CSV file.
• Export selected : Exports only the data in the row selected in the query results pane to an Excel or a CSV file. The charset for a file where exported data is saved can be specified.
• Export BLOC/CLOB data : Exporting/importing data for BLOB, CLOB, BIT VARYING (>100) cannot be executed, but importing detailed information in the result pane of the Query Editor is possible. Note that only type tags such as (BLOB), (CLOB), and (BIT) are displayed in the result pane, instead of displying real data.
• Import BLOB/CLOB data : Entering or editing data in the detailed information of the result pane is supported by opening the file where type data of STRING, CHAR, VARCHAR, NCHAR, NCHAR VARYING, BIT VARYING, BIT, BLOB, and CLOB is saved.

7.4. Query Editor other functions

Executing Multiple Queries

Enter a semicolon at the end of the query statement to specify the end of one query and the start of the next. If there are multiple queries, they are executed sequentially. Each query creates a corresponding tab in the query results pane. If you execute multiple queries without separating them with semi-colons, only the first query is executed, with the rest ignored.

Cancel Query Function

A function that stops the currently running query. This can be divided into two functions.

• When executing multiple queries : If you click the Stop button when multiple queries are being executed with the auto commit button enabled, queries processed before the stop operation are reflected normally, and the currently canceled query and following ones are not reflected. If the auto commit button is not enabled, no executed queries are reflected.
• When executing a long transaction : If you click the Stop button when executing a long transaction, a query stop command is delivered to CUBRID Manager > JDBC > Broker > Server, and the query finally stops in the database server the query is actually canceled. For Windows, this function is supported in CUBRID 2008 R2.2 or later.

7.5. Query Execution Plan

If [Display query plan] is selected in the Query Editor's options, [Display query plan] becomes activated in the Query Editor toolbar.

You can check how the selected query will be executed, even without executing it, by clicking [Display query plan] from the toolbar or by clicking <Ctrl+L>. You can also check query execution plan that have already been executed.

Since query plans are displayed all the time at the bottom of the Query Editor window, you can check the existing query plans by opening query plan history files without connecting to the database.

The query plan function retrieves the SQL execution plans it is used not for a one-time purpose but for a collection purpose to continuously manage and retrieve them. Every time you retrieve a query plan, the query plan history is accumulated. You can save this accumulated data to an .xml file. When you open the saved .xml file, you can check the original query plan and executed SQL statements. If it is a one-time retrieval, select [Disable to collecting histories] to view the current query plan without recording history.

The [Query Explain] tab consists of a toolbar, query plan display pane, original statement display pane and query plan history pane.

Query Explain tab

If you select a query and then click [Display query plan], the query plan is displayed in the [Query Explain] tab. The [Query Explain] tab shows the query plan summarized in the tree structure.

The [Query Explain] tab is located to the right of the [Result] tab. You can switch to the [Query Explain] tab while viewing the query result.

Query Explain Toolbar

The Query Explain toolbar has the following functions:

• New : Initializes all query plan histories retrieved so far and begins collecting them again. This function is used to initialize the existing job.
• Open a query explain file : Imports a previously saved query plan history file. If you open the .xml file, you can view the original query plan.
• Save a query explain file, Save a query explain file as : Saves the collected query plan to an external file. The file extension is xml.
• Disable to collecting histories : Histories are added to the query plan history pane whenever you retrieve the execution plan by using [Display query plan] in the Query Editor. To retrieve a query plan temporarily without recording history, click [Disable to collecting histories]. The name of the tab below the query plan display pane is displayed as "plan."
• Query plan type : By toggling the icon, the type can be switched between text and tree. You can view the unprocessed query plan source created by the database in a text form.
• Show or Hide a query history pane : Shows or hides the collection history pane on the right side.
• Query plan history file : If a query plan history is saved as a file, or an existing file is opened, the name of the currently used query plan history file is displayed.

Query Plan Display Pane

In the query plan display pane, the query plan executed in each step is displayed in the tree structure.

Each item in the vertical axis is called a node. Each node contains different data. You can view the tree moving from the top to the bottom.

The horizontal axis is called an item and contains Type, Table, Index, Terms, CPU I/O cost, Disk I/O cost, and Total (ROW/PAGE).

• Type : Indicates the scan type or join method (such as sscan, iscan and idx-join).
• Table : The table (class), view (virtual class) and alias, which are referred to when the node is executed, are displayed altogether.
• Index : The name of the index used is displayed if the type is iscan.
• Terms : Join and filter conditions are displayed. The contents are hidden for readability. If you click +, sub-nodes are extended to show details. In addition, different colors are used for different search conditions.
• Cost : Displays CPU and Disk I/O cost of the query plan. Fixed and variable costs are displayed separately.
• Total (r/p) : Displays the total number of rows and the number of pages to be used to fetch data.

The original statements of the query plan selected in the query plan pane are displayed below the query plan display pane.

Query Plan History Pane

Histories are displayed accumulatively in the query plan history pane every time a query plan is executed. # is the accumulation order and corresponds to the tab number below the query plan display pane. Date indicates the date when a query plan is executed, and Cost is the sum of CPU and Disk I/O costs. If you double-click an item in the query plan history pane, you can view the query plan again in the query plan display pane.

Using Query Plans

By using the query plan function, you can analyze data while viewing the query plan and the schema info of the corresponding table.

If you right-click a row where a table is located in the query plan display pane and then select [Show Schema Info], you can open and view the schema information of the table as well.

You can also view the information in a separate window by dragging the Schema Info pane out of the CUBRID Manager. This can be useful in an environment using multiple monitors.

8. Broker

A Broker is a multi-function connector, enabling the connection between a database and many different interfaces such as ODBC, OLEDB, JDBC, PHP, etc. For more information, see "Administrator's Guide."

A Broker consists of the names of individually configured Brokers and their SQL logs.

8.1. Broker Function

A Broker may contain several individual Brokers. For each Broker, you need to set a unique name, port, and shared memory ID.

You can check the status, edit the properties, or start/stop each Broker.

8.2. SQL Logs

All the executed queries are stored in the log file when the SQL_LOG parameter of the Broker is ON. This log file can be analyzed and re-executed with the CUBRID Manager.

View Log

This function reads the SQL log stored in the selected SQL log file and displays 100 lines at a time. It also provides a function for selecting and copying a specific area of the log information.

Analyze Log

When [Analyze Sql Log] is selected, the [Select File(s) to Analyze] dialog box appears. You can select which Broker's SQL log is to be analyzed. When the [Transaction based analyze] check box is selected, the log is analyzed for each transaction; otherwise, they are analyzed for each query.

If you select the SQL log file you want and then [OK] in the [Select File(s) to Analyze] dialog box, the [Sql Log Analyze Result] dialog box which shows the results appears.

• Log File : Displays the file name and the directory path of the SQL log file of the target Broker.
• Analyze Result : Shows log analysis results. If [Transaction based analyze] is selected, each transaction's execution time is displayed; otherwise, analysis information (e.g. total number of executions, number of errors, maximum execution time, minimum execution time, average execution time) about each query is displayed. When you click a column in the analyze result section, the results are sorted by the value of that column.
• Log Script : Shows the log script for the analysis results.
• Execute Result : Shows the results of the log execution.
• Execute log : Re-executes the SQL log in the log script. You can tune queries and correct errors by modifying and re-executing log queries.
• Save log script : Saves the log script in a file.

Execute Log

If you select [Execute log], the [Set Execution Information] dialog box appears, in which you can configure the environment.

• Database name : Select the database for which the log is to be re-executed.
• Broker name : Select the Broker for which the log is to be re-executed.
• User ID/Password : Enter the ID and password of the database user that re-executes the log.
• Concurrent thread num : Specify the number of times to execute the log query concurrently. When the log is re-executed, threads are created as many as this number, and the same query is executed concurrently. This function is useful when you want to check how a query is executed in a multi-user environment.
• Repeat count : Specify the number of times to execute a query repeatedly.
• Show query result : Shows the results of the query execution.
• Show query plan : This option is valid only when [Show query result] is selected.

Log Property

Provides information of the selected log file.

9. Monitoring / Dashboard

9.1. Status Monitor

In the navigation tree, right-click the [Status monitor] and select [Add Template]; the [Add Template] dialog will appear. In the dialog, you can create a monitoring template by selecting monitoring target, item, or chart property etc. Note that the options in the [Add Template] may be different from the picture below if you are connected to the version which is earlier than 3.0.

• [Monitor type] : Select either DATABASE or BROKER.
• [Template name] : Enter the name of status monitoring template to be created.
• [Chart Title] Tab : Specify a title (to be displayed at the top of a chart), background color, and font.
• [Plot Appearance] Tab : Set colors for a chart title, horizontal/vertical asix, or grid line.
• [Series Selection] Tab : Select a target to be monitored.
  

Monitoring Database Status

If you select DATABASE in the [Monitor type], you can select a desired monitoring item of database in the [Series Selection] and then add it to a template.

Monitoring database shows statistics data executed by the CUBRID server by using the cubrid statdump utility. It monitors items such as log pages, indexes, queries, or transactions. For more information, see "Outputting Statistics Information of Server."

Monitoring Broker Status

If you select BROKER in the [Monitor type], you can select a desired monitoring item of Broker in the [Serier Selection] and then add it to a template.

There are seven types of Broker monitoring item: SESSION, ACTIVE_SESSION, ERR_Q, LONG_Q, LONG_T, QPS, RPS, and TPS. For more information, see "Checking the Broker Status." All other object monitoring values except for ACTIVE_SESSION of the Broker represent the number of occurrences that happen during the last sampling interval.

• SESSION : The number of applications (CAS) connected to the Broker. In other words, it means the number of applications, not IDLE status. This value cannot exceeds the value specified in the MAX_NUM_APPL_SERVER parameter.
• ACTIVE_SESSION : The number of active applications (CAS) with BUSY status. In other words, it means the number of transactions that are currently executed.
• ERR_Q : The number of errors occurred
• LONG_Q : The number of long queries
• LONG_T : The number of long transactions
• QPS : The number of queries processed per second by the Broker
• RPS : The number of requests per second received by the Broker
• TPS : The number of transactions processed per second by the Broker

Template Information

• Name : Enter the name of the Status monitoring template to be created.
• Description : Enter the description of the template to be created.
• Sampling term (Second) : Specify the interval (in seconds) at which the target object is to be monitored.
• Target database : Select the target database. It is activated when the monitoring target object is related to the Database Server.

Executing the Status Monitor

If you right-click the Status Monitor Template to execute and then select [Status Monitor], the Status Monitor pane appears where you can monitor the Server and the Broker status depending on the selected template. The Status Monitor shows separate charts for each collected item, which consists of the current, minimum, maximum and average values.

The Status Monitor, represented in separate views, can be viewed together with other view interfaces. It can also be viewed outside the CUBRID Manager, which makes it convenient to perform jobs and monitoring at the same time in multi-monitor environment.

9.2. Integrated Status Monitoring

This feature is supported only when you connect to a database of CUBRID 2008 R2.2 or higher.

Broker Status Monitoring

You can monitor items related to the broker by combining them into a single chart. You can set the chart property by clicking the [Configuration] button in the bar at the top of the broker status monitoring pane.

Database Status Monitoring

This feature is supported only when you connect to a database of CUBRID 2008 R2.2 or higher. You can monitor items related to the database by combining them into a single chart.

Chart Properties Setting

You can set the chart title, image and items to be monitored in the chart setting wizard.

9.3. Manage Dashboard

[Dashboard] tap appears next to [Hosts] tab when you select [Tool] > [Open Dashboard Explorer] in menu. Dashboard is supported in CUBRID 2008 R3.1 or later.

Add Dashboard

Right-click on the [Dashboard] tab and select [Add Dashboard]. Then, [Add Monitoring Dashboard] dialog will appear. Enter the dashboard name in [Dashboard name] field and click [Add] button.

Step 1: Set Host Information

Enter the host information of the database server you want to monitor. At this time, The CUBRID manager server must be running in the host.

• Alias name : Enter an alias in the host information. If you skip this step, the host address is used.
• IP address : Enter the IP address of the host to monitor.
• Port : Enter the cm_port of CUBRID Manager server installed in the host. You can check cm_port value in $CUBRID/conf/cm.conf file.
• Password : Enter the password for a CUBRID Manager administrator.
• Connect : Verify whether it is possible to access with the entered host information. You can move to the next step only if the connection test succeeds.

Step 2: Select Database

Select one of the databases you wish to monitor which are installed in the host.

• Alias name : Enter an alias for the database information. If you skip this step, the database name is used.
• DBA password : Enter the DBA password of the database.
• HA Mode : It is automatically selected when the database is configured in HA mode (ha_mode=on).
• Add database : Verify whether the database information entered can access the database, and add it to the list of databases. If HA is configured in the database, a window that enables you to detect the rest of HA-configured database and add them will appear.
• Add HA database : If HA is configured in the database, you can add the rest of HA-configured databases.
• Delete : Delete information registered in the list of databases.

Step 2-1: Add HA Database

If you click the [Add HA database] button in the step 2, you can add the rest of HA configured nodes. If you click [Yes] in the window that confirms whether to add standby node, you can add the host information and database information of the standby node in the [Add HA database] window.

• Port : Enter the cm_port of CUBRID Manager server installed in the host. You can check cm_port in CUBRID/conf/cm.conf file.
• Password : Enter the password for a CUBRID Manager administrator.
• DBA password : Enter the DBA password of the database.
• Add database : Verify whether the database information entered can access the database, and add it to the list of databases.
• Delete : Delete information registered in the list of databases.

Step 3: Select Broker

You can select the broker running in the host, and add it as a target to be monitored.

• Alias name : Enter an alias of the broker. If you skip this step, the broker name is used.
• Add broker : Add selected broker in the list of brokers.
• Delete : Delete the registered information in the list of brokers.

Manage Dashboard Window

You can use a mouse or keyboard direction key to adjust a target object displayed on the dashboard windows; the adjusted location information is stored in a local directory where CUBRID Manager is installed, and the final location information always will be used. You can also adjust screen ratio by using the <Ctrl> key with mouse scrolling or <+> or <-> keys in the keyboard.

A popup menu will appear when you click right-click on the dashboard window.

• Select All : You can select all the objects indicated in the monitoring window to move their location.
• Add Host Monitor : You can add new host information that you want to monitor in the monitoring dashboard.
• Refresh : You can manually refresh the monitoring dashboard.

9.4. Dashboard - Host Monitor

It monitors the host in which database or broker is running and shows the current value of the CPU, MEMORY, and IO WAIT as percentage. A popup menu where you can configure functions below will appear when you right-click on the host monitor.

View Detailed Information

[View Detailed Information] shows changes with time of CPU, MEMORY, and IO WAIT.

You can configure the chart properties by clicking the icon on the upper right in the [View Detailed Information] screen.

• Plot Appearance : Configure the colors of cross gridlines and the background of a monitor host chart.
• Series Selection : Select items to display in a monitor host chart, and configure the colors and line thickness of the graph.
• History Record : Specify a directory where history will be saved when recording is on.
• Chart Selection : Select a chart to be monitored.

Clicking the start recording icon in the [View Detailed Information] screen will save all statistical data being recorded into a local folder. To stop recording, click stop recording icon.

View History Record

The function that provides the history record information. You can track trend of a specific time by selecting date and time.

9.5. Dashboard - Database Monitor

It monitors the database server which is currently running and shows the current value of CPU, MEMORY, and HA delay (msec) of the database server. A popup menu where you can configure functions below will appear when you right-click on the database monitor.

View Detailed Information

[View Detailed Information] shows changes with time of CPU, MEMORY, and HA delay.

You can configure the chart properties by clicking the icon on the upper right in the [View Detailed Information] screen.

• Plot Appearance : Configure the colors of cross gridlines and the background of a monitor host chart.
• Series Selection : Select items to display in a monitor host chart, and configure the colors and line thickness of the graph.
• History Record : Specify a directory where history will be saved when recording is on.
• Chart Selection : Select a chart to be monitored.

Clicking the start recording icon in the [View Detailed Information] screen will save all statistical data being recorded into a local folder. To stop recording, click stop recording icon.

View History Record

The function that provides the history record information. You can track trend of a specific time by selecting date and time.

View HA Applied Log

This is enabled in the HA standby database server where HA is configured; you can check the log generated upon execution of cubrid applylogdb command.

View HA Copied Log

This is enabled in the HA active database server where HA is configured; you can check the log generated upon execution of cubrid copylogdb command.

9.6. Dashboard - Broker Monitor

It monitors the broker which is currently running and shows the current value of the number of session and active session, including TPS. A popup menu where you can configure functions below will appear when you right-click on the broker monitor.

View Detailed Information

[View Detailed Information] shows values for the broker.

View History Record

The function that provides the history record information. You can track trend of a specific time by selecting date and time.

View Connected Client

This enables the window that represents an application client connected to a broker. An IP address of the connected application client is displayed.

View Connected Database

You can check database information connected by using the broker. The information based on the values of DB items are shown among broker monitoring items.

View Host

You can check the host information in which the database server is running.

10. Logs

Logs consist of Broker, Manager and Database logs. There can be sub-nodes such as Access, Error and Admin logs. Each log consists as follows:

10.1. Broker Log

Access Log

The access log file records information about application client access, and it analyzes and outputs what is saved with the name of " broker_name.access." In addition, if the LOG_BACKUP parameter is configured to " ON" in the broker configuration file, the information about the termination date and time is stored additionally to the log file upon successful termination of the broker operation.

Error Log

The error log file records information about errors that occurred during the client's request processing and is saved with the name of " broker_name_app_server_num.err."

The following is an example and description of an error log:

Time: 02/04/09 13:45:17.687 - SYNTAX ERROR *** ERROR CODE = -493, Tran = 1, EID = 38

Syntax: Unknown class "unknown_tbl". select * from unknown_tbl

• Time : 02/04/09 13:45:17.687 : Time when the error occurred
• SYNTAX ERROR : Type of the error (SYNTAX ERROR, ERROR, etc.)
• *** ERROR CODE = -493 : Error code
• Tran = 1 : Transaction ID. -1 if no transaction ID is assigned.
• EID = 38 : Error ID. This ID is used to find the SQL log related to the server or client logs when an error occurs during SQL statement processing.

Error Log Trace

You also can trace the broker error log for SYNTAX ERROR Type.

Click the [Trace Error] action, will pop up the error trace result dialog.

Admin Log

The admin log records the history about the service operation and termination.

10.2. Manager Log

Access Log

The access log files records information about the CUBRID Manager access. You can see user accounts, operation history, and time when operations are performed.

Error Log
The error log file records information about errors that occurred while connecting the CUBRID Manager.

10.3. Database Log

Admin Log

This admin log records information about errors that occurred while server is running. The format of output file is as follows: < database_name> _< date> _< time> .err.

11. Settings

11.1. Database Settings

[Selected Target Database] - [Display server/client parameters information]

Displays information on the parameters used in the database. You can check the items to be displayed when the cubrid paramdump utility is running in the Manager.

For more information about this utility, see "Outputting Parameters Used in Server/Client."

If you select [Display server/client parameters information] option, you can check all parameter values applied to the server and the client.

If you deselect the option, you can check only the parameter values applied to the server.

[Selected Target Database] - [Query Plan Cache Information]

Displays information on the query plan saved in the cache of the database server. You can check the items to be displayed when the cubrid plandump utility is running in the Manager. For more information about the utility, see "Checking the Query Plan Cache."

Since this feature can only be performed when the database server is running, the [Query Plan Cache Information] menu is activated only when the database server is running.

If you select the [Delete query plans saved in the cache] option, the collected database query plan cache information is displayed before it is initialized.

11.2. Query Editor Options

[File] > [Preferences] > [Query options]

Sets the basic information about the currently used CUBRID Manager. Provides the same items as the host setting.

[Host] > [Properties] > [Query]

In the [Query] dialog box, you can set the following options:

• Autocommit : You can set a default value so that autocommit is performed after a query is executed in the query edit pane. Even when [Autocommit] is selected, you can set/clear the function from the toolbar in the Query Editor.
• Search unit of result instances : Sets the number of result rows to be fetched at once from the database after the execution of the query. That is, if the number of search result rows is 7,000 when the value is set to 5,000, you can select whether or not to continue to fetch more search results after 5,000 rows are fetched. In addition, if you execute queries that satisfy the following conditions, ROWNUM is automatically added based on the set value to prevent using excessive server resources.
• • WHERE condition is missing.
  • GROUP BY is not used.
  • ORDER BY is not used.
  • Aggregate functions (SUM, COUNT, MIN, MAX, AVG, STDDEV and VARIANCE) are not used.  
  • Hierarchical Query is not used.
• Page unit of result instances : You can navigate in the query results pane by paging specified number of records.
• Enable query plan : You can check the query plan before and after its execution. Selecting this option may slightly affect the query execution time because plan information will be created in advance for queries to be executed.
• Get OID info : Fetches OID information during the query execution. This allows you to directly modify/delete data in the query results pane. However, “NONE” is displayed if the OID cannot be fetched as with Join queries. Selecting this option may extend the query execution time.
• Make keyword and functions lowercase : The auto-commit will show the keywords as lowercase.
• Without prompt to save on close when non-file editor is dirty : If the editor doesn't open a file, the save prompt will not pop on close whether the editor is dirty or not.
• Change font & size : You can change fonts and their sizes to be used in the Query Editor.
• Change style : Changes the show style of query editor's pane and result pane.

[Database] > [Properties] > [Connection Information]

• Database IP : The current database's IP address
• Broker IP : By default, the Broker address for the database connection is set to the IP address of the database server. If the Broker server is not connected, you can connect to the Broker by modifying this value. The Broker address can be modified only by the CUBRID Manager admin user. Other users can connect only through the Broker address specified by the admin user.
• Broker port : A Broker port to be used for database connection. The port is displayed by the CUBRID Manager admin user. The Broker port can be modified only by the admin user. Other users can connect only through the Broker port specified by the admin user.
• Character set : You can specify the character set for each database. It is recommended to use only one character set for a database. The default is one used in the system where the CUBRID Manager is running.

11.3. Global Settings

Help Setting

You can set whether the Help is displayed through the internal Help window or the external browser. You can also select the open mode when the Help is executed as an Eclipse plug-in.

Basic Information Setting

You can set the following through basic information setting:

• Whether the CUBRID Manager window is open in the maximum size or the previous size
• Whether to always exit without prompt when CUBRID Manager exits.
• Whether to show or not CUBRID News on startup(available when system locale is set to KR)
• Whether the information window opens with a single or double click in the navigation tree. (The default value is double click.)

JDBC Driver Setting

Multiple JDBC drivers are supported in CUBRID 2008 R2.1 or later. To access database in version earlier than 2.1, you can configure additional version of CUBRID JDBC driver. The CUBRID JDBC drivers are contained in cubridmanager/plugins. In CUBRID Manager R2.1, in general, you can access the corresponding version of database server by using CUBRID-JDBC-8.2.1.x. As multiple JDBC drivers are supported, you can use access the earlier version of database than the version of CUBRID Manager to execute queries. To do it, go to [Default Configuration] > [JDBC Driver Configuration] and configure additional JDBC driver that you will use.

However, depending on the version of the database server that is being connected to, there might be some restricted functions. For example, while the functions in the left tree structure work normally in the database of CUBRID 2008 R2.0 or higher, they do not work in earlier versions of the database. In addition, query editing or executing will work normally in the database of CUBRID 2008 R1.4 or higher, but will not work in earlier versions.

Monitoring Dashboard

You can set the color for each status of hosts, database servers, or brokers in the monitoring dashboard.

Import Options Setting

Set which strings will be regarded as NULL value during importing or updating.

Service Operation Setting

Sets database common parameters.

Server-Common/-Specific Parameter Setting

Sets the options related to the service operation. You may set automatic database startup.

HA Setting

Sets database HA parameters.

Edit Configuration File

There are four configuration file can be directly edited including cubrid.conf, cubrid_broker.conf, cm.conf and ha.conf (if this server is HA server and CUBRID version is after 2008R 4.0). For example, if you want to edit cubrid.conf directly, you need click [Edit Cubrid Config], then an editor shown the cubrid.conf will be opened.

If you want import/export the content in the editor, you can move server configration files.

12. For Power Users

12.1. Host Group Management

Host groups can make hosts display clearly when where are lots of hosts needed to manage.
 

Hide or Show Groups

Users can choose hide or show the host group by menu as follows:

• [Item] menu : show host only and hide the group nodes.
• [Group] menu : show the group nodes.

Open Groups Settings Dialog

Use [Group Settings…] above to open the group management dialog as follows:

Buttons [Top][UP][Down][Bottom] are responsible to adjust the display order of group.

And buttons [Add…] [Edit…] will open a new dialog to add or edit a group.

Add, Edit Group Nodes of Hosts

Button [Add] will open a new group dialog to let users input the new group's name and children hosts.

Left area of the dialog is a list of current hosts which is not in current group and right area is a list of current group’s children hosts.

Button [>] will move the selected in the left to right and [>>] will move all of the left to right;

Button [<] will move the selected in right to left and [<<] will all of the right to left.

Delete Group

Select a group to be deleted and push the button [Delete].

Note: the [Default Group] can not be deleted and edited, it store the hosts which is not in other groups.

Drag Group

Users can drag several host nodes to another group node or change the display order of host nodes of current group node.

Users can also change the display order of host nodes when group nodes are hidden.

12.2. Configuring Background Operations in Multiple-Host Environment

If you manage databases in several hosts by using [Add Host], databases can be configured for background operations. For example, if you want to execute a query to a database in host B while doing backup for a database in host A, the database backup operation, which generally takes a long time, can be configured to be executed as a background operation. The database operations that can be run in the background are as follows:

• Database related : Create Database, Unload/Load Database, Backup/Restore Database, Rename Database, Copy Database, Optimize Database, Compact Database, Check Database
• Table related : Import/Export, Delete All Records, Update data by changing constraints from NULL to NOT NULL
• Volume : Add Volume

12.3. OID Navigator

It is used to search data by OIDs.

You can run the OID Navigator by right-clicking a database or inside the Result pane of the Query editor and then selecting [OID Navigator]. Note that this function is activated only while the database server is running; this is deactivated while the server is not running.

2. Getting Started

2.1. Running CUBRID Manager

Running in Windows

Select [Start] > [All Programs] > [CUBRID] > [CUBRID Manager Client].

Click the CUBRID Service Tray and then select [Tools] > [CUBRID Manager].

Running in Linux

You can start the CUBRID Manager client by entering one of the following commands on the shell.

%cd $CUBRID/cubridmanager

%./cubridmanager

CUBRID Manager Client Log

2.2. Connect CUBRID Host

Connect Host

A connection to a specific host is made when you double-click the host registered in the host navigation tree. Or you can right-click a host, select [Connect Host], check the user name, and then click [Connect] to connect to the host.

If the connection is successful, the host icon changes

Disconnect Host

Right-click the host in the host navigation tree, and then select [Disconnect Host].

Add Host

You can manage databases through multiple hosts in a single manager by adding a host. To add a host, perform one of the followings:

• Click [Add Host] from the toolbar.
• Select [File] > [Add Host] on the menu.
• Right-click in the navigation tree, and then select [Add Host].

If you enter the information and then click the [Add] button, the host is added to the host navigation tree, but not connected to. If you click [Connect], however, the host is added to the navigation tree and connected to as well.

Delete Host

Deletes the information of the host registered in the host navigation tree. When a host is deleted, all information in the sub-nodes is deleted as well. However, only the CUBRID Manager client configuration, not the CUBRID Manager server configuration, is deleted.

2.1. Installing CUBRID Query Browser

2.1.1. Application type

2.1.2. Eclipse plug-in type

2.2. Connecting CUBRID Host

2.3. Executing SQL query

2.4. Managing a Table

2.5. Managing Multiple Hosts

1. Introduce to CUBRID Query Browser

The CUBRID Query Browser is a tool in which you can execute SQLs and manage the objects of CUBRID database conveniently.

It replaces the Query Editor of CUBRID Manager in version 2008 R3.1 or earlier. and is integrated into CUBRID Manager as a plug-in in version 2008 R3.2 or later.

The CUBRID Query Browser consists of a database server running on a host where the Broker in installed and a GUI client. The CUBRID Query Browser client utility is written in Java and can be run in any environment that supports Java. It can run as an RCP application or run as a plug-in of Eclipse IDE.

1. Introduction to CUBRID Manager

The CUBRID Manager facilitates various management tasks and provides the "Query Editor," allowing users to execute SQL statements against the connected database.

CUBRID Manager consists of a database server, a manager server running on a host where the Broker is installed, and a GUI client. The CUBRID Manager client utility is written in Java and can be run in any environment that supports Java.

The CUBRID Manager consists of a server and a client. You can run the CUBRID Manager client only when the CUBRID Manager server is running.

The CUBRID Manager client is a Java application program that runs only on JRE/JDK 1.6 or higher. If the version is below 1.6, an error message appears: "Unsupported JRE version. You must use JRE 1.6 or a later version."

3. References

Quick Links :

Create Table | Create Table Like | Create View | Execute Defined SQL | Export Data | Import Data | Trigger | TRUNCATE TABLE | Preferences

Create Table

Create Table Options:

• [General] tab : You can define the name of the table to be added and add, edit and drop columns. You can also set the primary key (PK) and, before the table is created, adjust the position of the selected column by using [↑] and [↓].
  Using the add column wizard, you can set the name, type, default value and constraints of the column to be added. You can also set to display a warning message when you enter something that is not grammatically correct, or to disable the selection of a grammatically incorrect entry.
  • Reuse_OID : If this option is selected, a table is created with the option REUSE_OID applied. For this kind of table, using with OID is restricted. For more information on OID reuse table, see "Table Options (REUSE_OID)" in the CUBRID online manual.
• [FK/Indexes] tab : You can set foreign keys and indexes.
  • Add Foreign Key : Using the add foreign key wizard, you can set the name of the foreign key, the name and primary key of the reference table and the trigger actions to maintain referential integrity. The ON UPDATE, ON DELETE and ON CACHE OBJECT options are provided.
  • Add Index : You can set index name, index type, a column to be indexed. Ascending (asc) and descending (desc) sorting can be selected within the supported range. For REVERSE indexes, only descending sorting is supported.
• [Partition] Tab : Supports partitioning setting and modification of the given table.
  • Add Partition : Using the add partition wizard, you can set the partition type and expression. The RANGE, LIST and HASH partitions are supported.
  • Edit/Delete Partition : You can edit or delete partition.
• [SQL Statement] Tab : You can check and copy SQL statements created according to the settings in [General], [Foreign Key/Index] and [Partition] tabs.

Adding Object Oriented Tables:

To add a table with object-oriented properties, select [Show object oriented related properties]. When you select [Show object oriented related properties], the Inheritance tab is added.

• [General] tab : When you select [Show object oriented related properties], Shared, Inheritance and Table column are added as a column in the table. When adding or editing columns, you can choose the column type as shown in the figure below. You can choose OBJECT or a table in the database as the data type.
• [Inheritance] tab : You can define the super table to inherit from. If a column name conflict occurs, it can be adjusted.

Create Table Like

Creates an empty table which has the same schema structure with an existing one. It works the same as CREATE TABLE LIKE.

Create View

Execute Defined SQL

With [Execute Defined SQL] menu, you can execute "prepared statement," pre-saving a specific query statement and specifying a new parameter value for the statement whenever the query is executed.

You can execute the SELECT statement which meets specified conditions by entering a parameter value of defined "prepared statement" by using [Select by input value].

You can execute the INSERT statement by entering a parameter value of defined "prepared statement" by using [Insert by input value].

You can use [Select by read file] when repeating the execution of SELECT statement by inputting several parameter values in the defined "prepared statement." The data is saved in Excel (.xls) or CSV format. You can configure a  file charset where parameter values are saved, the number of concurrent threads to be executed, and commit cycle. To change the value for [JDBC charset], right-click the mouse in Explorer and then select [Properties].

You can use [Insert by read file] when repeating the execution of INSERT statement by inputting several parameter values in the defined "prepared statement." The data is saved in Excel (.xls) or CSV format. You can configure a  file charset where parameter values are saved, the number of concurrent threads to be executed, and commit cycle. To change the value for [JDBC charset], right-click the mouse in Explorer and then select [Properties].

Export Data

Data (one or more tables) can be exported in Excel (.xls), CSV, SQL, or CUBRID load (.obs) format. The export progress will create a new file for each table and save the files into the path which you specified in [File path]. [File charset] is used to specify the file charset of the exported data.

Import Data

You can import data from an Excel or CSV file into the database.

• JDBC charset : Used to specify the charset when getting data from a file, and use [JDBC charset] to specify charset of the data to be imported into the database. The [JDBC charset] only can be changed at the [Open Connection] dialog, and the new value will work after the database is reconnected.
• File charset : Used to specify the charset of data to be imported from a file.
• Thread count : The import process support multi-thread to make better performance. It is used to specify how many thread will run during the importing, 5 is recommended and do not make it larger than 10.
• Commit lines once : Used to specify how many rows that memory cache stored in one thread, if the memory cache is full, all data in the cache will be committed to the database and new data will start to fill the memory cache.
• Mapping between file columns and table columns
• • If the first row of the import data is the names of columns, the [Use the first line data as column names] should be checked.
  • The buttons [Delete](of file column), [Up], [Down], [Delete] (of Table column) are used to specify the correspondence between file columns and table columns.
• Error-Handling : used to specify what the import progress will do when errors occurred. If [Ignore] is checked, the import progress will ignore all errors and show an error report dialog when progress is finished and errors occurred. And if the [Break] is checked, the progress will be broke when error occurred, but the committed data will not be rollback.

Trigger

Create Trigger options:

• Trigger name : Enter the name of the trigger to be added.
• Target table/Target column : Enter the target table and column information.
• Event Time : Select the point of time when the condition of the trigger is to be evaluated. You can select from BEFORE, AFTER, and DEFERRED.
• Event Type : Select the type of the event to be occurred. Event types are INSERT, DELETE, UPDATE, STATEMENT INSERT, STATEMENT DELETE, STATEMENT UPDATE, COMMIT and ROLLBACK.
• Event Condition : Enter the condition for the trigger action.
• Execution Time : Specify the point of time when the trigger to be executed. If DEFAULT is selected, the trigger fires based on the point of time when its condition is validated.
• Action Type : Select the type of the trigger action. If the type of the trigger action is PRINT, OTHER, or STATEMENT you can enter addition information in the SQL statement or print messages for action type.
• Trigger Status : You can specify whether to activate or deactivate the trigger to be added.
• Trigger Priority : You can set the priority of the trigger. The priority value is a FLOAT and can be between 0.00 and 9999.99.

TRUNCATE TABLE

You can delete entire records including indexes and constraints in a table by right-clicking [More] > [TRUNCATE TABLE]. This way is faster than using [DELETE ALL] because all indexes and constraints defined in the table are deleted before deleting records. The ON DELETE trigger is not activated when you use the [TRUNCATE TABLE].

Preferences

General:

• Show window maximize : The window of the CUBRID Query Browser is maximized when it is opened.
• Always exit without prompt : The confirmation prompt is not shown up when the CUBRID Query Browser is closed.
• Create the new information of CUBRID : The now information of CUBRID is shown up when the CUBRID Query Browser is opened.
• Open mode : Determine single click or double click when a node is opened in the connection explorer.

Import Options:

• Import options is used to specify which value will be turn to NULL when import data to database. Strings "NULL", "(NULL)" and "N" are the default options and you can input some custom values into the text area, the max length of text is 256 characters.

JDBC Management:

• Add : You can select and add the CUBRID JDBC driver file after opening a file selection dialog.
• Delete : You can delete selected CUBRID JDBC driver from the list.

1. Introduce to CUBRID Migration Toolkit

CMT provides you with an ability to contribute to efficient MySQL/Oracle/SQL Server/CUBRID to CUBRID migration and management using a variety of available tools easily and quickly.

First, you can connect to online source and target database by JDBC.

Second, when you succeed, a database tree is added to database explorer which locates at left bottem panel. You can use database explorer to view source or target database object.

Third, you can create new migration by migration wizard, in which:

• You can specify migration method, select source database objects, easily create new target database/table/view/serial or map table to some exist table.
• You can set migration parameters to speed up migration.
• You can save migration script for future use.
• You can view and save not supported partition tables and indexes to migrate.
• You can save DDL of creating tables, views and serials
• You can view migration progress, save migration report and error tracking.
• You can view history migration information or current running migration information on the remote migration server.
• You can configure data type mapping in migration.

2. Getting Started

2.1. Installing CUBRID Migration Toolkit

2.2. Migration senarios

2.2.1. Online migration from remote database to local with new database

2.2.2. Online migration from remote database to remote using CUBRID Migration Toolkit Server

2.2.3. Offline migration to export loaddb files

3. References

3.1. Migration Wizard

3.1.1. Step 1: Migration type Selection

3.1.2. Step 2: Set Source Database

3.1.3. Step 3: Migration Database Object Selection

3.1.4. Step 4: Set Target Database

3.1.5. Step 5: Set Database Object Mapping

3.1.6. Step 6: Migration Options Setting

3.1.6. Step 7: Migration

3.1.7. Step 8: Summary

3.2. Migration History Wizard

Migration History Wizard allows you to review history migration progress information of migration running on the localhost or running on the remote migration server but migration script was sent by localhost.

View Migration Progress Information

View Migration Report

3.3. Load Migration Script

Load Migration script allows you to load migration script you saved for future use. To load migration script, click main menu [File] > [Load Migration script], find you saved migration script and click [Open], a migration wizard with all migration parameters appears.

3.4. Data Type Mapping Preferences

Latest News

• January 02, 2012 - CUBRID Manager 8.4.0 patch 3 is now available
• April 20, 2011 - What’s New in Upcoming CUBRID Manager 8.4.0
• December 17, 2010 - CUBRID Database Manager for Mac Arrived!
• Novermber 12, 2010 - CUBRID 3.1 Beta: New Data Types. New Functions.
• October 29, 2010 - October Wrap-up by CUBRID Community
• July 19, 2010 - New CUBRID 2008 R3.0 Beta has been released!
• July 6, 2010 - CSQL – Command Line SQL Interpreter
• April 2, 2010 - What is CUBRID Manager?

Video Tutorials

• CUBRID Manager Part I & II
• CUBRID Manager Part III & IV

Mac OS X

• Running CM on Mac OS X
• CM Build Instructions for Mac OS X

• [CUBRID Manager]
• [CUBRID Query Browser]
• [CUBRID Migration Toolkit]
• WebQuery Release Notes

The CUBRID Manager facilitates various management tasks and provides the "Query Editor," allowing users to execute SQL statements against the connected database.

CUBRID Manager consists of a database server, a manager server running on a host where the Broker is installed, and a GUI client. The CUBRID Manager client utility is written in Java and can be run in any environment that supports Java.

Contents

1. [cm_manual_introduce|Introduction to CUBRID Manager]
2. [cm_manual_getting_started|Getting Started]
3. [cm_manual_host|Hosts / Services]
4. [cm_manual_user|Users]
5. [cm_manual_database|Databases]
6. [cm_manual_objects|Database objects]
7. [cm_manual_sql_editor|Query Editor]
8. [cm_manual_broker|Brokers]
9. [cm_manual_monitoring|Monitoring / Dashboard]
10. [cm_manual_log|Logs]
11. [cm_manual_configuration|Configurations]
12. [cm_manual_professional|For Power Users]

CUBRID 매니저는 GUI 환경에서 CUBRID 데이터베이스 관리 및 질의 기능을 제공하는 CUBRID 데이터베이스 전용 관리 도구이다. CUBRID 매니저를 사용하면 CUBRID 데이터베이스의 관리 작업을 GUI를 이용하여 쉽게 할 수 있다. 또한, CUBRID 매니저는 데이터베이스 관리 및 응용 개발에 필수적인 질의 편집기 도구를 제공한다.

CUBRID 매니저는 CUBRID DBMS가 설치된 서버에서 동작하는 매니저 서버와 GUI 기반의 클라이언트로 구성되어 있다. CUBRID 매니저 클라이언트 프로그램은 Java 및 Eclipse의 RCP로 제작되었으며 Java가 실행될 수 있는 환경(Java Runtime Environment)이면 사용 가능하다.

목차

1. [CUBRID Manager Introduce_kr|CUBRID 매니저 소개]

2. [CUBRID Manager Installation_kr|CUBRID 매니저 설치]

3. [CUBRID Manager Getting Started_kr|CUBRID 매니저 시작하기]

4. [CUBRID Manager Reference_kr|CUBRID 매니저 기능 설명]

5. [CUBRID Manager Monitoring_kr|CUBRID 매니저 모니터링]

6. [CUBRID Manager Configuration_kr|CUBRID 매니저 환경설정]

7. [CUBRID Manager Advanced Usage_kr|CUBRID 매니저 고급 사용]

In this window enter the following URL in the Work with: field, which will indicate where to download the CUBRID Query Browser.

Hit Enter or click on the Add button. The CUBRID Query Browser software should be then listed as shown in the image above.

From the available list check beside the CUBRID Query Browser plug-ins for Eclipse. Then press Next to start calculating the dependencies. After that you will see the following window with Install Details.

Press Next to see the license terms.

Accept the terms and press Finish. This will install the CUBRID Query Browser as an Eclipse plugin.

During the installation you might see the following message. Ignore it by clicking OK and continue.

After all Eclipse will prompt you to restart your IDE. Click on the Restart Now.

Once you restart you will see the your previous perspective. To switch to CUBRID Query Browser perspective, click on the Open Perspective button on the top right corner as shown in the image below.

You will see a list of perspectives. Click on Other... to add CUBRID Query Browser perspective.

A new window will show up. From the provided list, choose CUBRID Query Browser, then press OK.

You will notice that the view of IDE has been changed as shown in the image below. Now add a new host and do your database management.

Since CUBRID Query Browser is implemented in Java, it requires Java Runtime Environment or Java Development Kit version 1.6 or later.

• Download JRE or JDK from http://java.sun.com/javase/downloads/index.jsp.

Installation

CUBRID Query Browser does not require any installations. It is distributed in an archived file with an extension .tar.gz. All you have to do is extract the contents of the archive to a desired location (e.g. Desktop).

CQB uses JDBC driver to connect to CUBRID server. You do not have to separately download the drivers as CQB has them all.

Eclipse plugin

If you want to run the CQB as an Eclipse plugin, Eclipse version 3.5 or higher is recommended to be installed on your computer. To download the latest version of Eclipse, visit Eclipse Download page http://www.eclipse.org/downloads.

There are many different version of Eclipse optimized for different purposes. Choose the one you think applies to you best. If you are not sure which one suits you better, you may download Eclipse Classic.

Then, [Install CUBRID Query Browser as an Eclipse Plugin].

3. Host / Service Management

3.1. Host Management

Default Host Information

When you start the CUBRID Manager for the first time after installation, a host named "localhost" has been set by default in the host navigation tree. This setting has been made under the assumption that the CUBRID Manager server is installed on your PC where the CUBRID Manager client is currently running, and shows the basic information about the CUBRID Manager connection.

• Host name : Host name is an identifier that identifies a host to be managed in the CUBRID Manager. A host name must be unique. Internally managed host identifier has the format of [Host name + Connection port]. A host name can contain only alphanumeric character. Do not use spaces. The length of a host name must be between 4 and 32 characters.
• Host address : A host address cannot be a space or contain spaces.
• Connection port : Only an integer value between 1024 and 65535 can be entered for the connection port. The default port value is 8001. If the connection fails, check the cm_port value in the $CUBRID/conf/cm.conf file.
• User name : The user who has the administrator authorization of the CUBRID Manager is admin. You must connect with the admin account when you use the CUBRID Manager for the first time after installation. A user name can contain only alphanumeric character. Do not use spaces. The length of a user name must be between 4 and 32 characters.
• Password : The initial password for the admin user, who has the administrator authorization of the CUBRID Manager, is "admin." You cannot connect if you do not modify the password when you make the first connection with the admin account. Be careful not to lose the modified password of the admin user. The password cannot be reset to "admin." A password cannot contain spaces. The length of a password must be between 4 and 32 characters.
• Save Password : You can save password to local. If checked ,you only double click this host will auto login. Otherwise, will pop up the dialog to input this password.
• Driver version : You can select a CUBRID JDBC driver which will be used in the CUBRID Manager. The default value is Auto Detect; a driver is automatically detected if any version of driver which can be used in the CUBRID Manager exists; if exists, automatic connection is made. If not, the following message will appear.
• Browse : Clicking it will pop up the below JDBC driver management dialog .You can manage the JDBC driver.

Add Host

You can manage databases through multiple hosts in a single manager by adding a host. To add a host, perform one of the followings:

• Click [Add Host] from the toolbar.
• Select [File] > [Add Host] on the menu.
• Right-click in the navigation tree, and then select [Add Host].

If you enter the information and then click the [Add] button, the host is added to the host navigation tree, but not connected to. If you click [Connect], however, the host is added to the navigation tree and connected to as well.

Delete Host

Deletes the information of the host registered in the host navigation tree. When a host is deleted, all information in the sub-nodes is deleted as well. However, only the CUBRID Manager client configuration, not the CUBRID Manager server configuration, is deleted.

3.2. Service Management

You can start or stop CUBRID related services with the CUBRID Manager. This functionality works the same as using 'cubrid,' a management utility used in the CUBRID database. However, you cannot start or stop the CUBRID Manager server with the CUBRID Manager client.

Start Service

If you select [Tools] > [Start Service] in the menu, the service and database selected from [Start Service] start. To select a service and database to be started, right-click a host and then select [Properties] > [Start Service].

[Automatic Start Service] is activated only if the service from [Start Service] is selected.

Start Service

If you select [Tools] > [Stop Service] in the menu, the service and database selected from [Start Service] stop.

Start/Stop Database

To start or stop the selected database, perform one of the followings:

• Click [Start] or [Stop] from the toolbar.
• Right-click a database and then select [Start Database] or [Stop Database].
• Select [Action] > [Start Database], or [Action] > [Stop Database] on the menu.

Start/Stop Broker

To start or stop selected broker, perform one of the followings:

• Click [Start] or [Stop] from the toolbar.
• Right-click a Broker and then select [Start Broker] or [Stop Broker].
• Select [Action] > [Start Broker], or [Action] > [Stop Broker] on the menu.

If you plan to use CUBRID Manager on your local computer, you need to install CUBRID Manager Server. For remote database administration, the CM Server is not required.

Now install the latest version of CUBRID Manager (Client). This assumes that you are installing CM Client on Ubuntu Desktop version, since CM is a GUI application. CM Client will not run on Ubuntu Server so it is not required.

• CentOS: http://yumrepository.cubrid.org/indexg_Centos.html
• Fedora: http://yumrepository.cubrid.org/indexg_Fedora.html

There choose CUBRID version. You will be given a list of links for your particular version. For example, the following link is provided for Fedora 16 where fc16 means this OS version. Other versions will have fc15, etc.

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

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

If you plan to use CUBRID Manager on your local computer, you need to install CUBRID Manager Server. For remote database administration, the CM Server is not required. It should be installed on that remote server.

Now install the latest version of CUBRID Manager (GUI Client). This assumes that you are installing CM Client on Desktop version of OS (Fedora/CentOS). Since CM is a GUI application, it will not run on Server version of the OS, so it is not required.

The CUBRID Query Browser is a tool in which you can execute SQLs and manage the objects of CUBRID database conveniently.

It replaces the Query Editor of CUBRID Manager in version 2008 R3.1 or earlier. and is integrated into CUBRID Manager as a plug-in in version 2008 R3.2 or later.

The CUBRID Query Browser consists of a database server running on a host where the Broker in installed and a GUI client. The CUBRID Query Browser client utility is written in Java and can be run in any environment that supports Java. It can run as an RCP application or run as a plug-in of Eclipse IDE.

Contents

1. [cqb_manual_introduce|Introduction to CUBRID Query Browser]
2. [cqb_manual_getting_started|Getting Started]
3. [cqb_manual_reference|References]

Contents

1. [cmt_manual_introduce|Introduction to CUBRID Migration Toolkit]
2. [cmt_manual_getting_started|Getting Started]
3. [cmt_manual_references|References]

CUBRID 매니저는 데이터베이스 서버, 브로커가 설치된 호스트에서 동작하는 매니저 서버와 GUI 기반의 클라이언트로 구성되어 있다. CUBRID 매니저 클라이언트 프로그램은 Java 기반으로 작성되어 Java가 실행될 수 있는 환경이면 사용 가능하다.

CUBRID 매니저는 서버와 클라이언트로 구성되며, CUBRID 매니저 서버가 실행 중일 때에만 CUBRID 매니저 클라이언트를 실행할 수 있다.

CUBRID 매니저 클라이언트는 Java 응용 프로그램으로 JRE 혹은 JDK 1.6 이상 버전에서만 실행되며, 낮은 버전에서 실행할 경우 "지원하지 않는 JRE 버전입니다. CUBRID 매니저를 사용하기 위해서는 JRE 1.6 이상 버전을 사용해야 합니다."라는 오류 메시지가 출력된다.

• Supports migration of MySQL/Oracle/CUBRID database to CUBRID
• Supports offline/online migration
• Supports localhost or remote migration
• Supports MySQL dump file migration(XML format)
• Supports data type mapping configuration
• Supports migration history review
• Supports automatic table to table, view to view creating
• Supports migration script saving and loading
• Supports command line style to execute migration script
• Supports DDL of creating target table and view saving
• Supports migration progress view and migration report
• Supports migration error log
• Supports timezone data transform
• Supports creating new database in offline migration
• Supports multi parameters of loaddb command
• Supports partition table migration
• Supports parallel execution in exporting records
• Supports change owner in offline migration
• Supports sequence migration
• Supports configuration of changing MySQL unparsed time/date/timestamp/datetime value

QA OK Sign – CUBRID Migration Tools 8.4.1

NHN China Platform QA Team confirmed that “CUBRID Migration Tools 8.4.1” product has a good quality to unveil for users.

Our gratitude goes to Cui Zhong-Ran as PM, Cao Yi-Lin as Dev Leader, Pang Qi-Ren as Dev Part Leader, Fu lei, Wang Kai-Jiang as Developer.

See attached “CUBRID_Migration_Tools_v8.4.1_QA_TestReport_20120120.xlsx” file for detailed test results.

QA Report :

• CUBRID_Migration_Tools_v8.4.1_QA_TestReport_20120120.xlsx
• CUBRID_Migration_Tools_v8.4.1_QA_TestCase-20120120.xlsx

Since CUBRID Manager is implemented in Java, it requires Java Runtime Environment or Java Development Kit version 1.6 or later.

• Download JRE or JDK from http://java.sun.com/javase/downloads/index.jsp.

Installation

CUBRID Manager can be installed either by simply downloading CM binary file or using apt-get or yum repositories. Alternatively, you can build CM yourself.

Download CM binary file

Once downloaded, all you need to do is launch the installer (.exe) on Windows or untar the archive on Linux. That's all!

Install CM using apt-get or yum

• [Install CUBRID Manager using apt-get on Ubuntu]
• [Install CUBRID Manager using yum (Fedora, CentOS)]

Build CM from source

• [CUBRID Manager Build Instructions for Mac OS X]

What's next

You can now follow the tutorials created for CUBRID Manager.