An Oracle ASM can be used for standby operation.
Standby operation
Create an Oracle ASM instance resource.
The Oracle ASM instance will not be monitored, but only started or stopped. If the Oracle 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.
Refer to "2.3.2.1 Environment configuration".
Notes in the case of using Oracle ASM in standby operation are as follows.
Supported Configurations
In order to use Oracle ASM, 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 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 Oracle ASM instance and database should become 1:1 or 1:n.
Oracle ASM instance : database = 1:1
An Oracle ASM instance : database = 1:n
The following figure shows an example that Oracle ASM instance : database = 1:2.
The following configuration of standby operation using Oracle ASM is supported.
1:1 standby
The following configuration of standby operation using Oracle ASM 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)/12c R2
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
When creating userApplication, create an Oracle ASM instance resource and Oracle instance resource. Register them in the same Oracle resource.
Information
For further details of registering Oracle ASM instance in an Oracle resource, refer to the step 5 of "2.2.7.1 Oracle Resource Creation and Registration"
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)/12c R2, 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.
A disk group that is used for the Oracle ASM instance must not be mounted or unmounted manually. For the disk group is mounted, the following message might be output to the console when the Oracle ASM resource is activated, but no action needs to be taken.
ORA-15032: not all alterations performed
ORA-15017: diskgroup "diskgroup name" cannot be mounted
ORA-15030: diskgroup name "diskgroup name" is in use by another diskgroup
