Korean Characters & C++ about ocilib

[vrogier]

Hi,

What version of ocilib are you using ?
What ocilib charset mode (ansi/widechar) ?
What platform ?

Regards,

Vincent

[Tyrannmisu]

We are using ocilib 4.2.0 with charset mode ANSI.

The c++ Middleware runs on Red Hat Enterprise Linux Server release 6.7.
The Database is: Oracle Database 12c Enterprise Edition 12.1.0.2.0 64 bit

We found out that it works as desired without further adjustments of the middleware if the database is installed with an "AL32UTF8" Charset. (NLS_CHARACTERSET = AL32UTF8)

The other database-installation was done with "WE8ISO8859P15", this turned all korean characters to '¿¿¿¿'.

Still weird that it worked via a C# service.
My guess: The C# -Service wrote the strings as nvarchar, which is set to "AL16UTF16" in the database.

It seems like ocilib binds the values as varchar, which is set to "WE8ISO8859P15".
But that's really only me guessing.

[vrogier]

Hi,

you can use OCI_BindSetCharsetForm(bind, OCI_CSF_NATIONAL) to indicate you're binding strings using national charset) :)

Regards,

Vincent.

[Tyrannmisu]

Thanks!

I'll try that :)

[vrogier]

Hi,

Any news ?

Regards,

Vincent

[Tyrannmisu]

Sry that i was quiet for so long.

The problem is that i don't have an Database to test it any more.
The Only one that i can test against was re-installed with "AL32UTF8".

If i get a chance to test OCI_BindSetCharsetForm(bind, OCI_CSF_NATIONAL) against a "WE8ISO8859P15"-database i will. But right now i don't have this possibility in the current project.

We are supposed to get a new development-DB where we can play around, but i cannot change the charsets in the database we have right now.

[Ben136KBC]

FYI: We can successfully write Unicode to a database using OCILIB, using ANSI charset mode on Windows. We have this code:

     _putenv_s( "NLS_LANG", "American_America.UTF8");
     boolean ret = OCI_Initialize(NULL, NULL, OCI_ENV_DEFAULT);
     _putenv_s( "NLS_LANG", "");

And it also requires the database to have a suitable character set I think.
Any strings you transfer have to be UTF8 encoded first!

[vrogier]

Closing it as answers have been provided and no more OP activity