Another upgrade issue from 2.34.6 to 2.35.6

Hi @sagbodjan ,

Seems like the upgrade introduced a bad value into your database; I’ll have an extra look at that to make sure we’ll sort that out.

However, for you current case, you should just delete the affected row for now. You can use the following SQL:

DELETE FROM jobconfiguration WHERE jobtype = 'REMOVE_USED_OR_EXPIRED_RESERVED_VALUES'

Some extra information:
This job refers to a system job. The job was used to trim down the number of rows in a table named “reservedvalues”.

If you have automatically generated tracker attribute values (Tracker attributes → unique → generated), every value generated will be put into this table called “reservedvalues”. We previously used this table for validation during import, but recently moved away from this notion as the validation was uneccesary based on the requirements, and put extra strain on the import process.

Removing this job should not have any direct impact on your instance.

What you could also do, is have a look and see if your jobconfiguration table contains any jobs of the type “REMOVE_EXPIRED_RESERVED_VALUES”. This was the former name of this job. If it is missing, you can manually add the job back using SQL if you want to put the table back into it’s normal state (I’m not sure it would be a big issue to leave it though).

The SQL to look for that job:

SELECT * FROM jobconfiguration WHERE jobtype = 'REMOVE_EXPIRED_RESERVED_VALUES'
2 Likes