Step #1
Remove the failing migration from the DB with the following command:
DELETE from access_schema_version where version='7.82.0.1'
This allows the migration to run again on the next restart (DO NOT RESTART AT THIS POINT).
Step #2
Choose one of the following solutions:
1. Elevate the DB user permissions so it can create TRIGGERs.
2. If you’re using MySQL or MariaDB, set the flag
SET GLOBAL log_bin_trust_function_creators = 1;
which allows the creation of TRIGGERs and FUNCTIONs.
You can remove the flag after the migration is complete.
3. Starting Artifactory 7.77.5, you can manually review and apply the TRIGGERs to your DB and skip their automatic creation during the migration.
The trigger scripts for the different DBs are attached in this zip file.
To skip the trigger creation, set either one of the following properties:
Java System property:
jf.access.skip_pv2_legacy_tables_lock=true
Environment Variable:
JF_ACCESS_SKIP_PV2_LEGACY_TABLES_LOCK=true
Important: Do not restart the migration and skip the TRIGGERs creation before manually setting the TRIGGERs!
It can cause a data loss of permissions in the system (if you add/remove/edit permissions while some nodes in your JPD were not upgraded, you will lose these changes).
Step #3
You are ready to run the migration again.
Upgrade your nodes to the new version, the migration will succeed.