Hi Richard,
Thanks.. As you said. Now I tried to open the database that is not
corrupted with sqlite 2.8.13 (that we have). I have an intresting observation.
1.) I compiled sqlite 2.8.13 for PC (little endian) and ran sqlite binary on
the directory that had the journal also.
RESULT:
-------
It did a rollback successfully - So this means sqlite 2.8.13 is fine.
2.) I compiled sqlite 2.8.13 for a proprietary platform that we are using for
development(little endian) and ran sqlite binary on the directory that had the
journal also.
RESULT:
-------
The file is getting corrupted.
Please can you suggest to me what could be the issue. Or suggest to me where to
look for this issue.
Thanks and Regards
Jayanth
On Mon, 13 Nov 2006 [EMAIL PROTECTED] wrote :
>"jayanth KP" <[EMAIL PROTECTED]> wrote:
> > Hi Richard,
> > I downloaded the sqlite-2.8.17.bin from sqlite.org
> > (sqlite-2.8.17.bin.gz) and ran it on media.vdb.corrupt. I am getting the
> > following error . I am confused how were you able to open this file. Plz
> > open media..vdb.corrupt.
> >
>
>Once a file gets corrupted, there is nothing that can magically
>undo the corruption.
>
>What I did to open the file was put both the database as it
>appeared on disk after the power failure, but before it was
>opened by your broken version of sqlite, and the rollback
>journal together in the same directory. Then I opened the
>database with a working version of SQLite and it recovered
>the database correctly.
>
>--
>D. Richard Hipp <[EMAIL PROTECTED]>
>
>
>-----------------------------------------------------------------------------
>To unsubscribe, send email to [EMAIL PROTECTED]
>-----------------------------------------------------------------------------
>
