iOS Ultralite 12.0.1 SQLE_FILE_BAD_DB

[Former Member]

So we had a user who's database became "Bad" (SQLCODE -1006 (SQLE_FILE_BAD_DB)). It was just one instance and the user had not syncronized the database in quite awhile. Can anyone explain under what circumstances an ultralite database can become "Bad" and common practices to avoid this in the future? Thanks!

[former_SQLA_member1694876]

This code is raised on startup if UL detects a corrupted database file (the first page in the database is inconsistent or the length of the file is incorrect). It is also raised on subsequent startup if UL is terminated during an uninterruptible operation, such as changing the encryption key.