This article describes the procedure for installing the ORACLE 11gR2 DBMS on a stand-alone server running the ORACLE Linux 6 OS.

Foreword

If you are reading this, then I recommend that you stop it. Pay attention to other Orthodox DBMS, such as PostgreSQL, etc. You can also consider Dzen DBMS related to NoSQL. The only excuse for further reading may be a pistol (or something like that) pressed to a temple.
It is also considered that the product you are using is backed by a corresponding license. The organization in which this installation takes place is the lucky owner of the Oracle Standard Edition license, therefore the installation of this version will be considered. But the difference in installation will be only in the final stages.
This instruction was written during the installation of the DBMS in order to be able to be repeated by an employee with any qualification. In this connection, I tried to paint everything as detailed as possible. Some things may seem obvious, which in no way questions the skills of the masters.

Operator prerequisites

Understand what is written here . It is advisable to be registered with Red Hat for full access to the documentation, since there will be no links to it here, since it is available only to subscribers. For example: here pdf is available for subscribers with instructions for installing ORACLE on RHEL6.
')

Installing OS ORACLE Linux 6

Install Linux OS ORACLE 6 from the distribution downloaded from e-delivery (You can use any other clone RHEL5, for other clones you will need to install oracle-rdbms-server-11gR2-preinstall.x86_64 oracleasm-support.x86_64 with handles, only for RHEL5 clones) . When installing pay attention to the following:

1. It is necessary for the ORACLE DBMS server to have a FQDN . To do this, make the appropriate entry in your domain name server. In our case it will be oracleserver.kontora.ru .
   
2. The installation language for convenience is Russian, the keyboard layout is American.
   
3. Splitting hard drives (it is recommended not to use logical volumes for ASM disks, among other things, this gives a bonus in the form of the possibility of using udev rules instead of the ASMLib library, which will allow you to leave SELINUX enabled , but in view of the limited resources I use them):
   
   1. The / boot partition, most distros recommend 512MB for it.
      
   2. The remaining disk space for the PVM (physical partition for creating a volume group).
      
   3. Create a volume group and assign it the name “vg_oracleserver”. Create in it the following sections:
      
      1. swap - for 64-bit systems, is equal to RAM with RAM = <32 GB, or 32 GB with large RAM ( link ) with a probability close to 1, installation is performed on this type of equipment. [on the Internet there is an opinion that 250 Russian rubles will be saved by the father of Russian Democracy 16 GB]
         
      2. temp - at least 1 GB ( more ).
         
      3. 640 KB is enough for all 32 GB should be enough for the root directory (we will keep the base in ASM), you can create different block devices for each directory, but they will not differ in mount parameters.
         
      4. Partitions for ASM will be created during installation.
         
      
      
   4. Installation type 'Basic server', choose to configure the list of packages now:
      
      1. in the base packages, add a group of compatibility packages with previous Linux releases and a group of compatibility packages with Unix;
         
      2. in the group of servers we select administration packages and check packages that start with oracle * (further it is considered that these packages are installed, and corresponding parameters are already available, when installing on RHEL6, these packages will need to be installed manually).
         
      
      
   
   

After reboot, connect to the server through a secure shell.
$ ssh root @ oracleserver

After installation, add the EPEL repository (optional, I use it only because of bash-completion). Upgrade the system (required) !!!
# yum install download.fedoraproject.org/pub/epel/6/x86_64/epel-release-6-8.noarch.rpm
# yum -y upgrade

The oracle-rdbms-server-11gR2-preinstall package adds system users and configures the system parameters for running ORACLE DBMS, but this is not enough for US, so we do the following:

1. create user groups
   # groupadd -g 54321 oinstall (already there !!!)
   # groupadd -g 54322 dba (already there !!!)
   # groupadd -g 54324 asmadmin
   # groupadd -g 54326 asmdba
   # groupadd -g 54327 asmoper
   
   
2. create users and define their groups
   # usermod -G asmdba, dba oracle
   # useradd -u 54322 -g oinstall -G asmadmin, asmdba, asmoper, dba grid
   
   
