Retrying Orchestration Engine Upgrades and Clearing Warnings fail_out.xml if it is deleted or missing . For more examples on these options, refer to the renew command "-redeploy
SBM 10.x database upgrade to SBM 11.x gives error "Failed to upgrade Orchestration Engine database. Connection to the Application Engine server has timed out."
You might first go into this directory and move the log files that start with "upgrade..." to another folder just so you have clean ones for the next upgrade. C:\Program Files\Serena\ SBM \Common\Tomcat 7.0\server\default\logs Make sure Configurator is not running
Starting in SBM 11.2, administrators can use the Application Usage report in Work Center to track orchestration usage. Data for this report is stored in the SUA_ORCHACCESS table that is added as part of the upgrade to 11.2 (or higher). A new set of renew utility commands is available to help you move Event Manager data for asynchronous orchestrations that was collected prior to the upgrade into this new table and purge data from this new table as necessary.
