Home » SQL & PL/SQL » SQL & PL/SQL » Ora-04052 error plz help!!!
Ora-04052 error plz help!!! [message #241684] Wed, 30 May 2007 07:07 Go to next message
mr_dba01
Messages: 5
Registered: May 2007
Location: mumbai
Junior Member
Dear all,
While running a procedure I have received following error:

**************************************************************
Ora-04052 Error occurred looking up remote object ABNOPR.DATAMART_FLG@DATAMART

Description:
ORA-04052: error occurred when looking up remote object stringstringstringstringstring
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.

*****************************************************************

Is this error from the application side?? What action should have been taken? The table is present on remote database which is connected through database link.Please guide asap.

Thanks & Regards
Prasad
Re: Ora-04052 error plz help!!! [message #241688 is a reply to message #241684] Wed, 30 May 2007 07:24 Go to previous messageGo to next message
tahpush
Messages: 961
Registered: August 2006
Location: Stockholm/Sweden
Senior Member

Seems like KGLR.SQL has not been run in the source database.
Re: Ora-04052 error plz help!!! [message #241692 is a reply to message #241688] Wed, 30 May 2007 07:29 Go to previous messageGo to next message
mr_dba01
Messages: 5
Registered: May 2007
Location: mumbai
Junior Member
Dear,
In this procedure I am updating a table.When i queried the table it is giving me result.But the error pointing towards Update statement in the procedure. What is KGLR.sql?? Why it is run? Does anybody has idea.
Thanks & Regards
Prsad
Re: Ora-04052 error plz help!!! [message #241693 is a reply to message #241692] Wed, 30 May 2007 07:36 Go to previous message
tahpush
Messages: 961
Registered: August 2006
Location: Stockholm/Sweden
Senior Member

Search on Metalink

There are some other suggestions on how to resolve this.
Previous Topic: Create a trigger on a nested table
Next Topic: Querry taking a lot of time
Goto Forum:
  


Current Time: Thu Dec 05 12:54:06 CST 2024