Which of the following are included in a transportable tablespace set?

Which of the following are included in a transportable tablespace set? (Choose all that
apply.)

Which of the following are included in a transportable tablespace set? (Choose all that
apply.)

A.
The datafiles that make up a self-contained group of tablespaces required for copy

B.
The system tablespace

C.
An export of the tablespace metadata

D.
The spfile

E.
All of the above



Leave a Reply 1

Your email address will not be published. Required fields are marked *


Jake from SF

Jake from SF

A and C are correct:

https://docs.oracle.com/cd/B28359_01/server.111/b28310/tspaces013.htm

For A:here may be logical or physical dependencies between objects in the transportable set and those outside of the set. You can only transport a set of tablespaces that is self-contained. In this context “self-contained” means that there are no references from inside the set of tablespaces pointing outside of the tablespaces. Some examples of self contained tablespace violations are:

An index inside the set of tablespaces is for a table outside of the set of tablespaces.

Note:
It is not a violation if a corresponding index for a table is outside of the set of tablespaces.
A partitioned table is partially contained in the set of tablespaces.

The tablespace set you want to copy must contain either all partitions of a partitioned table, or none of the partitions of a partitioned table. If you want to transport a subset of a partition table, you must exchange the partitions into tables.

A referential integrity constraint points to a table across a set boundary.

When transporting a set of tablespaces, you can choose to include referential integrity constraints. However, doing so can affect whether or not a set of tablespaces is self-contained. If you decide not to transport constraints, then the constraints are not considered as pointers.

A table inside the set of tablespaces contains a LOB column that points to LOBs outside the set of tablespaces.

An XML DB schema (*.xsd) that was registered by user A imports a global schema that was registered by user B, and the following is true: the default tablespace for user A is tablespace A, the default tablespace for user B is tablespace B, and only tablespace A is included in the set of tablespaces.

For B: You cannot transport the SYSTEM tablespace. Therefore, objects such as sequences, PL/SQL packages, and other objects that depend on the SYSTEM tablespace are not transported. You must either create these objects manually on the destination database, or use Data Pump to transport the objects that are not moved by transportable tablespace.

For C: Beginning with Oracle Database 10g Release 2, you can transport tablespaces that contain XMLTypes. Beginning with Oracle Database 11g Release 1, you must use only Data Pump to export and import the tablespace metadata for tablespaces that contain XMLTypes.

For D: Unmentioned