The Upgrade Manager's DB history includes what was changed and on what dates back to the initial installation of Windchill. You can use it to track down the installed component numbers for all modules..
UpgradeManager -exportdbhistory dbHistory.xml
Note: We can also edit the file and re-load it. It may be easier than hacking database entries. However, I would make a backup of your currently broken database before doing this.
The following comes from my upgrade notes. It is not your current issue but the technique may prove useful.
Uninstall Modules During Rehosting
When we request the database history, the command exports an XML file with the full update/upgrade history of the system. This content is stored in database tables that start with ‘WtUpgInst_*’.
select owner, table_name from dba_tables where table_name like '%WTUPGINST_%';
We can query the database to get a list of all installed modules. (SQL Server)
select * from INFORMATION_SCHEMA.TABLES where TABLE_NAME LIKE '%VersionedAssembly%';
select * from WtUpgInst_VersionedAssembly;
And if we know the offending module(s), we can query for them directly.
select * from WtUpgInst_VersionedAssembly where releaseId like '%infomodeler%';
PTC does not recommend changing any of this information through database queries. Uninstallation of any module is not supported, so don’t bother logging a PTC Tech Supt call for this. However, sometimes there are installed modules that we don’t have or won’t seriously impact Windchill: PSM, PTC’s development environment, infomodeler, etc. When we encounter these modules, first check the knowledge base to see if there are explicit uninstall instructions for the module. Search for ‘uninstall’ and ‘module’ and the name of the module. Several modules have explicit instructions: MPMLink, SOLR, COGNOS, etc. If you can’t find instructions, follow these steps.
1. Ensure WindchillDS is running and run the UpgradeManager command from a Windchill shell:
UpgradeManager -exportdbhistory dbHistory.xml
This will export the DB history to the location where the command was executed (usually %wt_home%).
2. Copy the file to a new name.
copy /y %wt_home%\dbHistory.xml %wt_home%\dbHistory_mod.xml
3. Edit the file and delete all rows of the undesired entries.
%wt_home%\dbHistory_mod.xml
4. Import the modified history file.
UpgradeManager -importdbhistory dbHistory_mod.xml
5. Using a database query (as the database user), confirm module no longer exists.
select * from WtUpgInst_VersionedAssembly where releaseId like '%infomodeler%';
6. Start Apache and run the update_tool to clean up any issues.
bin\update_tool.bat -username wcadmin -password wcadmin -noui
windchill version
The installed version information should no longer include the offending module.
7. Now clean cache and restart Windchill.
