I need to direct connect an ArcSDE database already created from ArcCatalog. I know that I need Oracle Client for this purpose but when I start installing Oracle Client, it gives me several options like Instant Client, Administrator, Runtime etc.
I need to know what option should I Select to install minimum components only necessary for ArcSDE Direct Connect.
If you don't need a GUI to populate tnsnames.ora, your can probably get by with just the Runtime client; I've done a custom install and managed to get ArcSDE working with less than the packages installed with Administrator. Instant client is *not* enough. - V
I am trying to get the Instance parameter configured so I just need to provide the sid for the database
e.g. production instead of sde:oracle11g:production so my instance is not tied to a specific oracle client version in which case I would not need to modify my sde connections inside of mxds if I update the Oracle Client.
An ESRI technical representative said that it was setup this way on his machine, but sde:oracle11g keeps getting automatically added to my instance when I create a direct connection in ArcCatalog without specifying sde:oracle11g in the Instance parameter.
Has anyone reached any conclusions about direct connect and Oracle client versions? We are currently using application server connects but will be migrating to direct connects. We don't want to have all the users connections and mxds broken if they get a new Oracle client installed.
I have done some basic testing on a vmware image by using a connection file created for with Oracle 11g. I unstalled the 11G client and installed 10G. After doing this the connection file still worked but I'm not sure if there were still some remnants of the 11G client on my machine.
I'm not sure if at 10.1 and above if the oracle client in the direct connect string is actually used. I suspect it may be there just for historical formatting reasons.
In short I'm reluctant to move 500+ users to direct connects that may break if they get a new Oracle client installed.
I would be grateful if anyone has any experience or information on this.
You will also need to update any lyr files you have that reference application server connects, unless you want to recreate them. I could help you out with some code in that area.
Please note that the above script uses the findAndReplaceWorkspacePath which might have a memory leak that would be detected if you plan on running this script on a large batch of mxds (>400). I have a longer script that uses the replaceDataSource method that has a memory leak issue when running on a large batch of mxds. As such I run my python script on a Windows 2008 Server machine to get as big a batch as possible (>1500 mxds in 1 batch).