DataIntegrityViolationException after upgrading from 6.2 to 7.2

• Type: Bug
• Status: Closed
• Resolution: Won't Fix
• Affects Version/s: 7.2.X
• Fix Version/s: None
• Component/s: Social Activity
• Labels:
  • ee-ts
• Fix Priority: 3
• Bug Type: Database Upgrade

This is hard to reproduce since it depends on the customer data.

The key point is that it is possible that after performing the upgrade the activitySetId value is bigger than the Counter::currentId value.

When it happens, while creating new activitySets a duplicated activitySetId could be used so the error happens.