How to Create manually an ASM instance from scratch

 

This note will explain how to create an ASM instance from scratch instead of using dbca.

 

The procedure is as follows:

Before you start, its recommended that ASM instance installed in a separate Oracle Home, it is very useful in the case of applying patches and upgrade. for example you can upgrade ASM home from 10.2.0.3 to 10.2.0.4 while Database Home still on 10.2.0.3.

1) Because CSS must be running before any ASM instance, you have to make sure that CSS service is running:

# crsctl check css
Cluster Synchronization Services appears healthy

If its not running, you shoshould configure CSS process by running $ ORACLE_HOME/bin/localconfig script:

 

# $ORACLE_HOME/bin/localconfig all

/etc/oracle does not exist. Creating it now.
Successfully accumulated necessary OCR keys.
Creating OCR keys for user 'root', privgrp 'root'..
Operation successful.
Configuration for local CSS has been initialized

Adding to inittab
Startup will be queued to init within 90 seconds.
Checking the status of new Oracle init process...
Expecting the CRS daemons to be up within 600 seconds.

CSS is active on these nodes.
DEV1
CSS is active on all nodes.
Oracle CSS service is installed and running under init(1M)

2) Create the init + ASM. ora file in $ ORACLE_HOME/DBS (this ORACLE_HOME being the newly created one ).

(Change any of these parameters if needed for your environment)

# Default asm_diskstring values for supported platforms:
# Solaris (32/64 bit)/dev/rdsk /*
# Windows NT/XP //./orcldisk *
# Linux (32/64 bit)/dev/raw /*
# HPUX/dev/rdsk /*
# HPUX (Tru 64)/dev/RDISK /*
# AIX/dev/rhdisk /*

Asm_diskstring =''
Instance_type = 'asm'
Large_pool_size = 40 m
Remote_login_passwordfile = 'clusive'
User_dump_dest = $ ORACLE_HOME/admin/+ ASM/udump
Background_dump_dest = $ ORACLE_HOME/admin/+ ASM/bdump
Core_dump_dest = $ ORACLE_HOME/admin/+ ASM/cdump

3) Creating admin directories:

$ cd $ORACLE_HOME
$ mkdir dbs
$ mkdir admin
$ cd admin
$ mkdir +ASM
$ cd +ASM
$mkdir udump
$mkdir bdump
$mkdir cdump

4) starting the ASM instance

For UNIX platforms:

# su - oracle
$ ORACLE_SID=+ASM; export ORACLE_SID
$ sqlplus "/ as sysdba"
SQL> startup

For Microsoft Windows platforms:

C:/> oradim -new -asmsid +ASM -syspwd change_on_install
-pfile D:/oracle/product/10.2.0/admin/+ASM/pfile/init.ora -spfile
-startmode manual -shutmode immediate

Instance created.

C:/> oradim -edit -asmsid +ASM -startmode a
C:/> set oracle_sid=+ASM
C:/> sqlplus "/ as sysdba"

SQL> startup pfile='C:/oracle/product/10.1.0/admin/+ASM/pfile/init.ora';

5) Create spfile from pfile:

SQL> create spfile='+ASM' from pfile;

6) for UNIX platform, put an entry in the oratab file for the ASM intance:

+ASM:<ASM Oracle Home>:Y

You may get the following error on first start:

ORA-15110: No diskgroups mounted

This error can be safely ignored, when creating a new diskgroup, The diskgroup name will be added automatically to the asm_diskgroups parameter and you will not get this error again.

 

 

 

 

 

From Oracle

Bytes -------------------------------------------------------------------------------------------------------

Blog: http://blog.csdn.net/tianlesoftware

Email: dvd.dba@gmail.com

Dba1 group: 62697716 (full); dba2 group: 62697977 (full) dba3 group: 62697850 (full)

Super DBA group: 63306533 (full); dba4 group: 83829929 dba5 group: 142216823

Chat group: 40132017 chat 2 group: 69087192

-- Add the group to describe the relationship between Oracle tablespace and data files in the remarks section. Otherwise, the application is rejected.