Re: Ambiguous column name error after installing new server

On Jan 29, 8:10 am, Nicolas Avila <nicolasav..._at_gmail.com> wrote:
> On Jan 28, 7:11 pm, Michael O <cleveridea...._at_gmail.com> wrote:
>
>
>
>
>
> > On Jan 28, 11:11 am, Nicolas Avila <nicolasav..._at_gmail.com> wrote:
>
> > > mmmmmmmmm...
> > > I will try to make it easier by using an example
>
> > Your original post was clear enough without an example.  And my first
> > post is still the blueprint for your only rational course of action.
>
> > Clearly if you are:
>
> > #1 unwilling or unable to perform regression testing
> > #2 certain the application hasn't change
> > #3 introducing a significant change such as upgrading two releases of
> > your database server
> > #4 certain it is breaking your application
>
> > Then you must abandon your upgrade to 11g or modify your application
> > to accommodate 11g.  There really are no alternatives.  In fact, the
> > latter isn't really a choice given #1.
>
> > Michael Ohttp://blog.crisatunity.com
>
> ok michael and mark
>
> thanks for your answers
>
> I think I will load an SR and I will schedule a full system test in
> the new server
> It will take longer than I wanted, but we will anyway upgrade to 11g
>
> Thanks again and best regards- Hide quoted text -
>
> - Show quoted text -

I do not know why you want to log an SR. 11g is working correctly. The bug is in 9i where no error is returned. The potentially wrong result is however returned since you do not have control over which table the result is being pulled from.

HTH -- Mark D Powell -- Received on Tue Jan 29 2008 - 08:10:37 CST