JDBC Mysql persistence in OH3

@Logos Hi Rolf,
I assume you are also running OH 3.1, right? It is not clear to me which change caused the trouble the upgrade to OH 3 or the move from mariadb5 to mariadb10. It looks to me that you made two changes at once?

Here is my jdbc.cfg:

url=jdbc:mariadb://<ip_address>:3307/<mariadb_name>?useLegacyDatetimeCode=false&serverTimezone=Europe/Berlin

user=xxx
password=yyy
default_time_zone='Europe/Berlin'

reconnectCnt=0
waitTimeout=28800

sqltype.LOCATION      =   VARCHAR(256)
sqltype.STRING         =   VARCHAR(4096)
sqltype.IMAGE          =   BLOB

Did you create a new database in MariaDB10 or did you move your old database from v5 to V10?
When you migrate from OH2.5 to OH3 you should definitely create a new database following these instructions:

Somewhere in the web there is also a description how to exactly do it on a Synology NAS when leveraging the phpMyAdmin app that you can install from the Synology community. It creates the empty database with all required grants and rights.