From time to time we receive user reports about database crashes. Problems
seem to be iOS-related. (Given the number of reports it would be a
coincidence if other platforms worked flawlessly.)
Our testers finally managed to hit the problem, so I have a corrupted DB
file. On the other hand, that's all I have as the problem is not
reproducible.
Here is the result from integrity check:
sqlite> pragma integrity_check;
rowid 33 missing from index FK_systemuser_fullname
rowid 57 missing from index FK_systemuser_fullname
rowid 13 missing from index FK_account_name
rowid 23 missing from index FK_account_name
rowid 32 missing from index FK_account_name
rowid 39 missing from index FK_account_name
rowid 40 missing from index FK_account_name
rowid 52 missing from index FK_account_name
rowid 64 missing from index FK_account_name
rowid 84 missing from index FK_account_name
wrong # of entries in index FK_account_name
wrong # of entries in index FK_account_transactioncurrencyid // Guid
wrong # of entries in index FK_account_parentaccountid // Guid
wrong # of entries in index FK_account_ownerid // Guid
wrong # of entries in index FK_account_defaultpricelevelid // Guid
wrong # of entries in index sqlite_autoindex_account_1 // rowid
rowid 11 missing from index FK_annotation_subject
rowid 41 missing from index FK_annotation_subject
rowid 92 missing from index FK_annotation_subject
rowid 93 missing from index FK_annotation_subject
rowid 95 missing from index FK_annotation_subject
rowid 107 missing from index FK_annotation_subject
rowid 108 missing from index FK_annotation_subject
rowid 161 missing from index FK_annotation_subject
rowid 172 missing from index FK_annotation_subject
rowid 188 missing from index FK_annotation_subject
rowid 222 missing from index FK_annotation_subject
rowid 250 missing from index FK_annotation_subject
rowid 257 missing from index FK_annotation_subject
rowid 274 missing from index FK_annotation_subject
rowid 275 missing from index FK_annotation_subject
I marked Guid and rowid columns.
Remaining columns are of the type TEXT and use (custom) NOCASE collation.
The results from
sqlite3> SELECT rowid name FROM account;
look like this:
15|1A-Gesund Apotheken
40|A-Plus (Pharma Privat)
12|a.novum GmbH
34|ACO Apotheken Cooper
106|Ahorn Apotheke im Citypoint
....
11539|Geißsche Apotheke
7|Gesine
..........
9605|Meißner-Apotheke
..........
22080|Schloss Apotheke
22909|Schloss Apotheke
22984|Schlossberg-Apotheke
23255|Schlossgarten-Apotheke
21990|Schlosspark-Apotheke
etc.
ROWID's 1-112 seems to be correct. These rows are printed also by these
shell commands:
sqlite3> SELECT rowid name FROM account;
sqlite3> .dump
Remaining ROWID's are apparently corrupted and respective accounts are not
listed by above commands.
Has anybody any clue what can go wrong? I can add more details if usefull or
even send corrupted DB. (Just will have to convert it to plaintext,
hopefully this does not create other problems.)
Thanks in advance,
Jan
--
View this message in context:
http://sqlite.1065341.n5.nabble.com/What-can-be-deduced-from-integrity-check-tp70451.html
Sent from the SQLite mailing list archive at Nabble.com.
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
