Print Thread
NLS_LANG problem
#8597 08/13/06 03:26 PM
Joined: Aug 2006
Posts: 2
Israel
_
_ic_ Offline OP
Member
OP Offline
Member
_
Joined: Aug 2006
Posts: 2
Israel
Hi,
My regional settings set to Korean and the NLS_LANG character set set to KO16MSWIN949. I'm getting an error on the Korean client frown , I

Re: NLS_LANG problem
#8598 08/14/06 12:52 PM
Joined: Aug 2006
Posts: 2
Israel
_
_ic_ Offline OP
Member
OP Offline
Member
_
Joined: Aug 2006
Posts: 2
Israel
Hi.
We had a problem with OCILobRead when reading a multibyte LOB buffer (Korean).

We have found a workaround that seems to solve this problem, but is somewhat awkward. The workaround is to call OCILobRead with csid parameter set to 1, instead of 0, which explicitly sets a charset ID to be used for the returned buffer.

Our questions are:
1. Is this an appropriate solution?
2. Is there a better approach?
3. What influence will have not using NLS_LANG on the client side?

Thanks.

Re: NLS_LANG problem
#8599 08/14/06 09:54 PM
Joined: Aug 1999
Posts: 22,219
Member
Offline
Member
Joined: Aug 1999
Posts: 22,219
This is probably a DOA bug, so perhaps we can add suppport for this in 4.1. Can you let me know the results of the following query on this database?

select * from nls_database_parameters
where parameter like 'NLS%CHARACTERSET';


Marco Kalter
Allround Automations

Moderated by  support 

Link Copied to Clipboard
Powered by UBB.threads™ PHP Forum Software 7.7.4
(Release build 20200307)
Responsive Width:

PHP: 7.1.33 Page Time: 0.035s Queries: 13 (0.007s) Memory: 2.5023 MB (Peak: 3.0418 MB) Data Comp: Off Server Time: 2024-05-15 12:39:22 UTC
Valid HTML 5 and Valid CSS