2.4.2 ASM (Automatic Storage Management)

Automatic Storage Management (hereafter ASM) can be used for standby operation or scalable operation.

Standby operation
Create an ASM instance resource.
The ASM instance will not be monitored, but only started or stopped.
If the ASM instance fails, an Oracle instance resource error will be detected, so userApplication will be switched to the standby node, and ongoing operations will never be disrupted.
About notes on building the environment, in case of Oracle 10g R2/11g R1, refer to "2.4.2.1 Environment configuration with Oracle 10g R2/11g R1", and in case of Oracle 11g R2, refer to "2.4.2.2 Environment configuration with Oracle 11g R2".

Scalable operation
Do not create an ASM instance resource if ASM is used for Oracle RAC. The ASM instance will be controlled by Oracle Clusterware.

2.4.2.1 Environment configuration with Oracle 10g R2/11g R1

Notes in the case of using ASM of Oracle 10g R2/11g R1 in standby operation are as follows.

Creation and configuration of ASM instances

Operation node
The ASM instance and database are only created on the operating node. The standby nodes will only operate the database on the shared disk of the operating node.
Note
- ASM instance name must begin with “+”. The default name is “+ASM”.
  If multiple ASM instance are configured on one server, a different ASM instance name must be assigned.
- If multiple ORACLE_HOME are configured on one server, a different Oracle instance name must be assigned.
- The relation between ASM instance and database should become 1:1 or 1:n.
  - ASM instance : database = 1:1
  - ASM instance : database = 1:n
    The following figure shows an example that ASM instance : database = 1:2.
- In mutual standby operation and N:1 standby operation, the relation between ASM instance and database should become 1:1 or 1:n on each userApplication.
  - Mutual standby
    The following figure shows an example that ASM instance : database = 1:1 on each userApplication.
  - N:1 standby
    The following figure shows an example that ASM instance : database = 1:2 on each userApplication.
See
Refer to the Oracle manual.
Standby node
Set up the standby nodes in the same configuration (directory creation, file copy, and links) as the operating node where the AMS instance and database are created.
Under $ORACLE_HOME/dbs
Under $ORACLE_BASE/admin/$ORACLE_SID
Under $ORACLE_BASE/admin/<ASM instance name>
$ORACLE_BASE/diag/asm (Oracle 11g)
The access privilege to the directories and files must be also the same as that on the operating node.
If you set where archived redo log is output on the operating node, it is necessary to set the same on the standby nodes.
CSS on the standby node must be set and started by manually, though CSS on the operating node is set and started automatically while Oracle Database is being created.
Note
If required files on the operating node is backed up in the tar format with the /opt/FJSVclora/sbin/cloracpy command, configuration information of the ASM instance will not be backed up. Copy the following file manually in the tar format:
- $ORACLE_BASE/admin/<ASM instance name>

ASM initialization parameter check

Check if the disk group in which the Oracle Database is created is set for the ASM instance initialization parameter “ASM_DISKGROUPS”.

Information

For the initialization parameter of the ASM instance, see the Oracle manual.

userApplication creation

When creating userApplication, create an ASM instance resource and Oracle instance resource. Register them in the same Oracle resource.
The following screen is an example of the Oracle resource "Oracle1" with the ASM "+ASM" instance and the Oracle instance "db10g".

Information

For further details of registering ASM instance in an Oracle resource, refer to step 3 of "2.2.7.2 Oracle Resource Creation"
The NULLDETECTOR attribute is automatically set to the flag of the ASM instance resource. This value cannot be changed.

2.4.2.2 Environment configuration with Oracle 11g R2

Notes in the case of using ASM of Oracle 11g R2 in standby operation are as follows.

Supported Configurations

In order to use ASM of Oracle 11g R2, it is necessary to install Oracle Grid Infrastructure. When installing Oracle Grid Infrastructure, the composition which separates the installation user of Oracle Database and the installation user of Oracle Grid Infrastructure is supported. The composition which creating one user is not supported.
A different directory must be assigned respectively for an ORACLE_BASE of the installation user of Oracle Database and an ORACLE_BASE of the installation user of Oracle Grid Infrastructure.

Oracle Grid Infrastructure Installation and ASM instance, Oracle Database Creation

See "Appendix C Oracle Grid Infrastructure Installation and ASM instance, Oracle Database Creation" to install Oracle Grid Infrastructure and create ASM instance, Oracle Database.

Note

ASM instance name must begin with “+”. The default name is “+ASM”.
If multiple ORACLE_HOME are configured on one server, a different Oracle instance name must be assigned.
The relation between ASM instance and database should become 1:1 or 1:n.
- ASM instance : database = 1:1
- ASM instance : database = 1:n
  The following figure shows an example that ASM instance : database = 1:2.
The following configuration of standby operation using Oracle ASM 11g R2 is supported.
- 1:1 standby
The following configuration of standby operation using Oracle ASM 11g R2 is not supported.
- Cascade
- Mutual standby
- N:1 standby
- Priority transfer
- N:M standby
Information
For further details, refer to "Part 1 Planning" of the "PRIMECLUSTER Installation and Administration Guide".

See

Refer to the Oracle manual.

Change Oracle Restart Settings

Execute the following command on each node with Grid user access privileges to set for Oracle Restart and the CSS(Cluster Services Synchronization) daemon to start when OS starts, and disable automatic startup of Oracle instances, Oracle listener, and ASM.

Component	Command
Oracle Restart	crsctl enable has
CSS	crsctl modify resource ora.cssd -attr "AUTO_START=always"
ASM	srvctl disable asm
Oracle listener	srvctl disable listener [-l <listener_name>]
Oracle instance	srvctl disable database -d <db_unique_name>

userApplication Create

Information

For further details of registering ASM instance in a Oracle resource, refer to step 3 of "2.2.7.2 Oracle Resource Creation"
The NULLDETECTOR attribute is automatically set to the flag of the ASM instance resource. This value cannot be changed.

Note

Set up Grid user to ASM instance resource and Oracle listener resource, Oracle user to Oracle instance resource.
Set up the following script in PreOnlineScript of the ASM instance resource to start ASM after CSS started.
```
/opt/FJSVclora/sbin/cloracsswait <Grid user>
```