Ora-01882 is a known issue on Oracle side, here is the solution and workaround from [ID 1068063.1]:
"The solution is to use a timezone supported by the database. This can be done by setting the TZ environment variable. When TZ is set, its value will be used rather than the operating system default timezone.
The workaround is to set the connection property oracle.jdbc.timezoneAsRegion to "false". This reverts to the old style of session timezone behavior."