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

To enable Arabic and Urdu support across Oracle Database 10g and Developer 6i (Forms and Reports), you must align the character sets of the database, the client operating system, and the application registry. 1. Database Character Set Configuration

Your database must use a character set that supports Arabic/Urdu script.

Recommended Set: AR8MSWIN1256 (Arabic Microsoft Windows-1256) is standard for Arabic and Urdu support.

Alternative: UTF8 or AL32UTF8 provides broader Unicode support if you need multi-language compatibility beyond Arabic/Urdu.

Check Current Set: Run SELECT * FROM nls_database_parameters; to verify. To enable Arabic and Urdu support across Oracle

Changing Character Set: If the database is already created with an incompatible set (like WE8MSWIN1252), it is often safest to recreate it or use the INTERNAL_USE command (e.g., ALTER DATABASE CHARACTER SET INTERNAL_USE AR8MSWIN1256;) after a full backup. 2. Client Registry Settings (Forms & Reports 6i)

Developer 6i relies on the NLS_LANG parameter in the Windows Registry to interpret data. Writing Urdu or Arabic in Oracle Forms 6i

This text is designed to serve as a Standard Operating Procedure (SOP) or technical reference document for Database Administrators (DBAs) and Developers.

---

5. Reports Developer Configuration

Arabic and Urdu reports often face issues where characters appear disjointed (scrambled) or output as question marks. Open the Windows Registry ( regedit )

Step 2: Registry Settings (The NLS_LANG Key)

This is the most critical step. The Oracle Client (used by Developer 6i) needs to know how to interpret the bytes it receives from the database.

1. Open the Windows Registry (regedit).
2. Navigate to: HKEY_LOCAL_MACHINE -> SOFTWARE -> ORACLE -> KEY_DevSuiteHome (or your specific Oracle Home name for Developer 6i).
3. Locate the string value NLS_LANG.

The Setting: For Arabic/Urdu support with Developer 6i, set the value to:

ARABIC_UNITED ARAB EMIRATES.AR8MSWIN1256

Why this specific string?

• Language (ARABIC): Tells the client to use Arabic locale conventions (like day/month names).
• Territory (UNITED ARAB EMIRATES): Sets defaults for date formats, currency, etc. (You can use SAUDI ARABIA or others depending on your region).
• Character Set (AR8MSWIN1256): This must match the database character set. If your database is AR8MSWIN1256, the client and server speak the same language.

---

5.1 Report Property Palette

1. System Parameters: In the Object Navigator, under the Reports node, ensure the DESTYPE and DESNAME are correctly set.
2. Font Support: Ensure the printer or PDF driver used supports Arabic fonts (e.g., Arial, Traditional Arabic).

Create New Database with Proper Settings (if needed):

CREATE DATABASE ...
CHARACTER SET AR8MSWIN1256
NATIONAL CHARACTER SET AL16UTF16;

2.3 Reports 6i – Arabic/Urdu Support

• Set Character Mode = Yes (for correct shaping in older printers/PDF)
• In Report properties: Orientation = Right-To-Left
• For each field: Horizontal Justification = Right, Anchoring = End

3. Developer 6i Client Configuration

Part 6: Migration Path from AR8MSWIN1256 to AL32UTF8 (For Urdu)

If your existing database uses AR8MSWIN1256 (no Urdu support):

1. Run CSSCAN (Character Set Scanner) from Oracle 10g utilities:

   csscan system/manager FULL=Y FROMCHAR=AR8MSWIN1256 TOCHAR=AL32UTF8 ARRAY=1000000 PROCESS=4
   

2. Analyze scan.out. For Urdu columns, CSSCAN will mark them as "exceptional" (lossy).

   • Option A: Manually export those columns as CLOB via Data Pump.
   • Option B: Create a new AL32UTF8 database and use INSERT INTO ... SELECT UTL_RAW.CAST_TO_VARCHAR2(...) with conversion.

3. Do NOT use ALTER DATABASE CHARACTER SET for moving to UTF8 from a non-UTF8 superset – it will permanently corrupt Urdu data. coerce Developer 6i via registry keys

---

Conclusion: Legacy Doesn't Mean Broken

While Oracle Database 10g and Developer 6i are long past their support dates, they remain stable workhorses for organizations reluctant to modernize. Enabling proper Arabic and Urdu support requires discipline: use AL32UTF8 on the database, coerce Developer 6i via registry keys, and handle RTL logic in your triggers.

By following this guide, you can ensure that your forms display بسم اللہ and السلام علیکم correctly – and that Urdu letters like ڑ and ے appear as intended, not as empty squares.

---