ORA-29341: The transportable set is not self-contained

Cause : The set of objects in the set of tablespaces selected are not self-contained.

Action - How to fix it : DBA Scripts :: www.high-oracle.com/scripts

Consider using different export options, or removing some of the pointers that caused the violation, or selecting a different set of tablespaces.

update : 26-05-2017
ORA-29341

ORA-29341 - The transportable set is not self-contained
ORA-29341 - The transportable set is not self-contained

  • ora-01241 : an external cache has died
  • ora-38409 : invalid name or option for the attribute set: string
  • ora-01146 : cannot start online backup - file string is already in backup
  • ora-16103 : Logical Standby apply must be stopped to allow this operation
  • ora-10658 : Lob column to be shrunk is marked unused
  • ora-32578 : password for SYS already specified
  • ora-19916 : %s
  • ora-29362 : plan directive string, string does not exist
  • ora-39022 : Database version string is not supported.
  • ora-30159 : OCIFileOpen: Cannot create the file or cannot open in the requested mode
  • ora-31533 : only one change set (string) is allowed in change source
  • ora-00108 : failed to set up dispatcher to accept connection asynchronously
  • ora-39110 : error deleting worker processes
  • ora-30119 : unable to obtain a valid value for 'string'
  • ora-00402 : database changes by release string cannot be used by release string
  • ora-24265 : Insufficient privileges for SQL profile operation
  • ora-01235 : END BACKUP failed for string file(s) and succeeded for string
  • ora-38738 : Flashback log file is not current copy.
  • ora-27065 : cannot perform async vector I/O to file
  • ora-13775 : inconsistent datatype in input cursor
  • ora-32846 : Messaging Gateway agent cannot be started; status is string
  • ora-06573 : Function string modifies package state, cannot be used here
  • ora-24047 : invalid agent name string, agent name should be of the form NAME
  • ora-06930 : CMX: error when checking ORACLE_SID
  • ora-26577 : PRESERVE TABLE can not be used when dropping old style materialized view string.string
  • ora-01502 : index 'string.string' or partition of such index is in unusable state
  • ora-12648 : Encryption or data integrity algorithm list empty
  • ora-06517 : PL/SQL: Probe error - string
  • ora-38732 : Expected file size string does not match string.
  • ora-22338 : must specify CASCADE INCLUDING DATA when altering the final property
  • Oracle Database Error Messages



    Oracle Database High Availability Any organization evaluating a database solution for enterprise data must also evaluate the High Availability (HA) capabilities of the database. Data is one of the most critical business assets of an organization. If this data is not available and/or not protected, companies may stand to lose millions of dollars in business downtime as well as negative publicity. Building a highly available data infrastructure is critical to the success of all organizations in today's fast moving economy.

    Well, the reason for above error is that i have taken the above script from a 11g database and running it on 10g database. 11g has bring some changes in password management. Below code is executed on 11g and user created successfully, which is expected result.