| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
 |
 | |||
| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
|
| |||
Home -> Community -> Mailing Lists -> Oracle-L -> FW: phantom dblink
I forgot to include the part about the global_names. If you set it to false, the problem will go away also.
-----Original Message-----
From: Ruth Gramolini [mailto:rgramolini_at_tax.state.vt.us]
Sent: Wednesday, July 07, 2004 2:13 PM
To: oracle-l_at_freelists.org
Subject: RE: phantom dblink
If one DB is a clone of another then you have to change the DBID in order for the two DB's to appear separate. Use the DBNEWID utility to change the name and DBID or just the DBID. We had a similar problem with DB links and solved it in this way.
HTH,
Ruth
-----Original Message-----
From: oracle-l-bounce_at_freelists.org
[mailto:oracle-l-bounce_at_freelists.org]On Behalf Of Mike Hennesy
Sent: Wednesday, July 07, 2004 1:47 PM
To: oracle-l_at_freelists.org
Subject: phantom dblink
I routinely refresh my DEV instance with a backup of my PROD instance. After I test recovering PROD on the dev machine I create a new control file and rename the instance to DEV with the following:
CREATE CONTROLFILE SET DATABASE "DEV" RESETLOGS ARCHIVELOG Now for the strange part. In DEV there is NOT a dblink for PROD but the query
select * from APP_TABLE_at_PROD ;
returns rows. I would expect a ORA-02019 error. The returned rows are actually coming from the DEV instance and not PROD.
This isn't the end of the world for me by no means. The instance will be refreshed over the weekend and I told the programmers there isn't a dblink to PROD and to not try. I just thought this was a strange behavior and was wondering if anyone else had come across it.
8.1.7.3
Thanks - Mike
 |
 |