The task is asking for 2G of memory. Is there any chance that the 600 error is being caused by the fact that at the time of the request that 2G of free memory is not available? Have anyone looked at the OS statistics for the matching job error times to see what the OS looked like? From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Frits Hoogland Sent: Tuesday, September 02, 2014 4:31 AM To: Dominic Brooks Cc: mwf@xxxxxxxx; Kim Berg Hansen; oracle-l@xxxxxxxxxxxxx Subject: Re: Sort_area_size ora-0068 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<http://fritshoogland.wordpress.com/> frits.hoogland@xxxxxxxxx<mailto:frits.hoogland@xxxxxxxxx> Office : +31 20 5939953 Mobile: +31 6 14180860 On 02 Sep 2014, at 10:25, Dominic Brooks <dombrooks@xxxxxxxxxxx<mailto:dombrooks@xxxxxxxxxxx>> 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@xxxxxxxxx<mailto:frits.hoogland@xxxxxxxxx> Date: Tue, 2 Sep 2014 09:55:22 +0200 CC: mwf@xxxxxxxx<mailto:mwf@xxxxxxxx>; kibeha@xxxxxxxxx<mailto:kibeha@xxxxxxxxx>; oracle-l@xxxxxxxxxxxxx<mailto:oracle-l@xxxxxxxxxxxxx> To: dombrooks@xxxxxxxxxxx<mailto:dombrooks@xxxxxxxxxxx> 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<http://fritshoogland.wordpress.com/> frits.hoogland@xxxxxxxxx<mailto:frits.hoogland@xxxxxxxxx> Office : +31 20 5939953 Mobile: +31 6 14180860 On 02 Sep 2014, at 09:33, Dominic Brooks <dombrooks@xxxxxxxxxxx<mailto:dombrooks@xxxxxxxxxxx>> wrote: From trace files it looks like ORA-00068 is spurious and thrown by an underlying ORA-00600.