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.

---------------------------------------------------------------
 ./sqlite-2.8.17.bin  /home/jayanth/to_drh/media.vdb.corrupt
Unable to open database "/home/jayanth/to_drh/media.vdb": file is encrypted or 
is not a database
------------------------------------------------------------

Regards
Jayanth


On Mon, 13 Nov 2006 [EMAIL PROTECTED] wrote :
>"jayanth KP" <[EMAIL PROTECTED]> wrote:
> > Hi,
> >
> >     I am using sqlite 2.8.13 which is supposed to have fix for "Corrupt 
> > problem encountered on Windows NT platform" check this 
> > (http://www.sqlite.org/cvstrac/tktview?tn=599). But the code in pager.c 
> > still has the following rc = write32bits(&pPager->jfd, pPager->noSync ? 
> > 0xffffffff : 0); . But as suggested in the fix it should have been rc = 
> > write32bits(&pPager->jfd, 0xffffffff); .
> >
> > I also saw 2.8.13 and 2.8.12 code in sqlite CVS. Even that does not have 
> > the suggested change
> >
> > Can anybody Please  explain ..
> >
>
>I took the after-power-failure sample database you sent me and
>opened it using SQLite version 2.8.17.  That worked great.  There
>were no errors.  PRAGMA integrity_check showed that the database
>was recovered intact.
>
>I suggest you download the latest 2.8.17 code and recompile
>using that.
>--
>D. Richard Hipp  <[EMAIL PROTECTED]>
>
>
>-----------------------------------------------------------------------------
>To unsubscribe, send email to [EMAIL PROTECTED]
>-----------------------------------------------------------------------------
>


Reply via email to