About cookies on this site Our websites require some cookies to function properly (required). In addition, other cookies may be used with your consent to analyze site usage, improve the user experience and for advertising. For more information, please review your options. By visiting our website, you agree to our processing of information as described in IBM’sprivacy statement. To provide a smooth navigation, your cookie preferences will be shared across the IBM web domains listed here.
Question & Answer
Question
How can I know which character set is in use? This technote should be used to identify what Oracle Character set is in use, which can be important to know when an IBM® Rational® RequisitePro® requirement’s text has been replaced with question marks.
Cause
Oracle allows you to specify which character set it will use, both on the Oracle client and on the Oracle server. When the Oracle client flags the Oracle server to store a character it does not understand the Oracle server stores the character as a question mark. This usually happens when the character set on the client is not a subset of the character set in the database.
Answer
To resolve this problem you must identify what the character set is on your client, on your server, and if these character sets are compatible:
- The character set on an Oracle client is stored in the following key:
HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\HOME0\NLS_LANG
Note: There may be other HOME<N> Registry branches as well. The Oracle client character set is the last section of the value.
For example: If the registry value is: AMERICAN_AMERICA.WE8ISO8859P1 then the character set is WE8ISO8859P1. - To determine what character set in on the server submit the following query:
Select SYS.PROPS$.VALUE$ From SYS.PROPS$ Where ((SYS.PROPS$.NAME = 'NLS_CHARACTERSET')) ;
Note: To perform this query you need to be logged in with SYSDBA privileges such as a system/manager
The following chart is a brief list of Oracle character sets and their compatibility.
Superset | Subset |
WE8ISO8859P1 | US7ASCII |
ALT24UTFFSS | US7ASCII |
The follow is an example of two code pages that are not completely compatible.
If ISO-8859-1 was used on the database server and CP1252 was used on the client the top two rows of character in CP1252 could not be stored in the database server. The server would save these characters as question marks.
CP1252 Encoding Table

ISO-8859-1 Encoding Table

[{"Product":{"code":"SSSHCT","label":"Rational RequisitePro"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Database: Oracle","Platform":[{"code":"PF033","label":"Windows"}],"Version":"2003.06.15;2003.06.16;7.0;7.0.0.1;7.0.0.2;7.0.0.3;7.0.0.4;7.0.0.5;7.0.0.6;7.0.0.7;7.0.0.8;7.0.0.9;7.0.1;7.0.1.1;7.0.1.2;7.0.1.3;7.0.1.4;7.0.1.5;7.0.1.6;7.0.1.7;7.0.1.8;7.0.1.9;7.1;7.1.0.1;7.1.0.2;7.1.1;7.1.1.1;7.1.1.2","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Was this topic helpful?
Document Information
More support for:
Rational RequisitePro
Software version:
2003.06.15, 2003.06.16, 7.0, 7.0.0.1, 7.0.0.2, 7.0.0.3, 7.0.0.4, 7.0.0.5, 7.0.0.6, 7.0.0.7, 7.0.0.8, 7.0.0.9, 7.0.1, 7.0.1.1, 7.0.1.2, 7.0.1.3, 7.0.1.4, 7.0.1.5, 7.0.1.6, 7.0.1.7, 7.0.1.8, 7.0.1.9, 7.1, 7.1.0.1, 7.1.0.2, 7.1.1, 7.1.1.1, 7.1.1.2
Operating system(s):
Windows
Document number:
77423
Modified date:
16 June 2018
UID
swg21175124
Manage My Notification Subscriptions