Oracle FAQ Your Portal to the Oracle Knowledge Grid

Home -> Community -> Usenet -> c.d.o.server -> Re: MYDUL avaialbe for recovery, another choise of DUL.

Re: MYDUL avaialbe for recovery, another choise of DUL.

From: <>
Date: 28 Sep 2005 09:52:33 -0700
Message-ID: <>

> > Many utilities exist that can read MS Office formats, some of
> > them are open source - this seems analagous to me.
> Reading the contents of a Word document is far different, to me, than
> reading the contents of a corrupted, proprietary-format datafile,
> especially with a tool that is incomplete, as admitted by the
> programmer. Lacking the ability to recover LOB data, comporessed
> indexes and IOTs certainly leads me to wonder why I should trust such a
> tool to correctly read any other data in a corrupted file. The OP has
> claimed his tool is "ready for recovery", yet misses some data
> structures, meaning tables with LOB columns will be incomplete upon
> 'recovery', IOTs will be missing as well as compressed indexes. To me
> this is a failed attempt at reverse-engineering DUL; it is also an
> accident waiting to happen. Using this 'tool' to 'recover' corrupted
> datafiles would violate any service agreements between Oracle and the
> party using said 'tool' as it is NOT Oracle's DUL utility. There is
> nothing good about this work as I see the situation. Possibly I am
> wrong about the legality of this software and the process used to
> create it; from what I have read thus far I do not believe I am. That
> notwithstanding, this 'tool' is a hazard for anyone to use, whether it
> be legal or not. I certainly wouldn't trust it to recover my data.

Something else that comes to mind involves the PC BIOS.

Years ago some companies decided to create BIOS emulators. Phoenix for instance.

When hiring engineers to create the BIOS code, the candidate engineers had to be interviewed by attorneys to ensure that the engineers were 'virgin', that is, they had never had any involvement with IBM BIOS, and had in fact never even seen the code.

Producing a BIOS that emulated IBM's was legal under these conditions, as they were not reverse engineering the code, but producing new code that emulated the behavior of the IBM BIOS.

Jared Received on Wed Sep 28 2005 - 11:52:33 CDT

Original text of this message