Configuration Details:
Database: Oracle DB 18.0.0.0 EE 64 Bit
Operating System: Oracle Enterprise Linux 7.1 64 Bit
Single Instance/RAC: Single Instance
Pluggable(PDB/CDB): No
Points to be checked before starting installation prerequisites:
1) Am I downloading Oracle DB software of correct version?
2) Is my database certified on current Operating System ?
3) Is database software architecture 32 bit or 64 bit ?
4) Is Operating System architecture 32 bit or 64 bit ?
5) Are Database and Operating System from same architecture ?
6) Is Operating System Kernel Version compatible with Oracle Database version to be installed ?
7) Oracle Database is supported on ext2, ext3 and ext4 file systems.
8) Is current kernel version supported ? It is observed that there are hang issues in RHEL-7 with many CPU cores and more RAM, due to NUMA was enabled. As a work around it is recommended to turn off NUMA. It is not mandatory to Install Oracle UEK Kernel on RHEL, Oracle highly recommends deploying the Oracle Unbreakable Enterprise Kernel in your Linux environment, especially if you run enterprise applications. However, using Oracle Unbreakable Enterprise Kernel is optional.
- Oracle Linux 7 with the Unbreakable Enterprise Kernel 3: 3.8.13-35.3.1.el7uek.x86_64 or later
- Oracle Linux 7.2 with the Unbreakable Enterprise Kernel 4: 4.1.12-32.2.3.el7uek.x86_64 or later
- Oracle Linux 7 with the Red Hat Compatible kernel: 3.10.0-123.el7.x86_64 or later
- Red Hat Enterprise Linux 7: 3.10.0-123.el7.x86_64 or later
9) Minimum Configuration Required for installation(You can add more resources later as per requirement):
- RAM - 2 GB or more
- CPU - 1 or more
- /oracle - 20 GB
- /tmp - 1 GB
RAM | Swap Space |
Between 1 GB and 2 GB | 1.5 times the size of RAM |
Between 2 GB and 16 GB | Equal to the size of RAM |
More than 16 GB | 16 GB |
10) Storage Checklist for Oracle Database:
At least 7.5 GB for Oracle Database Enterprise Edition.
At least 7.5 GB for Oracle Database Standard Edition 2.
11) Server should be started in runlevel 3 or runlevel 5.
[oracle@myblog ~]$ who -r
run-level 5 2022-06-06 10:50
12)Ensure minimum 2 GB RAM is free on server.
[oracle@myblog ~]$ cat /proc/meminfo | grep Mem
MemTotal: 4793400 kB
MemFree: 3584864 kB
13)Ensure minimum 20 GB Hard Disk space is free on server for software installation (Disk space for Oracle Software is based on the Oracle Database edition).
[oracle@myblog ~]$ df -PTh /u01
Filesystem Type Size Used Avail Use% Mounted on
/dev/mapper/ol-root xfs 47G 18G 30G 38% /
Step 1: Download Virtual Box Software and configure virtual environment.
Go to google and type "Download virtual box for windows 64 bit".
You can refer the previous post link "https://rupeshanantghubade.blogspot.com/2021/07/oracle-database-12.html" to know how to download virtual box for Windows machine.
Step 2: VDI Machine configuration
Here, we will create new virtual machine considering we have downloaded virtual box.
Step 3: Linux Installation
Start the VDI machine and proceed with Linux OS installation.
Here, add IP address for server and make below changes in network settings.
Step 4: Server Readiness for Oracle Software installation.
Add host name entry in "/etc/hosts" file as below and check ping response.
[oracle@myblog ~]$ cat /etc/selinux/config
# This file controls the state of SELinux on the system.
# SELINUX= can take one of these three values:
# enforcing - SELinux security policy is enforced.
# permissive - SELinux prints warnings instead of enforcing.
# disabled - No SELinux policy is loaded.
#SELINUX=enforcing
SELINUX=disabled
# SELINUXTYPE= can take one of these two values:
# targeted - Targeted processes are protected,
# mls - Multi Level Security protection.
SELINUXTYPE=targeted
#systemctl status firewalld
#systemctl stop firewalld
#systemctl disable firewalld
#systemctl status firewalld
Create below directories and user/groups.
#mkdir -p /u01/app/oracle/product/18.0.0/dbhome_1
#mkdir -p /u01/app/oraInventory
Note: No need to create full Oracle Home path since Installer will automatically create that.
Create inventory location and owner of the inventory should be primary group i.e. oinstall. Oracle will automatically assign oinstall and read-write permissions to this directory post installation by root.sh script.
[root@myblog u01]# chown -R oracle:oinstall /u01
[root@myblog u01]# chmod -R 755 /u01
Group Creation:
#groupadd oinstall
#groupadd dba
User Creation and primary (oinstall) and secondary (dba) group assignment:
You can create user and assign primary & secondary group in one command OR you can use two different commands to create user and assign primary & secondary group.
#useradd -g oinstall -G dba oracle
#passwd oracle
OR
#useradd oracle
#usermod -g oinstall -G dba oracle
#passwd oracle
[root@myblog u01]# ls -ld /u01/app/oracle/product/18.0.0/dbhome_1/
drwxr-xr-x. 2 oracle oinstall 6 Jan 11 10:21 /u01/app/oracle/product/18.0.0/dbhome_1/
Ensure kernel and limits parameters set correctly on server.
# vi /etc/sysctl.conf
fs.file-max = 6815744
kernel.sem = 250 32000 100 128
kernel.shmmni = 4096
kernel.shmall = 1073741824
kernel.shmmax = 4398046511104
kernel.panic_on_oops = 1
net.core.rmem_default = 262144
net.core.rmem_max = 4194304
net.core.wmem_default = 262144
net.core.wmem_max = 1048576
net.ipv4.conf.all.rp_filter = 2
net.ipv4.conf.default.rp_filter = 2
fs.aio-max-nr = 1048576
net.ipv4.ip_local_port_range = 9000 65500
#sysctl -p
vi /etc/security/limits.conf
oracle soft nofile 1024
oracle hard nofile 65536
oracle soft nproc 16384
oracle hard nproc 16384
oracle soft stack 10240
oracle hard stack 32768
oracle hard memlock 134217728
oracle soft memlock 134217728
The following packages (or later versions) must be installed before installation:
- bc
- binutils-2.23.52.0.1-12.el7.x86_64
- compat-libcap1-1.10-3.el7.x86_64
- compat-libstdc++-33-3.2.3-71.el7.i686
- compat-libstdc++-33-3.2.3-71.el7.x86_64
- fontconfig-devel-2.10.95-7.el7.x86_64
- ksh
- libX11-1.6.0-2.1.el7.i686
- libX11-1.6.0-2.1.el7.x86_64
- libXau-1.0.8-2.1.el7.i686
- libXau-1.0.8-2.1.el7.x86_64
- libXi-1.7.2-1.el7.i686
- libXi-1.7.2-1.el7.x86_64
- libXtst-1.2.2-1.el7.i686
- libXtst-1.2.2-1.el7.x86_64
- libXrender-devel-0.9.10-1.el7.i686
- libXrender-devel-0.9.10-1.el7.x86_64
- libXrender-0.9.10-1.el7.i686
- libXrender-0.9.10-1.el7.x86_64
- libgcc-4.8.2-3.el7.i686
- libgcc-4.8.2-3.el7.x86_64
- libstdc++-4.8.2-3.el7.i686
- libstdc++-4.8.2-3.el7.x86_64
- libstdc++-devel-4.8.2-3.el7.i686
- libstdc++-devel-4.8.2-3.el7.x86_64
- libxcb-1.9-5.el7.i686
- libxcb-1.9-5.el7.x86_64
- make-3.82-19.el7.x86_64 make-3.82-19.el7.x86_64
- nfs-utils-1.3.0-0.21.el7.x86_64
- smartmontools-6.2-4.el7.x86_64
- sysstat-10.1.5-1.el7.x86_64
Download Oracle Database Gold Image 18.0.0.0 Software for Linux 86_64 bit from Oracle Edelivery Site https://edelivery.oracle.com/ and upload it on target server. (Refer the steps (https://rupeshanantghubade.blogspot.com/2021/07/oracle-database-12.html) to download software from Edelivery site.
Copy the setup file to target server in ORACLE_HOME location and unzip the setup and start runInstaller by oracle user.
In older versions up to 12cR2, oracle home files are part of "database" directory and OUI copies software files to ORACLE_HOME location during installation, but starting from Oracle 18c (Gold Image Setup), if you unzip the setup then you will get directly installed home. Hence, you have to copy setup file directory to ORACLE_HOME location.
Here, setup file name is Oracle_18_DB.zip. I have renamed it manually.
[root@myblog RAC Setup]# cd Oracle\ 18c/
[root@myblog Oracle 18c]# pwd
/media/sf_Software/RAC Setup/Oracle 18c
[root@myblog Oracle 18c]# ls -ltr
total 4457668
-rwxrwx--- 1 root vboxsf 4564649047 May 22 2022 Oracle_18_DB.zip
[root@myblog Oracle 18c]# cp -pr Oracle_18_DB.zip /u01/app/oracle/product/18.0.0/dbhome_1/
[root@myblog Oracle 18c]# cd /u01/app/oracle/product/18.0.0/dbhome_1/
[root@myblog dbhome_1]$ ls -ltr
total 4457668
-rwxrwx--- 1 root vboxsf 4564649047 May 22 2022 Oracle_18_DB.zip
[root@myblog dbhome_1]# chown oracle:oinstall Oracle_18_DB.zip
[root@myblog dbhome_1]# chmod 755 Oracle_18_DB.zip
[root@myblog dbhome_1]# su - oracle
Last login: Tue Jan 11 10:33:06 IST 2022 on :0
[oracle@myblog ~]$ id
uid=1001(oracle) gid=1001(oinstall) groups=1001(oinstall),1002(dba)
[oracle@myblog ~]$ cd /u01/app/oracle/product/18.0.0/dbhome_1/
[oracle@myblog dbhome_1]$ ls -ltr
total 4457668
-rwxr-xr-x 1 oracle oinstall 4564649047 May 22 2022 Oracle_18_DB.zip
[oracle@myblog dbhome_1]$ unzip Oracle_18_DB.zip
...
...
precomp/public/ORACA.COB -> oraca.cob
precomp/public/SQLCA.COB -> sqlca.cob
javavm/admin/classes.bin -> ../../javavm/jdk/jdk8/admin/classes.bin
javavm/admin/libjtcjt.so -> ../../javavm/jdk/jdk8/admin/libjtcjt.so
javavm/admin/lfclasses.bin -> ../../javavm/jdk/jdk8/admin/lfclasses.bin
javavm/lib/security/cacerts -> ../../../javavm/jdk/jdk8/lib/security/cacerts
javavm/lib/sunjce_provider.jar -> ../../javavm/jdk/jdk8/lib/sunjce_provider.jar
javavm/lib/security/java.security -> ../../../javavm/jdk/jdk8/lib/security/java.security
javavm/lib/security/local_policy.jar -> ../../../javavm/jdk/jdk8/lib/security/local_policy.jar
javavm/lib/security/US_export_policy.jar -> ../../../javavm/jdk/jdk8/lib/security/US_export_policy.jar
[oracle@myblog dbhome_1]$
[oracle@myblog dbhome_1]$ pwd
/u01/app/oracle/product/18.0.0/dbhome_1
Here, you can see all binaries are part of ORACLE_HOME location.
[oracle@myblog dbhome_1]$ ls -ltr
total 4457760
-rw-r--r-- 1 oracle oinstall 852 Aug 18 2015 env.ora
-rw-r--r-- 1 oracle oinstall 2927 Oct 14 2016 schagent.conf
-rwxr-x--- 1 oracle oinstall 1783 Mar 8 2017 runInstaller
drwxr-x--- 7 oracle oinstall 64 Feb 8 2018 xdk
drwxr-xr-x 3 oracle oinstall 18 Feb 8 2018 wwg
drwxr-xr-x 4 oracle oinstall 29 Feb 8 2018 usm
drwxr-xr-x 5 oracle oinstall 42 Feb 8 2018 suptools
drwxr-xr-x 6 oracle oinstall 50 Feb 8 2018 srvm
drwxr-xr-x 3 oracle oinstall 16 Feb 8 2018 sqlj
drwxr-xr-x 3 oracle oinstall 17 Feb 8 2018 slax
-rw-r----- 1 oracle oinstall 10 Feb 8 2018 root.sh.old.1
drwxr-xr-x 3 oracle oinstall 20 Feb 8 2018 relnotes
drwxr-xr-x 4 oracle oinstall 27 Feb 8 2018 racg
drwxr-xr-x 5 oracle oinstall 49 Feb 8 2018 R
drwxr-xr-x 4 oracle oinstall 31 Feb 8 2018 owm
drwxr-xr-x 3 oracle oinstall 18 Feb 8 2018 oss
drwxr-xr-x 3 oracle oinstall 18 Feb 8 2018 ordim
drwxr-xr-x 4 oracle oinstall 32 Feb 8 2018 oracore
drwxr-xr-x 5 oracle oinstall 39 Feb 8 2018 olap
drwxr-xr-x 4 oracle oinstall 29 Feb 8 2018 mgw
drwxr-xr-x 2 oracle oinstall 6 Feb 8 2018 log
drwxr-xr-x 3 oracle oinstall 17 Feb 8 2018 has
drwxr-xr-x 3 oracle oinstall 18 Feb 8 2018 dv
drwxr-xr-x 3 oracle oinstall 19 Feb 8 2018 diagnostics
drwxr-xr-x 3 oracle oinstall 18 Feb 8 2018 dbjava
drwxr-xr-x 3 oracle oinstall 19 Feb 8 2018 data
drwxr-xr-x 3 oracle oinstall 17 Feb 8 2018 css
drwxr-xr-x 6 oracle oinstall 73 Feb 8 2018 plsql
drwxr-xr-x 2 oracle oinstall 21 Feb 8 2018 dbs
drwxr-xr-x 2 oracle oinstall 32 Feb 8 2018 utl
drwxr-xr-x 2 oracle oinstall 28 Feb 8 2018 instantclient
drwxr-xr-x 13 oracle oinstall 4096 Feb 8 2018 dmu
drwxr-xr-x 3 oracle oinstall 33 Feb 8 2018 ucp
drwxr-xr-x 3 oracle oinstall 33 Feb 8 2018 jdbc
drwxr-xr-x 2 oracle oinstall 25 Feb 8 2018 QOpatch
drwxr-xr-x 4 oracle oinstall 63 Feb 8 2018 ords
drwxr-xr-x 5 oracle oinstall 111 Feb 8 2018 sdk
drwxr-xr-x 6 oracle oinstall 4096 Feb 8 2018 apex
drwxr-xr-x 22 oracle oinstall 4096 Feb 8 2018 sqldeveloper
drwxr-xr-x 8 oracle oinstall 94 Feb 8 2018 odbc
drwxr-xr-x 11 oracle oinstall 110 Feb 8 2018 ctx
-rwx------ 1 oracle oinstall 786 Feb 8 2018 root.sh.old
drwxr-x--- 14 oracle oinstall 4096 Jun 4 2018 OPatch
drwxr-xr-x 6 oracle oinstall 49 Jul 18 2018 sqlplus
-rwx------ 1 oracle oinstall 638 Jul 18 2018 root.sh
drwxr-xr-x 2 oracle oinstall 4096 Jul 18 2018 jlib
drwxr-xr-x 5 oracle oinstall 145 Jul 18 2018 sqlpatch
drwxr-xr-x 7 oracle oinstall 4096 Jul 18 2018 jdk
drwxr-xr-x 13 oracle oinstall 129 Jul 18 2018 rdbms
drwxr-xr-x 6 oracle oinstall 52 Jul 18 2018 precomp
drwxr-xr-x 5 oracle oinstall 36 Jul 18 2018 perl
drwxr-xr-x 7 oracle oinstall 59 Jul 18 2018 ord
drwxr-xr-x 7 oracle oinstall 60 Jul 18 2018 opmn
drwxr-xr-x 5 oracle oinstall 43 Jul 18 2018 nls
drwxr-xr-x 10 oracle oinstall 98 Jul 18 2018 network
drwxr-xr-x 9 oracle oinstall 91 Jul 18 2018 md
drwxr-xr-x 10 oracle oinstall 104 Jul 18 2018 ldap
drwxr-xr-x 8 oracle oinstall 76 Jul 18 2018 javavm
drwxr-xr-x 5 oracle oinstall 38 Jul 18 2018 hs
drwxr-xr-x 4 oracle oinstall 28 Jul 18 2018 drdaas
drwxr-xr-x 3 oracle oinstall 19 Jul 18 2018 demo
drwxr-xr-x 7 oracle oinstall 66 Jul 18 2018 cv
drwxr-xr-x 6 oracle oinstall 51 Jul 18 2018 crs
drwxr-xr-x 9 oracle oinstall 86 Jul 18 2018 assistants
drwxr-xr-x 8 oracle oinstall 4096 Jul 18 2018 oui
drwxr-xr-x 3 oracle oinstall 12288 Jul 18 2018 lib
drwxr-x--- 13 oracle oinstall 4096 Jul 18 2018 inventory
drwxr-xr-x 5 oracle oinstall 4096 Jul 18 2018 deinstall
drwxr-xr-x 4 oracle oinstall 83 Jul 18 2018 clone
drwxr-xr-x 2 oracle oinstall 8192 Jul 18 2018 bin
drwxr-xr-x 2 oracle oinstall 98 Jul 18 2018 addnode
drwxr-xr-x 10 oracle oinstall 4096 Jul 18 2018 install
-rwxr-xr-x 1 oracle oinstall 4564649047 May 22 2022 Oracle_18_DB.zip
If unzip is done then you can remove setup file to release the space.
[oracle@myblog dbhome_1]$ rm -rf Oracle_18_DB.zip
[oracle@myblog dbhome_1]$ cd ..
[oracle@myblog 18.0.0]$ du -sh *
8.8G dbhome_1
[oracle@myblog 18.0.0]$
Step 5: Oracle Software Installation and configuration
Select Configuration Options:
- Create and configure a single instance database - Choose this option to create a new single instance database along with sample schemas.
- Set Up Software only - Choose this option to install only the database binaries. To configure the database, you must run Oracle Database Configuration Assistant after the software installation.
- Desktop Class - Choose this if you are installing on a laptop or a desktop class system which includes a starter database and allows minimal configuration. This option is designed for those who wish to get up and running with the database quickly.
- Server Class - Choose this option if you are installing on a server class system, such as for deploying Oracle in a production data center which allows more advanced configuration options which includes Oracle RAC, Automatic Storage Management, backup and recovery configuration, integration with Enterprise Manager Cloud Control, and more fine-grained memory tuning, among many others.
- Typical Install - This method is selected by default. It lets you quickly install Oracle Database using minimal input. It installs the software and optionally creates a general-purpose database using the information that you specify in this dialog.
- Advanced Install - Choose this if you want to perform more complex installations, such as creating individual passwords for different accounts, creating specific types of starter databases (for example, for transaction processing or data warehouse systems), using different language groups, specifying e-mail notifications, and so on.
- Enterprise Edition - This type is designed for enterprise-level applications. It is engineered for mission-critical, high-security online transaction processing (OLTP) and data warehousing environments. If you select this installation type, then all separately licensable Enterprise Edition options are installed.
- Standard Edition 2 - This installation type is designed for department or workgroup-level applications and for small and medium-sized enterprises (SMEs). It is engineered to provide core relational database management services and options. It installs an integrated set of management tools, full distribution, replication, web features, and facilities for building business-critical applications.
Ensure that the Oracle Inventory home path contains only ASCII characters. At the time of this release, the use of non-ASCII characters for an Oracle Inventory is not supported.
- General Purpose/Transaction Processing - Select this configuration type to create a preconfigured database suitable for a variety of uses, from simple transactions run by large numbers of concurrent users to complex queries. This configuration provides support for the following types of uses:
- Rapid access to data by many concurrent users, typical of transaction processing environments
- Long-running queries of complex historical data by a small number of users, typical of decision support systems (DSS)
- High availability and transaction processing performance
- High-volume recoverability
- Data Warehousing - Select this configuration type to create a preconfigured database that is suitable for running complex queries about specific subjects. Data warehouse databases are typically used to store the historical data required to answer strategic business questions on topics such as customer orders, support calls, sales force prospects, and customer purchasing patterns. This configuration provides optimal support for database environments with the following requirements:
- Rapid access to large volumes of data
- Support for online analytical processing (OLAP)
Specify Database Identifiers:
- Global database name - It is the name given to a database to uniquely identify it from the other databases in a network. The Global Database Name is composed of a database unique name (db_unique_name), a delimiter (a period), and a database domain name (db_domain). It is represented as: db_unique_name.db_domain.
- db_unique_name is the name of the database. It can contain a maximum of 30 characters, if the first eight characters are unique and begin with an alphabetic character. The characters can include alphanumeric, underscore (_), dollar sign ($), and pound sign (#).
- db_domain is the computer environment used for the database. It can contain a maximum of 128 characters. The characters can include alphanumeric, underscore (_), pound sign (#), and periods (.).
Ensure that the combination of the database name (first eight unique characters of database unique name), delimiter, and the database domain name does not exceed 128 characters.
For example: db_unique_name is orcl and domain_name is test.com then global_db_name will be orcl.test.com
- Oracle System Identifier - It is a unique name for an Oracle database instance on a specific host. The Oracle System Identifier (SID) helps in identifying the control file, and locating the files required to open the database. When you enter the Global Database Name, Oracle Universal Installer automatically populates the Oracle System Identifier field with the database name. You can change this name in Advanced installation. Oracle Univeral Installer limits the SID to 12 alphanumeric characters for single instance databases. For Oracle RAC databases, the SID prefix, which is the first eight characters of the SID, must be a unique name for each database. The SID cannot contain an underscore (_), dollar sign ( $), or pound sign (#).
Select the Create as Container database option to create the database as a container database (CDB) that can support one or more pluggable databases (PDBs). If you want Oracle Universal Installer to create a PDB when it creates the CDB, then specify the PDB name in the Pluggable Database Name field.
- Memory - Specify the amount of physical memory (RAM) that you want to allocate for the database. Oracle Universal Installer computes and displays a default value for the memory allocation in the Allocated Memory spin box and adjusts the slider bar accordingly. The values of the slide bar and spin box are also limited to the minimum and maximum values according to the available physical memory. You can use the slider bar or the spin box to specify a value (MB) for the amount of memory that you want to allocate for the database according to the requirements of the database.
The following is the ratio of the memory distribution according to the database types:
General Purpose/Transaction Processing:
- SGA Target: 75%
- PGA Aggregate Target: 25%
Percentage: The percentage text displays the percentage of the available physical memory that you have allocated for the database.
Character Sets - This option enables you to select the character set used to store and process character data in the database. The choices are:
- Use Unicode (AL32UTF8) - The database character set is AL32UTF8 and the database can process most languages of the world.
- Use OS character set (WE8MSWN1252) - The database character set (WE8MSWN1252) is based on the language of the operating system.
- Sample Schemas - Specify if you want to include the sample schemas in the database. Oracle provides sample schemas for use with product and documentation examples. If you choose to install the sample schemas, then Oracle Database Configuration Assistant creates the EXAMPLES tablespace in the database, which requires 150 MB of disk space.
Oracle recommends that you change the default path chosen by Oracle Universal Installer. If the ORACLE_BASE environment variable is defined when you start Oracle Universal Installer, then the default directory path is $ORACLE_BASE/oradata. If the ORACLE_BASE environment variable is not defined, but you have write permissions in the parent directory of the Oracle home directory, then the default directory path is oracle_home_parent_dir/oradata, where oracle_home_parent_dir is the path to the parent directory of the Oracle home directory that you specify. In all other cases, the default directory path is oracle_home/oradata, where oracle_home is path to the Oracle home directory that you specify.
- File System - Select this option if you want to store the database files on a file system. For Oracle Real Application Clusters (Oracle RAC) installations, the file system that you choose must be a cluster file system. Alternatively, it must be on a certified network attached storage (NAS) device. The file system that contains the directory must have at least 1.2 GB of free disk space. Additional disk space is required for production databases, depending on the amount of data that you plan to store.
- Oracle Automatic Storage Management - Select this option if you installed Grid Infrastructure and you want to store the database files in an Oracle Automatic Storage Management disk group. Oracle Automatic Storage Management disk groups are created by specifying one or more disk devices that will be managed by a separate Oracle Automatic Storage Management instance.
- Recovery Options - Select Enable Recovery to enable recovery using one of the following options:
- Select File System to use a file system directory for the fast recovery area, and then specify the fast recovery area path in the Recovery Area location field.
- Select Oracle Automatic Storage Management to use an Automatic Storage Management disk group for the fast recovery area.
Note: As a general guideline, the space available for the fast recovery area should be twice the size of the database.To improve performance and to ensure that a single point of failure does not cause you to lose data, Oracle recommends that you select a separate file system for the fast recovery area. Select a file system that is separate from the operating system, Oracle software, and database files.
The PDBADMIN account is optional. This option is available when you configure a configure a multitenant container database, and a pluggable database.
To provide better security, Oracle strongly recommends that you specify different passwords for each account. These accounts are the privileged database accounts. You must remember the passwords that you specify for each account.
Minimum Password Requirements:
- Passwords cannot exceed 30 characters.
- Passwords cannot contain special characters: ! @ % ^ & * ( ) + = \ | ` ~ [ { ] } ; : ' " , < > ?
- User names cannot be the same character string as a password.
- You cannot leave a password field empty.
- The SYS account password cannot be change_on_install. (case-insensitive)
- The SYSTEM account password cannot be manager. (case-insensitive)
- The PDBADMIN account password cannot be pdbadmin. (case-insensitive)
Password Recommendations:
- Contains at least one lowercase letter.
- Contains at least one uppercase letter.
- Contains at least one digit.
- Is at least 8 characters in length.
- Uses the same database character set, which can include the underscore (_), dollar ($), and pound sign (#) characters.
- Should not be an actual word.
Privileged Operating System Groups:
- The OSDBA group (typically, dba) - You must create this group the first time you install Oracle Database software on the system. This group identifies operating system user accounts that have the database administrative privileges (the SYSDBA privilege). The name used for this group in Oracle code examples is dba.
- The OSOPER group for Oracle Database (typically, oper) - This is an optional group. Create this group if you want a separate group of operating system users to have a limited set of database administrative privileges (the SYSOPER privilege). This group cannot directly connect as SYSOPER, unless explicitly granted. However, they have the privileges granted by the SYSOPER privilege. By default, members of the OSDBA group have all privileges granted by the SYSOPER privilege. The name used for this group in Oracle code examples is oper.
- The OSBACKUPDBA group for Oracle Database (typically, backupdba) - Create this group if you want a separate group of operating system users to have a limited set of database backup and recovery related administrative privileges (the SYSBACKUP privilege). The usual name for this group is backupdba.
- The OSDGDBA group for Oracle Data Guard (typically, dgdba) - Create this group if you want a separate group of operating system users to have a limited set of privileges to administer and monitor Oracle Data Guard (the SYSDG privilege). The usual name for this group is dgdba.
- The OSKMDBA group for encryption key management (typically, kmdba) - Create this group if you want a separate group of operating system users to have a limited set of privileges for encryption key management such as Oracle Wallet Manager management (the SYSKM privilege). The usual name for this group is kmdba.
- The OSRACDBA group for Oracle Real Application Cluster Administration (typically, racdba) - Create this group if you want a separate group of operating system users to have a limited set of Oracle Real Application Cluster administrative privileges (the SYSRAC privilege). The usual name for this group is racdba.
The below section presents a summary of the options you selected during the installation process.
- Global Settings
- Disk space
- Oracle Service User (Microsoft Windows Operating Systems Only)
- Source location
- Install method
- Database edition
- Oracle base
- Software location
- Privileged Operating System Groups
- Database Information
- Configuration
- Global database name
- Oracle system identifier (SID)
- Allocated memory
- Automatic memory management option
- Database character set
- Database storage mechanism
- Database file location
- Automated backup
Click Save Response File if you want to save all the installation steps into a response file.
Click Install.
Below screen will be appeared. Try to resolve errors if any.
You will get below pop-up box to run below two scripts by root user:
- /u01/app/oraInventory/orainstRoot.sh
- /u01/app/oracle/product/18.0.0/dbhome_1/root.sh
Open new terminal as root user and run above two scripts.
[root@myblog ~]# /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.
[root@myblog ~]#
[root@myblog ~]# /u01/app/oracle/product/18.0.0/dbhome_1/root.sh
Performing root user operation.
The following environment variables are set as:
ORACLE_OWNER= oracle
ORACLE_HOME= /u01/app/oracle/product/18.0.0/dbhome_1
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 script.
Now product-specific root actions will be performed.
Do you want to setup Oracle Trace File Analyzer (TFA) now ? yes|[no] :
no
Oracle Trace File Analyzer (TFA - Non Daemon Mode) is available at :
/u01/app/oracle/product/18.0.0/dbhome_1/suptools/tfa/release/tfa_home/bin/tfactl
Note :
1. tfactl will use TFA Daemon Mode if TFA already running in Daemon Mode and user has access to TFA
2. tfactl will configure TFA Non Daemon Mode only if user has no access to TFA Daemon mode or TFA Daemon mode is not installed
OR
Oracle Trace File Analyzer (TFA - Daemon Mode) can be installed by running this script :
/u01/app/oracle/product/18.0.0/dbhome_1/suptools/tfa/release/tfa_home/install/roottfa.sh
[root@myblog ~]#
-------
Thanks !
Please comment if you like this post !
Very useful 👍
ReplyDelete