AdnanDBA: ORACLE

Showing posts with label ORACLE. Show all posts

Oracle Database 12c Release 1 (12.1) Installation On Oracle Linux 6

This article describes the installation of Oracle Database 12c Release 1 (12.1) (64-bit) on Oracle Linux 6 (64-bit). The article is based on a server installation with a minimum of 2G swap, with SELinux set to permissive and the firewall disabled. The following package groups were included for this installation.

Base System > Base
Base System > Compatibility libraries
Base System > Hardware monitoring utilities
Base System > Large Systems Performance
Base System > Network file system client
Base System > Performance Tools
Base System > Perl Support
Servers > Server Platform
Servers > System administration tools
Desktops > Desktop
Desktops > Desktop Platform
Desktops > Fonts
Desktops > General Purpose Desktop
Desktops > Graphical Administration Tools
Desktops > Input Methods
Desktops > X Window System
Applications > Internet Browser
Development > Additional Development
Development > Development Tools

An example of this type of Linux installations can be seen here. Alternative installations may require more packages to be loaded, in addition to the ones listed below.

Download Software

Download the Oracle software from OTN or MOS depending on your support status.

This article has been updated for the 12.1.0.2 release, but the installation is essentially unchanged since 12.1.0.1. Any variations specific for 12.1.0.1 will be noted.

Depending on your version of VirtualBox and Oracle Linux, there may be some slight variation in how the screen shots look.

Unpack Files

Unzip the files.

unzip linuxamd64_12102_database_1of2.zip
unzip linuxamd64_12102_database_2of2.zip

You should now have a single directory called "database" containing installation files.

Hosts File

The "/etc/hosts" file must contain a fully qualified name for the server.

<IP-address>  <fully-qualified-machine-name>  <machine-name>

For example.

127.0.0.1       localhost.localdomain  localhost
192.168.0.210   ol6-121.localdomain    ol6-121

Oracle Installation Prerequisites

Perform either the Automatic Setup or the Manual Setup to complete the basic prerequisites. The Additional Setup is required for all installations.

Automatic Setup

If you plan to use the "oracle-rdbms-server-12cR1-preinstall" package to perform all your prerequisite setup, issue the following command.

# yum install oracle-rdbms-server-12cR1-preinstall -y

Earlier versions of Oracle Linux required manual setup of the Yum repository by following the instructions at http://public-yum.oracle.com.

It is probably worth doing a full update as well, but this is not strictly speaking necessary.

# yum update

Manual Setup

If you have not used the "oracle-rdbms-server-12cR1-preinstall" package to perform all prerequisites, you will need to manually perform the following setup tasks.

Add or amend the following lines in the "/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

Run the following command to change the current kernel parameters.

/sbin/sysctl -p

Add the following lines to the "/etc/security/limits.conf" file.

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

Install the following packages if they are not already present.

# From Public Yum or ULN
yum install binutils -y
yum install compat-libcap1 -y
yum install compat-libstdc++-33 -y
yum install compat-libstdc++-33.i686 -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.i686 -y
yum install ksh -y
yum install libgcc -y
yum install libgcc.i686 -y
yum install libstdc++ -y
yum install libstdc++.i686 -y
yum install libstdc++-devel -y
yum install libstdc++-devel.i686 -y
yum install libaio -y
yum install libaio.i686 -y
yum install libaio-devel -y
yum install libaio-devel.i686 -y
yum install libXext -y
yum install libXext.i686 -y
yum install libXtst -y
yum install libXtst.i686 -y
yum install libX11 -y
yum install libX11.i686 -y
yum install libXau -y
yum install libXau.i686 -y
yum install libxcb -y
yum install libxcb.i686 -y
yum install libXi -y
yum install libXi.i686 -y
yum install make -y
yum install sysstat -y
yum install unixODBC -y
yum install unixODBC-devel -y

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

Uncomment the extra groups you require.

Additional Setup

The following steps must be performed, whether you did the manual or automatic setup.

Set the password for the "oracle" user.

passwd oracle

Amend the "/etc/security/limits.d/90-nproc.conf" file as described below. See MOS Note [ID 1487773.1]

# Change this
*          soft    nproc    1024

# To this
* - nproc 16384

Set secure Linux to permissive by editing the "/etc/selinux/config" file, making sure the SELINUX flag is set as follows.

