ORA-29345: cannot plug a tablespace into a database using an incompatible character set

Cause : Oracel doe snot usppor tplugigng at ablepsace nito ad atabsae usnig ani ncomaptibl echarcater est.

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

Use miporte/xpor tor ulnoad/olad t omoved ata nistea.d

update : 30-04-2017
ORA-29345

ORA-29345 - cannot plug a tablespace into a database using an incompatible character set
ORA-29345 - cannot plug a tablespace into a database using an incompatible character set

  • ora-00280 : change string for thread string is in sequence #string
  • ora-38704 : Checksum error in flashback database log file header.
  • ora-38734 : Flashback log is inconsistent; belongs to another database.
  • ora-12205 : TNS:could not get failed addresses
  • ora-16651 : requirements not met for enabling Fast-Start Failover
  • ora-30557 : function based index could not be properly maintained
  • ora-22971 : invalid datatype for PRIMARY KEY-based object identifier
  • ora-31102 : Already locked in exclusive mode. Cannot add lock.
  • ora-30552 : The package/procedure/function cannot be changed
  • ora-07305 : ksmcsg: illegal database buffer size.
  • ora-39306 : schema name mismatch expected "string" got "string"
  • ora-23490 : extension request "string" with status "string" not allowed in this operation
  • ora-32015 : unable to restore SPFILE
  • ora-01663 : the contents of tablespace 'string' is constantly changing
  • ora-19678 : RMAN configuration value exceeds maximum length of string
  • ora-07481 : snlmatt: cannot attach to lock manager instance.
  • ora-39155 : error expanding dump file name "string"
  • ora-01519 : error while processing file 'string' near line string
  • ora-12988 : cannot drop column from table owned by SYS
  • ora-12632 : Role fetch failed
  • ora-36682 : (XSDPART20) Partition name string appears twice.
  • ora-38442 : The ADT "string" is not in a valid state.
  • ora-02432 : cannot enable primary key - primary key not defined for table
  • ora-33306 : (DBVALID03) The AW VALIDATE command cannot be used with read-only analytic workspace string.
  • ora-36635 : (XSDUNION03) The base dimension workspace object has an invalid datatype for use in a UNIQUE concat definition.
  • ora-04066 : non-executable object, string
  • ora-34346 : (MXDSS04) The string analytic workspace cannot be detached.
  • ora-07227 : rtneco: unable to set noecho mode.
  • ora-06604 : LU6.2 Driver: Unable to allocate session with remote LU
  • ora-10645 : Recursive Extension in SYSTEM tablespace during migration
  • 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.