Oracle Database 1. R2 prerequisites. Oracle RAC 12c Database on Linux Using VirtualBox By Sergei Romanenko October, 2013 This article describes the installation of Oracle Database 12c Release 1 (12.1.0.1. RAC on OS OEL6.5 on Oracle. Step Install of Oracle RAC 11gR2 on OEL 6.5 on Oracle VM Virtual BOX 56 comments. Here I am listing out the steps to install 11gR2. Before actual installation on Solaris 1. Details. Last Updated on Sunday, 2. February 2. 01. 3 2. Published on Sunday, 3. Installing Oracle RAC 10g on. Learn the basics of installing Oracle RAC 10g Release 2 on Red Hat Enterprise. Turing's Man Blog Part 4. Database 11gR2 installation process on Oracle Solaris 11.1 is much easier than when compared to Oracle Solaris 10 or. Oracle Database 11g Release 2 RAC On Oracle Linux 5.8 Using VirtualBox. 11gR2 RAC requires much more memory than. Step by Step to Install oracle grid 11.2.0.3 On solaris 11.1. Step by Step to Install oracle grid. December 2. 01. 2 2. Written by Pawel Wawrzyniak. Hits: 3. 55. 49 We have configured our fresh Oracle Solaris 1. Oracle Database 11gR2 on Solaris 11.1. Create virtual Machine using Oracle VirtualBOX 2) Install Oracle Solaris 11.1. Install Oracle Solaris 11.1. RAC Attack - Oracle Cluster Database at Home/Overview. RAC Install; Create Database; Rolling. 11gR2 RAC on VMware Server with ASM or Shared Filesystem and. This Video Describes how to install oracle 12c rac on virtualbox. Skip navigation Upload. The Oracle Real Application Clusters (RAC). Oracle Solaris 11.1 VM for Oracle VM VirtualBox. I have Install Oracle Solaris 11 x86. Now we can start preparations for Oracle Database 1. R2 binaries installation. Let's check all the prerequisites – as presented in the official documentation – and then run the installation process with Oracle Universal Installer (OUI). The most important documents for us are: First of all, let's check the RAM requirements. According to documentation, a minimum is 1 GB and recommended amount of RAM is 2 GB or more. We set 2 GB for our virtual machine, so it's good, but anyway – use root role: root@turingsman: ~# prtconf . The rule is that for RAM size between 1 GB and 2 GB, the swap size should be equal to 1. RAM. If there is more than 2 GB RAM and less than 1. GB, then the swap size should be equal to the RAM size. If there is more than 1. GB of RAM, our swap size shouldn't be bigger than 1. GB. Execute the following command: root@turingsman: ~# swap - lhswapfile dev swaplo blocks free/dev/zvol/dsk/rpool/swap 2. K 2. 0. G 2. 0. G2 GB is enough. If you have less than 2 GB, please refer to the ZFS documentation and expand swap to required size – the process of adjusting size of swap on an active system is very well documented in ! Of course, this is supported architecture. We will need at least 1 GB in the /tmp directory. Therefore, let's check it: root@turingsman: ~# df - h /tmp. Filesystem Size Used Available Capacity Mounted onswap 2. G 1. 28. M 2. 4. G 6% /tmp. OK. Otherwise, it should be expanded – refer to . If you created at least 3. GB hard drive for your virtual machine in Virtual. Box, as it was recommended several times before – it's Ok. Otherwise, please refer to part 4. A of this series. Now, there is the most important information in official Oracle Database 1. R2 installation guide: no special kernel parameters, packages, or patches are required at the time of this release for Oracle Solaris 1. Seems that the whole Oracle Database 1. R2 installation process on Oracle Solaris 1. Oracle Solaris 1. Linux distributions. I strongly recommend to follow the official documentation. However, as I made some additional modifications using Oracle Solaris projects feature I'll present them later in this article. Alright. Enough about parameters, packages or patches (still, as I was experimenting with the whole thing, I made some more/less rational decisions myself – I'll present these modifications later). We have to check what version of Solaris and what update level we’re using – to be sure we're compliant with the Oracle requirements: root@turingsman: ~# uname - a. Sun. OS turingsman 5. Oracle Solaris 1. X8. 6 Copyright (c) 1. Oracle and/or its affiliates. Assembled 1. 9 September 2. Everything is OK. We assume that there are no other Oracle products installed on this machine. This is the first installation, so we now have to create some required groups and users: # groupadd oinstall# groupadd dba# useradd - d /export/home/oracle - m - s /bin/bash - g oinstall - G dba oracle. This command creates the oracle user and specifies . Oracle recommends the following minimum values for STACK (- s) = 3. NOFILES (- n) = 4. Tune them with the following commands: root@turingsman: ~# ulimit –s 3. You can check that limits were changed with the previous commands again (ulimit –s, ulimit –n). To have these changes permanent, you should define the limits in /etc/system or use Oracle Solaris projects feature. Now, I've unfortunately made some additional changes with the projects feature of Oracle Solaris. You can follow my way to stay compliant with the record of this exercise. Perform the following commands: root@turingsman: ~# projadd - U oracle - K . So, log to the oracle account now: # su – oracle. And run vi editor with the . However, at this stage this can be tricky as all the paths presented in the . These paths don't exist at this stage of installation. Please only note, that if we change the paths in OUI we have to edit . Also, our Oracle Database 1. R2 installation should be planned, so we can assume that the following paths pattern will be copied in OUI (this is our plan). Now, we can copy the installation packages and unzip them for oracle user. So, login as oracle (if not logged in already) and create a directory for installation packages. This can be anywhere – we just have to remember that we will require a few GBs of space for zipped installation packages and unzipped content. For example, this can be done the following way: root@turingsman: ~# su - oracle. Oracle Corporation Sun. OS 5. 1. 1 1. 1. 1 September 2. So, copy the installation packages to . Let's check it: -bash- 4. Dec 2. 6 0. 1: 0. Dec 2. 6 0. 1: 0. Nov 2. 4 2. 00. 9 database- bash- 4. Before I ran Oracle Universal Installer (OUI) from database directory for good, I did some additional changes in the operating system. I installed JDK7 (with Add More Software tool – available directly from the Gnome desktop). Also, I installed SUNWmfrun package – to avoid possible error about Motif libraries. You can do the same to stay compliant with our exercise. Also, some experts say that this is not required to export DISPLAY variable when OUI is executed locally. Well, seems this statement is not true. I had to export DISPLAY variable to avoid OUI errors during initial prerequisites check. This can be done with the following command from oracle user (Bash): -bash- 4. DISPLAY=turingsman: 0. DISPLAYChange . Let's check we have all we need in the database directory: -bash- 4. Nov 2. 4 2. 00. 9 . Dec 2. 6 0. 1: 0. Nov 1. 8 2. 00. 9 docdrwxr- xr- x 4 oracle oinstall 1. Nov 2. 4 2. 00. 9 installdrwxr- xr- x 2 oracle oinstall 5 Nov 2. Nov 2. 4 2. 00. 9 rpm- rwxr- xr- x 1 oracle oinstall 6. Nov 2. 4 2. 00. 9 run. Installerdrwxr- xr- x 2 oracle oinstall 3 Nov 2. Nov 2. 4 2. 00. 9 stage- rw- r- -r- - 1 oracle oinstall 5. Nov 1. 7 2. 00. 9 welcome. Be sure to run the OUI from oracle user session in Gnome: -bash- 4. Installer. That's all for now. We will continue with the Oracle Universal Installer in the part 5 of this series.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
January 2017
Categories |