Specifies the client-side character set for the current environment handle.
O90 Oracle9i
O10 Oracle 10g
ORA Oracle 11g
NLS_Charset='value'
NLS_Charset='Unicode'
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.
Author comment:
HF - 3/3 Check the following - changed sentence
plus added sentences.
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.
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:
SQLCA.DBParm="NLS_Charset='Local'"
