on 12-29-2008 9:56 AM
Hi,
We're using BO XI R2 sp4 on Japanese win2003, and while testing the connection to Oracle 10g (XE) via BO Designer, we see:
Server is not responding (SBO0001)
The detail of the error says:
CS:Invalid native charset : JA16SJISTILDE
Does any one have any idea what to look for?
thanks
Hi Orit
As per my understanding the registry key JA16SJISTILDE for japanese character set is missing.
Please refer to the below links. There is the information about how to set this key.This might be useful:
1. [shodai.hp.infoseek.co.jp/oracle_global/oracle_global.html ]
2.http://publib.boulder.ibm.com/infocenter/cqhelp/v7r0m1/index.jsp?topic=/com.ibm.rational.clearquest.install_upgrade.doc/upgrade/c_migrate_oracle_jp.htm
Regards
Sourashree
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi, the website is in japanese, and unfortunately I don't know the language.. I just provide support to a japanese customer however, here is the oracle registry, can someone comment on its content, or maybe I need to collect more information?
I also asked the customer to provide the output of the following oracle query
*select * from NLS_DATABASE_PARAMETERS*
(output follows the registry below)
[HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE]
@=""
[HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\KEY_XE]
"StmtCacheSize"="0"
"NLS_LANG"="JAPANESE_JAPAN.JA16SJISTILDE"
"ORACLE_HOME_NAME"="XE"
"ORACLE_BASE"="C:
oraclexe
"
"VERSION"="10.2.0.1.0"
"ORACLE_HOME_KEY"="SOFTWARE
ORACLE
KEY_XE"
@=""
"ORAMTS_CP_TRACE_LEVEL"="0"
"Type"=dword:00000055
"ORACLE_SID"="XE"
"ORACLE_HOME"="C:
oraclexe
app
oracle
product
10.2.0
server"
"ORAMTS_CP_TRACE_DIR"="C:
oraclexe
app
oracle
product
10.2.0
server
oramts
trace"
"StatementCacheSize"="0"
"OLEDB"="C:
oraclexe
app
oracle
product
10.2.0
server
oledb
mesg"
"ORA_XE_AUTOSTART"=hex(2):54,00,52,00,55,00,45,00,00,00
"ORA_XE_SHUTDOWN"=hex(2):54,00,52,00,55,00,45,00,00,00
"ORA_XE_SHUTDOWNTYPE"=hex(2):69,00,6d,00,6d,00,65,00,64,00,69,00,61,00,74,00,\
65,00,00,00
"ORA_XE_SHUTDOWN_TIMEOUT"=hex(2):39,00,30,00,00,00
[HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\KEY_XE\ODP.NET]
@=""
"TraceFileName"="C:
ODPNET.trc"
"TraceLevel"="0"
"TraceOption"="0"
"StatementCacheSize"="10"
"Version"="10.2.0.100"
[HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\KEY_XE\OLEDB]
@=""
"CacheType"="Memory"
"ChunkSize"="100"
"DistribTX"="1"
"FetchSize"="100"
"OSAuthent"="0"
"PLSQLRset"="0"
"PwdChgDlg"="1"
"SchRstLng"="10000"
"UserDefFn"="0"
"DisableRetClause"="1"
"VCharNull"="1"
"TraceCategory"="0"
"TraceFileName"="c:
OraOLEDB.trc"
"TraceLevel"="0"
"TraceOption"="0"
"SPPrmDefVal"="0"
"StmtCacheSize"="10"
[HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\OracleMTSRecoveryService]
[HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\OracleMTSRecoveryService\Protid_0]
"Name"="HTTP"
"Host"="test123.lab.com"
"Port"="2030"
[HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\OracleMTSRecoveryService\Setup]
"NumberOfInstalls"=dword:00000001
[HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\OracleMTSRecoveryService\Setup\All Versions]
[HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\OracleMTSRecoveryService\Setup\All Versions\1]
"Version"="10.2.0.1.0"
"Home"="C:
oraclexe
app
oracle
product
10.2.0
server"
[HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\OracleMTSRecoveryService\Setup\Current Version]
"Version"="10.2.0.1.0"
"Home"="C:
oraclexe
app
oracle
product
10.2.0
server"
output of oracle query:
NLS_LANGUAGE AMERICAN
NLS_TERRITORY AMERICA
NLS_CURRENCY $
NLS_ISO_CURRENCY AMERICA
NLS_NUMERIC_CHARACTERS .,
NLS_CHARACTERSET AL32UTF8
NLS_CALENDAR GREGORIAN
NLS_DATE_FORMAT DD-MON-RR
NLS_DATE_LANGUAGE AMERICAN
NLS_SORT BINARY
NLS_TIME_FORMAT HH.MI.SSXFF AM
NLS_TIMESTAMP_FORMAT DD-MON-RR HH.MI.SSXFF AM
NLS_TIME_TZ_FORMAT HH.MI.SSXFF AM TZR
NLS_TIMESTAMP_TZ_FORMAT DD-MON-RR HH.MI.SSXFF AM TZR
NLS_DUAL_CURRENCY $
NLS_COMP BINARY
NLS_LENGTH_SEMANTICS BYTE
NLS_NCHAR_CONV_EXCP FALSE
NLS_NCHAR_CHARACTERSET AL16UTF16
NLS_RDBMS_VERSION 10.2.0.1.0
Hello,
I'm also attached the environment of the admin user and the system env.
Note there is no NLS_LANG setting, maybe related to the issue...
thanks.
admin env:
TEMP=C:\DOCUME1\ADMINI1\LOCALS~1\Temp
TMP=C:\DOCUME1\ADMINI1\LOCALS~1\Temp
system env:
ALLUSERSPROFILE=C:\Documents and Settings\All Users
APPDATA=C:\Documents and Settings\Administrator\Application Data
ClusterLog=C:\WINDOWS\Cluster\cluster.log
CommonProgramFiles=C:\Program Files\Common Files
COMPUTERNAME=TEST123
ComSpec=C:\WINDOWS\system32\cmd.exe
FP_NO_HOST_CHECK=NO
HOMEDRIVE=C:
HOMEPATH=\Documents and Settings\Administrator
JAVA_HOME=C:\j2sdk1.4.2_12
LOGONSERVER=
TEST123
NUMBER_OF_PROCESSORS=1
OS=Windows_NT
Path=C:\PROGRA1\CA\SC\COMMON1\common\3.5\bin\NOTES\;C:\PROGRA1\CA\SC\COMMON1\common\3.5\bin\NOTES\DATA\;C:\oraclexe\app\oracle\product\10.2.0\server\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem
PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH
PROCESSOR_ARCHITECTURE=x86
PROCESSOR_IDENTIFIER=x86 Family 15 Model 4 Stepping 8, GenuineIntel
PROCESSOR_LEVEL=15
PROCESSOR_REVISION=0408
ProgramFiles=C:\Program Files
PROMPT=$P$G
SESSIONNAME=Console
SystemDrive=C:
SystemRoot=C:\WINDOWS
USERDOMAIN=LAB.COM
USERNAME=Administrator
USERPROFILE=C:\Documents and Settings\Administrator
windir=C:\WINDOWS
Hi Orid,
to pick up where Sourashree left off, there seems to be differences in characterset settings between the database the middleware and your client machine.
Has anyone connected successfully before? Can you identify any differences in settings between a machine which connects and one that fails. Has the client setting been altered?
If we assume all machines fail:
1)-Confirm characterset of the database to be unicode eg UTF8 which is multibyte (This seems to be the case from your screen shot)
2)-confirm the character set of the oracle client via iSQL Plus
-SQL>host echo %NLS_LANG% -> (returns NLS_LANG if not set if not set in the Environment)
or
-SQL>@ %NLS_LANG% . -> (returns NLS_LANG if not set if not set in the registry)
-default falue is typically assumed eg US if not set duing client installation
3)-confirm the code page value on the client machine via
HKEY_LOCAL_MACHINE
SYSTEM
CURRENTCONTROLSET
CONTROL
NLS
CodePage -> ACP -> Data -> eg 1252
Do 2 and 3 above correspond? They should otherwise information is lost in translation:
Link: [For more information|http://www.oracle.com/technology/tech/globalization/htdocs/nls_lang%20faq.htm|Valuable information on character sets and how they are dealt with across applications clients and server]
-Ensure the oracle.sbo and oracle.prm files are encoded as UTF-8
-in universe designer, ensure the "unicode" parameter is set to "Yes"
Test your connection
This typically adds to Sourashree's input. I hope our input will help you find a solution.
Regards,
Ken
I will answer the questions:
"Has anyone connected successfully before?"
It depends on which layer. I am using Squirrel with a JDBC Driver from a remote English box, sql plus/tns ping on the local box, and connection seems to work fine. Only connection from the Universe designer seems to fail.
"Can you identify any differences in settings between a machine which connects and one that fails."
The only difference from other boxes where I have experience with a working environment, is the fact that both BO and Oracle XE are on a Japanese OS instead of an English OS. Up until now, we only supported English, and now when we support Japanese we start getting this issue.
"Has the client setting been altered?"
No, it is a fresh oracle XE installation, no changes. I did not also run a separate Oracle Client installation. The XE installation did not ask anything regarding language setup.
Now, the rest of the diagnostics information as requested:
1. db charset is AL32UTF8 as shown earlier, so yes, it's UTF8
2. from SQL Plus I get:
SQL> host echo %NLS_LANG%
%NLS_LANG%
SQL> @.[%NLS_LANG%].
SP2-0310: ファイル".[JAPANESE_JAPAN.JA16SJISTILDE]..sql"をオープンできません。
registry under software/oracle/key_xe/NLS_LANG=JAPANESE_JAPAN.JA16SJISTILDE
NLS_LANG env variable is not set in computer -> properties -> advanced -> env
4. codepage -> ACP = 932 on this box
I've also looked into the link you sent, but I can't say it helped me troubleshoot.
Pls advise, I'm still getting the error. Does this information shed any light on anything?
thanks.
I have some progress:
I updated the registry software/oracle/key_xe/NLS_LANG:
instead of:
JAPANESE_JAPAN.JA16SJISTILDE
I changed it to:
JAPANESE_JAPAN.UTF8
the error in the designer is gone, and after restarting both Oracle and BO, the issue disappears. Note that restarting Oracle alone was not enough. I guess the Oracle client (OCI) really also uses the NLS_LANG registry settings (it should, assuming I understood the NLS faq webpage you sent)
thanks, looks like the issue is resolved!
User | Count |
---|---|
88 | |
10 | |
10 | |
9 | |
6 | |
6 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.