 |
|
ORA-04052: error occurred when looking up remote object
tips
Oracle Error Tips by Stephanie F.
|
The Oracle docs note this on the
ORA-04052 error:
- ORA-04052
error occurred when looking up remote object
- Cause:
An error has occurred when trying to look up a remote object.
-
- Action:
Fix the error. Make sure the remote database system has run KGLR.SQL to
create necessary views used for querying/looking up objects stored in
the database.
During compilation, a forum poster at
Oracle FAQ's continues to
receive ORA-04052 in a link connection Oracle to Sybase:
I am running the SQL and it works
fine over a dblink while I put the same query inside a cursor and am
creating a procedure there is an error that gets generated during
compilation. The link connects a Oracle system to a Sybase system.
The replier informed the Oracle
user that the problem may be that:
Oracle cannot see the remote object. Try to
enable ODBC tracing on the gateway machine to see what is happening
here.
Given this advice, the original issue
concerning ORA-04052 is resolved, yet with a slightly different problem:
The error for some reason was eliminated
when the owner was removed from the table name reference. I am not sure why
it requires the owner information when the SQL is run but when I put
it into the procedure it does not recognize it. In both cases I am connected
to using the same db link and as the same user.
This only required a simple alteration to the
SQL as the discrepancy in this case needed:
In your registry enter string LOCAL
and in value enter the SID. you don't have to write the owner name
after it.
