My Oracle Support Banner

ASM In Hung State Across All Nodes In Exadata Server (Doc ID 1458626.1)

Last updated on MAY 29, 2018

Applies to:

Oracle Exadata Hardware - Version 11.2.0.2 and later
Exadata Database Machine V2 - Version All Versions and later
Exadata Database Machine X2-2 Hardware - Version All Versions and later
Exadata Database Machine X2-8 - Version All Versions and later
Exadata X3-2 Hardware - Version All Versions and later
Information in this document applies to any platform.

Symptoms

 

More from the ASM ALERT.logs

As this was on an eight-node ASM cluster the only location the following command
will be found was on the original node where the ALTER SYSTEM command was issued
from a single node

...
...
  Sat Apr 28 06:16:49 2012
  ALTER SYSTEM SET memory_target='0' SCOPE=SPFILE SID='*';
  Sat Apr 28 06:17:26 2012
  ALTER SYSTEM SET memory_max_target='0' SCOPE=SPFILE SID='*';
  Sat Apr 28 06:17:50 2012
  ALTER SYSTEM RESET memory_max_target SCOPE=SPFILE SID='*';
  Sat Apr 28 06:18:18 2012
  ALTER SYSTEM SET use_large_pages='TRUE' SCOPE=SPFILE SID='*';
  Sat Apr 28 06:23:51 2012
...
...

 

However, we would find evidence of the changes in the ALERT.LOGs especially during instance restarts (which were frequent).


Changes

Switched ASM from using AMM to USE_LARGE_PAGES.

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.