Re: User process starting before the last DB restarting and using a lot of memory

In the future, run ipcs to see what shared memory is being used. There is a doc on metalink that explains how to figure out which shared memory areas go with which instance. Messed up svrmgrl and crashed instances can do strange things.

Wild speculation is your instance crashed, you restarted instance but app still was holding 18G shared memory from old instance, and memory keys for shared memory hashed to the same value, so all new oracle processes would hang. I forget which, but some versions of oracle/sun require manually removing files that map shared memory in the case of a crash.

Time to upgrade. Well, past time, really.

jg

--
@home.com is bogus.
http://www.nytimes.com/2006/05/25/fashion/thursdaystyles/25intern.html?_r=1&pagewanted=1&th&emc=th:&oref=slogin