My Oracle Support Banner

LMS terminating the instance due to error 481 When the ZFS File System Hosting Oracle Binary is nearly Full on Solaris (Doc ID 2295886.1)

Last updated on SEPTEMBER 04, 2022

Applies to:

Oracle Database - Enterprise Edition - Version 11.2.0.4 and later
Oracle Database Cloud Schema Service - Version N/A 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 Solaris on SPARC (64-bit)

Symptoms

 Database crashed with below error

Alert log:

------------
 .
 Sun Jul 09 08:02:14 2017
 LMS0 (ospid: 22933) has not called a wait for 89 secs.
 Sun Jul 09 08:03:47 2017
 LMS0 (ospid: 22933): terminating the instance due to error 481
 Sun Jul 09 08:03:47 2017
 opiodr aborting process unknown ospid (24650) as a result of ORA-1092
 Sun Jul 09 08:03:47 2017
 opiodr aborting process unknown ospid (25144) as a result of ORA-1092
 Sun Jul 09 08:03:47 2017
System state dump requested by (instance=1, osid=22933 (LMS0)),
 summary=[abnormal instance termination].
 System State dumped to trace file
$TRACE/<instancename>_diag_22925_20170709080347.trc

 

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.