Database Link Problem in 9.2.0.5 2004-10-14 - By Mark Strickland
It 's set to "world ". Yet, when I create a database link, it get defined
as db_link.localdomain.
-- --Original Message-- --
From: Spears, Brian [mailto:BSpears@(protected)]=20
Sent: Thursday, October 14, 2004 12:31 PM
To: Mark Strickland; oracle-l@(protected)
Subject: RE: Database Link Problem in 9.2.0.5
Set the default extention in sqlnet.ora.
NAMES.DEFAULT_DOMAIN=3Dworld
Many a head has been scratched over this. :)
Brian
-- --Original Message-- --
From: oracle-l-bounce@(protected)
[mailto:oracle-l-bounce@(protected)] On Behalf Of Mark Strickland
Sent: Thursday, October 14, 2004 3:24 PM
To: oracle-l@(protected)
Subject: Database Link Problem in 9.2.0.5
This probably has an easy answer that I should have thought of already,
and I 'll submit myself to the ridicule if so, but I 'm scratching my
head. I copied a schema from a 9.2.0.4 database on one Linux server to
a 9.2.0.5 database on another Linux server. The schema has a stored
procedure that selects over a database link called "refresh ". The query
"select table_name from user_tables@(protected) " works find in the source
database, but I get ORA-02019 (See ORA-02019.ora-code.com) when I do it in the target database. If I
suffix the db_link with ".world ", it works in the target database. The
database link definitions are identical, global_names is set to false in
both databases and names.default_domain is not set for both. Another
curious thing. When I create a test database link in the target
database called "test " using the same definition as "refresh ", the
db_link in dba_db_links is called "TEST.LOCALDOMAIN ". I can 't figure
out where that is coming from.
Thanks!
Mark Strickland
Seattle, WA
--
http://www.freelists.org/webpage/oracle-l
--
http://www.freelists.org/webpage/oracle-l
|
|
