Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: Some Lateral thinking Required - Hard-Coded instance workaround

Re: Some Lateral thinking Required - Hard-Coded instance workaround

From: Jim Kennedy <jim>
Date: Mon, 17 Apr 2006 18:48:04 -0700
Message-ID: <RtydnV4QO6lf2dnZRVn-gQ@comcast.com>

"Johne_uk" <edgarj_at_tiscali.co.uk> wrote in message news:1145294842.841056.47990_at_i39g2000cwa.googlegroups.com...
> Thanks for the replies guys.
>
> I've just found out that the app uses a connection string (no tnsnames)
> so that rules out using tnsnames.The orany1 database is going to be
> scrapped and rebuilt again in the future so the option of connecting to
> orany2 and using db link / synonyms to point to orany1 cannot be used
> (good idea though). Our development is done offshore and we would be
> charged for these changes which is not worth it for the short time we
> need to relocate the app. I agree its bad practise and I believe none
> of other others apps have hard-coded references.
>
> I did trying connecting directly to orany2 and creating synonyms that
> reference table_at_orany2 for any reference to table_at_orany1 in the code
> but it refuses to work.
>
> Thanx again
> John
>

Which gives a good reason why off shoring is not a bright idea. But I am sure you already knew that. Clearly these aren't talented or seasoned application developers. All that money that was "saved" by off shoring comes back to haunt one.
Jim Received on Mon Apr 17 2006 - 20:48:04 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US