NLS_Charset – PB Docs 126

NLS_Charset database parameter

Description

Specifies
the client-side character set for the current environment handle.

Controls

  • O90 Oracle9i

  • O10 Oracle 10g

  • ORA Oracle 11g

Syntax

Parameter

Description

value

Specifies the
client-side character set for the current environment handle. Values
are:

  • Unicode

    (Default) The OCI client uses the UTF-16 character set. When
    connecting to EAServer with a connection cache, the cache’s
    database driver type must be OCI_9U.

  • Local

    The OCI client uses the current character set defined by the
    NLS_LANG parameter on the local computer. When connecting
    to EAServer with a connection cache, the cache’s database
    driver type must be OCI_9.

  • ValidCharsetName

    Any valid character set name except AL16UTF16. To specify
    a value in the Database Profile Setup dialog box, type the name
    of the character set into the NLS Charset drop-down list box on
    the System page.

Default

NLS_Charset=’Unicode’

Usage

When you specify a value for NLS_Charset, PowerBuilder sets
the OCI NLS_CHARACTERSET property in the current connection. NLS_CHARACTERSET
is a database parameter that specifies the character set encoding
used to store CHAR, VARCHAR2, LONG, and CLOB datatypes. The value
you set corresponds to the character set defined by the NLS_LANG client-side
parameter. NLS_LANG defines the character set encoding
of text that OCI gets from or sends to applications in bind or define
variables or as SQL statements
to be executed by the server.

For the national character set NLS_NCHAR_CHARACTERSET,
the Oracle database interfaces always use the UTF-16 character set.
If you are using pooling with the ORA driver, and two Oracle connections
are connected to the same Oracle server but use different character
sets, the connections must reside in different connection or session
pools. All pooling-related DBParm parameters must be set before
the initial database connection.

For EAServer connections, you can use only Unicode or Local.
For COM+ connections, you can use only Local.

Examples

To specify that the OCI client should use the current
character set defined by the NLS_LANG parameter on the
local computer to store string datatypes:

  • Database profile

    Select Local from the NLS Charset drop-down list on the System
    page in the Database Profile Setup dialog box.

  • Application

    Type the following in code:

See Also

StrByCharset


Document get from Powerbuilder help
Thank you for watching.
Was this article helpful?
Subscribe
Notify of
guest
0 Comments
Inline Feedbacks
View all comments
0
Would love your thoughts, please comment.x
()
x