Finalize Upgrade
This phase performs final clean up and scheduling tasks. For this phase to run successfully, Web Server and method server must be running on the target installation. During this phase, the following tasks are performed:
1. Blob Rewriting
This task schedules a long running background process that attempts to ensure that all instances of Java objects stored inside BLOBs and SMALLBLOBs in your database are evolved to their current class schema versions. Since this evolution process is long running, it is scheduled to run in schedule queues during overnight hours and may not complete for several days. To communicate any issues it encounters during the evolution process, it sends emails to the administrative user. Confirm that your target installation's email server is configured properly and the Administrator has a valid email address. If this step succeeds, your system is upgraded. To view the log, navigate to: <Windchill>/logs/Upgrade-BackgroundBlobRewriter.log. To turn on the logging for the blob rewriter, add the following line to <Windchill>/codebase/WEB-INF/log4jMethodServer.properties:
log4j.logger.com.ptc.windchill.upgrade.blobrewriting=ALL
2. Rebuilding Invalid Objects
This task is performed only for Oracle database. This is the final upgrade step that collects and recompiles invalid database objects.
3. Removing Content Synchronization Queue Entries and Data
This task removes entries from the package content synchronization processing queue (WPSyncQueue). It also removes data from tables which store temporary information used for content synchronization of CAD documents when exported via packages and content synchronization is enabled. This data is removed to avoid upgrading it, as it has no life span beyond an active package export process.
After all of the Finalize Upgrade tasks are performed, an Upgrade Manager Alert appears to prompt you to restart the web server if you have moved administrative or enterprise data from the source to the target system.