3. create passwords
   # passwd oracle
   # passwd grid
   
   
4. let's set SELINUX rules
   # vim / etc / selinux / config
   replace SELINUX = enabled
   on SELINUX = disabled
   This action is awful, but it is required by the official ORACLE documentation. Judging by the RedHat documentation, this item can be circumvented by using udev instead of ASMlib (if I have hardware and time, I’ll check it, but for the time being we are working on the ORACLE documentation).
   
   
5. let's set the firewall right
   # vim / etc / sysconfig / iptables
   comment out the restrict lines and restart
   # service iptables restart
   Again, terrible action, and again required documentation. Although after installation you can experiment and achieve stable operation.
   
   
6. these packages must be installed (versions may differ !!!):
   binutils-2.20.51.0.2-5.11.el6 (x86_64)
   compat-libcap1-1.10-1 (x86_64)
   compat-libstdc ++ - 33-3.2.3-69.el6 (x86_64)
   compat-libstdc ++ - 33-3.2.3-69.el6.i686
   gcc-4.4.4-13.el6 (x86_64)
   gcc-c ++ - 4.4.4-13.el6 (x86_64)
   glibc-2.12-1.7.el6 (i686)
   glibc-2.12-1.7.el6 (x86_64)
   glibc-devel-2.12-1.7.el6 (x86_64)
   glibc-devel-2.12-1.7.el6.i686
   ksh
   libgcc-4.4.4-13.el6 (i686)
   libgcc-4.4.4-13.el6 (x86_64)
   libstdc ++ - 4.4.4-13.el6 (x86_64)
   libstdc ++ - 4.4.4-13.el6.i686
   libstdc ++ - devel-4.4.4-13.el6 (x86_64)
   libstdc ++ - devel-4.4.4-13.el6.i686
   libaio-0.3.107-10.el6 (x86_64)
   libaio-0.3.107-10.el6.i686
   libaio-devel-0.3.107-10.el6 (x86_64)
   libaio-devel-0.3.107-10.el6.i686
   make-3.81-19.el6
   sysstat-9.0.4-11.el6 (x86_64)
   
   
7. install unixODBC and unixODBC-devel packages of both digits
   
   
8. Install and run the OS profile configuration daemon:
   # yum install tuned
   # chkconfig tuned on
   # tuned-adm profile enterprise-storage
   Taken from a Red Hat subscription file.
   
   
9. configure huge pages for ORACLE
   
   
   1. find the size of one page
      # grep Hugepagesize / proc / meminfo
      in my case it was 2048kB
      
      
   2. those. to create a 1GB page set, we need 512 pages:
      # echo '# Number of hugepages to use' >> /etc/sysctl.conf
      # echo vm.nr_hugepages = 512 >> /etc/sysctl.conf
      # echo >> /etc/sysctl.conf
      # sysctl -p
      
      
   3. since static 'huge pages' are fixed in memory and cannot be transferred to the swap users oracle and grid need the rights to use this memory (further for the case described in paragraph 2 above):
      # echo '# hugepages access by oracle user' >> /etc/security/limits.conf
      # echo 'oracle hard memlock 1048576' >> /etc/security/limits.conf
      # echo 'oracle soft memlock 1048576' >> /etc/security/limits.conf
      # echo >> /etc/security/limits.conf
      # echo '# huge pages access by grid user.' >> /etc/security/limits.conf
      # echo 'grid hard memlock 1048576' >> /etc/security/limits.conf
      # echo 'grid soft memlock 1048576' >> /etc/security/limits.conf
      # echo >> /etc/security/limits.conf
      
   
   
10. The following parameters are recommended for controlling the frequency of memory accesses:
    # echo 'This is where the virtual memory is reclaimed' >> /etc/sysctl.conf
    # echo vm.swappiness = 0 >> /etc/sysctl.conf
    # echo vm.dirty_background_ratio = 3 >> /etc/sysctl.conf
    # echo vm.dirty_ratio = 15 >> /etc/sysctl.conf
    # echo vm.dirty_expire_centisecs = 500 >> /etc/sysctl.conf
    # echo vm.dirty_writeback_centisecs = 100 >> /etc/sysctl.conf
    # echo >> /etc/sysctl.conf
    # sysctl -p
    
    
