LMON: terminating instance due to error 481一例

ALLSTARS_ORACLE

LMON: terminating instance due to error 481一例



首先查看数据库告警日志：





Tue Nov  8 09:32:18 2011
Thread 2 advanced to log sequence 91980 (LGWR switch)
  Current log# 28 seq# 91980 mem# 0: /oracle/orcl1/origlogA/log_g208m1.dbf
  Current log# 28 seq# 91980 mem# 1: /oracle/orcl1/mirrlogA/log_g208m2.dbf
Tue Nov  8 09:37:20 2011
Errors in file /oracle/orcl1/DBS/background/orcl1002_lmon_377522.trc:
ORA-00481: LMON process terminated with error
Tue Nov  8 09:37:20 2011
LMON: terminating instance due to error 481
Tue Nov  8 09:37:20 2011
Errors in file /oracle/orcl1/DBS/background/orcl1002_lmsb_402116.trc:
ORA-00481: LMON process terminated with error
Tue Nov  8 09:37:20 2011
System state dump is made for local instance
System State dumped to trace file /oracle/orcl1/DBS/background/orcl1002_diag_361134.trc
Tue Nov  8 09:37:21 2011
Shutting down instance (abort)
License high water mark = 603
Tue Nov  8 09:37:25 2011
Instance terminated by LMON, pid = 377522
Tue Nov  8 09:37:26 2011
Instance terminated by USER, pid = 2273308
Tue Nov  8 09:38:46 2011
Starting ORACLE instance (normal)
sskgpgetexecname failed to get name
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Interface type 1 en4 192.168.0.0 configured from OCR for use as a cluster interconnect
Interface type 1 en8 10.24.53.0 configured from OCR for use as  a public interface
Picked latch-free SCN scheme 3
Autotune of undo retention is turned on.
LICENSE_MAX_USERS = 0
SYS auditing is enabled
ksdpec: called for event 13740 prior to event group initialization

注意红色字体部分，我们可以从告警日志中看到下面两条最重要的信息：
1） 9.37分，LMON进程出错
2） 9.38分，数据库实例重启

并且另外的实例，没有任何错误信息。同时此实例重启之前，只有LMON ORA-00481错误。因此我们可以初步得到下面的结论：
由于LMON进程异常终止，导致出现了ORA-00481错误，而ORA-00481错误最终导致了数据库实例重启。


我们可以从METALINK上查到ORA-00481将实例重启的很多案例，下面这个症状无法排除：



Bug 9089602 - Instance crash by LMON due to timeout waiting for MMNL [ID 9089602.8]

--------------------------------------------------------------------------------

  修改时间 29-NOV-2010     类型 PATCH     状态 PUBLISHED   


Bug 9089602  Instance crash by LMON due to timeout waiting for MMNL
This note gives a brief overview bug 9089602.
The content was last updated on: 29-NOV-2010
Click here for details of each of the sections below.

Affects:
Product (Component) Oracle Server (Rdbms)  
Range of versions believed to be affected Versions BELOW 11.1  
Versions confirmed as being affected ?10.2.0.5
?10.2.0.4

Platforms affected Generic (all / most platforms affected)  

Fixed:
This issue is fixed in ?(None Specified)


Symptoms: Related To:
?Instance May Crash
?ORA-481
?RAC (Real Application Clusters) / OPS


Description
Instance terminated by LMON due to ORA-481 with dynamic remastering.

Rediscovery Notes:
LMON is blocked by MMNL causing DRM SYNC timeout.
LMON trace has a message of the form:
    sync() timed out - lmon exiting

HOOKS ERROR:ORA-481 NEED:RAC LIKELYAFFECTS XAFFECTS_10.2.0.1 XAFFECTS_V10020001 AFFECTS=10.2.0.1 XAFFECTS_10.2.0.2 XAFFECTS_V10020002 AFFECTS=10.2.0.2 XAFFECTS_10.2.0.3 XAFFECTS_V10020003 AFFECTS=10.2.0.3 XAFFECTS_10.2.0.4 XAFFECTS_V10020004 AFFECTS=10.2.0.4 XAFFECTS_10.2.0.5 XAFFECTS_V10020005 AFFECTS=10.2.0.5 XPRODID_5 PRODUCT_ID=5 PRODID-5 RDBMS XCOMP_RDBMS COMPONENT=RDBMS TAG_CRASH TAG_OPS CRASH OPS

Please note: The above is a summary description only. Actual symptoms can vary. Matching to any symptoms here does not confirm that you are encountering this problem. Always consult with Oracle Support for advice.


References
Bug:9089602 (This link will only work for PUBLISHED bugs)
Note:245840.1 Information on the sections in this article


--------------------------------------------------------------------------------

lunar

LMON is blocked by MMNL causing DRM SYNC timeout.

貌似这个disable DRM可以尝试下？