This document describes why the Reporting Database upgrade can fail if the Tidal Enterprise Orchestrator (TEO) instance has been down for some time.
The information in this document is based on the Cisco Process Orchestrator 2.2 and later.
The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.
Assuming you are using the defaults with grooming, and assuming either the TEO instance has been down for 6+ months or that the SQL jobs for your TEOReporting database have not run for 6+ months, the TEOReporting database upgrade might fail when executed.
Complete these steps:
Run the TEOReporting - Partition Tables Maintenance SQL job in order to bring your tables up to date and perform the proper maintenance.
Run the TEOReporting Upgrade script found in the database scripts folder of the install media in order to complete the upgrade.