From: Nicolas Bronke on
With Oracle 10g the RULE command will not be supported.
So far as good, we removed all RULE statements inside Queries and views.
Mostly it works fine, but in some cases the queries does not work correcly.
No rows are returned. If I put the RULE back in this query everything works
fine.
This happens with 20g2.0.3 and 10g2.0.4

Does someone else has seen this and does exist a patch for this behaviour?

Regards
Nicolas

From: Mark D Powell on
On Mar 20, 7:41 am, "Nicolas Bronke" <Nicolas_Bro...(a)web.de> wrote:
> With Oracle 10g the RULE command will not be supported.
> So far as good, we removed all RULE statements inside Queries and views.
> Mostly it works fine, but in some cases the queries does not work correcly.
> No rows are returned. If I put the RULE back in this query everything works
> fine.
> This happens with 20g2.0.3 and 10g2.0.4
>
> Does someone else has seen this and does exist a patch for this behaviour?
>
> Regards
> Nicolas

An actual example SQL showing both versions wtih results and the
explain plan would likely be helpful. Also information on the type of
table: heap, IOT, partitioned involved in the query is useful.

We have 10.2.0.3 and have not seen this.

Performance issues are common after upgrading to 10g from a lower
version but changes in the query results are not.

HTH -- Mark D Powell --
From: joel garry on
On Mar 20, 4:41 am, "Nicolas Bronke" <Nicolas_Bro...(a)web.de> wrote:
> With Oracle 10g the RULE command will not be supported.
> So far as good, we removed all RULE statements inside Queries and views.
> Mostly it works fine, but in some cases the queries does not work correcly.
> No rows are returned. If I put the RULE back in this query everything works
> fine.
> This happens with 20g2.0.3 and 10g2.0.4
>
> Does someone else has seen this and does exist a patch for this behaviour?
>
> Regards
> Nicolas

In addition to what Mark said, see the 10.2.0.4 and 11g notes that
list all the bugfixes for all the patches. There are some CBO wrong
results bugs that aren't fixed until 11g, but they tend to be really
obscure. Are you using dblinks? How _exactly_ are you gathering
statistics?

jg
--
@home.com is bogus.
http://www.signonsandiego.com/news/2010/mar/20/small-crowd-at-floatopia-party-so-far/
From: Gerard H. Pille on
Nicolas Bronke wrote:
> With Oracle 10g the RULE command will not be supported.
> So far as good, we removed all RULE statements inside Queries and views.
> Mostly it works fine, but in some cases the queries does not work
> correcly. No rows are returned. If I put the RULE back in this query
> everything works fine.
> This happens with 20g2.0.3 and 10g2.0.4
>
> Does someone else has seen this and does exist a patch for this behaviour?
>
> Regards
> Nicolas


The patch being to let the rule hint be. Report the bug to Oracle, if you are able to reproduce
it with the emp and dept tables.
From: Nicolas Bronke on
>> With Oracle 10g the RULE command will not be supported.
>> So far as good, we removed all RULE statements inside Queries and views.
>> Mostly it works fine, but in some cases the queries does not work
>> correcly.
>> No rows are returned. If I put the RULE back in this query everything
>> works
>> fine.
>> This happens with 20g2.0.3 and 10g2.0.4
>>
>> Does someone else has seen this and does exist a patch for this
>> behaviour?
>>
>An actual example SQL showing both versions wtih results and the
>explain plan would likely be helpful. Also information on the type of
>table: heap, IOT, partitioned involved in the query is useful.
>
>We have 10.2.0.3 and have not seen this.
>
>Performance issues are common after upgrading to 10g from a lower
>version but changes in the query results are not.

Thank you. I could not answer earlier.
The problem is, that the sql is very specific (depends also from session
variables) and it seems, that the problem only occurs with a number of data
(or complexity of data).
I think we will ow look a little more deeper in the explain plan.

Regards
Nicolas