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 : 28-07-2017
ORA-12713

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

  • ora-24170 : %s.string is created by AQ, cannot be dropped directly
  • ora-37145 : (XSTTS_PLAT) Cannot transport analytic workspace across platforms.
  • ora-38461 : XML Tag "string" already exists for the XMLType attribute "string"
  • ora-14003 : GLOBAL clause contradicts previosly specified LOCAL clause
  • ora-19688 : control file autobackup format(string) for string does not have %F
  • ora-10663 : Object has rowid based materialized views
  • ora-23290 : This operation may not be combined with any other operation
  • ora-16101 : a valid start SCN could not be found
  • ora-19595 : archivelog string already included in backup conversation
  • ora-01633 : Real Application Clusters Option needed for this operation
  • ora-30085 : syntax error was found in overlaps predicate
  • ora-10921 : Cannot drop tablespace belonging to default temporary tablespace group
  • ora-07267 : spwat: invalid process number.
  • ora-30658 : attempt was made to create a temporary table with EXTERNAL organization
  • ora-23536 : the object "string"."string" is not cached at the middle tier as expected.
  • ora-08207 : ora_addr: cannot open address file
  • ora-13462 : invalid blocking specification
  • ora-12463 : undefined group string for policy string
  • ora-19232 : XQ0012 - imported schemas violate validity rules
  • ora-24801 : illegal parameter value in OCI lob function
  • ora-29296 : invalid encoded string
  • ora-26680 : object type not supported
  • ora-34897 : (PPMONTHS01) Blank lines are not allowed in the MONTHNAMES option.
  • ora-10690 : Set shadow process core file dump type (Unix only)
  • ora-38423 : Attribute set created from an ADT may not be extended.
  • ora-07744 : slemcl: invalid error message file handle
  • ora-31232 : DBMS_LDAP: invalid MOD_PROPERTY_SET
  • ora-08117 : Index Organized Table operation released its block pin
  • ora-00275 : media recovery has already been started
  • ora-06760 : TLI Driver: timeout reading orderly release
  • 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.