How to configure 12C ASM for a
Standalone Server
This toturial I am going to demo how to install oracle 12c ASM for a
standalone server
New ASM Features for Oracle
Database 12c:-
Oracle Database version 12c has been
released, which means a brand new version of ASM is out! Notable new features
are Flex ASM, proactive data validation and better handling of disk management
operations. Let's have an overview with more details in separate posts.
Oracle Flex ASM:-
Oracle Flex ASM is a set of new
features that provide critical capabilities required for cloud computing.
Oracle Flex ASM redefines the traditional ASM cluster architecture of having
one ASM instance on every node in the cluster; this means you can have less ASM
instances than nodes in your cluster. In this configuration the number of ASM
instances running is called ASM cardinality, by default the ASM cardinality is
3 and can be changed with a Clusterware command.
What are the benefits of Flex ASM?
On the traditional architecture
when an ASM instance fails; all DB instances connected to that instance in the
node will also fail. With Oracle Flex ASM if the ASM instance fail the
Clusterware will relocate that ASM instance to a different node and the DB
instances will remotely (through private network) connect to the relocated ASM
instance, all without disruption to the DB client.
Dedicated ASM Network
This new 12c feature provides the
option to dedicate a private network for ASM network traffic only. There’s also
the option to use the Oracle Clusterware interconnect private network.
Remote Access
As per the new Oracle Flex ASM
feature, the DB instance can remotely connect to ASM instance hence the need of
a password file in order to authenticate remote DB instances to ASM. Oracle
Flex ASM has the ability of storing password files in a Disk Group and is
extended to DB clients; this is really useful to avoid synchronizing multiple
password files within the cluster.
Other Flex ASM
Features
Other important
features of Oracle Flex ASM include;
The maximum number of
ASM Disk Group is increased from 63 to 511.
Oracle Flex ASM
supports larger LUN sizes for Oracle Database 12c clients (increased to 32 PB).
There is now a command
for renaming an ASM Disk in a Disk Group.
All the instances in
an ASM cluster ensure they are running the same code release by validating the
patch level across the cluster.
Install Required Linux
Packages for Oracle:-
Create Groups and User for Oracle Grid
& Database Software:-
If necessary, update the resource limits in the
/etc/security/limits.conf configuration file for the Oracle installation owner
by adding the following lines.
Add the following line to the /etc/pam.d/login file, if it does not already exist.
Depending on your shell environment, make the
following changes to the default shell startup file in order to change ulimit
settings for the Oracle installation owner.
For the Bourne, Bash, or Korn shell, add the
following lines to the /etc/profile file.
For the C shell (csh or tcsh), add the following
lines to the /etc/csh.login file.
Kernel Parameters
The kernel parameters presented in this section are
only recommended values as documented by Oracle. For production database
systems, Oracle recommends that you tune these values to optimize the
performance of the system.
Verify that the kernel parameters described in this
section are set to values greater than or equal to the recommended values. Also
note that when setting the four semaphore values that all four values need to
be entered on one line.
Oracle Database 12C Release 1 for Linux requires
the kernel parameter settings shown below. The values given are minimums, so if
your system uses a larger value, do not change it.
Configure Disks for Oracle ASM:-
Partition Oracle ASM Disks - (Optional)
Before using a hard disk as a physical volume for
Oracle ASM, decide whether the entire disk will be used (/dev/sdd) and
(/dev/sde) or a disk partition (/dev/sdd1) or (/dev/sde1). In this guide, two
unformatted hard disks were earmarked to be Oracle ASM disks. Given that there
is no information on these disks, it doesn't matter if you use the entire disk
or whether to create a partition on each hard disk.
For the purpose of this guide, I decided to create
a single partition on each hard disk.
Raw Device Setup
This step is only necessary if you want ASM to
access the disks as raw devices.
Edit the "/etc/sysconfig/rawdevices"
file, adding the following lines.
/dev/raw/raw1 /dev/sdd1
/dev/raw/raw2 /dev/sde1
Restart the rawdevices
service using the following command.
service rawdevices
restart
Run the following
commands and add them the "/etc/rc.local" file.
chown oracle:oinstall
/dev/raw/raw1
chown oracle:oinstall
/dev/raw/raw2
chmod 600
/dev/raw/raw1
chmod 600
/dev/raw/raw2
Pre-Installation
Tasks:-
If you decide to run
the CVU, configure user equivalence for the oracle user account and run
runcluvfy.sh stage -pre hacfg to verify that the server meets the installation
requirements for Oracle Restart.
Install Oracle Grid
Infrastructure for a Standalone Server:-
Post-installation
Tasks for Oracle Grid Infrastructure for a Standalone Server
After the installation
of Oracle Grid Infrastructure for a Standalone Server, use the SRVCTL and
CRSCTL commands to verify the Oracle Restart configuration.
Note that the Create
ASM Disk Group wizard only allows for the configuration of one disk group.
Using this wizard, create an Oracle ASM disk group that will be used for
database files. A second Oracle ASM disk group will be created for the recovery
files (Fast Recovery Area) later in this guide using the Oracle Automatic
Storage Management Configuration Assistant (Oracle ASMCA).
For database installation,
Please refer this link ->
Database Creation :-
Hope
it helps. Please stay tuned, add me to your G+ Circles!! Your feedback always
helps me and motivates me to blog more, please leave your valuable comment that
is always a pleasure to read.
Many
Thanks,
Regards
Senthilkumar
Devaraj
