Dennis, it was a 10046^8 dump for a "optimized java program" ... Ha !! Couldn't make tkprof to read it though ... even with ulimit unlimited. 16 CPU, 32GB box.
We have intentionally left max_dump_file_size to unlimited ...
Raj
--------------------------------------------------------------------------------
Rajendra dot Jamadagni at nospamespn dot com
All Views expressed in this email are strictly personal.
QOTD: Any clod can have facts, having an opinion is an art !
-----Original Message-----
From: DENNIS WILLIAMS [mailto:[EMAIL PROTECTED]]
Sent: Friday, September 26, 2003 4:40 PM
To: Multiple recipients of list ORACLE-L
Subject: RE: RE: what causes a memory dump?
Raj - Thanks, I forgot about that one.
Ryan - you might want to check your value for that parameter.
So Raj, was there any value to the 8-gig dump file beyond the first 4-meg of
it? Or did you have an error that required you to increase the dump file
size in order to diagnose it?
Dennis Williams
DBA, 80%OCP, 100% DBA
Lifetouch, Inc.
[EMAIL PROTECTED]
********************************************************************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