11. create a shell constraint for the grid user, similar to the oracle shell constraints created by the packages selected during installation
    # echo '# grid setting for nofile soft limit is 1024' >> /etc/security/limits.conf
    # echo 'grid soft nofile 1024' >> /etc/security/limits.conf
    # echo '# grid setting for nofile hard limit is 65536' >> /etc/security/limits.conf
    # echo 'grid hard nofile 65536' >> /etc/security/limits.conf
    # echo '# grid setting for nproc soft limit is 2047' >> /etc/security/limits.conf
    # echo 'grid soft nproc 2047' >> /etc/security/limits.conf
    # echo '# grid setting for nproc hard limit is 16384' >> /etc/security/limits.conf
    # echo 'grid hard nproc 16384' >> /etc/security/limits.conf
    # echo '# grid setting soft limit is 10240KB' >> /etc/security/limits.conf
    # echo 'grid soft stack 10240' >> /etc/security/limits.conf
    # echo 'grid setting # limit hard limit is 32768KB' >> /etc/security/limits.conf
    # echo 'grid hard stack 32768' >> /etc/security/limits.conf
    # echo >> /etc/security/limits.conf
    
    
12. optimize kernel parameters for the network
    # echo '# Additional network parameters' >> /etc/sysctl.conf
    # echo 'net.ipv4.tcp_wmem = 262144 262144 262144' >> /etc/sysctl.conf
    # echo 'net.ipv4.tcp_rmem = 4194304 4194304 4194304' >> /etc/sysctl.conf
    # echo >> /etc/sysctl.conf
    # sysctl -p
    
    
13. add a line to the /etc/pam.d/login file
    # echo 'session required pam_limits.so' >> /etc/pam.d/login
    
    
14. create a script defining shell parameters
    # touch /etc/profile.d/oraclegrid.sh
    # echo '#! / bin / bash'> /etc/profile.d/oraclegrid.sh
    # echo 'if [$ USER = "oracle"] || [$ USER = "grid"]; then '>> /etc/profile.d/oraclegrid.sh
    # echo 'if [$ SHELL = "/ bin / ksh"]; then '>> /etc/profile.d/oraclegrid.sh
    # echo 'ulimit -p 16384' >> /etc/profile.d/oraclegrid.sh
    # echo 'ulimit -n 65536' >> /etc/profile.d/oraclegrid.sh
    # echo 'else' >> /etc/profile.d/oraclegrid.sh
    # echo 'ulimit -u 16384 -n 65536' >> /etc/profile.d/oraclegrid.sh
    # echo 'fi' >> /etc/profile.d/oraclegrid.sh
    # echo 'umask 022' >> /etc/profile.d/oraclegrid.sh
    # echo 'fi' >> /etc/profile.d/oraclegrid.sh
    # chmod + x /etc/profile.d/oraclegrid.sh
    

Create folders:

1. Oracle inventory
   # mkdir -p / u01 / app / oraInventory
   # chown -R grid: oinstall / u01 / app / oraInventory
   # chmod -R 775 / u01 / app / oraInventory
   
   
2. Grid infrastructure home
   # mkdir -p /u01/11.2.0/grid
   # chown -R grid: oinstall /u01/11.2.0/grid
   # chmod -R 775 /u01/11.2.0/grid
   
   
3. Oracle Base Directory
   # mkdir -p / u01 / app / oracle
   # mkdir / u01 / app / oracle / cfgtoollogs
   # chown -R oracle: oinstall / u01 / app / oracle
   # chmod -R 775 / u01 / app / oracle
   
   
4. Oracle RDBMS Home
   # mkdir -p /u01/app/oracle/product/11.2.0/db_1
   # chown -R oracle: oinstall /u01/app/oracle/product/11.2.0/db_1
   # chmod -R 775 /u01/app/oracle/product/11.2.0/db_1
   

