Ole_Brun
asked on
How to configure ODP.NET XCOPY installation on client machine?
I have created a Windows service that interacts with an ORACLE database. For talking with the database I am using the latest version of ODP.NET.
Now, I want to install the service on a client server. However, I do not want to install a full-blown ORACLE client. I only want to copy the necessary files to the server.
Found the following from a thread in the ORACLE forum:
--------------------------
"if you're using ODP.NET 11g and .NET framework 2.0, then try copying these files into your ASP.NET application bin folder
oci.dll
ociw32.dll
Oracle.DataAccess.dll
orannzsbb11.dll
oraociei11.dll
OraOps11w.dll
And make sure you're using easy connect naming for your connection string in your web.config file, similar to below sample
<connectionStrings>
<add name="ConnectionString"
connectionString="Data Source=//192.168.2.8/xe;Pa
providerName="Oracle.DataA
</connectionStrings>
Just replace 192.168.2.8 with your server ip/name and xe with your database service name."
--------------------------
I tried this, but still the service cannot find the dataprovider.
Something tells me that I should have added something to the registry or to the PATH.
Does anyone know what I am missing?
Now, I want to install the service on a client server. However, I do not want to install a full-blown ORACLE client. I only want to copy the necessary files to the server.
Found the following from a thread in the ORACLE forum:
--------------------------
"if you're using ODP.NET 11g and .NET framework 2.0, then try copying these files into your ASP.NET application bin folder
oci.dll
ociw32.dll
Oracle.DataAccess.dll
orannzsbb11.dll
oraociei11.dll
OraOps11w.dll
And make sure you're using easy connect naming for your connection string in your web.config file, similar to below sample
<connectionStrings>
<add name="ConnectionString"
connectionString="Data Source=//192.168.2.8/xe;Pa
providerName="Oracle.DataA
</connectionStrings>
Just replace 192.168.2.8 with your server ip/name and xe with your database service name."
--------------------------
I tried this, but still the service cannot find the dataprovider.
Something tells me that I should have added something to the registry or to the PATH.
Does anyone know what I am missing?
ASKER
schwertner,
Not sure what you mean by this.
I forgot to mention that the connectionstring "Data Source=//myip/prd;Password
Using EZconnect so that I don't need tnsnames.ora.
Not sure what you mean by this.
I forgot to mention that the connectionstring "Data Source=//myip/prd;Password
Using EZconnect so that I don't need tnsnames.ora.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I have been debugging this issue for some time now, and the only solution (or workaround) I have found, is to delete the NLS entry in the registry.
This is ok on a client machine, but when installing the application on an ORACLE server, this is probably not a very good solution.
Anyone who know a different solution to this problem?
This is ok on a client machine, but when installing the application on an ORACLE server, this is probably not a very good solution.
Anyone who know a different solution to this problem?
On the server NLS_LANG parameter is very important and if you use the application there
all components that ensure language transformation should be available. And apparantly this is not the case.
Concentrate on the client site. Oracle also have 'thin client", that is not so big as the normal Oracle client.
all components that ensure language transformation should be available. And apparantly this is not the case.
Concentrate on the client site. Oracle also have 'thin client", that is not so big as the normal Oracle client.
ASKER
Thanks for you answer!
I have tried using both the ODP.NET client and the Microsoft Oracle client, but with the same result.
The error message regarding the NLS_LANG pops up. Strangely this only happens when running the .NET 2.0 version of the application. I have an older version using .NET 1.1, and that works fine.
One of our clients will have the application running on an ORACLE server, which means it will not work.
This is becoming a big problem, and I have to find a way around it asap.
I have tried using both the ODP.NET client and the Microsoft Oracle client, but with the same result.
The error message regarding the NLS_LANG pops up. Strangely this only happens when running the .NET 2.0 version of the application. I have an older version using .NET 1.1, and that works fine.
One of our clients will have the application running on an ORACLE server, which means it will not work.
This is becoming a big problem, and I have to find a way around it asap.
see
http://www.connectionstrings.com/?carrier=oracle