If you reverted the db but not the vault, the problem is that your oracle sequence that drives the vault names was set back to values that have already been used. There are two things you can doto fix the problem:
1) move the extra files from the vault manually by selecting anything created later than the latest date of vaulted objects you find in the database (meta)data.
2) or set the sequence to a higher current value using "alter sequence <name> increment by <integer>". The sequence used is uniquesequence_seq.
In Reply to Marty Ross:
Hi,
I reverted a Windchill instance's data (database + LDAP) but not the vaulted content.
Users reported issues when saving "configuration spec" for ACPs - seeing "wt.fv.FvFileCanNotBeStored" exceptions in the log.
I then did a "remove unreferenced files" using "Vault Configuration" utility, which removed a lot of files, and things SEEM to be working better now, but I'm wary of the integrity of the objects they already created which DIDN'T error out, and/or what other problems they'll have in the future.
Should I just say sorry to my users, kick 'em out and revert again to the checkpoint - this time remembering to revert the Vault as well, or is there a (good) chance that the "cleanup" operation I did with the "External Storage Administrator" did just as good a job, and things are now with integrity once more going forward?
Tim Atwood
PTC Enterprise Deployment Center
