Skip to Main Content

Database Software

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

DB Link no longer works as Pluggable Database

1001371Jan 21 2016 — edited Jan 25 2016

We recently upgraded our database from 11g to 12c (I did not perform the upgrade itself). Afterwards, the database was converted into a pluggable database. We then noticed objects that were dependent on db links became invalid objects. We tried using the db links and found that we now have to use the full name (with domain) otherwise it will not work (ORA-02019: connection description for remote database not found). This was never an issue and have confirmed it on other environments that have not been upgraded. We are still new to Multitenant Architecture and our SR with Oracle has not resulted in a solution. Parameters are unchanged and DB_DOMAIN is identical in both environments. When we query for Global_name however, the domain is not attached to it. We're hoping someone has had a similar issue and can point us in the right direction. Adding NAMES.DEFAULT_DOMAIN to the SQLNET.ORA file made no difference. The issue only arises when it is converted to a PDB. Any thoughts are greatly appreciated.

select sysdate from dual@remote_db;

SYSDATE

---------

21-JAN-16

--After cdb conversion

select sysdate from dual@remote_db;

*

ERROR at line 1:

ORA-02019: connection description for remote database not found

This post has been answered by 1001371 on Jan 25 2016
Jump to Answer
Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on Feb 22 2016
Added on Jan 21 2016
9 comments
5,337 views