Additional Diskgroups Does Not Get Mounted When SRVCTL Is Used To Start And Shutdown ASM Instance [I

最新推荐文章于 2024-09-22 11:17:00 发布

ctfr3038

最新推荐文章于 2024-09-22 11:17:00 发布

阅读量138

点赞数

文章标签：数据库

Additional Diskgroups Does Not Get Mounted When SRVCTL Is Used To Start And Shutdown ASM Instance [ID 987904.1]

		修改时间 26-APR-2010 类型 PROBLEM 状态 PUBLISHED

In this Document
Symptoms
Changes
Cause
Solution
References

Symptoms

In 11.2 Oracle Restart (Standalone) installation, ASM diskgroups are mounted automatically after ASM instance is stopped and started with srvctl. Only the ASM diskgroup containing spfile for the ASM instance is mounted.

Changes

Starting with 11gR2, ASM instance, listeners, diskgroups are a resoure in CRS repository also in single instance installations. They are registered to OCR and OCR resources were affected by srvctl stop/start asm instance commands.

Cause

"crsctl stop asm" statement removes diskgroup names from asm_diskgroups parameter file.

This is a known bug.

Bug 8448079 TB-CMP: 11.2 CRS+10.2 RAC DB INSTANCE FAILED TO START AFTER BOUNCING CRS STACK

In Oracle Restart Installations, during "crsctl stop ASM", when CRS 11.2 tries to stop diskgroup resources, it will remove the diskgroup name from the asm parameter "$ASM_SID.asm_diskgroups".

The bug is fixed in 11.2.0.2 patchset version and next major database version 12.0.
Disabling diskgroup from CRS repository is a workaround. If a backport is needed, please contact Oracle Support.

Solution

In order to workaround this issue, you need to disable diskgroup resources to prevent asm parameter "asm_diskgroups" from being changed during "crsctl stop crs". And then manually set ASM parameter "$ASM_SID.asm_diskgroups".

Please note that the following procedure only applies for 10.2 database version or if database compatibility is set to 10.2 for a 11g database.

For 11.2 databases there is a dependency between ASM diskgroups and databases created. Oracle Restart checks the dependencies included in the resources and starts the diskgroups automatically when the databases are started.

If the procedure is aplied to an 11.2 database, then Oracle Restart may not start the database because diskgroups are disabled.

See the followings as an example for DATA and BACKUP diskgroups as a workaround for 11.2 CRS and 10.2 RAC databases:

1- Disable diskgroups

$CRS112_HOME/bin/srvctl disable diskgroup -g data
$CRS112_HOME/bin/srvctl disable diskgroup -g backup

2- Stop diskgroups and ASM instance.

srvctl stop diskgroup -g data
srvctl stop diskgroup -g backup
srvctl stop asm

3- Alter spfile and include DATA and BACKUP diskgroups.

sql> alter system set asm_diskgroups='DATA','BACKUP' scope=spfile;

At this step, please check spfile and ensure it does NOT contain a line like follows:

asm_diskgroups=''#Manual Dismount

If exists, modify asm_diskgroups parameter by creating a pfile from spfile and include all diskgroups that needs to be mounted.

4- Start asm instance

srvctl start asm

With the above setting, when asm starts, it will automatically mount diskgroups "DATA" and "BACKUP".

select name,state from v$asm_diskgroup;

Query diskgroup name, state from v$asm_disk. "srvctl status diskgroup" will always show the diskgroups offline because their are disabled from OCR.

sql> select name,state from v$asm_diskgroup;

NAME STATE
------------------------------ -----------
DATA MOUNTED
BACKUP MOUNTED