Oracle 12C Installation

Installation step by step for Oracle 12C

(01)
Dowload the sotware from the links.
edelivery Oracle Site: Oracle Database 12c Release 1 (12.1.0.1) Software (64-bit)

(02)

unzip linuxamd64_12c_database_1of2.zip
unzip linuxamd64_12c_database_2of2.zip

(03)

Oracle Installation Prerequisites
Automatic Setup
# # The following package is currently available on the public Yum.
# yum install oracle-validated -y
# yum update

(04)if Oracle validate package performs than ok otherwsie put thse value in /etc/sysctl.conf file.
fs.file-max = 6815744
kernel.sem = 250 32000 100 128
kernel.shmmni = 4096
kernel.shmall = 1073741824
kernel.shmmax = 4398046511104
net.core.rmem_default = 262144
net.core.rmem_max = 4194304
net.core.wmem_default = 262144
net.core.wmem_max = 1048576
fs.aio-max-nr = 1048576
net.ipv4.ip_local_port_range = 9000 65500

and run the /sbin/sysctl -p and modify the /etc/security/limits.conf file by below values.

oracle   soft   nofile    1024
oracle   hard   nofile    65536
oracle   soft   nproc    2047
oracle   hard   nproc    16384
oracle   soft   stack    10240
oracle   hard   stack    32768

(05) Verfiy below packages if not availble than install.

# From Public Yum or ULN
yum install binutils -y
yum install compat-libstdc++-33 -y
yum install compat-libstdc++-33.i386 -y
yum install gcc -y
yum install gcc-c++ -y
yum install glibc -y
yum install glibc.i686 -y
yum install glibc-devel -y
yum install glibc-devel.i386 -y
yum install ksh -y
yum install libaio -y
yum install libaio.i386 -y
yum install libaio-devel -y
yum install libaio-devel.i386 -y
yum install libgcc -y
yum install libgcc.i686 -y
yum install libstdc++ -y
yum install libstdc++.i386 -y
yum install libstdc++-devel -y
yum install libstdc++-devel.i386 -y
yum install libXext -y
yum install libXext.i386 -y
yum install libXtst -y
yum install libXtst.i386 -y
yum install libX11 -y
yum install libX11.i386 -y
yum install libXau -y
yum install libXau.i386 -y
#yum install libxcb -y
#yum install libxcb.i386 -y
yum install libXi -y
yum install libXi.i386 -y
yum install make -y
yum install sysstat -y
yum install unixODBC -y
yum install unixODBC-devel -y

(06)Create the new groups and users.

groupadd -g 54321 oinstall
groupadd -g 54322 dba
groupadd -g 54323 oper
#groupadd -g 54324 backupdba
#groupadd -g 54325 dgdba
#groupadd -g 54326 kmdba
#groupadd -g 54327 asmdba
#groupadd -g 54328 asmoper
#groupadd -g 54329 asmadmin

useradd -u 54321 -g oinstall -G dba,oper oracle
passwd oracle


(07)Set secure Linux to permissive by editing the "/etc/selinux/config" file, making sure the SELINUX flag is set as follows.
    SELINUX=permissive
(08)Once the change is complete, restart the server or run the following command.
    # setenforce Permissive

(09)If you have the Linux firewall enabled, you will need to disable or configure it,o disable it, do the following.
    # service iptables stop
    # chkconfig iptables off
(10)Create the directories in which the Oracle software will be installed
    Example
    mkdir -p /u01/app/oracle/product/12.1.0/db_1
    chown -R oracle:oinstall /u01
    chmod -R 775 /u01

(11)Add the following lines at the end of the "/home/oracle/.bash_profile" file.

   # Oracle Settings
export TMP=/tmp
export TMPDIR=$TMP

export ORACLE_HOSTNAME=ol5-121.localdomain
export ORACLE_UNQNAME=cdb12c
export ORACLE_BASE=/u01/app/oracle
export ORACLE_HOME=$ORACLE_BASE/product/12.1.0/db_1
export ORACLE_SID=cdb12c

export PATH=/usr/sbin:$PATH
export PATH=$ORACLE_HOME/bin:$PATH

export LD_LIBRARY_PATH=$ORACLE_HOME/lib:/lib:/usr/lib
export CLASSPATH=$ORACLE_HOME/jlib:$ORACLE_HOME/rdbms/jlib

(12) Set Display.

(13) Run installer

   ./runInstaller

(14) update oratab as per requirement

Edit the "/etc/oratab" file setting the restart flag for each instance to 'Y'.

Comments

Post a Comment

Popular posts from this blog

Key points on Read-Only Instance and Read-Only Database

 In Oracle, both Read-Only Instance and Read-Only Database provide mechanisms to limit data modifications, but they are used in different contexts and for different purposes. Here's a comparison: 1. Read-Only Instance Definition : A read-only instance is a configuration in Oracle Real Application Clusters (RAC) where one or more instances of a multi-instance database are set up to operate in read-only mode. This is typically done in environments with high concurrency for both read and write operations. Key Features : Allows real-time query scaling by dedicating specific instances to read-only operations. Write operations are not allowed on the designated read-only instance, but other instances in the cluster can still handle write operations. Useful in RAC configurations for load balancing , where read workloads can be distributed across multiple read-only instances. Instance-specific: The database remains fully functional (read-write) when accessed through other instances. Us...
Read more

Steps to create database link between Oracle database and SQL Server

 Creating a database link between SQL Server and Oracle allows seamless data exchange between the two systems. Here’s a step-by-step guide: Step 1: Install the Required Drivers Install Oracle Database Gateway for SQL Server (ODG4MS). This acts as a bridge between Oracle and SQL Server. Ensure the Oracle Client is installed on the Oracle database server or the server acting as the gateway. Step 2: Configure the Oracle Database Gateway Locate Configuration Files: Navigate to the $ORACLE_HOME/network/admin directory on the Oracle Gateway server. Edit tnsnames.ora: Add an entry for the database link pointing to the SQL Server database: dg4msql =   (DESCRIPTION =     (ADDRESS = (PROTOCOL = TCP)(HOST = <SQL_SERVER_HOSTNAME>)(PORT = 1521))     (CONNECT_DATA = (SID = dg4msql))     (HS=OK)  -- Required for heterogeneous services   )   Edit listener.ora: Update the Oracle listener configuration to recognize the gateway: SID_LIST_LISTENE...
Read more

How to Configure Logging for EM 12c Management Agent

The goal of this article is to provide instruction on how to enable logging for the Enterprise Manager 12c Management Agent.. ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- The logging properties for the agent are stored in $EMSTATE/sysman/config/emd.properties file, same as in 11.1. But the properties that control logging follow the log4j configuration syntax instead of the syntax supported by the 11.1 agent. To active changes to the logging parameters, you can use either of the emctl commands: emctl reload agent emctl setproperty agent Overview Agent logging entries look similar to the standard log4j logging, with the only significant difference being the prefix 'Logger.' that you will see on each line. For example: # logging properties Logger.log4j.appender.Rolling=org.apache.log4j.RollingFileAppender Logger.lo...
Read more