Oracle version difference configuration)

Most people, not all of whom are usually used in development, are 32-bit PCs. Therefore, oracle32-bit clients are installed. However, the general server is 64-bit and the 64-bit Oracle client is installed. to deploy the application that uses oracle. dataaccess to connect to OracleProgramMay encounter version issues. Specifically, it is manifested in the following two aspects:
There are two major version problems: 32-bit and 64-bit. If the developed application is 32-bit, you must use a 32-bit client, if it is a 64-bit application, it certainly corresponds to a 64-bit client. Note: In a 64-bit environment, use the vsdevelopment web program. The WebService running webdev.webserver.exe is 32-bit. Therefore, to debug a 64-bit Oracle Connection Program, you 'd better deploy it in IIS and use IIS to connect to the Oracle database.
Another version issue is Oracle. dataaccess version. My local machine is 32-bit xp. After the oracle11gr2 client is installed, the ODP under the installation directory is displayed. net \ bin \ 2. oracle. dataaccess. DLL file. The version number is 2.112.1.2. So the program I developed references the library of this version.

However, the 64-bit oracle. dataaccess. dll is different. The installed version is 2.112.1.0 and it is Oracle. dataaccess. dll on windows2008x64.

if you release the Development Environment Program to the server, an exception is thrown.
the file or assembly "oracle. dataaccess, version = 2.112.1.2, culture = neutral, publickeytoken = 89b483f429c47342 "or one of its dependencies.
or
cocould not load file or assembly 'oracle. dataaccess, version = 2.112.1.2, culture = neutral, publickeytoken = 89b483f429c47342 'or one of its dependencies. an attempt was made to load a program with an incorrect format.
in short, the corresponding assembly cannot be found. Apparently, the system is looking for Oracle 2.112.1.2. dataaccess, and only version 2.112.1.0 on the server, so the error is reported. The solution is in the web. modify in config and add the following content after the configsemas node ends:




publickeytoken =" 89b483f429c47342 "
Culture =" neutral "/>

oldversion =" 2.112.1.2 "
newversion =" 2.112.1. 0 "/>



IIS can call Oracle 2.112.1.0. dataaccess. After this configuration is added, it can run normally.

http://blog.csdn.net/linghao00/article/details/8058730