Bulk Data Movement Guide

10.5.5
- 10.5.8
- 10.5.6
- 10.5.4
- 10.5.3
- 10.5.2
- 10.5.1
- 10.5
- 10.4.1
- 10.4.0 HotFix 1
- 10.4.0

Back Next

ORACLECODEPAGE Statement

If the NLS_LANG environment variable specifies a character set other than UTF8 or AL32UTF8, you must define the ORACLECODEPAGE statement. This statement determines the code pages that PowerExchange and PowerCenter use for a specific Oracle database during bulk data movement operations.

The code page or pages that you specify in this statement must match the character set that is identified in the NLS_LANG environment variable. The NLS_LANG environment variable determines how the Oracle client libraries deliver data to PowerExchange.

Linux, UNIX, and Windows

Oracle

CODEPAGE

If NLS_LANG specifies a character set other than UTF8 or AL32UTF8

ORACLECODEPAGE=(tnsname_host
               ,pwx_codepage
               ,pc_codepage
)

tnsname_host: Required. An entry in the Oracle tnsnames.ora configuration file for an Oracle database. The entry defines the database address that PowerExchange uses to connect to the database.
pwx_codepage: Required. A code page number or alias name that PowerExchange uses to identify a code page. To determine valid PowerExchange code page and alias values, use the ICUCHECK utility to generate report 5, “PowerExchange Code Page Names and Aliases.”

PowerExchange supports some common Oracle character set names as aliases to code pages.
pc_codepage: Optional. A name that controls the processing of the SQL statements that PowerExchange passes to Oracle on behalf of PowerCenter bulk data movement sessions. PowerExchange supplies a default that is usually suitable.

Do not specify this parameter except in special circumstances when the default does not work. For example, if you specify a user-defined ICU code page for the pwx_codepage parameter, you need to specify this parameter.

You can specify up to 20 ORACLECODEPAGE statements, each for a separate database, in a dbmover.cfg configuration file.

If PowerExchange uses the same NLS_LANG environment variable to access multiple Oracle databases, you do not need to specify a separate ORACLECODEPAGE statement for each database. Instead, specify a single ORACLECODEPAGE statement and leave the tnsname_host parameter blank. The specified code page then applies to all databases that have an entry in the tnsnames.ora file. The following example shows a statement without a tnsname_host parameter:

ORACLECODEPAGE=(,MS1252)

If you enter an incorrect PowerCenter code page value, the ODLNumResultCols routine usually reports Oracle return code 911.

If the NLS_LANG environment variable specifies Korean_Korea.KO16MSWIN949, define the following ORACLECODEPAGE statement:

ORACLECODEPAGE=(KO102DTL,MS949)

Rename Saved Search

Table of Contents

Bulk Data Movement Guide

Bulk Data Movement Guide

ORACLECODEPAGE Statement

ORACLECODEPAGE Statement