Shulou(Shulou.com)06/01 Report--

Generally speaking, there are several situations in which asm instances cannot be created (take 11g as an example):

1. Ocrvote disk is damaged

2. The memory allocation of asm instance is unreasonable (it is very likely that it will not work after being rebooted, heh heh)

3. Ran into bug

To get to the point, in case of unreasonable asm memory allocation, the asm instance cannot be started:

For example: ORA-00823: Specified value of sga_target greater than sga_max_size

The following are the most common and commonly used ASM initialization parameter configurations:

+ ASM1.asm_diskgroups='DATA'#Manual Mount

+ ASM2.asm_diskgroups='DATA'#Manual Mount

* .asm_diskstring='/dev/asm*'

* .asm_power_limit=1

* .diagnostic_dest='/u01/gridbase'

* .instance_type='asm'

* .large_pool_size=12M

* .remote_login_passwordfile='EXCLUSIVE'

You cannot change the asm parameter file spfile when the asm instance is not up. How can this be done?

Create a new pfile:

[grid@racpri1 tmp] $vi asm.ora

Start the asm instance with pfile

SQL > startup pfile='/tmp/asm.ora' mount

ASM instance started

Total System Global Area 1135747072 bytes

Fixed Size 2260728 bytes

Variable Size 1108320520 bytes

ASM Cache 25165824 bytes

ASM diskgroups mounted

Rebuild asm spfile:

SQL > create spfile='+ocrvt/racpri-cluster/ASMPARAMETERFILE/spfileasm.ora' from pfile='/tmp/asm.ora'

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.