Repository navigation
Problem migration with New Storage option --storage=jpa #14890
pablodiazv
started this conversation in
Archive
Replies: 1 comment 1 reply
|
See https://keycloak.discourse.group/t/upgrading-18-0-2-to-19-0-2/17883 you might be missing KC_DB property. |
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
I tried to migrate from postgres:11 to postgres:14 and use the new storage option --storage=jpa.
First, I did a backup from database and restore it in postgres 14 instance.
Then I start keycloak instance with:
start --cache-config-file=my-cache-ispn.xml --hostname-strict=false --hostname-strict-https=false --proxy edge --spi-connections-jpa-legacy-migration-strategy=update --spi-connections-jpa-legacy-initialize-empty=false --spi-connections-jpa-quarkus-migration-strategy=update --spi-connections-jpa-quarkus-initialize-empty=falseInstead the migration, the database is initialize from zero, as if the first execution was.
Without storage option data is ok in database.
ENVIROMENT:
All reactions