Download CUBRID JDBC Driver

Download the CUBRID JDBC driver, copy the JDBC URL into DbSchema, and start designing schemas with ER diagrams — free Community Edition.

About the CUBRID JDBC driver

A JDBC driver is a Java .jar library that lets applications connect to CUBRID. DbSchema uses JDBC to reverse engineer schemas, run SQL, and generate documentation. Driver files are usually published by the database vendor or an open-source project.

JDBC URL format

Host, port, database name, and SSL options are passed in a URL starting with jdbc:. Each CUBRID driver uses its own syntax — see the connection details below.

The CUBRID JDBC driver

CUBRID is an open-source, object-relational database management system optimized for web applications. It supports advanced data types including set, multiset, and list collection types, and offers native support for horizontal scalability through its HA and sharding extensions. CUBRID is particularly popular for large-scale Korean web portals and enterprise applications.

The CUBRID JDBC URL

• Required File(s): JDBC-{version}-cubrid.jar
• Java Driver Class: cubrid.jdbc.driver.CUBRIDDriver
• JDBC URL: jdbc:cubrid:{HOST}:{PORT}:{DB}:::
• Website: CUBRID

The three colons at the end of the JDBC URL represent optional username and password fields left empty for default authentication. To supply credentials explicitly, use the format jdbc:cubrid:host:33000:dbname:user:password:. Port 33000 is the default broker port used by CUBRID's connection broker.

Connecting to CUBRID

Clients never reach a CUBRID database directly — they reach a broker, which forwards the work to the database server. That indirection explains both the port and the access rules.

1. Connect to the broker port, 33000. cubrid_broker.conf defines the brokers; the default configuration publishes 30000 and 33000, and 33000 is the one applications use. The database server's own port is not what a JDBC client connects to.
2. Check the broker's access control list. Where ACCESS_CONTROL is on, the broker only accepts the client addresses listed in its access control file, and rejected attempts are written to the broker log. cubrid broker acl status shows what is currently allowed.
3. Mind the URL's trailing colons. The form is jdbc:cubrid:host:33000:dbname::: — the empty fields at the end are the user and password positions, and dropping them changes how the URL parses.
4. Open port 33000 in the server's firewall. The database listens on port 33000 unless it was installed with a different one. A host firewall on the server blocks incoming connections on that port until a rule allows them. The firewall guide has the commands for Windows, ufw, firewalld and iptables.
5. Connect from DbSchema. In the Connection Dialog choose Remote computer or custom port, fill in the server host and the port, then press Test Connection to check that the server answers before you connect.

DbSchema and CUBRID

DbSchema connects to CUBRID using the official CUBRID JDBC driver, supporting schema visualization for CUBRID's object-relational tables including collection types, and SQL execution through the integrated editor for CUBRID applications.