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.
Trusted by teams at
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.
The migration workbench: schema on the canvas, PL/SQL in the editor, rows in the grid.
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.
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.
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.
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.
Shape the target schema before the Tibero server is even provisioned.
Commit the model file, so every migration decision has a diff and an author.
Every model change becomes statements you inspect before they reach Tibero.
Check the model against source and target environments to catch objects left behind.
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:TIBERO — 8629 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.
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.