Hi!

did you try to either perform a fresh installation of the App on the device or remove cache and data for the FSM App?

Best regards
Roman

Hi Roman,

yes we tried to uninstall and install the app and we overcome this issue. Our post is mainly focusing on finding the root cause of the issue to fix it and avoid having this issue in the future.

Thanks,

G.T

Hi George,

I’m not totally sure as I haven’t seen this error before. This is the description of the SQLLITE_BUSY result code:

“The SQLITE_BUSY result code indicates that the database file could not be written (or in some cases read) because of concurrent activity by some other database connection, usually a database connection in a separate process.” (source: https://www.sqlite.org/rescode.html)

Further, the PRAGMA cache_size is described as following:

“Query or change the suggested maximum number of database disk pages that SQLite will hold in memory at once per open database file.” (source: https://www.sqlite.org/pragma.html)

The obvious reason would be that the mobile database on the device couldn’t be created / updated because of a concurrent write activity. If it was a on-off issue, I wouldn’t bother to investigate in more detail now as it could be just something temporary. However, if you will receive this error quite frequently I would suggest to raise a support case.

Best regards
Roman