ASM In Hung State Across All Nodes In Exadata Server
(Doc ID 1458626.1)
Last updated on MARCH 04, 2019
Applies to:Exadata Database Machine V2 - Version All Versions and later
Oracle Exadata Hardware - Version 220.127.116.11 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.
- ASM in hung state across all nodes in Exadata server
- System state dump requested by (instance=2, osid=3618), summary=[SYSTEMSTATE_GLOBAL: global system state dump request (kjdgdss_g)] **
System State dumped to trace file /u01/app/oracle/diag/asm/+asm/+<ASM INSTANCE>8/trace/+<ASM INSTANCE>x_diag_7745.trc
- Enqueue blocker waiting on 'GCS lock esc X'
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).
Switched ASM from using AMM to USE_LARGE_PAGES.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!