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: AK
INET: oramagic_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 Wed Apr 23 2003 - 14:47:03 CDT
