ORA-00600 [15851] - Help!

[chrisrlong]

ORA-12801: error signaled in parallel query server
ORA-00600: internal error code, arguments: [15851], [8], [8], [1], [2], [], [],
[]

Okay, so forgive the metalink-disabled...

I keep getting this one when I try a particularly complicated parallel statement.

Thoughts?

- Chris

[sambavan]

Chris, did you check your stack trace ... to see what is causing the problem.


Here are some findings on this...

You would have to reduce the size of the sort segments by increasing sort area through one or more of these parameters

SORT_AREA_SIZE
SORT_AREA_RETAINED_SIZE
HASH_AREA_SIZE
SORT_WRITE_BUFFERS
SORT_WRITE_BUFFER_SIZE


Sort temporary segments are necessary to hold portions of sort runs which don't
fit into memory. If little or no memory is reserved for a sort, join or
aggregate operation, the temporary segments can be large.

The Ora-00600 [15851] error is known to occur during queries against databases
with non-sensible configurations such as

hash_join_enabled = true
hash_area_size = 0

Such a configuration sets up a requirement for a hash area, where no hash area
exists.


Hope this would help you

Sam

[Edited by sambavan on 07-26-2001 at 04:08 PM]

[chrisrlong]

Originally posted by sambavan
Chris, did you check your stack trace ... to see what is causing the problem.

Awesome info Sam!

But I confess be being completely ignorant about how to check a stack trace. Guess that's the downside of being a database developer/programmer and not a DBA

Is this something I can actually do or would I require assistance from my 'never-seems-to-be-around' DBA?

Thanks,

- Chris

[sambavan]

That was the info, I acquired out of metalink. But the stack trace at times would hint you in the right direction. Most of the time it would have the statement that was causing the problem and then you can drill down. On the other hand analyzing the stack trace is a mystry, which oracle doesn't want to release out But, in one of the past postings I noticed that some one had a crude way to analyze the stack trace.

Good that it was helpful to you.
Sam