As you have said is fine but i have some questions.
If you move the TS if it contains only the table then Ok if it contains other objects wont it be a problem?
I think it all depends on the volume of Data to be moved from the TS. ?
Am i correct please.
From Oracle DOCS
Moving data by transporting tablespaces can be orders of magnitude faster than either export/import or unload/load of the same data, because transporting a tablespace involves only copying datafiles and integrating the tablespace metadata. When you transport tablespaces you can also move index data, so that you do not have to rebuild the indexes after importing or loading the table data.
In the current release, you can transport tablespaces only between Oracle databases that use the same data block size and character set, and that run on compatible platforms from the same hardware vendor.
To move or copy a set of tablespaces, you must make the tablespaces read-only, copy the datafiles of these tablespaces, and use export/import to move the database information (metadata) stored in data dictionary. Both the datafiles and the metadata export file must be copied to the target database. The transport of these filescan be done using any facility for copying flat files, such as the operating system copying facility, ftp, or publishing on CDs.
After copying the datafiles and importing the metadata, you can optionally put the tablespaces in read-write mode.
Attitude:Attack every problem with enthusiasam ...as if your survival depends upon it
Pipo hasn't suggest moving tablespaces (as with transportable tablespaces), he suggested to use ALTER TABLE ... MOVE command to rebuild the table in some other tablespace. Using this method you don't have to wory about all the grants, indexes, constraints, triggers etc etc...
Jurij Modic ASCII a stupid question, get a stupid ANSI
24 hours in a day .... 24 beer in a case .... coincidence?