No, it is not necessary to take a cold backup of temporary tablespaces. Data in a temporary tablespace is temporary,...
By submitting your email address, you agree to receive emails regarding relevant topic offers from TechTarget and its partners. You can withdraw your consent at any time. Contact TechTarget at 275 Grove Street, Newton, MA.
just like the name says. Data only lives in the temporary tablespace for the duration of the transaction. If you shut down the database, all transactions are ended (normally or abnormally). In either case, there are no transactions that require the contents of the temporary tablespace. When you start the database, SMON will clean up any data in the temporary tablespace as it is no longer needed.
If you restore from a cold backup and do not restore a TEMPORARY TABLESPACE (one that was created with the "CREATE TEMPORARY TABLESPACE ... TEMPFILE ...;" command) and the temporary tablespace is missing, then Oracle will re-create this for you automatically. If you created your Temp tablespace with the "CREATE TABLESPACE .... DATAFILE ... TEMP;" command, then Oracle will not recreate the tablespace for you on startup. In this case (which should no longer be used), you definitely should back up your temporary tablespace.
Related Q&A from Brian Peasland
Oracle expert Brian Peasland answers one reader's question about common pitfalls when connecting Oracle to outside programs.continue reading
One reader asks expert Brian Peasland a question about datafile sizes with the Oracle RMAN duplicate 10g command.continue reading
Managing parent table-child table relations in Oracle SQL environments is key to efficient programming.continue reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.