Community Tip - You can change your system assigned username to something more personal in your community settings. X
Solved! Go to Solution.
Thanks for the advise. We manage to trace the root cause to an almost full DB table, which we fixed by adding a new data file.
I would focus on permission issues which you should be able to see in the method server log or something with your vaults. Make sure they are operating and populating fine. You run a verification job on the vaults to verify content.
Thanks for the advise. We manage to trace the root cause to an almost full DB table, which we fixed by adding a new data file.
We just had the same issue this morning. No changes to Windchill in the last few months. Permission issues not relevant as this happens for admins as well. Vaults appear to be operating fine. Can I get more information on this DB table fix?
Have you DBA look at the Tablespaces to see if they are full. Look for storage issues where the DB files are stored (out of space?). You might see DB error messages in your log files if its having problems extended. You said the are operating fine. Are new files still being written to vaults?
I think we did something like the above. However, unable to verify as we've switch from Oracle to SQL.
Look at the possibility that the Windchill/tmp/ directory is in a full partition. It can contain large aaa.expimp files, and they don't seem to get cleaned up after they are no longer in use.
We started by using a symbolic link so this tmp directory could be in another partition separate from the partition Windchill was in (not the Linux /tmp directory, we created a tmp directory under /home). That was an improvement because Windchill itself did not lock up due to a full partition. However the large downloads still could lock up due to the partition being full.
Now we use a cron script which checks daily, and deletes old .expimp files.