Re: sending core dumps to dev/null

Check alert.log and trace files why core dumps happen. If not in de background_dump_dest or user_dump_dest check $ORACLE_HOME/rdbms/log and trace and $ORACLE_HOME/dbs directories too. Oracle uses the defaults instead of init.ora values in really stressed situations.
To minimize the size of core dumps set init.ora

    background_core_dump = none
Although not documented, it will make the coredump smaller than "partial" will.
Use

   /usr/sbin/fuser core
to see what process has the core file still open. You can delete an open file on Unix and it will no longer be visable with "ls" but it is still on the filesystem untill all processes that have it open are terminated. That could explain why diskspace is not freed.

Steven <askme_at_nowhere.com> schreef in berichtnieuws arj1gq$j4aq3$1_at_ID-82797.news.dfncis.de...
| Hi,
|
| As I are using Oracle 8.1.7 we get a considerable amount of core dumps on
| our system filling up the disk space over a period of months. Eventually
| there is no space left which forces us to shutdown Oracle. Just removing
| the dumps does not release the space (because this is how UNIX works - or
| does someone know how to fix this?). So I was wondering if I can disable
| the core dumping function of oracle (probably not) or even send the dumps
to
| dev/null. Anyone tried this??
|
| I know it's a stupid idea to send the core dumps to dev/null. I don't
| really think I will do this it's more a theoretical question.
|
| Thank,
| Steve
|
| --
| -----------------------------------------------------------------
| Holidays in Berchtesgaden, Germany:
| http://www.sonnenkoepfl.de/
|
|
Received on Thu Nov 21 2002 - 14:49:31 CST