Skip to content
December 27, 2011 / doganay

ORA-2019 Connection description for remote database not found when ALTER SESSION SET CURRENT_SCHEMA

, , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,

 

Hi,

 

You can use

alter session set current_schema=myuser2;

in order not to specify table owners in you sql script.  But it causes some failure rarely (I assume you connect as myuser1):

When you set your current_schema to myuser2 and use @dblink you will hit this error even if myuser has a working  @dblink private-link. Because myuser1 can never access myuser2’s private @dblink.

ORA-2019 Connection description for remote database not found

solution:

Create one public database link instead of the two private links .

There is also a metalink note:

ALTER SESSION SET CURRENT_SCHEMA causes ORA-2019 [ID 793693.1]

 

try and pray 🙂

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: