Migrating Oracle Queries to Tibero: What to Check
A practical checklist before moving schemas and queries from Oracle to Tibero.
You are reading a translated version.
Start with an object inventory
List all database objects used by the application: tables, indexes, sequences, views, procedures, functions, triggers, and scheduled jobs. Supporting objects are easy to overlook during migration.
Check data types
-- Tipe data umum yang perlu diverifikasi kompatibilitasnya
-- NUMBER, VARCHAR2, DATE, TIMESTAMP, CLOB, BLOB
DESC nama_tabel;
Verify the precision limits of NUMBER and the time-zone behavior of TIMESTAMP in the target Tibero environment, even when familiar core types are available.
Review procedural code using Oracle packages
Test code that calls packages such as DBMS_OUTPUT and UTL_FILE, or other Oracle-specific features, individually. Package coverage may differ between platforms.
BEGIN
DBMS_OUTPUT.PUT_LINE('Contoh pesan debug');
END;
/
Test analytic functions and complex queries
Recheck both results and performance for analytic functions, hierarchical queries (CONNECT BY), and optimizer hints. Tibero may choose a different execution plan even when the SQL syntax is identical.
Plan for rollback
Prepare a return path if critical issues appear after cutover. Where practical, run both systems in parallel to compare results before fully switching.
Exercise
Choose a moderately complex PL/SQL procedure from your Oracle application. List the sections that require verification before running it in Tibero.