Customer has an all in one system on Windows server 2016 with SQL Server 2014 R2 and many successful upgrades from V13 to V19.

Upgrade to V20 fails at the schema rebuild page and the tema log file errors with:

iner.webapp                I SRVE0292I: Servlet Message - [tema]:.[INFO] Begin applying migration 1591775375_rambo_remove_inventory_panel.rb, direction: up

[30/07/20 3:35:52:529 UTC] 00000047 com.ibm.ws.webcontainer.webapp                I SRVE0292I: Servlet Message - [tema]:.[ERROR] Java::ComMicrosoftSqlserverJdbc::SQLServerException: Cannot drop the trigger 'sam.computer_group_catalog_hierarchy_rollups_trigger_uuid_guid', because it does not exist or you do not have permission.: drop trigger sam.computer_group_catalog_hierarchy_rollups_trigger_uuid_guid

[30/07/20 3:35:52:608 UTC] 00000047 com.ibm.ws.webcontainer.webapp                I SRVE0292I: Servlet Message - [tema]:.[ERROR] Java::ComMicrosoftSqlserverJdbc::SQLServerException: The DELETE statement conflicted with the REFERENCE constraint "FK__reports__pagesta__2F9A1060". The conflict occurred in database "temadb", table "dbo.reports", column 'pagestate_id'.: delete from dbo.pagestates where id in (select pagestate_id from dbo.reports where path like '%software_aggregates%')

and then:

I SRVE0292I: Servlet Message - [tema]:.[FATAL] 

Sequel::ForeignKeyConstraintViolation (DBNAME: temadb - Java::ComMicrosoftSqlserverJdbc::SQLServerException: The DELETE statement conflicted with the REFERENCE constraint "FK__reports__pagesta__2F9A1060". The conflict occurred in database "temadb", table "dbo.reports", column 'pagestate_id'.):

 com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(com/microsoft/sqlserver/jdbc/SQLServerException.java:258)

Uninstall of ILMT and reinstall results in the same error.

The database is private to ILMT and has not been updated nor serviced since the last upgrade.

it looks identical to the issue reported here:

https://www.ibm.com/support/pages/node/6244612?myns=swgother&mynp=OCSS8JFY&mync=E&cm_sp=swgother-_-OCSS8JFY-_-E

Yes this does look identical so consider it fixed if I don't write back and thankyou.

Unfortunately in the process of trying to recreate this error on a second system (all in 1) this time on Windows Server 2012 R2 the upgrade fell over trying to copy the backup ILMT and when doing it manually it looks like the 9.2.20 is using file names that are too long. Will ask this question separately.