The dbinit_service_name.sde file is not being read when using a second multiple geodatabase in a second Oracle database instance residing in the same SDEHOME as first Oracle database instance.
上次发布: August 25, 2014ArcSDE/Enterprise Geodatabase
漏洞 ID 编号
NIM058641
已提交
June 29, 2010
上次修改时间
April 2, 2025
适用范围
ArcSDE/Enterprise Geodatabase
找到的版本
9.3.1
操作系统
Windows OS
操作系统版本
2008 64 Bit
状态
Will Not Be Addressed
开发团队已考虑过该问题或请求,并决定不会解决该问题。 问题的“其他信息”部分可能包含进一步说明。
附加信息
We apologize that we were unable to address this issue within the current product support cycle. If the issue continues to affect your work in a supported release, please contact Technical Support.
解决办法
Workarounds:************a) Set LOCAL as second database instance in command line before running the sdesetup command for second geodatabase schema.e.g., set LOCAL=GISPRODIt creates multiple geodatabase schema. However, connection fails with error: "Failed to connect to the server. Bad login user". Because it is only reading the default dbinit.sde file even though it has been renamed as dbinit_service_name1 and SDEHOME has another dbinit with second service name appended to its name.b) Set ORACLE_SID to second database instance in the default dbinit.sde file.e.g., set ORACLE_SID=gisprod (in dbinit_esri_gisdev.sde/dbinit.sde)c) Use Direct connection string after password to run the command.e.g., sdesetup -o install -d ORACLE10G -u cprod -p cprod@gisprod -i esri_gisprod:cprod -H "<a href="file:C:/Program" target="_blank">C:\Program</a> Files\ArcGIS\ArcSDE\ora10gexe"d) Copy the SDEHOME and create a new service pointing to new SDEHOME for one database instance.e) Do not set LOCAL or ORACLE_HOME to any Oracle instance in default dbinit.sde.