No. All previous updates have worked fine. Looking at the database, before and after, it is crashing during the renaming of the os_ticket tables to os_thread tables. There is no table or view called 'ost__ticket_thread_evt' which is mentioned in the error above.

thread_id exists in the ost_thread_event, but no ticket_id is in that table and obviously not in the missing table.