Oracle Recovery Tools

The current research direction has been in the database with the server, the Oracle database often encountered, downtime, file corruption, file loss and other failures, and is currently writing software, let us look at the highlights of it!

• No need to run Oracle database software, EOR directly read the database file parsing data.

• ASM is supported to export data directly from ASM disks, even if the associated disk group does not succeed Mount

• Support for extracting data files and any other files stored in ASM (including control files, log files, archive logs, etc.) directly from ASM, even if the associated disk group does not succeed Mount

• In cases where ASM disk corruption is critical, EOR can scan ASM disks, extract data files that are not overwritten, and then extract and recover data.

• Supported versions of Oracle databases include 7,8I,9I,10G,11G,12C
  Support cross-platform operation, aix,hpux,linux,windows, etc.

• Supported data types include: number, CHAR, VARCHAR2, Nchar,nvarhcar2, Long, DATE, raw, long raw, BLOB, CLOB, TIMESTAMP (9i+), BINARY FLOAT, BINARY DOUBLE (10g+)
  

• Full support for LOB fields:

• Supports CLOB, NCLOB, and BLOBs

• CLOB supports big endian and little endian byte order

• Support for LOB partitions, sub-partitions

• Support for cases where different LOB columns use different chunk size in the same table

• CLOB data can be exported to the same file as other columns, or stored in a separate file

• LOB columns can still be exported without the system table space

• LOB columns can still be exported if the associated LOB index is corrupted

• Ability to recover Oracle 11g and above Securefile LOB (Securefile lob that currently does not support compression, de-weight, and encryption)

• supports a variety of tables, including regular heap tables, IoT tables, and clustered (CLUSTER) tables

• Support for IoT tables:

• Support for the export of ordinary IoT tables

• Supports the export of compact IoT tables

• Support for IoT table overflow segments

• Support for IoT table partitioning (including sub-partitions)

• You can export an IoT table only if you have a system table space

• Support Compression table

• Support for data recovery after table is truncate

• Data recovery after drop of support table

• Automatically get data dictionary information in the case of a system table space

• Support for recovering data without system tablespace and data dictionary corruption, EOR can automatically determine the type of data when no data dictionary is available

• Supports large file (bigfile) table spaces of 10g and above

• Fully supports 64-bit systems that support data files larger than 4G in size.

• A bad file that supports replication operating system commands that cannot be copied

• Supports data files of different block sizes in the same library.

• Supports conversions between multiple character sets to correctly convert data of CLOB, NCLOB, NVARCHAR2 column types to the specified character set.

• Automatically detect the tablespace number and file number of a data file

• The exported data format includes two types of plain text and DMP files. The ability to automatically generate SQL statements and Sql*loader import required control files when exporting as plain text

• The DESC table is supported to display the table's column definition
  

• Supports listing partitions and sub-partitions of tables

• Supports recovery of deleted data, even if there are LOB columns in the table of deleted data, even if the offset for all records in row directory in the deleted data table has been completely cleared by Oracle

Software basically can kill Oracle file damage failure, is working hard to develop, immediately published, and hope to make some database here Daniel, learn to learn!!

This article from "Sqlrecovery" blog, declined reprint!

Oracle Recovery Tools