Database Shutdown Did Not Complete In 60 Minutes, Active Secondary Process Waits for 'class secondary wait' (Doc ID 2584522.1)

Last updated on APRIL 17, 2023

Applies to:

Symptoms

Database instance shutdown takes long time and does not come to an end. Alert log file shows:

2018-10-01T11:19:54.331192-04:00
Shutting down instance (immediate) (OS id: 15065)
...
2018-10-01T11:24:57.814852-04:00
Active process 25599 user 'xxxxx' program 'xxxx@xxxxxx'(M000)', waiting for 'class secondary wait'

SHUTDOWN: waiting for logins to complete.
...
2018-10-01T11:27:43.180374-04:00
WARNING: CLMN has failed to cleanup a dead process for 4000 attempts

...
2018-10-01T12:17:43.522849-04:00
WARNING: CLMN has failed to cleanup a dead process for 4100 attempts
2018-10-01T12:19:55.854358-04:00
Active process 25599 user 'm77hcmorad' program 'userx@xxxxxx(M000)', waiting for 'class secondary wait'

SHUTDOWN: Active sessions prevent database close operation
Shutdown did not complete in 60 minutes
2018-10-01T12:19:55.879112-04:00

Changes

 + Shutdown immediate hangs when an active background secondary process is waiting for 'class secondary wait'.

+ This background process is not always the same, but most of the time is MMON secondary one.

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.