NPM 2023.4.x Upgrade feedback

Has anyone upgraded to 2023.4.1 or 2023.4.2?  Only seeing two posts in the catalog.  If you have upgraded has it been smooth?  Trying to skip over the job engine issues that plagued releases until 2023.3.x.

Parents
  • I just made our third attempt to get off of 2020.2.6, this time to 2023.4.2.  Again, received a failure during the Configuration Wizard stage that was yet again different from previous attempts to previous versions:

    "Database configuration failed:  Error while executing script- Column already has a DEFAULT bound to it.  Could not create constraint or index.  See previous errors."

    I'm finally opening a case as we need to get this thing upgraded as I can't find anything on this error.  I don't know why these recent upgrades are so problematic for us, we aren't doing anything particularly custom.  Also annoying since we completely rebuilt our cluster from scratch a few years ago.  I've easily got 120 hours into trying to get past 2020.2.6 and it's become annoying.

  • In the CW logs they usually post exactly the SQL they are trying to run at each step, so if I run into something weird like that I usually just dig into the SQL and reverse engineer the change that it's attempting to make and see what hoops I need to clear to make it happen.  In the past I've had to do various fixes for customers that didn't seem like they would have been needed, but things like dropping existing tables just for the CW to recreate them, or removing indexes, other bits.  Can't say why some environments run into things like that when most don't but it seems to happen maybe one out of 20-30 upgrades that I've performed for clients.

Reply
  • In the CW logs they usually post exactly the SQL they are trying to run at each step, so if I run into something weird like that I usually just dig into the SQL and reverse engineer the change that it's attempting to make and see what hoops I need to clear to make it happen.  In the past I've had to do various fixes for customers that didn't seem like they would have been needed, but things like dropping existing tables just for the CW to recreate them, or removing indexes, other bits.  Can't say why some environments run into things like that when most don't but it seems to happen maybe one out of 20-30 upgrades that I've performed for clients.

Children