HammerDB 4.7 fails to start on Windows if 4.6 SQLite files present

[sm-shaw]

HammerDB checks version number against the SQLite files and deletes and recreates them in case of mismatch. To check the version it opens the generic.db file. On Linux we can delete a file open for read, on Windows we get permission denied, this is not caught on startup and stops HammerDB starting on Windows.

The GUI, CLI and WS init files need updating to close SQLite before deleting the files and also to catch any error messages when trying to delete.

Example as follows:

#SQLite found, check whether the schema versions from SQLite and XML are consistent
if { $sqlite_hdb_version ne $hdb_version } {
puts "The existing SQLite DBs are from version $sqlite_hdb_version. SQLite DBs will be reset to $hdb_version."
# Close SQLite before deleting else get permission denied on Windows
if { [catch {hdb close} message]} { puts "Failed to close SQLite file: $message" }
foreach { dbname } { generic database db2 mariadb mssqlserver mysql oracle postgresql } {
set dbfile [ CheckSQLiteDB $dbname ]
if { [catch {file delete $dbfile} message]} { puts "Error deleting SQLite file from $sqlite_hdb_version: $message" }
}

[sm-shaw]

Bug also exists in v4.6 so if v4.7 has already been run and then v4.6 started it will show the same symptoms and not start.
Manual workaround is to remove the SQLite files manually from the defined directory (by default TEMP) before starting.