The transportable tablespace feature enables you to definitely move or copy a subset of the Oracle database in one Oracle database to a different. Transportable tablespace helps with any situations requiring bulk data to become transferred for example throughout the following scenarios.
– We are able to use for archival of pertinent data just before purging it without significant impact towards the source database.
– Migration from the source data from your OLTP to some reporting database of change in data from operational data sources towards the data warehousing.
– Change in production data to some test platform.
– We are able to copy data in the enterprise data warehouse to temporary staging databases for massaging or converting data just before loading lower-stream data marts.
Moving data via transportable tablespace is a lot quicker than conventional upload/load utilities, for example export/import and SQL*Loader. The reason behind this really is that, transporting a tablespace only necessitates the documents to become copied across in the source towards the target database and integrating metadata relating towards the tablespace structure. Index data may also be copied or moved without one getting to become reconstructed.
Whenever a tablespace will be transported, it’s put into read only mode to make sure that a regular picture of the information is taken. Then only specific dictionary details are exported in the source data dictionary. Next, the tablespace documents are copied across towards the target database via any operating-system utilities or instructions. Then your metadata describing the tablespace is imported in to the target database. This is extremely fast because how big the import is minimized. Optionally, the transferred tablespace may then go in read write mode. The particular implementation includes while using datapump utility or export/import utilities. The exp utility includes a option, transport_tablespace, whereas imp has three options, transport_tablespace, documents, and tts_proprietors, to aid this selection.
You are able to transport tablespace between Oracle databases which use exactly the same data block size and character set. Even the source and target platform ought to be compatible and, it possible, in the same hardware vendor. Also, to avoid breach of functional and physical dependencies and referential integrity, another limitation enables only known as “self-contained” tablespace to become transported. “Self-contained” implies that tthere shouldn’t be references inside the tablespace pointing to segments outdoors the tablespace. For instance, when the tablespace set you want to repeat must contain either any no partitions of the partitioned table. The process DBMS_TTS.transport_set_check may be used to determine set up tablespace under consideration is self-contained. All violations as reported by this process is visible within transport_set_violations view which is empty when there aren’t any violations. To be able to pick which from the tablespace in the present database happen to be transported the plugged_in column in “dba_tablespaces” could be checked.