Oracle 12c Download For Windows 64-bit |VERIFIED|

Hello. I'm writing to share some hard-won lessons about this installation process that are specific to Windows 7 64-bit. First of all, it should be known that the port of Oracle from 32-bit to 64-bit is not, in my opinion, complete.

The installation comes with its own version of Java which apparently has bugs in it. The installation script will not work as it is. It will mysteriously fail without any meaningful log messages. The window just disappears. Even clicking on buttons in the dialog box will make it inexplicably vanish. See other discussions on this forum which are now archived (which is why I'm not simply responding to one of those). To get around this, you will need to use a more recent version of Java. I used the 64-bit version of jdk1.8.0_05. To get the shortened DOS version of this path, I issued the following cygwin command:

Oracle 12c Download For Windows 64-bit

Download Zip 🔥 https://shurll.com/2y7OB3 🔥

On step 2 of 9, check the radio button for "Create and configure database". Step 3 of 9, I selected Desktop Class. On step 4 of 9, I changed the Oracle base to "C:\cygwin\home\lylez\oracle", and accepted the other defaults (such as "Enterprise Edition"). You may wish to accept all the defaults; that's up to you. Select an administrative password (and write it down) and click on Next. Then click on Finish.

Now, when you attempt to launch PL SQL Developer, it will ask you for a JDK. This is another source of misery. If you give it the 64-bit JDK, it will reject it, without telling you why, and it will stay in rejection mode until you give it a different path, even if the contents of the folder you gave it have since changed. You must instead give it a 32-bit JDK version, but it's not enough to simply provide it with a 32-bit java.exe file, you must provide the entire JDK directory and all contents. I copied my 32-bit JDK directory from my other computer, that is, the jdk.1.8.0_05 directory and contents, and gave that path (C:\Program Files\Java\jdk1.8.0_05_32bit is what I named it) to the PL SQL dialog box. Then it will work. At least, it did for me.

Note: the Windows EXE requires a MSVCR100.dll to run. Most computers will already have this file and in the Windows PATH. However, if the first copy of the file found by the EXE is a 32-bit copy of the DLL, then SQL Developer will fail to start. You can fix this by copying a 64-bit version of the DLL into the BIN directory or updating your OS PATH such that a 64 bit copy of the DLL is found first.

Recently I have installed Oracle 11g XE in my laptop with Windows 10 64-bit machine. The installation was smooth. However, I have issue with listener. Can someone please let me know if 11g XE works on Windows 10 o/s ?

I am not sure if that is causing the issue. But can you please let me know how to know if they are blocked in windows firewall ? In-case blocked, how to open them? OR the issue is something else? Please help.

Has anyone gotten JMP 9 or 10 on Windows 7 64-bit to work with a 32-bit Oracle ODBC? I set up several Oracle ODBC data sources using the 32-bit ODBC driver administrator, found here: C:\Windows\SysWOW64\odbcad32.exe

This document collects into one place all the individual platform and certification notes for Database on Microsoft Windows x64 (64-bit) that were in the older My Oracle Support certification system. This document can be used as a standalone reference and index to important details about the certification of all active Database releases on the Microsoft Windows x64 (64-bit) platform. In addition, all individual certifications will refer to this note so there is a single consistent source of certification details.

I have a system running an Oracle database (12c, 64bit) and I need to have ArcMap running on this same system connect to the database. ArcMap is 32bit so I also have the 32bit Oracle 12c instant client on the system. The user I was connected as when I set all of this up works fine having the 64bit oracle server path first in the environment variables. But any other user on this system gets the "Failed to connect to database ... database client software failed to load..." error. All of the discussions on this topic seem to focus on the environment path which I did in order to get the first user to work. But everything is setup the same for the other users yet it doesn't work for them. Is there anything else that could cause the Oracle client to fail to load? Is there any other logs or checks you can perform to see where the problem is coming from?

Also, you mention system in a couple of places- are these different windows users on the same machine trying to open ArcMap 10.2.1 and connect to that Oracle database or are these users on different machines?

I never got it to work. In the end, I setup a VM on the same hardware to act as the "client" while the physical system acted as the server. Then I didn't have to try to work around having the server and client software running on the same windows installation.

I am looking to install toad for oracle 64 bit version to install on windows 10. I am currently running toad for oracle 32 bit version and when i try to install oracle client 32 bit version on windows 10 i am getting this error:

I know this post is about 3.5 years old, but I have a business requirement to export a lot of data to MS Access. I have installed TOAD 11.6, 64-bit on my Windows machine, as well as the 64-bit MS Access Engine. I still get the same error referenced in the original post. Perhaps this is a dumb question, but:

To connect to an Oracle database or Oracle Autonomous Database with Power BI Desktop, install Oracle Client for Microsoft Tools (OCMT) on the computer running Power BI Desktop. The OCMT software you use depends on which version of Power BI Desktop you've installed: 32-bit or 64-bit. It also depends on your version of Oracle server.

To determine which version of Power BI Desktop is installed, on the Help ribbon, select About, then check the Version line. In the following image, a 64-bit version of Power BI Desktop is installed:

Some Power BI Desktop app deployments use on-premises data gateway to connect to Oracle database. To connect to an Oracle database with the on-premises data gateway, use 64-bit OCMT on the computer running the gateway since the gateway is a 64-bit app. For more information, go to Manage your data source - Oracle.

I have downloaded and installed the newest virtualbox 4.3.20 for my Windows 7 (64-bit OS), but when I want to install 64-bit Linux, the New->Create Virtual Machine only displays 32-bit option, no 64-bit option. Could anyone give any clues about this issue? Thanks very much in advance!

We recommend that you migrate one path code to 64-bit ensuring that your business functions migrate properly. This process is described in more detail in the multi-foundation content included in this learning path. Specification merge for UBEs, business views, and table indexes is deprecated with the 64-bit Deployment Server update. Compare tools are available for these objects. Please see the Software Updates guide for more information regarding the compare tools.

Tools Release 9.2.6 and later provides support for upgrading Deployment Server, Enterprise Servers, and Development Clients to 64-bit. If any path code or server remains at 32-bit, the source of truth will be 32-bit . A conversion tool from 32-bit to 64-bit is provided, but the ability to reverse engineer from 64-bit back to 32-bit is not supported.

If you are using a 64-bit development client, business function development is always performed in 32-bit. When you check-in or build through Busbuild the 32-bit version is run through the 64-bit conversion and both the 32-bit and the 64-bit versions are written to the repository in a single record. Any subsequent par that is generated via Configuration Assistant will contain both the 32-bit and 64-bit versions and can be deployed to either a 32-bit or 64-bit path code.

Is there a legitimate best practice way to do this? Specifically I'm wondering about whether each client needs to be in its own BASE directory (say C:\oracle and C:\oracle32) or if they should be within the same base direct but have their own client folders.

This article describes the default installation of Oracle Forms and Reports on Windows (64-bit). The article assumes there is already an Oracle WebLogic Server 11gR1 (10.3.6) installation present on the machine.

Last year I was working on a Data Warehouse project where we were going to use SSIS (SQL Server Integration Services) to read data from an Oracle Database. The problem was that the SSIS development environment uses 32-bit OLE DB drivers, but the SSIS runtime uses 64-bit drivers (this could be changed to 32-bit, but it was not a good solution). So we needed to have Oracle OLE DB 32-bit and 64-bit drivers side-by-side. This was trickier than expected. Here is how we solved it!

The ODAC OUI gives you a graphical user interface for installation, but it only provides you with 64-bit version of the drivers. If you need 32-bit drivers, you will have to use the command-line ODAC XCopy.

The trick is to use Windows symbolic links. The Windows system folder will be in different locations depending on 64-bit or 32-bit mode. Using symbolic links, you can therefore create a path that points differently for 64-bit applications and 32-bit applications.

Before you test the connection to InfoAccess, ensure you have the Oracle client installed and your TNSnames.ora file is in the correct location with an entry for INFOACCESS or DWHP. If you have both 32-bit and 64-bit versions installed, ensure you know your Oracle client paths. Note that paths can be different on different machines. You can find your Oracle client path by searching for tnsping in Windows Explorer. Please refer to Downloading and Installing Oracle Client and Adding, Editing, or Replacing Your TNSnames.ora File for more information.

In Command Prompt, you must change the directory to where the tnsping command is located in the 64-bit Oracle client installation. Type cd C:\, which will allow you to change the directory to the 64-bit Oracle path. You'l know this is successful when Command Prompt shows C:\> before the cursor. 006ab0faaa