64-bit host 64-bit Oracle under 32-bit client ODAC (version Nfpacs)

64-bit host 64-bit Oracle under 32-bit client ODAC (Nfpacs version) by DD

1. Download the two versions of Oracle Data Access components (ODAC) xcopy:

x86: (We use this odac1120320xcopy_32bit) http://www.oracle.com/technetwork/database/windows/downloads/index-101290.html

X64:http://www.oracle.com/technetwork/database/windows/downloads/index-090165.html

2, extract to any folder (temporary, one can be deleted)

2.1 Start and run->CMD->CD the folder (it is recommended to open CMD directly to the Cmd.exe directory as an administrator)

2.2 Run command install.bat all {destination path: The last directory to be installed} ODAC

Example: Install.bat all C:\Oracle\ODAC1120320Xcopy_32bit ODAC Enter

3 Add it to the system environment variable: (remember to do exactly the same as the actual path)

The value of path is increased by: C:\Oracle\ODAC1120320Xcopy_32bit; C:\Oracle\ODAC1120320Xcopy_32bit\bin;

This value is subject to actual conditions.

4. Set Tnsnames.ora

After installing ODAC, it means that the 32-bit program connects to Oracle instead of installing ORACL's own client, so you need to add Network\admin\tnsnames.ora to the corresponding path. Specifically in the Odac1120320xcopy_32bit directory add Network\admin\tnsnames.ora and Network\admin\sqlnet.ora (sqlnet.net best Plus, no impact)

5. Set character sets.

Because the web needs to connect to the database through the ODAC, the client's character set is not in the original registry software, but the client's character set does not necessarily match the character of the database server. Directly at the advanced level, the environment variable plus a character set can be solved. This step is available for step 6 of the web and step 7 of Plsql, and restarts IIS or the server if the Web does not work.

Programs placed in 6.IIS require local access to Oracle, including access using oracle.dataaccess and System.Data.OracleClient, and may require running "IISRESET" to restart IIS or restart your computer before you can use it.

7. Set up Web. config Connection driver, open web.config--<!--PACs database-->--name= "pacsconnectionstring" connectionstring= "--provider =msdaora.1;

Determine provider=msdaora.1, which is appropriate for the character set of Us7ascii.

8. Due to the 64-bit Oracle installed on the machine, the result of attempting to access it using Plsql Developer reported that the Oci.dll file could not be loaded. On the basis of the above can solve this problem.

Set up the Oracle_home and OCI libraries, such as the native settings, in the preferences, tools, such as:

Oracle Home:c:\oracle\odac1120320xcopy_32bit

OCI Library:c:\oracle\odac1120320xcopy_32bit\oci.dll

About some of the issues you might encounter:

First: The "oraledb.oracle" provider is not registered on the local computer.

Several methods have been looked up on the internet, probably as follows

1. Add maximum permissions to the Everyone,asp.net or Network Service account for the catalog.

2.regsvr32 OraOLEDB11.dll (register as below)

When I install ODAC 32-bit, I try to do nothing, you can try this:

1. Remove it first and reload it again.

2. Ensure that the path to the environment variable is consistent with the directory you are installing.

Second: To prevent a program from being incompatible with 64-bit systems, set the program pool to 32-bit enabled. Click: roles-Internet Information Services (IIS) Manager-Application pool-pacsweb-right advanced settings-enable 32-bit application: True to determine.

64-bit host 64-bit Oracle under 32-bit client ODAC (version Nfpacs)