If you can get the errors, by say redirecting the output from the .read to
a file, the error message will likely be enlightening.  When I recover
corrupt db files, there are often some records with a conflicting primary
key.   In those cases I have to edit the input to fix the old one.
Naturally, you desire a commit rather than a rollback when your .read can
execute with no errors.

Others on the list are far better at explaining the output of the integrity
check than I am.

Adam


On Tue, May 14, 2013 at 11:40 AM, Marcin <ign...@op.pl> wrote:

> No errors, but tshockfixed.sqlite is empty, and in the end of file
> dump_all.sql there is "ROLLBACK; -- due to errors".
>
> It's was check of tshock.sqlite, old one.
>
> ignac8
>
> Sent: Tuesday, May 14, 2013 4:43 PM
> Subject: Re: [sqlite] Malformed database recovery
>
>
>  Where there any errors on
>>
>> .read dump_all.sql ?
>>
>> was PRAGMA integrity_check;  on the new file or the old one?
>>
>>
>> On Tue, May 14, 2013 at 10:29 AM, Marcin <ign...@op.pl> wrote:
>>
>>  Hi everybody.
>>>
>>> Somehow my database got malformed, and journal file is unfortunately
>>> nowhere to found.
>>>
>>> Suprisingly, I'm able to open it in Sqlite Database Browser, and read
>>> stored values. There is only minor data loss, as I can't really see what
>>> got missing. I've also managed to figure which table is damaged.
>>>
>>> I've tried doing this:
>>>
>>> sqlite3.exe tshock.sqlite
>>> sqlite> .mode insert
>>> sqlite> .output dump_all.sql
>>> sqlite> .dump
>>> sqlite> .exit
>>> sqlite3.exe tshockfixed.sqlite
>>> sqlite> .read dump_all.sql
>>> sqlite> .exit
>>>
>>> But it still returns malformed one.
>>>
>>> PRAGMA integrity_check; returns this:
>>>
>>> *** in database main ***
>>> On tree page 3 cell 17: invalid page number 9049
>>> On tree page 3 cell 17: Child page depth differs
>>> On tree page 3 cell 18: Child page depth differs
>>> On tree page 8948 cell 86: invalid page number 9047
>>> On tree page 8948 cell 86: Child page depth differs
>>> On tree page 8948 cell 87: invalid page number 9051
>>> On tree page 8948 cell 88: invalid page number 9055
>>> On tree page 8948 cell 89: Child page depth differs
>>> On tree page 8948 cell 90: invalid page number 9061
>>> On tree page 8948 cell 90: Child page depth differs
>>> On tree page 8948 cell 91: invalid page number 9066
>>> On tree page 8948 cell 92: invalid page number 9069
>>> On page 8948 at right child: invalid page number 9074
>>> On tree page 9039 cell 69: invalid page number 9046
>>> On tree page 9039 cell 69: Child page depth differs
>>> On tree page 9039 cell 70: invalid page number 9048
>>> On tree page 9039 cell 71: invalid page number 9050
>>> On tree page 9039 cell 72: invalid page number 9052
>>> On tree page 9039 cell 73: invalid page number 9053
>>> On tree page 9039 cell 74: invalid page number 9054
>>> On tree page 9039 cell 75: invalid page number 9056
>>> On tree page 9039 cell 76: invalid page number 9057
>>> On tree page 9039 cell 77: invalid page number 9058
>>> On tree page 9039 cell 78: invalid page number 9059
>>> On tree page 9039 cell 79: invalid page number 9060
>>> On tree page 9039 cell 80: invalid page number 9062
>>> On tree page 9039 cell 81: invalid page number 9063
>>> On tree page 9039 cell 82: invalid page number 9064
>>> On tree page 9039 cell 83: invalid page number 9065
>>> On tree page 9039 cell 84: invalid page number 9067
>>> On tree page 9039 cell 85: invalid page number 9068
>>> On tree page 9039 cell 86: invalid page number 9070
>>> On tree page 9039 cell 87: invalid page number 9071
>>> On tree page 9039 cell 88: invalid page number 9072
>>> On tree page 9039 cell 89: invalid page number 9073
>>> On tree page 9039 cell 90: invalid page number 9075
>>> On tree page 9039 cell 91: invalid page number 9077
>>> On page 9039 at right child: invalid page number 9076
>>> Error: database disk image is malformed
>>>
>>> Does anybody got an idea, and can help me?
>>>
>>> ignac8
>>>
>>> ______________________________****_________________
>>> sqlite-users mailing list
>>> sqlite-users@sqlite.org
>>> http://sqlite.org:8080/cgi-****bin/mailman/listinfo/sqlite-****users<http://sqlite.org:8080/cgi-**bin/mailman/listinfo/sqlite-**users>
>>> <http://sqlite.org:8080/**cgi-bin/mailman/listinfo/**sqlite-users<http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users>
>>> >
>>>
>>>
>>
>>
>> --
>> VerifEye Technologies Inc.
>> 905-948-0015x245
>> 151 Whitehall Dr, Unit 2
>> Markham ON, L3R 9T1
>> Canada
>> ______________________________**_________________
>> sqlite-users mailing list
>> sqlite-users@sqlite.org
>> http://sqlite.org:8080/cgi-**bin/mailman/listinfo/sqlite-**users<http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users>
>>
>
> ______________________________**_________________
> sqlite-users mailing list
> sqlite-users@sqlite.org
> http://sqlite.org:8080/cgi-**bin/mailman/listinfo/sqlite-**users<http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users>
>



-- 
VerifEye Technologies Inc.
905-948-0015x245
151 Whitehall Dr, Unit 2
Markham ON, L3R 9T1
Canada
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Reply via email to