Re: 2,2 GB Coredump

  • From: Stefan Moeding <dba@xxxxxxxxxxx>
  • To: oracle-l@xxxxxxxxxxxxx
  • Date: Tue, 11 May 2010 19:10:44 +0200

Hi!

Ozgur Ozdemircili writes:
> Weird yet I have the max_dump_file_size =1024
>
> Until now I have been going with a script that check the file size and
> {echo "" > file }`s it every minute.
>
> Any more thoughts?

Core files are written by the operating system and the OS obviously does
not honor the parameter. Depending on the shell the ulimit (/bin/sh and
family) or limit (/bin/csh and family) command can tell you the allowed
core size and also limit the size.

Log in as oracle and (assuming a /bin/sh) run

$ ulimit -a

This should tell you among other things the maximum core size that the
oracle user can write. With

$ ulimit -c 0

the generation of core files should be disabled for all processes
started in this shell. Restarting the listener in this shell should do
the trick as all server processes are forked from the listener.

--
Stefan
--
//www.freelists.org/webpage/oracle-l


Other related posts: