Difference between revisions of "TUFLOW Message 0642"
Jump to navigation
Jump to search
Ellis Symons (talk | contribs) |
Teegan.Burke (talk | contribs) m |
||
| (2 intermediate revisions by one other user not shown) | |||
| Line 10: | Line 10: | ||
* Ensure the GeoPackage database exists, and all file references in the TUFLOW control files are correct. | * 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. | * 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>GPKG Inputs Read Only == 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>SQLite On Open SQL Read == 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, | + | * 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]] | |uplink=[[0xxx_TUFLOW_Messages|0xxx Messages]] | ||
}} | }} | ||
Latest revision as of 14:07, 4 July 2025
TUFLOW Message
ERROR 0642 - opening geopackage database: <>.
Alternate Message
ERROR 0642 - "<>" is not in database.
ERROR 0642 - opening geopackage database: database is locked.
Message Type
ERROR
Description
TUFLOW is unable to open geopackage database or layer within database shown.
Suggestions
- If the GeoPackage database is open in a QGIS workspace, ensure that all edits have been saved and editing is turned off.
- 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 "GPKG Inputs Read Only == ON" 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 "SQLite On Open SQL Read == PRAGMA busy_timeout = 10000;" (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.
| Up |
|---|
 0xxx Messages
|