Let's duplicate the FQDN in the / etc / hosts file

With the general parameters of the systems all.

GRID setup

Installing Automatic Storage Management Library (ASM Lib) Driver.
The oracleasm package does not need to be installed, since it is included in the Oracle Linux kernel. We installed the oracleasm-support package during the OS installation, selecting packages that start with oracle * , if it is not installed, we can install it from the public repository . Therefore, it remains for us to install only oracleasmlib .
# yum -y install download.oracle.com/otn_software/asmlib/oracleasmlib-2.0.4-1.el6.x86_64.rpm

Customize ASMLib
# /etc/init.d/oracleasm configure
This will configure the on-boot properties of the Oracle ASM library.
driver. The following questions will determine whether the driver is
it will have. The current values
will be shown in brackets ('[]'). Hitting without typing an
answer will keep that current value. Ctrl-C will abort.
Default user to own driver interface []: grid
Default group to own driver interface []: asmadmin
Start Oracle ASM library driver on boot (y / n) [n]: y
Scan for Oracle ASM disks on boot (y / n) [y]:
Writing Oracle ASM library driver configuration: done
Initializing the Oracle ASMLib driver: [OK]
Scanning the system for Oracle ASMLib disks: [OK]

Let's create disks for ASM

1. determine the free disk space:
   # vgdisplay vg_oracleserver
   - Volume group - VG Name vg_oracleserver
   System id
   Format lvm2
   Metadata Areas 1
   Metadata Sequence No 4
   VG Access read / write
   VG Status resizable
   MAX LV 0
   Cur LV 3
   Open LV 3
   Max PV 0
   Cur PV 1
   Act PV 1
   VG Size 930,38 GiB
   PE Size 4.00 MiB
   Total PE 238177
   Alloc PE / Size 12544 / 49,00 GiB
   Free PE / Size 225633 / 881.38 GiB
   VG UUID LvgSW2-ZILO-KOZf-ZwAY-8WBB-9X2u-lzaWuv
   
   
2. disk sizes are determined individually. I left 80GB for Redo Logs, the rest of the space was divided equally between db files and FRA.
   # lvcreate -L81,37G -n lvasmredo vg_oracleserver
   # lvcreate -L400G -n lvasmfra vg_oracleserver
   # lvcreate -L400G -n lvasmdata vg_oracleserver
   
   

Create ASM disks
# oracleasm createdisk ASMDATA01 / dev / vg_oracleserver / lvasmdata
# oracleasm createdisk ASMFRA02 / dev / vg_oracleserver / lvasmfra
# oracleasm createdisk ASMREDO02 / dev / vg_oracleserver / lvasmredo

Check them out
# oracleasm listdisks
ASMDATA01
ASMFRA02
ASMREDO02
# ls -ltr / dev / oracleasm / disks
total 0
brw-rw ---- 1 grid asmadmin 252, 7 Nov 12 06:15 ASMDATA01
brw-rw ---- 1 grid asmadmin 252, Nov 8 12 06:15 ASMFRA02
brw-rw ---- 1 grid asmadmin 252, 6 Nov 12 06:16 ASMREDO02
# oracleasm-discover ORCL: *
Using ASMLib from /opt/oracle/extapi/64/asm/orcl/1/libasm.so
[ASM Library - Generic Linux, version 2.0.4 (KABI_V2)]
Discovered disk: ORCL: ASMDATA01 [838860800 blocks (429496729600 bytes), maxio 512]
Discovered disk: ORCL: ASMFRA02 [838860800 blocks (429496729600 bytes), maxio 512]
Discovered disk: ORCL: ASMREDO02 [170647552 blocks (87371546624 bytes), maxio 512]

Set the parameters of the user grid shell
# echo 'ORACLE_HOME = / u01 / 11.2.0 / grid' >> /home/grid/.bash_profile
# echo 'ORACLE_SID = + ASM' >> /home/grid/.bash_profile
# echo 'PATH = $ ORACLE_HOME / bin: $ PATH' >> /home/grid/.bash_profile
# echo 'export ORACLE_HOME' >> /home/grid/.bash_profile
# echo 'export ORACLE_SID' >> /home/grid/.bash_profile
# echo 'export PATH' >> /home/grid/.bash_profile

