Error during upgrade to 8.0.1

Hello everybody,

We are migrating the instance of our customer, here are the detailed informations : 

  • SugarCRM v7.9.4.0
  • Flavor Enterprise
  • Oracle 12c
  • PHP 7.1.17
  • Oracle Linux 7.5
  • ElasticSearch 6.2.4
The healthcheck from v7.9.4.0 to 8.0.1 passed only with yellow flags, but when passing the upgrade to 8.0.1 we have the following error message (complete log in attachment) : 
Tue, 27 Jul 2021 15:12:09 +0200 [Upgrader] - Starting script 4_SynchronizeActivitiesRelationshipToEmailsBeansTable
Tue, 27 Jul 2021 15:12:10 +0200 [Upgrader] - part_c has an activities link named part_c_activities_1_emails
Tue, 27 Jul 2021 15:13:32 +0200 [Upgrader] - ERROR: Exception: An exception occurred while executing 'SELECT part_c.assigned_user_id, part_c.id, part_c.name FROM part_c ...
ORA-01795: maximum number of expressions in a list is 1000
Tue, 27 Jul 2021 15:13:32 +0200 [Upgrader] - Finished script 4_SynchronizeActivitiesRelationshipToEmailsBeansTable
Tue, 27 Jul 2021 15:13:32 +0200 [Upgrader] - ERROR: Post-upgrade stage failed! Error executing post scripts
After spending more than 2 hours to debug the upgrade tool (first time we're doing this at ITS4U Slight smile) we don't find any solution to fix the problem, and our instance is in a instable and not working state.
Is there anybody that faced the same issue ?
Is there any fix you can provide us or some trick to perform the next upgrades ? 
Also, how to be sure that we won't face the same issue again in the future (to V9 and V10) ?
Many thanks in advance for your answer.
Best regards,
Enes
Parents
  • Is v8 the one with all the collation changes?
    If I remember right we had a similar issue and it had to do with not enough temp space on our MySQL Database.
    Have you checked the database end to see if you can see anything there?

    Also, the collation changes were taking forever so we did them in batches before the upgrade, so our PRD would not be down for too long a span of time since many of our web forms and services rely on Sugar being up and running.

Reply
  • Is v8 the one with all the collation changes?
    If I remember right we had a similar issue and it had to do with not enough temp space on our MySQL Database.
    Have you checked the database end to see if you can see anything there?

    Also, the collation changes were taking forever so we did them in batches before the upgrade, so our PRD would not be down for too long a span of time since many of our web forms and services rely on Sugar being up and running.

Children
No Data