26.07.2011 16:46, Alessandro Fiorino wrote:
> Already tried it says it can't recover anything. Also tried ibrecovery
> and it only recovers 20% of the data, less that what I have from my
> last backup.
The IBSurgeon team also offers manual database recovery and they're
experienced in that. Perha
26.07.2011 16:30, Alessandro Fiorino wrote:
> I've been at least a bit lucky: the record structure of the data I
> want to recover is simple and I already found how to detect a record
> and decode all the other fields (a varchar which always store a 17
> chars string and two integers).
> The da
Already tried it says it can't recover anything. Also tried ibrecovery
and it only recovers 20% of the data, less that what I have from my
last backup.
But if I open the file with an hex editor I can SEE that almost all
the data is there, even rows inserted just before the crash, I just
need to dec
26.07.2011 14:30, Alessandro Fiorino wrote:
> I've been at least a bit lucky: the record structure of the data I
> want to recover is simple and I already found how to detect a record
> and decode all the other fields (a varchar which always store a 17
> chars string and two integers).
Don't
Thanks for your fast reply!
I've been at least a bit lucky: the record structure of the data I
want to recover is simple and I already found how to detect a record
and decode all the other fields (a varchar which always store a 17
chars string and two integers).
The database is in ODS 11 format
26.07.2011 16:00, Alessandro Fiorino wrote:
> Can someone point me to where can I found in the source how a DECIMAL
> field is encoded when saved on disk ?
> I need it to manually recover a broken database.
It depends on its declared precision and database dialect.
Also, you're unlikely to detec
Can someone point me to where can I found in the source how a DECIMAL
field is encoded when saved on disk ?
I need it to manually recover a broken database.
Thanks in advance.
--
Magic Quadrant for Content-Aware Data Loss
