Skip to main content

Oracle Database 19c Step by Step Installation On Oracle Linux 7.6

This post describes the installation of Oracle Database 19c 64-bit on Oracle Linux 7.6  x86-64 bit. The Linux server needs a minimum of 3G swap and secure Linux set to permissive. An example of this type of Linux installation can be seen here.

Download Software

Download the Oracle software from oracle edelivery.

Oracle Installation Prerequisites

Automatic Setup

Use the "oracle-database-preinstall-19c" package to perform all your prerequisite setup.
# yum install -y oracle-database-preinstall-19c
If you are using RHEL7 or CentOS7, you can pick up the PRM from the OL7 repository and install it. It will pull the dependencies from your normal repositories.
# yum install -y https://yum.oracle.com/repo/OracleLinux/OL7/latest/x86_64/getPackage/oracle-database-preinstall-19c-1.0-1.el7.x86_64.rpm

Hosts File

Set a fully qualified name for the server in the "/etc/hosts" file.
< IP-address >  < fully-qualified-machine-name >  < machine-name >
# vi /etc/hosts

Set the correct hostname in the "/etc/hostname" file.
# vi /etc/hostname
arandy.cm
NB!! Make sure you can ping the hostname you added in the host file.

Additional Setup

Set the password for the "oracle" user.
# passwd oracle
Set secure Linux to permissive by editing the "/etc/selinux/config" file. 
# vi /etc/selinux/config
SELINUX=permissive

Once the change is complete, run the following command.
# setenforce Permissive
Disable the Linux firewall.
# systemctl stop firewalld
# systemctl disable firewalld
Create the directories in which the Oracle software will be installed.
mkdir -p /u01/app/oracle/product/19.3.0/dbhome_1
mkdir -p /u02/oradata
chown -R oracle:oinstall /u01 /u02
chmod -R 775 /u01 /u02
Reboot the server and login in with the oracle user using the password that we set above. 
Hope you haven’t forgotten your password if you have don’t worry just log in as the root user and reset the password again with passwd command.
# reboot

 Set Environment variables.

Add the following environment variables in the .bash_profile file.
$ vi .bash_profile
# Oracle Settings
export TMP=/tmp
export TMPDIR=$TMP

export ORACLE_HOSTNAME=arandy.cm
export ORACLE_UNQNAME=cdb1
export ORACLE_BASE=/u01/app/oracle
export ORACLE_HOME=$ORACLE_BASE/product/19.3.0/dbhome_1
export ORA_INVENTORY=/u01/app/oraInventory
export ORACLE_SID=cdb1
export PDB_NAME=pdb1
export DATA_DIR=/u02/oradata

export PATH=/usr/sbin:/usr/local/bin:$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
$ . .bash_profile

Unzip the File 

Switch to the ORACLE_HOME directory and unzip the software directly into this path.
Please note that after you must have downloaded the installation file you have to transfer them into the VM. This can be done with Filezilla or by using the scp command in the terminal.
$ cd $ORACLE_HOME
$ unzip -oq /home/oracle/LINUX.X64_193000_db_home.zip

Run the Installer

Log into the oracle user, start the Oracle Universal Installer (OUI) by issuing the following command and follow the GUI guided steps
$ cd $ORACLE_HOME
$ ./runInstaller
Select the install option Set Up Software Only and click Next:
Select the install option Single Instance database installation and click Next:
Select the install option Enterprise Edition and click Next:
 Click Next.

 Click Next.
 Click Next.
 Click Next.
 Click Next.
Make sure all Prerequisite Checks Succeeded.
Click Install.
Run the root scripts when prompted.

As a root user, execute the following script(s):
# /u01/app/oraInventory/orainstRoot.sh
# /u01/app/oracle/product/19.0.0/dbhome_1/root.sh
Click Close.

You are now ready to create a database.

Database Creation

You create a database using the Database Configuration Assistant (DBCA). The interactive mode will display GUI screens to allow user input.

After successfully installing the database software, start the listener:
# Start the listener
$ lsnrctl start
To create the database using the interactive mode, start the Database Configuration Assistance (dbca) by issuing the following command and follow the GUI guided steps
# Interactive mode.
$ dbca
Click Next.

