咨询热线: 13764045638 7 x 24 在线支持!

DUL a database scavenger tool For Oracle

DUL a database scavenger tool For Oracle

If you cannot recover data by yourself, ask Parnassusdata, the professional ORACLE database recovery team for help.

Parnassusdata Software Database Recovery Team

 

 

Service Hotline:  +86 13764045638 E-mail: service@parnassusdata.com

 

 

DUL a database scavenger tool For Oracle

 
 
Sometimes something goes really wrong with a database or a filesystem, and suddenly the precious data can no longer be found, it looks gone. 
 
In most cases standard recovery procedures will solve the problem.
 
In rare cases recovery also fails and all that is left are the broken damaged pieces. What most people do not realize is that the database or the filesystem is typically not wiped out, it is inaccessible, but most data is unharmed.
 
DUL is a tool that is able to retrieve the remaining data from the smallest snippets that are still available. The smallest element accepted is an Oracle database block.
 
It can work with corrupted files systems, ASM disk groups, parts of datafiles, it will use the dictionary if usable for DUL (even an older backup of the dictionary works most data is relative static).
 
Most Oracle features supported. There is also functionality to mine damaged exp and expdp dumpfiles.
 

 

Most important features

 

  • RDBMS versions supported from as early as 6.0.34 up to the latest production software
  • Standalone program written in C
  • Platform independent, cross platform unloading fully supported
  • Output in SQL*Loader (stream or fixed record) or export format
  • DUL will not dump or crash however bad its input is
  • All normal datatypes including adt's, varrays and clobs, blobs, cfiles and bfiles
  • Direct reads of datafiles on asm, no asm instance needed
  • Unexp and unpump commands to recover data from corrupted dump files
  • Retrieve data from corrupt not mounted filesystems (scan device, create block index)
  • Parts of data files as small as a single block
  • Easy of configuration through datafile/disk header inspection
  • Recover data from an accidentally truncated table

 

Restrictions

  • 11g secure file lobs are not supported yet.
  • Label security
  • Encryption
  • 11g ASM with variable extent sizes and ASM striping support is available on request in a beta
  • Asm disks on exadata cells (no idea how to read those efficiently yet)
  • Complex types not supported in export_mode
  • The generated dump file in export_mode=true contains minimal create and insert statement to allow the table to load, metadata not included.