Revision History

2.0.0

• New module to recognize automatically the file type ( datafile, controlfile redolog file).
• dbname, dbid and  Oracle version are now displayed.
• New feature for extracting informations from control files ( versions 8i, 9i, 10g, 11g and  12c). Each section of the control file is "decrypted" :
      DATABASE,
      CKPT PROGRESS,
      REDO THREAD,
      REDO LOG,
      DATAFILE,
      FILENAME,
      TABLESPACE,
      TEMPORARY FILENAME,
      RMAN CONFIGURATION,
      LOG HISTORY,
      OFFLINE RANGE,
      ARCHIVED LOG,
      BACKUP SET,
      BACKUP PIECE,
      BACKUP DATAFILE,
      BACKUP REDOLOG,
      DATAFILE COPY,
      BACKUP CORRUPTION,
      COPY CORRUPTION,
      DELETED OBJECT,
      PROXY COPY,
      BACKUP SPFILE,
      EXTENDED DATABASE,
      DATABASE INCARNATION,
      FLASHBACK LOG,
      RECOVERY DESTINATION,
      INSTANCE SPACE RESERVATION,
      REMOVABLE RECOVERY FILES,
      RMAN STATUS,
      THREAD INSTANCE NAME MAPPING,
      MTTR,
      DATAFILE HISTORY,
      STANDBY DATABASE MATRIX,
      GUARANTEED RESTORE POINT,
      RESTORE POINT,
      DATABASE BLOCK CORRUPTION,
      ACM OPERATION,
      FOREIGN ARCHIVED LOG,
      PDB RECORD,
      AUXILIARY DATAFILE COPY,
      MULTI INSTANCE REDO APPLY,
      PDBINC RECORD
• New feature to check the synchronization of datafiles ( with informations from the control file ).
  If a file is not synchronized, db forensics is able to correct the problem by writing data to the header of datafile. 
  In particular, in situations where there is no backup ( with or without archivelog mode ), db forensics can help to restart a database :
  
  ERROR at line 1:
  ORA-01113: file 1 needs media recovery
  ORA-01110: data file ...
  
  ERROR at line 1:
  ORA-16004: backup database requires recovery
  ORA-01152: file 4 was not restored from a sufficiently old backup

1.3.1

Database export:

• Recover all files functionality
• Continue on error database export.
• SQL export
• Bug fix ORA-00972: identifier is too long.
• New option ' Create primary key' to enable / disable the creation of the primary key ID_QDUL.
•  ...table_D are not created if 'Active' is the only item selected.

Volume Scan functionalities are now implemented : 

• Start cluster / end cluster have been added.
• Sector size / sectors per cluster can be manually adjusted ( double-click on volume table row ).
• New option for raw disk image scan. The parameter offset allows you to skip possible metada added by some disk image software.
• Button next to "offset" allows to "guess" that offset ( experimental ).
• The volume scan function takes the byte order of the machine on which the scan is performed.An option allows to set it (little endian / big endian).
• Support for lob (PAGETABLE MANAGED LOB BLOCK), chained rows and long.
• Datafile extraction by file id ( SMALL FILE TABLESPACE ).
• Recognize ASM disks during the initialization phase of "volume scan" : cluster size , total number of clusters are automatically adjusted.
• Adding a security mechanism when the "end cluster" parameter exceeds the capacity of the disk ( linux disk ).
• Volume scan works for ASM disk  
• Extracting files spread across multiple ASM disk must be performed with db forensics ASM management module, which is not a data carving algorithm.
• Tests for "linux disks" : it allows Windows to read Linux file systems natively, providing access to the file system via a drive letter.