Re: Ambiguous column name error after installing new server

From: Nicolas Avila <nicolasavila_at_gmail.com>
Date: Tue, 29 Jan 2008 05:10:40 -0800 (PST)
Message-ID: <9934122e-894c-43b5-9b7c-3640a9cd567b@m34g2000hsb.googlegroups.com>


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 Received on Tue Jan 29 2008 - 07:10:40 CST

Original text of this message