My TEMP tablespace is a locally managed temporary tablespace using a tempfile (not datafile). See results below;
SQL> alter tablespace TEMP begin backup; alter tablespace TEMP begin backup * ERROR at line 1: ORA-03217: invalid option for alter of TEMPORARY TABLESPACE which makes perfect sense, because you wouldn't want to restore that sucker anyway. Here's the skinny from Oracle: cause: Alter database and alter tablespace will not work on locally managed tempfiles as they have no reference in the data dictionary. There is no need to back up the tempfiles as they are used and destroyed every time you start up and shut down the database. fix: There is no need to backup the temporary locally manged tablespaces because: 1. Locally managed tempfiles are always set to NOLOGGING mode. So thus will have no undo. 2. Extents are managed by bitmap in each datafile to keep track of free or used status of blocks in that datafile. 3. The data dictionary does not manage the tablespace. 4. Rollback information is not generated because there is no update on the data dictionary. 5. Media recovery does not recognize tempfiles. > -----Original Message----- > From: Robert Pegram [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, April 17, 2002 11:34 AM > To: Multiple recipients of list ORACLE-L > Subject: RE: Locally managed tablespaces/What a DBA can do ? > > > What about your locally managed "temporary" > tablespace? > > > --- "Koivu, Lisa" <[EMAIL PROTECTED]> wrote: > > What? I was just able to do it. 8.1.7, W2K > > > > (INV-SYSTEM)>@ts > > > > TS_NAME LMT MB_FREE MB_TOTAL > > PCT_USED > > --------------- ---------- --------- --------- > > --------- > > LOAD_DATA_A LOCAL 740 2000 > > 63 > > LRG_INDEX_A LOCAL 390 2500 > > 84.4 > > LRG_INDEX_B LOCAL 980 1000 > > 2 > > LRG_TABLE_A LOCAL 2440 4000 > > 39 > > LRG_TABLE_B LOCAL 360 1000 > > 64 > > MED_INDEX_A LOCAL 480 1000 > > 52 > > MED_TABLE_A LOCAL 680 1000 > > 32 > > RBS DICTIONARY 299 1000 > > 70.1 > > SMALL_INDEX_A LOCAL 183 200 > > 8.5 > > SMALL_TABLE_A LOCAL 169 200 > > 15.5 > > SYSTEM DICTIONARY 110 200 > > 45 > > TEMP DICTIONARY 961 1000 > > 3.9 > > TEMP_DATA_A LOCAL 900 1000 > > 10 > > TOOLS LOCAL 19 20 > > 5 > > USERS LOCAL 34 75 > > 54.7 > > > > 15 rows selected. > > > > (INV-SYSTEM)>alter tablespace load_data_a begin > > backup; > > > > Tablespace altered. > > > > (INV-SYSTEM)>alter tablespace load_data_a end > > backup; > > > > Tablespace altered. > > > > > > > > > -----Original Message----- > > > From: Robert Pegram [SMTP:[EMAIL PROTECTED]] > > > Sent: Wednesday, April 17, 2002 9:58 AM > > > To: Multiple recipients of list ORACLE-L > > > Subject: RE: Locally managed tablespaces/What a > > DBA can do ? > > > > > > Darren, > > > > > > If using a hot backup strategy (other than Rman), > > > make sure to test your backup/recovery if you > > switch > > > the temporary tablespace to locally managed. You > > > can't put a locally managed temporary tablespace > > in > > > backup mode. > > > > > > Rob Pegram > > > Oracle Certified DBA > > > > > > ---------------- > > > > > > SQL> create tablespace temp_dict > > > 2 datafile 'c:oracleoradataorcl emp_dict.dbf' > > size > > > 10M > > > 3 default storage (initial 1M next 1M > > maxextents > > > unlimited pctincrease 0) > > > 4* temporary > > > SQL> / > > > > > > Tablespace created. > > > > > > SQL> create temporary tablespace temp_local > > > 2 tempfile 'c:oracleoradataorcl emp_local.dbf' > > size > > > 10M > > > 3 extent management local > > > 4 uniform size 1M; > > > > > > Tablespace created. > > > > > > > > > SQL> alter tablespace temp_dict begin backup; > > > > > > Tablespace altered. > > > > > > SQL> alter tablespace temp_local begin backup; > > > alter tablespace temp_local begin backup > > > * > > > ERROR at line 1: > > > ORA-03217: invalid option for alter of TEMPORARY > > > TABLESPACE > > > > > > > > > --- "Browett, Darren" > > <[EMAIL PROTECTED]> > > > wrote: > > > > Okay, maybe re-org would be a little too much, > > as > > > > you say, I would need > > > > to know the application better, and with 8 > > > > distinctly different apps, > > > > including > > > > oracle financials, I maybe heading for trouble. > > > > > > > > But what about simply turning the existing > > > > dictionary-managed tablespaces > > > > into > > > > locally managed tablespaces, other then > > maintenance, > > > > would I gain > > > > performance ? > > > > > > > > From what I read on this list, the growth of my > > > > tables is very small > > > > compared > > > > to some of the other org's, so maybe staying > > with > > > > dictionary-managed would > > > > be > > > > best, except for the temporary tablespace. > > > > > > > > Darren. > > > > > > > > > > > > > > > > -----Original Message----- > > > > Sent: April 15, 2002 3:58 PM > > > > To: Multiple recipients of list ORACLE-L > > > > > > > > > > > > Darren - Do you have to reorganize the vendor's > > > > files now? The objective of > > > > LMT's is to make Oracle more self-managing (you > > > > know, so the MS SQL people > > > > can't say it takes a lot more DBA time to manage > > the > > > > database). To me in > > > > your situation, the bottom line is whether you > > have > > > > to spend quite a bit of > > > > time reorganizing those files today. If the > > answer > > > > is "no", then LMT's > > > > probably aren't going to help you much. If the > > > > answer is "yes", then that > > > > gives you some opportunity try something with > > their > > > > files, since you are > > > > doing that anyway. The key point is whether you > > know > > > > how the vendor's > > > > software interfaces with Oracle. If you have to > > > > reorg quite a bit, then I am > > > > confident you know that interface well > > (otherwise > > > > you are jeopardizing the > > > > data). If the vendor has made it pretty > > automated > > > > (management of the data), > > > > then you probably aren't that familiar with the > > > > details of how the vendor > > > > accomplishes that, and shouldn't mess with their > > > > stuff. I apologize for > > > > being wordy here, but maybe you can see my > > point. > > > > Dennis Williams > > > > DBA > > > > Lifetouch, Inc. > > > > [EMAIL PROTECTED] > > > > > > > > > > > > -----Original Message----- > > > > Sent: Monday, April 15, 2002 4:33 PM > > > > To: Multiple recipients of list ORACLE-L > > > > > > > > > > > > I am looking into locally managed tablespaces, > > have > > > > done some research, and > > > > have a basic > > > > understanding of how they work, but I am unsure > > > > about the benefits if any > > > > for my environment. > > > > > > > > I have multiple instances running, one for each > > > === message truncated === -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: Glenn Travis INET: [EMAIL PROTECTED] Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051 San Diego, California -- Public Internet access / Mailing Lists -------------------------------------------------------------------- To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).
