Well, again the problem is not that "sequence_name" is the primary key for the table. That is expected. The problem in what you are seeing is that the column is marked as nullable.

But I think I may see the problem.. I bet your app is resolving the table generator to org.hibernate.id.MultipleHiLoPerTableGenerator rather than org.hibernate.id.enhanced.TableGenerator. The former is deprecated and as far as I can tell does have the problem you mention.

You can try just setting hibernate.id.new_generator_mappings to true. The legacy default for this was false. Starting in CR4 that will default to true. I just assumed you were using the newer table-based gen strategy.

Anyway, I'll fix the deprecated org.hibernate.id.MultipleHiLoPerTableGenerator as well to generate that properly.