MMNL absent for 1206 secs; Foregrounds taking over in oracle Database

MMNL absent for 1206 secs; Foregrounds taking over in oracle Database
=====================================================================

on last thursday i face a problem, this is ...

I shutdown immediate my Database, after waiting a long time(about 3.30 hours +) for it to shutdown I checked its alet log and found this "MMNL absent for 1422 secs; Foregrounds taking over",
. Its not shutting down. I am using Oracle 10.2.0.4 and Sun solaries spark platform.
what can i do ?

alert log showing :-

Fri Jun 10 00:29:00 2011
Shutting down instance: further logons disabled
Fri Jun 10 00:29:01 2011
Stopping background process CJQ0
Fri Jun 10 00:29:01 2011
Stopping background process QMNC
Fri Jun 10 00:29:03 2011
Stopping background process MMNL
Fri Jun 10 00:29:04 2011
Stopping background process MMON
Fri Jun 10 00:29:05 2011
Shutting down instance (immediate)
License high water mark = 3965
Fri Jun 10 00:29:05 2011
Stopping Job queue slave processes, flags = 7
Fri Jun 10 00:29:05 2011
Job queue slave processes stopped
Fri Jun 10 00:49:05 2011
MMNL absent for 1206 secs; Foregrounds taking over



solution:-

At last i have to do something else. because its a production Database . so much downtime is not tolerable.

at last i execute "shutdown abort" from another session and it works within to minutes .


Description:-
=============

"MMNL absent for 1206 secs; Foregrounds taking over" its mean:-
MMNL(Memory Monitor Light) cannot connect to the Database then the problem of the MMNL absent for 1201 secs; Foregrounds taking over is related to the MMNL process.

If MMNL is absent then foregrounds processes take over to do the job that should be doing itself, for example to determine the longest query duration to tune undo retention appropriately. There are cases where because of incomplete database shutdown process after the startup the MMNL is not restarted!


If this is a hang situation during shutdown (after MMNL is stopped) or
during database open (when MMNL is not yet started), messages are written to the alert.log every 5 minutes.

These messages are for informational purposes only to indicate a hang situation which lasted a long period of time and MMNL is unable to run its job at that moment. When the hang lasts for several hours before the instance is completely stopped/killed, the tail of the alert.log may flood with these messages. Although the message text contains MMNL process, in this case MMNL is actually the victim of the hang issue rather than the cause.

The Memory Monitor Light (MMNL) process is a new process in 10g which works with the Automatic Workload Repository new features (AWR) to write out full statistics buffers to disk as needed.