Re: Upgraded to v7.1, dblink from v6 not supported?

In article <DACpx3.27H_at_ncrcan.canada.ncr.com>, Sandra Fergusson <rod.fergusson_at_canada.attgis.com> wrote:
>In article <3rrhll$206_at_news.dax.net>, hts_at_sasdata.no says...
>>
>>Hi all,
>>
>>We just upgraded one of our servers from 7.0 to 7.1.
>>
>>We have one server that is still on v6 that has some database links to
>>the v7 server.
>>
>>On v7.0 this still worked fine, now that we upgraded to 7.1, it won't
>>work anymore.
>>
>>Oracle support in Norway suggest that this is the way it's supposed to
>>work, and that we have to upgrade our v6 to v7.X.
>>
>>Needless to say, that isn't done in a hurry.
>>
>>Is there a workaround? Or a patch or _something_?
>>
>>Thanks in advance,
>>Haakon
>>--
>>hts_at_sasdata.no | haakon.soenderland_at_thcave.bbs.no | Haakon T.
 Soenderland
>>Scandinavian Airlines Data Norway A/S
>>
>Hi!
>
>I sympathize with your predicament...I would suggest upgrading the V6
>database...there were significant data dictionary table and
>functionality changes to both V7 and V7.1 upgrade which could be
>contributing to your problem...I was in the same boat. Are you getting
>any specific error messages that would give us a clue as to exactly what
>problem the database is having with your current DBLINKs?
>
>Sandra Fergusson
>
Here is yet another DBA's perspective from the trenches.

Just last week our firm migrated a company's Novell Oracle 7.0.16.4 DB Server to Oracle7 7.1.3. The orginal 7.0.16.4 database was 'talking' using db_links with an Oracle version 6 database. All was fine. Since migrating from 6 to 7.x we have had nothing but problems. The performace of the DB_LINK is extremely inconsitent. One time a test 'select' using the db_link will work, the next time, literally ten seconds later, it will go into out space never returning anything. Not good!

PB

I don't even bother calling Oracle Support lately. They have not been helpful. I believe Oracle internals are misbehaving, which is nothing new. Just wait for the next upgrade of the month. It might be fixed then. Received on Sun Jun 18 1995 - 00:00:00 CEST