My Oracle Support Banner

ASM Instance Terminated by PMON Due to Error 488 (Doc ID 1665382.1)

Last updated on FEBRUARY 14, 2019

Applies to:

Oracle Database - Enterprise Edition - Version 11.2.0.3 and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Information in this document applies to any platform.

Symptoms

 ASM instance has been terminated by PMON process.

alert__ASM1.log:
=================
Thu Dec 12 07:55:10 2013
Dumping diagnostic data in directory=[cdmp_20131212075510], requested by (instance=1, osid=16232 (RBAL)), summary=[incident=147985].
System state dump requested by (instance=1, osid=16188 (PMON)), summary=[abnormal instance termination].
System State dumped to trace file <ASM Trace Directory>/+ASM1_diag_16199.trc
Thu Dec 12 07:55:13 2013
PMON (ospid: 16188): terminating the instance due to error 488
Dumping diagnostic data in directory=[cdmp_20131212075513], requested by (instance=1, osid=16188 (PMON)), summary=[abnormal instance termination].
Instance terminated by PMON, pid = 16188
Thu Dec 12 07:55:15 2013

 

Changes

 

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!


In this Document
Symptoms
Changes
Cause
Solution
References


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