Last updated on SEPTEMBER 02, 2017
Applies to:Oracle Database - Enterprise Edition - Version 184.108.40.206 to 220.127.116.11 [Release 11.1 to 11.2]
Information in this document applies to any platform.
***Checked for relevance on 01-Sep-2017***
+ Oracle Database 18.104.22.168 (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.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms