InfluxDB Data type

Hi,

I just migrated hard to Openhab 3.0.
Now the logs show multiple different errors like this.
Any idea how to fix it? Could I just delete the whole database? If yes, where is it located?

Daniel

==> /log/openhab.log <==
2020-12-23 17:09:44.925 [ERROR] [org.influxdb.impl.BatchProcessor    ] - Batch could not be sent. Data will be lost
org.influxdb.InfluxDBException$FieldTypeConflictException: partial write: field type conflict: input field "value" on measurement "Speedtest_LUD" is type integer, already exists as type float dropped=1
	at org.influxdb.InfluxDBException.buildExceptionFromErrorMessage(InfluxDBException.java:144) ~[bundleFile:?]
	at org.influxdb.InfluxDBException.buildExceptionForErrorState(InfluxDBException.java:173) ~[bundleFile:?]
	at org.influxdb.impl.InfluxDBImpl.execute(InfluxDBImpl.java:827) ~[bundleFile:?]
	at org.influxdb.impl.InfluxDBImpl.write(InfluxDBImpl.java:460) ~[bundleFile:?]
	at org.influxdb.impl.OneShotBatchWriter.write(OneShotBatchWriter.java:22) ~[bundleFile:?]
	at org.influxdb.impl.BatchProcessor.write(BatchProcessor.java:340) [bundleFile:?]
	at org.influxdb.impl.BatchProcessor$1.run(BatchProcessor.java:287) [bundleFile:?]
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) [?:?]
	at java.util.concurrent.FutureTask.run(FutureTask.java:264) [?:?]
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304) [?:?]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) [?:?]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [?:?]
	at java.lang.Thread.run(Thread.java:834) [?:?]


See [influxdb] FieldTypeConflictException: “…” is type integer, already exists as type float · Issue #9037 · openhab/openhab-addons · GitHub

At [influxdb] FieldTypeConflictException: “…” is type integer, already exists as type float · Issue #9037 · openhab/openhab-addons · GitHub in the above thread a temp. solution / workaround is described.

Thank you! This does not seem to be workable for a docker setup. I cannot even put the bash script into the container.

executing

select value::integer into temp from Flur_Bell_Lock

on the database for a single value gives me a timeout error.

Is there a way to delete the database?