Use case · audit accessSRC · archive / dumpLOCK-ON · 1 RECORD
One record. Pulled fast.
An auditor needs a single row that left the live database years ago. Point reclaimDB at the backup or the dump and pull exactly that record — without rebuilding the whole environment.
//What is verified here
- Targeted lookup against cold backups and archived dumps (
-t/--table/--schema) GA - No full restore, no staging instance needed GA
- Answer an audit / eDiscovery request in minutes, not days GA
Scope · granularity
Selection happens at table / schema level (plus format and column choice on export). You get a single row by extracting the target table and filtering it — e.g. via grep or a SQLite query — without ever spinning up the DB.
//Step by step
01
Survey the source and find the right table
# From a cold backup datafile: reclaimdb scan /cold/users01.dbf # Or from an archived dump: reclaimdb dmp-extract --info archive_2019.dmp
02
Pull exactly one table — no full restore
# From datafile / backup: reclaimdb restore -m meta.json -t HR.EMPLOYEES --csv ./out/ /cold/*.dbf # From a dump, just one table of a schema: reclaimdb dmp-extract --schema HR --table EMPLOYEES --csv ./out/ archive_2019.dmp
No staging instance, no rebuilding the whole environment.
03
Output directly in an auditable format
# NDJSON for SIEM/Elastic, or XLSX for the business unit: reclaimdb restore -m meta.json -t HR.EMPLOYEES --ndjson ./out/ /cold/*.dbf reclaimdb restore -m meta.json -t HR.EMPLOYEES --xlsx ./out/ /cold/*.dbf
//Relevant exit codes
0
Success
3
Source not found
11
Encrypted without a key (handoff / TDE wallet needed)
21
Feature not byte-exact
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.