I have seen smon going upto 127M at which point it starts dumping trace files (one trace file and a core directory for each connected session) as if it's raining. Then instance crashes. All DBAs and Unix Admins panic and bring up the system, unfortunately most important trace file (the smon trace) itself can't be found, because before Oracle finished writing the file the instance crashed, so OWS didn't believe in first place. So we used OEM to capture smon memory leak and sent out the graphs, then they agreed and fixed it as a bug.
We could see this value from OWM, SQL scripts, Spotlight, TOAD, pretty much any tool. BTW this is all on AIX and 9011/9012 (without the patch to fix this problem). Raj ______________________________________________________ Rajendra Jamadagni MIS, ESPN Inc. Rajendra dot Jamadagni at ESPN dot com Any opinion expressed here is personal and doesn't reflect that of ESPN Inc. QOTD: Any clod can have facts, but having an opinion is an art! -----Original Message----- Sent: Thursday, June 20, 2002 2:51 PM To: Multiple recipients of list ORACLE-L Hello, how utility/tool said that SMON was using 50M+ ? regards...
*********************************************************************This e-mail message is confidential, intended only for the named recipient(s) above and may contain information that is privileged, attorney work product or exempt from disclosure under applicable law. If you have received this message in error, or are not the named recipient(s), please immediately notify corporate MIS at (860) 766-2000 and delete this e-mail message from your computer, Thank you.*********************************************************************2
