Cannot drop a database link after changing the global_name ORA-02024 [ID 382994.1]
|
|
|
Modified 22-NOV-2010Type PROBLEMStatus MODERATED
|
|
In this Document
Symptoms
Cause
Solution
Platforms: 1-914CU;
This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.
|
Applies to:
Oracle Server - Enterprise Edition - Version: 9.2.0.6 and later[Release: 9.2 and later ]
Information in this document applies to any platform.
***Checked for relevance on 14-Jan-2010***
Not able to drop a database link after changing the global_name of the database
Earlier global_name had did not have domain name attached to it. The newly added
global_name has a domain name attached to it
When trying to drop the database link after this change throws the following error
ORA-02024: database link not found
But database link is present and the query on user_db_links displays the value
Example :-
SQL> select * from global_name;
GLOBAL_NAME
---------------------------------------------------------
DB10GR2
SQL> create database link l1 connect to scott identified by tiger;
Database link created.
SQL> select db_link from user_db_links;
DB_LINK
---------------------------------------------------------
L1
SQL> alter database rename global_name to DB10GR2.WORLD;
Database altered.
SQL> select * from global_name;
GLOBAL_NAME
---------------------------------------------------------
DB10GR2.WORLD
SQL> drop database link l1;
drop database link l1
*
ERROR at line 1:
ORA-02024: database link not found
Even if the global_name is changed back to the original value, the same errors
occurs.
Initially when a database is created without domain in the global name, null will
used from domain as opposed to .world in earlier releases
Later on when the global_name is altered to contain the domain part also, this
domain remains even when the global_name is altered back a name without domain name
Example :-
SQL> select * from global_name;
GLOBAL_NAME
---------------------------------------------------------
DB10GR2
SQL> alter database rename global_name to DB10GR2.WORLD;
Database altered.
SQL> select * from global_name;
GLOBAL_NAME
---------------------------------------------------------
DB10GR2.WORLD
SQL> alter database rename global_name to DB10GR2;
Database altered.
SQL> select * from global_name;
GLOBAL_NAME
---------------------------------------------------------
DB10GR2.WORLD
The only option left to correct this is to update the base table props$
To implement the solution, please execute the following steps:
1)Take a complete consistent backup of the database
2)Execute the following:
$sqlplus /nolog
connect / as sysdba
SQL> update props$ set value$ = '<globalname without domain>' where name ='GLOBAL_DB_NAME';
SQL>commit;
3)
a) Then connect as the schema user that owns the DBLINK and try to drop it.
If you still get ORA-2024: database link not found , that means the domain name is in your cache and needs to be cleared.
b) Flush shared pool thrice and retry drop database link.
alter system flush SHARED_POOL;
alter system flush SHARED_POOL;
alter system flush SHARED_POOL;
c) If step b doesn't help, you need to bounce your database and try to drop the database link.
4)Once the database link is dropped, the global_name can be changed back to the
desired name containing domain part using the alter database rename global_name
statement
------------------------------------------------------------------------------
Blog: http://blog.csdn.net/tianlesoftware
网上资源: http://tianlesoftware.download.csdn.net
相关视频:http://blog.csdn.net/tianlesoftware/archive/2009/11/27/4886500.aspx
DBA1 群:62697716(满); DBA2 群:62697977(满)
DBA3 群:62697850 DBA 超级群:63306533;
聊天 群:40132017
--加群需要在备注说明Oracle表空间和数据文件的关系,否则拒绝申请
分享到:
相关推荐
oracle网络配置(listener_ora-sqlnet_ora-tnsnames_ora).mht
ORA-29532 ON JAVAMAIL API AFTER UPGRADE TO 11.2.0.4 17804361 SET COLLECTION TYPE AS A BIND VARIABLE IS VERY SLOW AFTER UPGRADE TO 11.2.0.4 18166577 JAVA STORED PROCEDURE FAILS WITH ORA-29532 IN 11.2...
补丁用于解决ORA-39405 TSTZ版本问题的错误 用于把oracle19.0数据库加TSTZ35版本的补丁 可通过SQL> SELECT * FROM v$timezone_file;命令查询时区版本 Oracle Database 19 Release 19.0.0.0.190416DBRU CORE Patch ...
BLOG_【故障处理】Oracle_lhr_ORA-19809错误处理.pdfBLOG_【故障处理】Oracle_lhr_ORA-19809错误处理.pdf
适用于将oracle 19.3版本数据库的时区补丁升级到34(默认为32) 用于解决impdp时遇到ORA-39405 TSTZ版本错误 p29997937_190000_MSWIN-x86-64,适用于windows平台
1)rpm格式包安装配置 1.1 下载以rpm后缀名的包,以11.2.0.4.0 版本为例,其中基础包basic、sql*plus、devel包建议默认下载,其他包视情况而定: oracle-instantclient11.2-basic-11.2.0.4.0-1.x86_64.rpm --基础包...
资源来自pypi官网。 资源全名:TextProcess_Ora-0.0.2.tar.gz
补丁用于解决ORA-39405 TSTZ版本问题的错误 用于把oracle19.3数据库加TSTZ33版本的补丁 可通过SQL> SELECT * FROM v$timezone_file;命令查询时区版本 Oracle Database 19 Release 19.3.0.0.190416DBRU CORE Patch ...
12658755 ORA-7445 [EOACCESS_IU()+1412] COMPILING JAVA THEN RE-EXECUTING IN SESSION STATE 12916550 ORA-7445 [JOE_RUN_VM] 13023632 12.2:PICK RELEASE ASSERTION FAILURE AT JOEZ.C:2943 HOTLOADED XREF-...
1)rpm格式包安装配置 1.1 下载以rpm后缀名的包,以11.2.0.4.0 版本为例,其中基础包basic、sql*plus、devel包建议默认下载,其他包视情况而定: oracle-instantclient11.2-basic-11.2.0.4.0-1.x86_64.rpm --基础包...
1)rpm格式包安装配置 1.1 下载以rpm后缀名的包,以11.2.0.4.0 版本为例,其中基础包basic、sql*plus、devel包建议默认下载,其他包视情况而定: oracle-instantclient11.2-basic-11.2.0.4.0-1.x86_64.rpm --基础包...
ORA-20011,ORA06564错误分析
1.下载instantclient-basic-nt-12.1.0.2.0.zip解压至某路径,如:D:\Database\instantclient_12_1(注:由于PLSQL Developer只支持x32,故只需下载x32的精简系统) 2.获取sqlpls等小工具(精简客户端不自带各种...
python3.6对应的cx_oracle连接11goracle数据库的32位的5.3版本, python3.6对应的cx_oracle的32位的5.3版本
Golden Gate(简称OGG)提供异构环境下交易数据的实时捕捉、变换、投递。 ogg数oracle数据库的产品,是一款很优秀的数据容灾产品
1、下载并解压Oracle客户端(要记住解压路径) instantclient-basic-nt-19.8.0.0.0dbru.zip(我电脑上用的是这个版本连接的Oracle11g) 3、配置window操作系统环境变量(新建以下两个变量) 此电脑(右键)→属性→...
ORA-01157解决方案
ogg112101_ggs_Windows_x64_ora11g_64bit.zip 还有 linux版本的,但是因为文件大于60mb,不能上传,有需要请联系。
12.1.2.0与11.2.0.4通过DB Link查询触发BUG 17890099, ORA-2072 AND ORA-2063 ON QUERY VIA DBLINK
Navicat v15连接oracle报错:ORA-28547: connection to server failed, probable Oracle Net admin error; instantclient-basic-windows.x64-11.2.0.4.0.zip; 最少分; 不吃亏; 不上当;