Read datafiles. Without an instance.
Read Oracle .dbf datafiles directly and extract supported tables for recovery and export. A running Oracle database or client is not required.
//What is verified here
- BASIC & OLTP compression on 19c / 26ai GA; row chaining / migration within documented datafile shapes BETA
- Offline TDE: raw-key input GA; password wallets (
ewallet.p12) within validated forms BETA - TDE auto-login wallet (
cwallet.sso) —-auto_login_localis refused with a clear message BETA - Autoscan across the SYSTEM tablespace (dictionary extraction) GA
- Point-in-time with redo / archive-log apply (
--as-of, INSERT/UPDATE/DELETE); a missing archive-log sequence refuses (REDO_INCOMPLETE) BETA - Consistency certificate: separate guarantees and gaps; a committed subset is not a single-SCN snapshot BETA
Datafile recovery as a whole is Beta, including row chaining, out-of-row LOBs and point-in-time recovery within documented forms. Metadata detection, corruption isolation, parallel export and BASIC / OLTP decoding on 19c / 26ai are GA. See the support matrix for source-specific limits.
Direct extraction also supplies analytics, data platforms and migration workflows. In our Oracle 19c benchmark, the database remained running while reclaimDB read its original datafiles; the source tablespaces were read-only. Suitable standby files and offline snapshots provide additional source arrangements. Preparation and current consistency limits apply.
//Step by step
Discover databases & tables
With no existing metadata, autoscan finds all Oracle databases on the host and reads the dictionary straight from the SYSTEM tablespace; scan shows the schemas/tables of a single file.
# Find every DB on the host + read dictionary from SYSTEM reclaimdb autoscan /oradata # Or inspect a single file without the SYSTEM tablespace reclaimdb scan /data/users01.dbf
Verify readability
reclaimdb verify -m metadata.json /backup/*.dbf # With a sealed point-in-time consistency certificate: reclaimdb verify --consistency-cert -m metadata.json /backup/*.dbf echo $? # 0 = ok, >0 = see exit codes
Extract tables (CSV / 14 more formats)
reclaimdb restore -m meta.json --csv ./out/ /backup/*.dbf # Specific tables, different format: reclaimdb restore -m meta.json -t HR.EMPLOYEES --parquet ./out/ /data/*.dbf
BASIC- and OLTP-compressed blocks, chained rows and partitioned tables are reconstructed block by block.
Unlock encrypted tablespaces (TDE) offline
Wallet → master key → AES-256, fully offline. A wrong key is fail-closed (exit 11) — never a silent mis-decode.
reclaimdb --tde-wallet ewallet.p12 --tde-wallet-password *** \ restore -m meta.json --csv ./out/ /data/*.dbf
Point-in-time: state at a timestamp / SCN
With archive logs, INSERT/UPDATE/DELETE from the redo are applied offline (--as-of). A gap in the archive-log sequence refuses fail-closed; --allow-redo-gap is an explicit best-effort opt-in.
reclaimdb restore -m meta.json --as-of "2024-06-15 14:00:00" \ --archive-dir /backup/archives/ --csv ./restored/ /backup/*.dbf
//Relevant exit codes
Default = fast path. On intact datafiles with a dictionary, reclaimDB answers without a full block scan. The forensic full scan is the special case (see Module 03).
Recover deleted Oracle rows from a datafile: a real Oracle 19c example. Includes the observed results and the limits of deleted-row recovery.
Test this case on your data
Send us the kind of source you actually have — a .dmp, a .dbf, an RMAN backup piece or a storage snapshot. You get a signed evaluation binary, a sample report, and an honest assessment of which paths apply to your case.