It is rather unusual location but it is possible. I'm sorry for my mistake, the location of the database is not bound to the java.io.tmpdir variable but it is located in working directory by default and can be changed by a property. More information can be found in our documentation
. I would suggest to create a backup of the directory (cloverDb102) and then delete it from there.
Also, it could be beneficial to utilize a "real" SQL database to prevent such an issue from happening in the future.
Hope this helps.