Friday, July 25, 2008

Oracle Error ORA-12704: character set mismatch

One gets much worried by ORA-12704:character set mismatch. It is hard to track what is going on. But the guideline below will give relief.

Causes of Oracle Error ORA-12704: character set mismatch

-The string operands(other than an nlsparams argument) to an operator or built-in function do not have the same character set.

- An nlsparams operand is not in the database character set.

- String data with character set other than the database character set is passed to a built-in function not expecting it.

- The second argument to CHR() or CSCONVERT() is not CHAR_CS or NCHAR_CS.

- A string expression in the VALUES clause of an INSERT statement, or the SET clause of an UPDATE statement, does not have the same character set as the column into which the value would be inserted.

- A value provided in a DEFAULT clause when creating a table does not have the same character set as declared for the column.

- An argument to a PL/SQL function does not conform to the character set requirements of the corresponding parameter.

Action to be taken

Check one of the suspected region in your coding in PL/SQL and find the error occuring part. Then you can fix it and get rid of it! Happy error detection!!

Finally I would like to welcome you to get insight on implementing object relational features in oracle illustrated with a simple ecommerce scenario.

Happy Programming!


Anonymous said...

This has to be the most useless blog post I've ever read.
You may as well just say: "You fix it by fixing it".

Anonymous said...

I agree with anonymous

Post a Comment

Hope you liked this post. You can leave your message or you can put your valuable suggestions on this post here. Thanks for the sharing and cooperation!

Popular Posts

Recent Articles