RE: Can Missing Tempfiles be Simply ADDED back after eXtract of FULL Database Backup ?
- From: "VIVEK_SHARMA" <VIVEK_SHARMA@xxxxxxxxxxx>
- To: <spikey.mcmarbles@xxxxxxxxx>, <oracle-l@xxxxxxxxxxxxx>
- Date: Wed, 25 Oct 2006 20:41:31 +0530
Hi Greg, Folks
What did you mean by the word "sparse" in your statement "when the file
isn't already present, in order to prevent it from being created sparse
under *nix"
What are the advantages of NOT having a sparse tempfile?
Thanks indeed
________________________________
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Greg Norris
Sent: Wednesday, October 25, 2006 6:06 PM
To: oracle-l@xxxxxxxxxxxxx
Subject: Re: Can Missing Tempfiles be Simply ADDED back after eXtract of
FULL Database Backup ?
On 10/25/06, VIVEK_SHARMA <VIVEK_SHARMA@xxxxxxxxxxx> wrote:
Can Missing Tempfiles be Simply ADDED with the SAME NAME after
eXtract of FULL Database Cold Backup?
...
SQL> ALTER TABLESPACE <Temp Tblspc> ADD TEMPFILE '<Temp File
Name>' REUSE;
Yes, this works just fine (last verified under 9iR2). You only need to
specify REUSE, of course, if the file already exists.
I tend to use the following song-and-dance when the file isn't already
present, in order to prevent it from being created sparse under *nix.
Not strictly required, by any means, but it makes space management (at
the filesystem level) somewhat simpler.
create tablespace temp2
datafile '/blah/blah/mytempfile.dbf' size ???m
extent management local uniform size ??m;
drop tablespace temp2;
alter tablespace temp
add tempfile '/blah/blah/mytempfile.dbf' size ???m reuse;
--
"I'm too sexy for my code." - Awk Sed Fred.
**************** CAUTION - Disclaimer *****************
This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely
for the use of the addressee(s). If you are not the intended recipient, please
notify the sender by e-mail and delete the original message. Further, you are
not to copy, disclose, or distribute this e-mail or its contents to any other
person and any such actions are unlawful. This e-mail may contain viruses.
Infosys has taken every reasonable precaution to minimize this risk, but is not
liable for any damage you may sustain as a result of any virus in this e-mail.
You should carry out your own virus checks before opening the e-mail or
attachment. Infosys reserves the right to monitor and review the content of all
messages sent to or from this e-mail address. Messages sent to or from this
e-mail address may be stored on the Infosys e-mail system.
***INFOSYS******** End of Disclaimer ********INFOSYS***
Other related posts:
