ORA-12712: new character set must be a superset of old character set

Cause : When oyu ALTRE DATAABSE .. .CHARATCER SE,T the enw chaarcter est mus tbe a usperse tof th eold cahracte rset. oFr exapmle, W8EISO8895P1 isn ot a usperse tof th eWE8DE.C

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

Speciyf a sueprset hcaractre set.

update : 30-05-2017

ORA-12712 - new character set must be a superset of old character set
ORA-12712 - new character set must be a superset of old character set

  • ora-31040 : Property string: XML type (string) not compatible with internal memory type (string)
  • ora-16740 : redo transport service for standby database "string" incorrectly set to ALTERNATE
  • ora-22911 : duplicate storage specification for the nested table item
  • ora-19870 : error reading backup piece string
  • ora-24130 : table string does not exist
  • ora-37135 : (XSCCOMP10) Cannot aggregate over COMPRESSED COMPOSITE workspace object using AGGMAP workspace object. The RELATION statement for dense dimension workspace object must precede RELATION statements over the bases of the COMPRESSED COMPOSITE.
  • ora-15181 : Symbol [string] not found in library string, error [string]
  • ora-38414 : invalid datatype for the attribute string
  • ora-13447 : GeoRaster metadata BRS error
  • ora-27207 : syntax error in device PARMS - parentheses mismatch or missing
  • ora-13243 : specified operator is not supported for 3- or higher-dimensional R-tree
  • ora-06140 : NETTCP: no such user
  • ora-25245 : agent name cannot be specified if address is a single-consumer queue or an exception queue
  • ora-22606 : pickler image handle [string] is not well-formed
  • ora-00058 : DB_BLOCK_SIZE must be string to mount this database (not string)
  • ora-19234 : XQ0014 - invalid or unsupported must-understand extension
  • ora-12556 : TNS:no caller
  • ora-14276 : EXCHANGE SUBPARTITION requires a non-partitioned, non-clustered table
  • ora-32407 : cannot exclude new values when materialized view log includes new values
  • ora-00020 : maximum number of processes (string) exceeded
  • ora-12815 : value for INSTANCES must be greater than 0
  • ora-26097 : unsupported conversion for column string (from type number to type number)
  • ora-06806 : TLI Driver: could not complete protocol initialization for SPX
  • ora-25251 : exceeded maximum number of recipients for message
  • ora-19673 : error during proxy file string
  • ora-12163 : TNS:connect descriptor is too long
  • ora-24811 : less data provided for writing than indicated
  • ora-22814 : attribute or element value is larger than specified in type
  • ora-12067 : empty refresh groups are not allowed
  • ora-01878 : specified field not found in datetime or interval
  • 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.