2.4.2 Oracle ASM (Automatic Storage Management)

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

Creation and configuration of Oracle ASM instances

Operating node
The Oracle 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
- An Oracle ASM instance name must begin with “+”. The default name is “+ASM”.
  If multiple Oracle ASM instances are configured on one server, a different Oracle ASM instance name must be assigned for Oracle ASM instance.
- If multiple Oracle homes are configured on one server, a different Oracle instance name must be assigned for each Oracle home.
- The relation between an Oracle ASM instance and database should become 1:1 or 1:n.
  - An Oracle ASM instance : database = 1:1
  - An Oracle ASM instance : database = 1:n
- In mutual standby operation and N:1 standby operation, the relation between an Oracle ASM instance and database should become 1:1 or 1:n on each userApplication.
  - Mutual standby
    The following figure shows an example that an Oracle ASM instance : database = 1:1 on each userApplication.
  - N:1 standby
    The following figure shows an example that an Oracle ASM instance : database = 1:2 on each userApplication.
See
Refer to the Oracle Database 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/< Oracle ASM instance name>
$ORACLE_BASE/diag/asm (Oracle Database 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 Oracle ASM instance will not be backed up. Copy the following file manually in the tar format:
- $ORACLE_BASE/admin/< Oracle ASM instance name>

Oracle ASM initialization parameter check

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

See

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

userApplication creation

When creating userApplication, create an Oracle 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 Oracle ASM "+ASM" instance and the Oracle instance "db1".

Information

For further details of registering Oracle 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 Oracle ASM instance resource. This value cannot be changed.

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

Supported Configurations

In order to use Oracle ASM of Oracle Database 11g R2/12c R1, it is necessary to install Oracle Grid Infrastructure. The composition which separates the installation user of Oracle database and the installation user of Oracle Grid Infrastructure is supported in standby operation or single-node cluster operation. 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 Oracle ASM instance, Oracle database Creation

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

Note

An Oracle ASM instance name must begin with “+”. The default name is “+ASM”.
If multiple Oracle homes are configured on one server, a different Oracle instance name must be assigned for each Oracle home. The relation between an Oracle ASM instance and database should become 1:1 or 1:n.
- ASM instance : database = 1:1
- An Oracle ASM instance : database = 1:n
  The following figure shows an example that an Oracle ASM instance : database = 1:2.
The following configuration of standby operation using Oracle ASM 11g R2/12c R1 is supported.
- 1:1 standby
The following configuration of standby operation using Oracle ASM 11g R2/12c R1 is not supported.
- Cascade
- Mutual standby
- N:1 standby
- Priority transfer
- N:M standby

See

Refer to the Oracle Database manual.

Change Oracle Restart Settings

Change the settings of Oracle Restart to control Oracle ASM by PRIMECLUSTER Wizard for Oracle.

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

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

Oracle Database 12c R1 PSR12.1.0.2 or later
Execute the following command on each node with Grid user access privileges to set for Oracle Restart to start when OS starts, and disable automatic startup of Oracle instances, Oracle listener, and Oracle ASM.

Component	Command
Oracle Restart	crsctl enable has
Oracle 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 Oracle 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 Oracle ASM instance resource. This value cannot be changed.

Note

Set up Grid user to Oracle ASM instance resource and Oracle listener resource, Oracle user to Oracle instance resource.
In case of Oracle Database 11g R2/12c R1(12.1.0.1), set up the following script in PreOnlineScript of the Oracle ASM instance resource to start Oracle ASM after CSS started. In case of Oracle Database 12c R1 PSR12.1.0.2 or later, do not set up the following script.
```
/opt/FJSVclora/sbin/cloracsswait <Grid user>
```

In case of using Oracle database services

In case of using Oracle database services other than the default service made when Oracle data base is made, set up the following script.

Create the Cmdline resource, and set up the following scripts to the Start script. The Stop script and the Check script is not set. Set NULLDETECTOR to "Yes". Set TIMEOUT to default value 300.
```
/opt/FJSVclora/sbin/clorasrvstart <Grid user> <db_unique_name>[,<db_unique_name>,...]
```
db_unique_name that uses the Oracle database service is two or more cases, place a comma between db_unique_name.
After starting the Oracle instance, all the Oracle database services registered in db_unique_name start.

See

For Oracle database services, refer to the Oracle Database manual.

2.4.2 Oracle ASM (Automatic Storage Management)

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

2.4.2.2 Environment configuration with Oracle Database 11g R2/12c R1

2.4.2.3 Precaution for Oracle ASM operation