SELINUX=permissive

Once the change is complete, restart the server or run the following command.

# setenforce Permissive

If you have the Linux firewall enabled, you will need to disable or configure it, as shown here or here. To disable it, do the following.

# service iptables stop
# chkconfig iptables off

Create the directories in which the Oracle software will be installed.

mkdir -p /u01/app/oracle/product/12.1.0.2/db_1
chown -R oracle:oinstall /u01
chmod -R 775 /u01

Putting mount points directly under root is typically a bad idea. It's done here for simplicity, but for a real installation "/" should be reserved for the OS.

Unless you are working from the console, or using SSH tunnelling, login as root and issue the following command.

xhost +<machine-name>

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=ol6-121.localdomain
export ORACLE_UNQNAME=cdb1
export ORACLE_BASE=/u01/app/oracle
export ORACLE_HOME=$ORACLE_BASE/product/12.1.0.2/db_1
export ORACLE_SID=cdb1

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

Installation

Log into the oracle user. If you are using X emulation then set the DISPLAY environmental variable.

DISPLAY=<machine-name>:0.0; export DISPLAY

Start the Oracle Universal Installer (OUI) by issuing the following command in the database directory.

./runInstaller

Proceed with the installation of your choice.

If you are doing an installation for an Enterprise Manager repository, remember to do an advanced installation and pick the ALT32UTF8 character set.

You can see the type of installation I performed by clicking on the links below to see screen shots of each stage.

The "Database Configuration Assistant Complete" screen displays the Database Express 12c URL, which will be something like "https://ol6-121.localdomain:5500/em".

Post Installation

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

cdb1:/u01/app/oracle/product/12.1.0.2/db_1:Y

If Database Express 12c is not working, check the XMLDB HTTP port. If it is 0, set it to the port you want to use.

SQL> SELECT dbms_xdb_config.gethttpsport FROM dual;

GETHTTPSPORT
------------
        5500

SQL> EXEC dbms_xdb_config.sethttpsport(5500);

PL/SQL procedure successfully completed.

SQL>

Common Errors

"error code 35" : The machine name in the "/etc/hosts" file is not correct. It needs an entry for the loopback adapter (localhost) and the machine name. If you are using DNS for name resolution, you still need the loopback adapter reference in this file.
"error code 37" : The DNS not working properly. You may also get this error is the "/etc/hosts" file is not configured correctly.
"sqlplus: error while loading shared libraries: libclntsh.so.12.1" : The prerequisites have not been met. Work through them again. Specifically, make sure the "gcc" package has been installed.
Listener fails to start - Typically this is due to incorrect name resolution. Make sure the "/etc/hosts" and/or DNS is configured correctly.
Linking errors - Almost always due to missing prerequisites. Review the setup sections.

How to force log switch on every 15 minutes (ARCHIVE_LAG_TARGET)

For performance reason It is preferred that redo switches should not be less than 15 minutes .So we must resize our redo logs optimally (for detail look Redo logs sizing advisory article

When we plan our redo logs for peak hours.while off peak-hours the redo switch does not occur for hours .This situation has some risk

In a case of catastrophic hardware failure, we may lose our current redo log having a enormous long redo data.There is no way to recover transactions that are sitting in the current redo log .

Standby and Primary database may not be close synchronous If you use MAXIMUM AVAILABILITY

so It will be better to switch log for each specified interval.ARCHIVE_LAG_TARGET parameter simply forces a log switch at a specified interval, and that can be very useful.

In order to set 15 minutes (900 seconds )

ALTER SYSTEM SET ARCHIVE_LAG_TARGET = 900 SCOPE=BOTH;

CHANGING A DATABASE NAME USING NEWID

You will need to change the database name and the DBID internally. Oracle has a utility for this, the NEWID application.

This document will detail the steps required to perform the database name change using NEWID.

Database Name : OMS112

New Database Name : OMSREP

Overview of Process

There are four steps to perform to change an Oracle database name (SID).

Preliminary prep work
Use NID application
Change SID References
Start database and finalize changes

1. PRELIMINARY PREP WORK

Once the database name change, changes will need to be made to the Oracle parameter file. If the database is using an server parameter file (SPFILE) instead of a parameter file (PFILE), you will need to convert from a SPFILE to a PFILE before the database name change occurs.

1.1 Determining if SPFILE is in Use

Run the following query to see if your database was started with a PFILE or SPFILE:

SQL> sho parameter spfile

NAME TYPE VALUE

------------------------------------ ----------- ------------------------------

spfile string /u01/app/oracle/product/12.1.0

.2/dbhome_1/dbs/spfileOMS112.ora

If the database starts with a PFILE, no further prep work is necessary and you can proceed to step 2 – Use NID application. Otherwise, continue with the next step.

1.2 Creating a PFILE from SPFILE

Run the following sql to create a PFILE from an SPFILE:

Figure 1.2 Creating a PFILE from SPFILE.

Run the following query to see if your database was started with a PFILE or SPFILE:

SQL> create pfile from spfile;

File created.

Figure 1.3 Copying the old PFILE to its new name

[oracle@xxxxx ~]$ cd /u01/app/oracle/product/12.1.0.2/dbhome_1/dbs

[oracle@xxxxx dbs]$ ll

total 20

-rw-rw----. 1 oracle oinstall 1544 May 2 23:05 hc_OMS112.dat

-rw-r-----. 1 oracle oinstall 1271 May 2 23:48 initOMS112.ora

-rw-r--r--. 1 oracle oinstall 2992 Feb 3 2012 init.ora

-rw-r-----. 1 oracle oinstall 24 May 2 22:31 lkOMS112

-rw-r-----. 1 oracle oinstall 3584 May 2 23:05 spfileOMS112.ora

[oracle@xxxxx dbs]$ cp initOMS112.ora initOMSREP.ora

2. USE NID APPLICATION

To use the NID application, you will need to log into the database server as the oracle user and perform the following steps.

Shutdown the database
Start the database in mount mode
Run the NID command
Shut the database down

2.1 Shutdown the Database

[oracle@xxxxxxx dbs]$ sqlplus / as sysdba

SQL*Plus: Release 12.1.0.2.0 Production on Tue May 2 23:56:16 2017

Connected to:

Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production

With the Partitioning, OLAP, Advanced Analytics and Real Application Testing options

SQL> shutdown immediate;

Database closed.

Database dismounted.

ORACLE instance shut down.

SQL> startup mount

ORACLE instance started.

Total System Global Area 4294967296 bytes

Fixed Size 2932632 bytes

Variable Size 2466250856 bytes

Database Buffers 1811939328 bytes

Redo Buffers 13844480 bytes

Database mounted.

SQL> exit

Disconnected from Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production

With the Partitioning, OLAP, Advanced Analytics and Real Application Testing options

[oracle@xxxxxxx dbs]$ nid target=sys dbname=OMSREP

DBNEWID: Release 12.1.0.2.0 - Production on Wed May 3 00:03:32 2017

Password:

Connected to database OMS112 (DBID=187475667)

Connected to server version 12.1.0

Control Files in database:

/u02/oradata/OMS112/OMS112/control01.ctl

/u02/oradata/OMS112/OMS112/control02.ctl

Change database ID and database name OMS112 to OMSREP? (Y/[N]) => Y

Proceeding with operation

Changing database ID from 187475667 to 4204721757

Changing database name from OMS112 to OMSREP

Control File /u02/oradata/OMS112/OMS112/control01.ctl - modified

Control File /u02/oradata/OMS112/OMS112/control02.ctl - modified

Datafile /u02/oradata/OMS112/OMS112/system01.db - dbid changed, wrote new name

Datafile /u02/oradata/OMS112/OMS112/sysaux01.db - dbid changed, wrote new name

Datafile /u02/oradata/OMS112/OMS112/undotbs01.db - dbid changed, wrote new name

Datafile /u02/oradata/OMS112/OMS112/users01.db - dbid changed, wrote new name

Datafile /u02/oradata/OMS112/OMS112/mgmt_ecm_depot1.db - dbid changed, wrote new name

Datafile /u02/oradata/OMS112/OMS112/mgmt.db - dbid changed, wrote new name

Datafile /u02/oradata/OMS112/OMS112/mgmt_deepdive.db - dbid changed, wrote new name

Datafile /u02/oradata/OMS112/OMS112/audi - dbid changed, wrote new name

Datafile /u02/oradata/OMS112/OMS112/temp01.db - dbid changed, wrote new name

Control File /u02/oradata/OMS112/OMS112/control01.ctl - dbid changed, wrote new name

Control File /u02/oradata/OMS112/OMS112/control02.ctl - dbid changed, wrote new name

Instance shut down

Database name changed to OMSREP.

Modify parameter file and generate a new password file before restarting.

Database ID for database OMSREP changed to 4204721757.

All previous backups and archived redo logs for this database are unusable.

Database is not aware of previous backups and archived logs in Recovery Area.

Database has been shutdown, open database with RESETLOGS option.

Succesfully changed database name and ID.

DBNEWID - Completed succesfully.

Output from NID program showing a successful completion.

3. CHANGE SID REFERENCES

Changes will need to be made in the database parameter, tnsnames, oratab, and environment files to reflect the change of the database SID.

Oracle parameter file needs to be renamed and edited.
Oratab needs to have the SID renamed.
ora file needs the SID renamed
If the ORACLE_SID is set in the profile, it will need to be changed.

3.1 Oracle parameter file needs to be renamed and edited

The Oracle parameter file will need to be edited and have two lines changed. Change to where the parameter file is stored, the $ORACLE_HOME/dbs folder.

[oracle@xxxxx dbs]$ vi initOMSREP.ora

*.db_name='OMSREP'

*.db_recovery_file_dest='/u03/fast_recovery_area'

*.db_recovery_file_dest_size=19587399680

*.db_unique_name='OMSREP'

*.diagnostic_dest='/u01/app/oracle'

3.2 Oratab needs to have the SID renamed

Edit the file and change the old SID entry to the new SID. stored, the $ORACLE_HOME/dbs folder.

# This file is used by ORACLE utilities. It is created by root.sh

# and updated by either Database Configuration Assistant while creating

# a database or ASM Configuration Assistant while creating ASM instance.

# A colon, ':', is used as the field terminator. A new line terminates

# the entry. Lines beginning with a pound sign, '#', are comments.

# Entries are of the form:

# $ORACLE_SID:$ORACLE_HOME:<N|Y>:

# The first and second fields are the system identifier and home

# directory of the database respectively. The third filed indicates

# to the dbstart utility that the database should , "Y", or should not,

# "N", be brought up at system boot time.

# Multiple entries with the same $ORACLE_SID are not allowed.

OMSREP:/u01/app/oracle/product/12.1.0.2/dbhome_1:Y

Example ORATAB file showing changed SID reference from dwprd to dwqa. The changed value is in bold.

3.3 TNSNAMES needs to have the SID renamed

TNSNAMES is located in the folder $ORACLE_HOME/network/admin. Edit the file and change the old SID entry to the new SID, and change the HOST address to match the new system. See Figure 3.3.1 for an example.

stored, the $ORACLE_HOME/dbs folder.

[oracle@xxxxx dbs]$ vi /u01/app/oracle/product/12.1.0.2/dbhome_1/network/admin/tnsnames.ora

OMSREP =

(DESCRIPTION =

(ADDRESS = (PROTOCOL = TCP)(HOST = FCISCOPRDOEM.fcicanada.com)(PORT = 1521))

(CONNECT_DATA =

(SERVER = DEDICATED)

(SERVICE_NAME = OMS112.fcicanada.com)

)

LISTENER_OMSREP =

(ADDRESS = (PROTOCOL = TCP)(HOST = FCISCOPRDOEM.fcicanada.com)(PORT = 1521))

4. START DATABASE AND FINALIZE CHANGES

SQL> startup nomount pfile='/u01/app/oracle/product/12.1.0.2/dbhome_1/dbs/initOMSREP.ora';

ORACLE instance started.

Total System Global Area 4294967296 bytes

Fixed Size 2932632 bytes

Variable Size 2466250856 bytes

Database Buffers 1811939328 bytes

Redo Buffers 13844480 bytes

SQL> create spfile from pfile;

File created.

SQL> shutdown immediate;

ORA-01507: database not mounted

ORACLE instance shut down.

SQL> startup mount;

ORACLE instance started.

Total System Global Area 4294967296 bytes

Fixed Size 2932632 bytes

Variable Size 2466250856 bytes

Database Buffers 1811939328 bytes

Redo Buffers 13844480 bytes

Database mounted.

SQL> select name from v$database;

NAME

---------

OMSREP

SQL> alter database open resetlogs;

Database altered.