!!! IMPORTANT!!! The ORACLE GRID installer is most likely targeted at the SysV initialization system, while the 6th version of Enterprise Linux uses Upstart. Because of this, the installer, when attempting to initialize an OHASD daemon, generates an error and shuts down incorrectly. In this regard, it is necessary to create the following file before installation (use the date and name accordingly):
# touch /etc/init/ohasd.conf
# echo '#start init.ohasd'> /etc/init/ohasd.conf
# echo '# What: oracle high-availability watchdog' >> /etc/init/ohasd.conf
# echo '# When 12_11_2012' >> /etc/init/ohasd.conf
# echo 'Who: Arthur' >> /etc/init/ohasd.conf
# echo 'start on runlevel [35]' >> /etc/init/ohasd.conf
# echo 'stop on runlevel [016]' >> /etc/init/ohasd.conf
# echo 'respawn' >> /etc/init/ohasd.conf
# echo 'exec /etc/init.d/init.ohasd run> / dev / null 2> & 1 </ dev / null' >> /etc/init/ohasd.conf

!!! IMPORTANT!!! at some point, it will be necessary to manually start this daemon, so keep the second console open as root.

From our workstation, we go to e-delivery , log in, and agree to the rules. Select the product: “Oracle Database”, platform: “Linux x86-64”. In the label that appears, select “Oracle Database 11g Release 2 (in my case 11.2.0.1.0) Media Pack for Linux x86-64” and click the continue button. We choose to download “Oracle Database 11g Release 2 Grid Infrastructure (in my case 11.2.0.1.0) for Linux x86-64”.

Copy the downloaded file to the server in the grid user's home folder.
$ scp V17531-01.zip grid @ oracleserver: ~ /

Connect to the server under the grid account (we will use the now unloved X-server network transparency)
$ ssh -Y grid @ oracleserver

Enable access to X-applications from other computers
$ xhost +
you can at your discretion limit the nodes from which you can connect.

Unpack the archive
$ unzip V17531-01.zip

Go to the folder ~ / grid and run the installer
$ cd ~ / grid /
$ ./runInstaller
Starting Oracle Universal Installer ...

Checking Temp space: must be greater than 120 MB. Actual 955 MB Passed
Checking swap space: must be greater than 150 MB. Actual 16383 MB Passed
Checking monitor: must be configured to display at least 256 colors. Actual 16777216 Passed
Preparing to run Oracle Universal Installer from / tmp / OraInstall2012-11-12_06-30-47PM. Please wait ...

Next, the installation will go in graphics mode.

1. In the first window, select “installation and configuration of grid infrastructure for a single server”
   
   
   
2. in the second window, select English and Russian
   
   
   
3. In the third window, we select the disk for this one (reliability is ensured by RAID, so we select external)
   
   
   
4. create a password for users SYS and ASMSNMP
   
   
   
5. may complain about the quality of the password (here we decide to change the password or ignore it; the system may also react inadequately to a complex password)
   
   
   
6. select user groups
   
   
   
7. choose paths for database and grid files
   
   
   
8. choose a path for inventory
   
   
   
9. The installer will check the dependencies and swear.
   
   
   
10. but we will send it by ticking “Ignore All” for all dependencies we decided at the beginning of the installation
    
    
11. save the file responses. we can use it when installing Oracle without a graphical environment
    
    
    
12. Click the “Finish” button and observe the installation process until the next message opens.
    
    
    
