Hello,

I found out that the problem seems to be connected to my V_BASE. It
looks fine if you look at its results alone or in simple joins but if
it gets more complicated it shows that strange behavior of changing
the values in one column. It is highly disturbing for me that I can
not rely on a view's results, that it changes it's values when used in
another context.

If I solve the problem I will report it. Has anybody ever had a view
that was "unreliable" as mine? Either I have done something really bad
or something in our server is really mixed up.

Thanks and best,

Hans

On Feb 25, 10:23*am, Hans Mayr <mayr1... (AT) gmx (DOT) de> wrote:
There have been bugs related to hierarchies and union alls, supposedly
fixed in your version - which could mean they broke something related
with the fix. I'd advise you to open an SR with support with the
simplest possible reproducible case to at least rule out a bug or find
a workaround if there is one (which might be an undocumented init.ora
parameter).

jg
--
@home.com is bogus.
http://www.wavewatch.com/Live-Surf-Cams.php

On Feb 25, 10:23*am, Hans Mayr <mayr1... (AT) gmx (DOT) de> wrote:
There have been bugs related to hierarchies and union alls, supposedly
fixed in your version - which could mean they broke something related
with the fix. I'd advise you to open an SR with support with the
simplest possible reproducible case to at least rule out a bug or find
a workaround if there is one (which might be an undocumented init.ora
parameter).

jg
--
@home.com is bogus.
http://www.wavewatch.com/Live-Surf-Cams.php

On Feb 25, 10:23*am, Hans Mayr <mayr1... (AT) gmx (DOT) de> wrote:
There have been bugs related to hierarchies and union alls, supposedly
fixed in your version - which could mean they broke something related
with the fix. I'd advise you to open an SR with support with the
simplest possible reproducible case to at least rule out a bug or find
a workaround if there is one (which might be an undocumented init.ora
parameter).

jg
--
@home.com is bogus.
http://www.wavewatch.com/Live-Surf-Cams.php

On Feb 25, 10:23*am, Hans Mayr <mayr1... (AT) gmx (DOT) de> wrote:
There have been bugs related to hierarchies and union alls, supposedly
fixed in your version - which could mean they broke something related
with the fix. I'd advise you to open an SR with support with the
simplest possible reproducible case to at least rule out a bug or find
a workaround if there is one (which might be an undocumented init.ora
parameter).

jg
--
@home.com is bogus.
http://www.wavewatch.com/Live-Surf-Cams.php

Well:

I found that the WITH clause caused problems. Did I do something one
should not do with WITH? The ugly way of having the same sub select
more than once in the code ran without problems. After solving this
further problems occurred which I could solve trough
OPTIMIZER_FEATURES_ENABLE='10.2.0.2'. I had hoped for a more coherent
and more stable environment.

Best,

Hans

Well:

I found that the WITH clause caused problems. Did I do something one
should not do with WITH? The ugly way of having the same sub select
more than once in the code ran without problems. After solving this
further problems occurred which I could solve trough
OPTIMIZER_FEATURES_ENABLE='10.2.0.2'. I had hoped for a more coherent
and more stable environment.

Best,

Hans

Well:

I found that the WITH clause caused problems. Did I do something one
should not do with WITH? The ugly way of having the same sub select
more than once in the code ran without problems. After solving this
further problems occurred which I could solve trough
OPTIMIZER_FEATURES_ENABLE='10.2.0.2'. I had hoped for a more coherent
and more stable environment.

Best,

Hans

Well:

I found that the WITH clause caused problems. Did I do something one
should not do with WITH? The ugly way of having the same sub select
more than once in the code ran without problems. After solving this
further problems occurred which I could solve trough
OPTIMIZER_FEATURES_ENABLE='10.2.0.2'. I had hoped for a more coherent
and more stable environment.

Best,

Hans