ORACLE RAC 11.2.0.4 ASM加盘导致集群重启之ASM sga设置过小怎么处理

55次阅读
没有评论

共计 4199 个字符,预计需要花费 11 分钟才能阅读完成。

行业资讯    
数据库    
关系型数据库    
ORACLE RAC 11.2.0.4 ASM 加盘导致集群重启之 ASM sga 设置过小怎么处理

丸趣 TV 小编给大家分享一下 ORACLE RAC 11.2.0.4 ASM 加盘导致集群重启之 ASM sga 设置过小怎么处理,相信大部分人都还不怎么了解,因此分享这篇文章给大家参考一下,希望大家阅读完这篇文章后大有收获,下面让我们一起去了解一下吧!

    一同事为一 2 节点的 ORACLE RAC 11.2.0.4 集群 ASM 加盘,没有注意到 ASM 的 sga 设置过小,加盘 reblance 时导致集群重启。详细描述如下:

 1、问题描述

 ORACLE RAC 11.2.0.4 集群 ASM 加盘,没有注意到 ASM 的 sga 设置过小,加盘 reblance 时导致集群重启。

 2、问题分析

 2.1 首先,接到运维监控告警,某某平台发生严重告警

 2.2 登陆相关平台查看数据库和集群 ASM 日志,发现节点 1 集群发生重启,相关报错日志如下:

Wed Dec 26 17:20:29 2018

ARB0 started with pid=43, OS id=22557 

NOTE: assigning ARB0 to group 2/0x6b4139d2 (ORADATA) with 1 parallel I/O

NOTE: Attempting voting file refresh on diskgroup ORADATA

Wed Dec 26 17:22:37 2018

Errors in file /u01/app/grid/diag/asm/+asm/+ASM1/trace/+ASM1_arb0_22557.trc  (incident=208353):

ORA-04031: unable to allocate 7072 bytes of shared memory (shared pool , unknown object , sga heap(1,1) , ges resource )

Incident details in: /u01/app/grid/diag/asm/+asm/+ASM1/incident/incdir_208353/+ASM1_arb0_22557_i208353.trc

Use ADRCI or Support Workbench to package the incident.

See Note 411.1 at My Oracle Support for error and packaging details.

Wed Dec 26 17:22:39 2018

Dumping diagnostic data in directory=[cdmp_20181226172239], requested by (instance=1, osid=22557 (ARB0)), summary=[incident=208353].

Wed Dec 26 17:22:46 2018

Errors in file /u01/app/grid/diag/asm/+asm/+ASM1/trace/+ASM1_m000_22771.trc  (incident=208345):

ORA-04031: unable to allocate 12312 bytes of shared memory (shared pool , unknown object , KKSSP^1232 , kglseshtTable)

Incident details in: /u01/app/grid/diag/asm/+asm/+ASM1/incident/incdir_208345/+ASM1_m000_22771_i208345.trc

Use ADRCI or Support Workbench to package the incident.

See Note 411.1 at My Oracle Support for error and packaging details.

Errors in file /u01/app/grid/diag/asm/+asm/+ASM1/trace/+ASM1_m000_22771.trc:

ORA-04031: unable to allocate 12312 bytes of shared memory (shared pool , unknown object , KKSSP^1232 , kglseshtTable)

 2.3 数据库运维人员注意到,此前的主要操作主要就是给磁盘组加盘,观察 ASM 告警日志,相关操作记录如下:

Wed Dec 26 17:20:16 2018

SQL ALTER DISKGROUP ORADATA ADD  DISK /dev/rdisk/VD-DATA21 SIZE 182272M ,

/dev/rdisk/VD-DATA22 SIZE 182272M /* ASMCA */ 

NOTE: GroupBlock outside rolling migration privileged region

NOTE: Assigning number (2,20) to disk (/dev/rdisk/VD-DATA21)

NOTE: Assigning number (2,21) to disk (/dev/rdisk/VD-DATA22)

NOTE: requesting all-instance membership refresh for group=2