13. open a new secure shell with the root user (we already have one, just after that 2 shells are opened with the root user and 1 under the grid user) and run the required scripts:
    # /u01/app/oraInventory/orainstRoot.sh
    Changing permissions of / u01 / app / oraInventory.
    Adding read, write permissions for group.
    Removing read, write, execute permissions for world.
    
    Changing groupname of / u01 / app / oraInventory to oinstall.
    The execution of the script is complete.
    
    # /u01/11.2.0/grid/root.sh
    Running Oracle 11g root.sh script ...
    
    The following environment variables are set as:
    ORACLE_OWNER = grid
    ORACLE_HOME = /u01/11.2.0/grid
    
    Enter the full pathname of the local bin directory: [/ usr / local / bin]:
    Copying dbhome to / usr / local / bin ...
    Copying oraenv to / usr / local / bin ...
    Copying coraenv to / usr / local / bin ...
    
    Creating / etc / oratab file ...
    Entries will be added to the / etc / oratab file as needed by
    Database Configuration Assistant when a database is created
    Finished running generic part of root.sh script.
    Now product-specific root actions will be performed.
    2012-11-12 21:11:43: Checking for super user privileges
    2012-11-12 21:11:43: User has super user privileges
    2012-11-12 21:11:43: Parsing the host name
    Using configuration parameter file: /u01/11.2.0/grid/crs/install/crsconfig_params
    Creating trace directory
    LOCAL ADD MODE
    Creating OCR keys for user 'grid', privgrp 'oinstall' ...
    Operation successful.
    CRS-4664: Node oracleserver successfully pinned.
    Adding daemon to inittab
    
    
14. At this moment, the execution of the script is stalled (point 3.h and 3.i), go to the second root session and execute
    # initctl start ohasd
    ohasd start / running, process 6933
    
    
15. script execution will continue
    CRS-4123: Oracle High Availability Services has been started.
    ohasd is starting
    ADVM / ACFS is not supported on oraclelinux-release-6Server-3.0.2.x86_64
    
    oracleserver 2012/11/12 21:18:34 /u01/11.2.0/grid/cdata/oracleserver/backup_20121112_211834.olr
    Successfully configured Oracle Grid Infrastructure for a Standalone Server
    Updating inventory properties for clusterware
    Starting Oracle Universal Installer ...
    
    Checking swap space: must be greater than 500 MB. Actual 16371 MB Passed
    The inventory pointer is located at /etc/oraInst.loc
    The inventory is located at / u01 / app / oraInventory
    'UpdateNodeList' was successful.
    
    
16. After this, go and click in the window “OK”
    
    
17. finita la comedy
    
    
    

Add the rest of the ASM disk groups.

1. in session with the grid user
   $ asmca
   
   
2. in the first window, select the button “create”
   
   
   
3. in the pop-up window, create a group FRA, external fault tolerance (using RAID), select the ASMFRA02 drive
   
   
   
4. do the same for REDO
   
   
   
5. as a result we get
   
   
   
6. For this, the GRID installation is complete.
   
   

Installing ORACLE DBMS

Set the shell options of the user oracle
# echo 'ORACLE_HOME = / u01 / app / oracle / product / 11.2.0 / db_1' >> /home/oracle/.bash_profile
# echo 'ORACLE_SID = LOC11' >> /home/oracle/.bash_profile
# echo 'PATH = $ ORACLE_HOME / bin: $ PATH' >> /home/oracle/.bash_profile
# echo 'export ORACLE_HOME' >> /home/oracle/.bash_profile
# echo 'export ORACLE_SID' >> /home/oracle/.bash_profile
# echo 'export PATH' >> /home/oracle/.bash_profile

From our workstation, we go to e-delivery , log in, and agree to the rules. Select the product: “Oracle Database”, platform: “Linux x86-64”. In the label that appears, select “Oracle Database 11g Release 2 (in my case 11.2.0.1.0) Media Pack for Linux x86-64” and click the continue button. We select download “Oracle Database 11g Release 2 (in my case 11.2.0.1.0) for Linux x86-64 (Part 1 of 2)” and “Oracle Database 11g Release 2 (in my case 11.2.0.1.0) for Linux x86 -64 (Part 2 of 2) ”.

Copy the downloaded file to the server in the home folder of the user oracle
$ scp V17530-01_ * oracle @ oracleserver: ~ /

Connect to the server under the oracle account (we will use the now unloved X-server network transparency)
$ ssh -Y oracle @ oracleserver

Enable access to X-applications from other computers
$ xhost +
you can at your discretion limit the nodes from which you can connect.

