This site is intended to keep you up-to-date with the latest developments of DUDE.
DUDE (Database Unloading by Data Extraction) is a database unloader - it's able to bypass Oracle's database engine, extracting data directly at the block level.
This way, the database doesn't have to be up and running to unload data - what's more, DUDE is specifically designed to extract data when the database is down and/or corrupted.
It can be used for data that can not be retrieved any other way (even when you've lost your system tablespace). However, it should not be considered as a replacement for other Oracle utilities like sql*plus or exp/imp. It should be used as a last resort to recover your data, when everything else fails.
DUDE was also known as jDUL. jDUL refers to Oracle DUL (Data Unloader).
DUDE basically offers the same functionality as DUL in a multi-platform java environment.DUDE is a standalone java program - and therefore can be run on every platform supporting java (1.2.x or higher is recommended).
DUDE is available as a service or as a product.
I n most cases, loss of service can be fatal for a business - therefore, DUDE is also available as a product. This way, no valuable time is lost getting a consultant on-site, or uploading datafiles. T his option can - for example - be used for databases that contain sensitive data (credit card numbers, medical patient files) that should never leave your server.
A limited 'proof of concept' version is available on request.
jDUL/DUDE v 2 .6 .6 currently supports :
 |
creation of blockmap | ||||||||||||||
| |
recreation of the Oracle dictionary | ||||||||||||||
| |
autodetection of file number and blocksize of datafiles | ||||||||||||||
| |
performing a describe of tables | ||||||||||||||
| |
extracting tables based on object id or tablename | ||||||||||||||
| |
extracting entire tablespaces | ||||||||||||||
| |
extracting partitioned tables (including subpartitions) | ||||||||||||||
| |
extracting PLSQL code (packages, procedures, functions, triggers, ...) | ||||||||||||||
| |
generation of table DDL scripts | ||||||||||||||
| |
generation of sequence DDL scripts | ||||||||||||||
| |
generation of view DDL scripts | ||||||||||||||
| |
heuristic scanning : in case of missing SYSTEM tablespace - tables, columns, and datatypes are guessed through sampling of datasets | ||||||||||||||
| |
data can be extracted to :
|
||||||||||||||
| |
all major intel & unix platforms are supported : windows, linux, IBM AIX, Sun Solaris/SunOS, HPUX, Tru64, Open VMS (on alpha) | ||||||||||||||
| |
datatypes supported : NUMBER, CHAR, VARCHAR2, LONG, DATE, RAW, LONG RAW, BLOB, CLOB, TIMESTAMP (+9i) , BINARY FLOAT, BINARY DOUBLE (+10g) | ||||||||||||||
| |
LOB support :
|
||||||||||||||
| |
supports Oracle RDBMS versions 7, 8.0, 8i, 9i,10g and 11g | ||||||||||||||
| |
supports Oracle RDBMS versions migrated using the mig utility | ||||||||||||||
| |
supports Oracle 10g BIGFILE tablespaces | ||||||||||||||
| |
cross-platform unloading : for example unloading AIX based datafiles on a Windows host | ||||||||||||||
| |
Compressed table blocks and 11g table compression (currently in beta) | ||||||||||||||
| |
chained & migrated rows, trailing NULL columns, first free row index, intra-block chaining |
DUDE v 2 .6 .6 currently does not support :
| |
IOT's - index organized tables |
| |
ASM support |
What can be recovered :
| |
Inconsistent restores/recoveries or any situation preventing your datase from opening, like
|
||||||
| |
the loss of system tablespace : in case of a missing data dictionary, a heuristic scanner will examine the data and will try to determine datatypes and columns | ||||||
| |
orphaned datafiles : same as the loss of the system tablespace, even if you only have one datafile left - data can be extracted | ||||||
| |
dropped tablespaces : if the datafiles still exist, data can be recovered | ||||||
| |
dropped tables : freeze the application/database and make a copy of the affected datafile(s) immediate to improve chances of recovery | ||||||
| |
truncated tables : same as dropped tables | ||||||
| |
dropped columns |
DUDE is not an alternative for Oracle exp or SQL*Plus utilities. You should only use DUDE when :
| |
you’re unable to open the database using standard restore and recovery techniques |
| |
you're unable to open the database using non-standard recovery techniques (use of hidden parameters - _allow_..._corruption) |
| |
Oracle Support tells you the database is death, gone, kapot, cassé, tod, roto - but data can be recovered using a DUL-like too l |
| |
you accept the fact that there's NO guarantee - there's a reason why the database doesn't open anymore ! (this is true for all DUL-like tools) |
This site is intended to keep you up-to-date with the latest developments of DUDE.
DUDE (Database Unloading by Data Extraction) is a database unloader - it's able to bypass Oracle's database engine, extracting data directly at the block level.
This way, the database doesn't have to be up and running to unload data - what's more, DUDE is specifically designed to extract data when the database is down and/or corrupted.
It can be used for data that can not be retrieved any other way (even when you've lost your system tablespace). However, it should not be considered as a replacement for other Oracle utilities like sql*plus or exp/imp. It should be used as a last resort to recover your data, when everything else fails.
DUDE was also known as jDUL. jDUL refers to Oracle DUL (Data Unloader).
DUDE basically offers the same functionality as DUL in a multi-platform java environment.DUDE is a standalone java program - and therefore can be run on every platform supporting java (1.2.x or higher is recommended).
DUDE is available as a service or as a product.
I n most cases, loss of service can be fatal for a business - therefore, DUDE is also available as a product. This way, no valuable time is lost getting a consultant on-site, or uploading datafiles. T his option can - for example - be used for databases that contain sensitive data (credit card numbers, medical patient files) that should never leave your server.
A limited 'proof of concept' version is available on request.
jDUL/DUDE v 2 .6 .6 currently supports :
| |
creation of blockmap | ||||||||||||||
| |
recreation of the Oracle dictionary | ||||||||||||||
| |
autodetection of file number and blocksize of datafiles | ||||||||||||||
| |
performing a describe of tables | ||||||||||||||
| |
extracting tables based on object id or tablename | ||||||||||||||
| |
extracting entire tablespaces | ||||||||||||||
| |
extracting partitioned tables (including subpartitions) | ||||||||||||||
| |
extracting PLSQL code (packages, procedures, functions, triggers, ...) | ||||||||||||||
| |
generation of table DDL scripts | ||||||||||||||
| |
generation of sequence DDL scripts | ||||||||||||||
| |
generation of view DDL scripts | ||||||||||||||
| |
heuristic scanning : in case of missing SYSTEM tablespace - tables, columns, and datatypes are guessed through sampling of datasets | ||||||||||||||
| |
data can be extracted to :
|
||||||||||||||
| |
all major intel & unix platforms are supported : windows, linux, IBM AIX, Sun Solaris/SunOS, HPUX, Tru64, Open VMS (on alpha) | ||||||||||||||
| |
datatypes supported : NUMBER, CHAR, VARCHAR2, LONG, DATE, RAW, LONG RAW, BLOB, CLOB, TIMESTAMP (+9i) , BINARY FLOAT, BINARY DOUBLE (+10g) | ||||||||||||||
| |
LOB support :
|
||||||||||||||
| |
supports Oracle RDBMS versions 7, 8.0, 8i, 9i,10g and 11g | ||||||||||||||
| |
supports Oracle RDBMS versions migrated using the mig utility | ||||||||||||||
| |
supports Oracle 10g BIGFILE tablespaces | ||||||||||||||
| |
cross-platform unloading : for example unloading AIX based datafiles on a Windows host | ||||||||||||||
| |
Compressed table blocks and 11g table compression (currently in beta) | ||||||||||||||
| |
chained & migrated rows, trailing NULL columns, first free row index, intra-block chaining |
DUDE v 2 .6 .6 currently does not support :
| |
IOT's - index organized tables |
| |
ASM support |
What can be recovered :
| |
Inconsistent restores/recoveries or any situation preventing your datase from opening, like
|
||||||
| |
the loss of system tablespace : in case of a missing data dictionary, a heuristic scanner will examine the data and will try to determine datatypes and columns | ||||||
| |
orphaned datafiles : same as the loss of the system tablespace, even if you only have one datafile left - data can be extracted | ||||||
| |
dropped tablespaces : if the datafiles still exist, data can be recovered | ||||||
| |
dropped tables : freeze the application/database and make a copy of the affected datafile(s) immediate to improve chances of recovery | ||||||
| |
truncated tables : same as dropped tables | ||||||
| |
dropped columns |
DUDE is not an alternative for Oracle exp or SQL*Plus utilities. You should only use DUDE when :
| |
you’re unable to open the database using standard restore and recovery techniques |
| |
you're unable to open the database using non-standard recovery techniques (use of hidden parameters - _allow_..._corruption) |
| |
Oracle Support tells you the database is death, gone, kapot, cassé, tod, roto - but data can be recovered using a DUL-like too l |
| |
you accept the fact that there's NO guarantee - there's a reason why the database doesn't open anymore ! (this is true for all DUL-like tools) |