Once you finished downloading the installation source from Oracle, extract the files using any available unzip utility.
Copy all the folders from “win64_11gR2_database_2of2\database\stage\Components” to
“win64_11gR2_database_1of2\database\stage\Components” folder to avoid warnings about missing components during installation. Oracle should fix it, right?
If your computer is a domain member, then
Create a local user
Add the user to “Administrator” group
Logon as local user
If you are installing Oracle on D:\ , right click and assign full rights to your account on that particular drive. Only applicable with Window7 and Windows 8
Start the installation, and you will be provided a warning. Refer the image below
Ignore it
Proceed with the installation
Ignore the update related warning also
Just follow the prompts and complete the installation. It should be a smooth sailing.
Prior trying to access the database, make sure you changed the sqlnet.ora file following
# This file is actually generated by netca. But if customers choose to # install “Software Only”, this file wont exist and without the native # authentication, they will not be able to connect to the database on NT.
So, you are still using classic ASP or develop 32bit .NET applications using Visual Studio and Oracle databases on a Windows 7 64bit box and completely lost as connection cannot be established?
Here are few workaround solutions
Install the latest Oracle clients (both 64bit and 32bit)
If you installed Oracle client in the following folders (example)
D:\app\yourusername\product
right click on the folder, under security tab check whether authenticated users have read privileges.
If not, provide the basic privileges (Read & Execute, list folder contents, Read) Refer the image
Now add the user “IIS_ISURS” user and provide the same rights mentioned above
RESTART your Windows 7 “64bit” box now!
You can establish the connection from classic ASP like following
<%
Dim adoCon 'Holds Connection
Dim rsViewRecords 'Holds Recordset
Set adoCon = Server.CreateObject("ADODB.Connection")
if Err.Number <> 0 then
Response.Clear()
response.Write "<hr>ORASESSION Error<br>" & err.number & " -- " & err.Description & "<hr>"
response.End
end if
adoCon.Open "provider=oraoledb.oracle;data source=test;user id=apps;password=apps;plsqlrset=true"
Set rsViewRecords = Server.CreateObject("ADODB.Recordset")
%>