How to use ASMCA in silent mode to configure ASM for a stand-alone server [ID 1068788.1]

本文链接：https://blog.csdn.net/wuweilong/article/details/7473769

How to use ASMCA in silent mode to configure ASM for a stand-alone server [ID 1068788.1]

--------------------------------------------------------------------------------

修改时间 05-OCT-2011 类型 HOWTO 状态 PUBLISHED

In this Document
Goal
Solution

--------------------------------------------------------------------------------

Applies to:
Oracle Server - Enterprise Edition - Version: 11.2.0.1.0 and later [Release: 11.2 and later ]
Information in this document applies to any platform.

Goal
Oracle ASM Configuration Assistant (ASMCA) was introduced in Oracle ASM version 11.2. ASMCA supports installing and configuring Oracle ASM instances, disk groups, volumes, and Oracle ASM cluster file systems (Oracle ACFS). ASMCA can be used interactively, in both GUI and command-line modes, or non interactively in silent command-line mode.

This article demonstrates the use of ASMCA in silent mode, to configure ASM with ASMLIB disks, on Linux and in Oracle Restart (single instance) setup.

Solution
Before configuring ASM, perform the following tasks:
- Prepare disks to be used for ASM and present them to the OS;
- Setup ASMLIB and create ASM disks;
- Install Oracle Grid Infrastructure - software only;
- Configure Grid Infrastructure install for a stand-alone server by running roothas.pl;

For details about completing those taks please see Oracle Grid Infrastructure Installation Guide 11g Release 2 (11.2) for Linux.

Configure ASM with a single disk group and use all ASMLIB disks. All commands are to be run from the Grid Infrastructure home, as the Grid Infrastructure owner.

1. Check for available ASM disks:

$ oracleasm listdisks
DISK1
DISK2
DISK3
DISK4

2. Configure ASM

$ asmca -silent -configureASM -sysAsmPassword sysPassw0rd -asmsnmpPassword asmsnmpPassw0rd -diskString 'ORCL:*' -diskGroupName DATA -disk 'ORCL:*' -redundancy EXTERNAL

3. On successful run, the above command should have returned:

ASM created and started successfully.
DiskGroup DATA created successfully.

And it should have performed the following:
- Start the cluster services daemon (process ocssd.bin);
- Start three agents (processes cssdagent, oraagent.bin and orarootagent.bin);
- Start the disk monitor (process diskmon.bin);
- Start the ASM instance, with instance name +ASM;
- Create the external redundancy disk group named DATA;
- Create ASM's own spfile in disk group DATA;