Unpack the archive
$ unzip V17530-01_1of2.zip
$ unzip V17530-01_2of2.zip

Go to the folder ~ / database and run the installer.
$ cd ~ / database /
$ ./runInstaller
Starting Oracle Universal Installer ...

Checking Temp space: must be greater than 120 MB. Actual 953 MB Passed
Checking swap space: must be greater than 150 MB. Actual 16383 MB Passed
Checking monitor: must be configured to display at least 256 colors. Actual 16777216 Passed
Preparing to run Oracle Universal Installer from / tmp / OraInstall2012-11-20_06-30-25PM. Please wait ...

Next, the installation is in graphical mode.

1. in the first window, we refuse to receive updates from those. Support Oracle (recommended software vendor)
   
   
   
2. We agree with the warning
   
   
   
3. in the second window we select only install the database software
   
   
   
4. in the third window choose the installation of a single database
   
   
   
5. in the fourth window choose languages
   
   
   
6. we are happy owners of the license for Oracle Standard Edition, so in the next window we select it
   
   
   
7. choose installation paths
   
   
   
8. we select user groups
   
   
   
9. ignore everything !!! (maybe take off)
   
   
   
10. It is recommended to save the answer file and run the installation.
    
    
    
11. what it looks like
    
    
    
12. you will need to run the script specified in the pop-up window
    
    
    # /u01/app/oracle/product/11.2.0/db_1/root.sh
    Running Oracle 11g root.sh script ...
    
    The following environment variables are set as:
    ORACLE_OWNER = oracle
    ORACLE_HOME = /u01/app/oracle/product/11.2.0/db_1
    
    Enter the full pathname of the local bin directory: [/ usr / local / bin]:
    The file "dbhome" already exists in / usr / local / bin. Overwrite it? (y / n)
    [n]:
    The file "oraenv" already exists in / usr / local / bin. Overwrite it? (y / n)
    [n]:
    The file "coraenv" already exists in / usr / local / bin. Overwrite it? (y / n)
    [n]:
    
    Entries will be added to the / etc / oratab file as needed by
    Database Configuration Assistant when a database is created
    Finished running generic part of root.sh script.
    Now product-specific root actions will be performed.
    Finished product-specific root actions.
    
    
13. Congratulations! You are the happy owner of ORACLE DBMS.
    
    
    

Creating a base

Before creating a database, you must:

1. check permissions for files and folders:
   
   1. Oracle inventory
      # chown -R grid: oinstall / u01 / app / oraInventory
      # chmod -R 775 / u01 / app / oraInventory
      
      
   2. Grid infrastructure home
      # chown -R grid: oinstall /u01/11.2.0/grid
      # chmod -R 775 /u01/11.2.0/grid
      
      
   3. Oracle Base Directory
      # chown -R oracle: oinstall / u01 / app / oracle
      # chmod -R 775 / u01 / app / oracle
      
      
   4. Oracle RDBMS Home
      # chown -R oracle: oinstall /u01/app/oracle/product/11.2.0/db_1
      # chmod -R 775 /u01/app/oracle/product/11.2.0/db_1
      
      
   
   
2. change access rights to
   # cd /u01/11.2.0/grid/bin/
   # chmod 6751 oracle
   # ls -l oracle
   -rwsr-s - x 1 grid oinstall 184285623 Nov 12 21:06 oracle
   
   # cd /u01/app/oracle/product/11.2.0/db_1/bin
   # chmod 6751 oracle
   # -l oracle
   -rwsr-s - x 1 oracle asmadmin 199650019 Nov 20 20:24 oracle
   

Connect to the server under the oracle account (we will use the now unloved X-server network transparency)
$ ssh -Y oracle @ oracleserver

Just in case, let's allow access to X-applications again.
$ xhost +
you can at your discretion limit the nodes from which you can connect.

Starting database configuration
$ dbca

Further we act according to the instruction which is applied on your software. From this stage, you can not fear mistakes, at any time you can remove the "broken" base and create a new one.

Thanks for attention!