Re: ORA-2085
Been there, Done that, Works in production. Yechiel Adar Mehish - Original Message - To: Multiple recipients of list ORACLE-L <[EMAIL PROTECTED]> Sent: Thursday, May 23, 2002 3:33 PM > > I'd never have thought that this was possible > in Advanced Replication > > Hemant K Chitale > > - Original Message - > To: "Multiple recipients of list ORACLE-L" <[EMAIL PROTECTED]> > Sent: Thursday, 23 May, 2002 12:48 AM > > > > At last something that I have experience in. > > > > Just do the following: > > > > On the target database issue the following: > > Alter database rename global_name to donot_trigger; > > > > We had the same problem. This solves it. > > The global name has no other influence. > > > > Yechiel Adar > > Mehish > > - Original Message - > > To: Multiple recipients of list ORACLE-L <[EMAIL PROTECTED]> > > Sent: Tuesday, May 21, 2002 6:08 PM > > > > > > > Yes, I "inherited" this, and I am setting up Multimaster > > > Advanced Replication, setting global_names=false isn't an > > > option. I have suggested moving the donotfiretrigger logic > > > into the trigger, which has some initial support. For the > > > moment, we are changing the code to point to a link with the > > > same name as the service name (which has obvious limitations, > > > so hopefully a real fix will get done). > > > > > > I was really hoping there might be another workaround bandaid > > > though, as I really don't want the "fix" to end up permanent. > > > > > > Thanks, > > > > > > John P Weatherman > > > Database Administrator > > > Replacements Ltd. > > > > > > > > > > > > -Original Message- > > > Sent: Tuesday, May 21, 2002 11:23 AM > > > To: Multiple recipients of list ORACLE-L > > > > > > > > > My guess is that you "inherited" an environment > > > where the DB-Link was setup that way [link-name different > > > from DB-name] . and then, sometime later, > > > you set GLOBAL_NAMES=TRUE > > > > > > Well you have no choice : > > > "// *Action: create a database link with the same name as the database > it > > > > // connects to, or set global_names=false." > > > > > > Are you setting up Advanced Replication [MultiMaster] > > > or Simple Replication [Snapshots] ? I believe that > > > Simple Replication does not mandate GLOBAL_NAMES=TRUE. > > > > > > > > > Hemant K Chitale > > > > > > - Original Message - > > > To: "Multiple recipients of list ORACLE-L" <[EMAIL PROTECTED]> > > > Sent: Tuesday, 21 May, 2002 9:23 PM > > > > > > > > > > Hi all. > > > > > > > > I have recently had to enable global_names in order to set up a > > > > replicated environment. The application uses a database link to > > > > reconnect to the database under a differant user id (I inheirited > > > > this, I had nothing to do with the design!). Appearantly, > > > > global_names has a prblem with this... > > > > > > > > SQL> select * from [EMAIL PROTECTED]; > > > > select * from [EMAIL PROTECTED] > > > >* > > > > ERROR at line 1: > > > > ORA-02085: database link DONOT_TRIGGER.WORLD connects to DRL2.WORLD > > > > > > > > SQL> !oerr ORA 2085 > > > > 02085, 0, "database link %s connects to %s" > > > > // *Cause: a database link connected to a database with a different > > name. > > > > // The connection is rejected. > > > > // *Action: create a database link with the same name as the database > it > > > > // connects to, or set global_names=false. > > > > > > > > So, does anybody have any work arounds or ideas how I can get this > > > > thing working again? > > > > > > > > TIA, > > > > > > > > John P Weatherman > > > > Database Administrator > > > > Replacements Ltd. > > > > -- > > > > Please see the official ORACLE-L FAQ: http://www.orafaq.com > > > > -- > > > > Author: John Weatherman > > > > INET: [EMAIL PROTECTED] > > > > > > > > Fat City Network Services-- (858) 538-5051 FAX: (858) 538-5051 > &g
Re: ORA-2085
I'd never have thought that this was possible in Advanced Replication Hemant K Chitale - Original Message - To: "Multiple recipients of list ORACLE-L" <[EMAIL PROTECTED]> Sent: Thursday, 23 May, 2002 12:48 AM > At last something that I have experience in. > > Just do the following: > > On the target database issue the following: > Alter database rename global_name to donot_trigger; > > We had the same problem. This solves it. > The global name has no other influence. > > Yechiel Adar > Mehish > - Original Message - > To: Multiple recipients of list ORACLE-L <[EMAIL PROTECTED]> > Sent: Tuesday, May 21, 2002 6:08 PM > > > > Yes, I "inherited" this, and I am setting up Multimaster > > Advanced Replication, setting global_names=false isn't an > > option. I have suggested moving the donotfiretrigger logic > > into the trigger, which has some initial support. For the > > moment, we are changing the code to point to a link with the > > same name as the service name (which has obvious limitations, > > so hopefully a real fix will get done). > > > > I was really hoping there might be another workaround bandaid > > though, as I really don't want the "fix" to end up permanent. > > > > Thanks, > > > > John P Weatherman > > Database Administrator > > Replacements Ltd. > > > > > > > > -Original Message- > > Sent: Tuesday, May 21, 2002 11:23 AM > > To: Multiple recipients of list ORACLE-L > > > > > > My guess is that you "inherited" an environment > > where the DB-Link was setup that way [link-name different > > from DB-name] . and then, sometime later, > > you set GLOBAL_NAMES=TRUE > > > > Well you have no choice : > > "// *Action: create a database link with the same name as the database it > > > // connects to, or set global_names=false." > > > > Are you setting up Advanced Replication [MultiMaster] > > or Simple Replication [Snapshots] ? I believe that > > Simple Replication does not mandate GLOBAL_NAMES=TRUE. > > > > > > Hemant K Chitale > > > > - Original Message - > > To: "Multiple recipients of list ORACLE-L" <[EMAIL PROTECTED]> > > Sent: Tuesday, 21 May, 2002 9:23 PM > > > > > > > Hi all. > > > > > > I have recently had to enable global_names in order to set up a > > > replicated environment. The application uses a database link to > > > reconnect to the database under a differant user id (I inheirited > > > this, I had nothing to do with the design!). Appearantly, > > > global_names has a prblem with this... > > > > > > SQL> select * from [EMAIL PROTECTED]; > > > select * from [EMAIL PROTECTED] > > >* > > > ERROR at line 1: > > > ORA-02085: database link DONOT_TRIGGER.WORLD connects to DRL2.WORLD > > > > > > SQL> !oerr ORA 2085 > > > 02085, 0, "database link %s connects to %s" > > > // *Cause: a database link connected to a database with a different > name. > > > // The connection is rejected. > > > // *Action: create a database link with the same name as the database it > > > // connects to, or set global_names=false. > > > > > > So, does anybody have any work arounds or ideas how I can get this > > > thing working again? > > > > > > TIA, > > > > > > John P Weatherman > > > Database Administrator > > > Replacements Ltd. > > > -- > > > Please see the official ORACLE-L FAQ: http://www.orafaq.com > > > -- > > > Author: John Weatherman > > > INET: [EMAIL PROTECTED] > > > > > > Fat City Network Services-- (858) 538-5051 FAX: (858) 538-5051 > > > San Diego, California-- Public Internet access / Mailing Lists > > > > > > To REMOVE yourself from this mailing list, send an E-Mail message > > > to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in > > > the message BODY, include a line containing: UNSUB ORACLE-L > > > (or the name of mailing list you want to be removed from). You may > > > also send the HELP command for other information (like subscribing). > > -- > > Please see the official ORACLE-L FAQ: http://www.orafaq.com > > -- > > Author: Hemant K Chitale > > INET: [EMAIL PROTEC
Re: ORA-2085
Hello Dennis It DOES. We rebuilt our databases number of times during system test. We are using vendor supplied scripts to build the database from an export file. We run the exactly same script on both machines and got two databases that are exactly the same. However on the backup machine we run this command after building because you can not have two databases having the same global name when working with global_names = true (of course, that the whole point of the parameter). After this we rebuild master to master replication - no problems. Also as part of the system test we moved the users ( parameter in the application) to the backup machine and they worked without problems, although the global name was different. Yechiel Adar Mehish - Original Message - To: Multiple recipients of list ORACLE-L <[EMAIL PROTECTED]> Sent: Wednesday, May 22, 2002 7:28 PM > Yechiel - If this does what I think it does, your value to postings ratio > just soared! > Dennis Williams > DBA > Lifetouch, Inc. > [EMAIL PROTECTED] > > > -Original Message- > Sent: Wednesday, May 22, 2002 11:49 AM > To: Multiple recipients of list ORACLE-L > > > At last something that I have experience in. > > Just do the following: > > On the target database issue the following: > Alter database rename global_name to donot_trigger; > > We had the same problem. This solves it. > The global name has no other influence. > > Yechiel Adar > Mehish > - Original Message - > To: Multiple recipients of list ORACLE-L <[EMAIL PROTECTED]> > Sent: Tuesday, May 21, 2002 6:08 PM > > > > Yes, I "inherited" this, and I am setting up Multimaster > > Advanced Replication, setting global_names=false isn't an > > option. I have suggested moving the donotfiretrigger logic > > into the trigger, which has some initial support. For the > > moment, we are changing the code to point to a link with the > > same name as the service name (which has obvious limitations, > > so hopefully a real fix will get done). > > > > I was really hoping there might be another workaround bandaid > > though, as I really don't want the "fix" to end up permanent. > > > > Thanks, > > > > John P Weatherman > > Database Administrator > > Replacements Ltd. > > > > > > > > -Original Message- > > Sent: Tuesday, May 21, 2002 11:23 AM > > To: Multiple recipients of list ORACLE-L > > > > > > My guess is that you "inherited" an environment > > where the DB-Link was setup that way [link-name different > > from DB-name] . and then, sometime later, > > you set GLOBAL_NAMES=TRUE > > > > Well you have no choice : > > "// *Action: create a database link with the same name as the database it > > > // connects to, or set global_names=false." > > > > Are you setting up Advanced Replication [MultiMaster] > > or Simple Replication [Snapshots] ? I believe that > > Simple Replication does not mandate GLOBAL_NAMES=TRUE. > > > > > > Hemant K Chitale > > > > - Original Message - > > To: "Multiple recipients of list ORACLE-L" <[EMAIL PROTECTED]> > > Sent: Tuesday, 21 May, 2002 9:23 PM > > > > > > > Hi all. > > > > > > I have recently had to enable global_names in order to set up a > > > replicated environment. The application uses a database link to > > > reconnect to the database under a differant user id (I inheirited > > > this, I had nothing to do with the design!). Appearantly, > > > global_names has a prblem with this... > > > > > > SQL> select * from [EMAIL PROTECTED]; > > > select * from [EMAIL PROTECTED] > > >* > > > ERROR at line 1: > > > ORA-02085: database link DONOT_TRIGGER.WORLD connects to DRL2.WORLD > > > > > > SQL> !oerr ORA 2085 > > > 02085, 0, "database link %s connects to %s" > > > // *Cause: a database link connected to a database with a different > name. > > > // The connection is rejected. > > > // *Action: create a database link with the same name as the database it > > > // connects to, or set global_names=false. > > > > > > So, does anybody have any work arounds or ideas how I can get this > > > thing working again? > > > > > > TIA, > > > > > > John P Weatherman > > > Database Administrator > > > Replacements Ltd. > > > -- > > > Please see the official ORACLE-L FAQ: http://www.ora
RE: ORA-2085
Yechiel - If this does what I think it does, your value to postings ratio just soared! Dennis Williams DBA Lifetouch, Inc. [EMAIL PROTECTED] -Original Message- Sent: Wednesday, May 22, 2002 11:49 AM To: Multiple recipients of list ORACLE-L At last something that I have experience in. Just do the following: On the target database issue the following: Alter database rename global_name to donot_trigger; We had the same problem. This solves it. The global name has no other influence. Yechiel Adar Mehish - Original Message - To: Multiple recipients of list ORACLE-L <[EMAIL PROTECTED]> Sent: Tuesday, May 21, 2002 6:08 PM > Yes, I "inherited" this, and I am setting up Multimaster > Advanced Replication, setting global_names=false isn't an > option. I have suggested moving the donotfiretrigger logic > into the trigger, which has some initial support. For the > moment, we are changing the code to point to a link with the > same name as the service name (which has obvious limitations, > so hopefully a real fix will get done). > > I was really hoping there might be another workaround bandaid > though, as I really don't want the "fix" to end up permanent. > > Thanks, > > John P Weatherman > Database Administrator > Replacements Ltd. > > > > -Original Message- > Sent: Tuesday, May 21, 2002 11:23 AM > To: Multiple recipients of list ORACLE-L > > > My guess is that you "inherited" an environment > where the DB-Link was setup that way [link-name different > from DB-name] . and then, sometime later, > you set GLOBAL_NAMES=TRUE > > Well you have no choice : > "// *Action: create a database link with the same name as the database it > > // connects to, or set global_names=false." > > Are you setting up Advanced Replication [MultiMaster] > or Simple Replication [Snapshots] ? I believe that > Simple Replication does not mandate GLOBAL_NAMES=TRUE. > > > Hemant K Chitale > > - Original Message - > To: "Multiple recipients of list ORACLE-L" <[EMAIL PROTECTED]> > Sent: Tuesday, 21 May, 2002 9:23 PM > > > > Hi all. > > > > I have recently had to enable global_names in order to set up a > > replicated environment. The application uses a database link to > > reconnect to the database under a differant user id (I inheirited > > this, I had nothing to do with the design!). Appearantly, > > global_names has a prblem with this... > > > > SQL> select * from [EMAIL PROTECTED]; > > select * from [EMAIL PROTECTED] > >* > > ERROR at line 1: > > ORA-02085: database link DONOT_TRIGGER.WORLD connects to DRL2.WORLD > > > > SQL> !oerr ORA 2085 > > 02085, 0, "database link %s connects to %s" > > // *Cause: a database link connected to a database with a different name. > > // The connection is rejected. > > // *Action: create a database link with the same name as the database it > > // connects to, or set global_names=false. > > > > So, does anybody have any work arounds or ideas how I can get this > > thing working again? > > > > TIA, > > > > John P Weatherman > > Database Administrator > > Replacements Ltd. > > -- > > Please see the official ORACLE-L FAQ: http://www.orafaq.com > > -- > > Author: John Weatherman > > INET: [EMAIL PROTECTED] > > > > Fat City Network Services-- (858) 538-5051 FAX: (858) 538-5051 > > San Diego, California-- Public Internet access / Mailing Lists > > > > To REMOVE yourself from this mailing list, send an E-Mail message > > to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in > > the message BODY, include a line containing: UNSUB ORACLE-L > > (or the name of mailing list you want to be removed from). You may > > also send the HELP command for other information (like subscribing). > -- > Please see the official ORACLE-L FAQ: http://www.orafaq.com > -- > Author: Hemant K Chitale > INET: [EMAIL PROTECTED] > > Fat City Network Services-- (858) 538-5051 FAX: (858) 538-5051 > San Diego, California-- Public Internet access / Mailing Lists > > To REMOVE yourself from this mailing list, send an E-Mail message > to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in > the message BODY, include a line containing: UNSUB ORACLE-L > (or the name of mailing list you want to be removed from). You may > also send the HELP command fo
Re: ORA-2085
At last something that I have experience in. Just do the following: On the target database issue the following: Alter database rename global_name to donot_trigger; We had the same problem. This solves it. The global name has no other influence. Yechiel Adar Mehish - Original Message - To: Multiple recipients of list ORACLE-L <[EMAIL PROTECTED]> Sent: Tuesday, May 21, 2002 6:08 PM > Yes, I "inherited" this, and I am setting up Multimaster > Advanced Replication, setting global_names=false isn't an > option. I have suggested moving the donotfiretrigger logic > into the trigger, which has some initial support. For the > moment, we are changing the code to point to a link with the > same name as the service name (which has obvious limitations, > so hopefully a real fix will get done). > > I was really hoping there might be another workaround bandaid > though, as I really don't want the "fix" to end up permanent. > > Thanks, > > John P Weatherman > Database Administrator > Replacements Ltd. > > > > -Original Message- > Sent: Tuesday, May 21, 2002 11:23 AM > To: Multiple recipients of list ORACLE-L > > > My guess is that you "inherited" an environment > where the DB-Link was setup that way [link-name different > from DB-name] . and then, sometime later, > you set GLOBAL_NAMES=TRUE > > Well you have no choice : > "// *Action: create a database link with the same name as the database it > > // connects to, or set global_names=false." > > Are you setting up Advanced Replication [MultiMaster] > or Simple Replication [Snapshots] ? I believe that > Simple Replication does not mandate GLOBAL_NAMES=TRUE. > > > Hemant K Chitale > > - Original Message - > To: "Multiple recipients of list ORACLE-L" <[EMAIL PROTECTED]> > Sent: Tuesday, 21 May, 2002 9:23 PM > > > > Hi all. > > > > I have recently had to enable global_names in order to set up a > > replicated environment. The application uses a database link to > > reconnect to the database under a differant user id (I inheirited > > this, I had nothing to do with the design!). Appearantly, > > global_names has a prblem with this... > > > > SQL> select * from [EMAIL PROTECTED]; > > select * from [EMAIL PROTECTED] > >* > > ERROR at line 1: > > ORA-02085: database link DONOT_TRIGGER.WORLD connects to DRL2.WORLD > > > > SQL> !oerr ORA 2085 > > 02085, 0, "database link %s connects to %s" > > // *Cause: a database link connected to a database with a different name. > > // The connection is rejected. > > // *Action: create a database link with the same name as the database it > > // connects to, or set global_names=false. > > > > So, does anybody have any work arounds or ideas how I can get this > > thing working again? > > > > TIA, > > > > John P Weatherman > > Database Administrator > > Replacements Ltd. > > -- > > Please see the official ORACLE-L FAQ: http://www.orafaq.com > > -- > > Author: John Weatherman > > INET: [EMAIL PROTECTED] > > > > Fat City Network Services-- (858) 538-5051 FAX: (858) 538-5051 > > San Diego, California-- Public Internet access / Mailing Lists > > > > To REMOVE yourself from this mailing list, send an E-Mail message > > to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in > > the message BODY, include a line containing: UNSUB ORACLE-L > > (or the name of mailing list you want to be removed from). You may > > also send the HELP command for other information (like subscribing). > -- > Please see the official ORACLE-L FAQ: http://www.orafaq.com > -- > Author: Hemant K Chitale > INET: [EMAIL PROTECTED] > > Fat City Network Services-- (858) 538-5051 FAX: (858) 538-5051 > San Diego, California-- Public Internet access / Mailing Lists > > To REMOVE yourself from this mailing list, send an E-Mail message > to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in > the message BODY, include a line containing: UNSUB ORACLE-L > (or the name of mailing list you want to be removed from). You may > also send the HELP command for other information (like subscribing). > -- > Please see the official ORACLE-L FAQ: http://www.orafaq.com > -- > Author: John Weatherman > INET: [EMAIL PROTECTED] > > Fat City Network Services-- (858) 538-5051 FAX: (858) 5
RE: ORA-2085
Yes, I "inherited" this, and I am setting up Multimaster Advanced Replication, setting global_names=false isn't an option. I have suggested moving the donotfiretrigger logic into the trigger, which has some initial support. For the moment, we are changing the code to point to a link with the same name as the service name (which has obvious limitations, so hopefully a real fix will get done). I was really hoping there might be another workaround bandaid though, as I really don't want the "fix" to end up permanent. Thanks, John P Weatherman Database Administrator Replacements Ltd. -Original Message- Sent: Tuesday, May 21, 2002 11:23 AM To: Multiple recipients of list ORACLE-L My guess is that you "inherited" an environment where the DB-Link was setup that way [link-name different from DB-name] . and then, sometime later, you set GLOBAL_NAMES=TRUE Well you have no choice : "// *Action: create a database link with the same name as the database it > // connects to, or set global_names=false." Are you setting up Advanced Replication [MultiMaster] or Simple Replication [Snapshots] ? I believe that Simple Replication does not mandate GLOBAL_NAMES=TRUE. Hemant K Chitale - Original Message - To: "Multiple recipients of list ORACLE-L" <[EMAIL PROTECTED]> Sent: Tuesday, 21 May, 2002 9:23 PM > Hi all. > > I have recently had to enable global_names in order to set up a > replicated environment. The application uses a database link to > reconnect to the database under a differant user id (I inheirited > this, I had nothing to do with the design!). Appearantly, > global_names has a prblem with this... > > SQL> select * from [EMAIL PROTECTED]; > select * from [EMAIL PROTECTED] >* > ERROR at line 1: > ORA-02085: database link DONOT_TRIGGER.WORLD connects to DRL2.WORLD > > SQL> !oerr ORA 2085 > 02085, 0, "database link %s connects to %s" > // *Cause: a database link connected to a database with a different name. > // The connection is rejected. > // *Action: create a database link with the same name as the database it > // connects to, or set global_names=false. > > So, does anybody have any work arounds or ideas how I can get this > thing working again? > > TIA, > > John P Weatherman > Database Administrator > Replacements Ltd. > -- > Please see the official ORACLE-L FAQ: http://www.orafaq.com > -- > Author: John Weatherman > INET: [EMAIL PROTECTED] > > Fat City Network Services-- (858) 538-5051 FAX: (858) 538-5051 > San Diego, California-- Public Internet access / Mailing Lists > > To REMOVE yourself from this mailing list, send an E-Mail message > to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in > the message BODY, include a line containing: UNSUB ORACLE-L > (or the name of mailing list you want to be removed from). You may > also send the HELP command for other information (like subscribing). -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: Hemant K Chitale INET: [EMAIL PROTECTED] Fat City Network Services-- (858) 538-5051 FAX: (858) 538-5051 San Diego, California-- Public Internet access / Mailing Lists To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing). -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: John Weatherman INET: [EMAIL PROTECTED] Fat City Network Services-- (858) 538-5051 FAX: (858) 538-5051 San Diego, California-- Public Internet access / Mailing Lists To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).
Re: ORA-2085
I think that this is one of the few Oracle error messages where the suggested "action" truly represents the solution. Far more helpful than "Contact your Oracle Representative"... :-) This might be a long shot, however... SQL> create synonym "[EMAIL PROTECTED]" for sys.dual; Synonym created. SQL> select count(*) from "[EMAIL PROTECTED]"; COUNT(*) -- 1 SQL> select count(*) from [EMAIL PROTECTED]; select count(*) from [EMAIL PROTECTED] * ERROR at line 1: ORA-02019: connection description for remote database not found Naturally, you would not make the synonym reference SYS.DUAL, but DUAL@ instead, to avoid the ORA-02085 error and keep GLOBAL_NAMES enabled... Of course, this might mean changes to the application if you have to add quotation marks around each reference to a table or view, which is what I imagine you are trying to avoid. However, you might be in luck if this application is accessing Oracle via Oracle's own ODBC drivers. By a stroke of luck, the Oracle ODBC drivers (downloadable from "otn.oracle.com") tend to wrap the names of all objects within quotation marks, at least in my limited experience... Hey, it might be worth a look-see. Sometimes you just get lucky... - Original Message - To: "Multiple recipients of list ORACLE-L" <[EMAIL PROTECTED]> Sent: Tuesday, May 21, 2002 7:23 AM > Hi all. > > I have recently had to enable global_names in order to set up a > replicated environment. The application uses a database link to > reconnect to the database under a differant user id (I inheirited > this, I had nothing to do with the design!). Appearantly, > global_names has a prblem with this... > > SQL> select * from [EMAIL PROTECTED]; > select * from [EMAIL PROTECTED] > * > ERROR at line 1: > ORA-02085: database link DONOT_TRIGGER.WORLD connects to DRL2.WORLD > > SQL> !oerr ORA 2085 > 02085, 0, "database link %s connects to %s" > // *Cause: a database link connected to a database with a different name. > // The connection is rejected. > // *Action: create a database link with the same name as the database it > // connects to, or set global_names=false. > > So, does anybody have any work arounds or ideas how I can get this > thing working again? > > TIA, > > John P Weatherman > Database Administrator > Replacements Ltd. > -- > Please see the official ORACLE-L FAQ: http://www.orafaq.com > -- > Author: John Weatherman > INET: [EMAIL PROTECTED] > > Fat City Network Services-- (858) 538-5051 FAX: (858) 538-5051 > San Diego, California-- Public Internet access / Mailing Lists > > To REMOVE yourself from this mailing list, send an E-Mail message > to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in > the message BODY, include a line containing: UNSUB ORACLE-L > (or the name of mailing list you want to be removed from). You may > also send the HELP command for other information (like subscribing). -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: Tim Gorman INET: [EMAIL PROTECTED] Fat City Network Services-- (858) 538-5051 FAX: (858) 538-5051 San Diego, California-- Public Internet access / Mailing Lists To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).
ORA-2085
Hi all. I have recently had to enable global_names in order to set up a replicated environment. The application uses a database link to reconnect to the database under a differant user id (I inheirited this, I had nothing to do with the design!). Appearantly, global_names has a prblem with this... SQL> select * from [EMAIL PROTECTED]; select * from [EMAIL PROTECTED] * ERROR at line 1: ORA-02085: database link DONOT_TRIGGER.WORLD connects to DRL2.WORLD SQL> !oerr ORA 2085 02085, 0, "database link %s connects to %s" // *Cause: a database link connected to a database with a different name. // The connection is rejected. // *Action: create a database link with the same name as the database it // connects to, or set global_names=false. So, does anybody have any work arounds or ideas how I can get this thing working again? TIA, John P Weatherman Database Administrator Replacements Ltd. -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: John Weatherman INET: [EMAIL PROTECTED] Fat City Network Services-- (858) 538-5051 FAX: (858) 538-5051 San Diego, California-- Public Internet access / Mailing Lists To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).
