Problem
After an update and the subsequent database activation, the process takes significantly longer than usual, possibly several hours. During this time, logging in is not possible. No progress bar is displayed, and there is no feedback on whether the process is still running.
Applies to: updates from versions before 9.1.0.30996 (e.g. 8.x or 9.0.x) to version 9.1.0.30996 or later, including updates to version 26.x
Cause
Since version 9.1.0.30996, the encryption of the quality fields has been further strengthened. During the first database activation after the update, each record must therefore be reprocessed once.
In addition, the activation applies all database migrations added since your previous version. This also applies if you update directly to version 26.x, not only when updating to 9.1.0.30996. The duration depends strongly on the performance of your servers and the size of the database, so it cannot be predicted reliably. As a rough guideline, allow about 5 to 6 minutes per 1,000 passwords. This corresponds roughly to 1 hour per 10,000 passwords. This effort only occurs during the first activation. Later updates from version 9.1.0.30996 or higher are not affected.
Resolution
- Create a database backup before the update. You need it if the process is interrupted.
- Allocate sufficient server resources (RAM, CPU) to shorten the duration.
- Plan enough time for the update and the database activation, and inform your users that logging in is not possible during this time. As a rough estimate, allow about 5 to 6 minutes per 1,000 passwords. The actual duration depends on the performance of your servers.
- Start the database activation and wait until it has fully completed. As long as no error message appears, the process is still running in the background.
Important: Do not interrupt the process, either by restarting the server or by stopping the service. If the process is interrupted anyway, you must restore the database backup and restart the database activation from the beginning.