Nhib.pdf connecting to Oracle

Oracle I used 10 Gb. Several problems were found after downloading the client for installation. The record is as follows:

Support for Windows 7

The Oracle10g client only supports Windows 6.0 and does not support Windows 7. You need to make the following settings:

Decompress the package and modify the client/install/oraparam. ini file.
[Certified versions]
# You can customise error message shown for failure, provide value for certified_version_failure_message
Windows = 5.0, 5.1, 5.2, 6.0, 6.1 (add 6.1 After window)
Add the following options after [windows-6.0-optional:
[Windows-6.0-optional]
[Windows-6.1-required]
# Minimum Display colours for Oui to run
Min_display_colors = 256
# Minimum CPU speed required for Oui
# CPU = 300
[Windows-6.1-optional]

Modify the following files respectively.
Client/stage/prereq/client/refhost. xml
Client/stage/prereq/client_prereqs/client/refhost. xml
<! -- Microsoft Windows Vista -->
<Operating_system>
<Version value = "6.0"/>
</Operating_system>

The following options are added:
<! -- Microsoft Windows 7 -->
<Operating_system>
<Version value = "6.1"/>
</Operating_system>

Note that multiple refhost. xml files may need to be modified. The 32-bit client may not need to modify oraparam. ini.

Connection string

The connection_string for connecting nhib.pdf to Oracle can be written as follows:

<Item key = "connection. connection_string "> Data Source = (description = (address_list = (address = (Protocol = TCP) (host = server address) (Port = port ))) (CONNECT_DATA = (Server = dedicated) (SERVICE_NAME = database Sid); User ID = user name; Password = password; </item>

32-bit 64-bit debugging environment

My development environment is Windows 7 64-bit, and the project is set to x86 and x64. Running Test in IDE prompts 32-bit code to call 64-bit library errors, check and find that I have hit the 64-bit Oracle client, unmount it, and install 32-bit.

Installation directory permission

After installing the minimum version of the Oracle client component, run the test class and prompt: Try to read or write the protected memory. This usually indicates that other memory is damaged. After checking, the permission problem should be solved. The permission is completely controlled by the authenticated user in the Oracle client directory. The cause is unknown.