Re: Sort_area_size ora-0068

From: Frits Hoogland <frits.hoogland_at_gmail.com>
Date: Tue, 2 Sep 2014 10:31:18 +0200
Message-Id: <3C2ED1C3-0BF1-47CF-A4D6-01011B83ED14_at_gmail.com>



Did I miss the platform, operating system? Is the database where this is occuring using AMM (automatic memory management) perhaps?

Frits Hoogland

http://fritshoogland.wordpress.com
frits.hoogland_at_gmail.com
Office : +31 20 5939953
Mobile: +31 6 14180860

On 02 Sep 2014, at 10:25, Dominic Brooks <dombrooks_at_hotmail.com> wrote:

> Yep, could do if they were still running.
> Jobs are weekend only and now disabled because of underlying ORA-00600 and ORA-01803 caused by problems with internal object type mismatches.
> From the ORA-00600 incident trace it looks like that triggered the ORA-00068 - which is ok as strange things can happen when you hit an ORA-00600.
>
> Thanks.
>
> Cheers,
> Dominic
>
> Subject: Re: Sort_area_size ora-0068
> From: frits.hoogland_at_gmail.com
> Date: Tue, 2 Sep 2014 09:55:22 +0200
> CC: mwf_at_rsiz.com; kibeha_at_gmail.com; oracle-l_at_freelists.org
> To: dombrooks_at_hotmail.com
>
> Dominic, can you set an event on the ora 68 to dump an errorstack level 3 dump? that should at least reveal from what (oracle database) kernel function the ora 68 is raised, and make underlying issues like an ora 600 visible (alter session set events '68 trace name errorstack level 3')
>
> Frits Hoogland
>
> http://fritshoogland.wordpress.com
> frits.hoogland_at_gmail.com
> Office : +31 20 5939953
> Mobile: +31 6 14180860
>
> On 02 Sep 2014, at 09:33, Dominic Brooks <dombrooks_at_hotmail.com> wrote:
>
> From trace files it looks like ORA-00068 is spurious and thrown by an underlying ORA-00600.

--
http://www.freelists.org/webpage/oracle-l
Received on Tue Sep 02 2014 - 10:31:18 CEST

Original text of this message