Databases Reference
In-Depth Information
These parameters unveil some of ASM's inner workings. The default settings indicate that
ASM divides an allocation unit (
_ASM_AUSIZE
) into 128 KB chunks (
_ASM_STRIPESIZE
) and places
each of those chunks on up to eight different disks (
_ASM_STRIPEWIDTH
). Very large databases
may benefit from increasing
_ASM_AUSIZE
, but this is beyond the scope of this topic.
4
This chapter
merely addresses
_ASM_ALLOW_ONLY_RAW_DISKS
.
Setting Up Oracle Clusterware for ASM
To start an ASM instance, a stripped down version of Oracle Clusterware must be running on
the same system. This is accomplished with the command
%ORACLE_HOME%\bin\localconfig
add
, which creates an ORACLE cluster registry (OCR) in
%ORACLE_HOME%\cdata\localhost\
local.ocr
. It also creates a new Windows service for the OCSSD Clusterware daemon. OCSSD
logging goes to the file
%ORACLE_HOME%\log\<host name>\cssd\ocssd.log
.
C:> localconfig add
Step 1: creating new OCR repository
Successfully accumulated necessary OCR keys.
Creating OCR keys for user 'ndebes', privgrp ''..
Operation successful.
Step 2: creating new CSS service
successfully created local CSS service
successfully added CSS to home
The service that implements OCSSD is called OracleCSService. You can verify that the
service is functional by running the command
net
start
in a Windows command interpreter.
This command lists all running services.
C:> net start
…
OracleCSService
OracleDB_10_2TNSListener
…
The Clusterware command for checking OCSSD's status is
crsctl
check
css
.
C:> crsctl check css
CSS appears healthy
By running
crsctl
check
crs
, it becomes apparent that only a subset of Clusterware daemons
are active in a local-only configuration. The CRS and EVM daemons required for RAC are
not needed.
C:> crsctl check crs
CSS appears healthy
Cannot communicate with CRS
Cannot communicate with EVM
4.
