Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
Home -> Community -> Mailing Lists -> Oracle-L -> Re: data and index tablespaces for rman tspitr
AK,
Not at all! The index and data should be in different tablespaces to take advantage of disk location (or location on the platter, in case of SAN and RAID). However, I guess you have confused about what a transportable set is. A set is a collection of all tablespaces where the objects have all links inside that set. In case of a set of data and index tablespaces, you would issue
exec dbms_tts.transport_set_check('TS_DATA,TS_INDEX',TRUE);
Note how both the tablespaces have been enclosed within the quotes seprated by comma. I guess you must have used just one tablespace inside the quotes.
HTH. Arup Nanda
I discovered that my ts_pitr_check table contains lots of rows with reason "Table and Index enforcing primary key constraint not in same tablespace" . I know that for the tablespace to be transportable objects should be contained in same tablespace. But it is general practive to distribute data among different tablespaces and datafiles. Most of us keep diffrent tablespace for indexes and data . What strategy you guys adapt to keep tablesapce trasnportable . Should we have all related objects in same tablespaces ? or u dont care ?
-ak
--
Please see the official ORACLE-L FAQ: http://www.orafaq.net
--
Author: Arup Nanda
INET: orarup_at_hotmail.com
Fat City Network Services -- 858-538-5051 http://www.fatcity.com San Diego, California -- Mailing list and web hosting services ---------------------------------------------------------------------To REMOVE yourself from this mailing list, send an E-Mail message to: ListGuru_at_fatcity.com (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). Received on Thu Apr 24 2003 - 14:16:42 CDT