If you plan to access an Oracle database that uses a Unicode double-byte character set or that relies on non-Western European languages, you must configure your DataServer and your Oracle installation so that they run with the appropriate locale settings. For more information on DataServer for Oracle's Unicode implementation, see Support for Unicode. For more information on the capabilities OpenEdge has for internationalized applications, see Internationalize ABL Applications.

Note: By default, the OpenEdge DataServer for Oracle is double-byte enabled (DBE) and Unicode-enabled. Use or build the standard executables.

The following examples describe a Unicode or double-byte environment, but the instructions apply to other locales as well.

To configure your international environment:

  1. Make sure that your installation of Oracle has been configured properly for the language required. See your Oracle documentation for details.
  2. After setting the environment variables required for a standard DataServer configuration, set the DLCDB environment variable to the appropriate $DLC/prolang/ subdirectory. Setting DLCDB ensures that empty OpenEdge databases you create are appropriate for the locale.

    For example, running the following command on UNIX ensures that empty databases support Japanese using the EUCJIS code page:

    DLCDB=$DLC/prolang/jpn/eucjis ; export DLCDB
    Note: When you set DLCDB to a prolang/ subdirectory, you cannot create a copy of the Sports database. Before copying the Sports database, unset DLCDB.
  3. Create a schema holder. See Creating, Maintaining, and Deploying a schema holder for instructions. Make sure that the code page of the empty database matches the code page that the OpenEdge client uses. Setting DLCDB addresses this if you are working in a single-language environment.
  4. When you create the schema holder, make sure that the code page associated with the schema image matches the code page used by the Oracle database. (The default is ibm850, which is not appropriate for Unicode or double-byte enabled applications or for applications running in many non-Western European locales.) Specify the OpenEdge name for the equivalent Oracle code page in the Code Page field. For a complete list of code pages and collation names supported by OpenEdge, see the README file in the $DLC/prolang directory.
  5. Run your OpenEdge application.
    Note: You must specify the Internal Code Page (-cpinternal) and Stream Code Page (-cpstream) parameters when you start the OpenEdge client. The values that you specify for these parameters must match the code page that the Oracle database uses. For example, if your Oracle database uses EUCJIS, specify EUCJIS for -cpinternal and -cpstream.

    In Windows, run this command to run a procedure against a local instance of Oracle:

    prowin32 -cpinternal code-page -cpstream code-page
  schema-holder-name -db oracle-dbname
  -ld oracle-logical-dbname -U userid -P password
  -p procedure-name

    In Windows, run this command to connect to and run a procedure in batch mode against a remote instance of Oracle through Oracle Networking:

    _prowin32 -cpinternal code-page -cpstream code-page
  schema-holder-name -db oracle-dbname
  -ld oracle-logical-dbname -U userid@service-name
  -P password -b -p procedure-name

    On UNIX, run this command to connect to and run a procedure against a local instance of Oracle:

    _progres -cpinternal code-page -cpstream code-page
  schema-holder-name -1 -db oracle-dbname
  -ld oracle-logical-dbname -U userid -P password
  -p procedure-name

    On UNIX, run this command to connect to and run a procedure against a remote instance of Oracle through Oracle Networking:

    _progres -cpinternal code-page -cpstream code-page
  schema-holder-name -1 -db oracle-dbname
  -ld oracle-logical-dbname -U userid@service-name
  -P password -p procedure-name

    On UNIX, run this command to connect to and run a procedure in batch mode against a remote instance of Oracle through OpenEdge networking after starting the broker on the host machine:

    _progres -cpinternal code-page -cpstream code-page
  schema-holder-name -db oracle-dbname
  -ld oracle-logical-dbname -S service-name -H host 
-U userid -P password -b -p procedure-name