Oracle database links between 10g and 11g?

I've been using DB Links from 11g to 10g. No big issues.

I've been using DB Links from 11g to 10g. No big issues. Only caveat is that 11g can use mixed-case passwords and you might want to switch that off if you are trying to connect from a 10g database to an 11g one.

Thanks. Did you consider using just uppercase passwords for connecting from 10g to 11g to still allow mix-case passwords? – JavaRocky Mar 19 '10 at 2:49.

Sometimes there are problems, when a link from 11G to 10.2.0.4. Oracle Support Doc ID 730423.1: Select With Local Function and Remote Tables Using a Dblink Hangs Due To Enq DX.

Thanks. Heres some refs for all. Ora600.Be/node/1955 surachartopun.

Com/2008/12/dbink-hangs-enq-dx-contention. Html – JavaRocky Mar 21 '10 at 22:26.

ORA-01719 can also be thrown if you have an outer join query in 11g that also uses IN or OR and the tables are being referenced through a db_link to 10g. 11g to 11g works as does 10g to 10g - just comes up if you db_link from 11g to 10g. Specifically, I'm currently seeing this issue using 11.2.0.1 to 10.2.0.3; and 11.2.0.2 to 10.2.0.4.As well as varying O/S releases: Windows and Solaris.

Run this in the target 10g and 11g databases: create table u1 (c1 number); create table u2 (c1 number, c2 number); insert into u1 values (1); insert into u1 values (2); insert into u2 values (1,1); insert into u2 values (1,2); commit; Create db_links (DB10, DB11) in your 11g linking database to both the 10g and 11g linked databases. Run these queries in your 11g linking database: /* this will fail 11g to 10g*/ SELECT * FROM u1@DB10 a, (SELECT * FROM u2@DB10 WHERE c1 IN (1, 2, 3)) be WHERE a. C1 = b.

C1(+); /* this will work 11g to 11g*/ SELECT * FROM u1@DB11 a, (SELECT * FROM u2@DB11 WHERE c1 IN (1, 2, 3)) be WHERE a. C1 = b. C1(+).

A view with dblink in the select list can no longer be accessed from another schema via a synonym (used to work in Oracle 10) The view create or replace foo_view as select foo. Id@link id --yes, I know this is stupid... legacy code from foo@link On other DB user create synonym foo_synonym for otherdb. Foo_view select foo_synonym: "ORA-02019 connection description for remote database not found" The solution is to remove dblinks from the underlying view's select clause (which shouldn't really be there in the first place): create or replace foo_view as select foo.Id id from foo@lin foo.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.