K kaimoeller Member Jun 15, 2008 #1 Hello, my database has the following NLS-settings NLS_LANGUAGE GERMAN NLS_TERRITORY GERMANY NLS_CURRENCY
Hello, my database has the following NLS-settings NLS_LANGUAGE GERMAN NLS_TERRITORY GERMANY NLS_CURRENCY
K kaimoeller Member Jun 15, 2008 #1 When I set NoUnicodeSupport := true; I got Ora-03130. Then setting NLS_LANG in registry back to AMERICAN_AMERICA.WE8MSWIN1252 seems to fix the issue. It's a bit confusing since Oracle encourages the standard use of UTF-8 character set.
When I set NoUnicodeSupport := true; I got Ora-03130. Then setting NLS_LANG in registry back to AMERICAN_AMERICA.WE8MSWIN1252 seems to fix the issue. It's a bit confusing since Oracle encourages the standard use of UTF-8 character set.
Marco Kalter Administrator Staff member Jun 16, 2008 #1 Have you set TOracleSession.BytesPerCharacter to bcAutoDetect? Also note that if you want to display Unicode characters, you need to use data-aware controls that support Unicode like the TNT Controls.
Have you set TOracleSession.BytesPerCharacter to bcAutoDetect? Also note that if you want to display Unicode characters, you need to use data-aware controls that support Unicode like the TNT Controls.
K kaimoeller Member Jun 20, 2008 #1 The setting of bcAutoDetect makes no difference. I do not want to display unicode characters, just special ASCII characters. Now I get an ORA-12899 - value too large for column when a field contains special characters and reaches the limit. If I insert the same string with an SQL tool it works.
The setting of bcAutoDetect makes no difference. I do not want to display unicode characters, just special ASCII characters. Now I get an ORA-12899 - value too large for column when a field contains special characters and reaches the limit. If I insert the same string with an SQL tool it works.
Marco Kalter Administrator Staff member Jun 20, 2008 #1 Can you try the following? Before or shortly after a connection is made in your application, set the global Oracle.NoUnicodeSupport to True.
Can you try the following? Before or shortly after a connection is made in your application, set the global Oracle.NoUnicodeSupport to True.
K kaimoeller Member Jun 20, 2008 #1 Hello Marco, this is already set. Otherwise special characters are not displayed correctly.
K kaimoeller Member Jun 20, 2008 #1 What seems to be the solution against ORA-12899 in UTF8 Databases is to define the varchar length in CHAR and not in BYTE.
What seems to be the solution against ORA-12899 in UTF8 Databases is to define the varchar length in CHAR and not in BYTE.