This is the current situation : there is a TEMP tablespace, which is the default temporary tablespace of 1 user, and which has got 1 datafile.
Aparently, there's not much usage of this Temporary tablespace, which is probably explainable in some way (relating to functional usage).
But, because the usage is that low, the file itself becomes old. Very old. In fact, the last change is 2 years ago.
I'm aware of the fact that a Temporary tablespace is not always in use ... but this is a bit too much on the other side.
What I'm asking here, is to find out if there is a way of validating the correctness of that file. You see, when I drop it now, it may take another 2 years before somebody notices it, since the database doesn't need that file on startup.
Apart from causing some transaction to run as the user that is linked to that tablespace, what options can a DBA take to validate this file and/or this tablespace ?
Using DBV (dbverify) doesn't really help here, since it doesn't check on temp files. Dropping the file (a temp file, obviously) also doesn't help since startup doesn't need the file, as stated above.