Migrating Oracle Objects

Go Up to Migration and Object Restrictions/requirements

The table describes the condition(s) that need to be satisfied on the target database to migrate objects:

Object	Condition(s) on Target Database
Clusters	The user who owns the cluster(s) must already exist in the target database. The tablespace on which the cluster(s) are placed must already exist in the target database.
Directories	To migrate directories successfully, the object must exist in the target database.
Functions	The user who owns the function(s) must already exist in the target database. Any objects referenced by the function(s) must already exist in the target database.
Indexes	The tables on which the indexes are being built must already exist in the target database. The user who owns the indexes must already exist in the target database. The tablespace on which the indexes are being placed must already exist in the target database.
Libraries	The object type must exist on the target server.
Materialized Views	The user who owns the materialized view(s) must already exist in the target database. Any objects referenced by the materialized view(s) must already exist in the target database.
Materialized View Logs	The user who owns the materialized view log(s) must already exist in the target database. Any objects referenced by the materialized view log(s) must already exist in the target database.
Packages	The user who owns the package(s) must already exist in the target database. Any objects referenced by the package(s) must already exist in the target database.
Procedures	The user who owns the procedure(s) must already exist in the target database. Any objects referenced by the procedure(s) must already exist in the target database.
Rollback Segments	The user who owns the rollback segment(s) must already exist in the target database. The tablespaces where the rollback segment(s) are to be placed must already exist in the target database.
Sequences	The user who owns the sequence(s) must already exist in the target database. Any objects referenced by the sequence(s) must already exist in the target database.
Synonyms	The user who owns the synonym(s) must already exist in the target database. The base objects referenced by the synonym(s) already exist in the target database.
Tables	Any referenced user datatypes must already exist in the target database. If you are copying tablespace placement also, then the tablespaces must already exist in the target database. If the tables have foreign key references to tables not included in the migration, these tables must already exist in the target database. NOTE: Index-Organized tables are coded to automatically migrate as though Copy Table Constraints in Alter Form is not selected, and Include Table Constraints is selected.
Triggers	The user who owns the trigger(s) must already exist in the target database. The base triggers must already exist in the target database. Any objects referenced by the trigger(s) must already exist in the target database.
Types	The user who owns the object type(s) must already exist in the target database. The base object types must already exist in the target database. Any objects referenced by the object type(s) must already exist in the target database.
Users	The default and temporary tablespaces assigned to the user(s) must already exist in the target database. The profiles assigned to the user(s) must already exist in the target database. Any tablespaces on which quotas are defined must already exist in the target database. Any roles granted to the user(s) must already exist in the target database.
Views	Any objects referenced by the view, including tables and other views, must already exist in the target database. The owner of the view must already exist in the target database.