Re: What is wrong with the following query?
From: Jonathan Lewis <jonathan_at_jlcomp.demon.co.uk>
Date: Sat, 19 Aug 2000 10:04:51 +0100
Message-ID: <966676140.12057.0.nnrp-07.9e984b29_at_news.demon.co.uk>
Date: Sat, 19 Aug 2000 10:04:51 +0100
Message-ID: <966676140.12057.0.nnrp-07.9e984b29_at_news.demon.co.uk>
I assume tableA is defined with some
degree of parallelism which is kicking
off a parallel execution plan.
There are cases where the code re-write
that takes place for the parallel query
slaves manages either to produce illegal
SQL, or a form of SQL that the uses some
of the 'parallel query only' functions (such
as SYS_OP_MSR) in ways which have not
been anticipated.
Do an explain plan on the query, (there is
a sample script on my website) and have
a look at the SQL generated for the slaves,
this may give you a clue of what is going
wrong, and suggest a way of working around
the problem.
-- Jonathan Lewis Yet another Oracle-related web site: http://www.jlcomp.demon.co.uk ds3_99_at_my-deja.com wrote in message <8ncae5$ktu$1_at_nnrp1.deja.com>...Received on Sat Aug 19 2000 - 11:04:51 CEST
>Hi,
>
>What is wrong with the following query?
>
>SELECT TRUNC(t173.timestamp,'DD'), COUNT(t173.id)
>FROM tableA t173
>GROUP BY TRUNC(t173.timestamp,'DD') ORDER BY 1 ASC;
>
>I use Oracle 8.1.6.1.0/Solaris 2.6, and get the following error:
>
>ORA-12801: error signaled in parallel query server P000
>ORA-00979: not a GROUP BY expression
>
>Is this a problem with the Oracle version? Is there a fix for this?
>
>Thanks in advance for your inputs.
>
>- ds
>
>
>Sent via Deja.com http://www.deja.com/
>Before you buy.