TUFLOW Message 0642: Difference between revisions

Content deleted Content added

Revision as of 15:06, 30 September 2024 view source Emilie Nielsen (talk \| contribs) Administrators 6,146 edits No edit summary ← Older edit		Latest revision as of 14:07, 4 July 2025 view source Teegan.Burke (talk \| contribs) Bureaucrats, Administrators 430 edits mNo edit summary Tag: Visual edit: Switched
(5 intermediate revisions by one other user not shown)
Line 10: * Ensure the GeoPackage database exists, and all file references in the TUFLOW control files are correct. * Check the GeoPackage layer name contains no spelling mistakes. * If the GeoPackage is reported as locked due to concurrent TUFLOW simulations, you can try adding the following command "<tt><font color="blue">GPKG Inputs Read Only </font><font color="red">== </font> ON</tt>" to the TCF. This tells TUFLOW to open the GPKG inputs in a strict read only mode which, in turn, should prevent TUFLOW from creating any locks on GPKG inputs. You can also try adding the following command "<tt><font color="blue">SQLite On Open SQL Read </font><font color="red">== </font>PRAGMA busy_timeout = 10000;</tt>" (note the semicolon at the end) to the TCF. This command sets the busy timeout to 10s which should give any read locks time to be let go by other TUFLOW simulations. Finally, running the model from a local directory (e.g. C drive) should also eliminate any read locks. \|uplink=[[0xxx_TUFLOW_Messages\|0xxx Messages]]