Can't read back a UTF8 clob.

[Greg Stevenson]

We are finally getting serious about multi-lingual support. I was just informed that we can read UTF8 data correctly, but if we write a CLOB it is corrupted when it gets read back (I think everything in the test clob should be plain ASCII characters) I check our current version which is // Version 4.0.6.2 (September 1, 2004). I will investigate further, but I'm just being preemptive just in case this is a known issue fixed in a later release. I also realize how quickly time flies and will get the ball moving on getting the most recent version of DOA.
--Greg

 

[Greg Stevenson]

Never mind. I could not reproduce and developer double checked and realized he was using old DOA dcus. However, I was wondering about how the registry NLS_LANG entries effect the bytesPerCharacter stuff. On various systems we still get ORA-03127 errors on various clobs that we can get to work by tweaking NLS_LANG values, but I sure would like knowing exactly how things should be configured.
--Greg

 

[Bernhard Geyer]

That are Oracle-Bugs. Not all Version of Oracle NET-Client work with all Version of Oracle-Server and Server-Coding.

So if it doesn't work: Try a other Server or Client-Version.

The fewest errors you will get if Client and Server works with UTF8