Top
PRIMECLUSTER Wizard for Oracle 4.5 Configuration and Administration Guide
FUJITSU Software
Chapter 2 Environment setup > 2.4 Information > 2.4.2 Oracle ASM (Automatic Storage Management)
PreviousNext

2.4.2 Oracle ASM (Automatic Storage Management)

An Oracle ASM can be used for standby operation or scalable 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.

About notes on building the environment, in case of Oracle Database 11g R1 or earlier, refer to "2.4.2.1 Environment configuration with Oracle Database 11g R1 or earlier", and in case of Oracle Database 11g R2 or later, refer to "2.4.2.2 Environment configuration with Oracle Database 11g R2 or later".

Scalable operation

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

2.4.2.1 Environment configuration with Oracle Database 11g R1 or earlier

Notes in the case of using Oracle ASM of Oracle Database 11g R1 or earlier in standby operation are as follows.

Creation and configuration of Oracle ASM instances

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.

2.4.2.2 Environment configuration with Oracle Database 11g R2 or later

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

Supported Configurations

In order to use Oracle ASM of Oracle Database 11g R2 or later, 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 or later is supported.

    • 1:1 standby

    The following configuration of standby operation using Oracle ASM 11g R2 or later is not supported.

    • Cascade

    • Mutual standby

    • N:1 standby

    • Priority transfer

    • N:M standby

See

Refer to the Oracle Database manual.

Using Oracle Database 18c/19c

Execute the procedure in "Appendix H Using Oracle Database 18c/19c".

Add RMS Stop Processing

To ensure that RMS is stopped before ohasd service of Oracle Grid Infrastructure is stopped during OS shutdown, execute the following procedure.

  1. Create the script file /etc/init.d/stopRMS and add execution permission as a root user.
    Create script file :

    # vi /etc/init.d/stopRMS
(Paste the following the content of script file)
# chmod 744 /etc/init.d/stopRMS

    Content of script file :

    #!/usr/bin/bash
#

case "$1" in
'stop')
    /opt/SMAW/SMAWRrms/lib/svc/smawrrms stop
    ;;

*)
    echo "Usage: stopRMS { stop }"
    ;;
esac

  2. Check the directory where the stop script of ohasd service of Oracle Grid Infrastructure is located.

    # find  /etc/rc*.d/ | grep ohasd
/etc/rc0.d/K19ohasd
/etc/rc1.d/K19ohasd
/etc/rc2.d/K19ohasd
/etc/rc3.d/S96ohasd
/etc/rcS.d/K19ohasd

  3. Create a symbolic link "K00stopRMS" to /etc/init.d/stopRMS in the directory where "K<Two digit number>ohasd" is located.
    The example in step 2, create them in /etc/rc0.d, /etc/rc1.d, /etc/rc2.d, and /etc/rcS.d.

    # ln -s /etc/init.d/stopRMS /etc/rc0.d/K00stopRMS
# ln -s /etc/init.d/stopRMS /etc/rc1.d/K00stopRMS
# ln -s /etc/init.d/stopRMS /etc/rc2.d/K00stopRMS
# ln -s /etc/init.d/stopRMS /etc/rcS.d/K00stopRMS

Change Oracle Restart Settings

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

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>

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.
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 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)/12c R2/18c/19c, 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.

See

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

2.4.2.3 Precaution for Oracle ASM operation

A disk group that is used for the Oracle ASM instance must not be mounted or unmounted manually. If 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

PreviousNext
All Rights Reserved, Copyright (C) FUJITSU LIMITED 2019-2021