Skip to Main Content

Oracle Database Discussions

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Issue inputting japanese characters in sqlplus?

Ray Van DolsonMay 8 2008 — edited May 11 2008
(Reposting this from Linux forum)

Hey all, looking for some feedback on this issue.

Background: Using a tool to process an external data file (with a Japanese filename and contents which contain Japanese as well). This tool ultimately places the converted data into an Oracle database.

When this tool is run from our Windows environment, everything works correctly.

However, when running the Linux version of the tool, talking to the same database, the following is output:

WARNING: underlying database error.
SDE Code (-51): Underlying DBMS error
Extended DBMS error code: 911
ORA-00911: invalid character
(駅)
Not able to create business table 駅
Delete layer "駅" ...
SDE Code (-51): Underlying DBMS error
Extended DBMS error code: 911
ORA-00911: invalid character
Unable to delete layer "駅"

When we re-run the tool with an English filename it seems to work fine regardless of the contents of the file.

Relevant environment variables:
LANG=ja_JP.UTF8
NLS_LANG=Japanese_Japan.UTF8
NLS_LANGUAGE=japanese

And I have also tried with:
LANG=ja_JP.eucJP
NLS_LANG=japanese_japan.JA16EUC
NLS_LANGUAGE=japanese

I have noticed that if I run sqlplus directly and attempt to create a simple table with a Japanese name, I get the ORA-00911 error with japanese_japan.JA16EUC as NLS_LANG. If I change NLS_LANG to Japanese_Japan.UTF8 I can then successfully create a table with japanese characters in its name. I still cannot run our conversion tool above.

Any ideas or tips? I believe the database is set up correctly as it does work with Windows as the client... perhaps the conversion tool is overriding my NLS_LANG settings? Any other possibilities you can think of?

TIA,
Ray
Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on Jun 5 2008
Added on May 8 2008
8 comments
2,389 views