| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
 |
 | |||
| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
|
| |||
Home -> Community -> Mailing Lists -> Oracle-L -> Re: phantom dblink
Ron:
I thought you got it. The Global_name was still PROD, I just issued the alter to DEV. Select from global_name now shows DEV. Started a new session to the instance but I am still seeing the same results. I wonder if the instance needs to be cycled, will try that later. This would explain it, since other instances created the same way on the same box and other boxes do not show this behaviour and their global_name was altered, not sure how it got missed in DEV.
Thanks - Mike
Ron Thomas <rthomas_at_hypercom.com> wrote:
Did you remember to
alter database rename global_name to DEV ;
Ron Thomas
Hypercom, Inc
rthomas_at_hypercom.com
"To really screw up Linux you have to work at it...To really screw up Windows, you have to work ON
it..."
orcl9ps8dba_at_yahoo.com
Sent by:
oracle-l-bounce_at_freelists.o To
rg oracle-l_at_freelists.org
cc
07/07/04 10:47 AM Subject
phantom dblink
Please respond to
oracle-l_at_freelists.org
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
 |
 |