Instance does not open spinning with 100% CPU utilization
(Doc ID 1554569.1)
Last updated on FEBRUARY 27, 2019
Applies to:Oracle Database - Enterprise Edition - Version 220.127.116.11 to 18.104.22.168 [Release 11.1 to 11.2]
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.
***Checked for relevance on 01-Sep-2017***
+ Oracle Database 22.214.171.124 (Standalone) got hung and no more connections were feasible including SYSDBA.
+ Customer took the decision to kill SMON at the operating system level.
+ Since then, the instance can be mounted but never opened.
+ When startup is issued, a new Oracle process is forked at the OS with 100% CPU usage.
+ The V$INSTANCE.STATUS shows OPEN, and the V$DATABASE.OPEN_MODE shows READ WRITE.
+ However, the "alter database open" is never reported as completed in the alert log file.
+ Also, the DBA_* and V$* views are accessible. However, no connections can be done to the application schemas.
+ Trying to "startup upgrade" hangs also.
Background SMON was killed explicitly at the operating system level when instance was hung.
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