Upgrade from 2.5.3 v172 to 2.9.0: There is no active transaction

[mic...@buchmann.ruhr]

Hi all,
I have a working version 2.5.3 v172 on ubuntu 18.4 LTS. Now I want to update to 2.9 on ubuntu 24.4 LTS
All installation works fine and I get a working system with empty data.
Then I followed the instruction here:
https://www.accesstomemory.org/de/docs/2.9/admin-manual/installation/upgrading/#installation-upgrading

and even included step four. Database import works fine.
The upgrade task however stops after some time with a red error message:

There is no active transaction

The command

php  symfony tools:get-version

shows 2.9.0 v178. I found this discussion:

https://groups.google.com/g/ica-atom-users/c/zVQLw1G0XV0/m/N7pMi4ONBQAJ

which seems to address a similar issue. Unfortunately the mentioned

links like https://projects.artefactual.com/issues/13641 do not open.

The fix menioned in the very beginning of the discussion does not help.

Any Idea?

Michael

[Amaya Rodrigo]

Michael, I am attaching a PDf with the issue discussed there, also here: https://github.com/artefactual/atom/pull/1578

Also, keep in mind this upgrade path is way too much, it should work, but really doesn't.

Can you attempt the upgrade in more steps?

I hope this helps, but let us know if you need further assistance. 

--
You received this message because you are subscribed to the Google Groups "AtoM Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ica-atom-user...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/ica-atom-users/7351f9e7-6776-48d3-b7cf-d4e5317fb9fcn%40googlegroups.com.

--

Amaya M Rodrigo Sastre (she/her/bofh) - sysadmin@artefactual 

<arod...@artefactual.com >|< https://www.artefactual.com >

[mic...@buchmann.ruhr]

Hi,

Thanks for sharing the info. I was able to migrate from 2.5.3 v172 to 2.6.4 v184 and then to 2.9.0 v193. This worked fine.

Just the command:

php -d memory_limit=-1 symfony tools:upgrade-sql

during the second step needed an additional n="193" to work.

Thanks for the help.

MIchael

[Amaya Rodrigo]

MIchael,

Awesome! I am very happy this worked, finally!

I'm curious what's the meaning of n="193"  (never had to use it!) and thank you for adding that detail, it might help others later.

Thanks!

To view this discussion visit https://groups.google.com/d/msgid/ica-atom-users/7060277a-332e-426c-a9b8-9630752c3ef9n%40googlegroups.com.

[José Raddaoui]

Hi there,

The `-n` flag is used to run a single migration:

https://github.com/artefactual/atom/blob/qa/2.x/lib/task/migrate/arUpgradeSqlTask.class.php#L54

Only applying that migration may not be enough for the upgrade, as it will be missing migrations 185 to 192.

Best.

[John Coquitlam]

Hi everyone,
We are having similar issue when upgrading from 2.8.0 - 193 to 2.9.1 - 184

When we do php -d memory_limit=-1 symfony tools:upgrade-sql, we get 'There is not active transaction'.

Then we try php -d memory_limit=-1 symfony tools:upgrade-sql -n="184" and it works but doing
php symfony digitalobject:regen-derivatives, we get Column not found: 1054 Unknown column 'digital_object.LANGUAGE' error.

Jose's comments mention it is missing migrations 2.8.0 193 to 2.9.1 184.
How do we do the upgrade-sql statement for the missing migrations?
In another thread, there was an example of

php -d memory_limit=-1 symfony tools:upgrade-sql -n="193"
php -d memory_limit=-1 symfony tools:upgrade-sql -n="192"
php -d memory_limit=-1 symfony tools:upgrade-sql -n="191"

Does it mean we repeat this 10x for 193 to 184?

Thank

John

[sergio...@gmail.com]

Hi, 

I am migrating Atom from 2.6.4 - 184 to 2.9.0 - 184. 

I run the command : php -d memory_limit=-1 symfony tools:upgrade-sql -n="184"

the returned message is:

>> upgrade-sql Successfully upgraded to Release 2.9.0 v184

The next step '"php symfony digitalobject:regen-derivative" returns

[wrapped: SQLSTATE[42S22]: Column not found: 1054 Unknown column 'digital_object.LANGUAGE' in 'field list']

How did you solve the issue?

Regards

Sergio

[John Coquitlam]

Hi Sergio,

I was not able to resolve this.

I plan to upgrade to 2.9.2 to see if the error will go away.

At least you are more successful, as you did not get the no active transaction error.

Thanks,

John