hibernate/hibernate-orm · error · HibernateException

Sequence was already registered with that name [<logicalName

Error message

Sequence was already registered with that name [<logicalName>]

What it means

Error "Sequence was already registered with that name [<logicalName>]" thrown in hibernate/hibernate-orm.

Source

Thrown at hibernate-core/src/main/java/org/hibernate/boot/model/relational/Namespace.java:146

		if ( existing != null ) {
			return (DenormalizedTable) existing;
		}
		else {
			final Identifier physicalTableName =
					physicalNamingStrategy.toPhysicalTableName( logicalTableName, jdbcEnvironment );
			final DenormalizedTable table = creator.apply( physicalTableName );
			tables.put( logicalTableName, table );
			return table;
		}
	}

	public Sequence locateSequence(Identifier name) {
		return sequences.get( name );
	}

	public void registerSequence(Identifier logicalName, Sequence sequence) {
		if ( sequences.containsKey( logicalName ) ) {
			throw new HibernateException( "Sequence was already registered with that name [" + logicalName.toString() + "]" );
		}
		sequences.put( logicalName, sequence );
	}

	public Sequence createSequence(Identifier logicalName, Function<Identifier,Sequence> creator) {
		if ( sequences.containsKey( logicalName ) ) {
			throw new HibernateException( "Sequence was already registered with that name [" + logicalName.toString() + "]" );
		}

		final Identifier physicalName = physicalNamingStrategy.toPhysicalSequenceName( logicalName, jdbcEnvironment );
		final Sequence sequence = creator.apply( physicalName );
		sequences.put( logicalName, sequence );
		return sequence;
	}

	@Incubating
	public Collection<UserDefinedType> getUserDefinedTypes() {
		return udts.values();

View on GitHub (pinned to fad1729dce)

Solutions

1. Use a unique sequence name per namespace, or reuse the existing registered sequence instead of registering a second one with the same name.

Example fix

Use a unique sequence name per namespace, or reuse the existing registered sequence instead of registering a second one with the same name.

When it happens

Trigger: An entity mapping annotation or bootstrap configuration violates a Hibernate mapping rule.

Common situations: Annotation mapping mistakes: inverse-side @Id associations, @Column on @OneToOne, unmapped association targets, mismatched @EnumeratedValue/@Temporal usage, duplicate sequence generators.

AI-assisted analysis of hibernate/hibernate-orm@fad1729dce (2026-08-22). Data as JSON: /api/errors/9f6f976592de17dd. Report an issue: GitHub.