This guide details the necessary settings for enabling, storing, and retrieving Arabic and Urdu data. 1. Database Level Configuration (Oracle 10g)
NLS_LANG is the "traffic cop" that tells Oracle clients how to convert character data between the client operating system and the database server. It is used by tools like SQL*Plus, exp, and imp. Incorrect configuration is the leading cause of garbage or question-mark data. You should set it on both the database server and each client machine.
Set the environment variable UI_ICON if custom icons are used, but more importantly, ensure the REPORTS_PATH includes the folders where your Urdu/Arabic fonts are located.
Yes. The same principles apply to newer Oracle Database versions (11g, 12c) when accessed from Developer 6i. In fact, many users are exactly in this scenario: a newer database (11g/12c) running with Arabic/Urdu support, accessed by a legacy Developer 6i frontend. The key is consistent NLS_LANG configuration across all layers.
