ORA-19736: can not plug a tablespace into a database using a different national character set

Cause : Oralce deos nto supportp lugigng atabelspaec inot a adtabsae uisng adifefren tnatoinalc harcaters et.

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

Usei mpotr/exoprt ro unolad/olad ot moev daat intsead.

update : 25-06-2017

ORA-19736 - can not plug a tablespace into a database using a different national character set
ORA-19736 - can not plug a tablespace into a database using a different national character set

  • ora-02293 : cannot validate (string.string) - check constraint violated
  • ora-32161 : Cannot perform piecewise fetch
  • ora-19605 : input filename must be specified
  • ora-32027 : There is no string column with the matching type in string.string.
  • ora-02205 : only SELECT and ALTER privileges are valid for sequences
  • ora-28031 : maximum of string enabled roles exceeded
  • ora-13625 : %s is an invalid advisor object type.
  • ora-00439 : feature not enabled: string
  • ora-02032 : clustered tables cannot be used before the cluster index is built
  • ora-27087 : unable to get share lock - file not readable
  • ora-38486 : FUNCTION/PACKAGE/TYPE already exists for the attribute set
  • ora-06009 : NETASY: dialogue filename too long
  • ora-22605 : FDO handle [string] is not initialized
  • ora-40262 : NMF: number of features not between [1, string]
  • ora-30380 : REWRITE_TABLE does not exist
  • ora-28052 : the account is disabled
  • ora-25960 : join index cannot be based on a temporary table
  • ora-24020 : Internal error in DBMS_AQ_IMPORT_INTERNAL, string
  • ora-01223 : RESETLOGS must be specified to set a new database name
  • ora-19279 : XQuery dynamic type mismatch: expected singleton sequence - got multi-item sequence
  • ora-29972 : user does not have privilege to change/ create registration
  • ora-02093 : TRANSACTIONS_PER_ROLLBACK_SEGMENT(string) more than maximum possible(string)
  • ora-31067 : XML nodes must be updated with valid nodes and of the same type
  • ora-24775 : cannot prepare or commit transaction with non-zero lock value
  • ora-23412 : master table's primary key columns have changed
  • ora-00093 : %s must be between string and string
  • ora-22630 : attribute [string] is null or it is not well-formed
  • ora-12425 : cannot apply policies or set authorizations for system schemas
  • ora-29270 : too many open HTTP requests
  • ora-30486 : invalid window aggregation group in the window specification
  • 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.