Turing's Man Blog
- Last Updated on Tuesday, 12 March 2013 01:46
- Published on Tuesday, 12 March 2013 00:17
- Written by Pawel Wawrzyniak
- Hits: 23777
Now, as we have our MS Windows 8 installed in Oracle VirtualBox (part 8), we can install Oracle Database 11gR2 Client. This will allow us to connect from MS Windows 8 to Solaris 11.1, where our Oracle Database 11gR2 is run. This part will be very straightforward, however, we have to remember that MS Windows 8 is not supported, hence not allowed in production environments (although such scenario is very possible in all kinds of development environments). It was said in previous parts, but... Anyway, we should remember this series is more about experiments than production systems. Let's go.
First of all, remember to download Oracle Client software – use your OTN account. Of course, chose the MS Windows version – in our case, 32-bit. Then extract zip files in the folder in which you store your installation versions.
Oracle client is not certified for Windows 8 – however, it will work. Also, remember about
Java (JDK, not JRE) and .NET platform – these components are required by Oracle tools and will be downloaded and installed during the process. At the time when I was preparing materials for this part, JDK 6 was supported, however, I decided to go with – unsupported – JDK7. This results with some additional tweaking to enable SQL Developer to work correctly, therefore, I think it is even more interesting (and is quite possible in development or other, not so important, environment in which one has to work).
So, let's start with the actual installation – execute setup.exe – a window will appear with the information that this version of Oracle Database 11gR2 Client is not supported on MS Windows 8:
Let's skip it. We already know it and accept the risk in favor of further experiments. On the next screen, we can see the famous Oracle Universal Installer (OUI) – we should select Administrator type of installation here (step 1):
I decided to choose English and Polish language (step 2):
Double-check the paths and click Next > (step 3):
As our MS Windows 8 is not supported by this version of Oracle Database 11gR2 Client, step 4 (Perform Prerequisite Checks) is skipped by the OUI. Now, we are in the step 5, please refer to the selected configuration. Everything is correct? Then click Finish:
Installation process will be started – see the progress bar and status (step 6):
Allow access – we're in secure place, as I guess (it's step 7 right now):
Enigmatic windows – Windows Features: Searching for required files (we can only guess what is going on here):
Well, "downloading required files" – so, it's nice, let's wait:
As we thought – it was about MS .NET 3.5 (which includes .NET 2.0 and 3.0, too). So, MS .NET 3.5 component was successfully installed:
The installation is finished (step 7):
Let's use Windows sign on the keyboard to go back to the metro-style Start menu – we have all the Oracle Database 11gR2 Client components installed and available:
This is a good moment to run SQL Developer. Click on the icon in metro-style Start menu – a window will be shown, asking to select actual JDK installation (in our case we will go with JDK 7, if it is not available, please download it from Oracle and install right now – then provide the path for JDK 7 installation):
We clicked OK and – here it goes, an error:
Well, it was expected. As we said previously – not only Oracle Database 11gR2 Client is not supported on Windows 8, also JDK 7 is not supported by Oracle Database 11gR2 Client. However, it's not a problem for us – there is a simple tweak (or hack, as you wish). We have to copy MSVCR100.dll from JDK directory (C:\Program Files\Java\jdk1.7.0_10\bin) to the root directory of SQL Developer. Ctrl+C in the source directory then Ctrl+V in the destination directory is the whole trick.
Now, when we will execute SQL Developer, there will be a message prompt – we are now officially informed that this product is not certified to be run with JDK 7 and some issues can occur. We will try, anyway:
And... It works (at least to this moment):
We're now ready for part 10.