Progress
DataServer
for ORACLE Guide
Configuring an International Environment
If you plan to access an ORACLE database that uses a double-byte character set or that relies on non-Western European languages, you must configure your DataServer so that it runs with the appropriate locale settings.
NOTE: By default, the DataServer for ORACLE is double-byte enabled (DBE). Use or build the standard executables.You can use the DataServer to access double-byte data in the following configurations:
- On NT, a graphical client accessing a local or remote DataServer and a local or remote ORACLE instance through Progress networking or SQL*Net or Net 8.
- On NT, a batch client accessing a local DataServer and a local ORACLE instance or accessing an ORACLE instance on another host through SQL*Net or Net 8.
- On UNIX, a character-mode client using VT100 or a VT100 terminal emulator accessing a local or remote DataServer and a local or remote ORACLE instance through Progress networking or SQL*Net or Net 8.
- On UNIX, a batch client accessing a local DataServer and a local ORACLE instance or accessing an ORACLE instance on another machine through Progress networking or SQL*Net or Net 8.
Follow these steps to configure your international environment. The examples describe a double-byte environment, but the instructions apply to other locales as well:
- Make sure that your installation of ORACLE includes the multilingual option with ALL LANGUAGES.
- On UNIX, make sure that the ORACLE environment variable, NLS_LANG, is set correctly. You must set the values for language, territory, and character set correctly (
NLS_LANG=
language_territory.charset). For example, to access a Japanese database, set NLS_LANG to JAPANESE_JAPAN.JA16EUC. See your ORACLE documentation for instructions. An incorrect NLS_LANG setting can result in corrupted data.On NT, make sure that your
oracle.ini
file includes the correct NLS_LANG setting.- 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 Progress databases you create are appropriate for the locale. For example, the following setting ensures that empty databases will support Japanese using the EUCJIS code page.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.- Create a schema holder. See the "Creating a Schema Holder" section for instructions. Make sure that the code page of the empty database matches the code page that the Progress client uses. Setting DLCDB addresses this if you are working in a single-language environment.
- 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 double-byte enabled applications or for applications running in many non-Western European locales.) Specify the Progress name for the equivalent ORACLE code page in the Code Page field. Table 3–5 lists the supported double-byte languages and the Progress names for their code pages.
Table 3–5: Supported DBE Code Pages Language Progress Code Page Japanese Shift-JIS (NT)
EUCJIS (UNIX) Korean CP949
CP1361
KSC5601 Simplified Chinese CP950
GB2312 Traditional Chinese BIG-5
CP950NOTE: You must specify the Internal Code Page (-cpinternal) and Stream Code Page (-cpstream) parameters when you start the Progress client. The values that you specify for these parameters much match the code page that the ORACLE database uses. For example, if your ORACLE database uses EUCJIS, specify EUCJIS for -cpinternal and -cpstream.- Run your Progress application.
On NT, run this command to run a procedure against a local instance of ORACLE:
On NT, run this command to connect to and run a procedure in batch mode against a remote instance of ORACLE through SQL*Net or Net 8:
On UNIX, run this command to connect to and run a procedure against a local instance of ORACLE:
On UNIX, run this command to connect to and run a procedure against a remote instance of ORACLE through SQL*Net or Net 8:
On UNIX, run this command to connect to and run a procedure in batch mode against a remote instance of ORACLE through Progress networking after starting the broker on the host machine:
Copyright © 2004 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095 |