Oracle Database 10g Developer 6i Settings For Arabic Urdu Support Work Fixed -

NLS_LANG = ARABIC_EGYPT.AR8MSWIN1256

: Change the NLS_LANG value to AMERICAN_AMERICA.AR8MSWIN1256 .

AR8MSWIN1256 : Best for standard Arabic/Urdu support on Windows. NLS_LANG = ARABIC_EGYPT

Run the following query in SQL*Plus or SQL Developer to check your current database character set:

: The application or database character set does not support Arabic script. Verify database character set using SELECT * FROM nls_database_parameters . If NLS_CHARACTERSET is US7ASCII , WE8MSWIN1252 , or another non-Arabic character set, you must either migrate the database to AR8MSWIN1256 or use NVARCHAR2 columns with Unicode support. Verify database character set using SELECT * FROM

The Windows font does not support Arabic script.

Use CHAR length semantics ( VARCHAR2(50 CHAR) ) to avoid byte-truncation. Use CHAR length semantics ( VARCHAR2(50 CHAR) )

The NLS_LANG environment variable tells the Oracle Client (Developer 6i) how to interpret data coming from the database. Because Developer 6i is a non-Unicode (ANSI) legacy application, setting the client NLS_LANG to AL32UTF8 will cause the application to crash or display garbage characters.