Hibernate with Oracle-Dialect only validates against Sequences of the currently logged in DB-User since 5.4.13. This is because this change, which only looks for user_sequences (before: all_sequences). .
But a very typical Setup is to use a DB-Run-User (without DDL Rights) and fully qualify sequences with the owner-schema, for example MYOWNER.MY_SEQUENCE. This does NOT work with Hibernate 5.4.13.Final and above anymore (Schema-Validation Error).
I think it can be fixed by changing this line to something like:
Select * from all_sequences where SEQUENCE_OWNER LIKE '<schema specified for sequence>';
Of course that would require passing the schema name to this function.
After reading a bit more about how oracle sequencing works I think the fix in should be reverted.
People who are experiencing this should simply use a User that does not have permission to see other conflicting sequences. Ideally a different User for every application.
I created to fix this.
This is a blocker for Springboot update. When can we expect to have this in a release ?
As a temporary workaround you can set the following property in maven and still update spring boot.
Sorry for my mistake. I’ve approved the PR