Oracle-compatible schemas, one clear diagram

A Desktop GUI for Tibero Schema Design

DbSchema reverse-engineers TmaxSoft's Tibero — tables, views, indexes, sequences, and stored procedures — into an ER diagram, and gives migration teams a SQL editor and data explorer for validating Oracle workloads on their new home.

  • Diagram foreign keys as directed edges between tables
  • Test PL/SQL-compatible blocks without an Oracle instance around
  • Spot-check migrated rows against the source system
  • See packages and procedures in the schema tree next to tables
Free Community Edition No signup required 15-day Architect trial included
Free Download

Trusted by teams at

An Oracle Migration Counts as Done
When Every Object Is Accounted For

Tibero's compatibility with Oracle — data types, sequences, synonyms, packages, triggers, partitioning — is precisely what makes migrations hard to verify: thousands of objects that must arrive intact, and only spreadsheets to track them.

DbSchema draws the migrated schema as one diagram, so what landed in Tibero can be read, validated, and signed off against the source.

Reverse Engineer, Test & Verify
Tibero from One Desktop App

The migration workbench: schema on the canvas, PL/SQL in the editor, rows in the grid.

Reverse engineer a Tibero schema with packages and procedures into a diagram
The Whole Schema, Procedures Included

Import tables, views, indexes, and sequences into a diagram, with packages and stored procedures listed in the schema tree beside them — the complete architectural view.

Write Oracle-compatible PL/SQL against Tibero in DbSchema
PL/SQL Blocks, Straight to Tibero

Run BEGIN...END blocks, cursor loops, exception handlers, and CREATE OR REPLACE PROCEDURE statements through the Tibero JDBC interface, with multiple tabs and CSV export of results.

Browse Tibero table contents in the DbSchema data explorer
Prove the Data Arrived Correctly

Page through tables and views, filter by column values, and compare row counts after a load — migration validation in the same session as the diagram.

Plan the Tibero schema before touching the server.

A Design Model,
Not Just a Connection

DbSchema keeps your Tibero schema in a model file of its own. During a migration that file becomes the neutral ground: designed offline, versioned, and checked against both systems.

Design the Tibero schema offline
Work Disconnected

Shape the target schema before the Tibero server is even provisioned.

Version the Tibero model in Git
Keep History in Git

Commit the model file, so every migration decision has a diff and an author.

Preview the DDL DbSchema generates for Tibero
Read the DDL First

Every model change becomes statements you inspect before they reach Tibero.

Compare the model against Oracle and Tibero
Compare Both Sides

Check the model against source and target environments to catch objects left behind.

Tibero Connection Details Worth Knowing

Tibero's driver is not on Maven Central: locate tbclient.jar in your Tibero installation (typically $TB_HOME/client/lib/) and register it in DbSchema's driver manager with driver class com.tmax.tibero.jdbc.TbDriver. The JDBC URL follows jdbc:tibero:thin:@localhost:8629:TIBERO8629 is the default listener port and TIBERO the default SID; the default DBA account is sys or tibero, depending on the installation.

For remote servers, swap localhost for the hostname or IP; for Tibero Active Cluster (TAC) setups, connect to the SCAN address rather than an individual node. More on the Tibero JDBC driver page.

Validate Your Tibero Migration Visually

One free installer: Community Edition plus a 15-day Architect trial, no account needed.

Teams working with Tibero often use these engines too. Explore dedicated guides and JDBC setup for each.

Browse all 100+ supported databases