Oracle Database - Enterprise Edition - Version 11.2.0.4 to 11.2.0.4 [Release 11.2] Information in this document applies to any platform.
SYMPTOMS
Due to other reasons, the MMON process died and subsequent AWR reports are therefore not getting generated.
The MMON process should automatically be respawned but it is not.
CAUSE
MMON/MMNL not being respawned or recreated is due to:
unpublished bug: Bug 19565533 - MMON/MMNL CAN NOT BE AUTOMATICALLY RESTARTED AFTER KILLED
The issue only occurs on 11.2.0.4 and is a regression of the fix forBug 14213856
SOLUTION
To solve the issue:
Apply interimpatch 19565533for 11.2.0.4, if available for your platform.
To check for conflicting patches, please use the MOS Patch Planner Tool Please refer to Note 1317012.1- How To Use MOS Patch Planner To Check And Request The Conflict Patches?
If no patch exists for your version, please contact Oracle Support for a backport request.
- OR -
As a workaround, you can respawn the MMON process by next methods:
Restart the database instance
- OR -
Set the instance to "restricted session" mode and then bring it back to normal mode using following commands as SYSDBA:
alter system enable restricted session; alter system disable restricted session;
原因。是bug所导致的mmon和mmnl进程死掉
解决办法:
1、重启实例
2、不需要重启实例,将数据库设置成
restricted session模式 alter system enable restricted session; alter system disable restricted session; 设置restricted session模式,对dba权限没有影响,普通用户是无法连接数据库,需要授予restricted session权限才能连接数据库,普通用户现有的链接不会有影响。