In this Document
Goal
Solution
Applies to:
Oracle Server - Enterprise Edition - Version: 10.1.0.2 to 10.2.0.5 - Release: 10.1 to 10.2Information in this document applies to any platform.
***Checked for relevance on 27-Feb-2011***
Goal
This note will explain how to create an ASM instance from scratch instead of using DBCA.
Solution
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
Cluster Synchronization Services appears healthy
If its not running, you should configure CSS process by running $ORACLE_HOME/bin/localconfig script.:
# $ORACLE_HOME/bin/localconfig add
/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)
/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=40M
REMOTE_LOGIN_PASSWORDFILE='EXCLUSIVE'
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
$ 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
$ 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';
-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::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.
