Network Security Internet Technology Development Database Servers Mobile Phone Android Software Apple Software Computer Software News IT Information

In addition to Weibo, there is also WeChat

Please pay attention

WeChat public account

Shulou

ORACLE RAC 11.2.0.4 what to do if the ASM sga setting for cluster restart caused by adding ASM disk is too small?

2025-01-18 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Database >

Share

Shulou(Shulou.com)05/31 Report--

Editor to share with you ORACLE RAC 11.2.0.4 ASM disk led to cluster restart ASM sga setting is too small how to deal with, I believe most people do not know much about it, so share this article for your reference, I hope you will learn a lot after reading this article, let's learn about it!

A colleague added a disk to a 2-node ORACLE RAC 11.2.0.4 cluster ASM and did not notice that the sga setting of ASM was too small, which caused the cluster to restart when adding disk reblance. The detailed description is as follows:

1. Problem description

ORACLE RAC 11.2.0.4 Cluster ASM adds disk, but does not notice that the sga setting of ASM is too small, which causes the cluster to restart when adding disk reblance.

2. Problem analysis.

2.1 first of all, a serious alarm occurred on the so-and-so platform when the operation and maintenance monitoring alarm was received.

2.2 Log in to the relevant platform to view the database and cluster ASM log, and it is found that node 1 cluster has been restarted, and the relevant error log is as follows:

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 Zuo

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 (1penny 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 Database OPS staff noticed that the main operation before was to add disks to the disk group and observe the ASM alarm log. The relevant operation records are as follows:

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 (2pm 20) to disk (/ dev/rdisk/VD-DATA21)

NOTE: Assigning number (2jue 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 Zuo

NOTE: Attempting voting file refresh on diskgroup ORADATA

2.4 at this point, it can be determined that the ASM disk is added. When ASM is doing reblance, the cluster restart is caused by the small SGA setting of ASM.

3. Problem handling

Adjust the SGA size of the ASM of the relevant cluster to 2G, restart the cluster, and ASM starts the normal 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

The above is all the contents of the article "how to deal with the small ASM sga setting caused by the addition of ORACLE RAC 11.2.0.4 ASM to the cluster restart". Thank you for reading! I believe we all have a certain understanding, hope to share the content to help you, if you want to learn more knowledge, welcome to follow the industry information channel!

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.

Views: 0

*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.

Share To

Wechat

© 2024 shulou.com SLNews company. All rights reserved.

12
Report