32-bit Plsql login 64-bit ORA11G related issues

32-bit PLSQL login 64-bit ora11g problem
background:
Windows 7 64-bit operating system, installation database: Win64_11gr2_database_1of2, WIN64_11GR2_DATABASE_2OF2,
client: win32_11gr2_client,plsql8.0 (currently only 32 bits)
issue: Plsql login times wrong:
initialization Error
Could not initialize "C:\oracle\product\10.2.0\client_1\bin\oci.dll"
Make sure you have the -bits Oracle Client installed.

Ocidll forced to
C:\oracle\product\10.2.0\client_1\bin\oci.dll
LoadLibrary (C:\oracle\product\10.2.0\client_1\bin\oci.dll)
returned 0
degree Niang solution:
   
this is because Plsql developer does not support the 64-bit version (Plsql Developer is Delphi Development, and the development tool itself is not 64-bit);

plsql Develpoer Official: http://www.allroundautomations.com/plsqldev.html. The solution is as follows: To download Oracle's Instant Client, official: http:/ /www.oracle.com/technology/software/tech/oci/instantclient/htdocs/winsoft.html

after downloading to a path, and then into Plsql Developer 8-tools-preferences-Inside the Oracle home directory and the OCI library, respectively, write the Oracle Instant client decompression path information, as follows:

Oracle Home directory: Instant client unzipped directory .../instantclient_11_2.

OCI Library: Oci.dll file in Oracle home directory .../instantclient_11_2/oci.dll.

The above configuration is actually equivalent to replacing the Oracle client, and then we need to configure the environment variables of the system.

The main requirements are the following two items:

variable name: tns_admin.

Variable Value:/product/11.2.0/dbhome_1/network/admin in the Oracle installation directory .

variable name: Nls_lang.

Variable Value: American_america (Database character encoding).
(in addition, the following is required to install Oracle, or there may be a TNS protocol adapter error)
variable name: Oracle_sid
Variable Value: Oracle's DB instance
The database character encoding can be queried by entering SQL PLUS select Userenv (' language ') from dual.
This restarts the Plsql Developer, and then it can be accessed.

This method still does not solve the problem, I do not know if you have encountered this situation