Re: [keycloak-user] DB error
Hi Cedric,
On Tue, Sep 11, 2018 at 12:39 PM, cedric(a)couralet.eu <cedric(a)couralet.eu>
wrote:
Hi,
I just had the same problem. Mine was from the fact the database was
already in version 4.x (table CLIENT_SCOPE created), but the value in table
MIGRATION_MODEL was 3.4.3 so Keycloak was trying to execute the migration
steps here :
https://github.com/keycloak/keycloak/blob/master/server-
spi-private/src/main/java/org/keycloak/migration/migrators/
MigrateTo4_0_0.java#L77
and failed due to the constraint.
My solution (surely not the best) was to update the value in
MIGRATION_MODEL to 4.0.0 and restart the service.
I think I was in that situation because I started an old instance (in
3.4.3) after the database ws migrated, but I'm not really sure how it is
possible.
Exactly, I started keycloak version 3.4.3, while the DB was already
migrated to 4.3.0. It usually goes pretty badly.
Is there anything we can do to prevent crashes when starting (by mistake) a
previous versions of Keycloak?
Cédric Couralet
Le Mardi, Septembre 11, 2018 12:25 CEST, Corentin Dupont <
corentin.dupont(a)gmail.com> a écrit:
> Hi,
> I currently have this problem when starting keycloak:
>
> Caused by:
> com.mysql.jdbc.exceptions.jdbc4.MySQLIntegrityConstraintViolat
ionException:
> Duplicate entry 'master-role_list' for key 'UK_CLI_SCOPE'
>
> Any idea?
> Thanks
> _______________________________________________
> keycloak-user mailing list
> keycloak-user(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/keycloak-user