My Oracle Support Banner

ALTER SESSION SET CURRENT_SCHEMA causes ORA-2019 (Doc ID 793693.1)

Last updated on SEPTEMBER 16, 2020

Applies to:

Oracle Database - Enterprise Edition - Version 9.2.0.8 and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Information in this document applies to any platform.

Symptoms

Alter session set current schema errors with  ORA-02019 with Database links.

The following scenario will explain the problem :

1. There are 2 instances: "A' and "B"

2. On instance "B" are defined 2 schemas: USER1, USER2

On instance "A" also both schema are defined: USER1, USER2.

On instance "A" USER3 is defined who is a owner of TABLE1. USER1 and USER2 on instance "A" have access (select) to objects on schema USER3.

Privileges on instances "A" and B" are the same for USER1 and USER2.

On instance "B" there is defined private DB link "BOP.world" for connection to "A" .

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.