Migrate SQLite to Oracle
Certified — live-tested pathThe converter maps 8 SQLite column types to Oracle. 2 of them change kind on the way (NUMERIC becomes BINARY_DOUBLE, BOOLEAN becomes NUMBER(1)); the table below lists every one. DBShifts converts the schema, copies the rows in parallel batches and checks the result with row counts and checksums.
Free tier · no credit card
SQLite vs Oracle
SQLite
the embedded database that ships inside everything.
Oracle
Oracle Database, the long-standing enterprise standard.
SQLite to Oracle data type mapping
Pulled directly from DBShifts's own conversion rules — not a general reference table, this is what actually runs.
| SQLite | Oracle |
|---|---|
| INTEGER | NUMBER(19) |
| REAL | BINARY_DOUBLE |
| TEXT | CLOB |
| BLOB | BLOB |
| NUMERIC | BINARY_DOUBLE |
| BOOLEAN | NUMBER(1) |
| DATETIME | TIMESTAMP |
| VARCHAR(255) | VARCHAR2(255 CHAR) |
Example: SQLite to Oracle schema conversion
SQLite
CREATE TABLE orders ( id INTEGER PRIMARY KEY AUTOINCREMENT, customer_id INTEGER NOT NULL, total NUMERIC NOT NULL, is_gift BOOLEAN NOT NULL DEFAULT 0, notes TEXT, placed_at DATETIME NOT NULL );
Oracle
CREATE TABLE "orders" (
"id" NUMBER GENERATED BY DEFAULT AS IDENTITY NOT NULL,
"customer_id" NUMBER(19) NOT NULL,
"total" BINARY_DOUBLE NOT NULL,
"is_gift" NUMBER(1) DEFAULT 0 NOT NULL,
"notes" CLOB,
"placed_at" TIMESTAMP NOT NULL,
CONSTRAINT pk_orders PRIMARY KEY ("id")
);SQLite never enforced VARCHAR lengths
A SQLite column declared VARCHAR(255) will hold ten thousand characters; the length is a comment. It becomes VARCHAR2(255 CHAR) in Oracle, which means it, and the first longer value fails with ORA-12899: value too large for column.
SELECT max(length(col)) FROM t on each VARCHAR column shows which declarations the data has outgrown. Widen those before the load. Plain TEXT columns are not affected: they become CLOB, which has no practical limit.
Oracle turns '' into NULL
SQLite distinguishes an empty string from NULL. Oracle does not: '' in a VARCHAR2 is stored as NULL. A NOT NULL column with any empty values refuses those rows with ORA-01400, and a nullable one changes meaning quietly, because a search for '' finds nothing afterwards.
SELECT count(*) FROM t WHERE col = '' shows the size of the problem per column. Most of the time the right answer is to let the column be nullable and treat NULL as empty in the application.
TEXT becomes CLOB, NUMERIC becomes BINARY_DOUBLE
TEXT maps to CLOB, because SQLite text has no length limit and a VARCHAR2 does. CLOB columns cannot be compared with =, sorted, grouped or used with DISTINCT without ORA-00932, so queries that did those things on a TEXT column need DBMS_LOB.SUBSTR or a VARCHAR2 column instead.
NUMERIC becomes BINARY_DOUBLE, a binary float, which matches how SQLite stored the values. For money, override it to NUMBER(12,2) and Oracle does exact decimal arithmetic from then on.
SQLite → Oracle conversion notes
Engine-specific rules baked into the conversion and transfer pipeline — verified by live certification of this exact pair.
- INTEGER columns are 64-bit — DBShifts maps them to BIGINT so large IDs don't overflow 32-bit INT targets.
- Typeless and mixed-affinity columns (SQLite's dynamic typing) are inferred, stringified safely, and flagged.
- NUMERIC affinity values are read exactly, not through float round-trips.
- CHAR columns use character semantics, so multi-byte UTF-8 doesn't overflow byte-sized columns.
- Booleans land as NUMBER(1) with values bound as integers (Oracle drivers can't bind Python booleans to NUMBER).
- DROP TABLE … CASCADE CONSTRAINTS wrappers handle re-runs without manual cleanup.
Frequently asked questions
Is SQLite to Oracle migration production-ready in DBShifts?
Yes. SQLite to Oracle is a certified pair: it passes the live certification suite on real SQLite and Oracle servers, which checks schema fidelity, row counts, type-aware checksums and paging across batches.
What happens to SQLite types that Oracle doesn't have?
Each gets the nearest Oracle type the converter treats as safe: NUMERIC becomes BINARY_DOUBLE, BOOLEAN becomes NUMBER(1). Every such decision is in the migration plan before anything runs, and any mapping can be overridden per column.
Can I keep SQLite and Oracle in sync after the initial migration?
Not continuously: SQLite keeps no change log to read. Incremental sync re-runs copy only the rows that changed, using a per-table sync key.
Go deeper
How We Live-Certified All 49 Migration Paths
The certification harness behind this page's claims.
What Is Database Migration? A Plain-English Guide
What a migration involves, and why it is harder than copying files.
Reference
Compared with other tools
Errors you may hit
Ready to move SQLite to Oracle?
Set up in under two minutes. Validation and rollback included.
Start Free Migration