NOTE: initializing header on grp 2 disk ORADATA_0020

NOTE: initializing header on grp 2 disk ORADATA_0021

NOTE: requesting all-instance disk validation for group=2

Wed Dec 26 17:20:19 2018

NOTE: skipping rediscovery for group 2/0x6b4139d2 (ORADATA) on local instance.

NOTE: requesting all-instance disk validation for group=2

NOTE: skipping rediscovery for group 2/0x6b4139d2 (ORADATA) on local instance.

NOTE: initiating PST update: grp = 2

Wed Dec 26 17:20:25 2018

GMON updating group 2 at 7 for pid 42, osid 22238

NOTE: PST update grp = 2 completed successfully 

NOTE: membership refresh pending for group 2/0x6b4139d2 (ORADATA)

GMON querying group 2 at 8 for pid 18, osid 5128

NOTE: cache opening disk 20 of grp 2: ORADATA_0020 path:/dev/rdisk/VD-DATA21

NOTE: cache opening disk 21 of grp 2: ORADATA_0021 path:/dev/rdisk/VD-DATA22

Wed Dec 26 17:20:29 2018

NOTE: Attempting voting file refresh on diskgroup ORADATA

GMON querying group 2 at 9 for pid 18, osid 5128

SUCCESS: refreshed membership for 2/0x6b4139d2 (ORADATA)

Wed Dec 26 17:20:29 2018

SUCCESS: ALTER DISKGROUP ORADATA ADD  DISK /dev/rdisk/VD-DATA21 SIZE 182272M ,

/dev/rdisk/VD-DATA22 SIZE 182272M /* ASMCA */

NOTE: starting rebalance of group 2/0x6b4139d2 (ORADATA) at power 1

Starting background process ARB0

Wed Dec 26 17:20:29 2018

ARB0 started with pid=43, OS id=22557 

NOTE: assigning ARB0 to group 2/0x6b4139d2 (ORADATA) with 1 parallel I/O

NOTE: Attempting voting file refresh on diskgroup ORADATA

 2.4 到此,基本上可以确定是 ASM 加盘,ASM 在进行 reblance 的时候,由于 ASM 的 SGA 设置过小导致的集群重启

 3、问题处理

  调整相关集群的 ASM 的 SGA 大小到 2G,重新启动集群,ASM 开始正常的 reblance:

Wed Dec 26 17:56:32 2018

NOTE: client SYXPTDB1:SYXPTDB registered, osid 1074, mbr 0x1

Wed Dec 26 18:35:33 2018

ALTER SYSTEM SET memory_max_target= 2G SCOPE=SPFILE SID= *

ALTER SYSTEM SET memory_target= 2G SCOPE=SPFILE SID= *

ALTER SYSTEM SET sga_max_size= 2G SCOPE=SPFILE SID= *

Wed Dec 26 20:50:11 2018

NOTE: GroupBlock outside rolling migration privileged region

NOTE: requesting all-instance membership refresh for group=2

Wed Dec 26 20:50:14 2018

NOTE: membership refresh pending for group 2/0x1edaa5d7 (ORADATA)

Wed Dec 26 20:50:17 2018

GMON querying group 2 at 7 for pid 18, osid 26306

SUCCESS: refreshed membership for 2/0x1edaa5d7 (ORADATA)

NOTE: Attempting voting file refresh on diskgroup ORADATA

以上是“ORACLE RAC 11.2.0.4 ASM 加盘导致集群重启之 ASM sga 设置过小怎么处理”这篇文章的所有内容,感谢各位的阅读!相信大家都有了一定的了解,希望分享的内容对大家有所帮助,如果还想学习更多知识,欢迎关注丸趣 TV 行业资讯频道!

正文完
 
丸趣
版权声明:本站原创文章,由 丸趣 2023-07-24发表,共计4199字。
转载说明:除特殊说明外本站除技术相关以外文章皆由网络搜集发布,转载请注明出处。
评论(没有评论)