ORA-12713: Character data loss in NCHAR/CHAR conversion

Cause : When character set conversion happens between CHAR and NCHAR either implicitly or explicitly, some characters are lost due to no mapping characters in the destination character set.

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

Make sure all the characters can be mapped to destination character set or set NLS_NCHAR_CONV_EXCP to be FALSE.

update : 25-09-2017

ORA-12713 - Character data loss in NCHAR/CHAR conversion
ORA-12713 - Character data loss in NCHAR/CHAR conversion

  • ora-12154 : TNS:could not resolve the connect identifier specified
  • ora-01080 : error in shutting down ORACLE
  • ora-01979 : missing or invalid password for role 'string'
  • ora-00102 : network protocol string cannot be used by dispatchers
  • ora-40271 : no statistically significant features were found
  • ora-00107 : failed to connect to ORACLE listener process
  • ora-19660 : some files in the backup set could not be verified
  • ora-19763 : compatibility version string is higher than maximum allowed: string
  • ora-12985 : tablespace 'string' is read only, cannot drop column
  • ora-38950 : Source platform string not cross platform compliant
  • ora-36163 : (XSMXAGGR06) The AGGREGATE function cannot be run on more than one variable at a time.
  • ora-12452 : label tag string already exists
  • ora-36710 : (XSMXALLOC01) TARGETLOG variable workspace object must be dimensioned identically to TARGET variable workspace object.
  • ora-15039 : diskgroup not dropped
  • ora-15175 : cannot create alias for diskgroup metadata file 'string'
  • ora-25246 : listen failed, the address string is an 8.0 style exception queue
  • ora-06258 : NETNTT: cannot allocate context area
  • ora-16222 : automatic Logical Standby retry of last action
  • ora-16506 : out of memory
  • ora-00306 : limit of string instances in this database
  • ora-39098 : Worker process received data objects while loading metadata. Invalid process order range is string..string
  • ora-08112 : a composite partition may not be coalesced as a whole
  • ora-33308 : (DBVALID04) SEVERE ERROR: Record number used but not allocated
  • ora-19204 : Non-scalar value 'string' is marked as XML attribute
  • ora-14115 : partition bound of partition number string is too long
  • ora-30570 : SEGMENT SPACE MANAGEMENT option already specified
  • ora-09828 : SCLFR: atomic latch return error.
  • ora-27419 : unable to determine valid execution date from repeat interval
  • ora-14094 : invalid ALTER TABLE EXCHANGE PARTITION option
  • ora-02165 : invalid option for CREATE DATABASE
  • 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.