That's when the ojdbc driver and the database don't play nicely together regarding time zones, i.e. the ojdbc driver sends a time zone ID to the DB server that the server doesn't know.
What Ivy and Oracle DB versions are you using exactly?
One way to fix it would be to downgrade (or upgrade, if your Oracle DB server is newer) the ojdbc library.
If you don't want to change the ojdbc version, a workaround would be to specify `-Doracle.jdbc.timezoneAsRegion=false` in the Engine system properties (by setting it in the `ivy.vm.additional.options` in your .iml .ilc file in the /bin folder).