Typical configuration:
Global database name: cdb1
Storage type: File System
Database file location: /u02/oradata
Fast Recovery Area (FRA): {ORACLE_BASE}/fast_recovery_area/{DB_UNIQUE_NAME}
Database character set: AL32UTF8
Adminitrative password: SysOracle_47   
Pluggable database name: pdb1
Click Next.
Click Finish.
Database Summary.

Database creation finish.

Once the Database 19c successfully created, validate the database using the following command.
$ sqlplus / as sysdba
SQL> select banner_full from v$version;
SQL> select instance_name,status from v$instance;
SQL> select con_id, name, open_mode from v$pdbs;

Hope this helps!!

Caution: Any information or materials on this blog is provided for educational purposes only. It has been tested internally, however, we do not guarantee that it will work for you. Ensure that you run it in your test environment before using.

Thanks,
randyDBA { serving to discover }















Comments

  1. Thanks Devi. Please check out my other posts.

    ReplyDelete
  2. This comment has been removed by the author.

    ReplyDelete
  3. SP2-0667: Message file sp1.msb not found
    SP2-0750: You may need to set ORACLE_HOME to your Oracle software directory
    this error occured how to fix this

    ReplyDelete
  4. Awesome article, it was exceptionally helpful! I simply began in this and I'm becoming more acquainted with it better! Cheers, keep doing awesome! Fresh SMTP Shop Buy Inbox Mailer

    ReplyDelete
  5. If Java Development is a field that you're dreaming of, then we, Infycle, are with you to make your dream into reality. Infycle Technologies offers the best Java Training in Chennai, with various highly demanded software courses such as Big Data, AWS, Python, Hadoop, AWS, etc., in 100% practical training with specialized tutors in the field. Along with that, the pre-interviews will be given for the candidates to face the interviews with complete knowledge. To know more, dial 7502633633 for more.Java Course in Chennai | Infycle Technologies

    ReplyDelete
  6. Thanks for sharing this blog. This very important and informative blog
    RHCE Certification Training online

    ReplyDelete
  7. Hello Every body,
    i followed this method but when i creating database using DBCA , it stuck at 36% and not going forward. Kindly give me a solution.
    BR
    Imtiaz Ali

    ReplyDelete
  8. The root cause analysis (RCA) aims to discover the root causes of problems in order to identify appropriate solutions. In Rbelieves proactively preventing and solving underlying issues is more effective than e analysis can be performed with a collection of principles, techniques, and methodologies that can all be leveraged to identify the root causes of an event or trend. Looking beyond superficial cause and effect, RCA can show where processes or systems failed or caused an issue in the first place.Root cause analysis

    ReplyDelete

Post a Comment

Popular posts from this blog

How to Delete Old Trace & Dump files with ADRCI

The ADRCI command interpreter has multiple features:- Create a package with incident or problem information for Oracle Support Analyze diagnostic data within the Automatic Diagnostic Repository (ADR) Run health checks In this post, we'll be concentrating on deleting the old diagnostic files with ADRCI. Set your environment and run the ADRCI utility: $ adrci Use the following command to list the ADR homes: adrci> show home ADR Homes: diag/rdbms/db11g/DB11G diag/tnslsnr/sol10/listener Choose the ADR home from the list above: adrci> set home diag/rdbms/db11g/DB11G Check the current retention policy: adrci> show control Check the following columns in the output: LONGP_POLICY:- It is set to 365 days by default. It is responsible for Incidents and Health Monitor warnings. SHORTP_POLICY:- It is set to 30 days by default. It manages the trace and core dump files. Use the following commands to change the retention policy: Specify the time in hours: 10 Days = 240 ...

Oracle Database 12C Error Codes, Solutions and Suggestions from ORA-19700 to ORA-20000

Oracle 12C Error Codes, Solutions and Suggestions from ORA 19700 to ORA 20000 ORA-19700: device type exceeds maximum length of string Cause:  The device type indicated is invalid. Action:  Supply a correct device type and retry the allocation. ORA-19701: device name exceeds maximum length of  string Cause:  The device name indicated is invalid. Action:  Supply a correct device name and retry the allocation. ORA-19702: device parameter exceeds maximum length of  string ORA-19703: device command string exceeds maximum length of  string Cause:  The device command string exceeds maximum length. Action:  Correct the command and retry the operation. ORA-19704: file name exceeds maximum length of  string Cause:  The specified file name, which was a parameter to a copy, backup, or restore operation, exceeds the maximum file name length for this operating system. Action:  Retry the operation with a s...