Scribd
Upload
50 views

Asm 2

RBAL coordinates rebalancing activity and opens disks for diskgroups. ARBn moves extents while adding or removing disks. ASMB communicates between RDBMS and ASM instances. ASM is an instance without a database that has background processes like ARBn, RBAL, ASMB, GMON, MARK to manage storage. Tools to manage ASM configuration include asmca, asmcmd.

Uploaded by

Naveen Vachipalli
Copyright
© © All Rights Reserved
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
50 views

Asm 2

RBAL coordinates rebalancing activity and opens disks for diskgroups. ARBn moves extents while adding or removing disks. ASMB communicates between RDBMS and ASM instances. ASM is an instance without a database that has background processes like ARBn, RBAL, ASMB, GMON, MARK to manage storage. Tools to manage ASM configuration include asmca, asmcmd.

Uploaded by

Naveen Vachipalli
Copyright
© © All Rights Reserved
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
You are on page 1/ 5

while startup.

Never start all the nodes at a time.


Once started , will take some time to bring up all cluster
resources on every node.

CRS-4535: Cannot communicate with Cluster Ready Services


interconnectivity
SSA
permissions on files /u01

Never change the permissions on binaries


once installed.

ls -ltr /u01/app/11.2.0/grid/bin/oracle

ASM -
is an instance with out database.
connected with /as sysasm
using grid home

Verify on every node. ..


$ps -ef | grep pmon

+ASM1
+ASM2

sql>show parameter spfile

resides on shared storage ASM

ASM Architecture
----------------
ASM is an instance , but not a database.
will have separate SGA and set of bg processes.

ASM - Background Processes and Parameters to configure


-------------------------------------------------------
the bg processes starts while instance started in
nomount stage.

ASMB
RBAL
ARBn
GMON
MARK
PMON,SMON

The following background processes are an integral part of Automatic Storage


Management:

ARBn
performs the actual rebalance data extent movements in an Automatic Storage
Management instance. There can be many of these processes running at a time, named
ARB0, ARB1, and so on.

ASMB runs in a database instance that is using an ASM disk group. ASMB
communicates with the ASM instance, managing storage and providing statistics. ASMB
can also run in the ASM instance. ASMB runs in ASM instances when the ASMCMD cp
command runs or when the database instance first starts if the SPFILE is stored in
ASM.

GMON maintains disk membership in ASM disk groups.

MARK marks ASM allocation units as stale following a missed write to an offline
disk. This essentially tracks which extents require resync for offline disks.

RBAL runs in both database and ASM instances. In the database instance, it does
a global open of ASM disks. In an ASM instance, it also coordinates rebalance
activity for disk groups.

ARBn - will move the extents while rebalancing.


RBAL - will provide the plan for rebalancing to arbn.
ASMB - will communicate with ASM Instances from rdbms which is common
for both instances.

Parameters :
----------

cluster_database=true
instance_type=ASM ( in database will find rdbms) - default
instance_name=+ASM1
ASM_POWER_LIMIT=1-11(from 12c - upto 1024) - to adjust rebalancing speed.
ASM_DISKGROUPS - DATA,FRA (default null)
ASM_DISKSTRING - ORCL:DISK1,ORCL:disk2( defa null - purpose to
discover/search for faster perf while instance startup)
DB_UNIQUE_NAME -
processes=35
memory_target=
memory_max_target=

INSTANCE_TYPE - Set to ASM or RDBMS depending on the instance type. The default is
RDBMS.

DB_UNIQUE_NAME - Specifies a globally unique name for the database. This defaults
to +ASM but must be altered if you intend to run multiple ASM instances.

ASM_POWER_LIMIT -The maximum power for a rebalancing operation on an ASM instance.


The valid values range from 1 to 11, with 1 being the default. The higher the limit
the more resources are allocated resulting in faster rebalancing operations. This
value is also used as the default when the POWER clause is omitted from a rebalance
operation.

ASM_DISKGROUPS - The list of disk groups that should be mounted by an ASM instance
during instance startup, or by the ALTER DISKGROUP ALL MOUNT statement. ASM
configuration changes are automatically reflected in this parameter.

ASM_DISKSTRING - Specifies a value that can be used to limit the disks considered
for discovery. Altering the default value may improve the speed of disk group mount
time and the speed of adding a disk to a disk group. Changing the parameter to a
value which prevents the discovery of already mounted disks results in an error.
The default value is NULL allowing all suitable disks to be considered.

Tool :

how to login to asm instance?


su - oracle
. grid_env
sqlplus '/as sysasm'

Finding instance status from gv$instance of every node from one single node of any.
select inst_id,instance_name,status from gv$instance;

------------------------------
asmca - configuration assistant
asmcmd (ASM file system - command mode)

$. grid_env
$asmcmd
asmcmd>
ls
cd
lsdg
du
mkdir
pwd

ARBn
ASMB
RBAL
GMON
MARK

Which background processes coordinate the rebalancing activity ?


RBAL
What is the primary task for RBAL ?
open disks for diskgroups.

Which background process involves moving extents while adding/removing disks?


ARbn

Which background processes runs on RDBMS and ASM ?


ASMB

How to change the parameter to effect all instances ?


sid='*';
sql>alter system set param=value scope=both sid='*';

Totally three diskgroups are recommended in a ASM.


DATA - to hold datafiles. Metadata
FRA - to hold backupsets,archives,control,redo.
OCRVote - for OCR if multiplexed.

select inst_id,instance_number,host_name,status from gv$instance;

How to find the asm instance status on unix level?

using $srvctl status asm -n rac1,rac2 (of list of nodes)


or
$srvctl status asm ( (of all nodes)
or
$srvctl status asm -n rac1 (only particular node)

Tools - ASM
-----------
asmca - automatic storage mgt configuration assistant
asmcmd - asm command line

About asmcmd
------------
$. grid_env
$asmcmd
$ascmd> ( this is the command line asm prompt )
where we can use few unix commands for asm storage)

can list the diskgroups status


$asmcmd>lsdg

for creating directories/listing/pwd/removing/start/stop diskgroup

About asmca - configuration assistant


-------------------------------------
Note: Use xhost + in root user to use it..

#xhost +
$su - oracle
$. grid_env
$asmca

we can view the diskgroup


mount/drop/create/add disks to the diskgroups

Diskgroup is a logical name associated with one or more physical asm disks.
eg: DATA - DISK1 - Can store ocr,votedisk,datafiles,redo,ctl.
FRA - DISK2 - can store archives,rman backup sets,redo,ctl
FAST Recovery Area

Oracle recommends to manage with min three diskgroups

DATA
FRA
OCRVOTE - If multiplexed - store ocr files.

Each diskgroup with min 4 disks to avail performance.

You might also like