Discussions
Categories
- 17.9K All Categories
- 3.4K Industry Applications
- 3.3K Intelligent Advisor
- 63 Insurance
- 536.4K On-Premises Infrastructure
- 138.3K Analytics Software
- 38.6K Application Development Software
- 5.8K Cloud Platform
- 109.5K Database Software
- 17.5K Enterprise Manager
- 8.8K Hardware
- 71.1K Infrastructure Software
- 105.3K Integration
- 41.6K Security Software
ORA-02002

Hello,
I am experiencing the below error when running a query over a db link. I can select on the remote system objects "DBA" tables and if i go over to the remote database I can select the objects schema objects fine. The privs seem fine what am i missing. I dont see any errors in the log. We are Oracle EE 12.2.0.1 linux redhat 7.4
ORA-02002: error while writing to audit trail
ORA-00942: table or view does not exist
-update I am kdh0007
privs
grant select on kdh0007.DH_SORT_TEST to public;
select * from [email protected];
ERROR at line 1:
ORA-02002: error while writing to audit trail
ORA-00942: table or view does not exist
on db with table
select * from kdh0007.DH_SORT_TEST;
5 A_A | |
6 A_A | |
7 B_B | |
8 B_B |
works via db link
select table_name from [email protected] where owner in ('KDH0007');
Thanks
Dave
Message was edited by: 2718118
Best Answer
-
Hi, I have the same problem.
I found out it works when I do not prefix the table name with the schema owner (even if the DBLINK is connecting with the schema owner).
select * from [email protected] -> OK
select * from [email protected] -> NOK
Answers
-
It seems permission issue.
Can you please share the below query result -select * from dba_db_links where dblink='<db_link_name>;
Regards
Vivek
-
the link is there. all the above information is the same as the output you are requesting.
I as well felt it was a priv issue at first but when the priv is granted to public how can it be a priv issue. It seems to be occurring on only 1 db.
-
Hi, I have the same problem.
I found out it works when I do not prefix the table name with the schema owner (even if the DBLINK is connecting with the schema owner).
select * from [email protected] -> OK
select * from [email protected] -> NOK
-
yeah we did finally figure out that that did work