http://marist89.blogspot.com/2008/05/something-to-be-aware-of-10204.html
Sounds like oracle has either made a change to allocate SGA in
different chunks in 10.2.0.4 or qa has let something slip by.
Ideas anyone?
Yes. I don't have that problem on Solaris, but it might be an attempted
backport of Oracle11 MEMORY_TARGET mechanism. See note 465048.1 for the
handling recipes.
--
Mladen Gogala
http://mgogala.freehostia.com