Either that or it's a OS bug. A simple google search on "SIGSEGV SEGV_MAPERR" returns tons of hits on OS issues related to this although most of them are on Solaris. Finn On 10/29/07, Allen, Brandon <Brandon.Allen@xxxxxxxxxxx> wrote: > > It looks to me like maybe the OS admins have something setup to > automatically kill processes that exceed a certain memory or CPU usage > threshold - maybe check with your Unix admin if you haven't already? > I've had similar issues in the past where processes were automatically > killed for using too much CPU. > > Regards, > Brandon > > -----Original Message----- > From: oracle-l-bounce@xxxxxxxxxxxxx > [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Herring Dave - > dherri > > I've got a regular job to delete obsolete pieces from our RMAN catalog, > which now is failing with "Memory fault". > > I even truss'ed the session and it ends with: > > ... > > Received signal #11, SIGSEGV [default] > siginfo: SIGSEGV SEGV_MAPERR addr=0x0000000000000058 > Err#11 Error 11 > occurred. > *** process killed *** > > Privileged/Confidential Information may be contained in this message or > attachments hereto. Please advise immediately if you or your employer do not > consent to Internet email for messages of this kind. Opinions, conclusions > and other information in this message that do not relate to the official > business of this company shall be understood as neither given nor endorsed > by it. > > -- > //www.freelists.org/webpage/oracle-l > > >