Re: core_dump_dest = /dev/null?

Now thats a new one, i've been dumping gigs of data to /dev/null with no problems.

i've done a full export of a >350G database to /dev/null for the sole purpose of forcing a scan on every block to detect block corruption with no problems, i'd like to know what platform you've seen that error happen on.

joe

"Heidi E. Schmidt" wrote:

> > Here's an interesting thought - since Oracle very rarely wants the core
> > dump files, and since they can consume a lot of space unless you
> > routinely clean them up, is there any disadvantage to setting the
> > core_dump_dest parameter to /dev/null? Has anyone actually tried this?
> > Seems like it should work...
>
> Well, /dev/null isn't exactly the garbage bin of the universe.
> It is more like a buffer.
>
> You can put alot into it, but it can play havoc on your system.
> Especially is there is are occuring error that streams constantly to the
> buffer. It can cause your machine to hang or reboot.
>
> My advice is that you can use it for small things but
> avoid dumping large amounts of data to /dev/null
>
> Heidi
>
> --
> Author: Heidi E. Schmidt
> INET: heidi_at_cybercom.net
>
> Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051
> San Diego, California -- Public Internet access / Mailing Lists
> --------------------------------------------------------------------
> To REMOVE yourself from this mailing list, send an E-Mail message
> to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in
> the message BODY, include a line containing: UNSUB ORACLE-L
> (or the name of mailing list you want to be removed from). You may
> also send the HELP command for other information (like subscribing).
Received on Thu May 25 2000 - 08:48:26 CDT