*How can I confirm that Chinese characters are supported by my oracle database ?*
See this answer to understand how to retrieve current NLS parameters. The full list of possible character sets. I presume that to support chinese database should have either AL32UTF8, or some appropriate national character set from the list above.
Related
I have an agent written in Lotuscript (IBM Domino 9.0.1 - Windows 10) that reads records into a DB2 database and writes them to Notes documents. The table in DB2 (Centos OS) contains international names in Varchar fields such as "Łódź".
The DB2 database was created as UTF-8 CodePage: 1208 and Domino by its nature supports UNICODE. Unfortunately, the value loaded in the notes document is not "Łódź" as it should be but it is "? Ód?".
How can I import special characters from DB2
in Domino NSF DBs in correct ways?
Thank you
To import the table I used the following code taken from OpenNtfs XSnippets:
https://openntf.org/XSnippets.nsf/snippet.xsp?id=db2-run-from-lotusscript-into-notes-form
Find where the codepage conversion is happening. Alter the lotusscript to dump the hex of the received data for the column-concerned to a file or in a dialog-box. If the hex codes differ from what is in the column, then it may be your Db2-client that is using the wrong codepage. Are you aware of the DB2CODEPAGE environment variable for Windows? That might help if it is the Db2-client that is doing the codepage conversion.
i.e setting environment variable DB2CODEPAGE=1208 may help, although careful testing is required to ensure it does not cause other symptoms that are mentioned online.
I am loading data into QlikView report from different sources, one of them is Sybase db. Seems like Sybase db is using ISO 8859-1 encoding, but there are also Russian characters there, and QlikView just don't display them properly.
I don't see the way to manually define encoding in Qlikview. Is there any?
I tried to specify cyrillic charset in ODBC settings, but it also doesn't help. Funny thing is ASE isql (tool to run queries on Sybase) there is no issue with encoding. Can I specify encoding when select stuff in Sybase?
Sounds like a charset conversion issue. My guess is that your isql has a charset conversion option enabled, but your qlikview session has not.
I hope there is some person from Georgia who might be able to help with my setup.
I have problem with Georgian database with SQL Server 2008R2. SQL Server is set to have default locale General Latin 1. it is running on Windows 7 which is installed with default English language. I am using this server to work with English, German, Slovak, Russian, Hebrew and Latvian databases without any problem.
now, when i try to create database using Georgian_Modern_Sort_CI_AS collation then database is created successfully, database structure is created but later when i try to use it it fails with error "The Collation specified by SQL Server is not supported."
I noticed that on MSDN page related to collations https://msdn.microsoft.com/en-us/library/ms143508%28v=sql.105%29.aspx Georgian collation is marked with star. However I didn't found any description what this star means.
I checked regional settings in my Windows and I noticed that if I want to change system locale then Georgian is not available in the list. I can install Georgian as display language, but it made no change in available system locales anyway.
Any idea what should I do to be able to work with Georgian databases?
Ouch, not sure if this is good, but I found something in mssql 2005 that is saying there is no way for Georgian or Hindi and varchar :/
The last example returns 0 (Unicode) as the code page for Hindi. This example illustrates the fact that many locales, such as Georgian and Hindi, do not have c?code pages, as they are Unicode-only collations. Those collations are not appropriate for columns that use the char, varchar, or text data type, and some collations have been deprecated. For a list of available collations and which collations are Unicode-only, see Collation Settings in Setup in SQL Server 2005 Books Online.
resources:
https://technet.microsoft.com/en-us/library/bb330962(v=sql.90).aspx
When must we use NVARCHAR/NCHAR instead of VARCHAR/CHAR in SQL Server?
DO SOMEONE HAVE DIFFERENT WAY HOW TO AVOID USING NVARCHARs FOR GEORGIAN SCRIPT OR HINDI?
I have recently started using PostgreSQL for creating/updating existing SQL databases. Being rather new in this I came across an issue of selecting correct encoding type while creating new database. UTF-8 (default) did not work for me as data to be included is of various languages (English, Chinese, Japanese, Russia etc) as well as includes symbolic characters.
Question: What is the right database encoding type to satisfy my needs.
Any help is highly appreciated.
There are four different encoding settings at play here:
The server side encoding for the database
The client_encoding that the PostgreSQL client announces to the PostgreSQL server. The PostgreSQL server assumes that text coming from the client is in client_encoding and converts it to the server encoding.
The operating system default encoding. This is the default client_encoding set by psql if you don't provide a different one. Other client drivers might have different defaults; eg PgJDBC always uses utf-8.
The encoding of any files or text being sent via the client driver. This is usually the OS default encoding, but it might be a different one - for example, your OS might be set to use utf-8 by default, but you might be trying to COPY some CSV content that was saved as latin-1.
You almost always want the server encoding set to utf-8. It's the rest that you need to change depending on what's appropriate for your situation. You would have to give more detail (exact error messages, file contents, etc) to be able to get help with the details.
My database(Oracle 10g) characterset is set to ISO-8859-6(AR8ISO8859P6) to store arabic characters.
When I query the database, JDBC Converts the data from the database character set to Unicode.
Because of this unicode conversion some of the characters are lost(translated to ?)
same behavior for both oci and thin..
In JAVA Is there any solution to retrieve the data in database format(without doing any unicode conversion)?
Is there any driver available retrieve the data from oracle in database format( encoding)?
Thanks
I doubt that any conversion TO Unicode can fail. But a conversion FROM Unicode to something else might fail. This can be the case when storing back the data or - most likely - on output to some terminal or UI.
If that's not the case: Can you give us some examples for each step?