Problema actualizacion db en actualización a v6

cbrianso

Hola
He actualizado un dedalo v5.9.6, a v6.3.1, como se indica en el manual https://dedalo.dev/docs/update_v5/update_from_v5/

Ha funcionado bien, hasta la actualizacion de los datos, que no me deja, al entrar a dedalo, sale que la db esta desactualizada

Pero al ir a actualizar, aparece que esta actualizada y no sale la opcion de actualizar

Alguna cosa que se pueda hacer para forzar la actualizacion?

Gracias

PaCo

Hi cbrianso

1 . Check that your browser is loading the proper panel code. Open the browser inspector and disable the cache temporally. Login and try again.

If there are no changes, try reviewing the matrix_updates table. You should see something like this:

The last record of the table contains the last data update (it should be 5.9.6 in your case)
Verify that you have a path to subsequent updates, (e.g. 6.0.0) or edit/add a matrix_updates record to tell Dédalo that that is the last effective update done.

Good luck

cbrianso

Hi PaCo

Solved, it wasn't a cache problem, for some reason, when updating the version to dedalo 5.9.8 something failed and it didn't update properly.

Recovering a previous version, and updating again, this time it seems to have gone well, and I already get the database update message.

Thanks

Alex

In the update manual from v5 to v6 specify that you need to update from, at least, v.5.9.7. >=5.9.7

https://dedalo.dev/docs/update_v5/update_from_v5/#preparing-your-current-v5-installation

And you are trying to upgrade from v5.9.6 which may not be upgradeable to v6, therefore the upgrade process refuses to upgrade it.

Please read it carefully, and follow the steps.

Best

cbrianso

Alex

Hi, you are correct, in the documentation it says

Ensure that your code is >= 5.9.7
Ensure that your data is updated to 5.8.7
Ensure that your ontology version is > 01-07-2023

In my case, the versions are
code is 5.9.8
data is 5.9.6
ontology is 27-09-2024
all are higher than the required versions

Thanks for the comment, but it does not apply here, because you confused the data version with the code version

Best