Try to find out from the Alert log and trace file what the problem is.You are lucky I hope this is just the Temporary datafile and does not hold any data.I had tried two options
First thing take a backup of the corrupted datafile
I tried to restore from my latest backup which had not worked
Perform the following steps
a) Start the database in mount mode
svrmgr> startup mount
b) Perform an offline drop of the data file that is the temp
Iam assuming there is no data in that data file if there is
any data in the data file do not perform the below steps
execute the following command
What are the reasons my dB TEMP files would become corrupt?
Hi...why would a TEMP file become corrupt like this? There were no hardware issues relating to the server the database is located on. Is this a WINDOWS NT related issue? I would really like to research what the possible causes are.
I feel the max size of a datafile is <= 4 GB on windows NT so if you had autoextend on the Temp datafile it is got extended beyond the limit of 4 GB maybe this might be one of the reson as to why it got corrupted I personally dont allow a Temp datafile to extend beyond 4 GB on windows NT.
But Oracle said they fixed this Bug in the later releases of Oracle 8.0.5
Offcourse If you have acces to metalink.oracle.com if you search thru for Ora-01200 you will be able to find more reasons as to what went wrong
i have this from the metalink and it is from Oracle Support:
"You can offline drop the datafile specified in the error message, open the database, take the tablespace offline, drop the tablespace and recreate it.
startup mount your database
alter database datafile 'filespec' offline drop;
alter database open;
alter tablespace TEMPTABLESPACE offline;
drop tablespace TEMPTABLESPACE;
delete datafiles associated with the TEMPTABLESPACE from the OS
create tablespace TEMPTABLESPACE datafile 'filespec' size xxm;
this is what oracle is saying, you can follow there advice