| ASM Diskgroups are not mounted with spfile on ASM on next startup with crsctl command in 11gR2. [ID 1059856.1] |
|
| |
修改时间 04-MAY-2011 类型 PROBLEM 状态 PUBLISHED |
|
In this Document
Symptoms
Changes
Cause
Solution
Applies to:
Oracle Server - Enterprise Edition - Version: 11.2.0.1 and later [Release: 11.2 and later ]
Information in this document applies to any platform.
Symptoms
1. 11gR2 Grid Infrastructure has been installed.
2. spfile has been created on the ASM disks.
3. Add some ASM diskgroup to spfile dynamically.
SQL> alter system set asm_diskgroups='DATA','FRA' scope=both sid='+ASM';
4. crsctl stop crs
5. crsctl start crs << FRA ASM diskgroup is not mounted.
SQL> show parameter asm_diskgroups
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
asm_diskgroups string DATA
6. Creat pfile from spfile show there is FRA ASM diskgroup added.
SQL> create pfile='/tmp/init+ASM.ora' from spfile ;
File created.
SQL> !cat /tmp/init+ASM.ora
+ASM.__oracle_base='/orasw/adr'#ORACLE_BASE set from in memory value
*.asm_diskgroups='FRA','DATA'
+ASM.asm_diskgroups='DATA'#Manual Dismount
*.asm_power_limit=1
*.diagnostic_dest='/orasw/adr'
* .instance_type='asm'
*.large_pool_size=12M
*.remote_login_passwordfile='EXCLUSIVE'
7. From alert_ASM.log, you see FRA ASM diskgroup is dismounted individually by asm agent
before ALTER DISKGROUP ALL DISMOUNT /* asm agent */
NOTE: diskgroup resource ora.FRA.dg is offline
SUCCESS: ALTER DISKGROUP FRA DISMOUNT /* asm agent */
...
ALTER DISKGROUP ALL DISMOUNT /* asm agent */
Changes
Please find the following 11gR2 doc regarding automatic update asm_diskgroup parameter.
Oracle Database Reference 11g Release 2 (11.2) ----
ASM_DISKGROUPS
specifies a list of names of disk groups to be mounted by an Automatic
Storage Management instance at instance startup. Oracle ignores the
value that you set for ASM_DISKGROUPS when you specify the NOMOUNT
option at startup or when a ALTER DISKGROUP ALL MOUNT statement is
issued.
Automatic Storage Management (ASM) automatically adds a
disk group to this parameter when the disk group is successfully created
or mounted, and automatically removes a disk group from this parameter
when the disk group is dropped or dismounted.
Issuing the ALTER DISKGROUP...ALL MOUNT or ALTER DISKGROUP...ALL DISMOUNT command does not affect the value of this parameter.
-----
This
issue rises with a combination of automatic update on ASM spfile and
manual dismount ASM diskgroup by asm agent on shutting down CRS.
According to the doc, ALTER DISKGROUP...ALL DISMOUNT command does not affect the value of this parameter.
But
for some reason ( maybe no dependency between asm and asm diskgroup ),
on CRS shutdown, each diskgroup is dismounted individually before ASM is
down, which is considered that the ASM diskgroup is dismounted manually
and spfile is updated accordingly. This affects the next startup.
Unless
there is any dependency, ASM diskgroups won't be mounted automatically
on startup as they are considered being dismounted manually by asm agent
in previous shutdown.
It appears that there is no dependency
between ASM diskgroup and ASM instance as manual ASM shutdown using
sqlplus doesn't cause this issue.
With this finding, once you
create a dependency on ASM diskgroup with a database, it will mount
correponding ASM diskgroups no matter what happens on CRS shutdown.
Cause
No dependency between asm and asm diskgroup
Solution
Workaround
--------------------
1. Create a dependency between FRA diskgroup and a database.
$srvctl modify database -d -a "DATA,FRA"
$srvctl config database -d
For the 10.2 databases using a 11.2 ASM and Grid Infrastructure, see the following document:
Additional Diskgroups Does Not Get Mounted When SRVCTL Is Used To Start And Shutdown ASM Instance (Doc ID 987904.1)
|
相关的
|
[@more@]
来自 “ ITPUB博客 ” ,链接:https://blog.itpub.net/161195/viewspace-1051558/
,如需转载,请注明出处,否则将追究法律责任。